Oracle Cloud offers a broad portfolio of software as a service applications, platform as a service, and social capabilities, all on a subscription basis. Oracle Cloud delivers instant value and productivity for end users, administrators, and developers alike through functionally rich, integrated, secure, enterprise cloud services.
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Subscribe to the OracleAppsHub to receive notifications when there are new posts:

 get RSS feed
 Oracle Fusion Applications (OFA) is a portfolio of next generation suite of software applications from Oracle Corporation. It is distributed across various product families; including financial management, human capital management, customer relationship management, supply chain management, procurement, governance, and project portfolio management
 Get a Free Magzine ...Profit:The Executive's Guide to Oracle Applications

Happy New Year 2008 I wish You ALL !

Posted on December 31st, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

va0120135

 

 

On this last day of 2007, I would like to take a moment to wish everyone a happy, healthy, blessed and peaceful New Year! Hope your 2008 is a great one!

Happy New Year 2008!

 

 

 

Affectionately yours,

Sanjit Anand

Posted in Blogroll, Uncategorized | No Comments »

ACH briefing..

Posted on December 31st, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Someone ask offline for ACH, as term appears in my last post, so thought to have a briefing...here to go

What is ACH?
ACH stands for Automated Clearing House.

The rules for ACH transactions are prepared by the National Automated Clearing House Association (NACHA).

Normally it refers to a national network used by banks and other financial institutions to move transactions (i.e., checks) between financial institutions.

In other sense moving money electronically to and from checking and savings accounts. Typical example would be a check by phone or taking recurring payments directly from a checking/saving account.

• ACH is a “loosely” defined standard for electronic fund transactions.

• Why use ACH payment processing?

  • More secured transaction than hardcopy check
  • Convenience of electronic banking. No visits to bank
  • Increases good-will with employees and suppliers
  • Immediate, tangible savings on every ACH transaction vs. hardcopy check!!!

The Difference with ACH & Credit Card

The MAJOR difference between ACH and credit card processing is that a credit card transaction “captures”
the merchant’s funds from the consumer and essentially guarantees payment. An ACH transaction is a request to transfer funds. The transaction may reject for several reasons with the most common being NSF (non sufficient funds) or a closed account. The funds are not guaranteed.

To debit a consumer's checking or savings account you need their permission to do so. Failure to produce proof of the authorization either by voice recording (one-time payments) or an ACH Authorization form can have consequences.

Where it is popular?

ACH Transaction in US iteslf sharing more than 40% payment pie. This was provided in recent releases Federal Reserve Payment Study.

Suggested Reading

Posted in Oracle Payment Module, Oracle Receivable | No Comments »

Managing receipts for credit card or ACH transactions

Posted on December 30th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Today world credit cards have become part in the our daily life. Not only have credit cards and different electronic payment options,changed the way that consumers manage their personal finances, these have also enabled companies to reduce the risk associated with receivables and improve their cash flow, and reduce the product delivery timeline.Specially in some sectors where there is direct interaction with Consumer , it is important to manage and do the efficient credit processing and recording hundreds of credit card/ACH remittances in Receivable area.

During in implementation, many times it requires the ability to more efficiently manage receipts for credit card or ACH transactions, therefore this post will brief you on the seeded functionlity offered within EBS.

The Importance?

Oracle Receivables integrates with any feeder system, such as Oracle Order Management, to automatically record and process customer payments made before the delivery of goods or services , such of business Scenario that have company companies who is selling there product through internet channel, which is very similar as buying a Dell laptop from internet and paid most of time credit card transactions or Internet banking. Oracle in there EBS environment refers to these transactions as prepayments.

How ?

Oracle receivables creates prepayments as receipts before the related invoices are created. Later, a business event from your feeder system triggers the invoicing process in Receivables, and an AutoInvoice postprocess matches the prepaid receipts to their related invoices.

When you determine that a prepayment is required, you record the payment information in your feeder system, and the information is passed to Oracle Receivables.

What is expected in the setup side is , in Oracle Order Management, if an order is to be evaluated for prepayment, the underline order must utilize both a Payment Term (Collect Credit Card Prepayment check box) at the order level that enables prepayments and a Payment Type of Credit Card, payment terms for an order line are ignored. At the time of order booking, Order Management will determine if the order is Prepaid and make a call to the Oracle Receivables Receipts API for receipt creation.

The Oracle Receivables Receipts API creates a prepayment receipt in Receivables, and processes the receipt using the payment information provided.

Receivables immediately applies all prepayment receipts against the Prepayment application type, and records accounting according to a special prepayment receivables activity. Receivables reserves these receipts for subsequent reapplication to the invoice or invoices that are eventually generated for the order.

When the order is later sent to Receivables for invoicing, AutoInvoice creates an invoice that is marked as prepaid . Additionally, AutoInvoice initiates a postprocess matching program to identify any open prepaid invoices and search for matching prepayment receipts.

Prepayment matching occurs when a prepayment receipt is created from a feeder system such as Order Management. When the subsequent order is shipped and an invoice is created in AR, the AR Automatic Receipts program automatically creates an application of the prepayment against the Transaction. This ONLY occurs if the Prepayment and Transaction stem from the SAME ORDER. If the order is different then a manual application is required to apply the prepayment.

The other functionality for AR Prepayments is , you can also be modified or cancelled for the orders processed. You can:

  • Increase the order amount
  • Decrease the order amount: For credit card prepayments, you can refund the original credit card for a full or partial refund.
  • Change an order without changing the order amount: If an order change does not result in a price change, then Receivables does nothing.
  • Cancel an order: For credit card prepayments, Receivables refunds the original credit card using standard credit card refund functionality.For prepayments made with other payment types, Receivables places the refund amount on account.
  • Reallocate prepaid funds towards an overdue invoice: You can unapply a prepayment receipt and manually reapply the amount to another invoice. When you later import the order into Receivables using AutoInvoice, Receivables considers the prepaid invoice that was associated with the receipt to be unpaid and treats it as a typical overdue invoice.

redarrow-1What's the difference between Deposits and pre-payments?

In reality , it looks very similar kind of process...

A prepayment is payment in advance of the delivery of goods or services.As discussed above , receivables creates prepayments as receipts before the related invoices are created. Later, a business event from your feeder system triggers the invoicing process in Receivables, and an AutoInvoice postprocess matches the prepaid receipts to their related invoices.

On the other hand Deposit a payment/receipt made against a Transaction or Invoice in advance.

redarrow-1How does a Receipt applied to a Credit Card Prepayment that is created and captured in Oracle Order Management get applied to the Invoice once it has been interfaced via AutoInvoice?

The matching of a Credit Card Prepayment Receipt and the associated Invoice is completed when the Invoice is interfaced into Oracle Receivables via AutoInvoice. The AutoInvoice process will look for all Invoice marked as 'Prepaid'. Once it finds one, it will then unapply the Prepayment from the Receipt that was created via the API AR_PREPAYMENTS_PUB.create_prepayment, and apply the Invoice.

Posted in Oracle Receivable | 6 Comments »

The ABCs of Payments

Posted on December 30th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Glossary of terms used in paymentsabc blocks

  • ACH Automated Clearing House
  • BOC Back Office Conversions
  • COGS Costs of Goods Sold
  • DTC Depository Transfer Check
  • EFT Electronic Funds Transfer
  • FAS Financial Accounting Standards
  • GDR Global Depository Receipt
  • HPR Highly Protected Risk
  • IRD Image Replacement Document
  • JIT Just-in-Time Inventory
  • KFC Kansas City Financial Center
  • L/C Letter of Credit
  • MICR Magnetic Ink Character Recognition
  • NACHA National Automated Clearing House Association
  • OBSA Off-Balance Sheet Arrangements
  • POP Point-of-Purchase
  • RCK Re-Presented Check Entries
  • STP Straight Through Processing
  • TEL Telephone Initiated Entry
  • UCC Uniform Commercial Code
  • VAT Value Added Tax
  • WIP Work-in-Progress
  • XBRL eXtensible Business Reporting Language
  • YTM Yield-to-Maturity
  • ZBA Zero Balance Accounts

Posted in Oracle Receivable | No Comments »

RSS Blog

Posted on December 29th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Aggregator for monitoring Oracle related weblogs and news.

This page is under construction as of 2007/12/29. Thank you for your patience.



[QuickRSS=false,false,false,5,true,200] http://www.oracle.com/rss/rss_ocom_pr.xml[/QuickRSS]


Steven Chan's Oracle E-Business Suite Technology
[QuickRSS=false,false,false,4,false,200] http://feeds.feedburner.com/OracleE-BusinessSuiteTechnology[/QuickRSS]

David Haimes's Oracle Intercompany Financials Blog[QuickRSS=false,false,false,3,false,200] http://davidhaimes.wordpress.com/feed/[/QuickRSS]

Floyd Teter's ORCLville
[QuickRSS=false,false,false,2,false,200] http://feeds.feedburner.com/ORCLville[/QuickRSS]

Oracle BI Publisher Blog
[QuickRSS=false,false,false,3,false,200] http://blogs.oracle.com/xmlpublisher/xml/rss.xml[/QuickRSS]

Oracle WMS
[QuickRSS=false,false,false,3,false,200] http://blogs.oracle.com/logistics/xml/rss.xml[/QuickRSS]

ItsFeature
[QuickRSS=false,false,false,2,false,200] http://itsafeature.com/xml/rss.xml[/QuickRSS]
Oracle Financials Strategy
[QuickRSS=false,false,false,3,false,200] http://blogs.oracle.com/financials/xml/rss.xml[/QuickRSS]
[QuickRSS=false,false,false,10,false,200] http://feeds.feedburner.com/orana[/QuickRSS]
[QuickRSS=false,false,false,3,false,200] http://blogs.oracle.com/readingLists/oracleblogs.xml[/QuickRSS]
Oracle Fusion Middleware from architecture to BPEL
[QuickRSS=false,false,false,3,false,200] http://blogs.oracle.com/reynolds/xml/rss.xml[/QuickRSS]

Posted in Oracle Application | No Comments »

Credit Card functionality within i-expense

Posted on December 26th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Is your company is in process of enabling credit card functionality within Oracle Internet Expense?

If answer is yes

It means, once the credit card functionality is enabled in i-Expense, then its allows users to select open credit card transactions and include them in their expense report. The only pre-requisite for your organization would make an agreement with the credit card company to import an electronic file of credit card transactions that summarizes employees' expenses for a period. Once the electronic file is imported and validated, employees would be able to see their credit card transactions and then select them for expensing on their expense report.

AMEX (American Express) Corporate card is most popular one normally companies providing there employee who have requirement to frequent travel or other similar requirement.

American Express Corporate Service does provide these services to there corporate customer:

  1. KR/KP-1205 Cardmember Listing Report
  2. KR-1600 Corporate Express Cash Billed Data
  3. KR/KP-1300 Monthly (Cyclic) Aging Analysis
  4. KR/KP-1301 Interim Aging Analysis
  5. KR/KP-1100 Industry Summary
  6. KR-1022 Monthly (Cyclic) Billed Reconciliation Data
  7. KR-1025 Daily Unbilled Reconciliation Data
  8. KR-1072 Line Item Detail
  9. KR-1075 Line Item Detail-Daily Unbilled

Once your company is decided, to go for AMEX Corporate Card, then Finnace IT/ERP team tries to find out the way to do integration within Oracle.From the above mentions list Oracle does only provide the direct integration for Items #7, which is KR-1025 Daily unbilled Reconciliation Data.

Item #8, 9 are treated as level 3 data, and important to know these kinds of data is not currently supported in Oracle.

Level 3 transaction data refers to the detailed transactions that constitute a single transaction line on the credit card statement. For example, a single hotel transaction can contain the detailed transactions of room charge, meals, and room service.

Not only Amexm there are few more for which Oracle does support credit card transactions data file formats in EBS:

  • American Express KR-1025 format (file name is Card Daily Data Feed)
  • Diner's Club Standard Data File format (file name is TRANS.DAT)
  • Master Card Common Data Format, version 2.0
  • Master Card Common Data Format, version 3.0
  • Visa VCF4 format
  • US Bank Visa format
  • Bank of America Visa TS2 format

arrow next redWhat is offered as a feature in EBS Suite:

  1. Import Credit Card Transactions :As discussed above, if employees in your company use corporate credit cards, you can set up Internet Expenses to enable users to automatically import credit card charges from the card issuer into an expense report. Employees can also categorize each charge as either Business or Personal and, depending on your implementation, place items in dispute.
  2. Flexible Credit Card Payment and Reimbursement Setup: Internet Expenses supports several different scenarios for paying the credit card company and reimbursing employees for corporate credit card charges. You can set up your system to indicate how payment must be remitted to the card issuer. Your choices are:
  • from your organization
  • from the employee
  • from both your organization and the employee

Next will share some setup activity to enable this functionality.

Posted in Oracle Payable | 25 Comments »

What is In “Purchase Order import”

Posted on December 24th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

You can use Purchase Document Open Interface which allows you to quickly import a large volume of Standard Purchase Orders into Oracle Purchasing.

The Import process involves populating the PO interface tables with the document information to be imported and then running the Import
Standard Purchase Orders concurrent program which will validate the data and create the PO in the application and return an error message if something fail.

dgreybarrow First Timer, know these first

Before you start, you need to understand the database objects which play critical role.

Table Name Description Type
PO_HEADERS_INTERFACE This is the table where to insert PO headers data in interface table. Interface table
PO_LINES_INTERFACE This is where we insert PO lines information to be imported ( it is used also for Shipments details ) Interface table
PO_DISTRIBUTIONS_INTERFACE This is where we insert PO distribution details before import Interface table
PO_INTERFACE_ERRORS Stores all errors resulted from import process. Errors table
PO_HEADERS_ALL Stores document headers for purchase orders, purchase agreements,quotations, and RFQs PO Base table
PO_LINES_ALL Stores purchase document lines for purchase orders, purchase agreements, quotations, and RFQs PO Base table
PO_LINE_LOCATIONS_ALL Stores document shipment schedules for purchase orders, purchase agreements, quotations, and RFQs PO Base table
PO_DISTRIBUTIONS_ALL Stores purchase order distributions PO Base table

dgreybarrow Steps by Steps

Know what is getting ining Data into Purchase Order Interface Tables

  1. Load PO header, lines, shipments and distributions data from your source system into the following interface tables
    • PO_HEADERS_INTERFACE
    • PO_LINES_INTERFACE
    • PO_DISTRIBUTIONS_INTERFACE
  2. Once the data has been inserted into the interface tables, a queries like the following can be used to review the information before running the import program :
    • Select * from PO_HEADERS_INTERFACE where INTERFACE_HEADER_ID=<headerid>
    • Select * from PO_LINES_INTERFACE where INTERFACE_HEADER_ID=&headerid
    • Select * from PO_DISTRIBUTIONS_INTERFACE where INTERFACE_HEADER_ID=&headerid

Review data before calling Import Standard Purchase Orders program.

when you submit the import program, third parameter is approval status , which altogether have different logic, which you need to understand the impact.

Purchase Order import

dgreybarrow Understanding approval status in parameter

Significant impact is there on Approval Status parameter and have import logic which is as below:

 

Status in
Interface Table
Imporft Program Approval Status Parameter Resulting Document Status
NULL Incomplete Incomplete
NULL Approved Approved
NULL Initiate Approval Initiate Approval
Incomplete Incomplete Incomplete
Incomplete Approved Incomplete
Incomplete Initiate Approval Initiate Approval
Approved Incomplete Approved
Approved Approved Approved
Approved Initiate Approval Approved

dgreybarrow Take Away

If the records got imported successfully without issues, the records will stay in the interface tables.

  • You can notice , successful records get PROCESS_CODE as “ACCEPTED”
  • It is good practice and important to check the Purchasing Interface Errors report always.
  • This Error report you can submit after your import completed.
  • Because the Purchasing Documents Open Interface saves or errors out line by line, it can accept partial documents. So that you may find a document has been accepted although some lines from it has been rejected . Therefore, to see which document lines were not submitted because of errors, you must check the Purchasing Interface Errors report.

dgreybarrow What happen with IMPORT

This seems sound intresting to you.

  • The Purchasing Documents Open Interface (PDOI) programs first process a record from the PO_HEADERS_INTERFACE table.
  • Then, the program processes the child records in the PO_LINES_INTERFACE table then process the PO_DISTRIBUTIONS_INTERFACE table, before going on to the next PO represented by a record in PO_HEADERS_INTERFACE. Make sense.
  • In between , If the program gets an error while processing a record, the program writes the error details to the PO_INTERFACE_ERRORS table and increments the record's error counter.
  • Therefore, the Purchasing Documents Open Interface saves or errors out on a line-byline basis.
  • This means that if an error is found in a document line, only that line is rolled back (not submitted to Purchasing), and we will be able to find the error in the PO_INTERFACE_ERRORS table.
  • You should be aware , because the Purchasing Documents Open Interface can accept partial documents as it saves or errors out line by line.
  • If an error is found in a header, none of its lines are processed.
  • The Purchasing Documents Open Interface rolls back the header, does not process its lines, and does the following:
    • Sets the PROCESS_CODE column value to REJECTED in the PO_HEADERS_INTERFACE table.
    • Writes out the record identification number and the details of the error to the PO_INTERFACE_ERRORS table.
    • Begins processing the next header record.
  • If no processing errors are found during processing, the header record and all successfully submitted child records are loaded into Purchasing, and then flagged as processed by setting the PROCESS_CODE column to ACCEPTED.

As mention earlier, To check for records in error, the Purchasing Interface Errors Report can be run to provide information as to the cause of the error.

dgreybarrow Other tools

This is most acceptable interface and widly used every where, therefore Oracle have Diagnostics tool for this keeping developer in mind.

Oracle Diagnostics tool name is Oracle Purchasing Documents Open Interface Data Collection Test.

This diagnostic test will verify the data in the interface tables used by the purchasing documents open interface (PDOI) so that it can be used proactively or reactively to resolve or prevent issues in the purchasing documents open interface (PDOI).

Hope you find this is very useful and productive tool.should you need any input send me offline.

Posted in Oracle Purchasing | No Comments »

What is In Requisition import

Posted on December 23rd, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

This interface lets you integrate Oracle Purchasing quickly with new or existing applications such as material requirements planning, inventory management, and production control systems and also helps to enter requisitions from external sources.

dgreybarrow First Timer, know these first

Before you start, you need to understand the database objects which play critical role.

Table Name Description Type
PO_REQUISITIONS_INTERFACE_ALL This is the main Requisition Import interface table Interface table
PO_REQ_DIST_INTERFACE_ALL

The PO_REQ_DIST_INTERFACE_ALL table was used in Release 11, for Self-
Service Purchasing

Interface table
PO_INTERFACE_ERRORS This table stores all errors resulted from import process. Errors table
PO_REQUISITION_HEADERS_ALL Base table that stores requisition headers REQ Base table
PO_REQUISITION_LINES_ALL Base table that stores requisition lines REQ Base table
PO_REQ_DISTRIBUTIONS_ALL This table stores requisition distributions REQ Base table

dgreybarrow Steps by Steps

These are the basic steps for the import process :

  • Insert data into interface table
  • Run import program to insert data into base tables
  • Review imported data from the front end.

First steps start with Inserting data into the Requisitions Interface Tables

You can inserts a single row into the PO_REQUISITIONS_INTERFACE_ALL and/or the PO_REQ_DIST_INTERFACE_ALL table for each requisition line that you want to import.

You identify the set of rows you want to import with each other by setting the INTERFACE_SOURCE_CODE and BATCH_ID columns appropriately in the PO_REQUISITIONS_INTERFACE_ALL table. You then pass these values as parameters to the Requisition Import program. If you do not specify any values for these parameters, the program imports all the requisition lines in the PO_REQUISITIONS_INTERFACE_ALL table.

Typically while inserting you might notice as per documentation, there are three types of columns exist in the in interface tables, as

  • Required Data
    • Required : That mean, You must provide values for all columns that are required.No choice.
    • Conditionally required :You may also have to provide values for columns that are conditionally required. Providing a CURRENCY_CODE, the RATE, RATE_DATE, and RATE_TYPE accordingly to Rate fields are conditionally required.
  • Derived Data : System will default those columns using logic similar to that used by the Requisitions form.
  • Optional Data : These are optional to be filled and will not stop the import process.

Review data before calling Import program.

when you submit the import program, third parameter is approval status , which altogether have different logic, which you need to understand the impact.

dgreybarrow How the Initiate Approval After Requisition Import parameter works and is the relationship between it and AUTHORIZATION_STATUS field?

Yes, this is important to understand the significance and importance of this field .

Req Import

Look at the table below , helps you to understand the value of parameter.

Value in table Parameter
value
Result
Approved YES Req is approved, no call to workflow
Incomplete YES Req is created, workflow is called. Result could be Incomplete, Approved, or In-Process
Approved NO Has no effect, record in the Interface states
Approved, no call to req approval workflow. Req is created as Approved.
Incomplete NO Req is created, and is Incomplete. No call to the workflow for req approval

dgreybarrow Take Away

If the records got imported successfully without issues, the records will stay in the interface tables.

  • You can notice ,successful records get PROCESS_CODE as “ACCEPTED”
  • It is good practice and important to check the Purchasing Interface Errors report always.
  • This Error report you can submit after your import completed.
  • Because the Purchasing Documents Open Interface saves or errors out line by line, it can accept partial documents. So that you may find a document has been accepted although some lines from it has been rejected . Therefore, to see which document lines were not submitted because of errors, you must check the Purchasing Interface Errors report.

dgreybarrow What happen when IMPORT run

This seems sound intresting to you.

when you run Requisition Import concurrent request , program enforced to complete in three steps phases.

The Requisition Import program operates in three phases.

Phase 1 :Validation

The first phase, where the program validates your data and derives or defaults additional information.

  1. The program generates an error message for every validation that fails and accordingly, it will create a row in the PO_INTERFACE_ERRORS table with detailed information about each error.
  2. Program will then check for the column MULTI_DISTRIBUTIONS in the PO_REQUISITIONS_INTERFACE_ALL table, if it is set to yes ( Y ) , Requisition Import will then check for corresponding distributions in the PO_REQ_DIST_INTERFACE_ALL table and if it did not find any corresponding distribution information, it will loads these as errors in the PO_INTERFACE_ERRORS table.

Phase 2 :Grouping

In the second phase, the program groups and numbers the validated requisition lines according to the following criteria:

  1. If you specify a value in the REQ_NUMBER_SEGMENT1 column of the PO_REQUISITIONS_INTERFACE_ALL table, all lines with the same value for this column are grouped together under a requisition header.
  2. If you provide a value in the GROUP_CODE column, all lines with the same value in this column are grouped together under a requisition header.
  3. If you do not provide values in either of these columns, the Requisition Import program uses the Group By parameter to group lines together.
  4. If you do not provide a value for this parameter, the program uses the default Group By that you set up to group requisition lines.

Phase 3 :Deletion

In the third phase, the program deletes all the successfully processed rows in the interface tables, and creates an output which lists the following :

  1. Number of interface records that were successfully imported.
  2. Number of interface records that were not imported.

This output can be viewed by choosing View Output for the Requisition Import concurrent Request ID in the Requests window.

dgreybarrow What Can , what Cann't

You can import approved or unapproved requisitions using the Requisitions Open Interface.

If you are using requisition encumbrance, approved requisitions that you import automatically become pre-approved.

In case there are some records not imported appears in the output from the report, then you can launch the Requisition Import Exceptions Report to view the rows that were not imported by the Requisition Import program along with the failure reason(s) for each row.

dgreybarrow A very common Observation while Requisition import

When you trying to submit a request to run the Requisition Import and when you try to select from the list of values in the parameter field for Import Source, you do not find any value and you receive the error message: "FRM-41830 List of Values contains No Entries "

Therefore you need to understand the List of Values for the Import Source parameter is dynamically determined by the INTERFACE_SOURCE_CODE column value in the PO_REQUISITIONS_INTERFACE_ALL table, So that if there are no values for the LOV, then there are no records in the table for the current organization.

In that case you just have to ensure that there are records in the interface and that the field INTERFACE_SOURCE_CODE is already populated.

Hope this post will be helpful.

Posted in Oracle Purchasing | No Comments »

Data Migration – Why Data Quality important ?

Posted on December 22nd, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Poor data quality in source systems is always addressed before or during the migration process. Regardless of structure, type, or format, source data intended for migration should be validated in terms of the all key attributes:

When ever you are doing a data migration, make sure you have understanding for different dimensions of data quality are as:

 

Dimension Description
Relevance Is it relevant to its intended purpose?
Accuracy Does the data accurately represent another verifiable source in the system?
Completeness Does it provide all the information required?Is all necessary data present?
Integrity Do the data values fall within the acceptable ranges defined by the business? or Is the structure of data and relationships among entities and attributes maintained consistently?
Validity Is it within acceptable parameters for the business?
Timeliness Is it up to date and available whenever required?
Consistency:

Is it consistent and easily to understand?Is all necessary data present?

Accessibility Can it be easily accessed and exported to the target application?
Compliance Does it comply with regulatory standards?

Posted in Conversion | No Comments »

Let’s Talk About ‘Security Groups’ functionality available within Oracle HRMS

Posted on December 19th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

There was a requirement to provide a particular BU user to access to other BU PO's for approval. Normally such kinds of requirement always happen in today's complex business model . To implement this requirement a best we can do it is to use of new profile option which was introduced in Oracle 11i called HR: Cross Business Group , which need to switched on (i.e. set to "Yes") can be used .This new profile option makes it possible for Oracle Application users to view and modify certain specific areas of data across all business groups.

From 11.5.9 onward in HRMS there are two Security Models as:

  • Standard HRMS Security
  • Security Groups

The first one is Standard HRMS security which normally requires defining a security profile, and defining a responsibility for use by application users, whereas security groups means whereby you can reuse a responsibility and assign it to different security profiles in different business groups if required.

Typically Multi-national Companies would be benefited from security as they normally have concept of service centres using multiple business groups and security profiles.

gre The good and bad in new Security Group Model

The Standard Security Model on Oracle HRMS forces a responsibility to be tied to only one business group/security profile. This means that when new business groups are added a brand new set of responsibilities must be set up for the business group, even if the new set of responsibilities is identical in every respect to existing responsibilities assigned to another business group.

The new security group model can cut down dramatically on the number of responsibilities required as it allows responsibilities to be reused by many different business groups.

Here are the key points of how the new security group functionality works.

  • Every time a business group is created a new security group of the same name is also created.
  • Security profiles are defined the same way they are now. There is no change in this functionality.
  • Form Assign Security Profile is activated under the new security model. This form allows a user to be linked to a security profile, responsibility, security group (business group) combination.
  • Profile option HR: Business Group is no longer set manually for HRMS responsibilities. This profile option will be set dynamically when a user selects a responsibility/security group combination at logon.
  • Profile option HR: Security Profile is no longer set manually for HRMS responsibilities. This profile option will be set dynamically when a user selects a responsibility/security group combination at logon.
  • The \Security\User Define Screen in the System Administrator responsibility is no longer user to assign HRMS responsibilities to users as this is now done in the new Assign Security Profile screen.

Please note, that although it is possible in the new security group model to access many business groups through the same responsibility, because of the way users are now assigned to responsibility/security group combinations, an HRMS user can only access the data in one business group at any one time.This can be best understood in next section.

red Overview of Standard Security Model versus new Security Group Model

Lets try to understand by a simple diagram below, what is here is 3 BU defined in global instance representing three BU X-Singapore, X- Australia and third one X-UK. The simple diagram below shows the difference in responsibility set-ups associated with each model.

old securitymodel

In the standard security model when a user logs on or decides to change responsibility the list of responsibility names they have access to are presented to them to select from. In the security group model when a user logs on or decides to change responsibility the list of responsibility names and the associated security group (i.e. business group) assigned to the user are presented to the user to select from. This difference can be best described as:

comparebothmodel

ora3 steps away to switching to the new security model

The steps required to switch to the new security model are as follows;

  • Profile option HR: Cross Business Group should be set to "Yes".
  • Profile option Enable Security Groups must be set to "Service Bureau"
  • Concurrent request Enable Multiple Security Groups must be run.

purpNot to Forget

Once the new security model is switched on, it cannot be switched off.

bluSuggested Reading

  • Enhancements in Oracle HRMS Security in R11.5: Note:202478.1
  • How Does the Cross Business Group Profile Option Impact the Application :Note:224822.1
  • Understanding and Using HRMS Security in Oracle HRMS :Note:394083.1

Other related post in Security

Posted in 11i, EBS Suite, Functional, HRMS | 6 Comments »

Page 1 of 3123

« Previous Entries