Fusion Application-Steps to create successful Ledger Mapping

In this Fusion Financials training document, user will understand how to create mappings between different Ledgers in Fusion General Ledger. There can be number of reasons of not able to create mapping and most common cause is that set ups steps not completed systematically. This does not allow user to proceed further if one or more steps are not completed before jumping to creating Ledger mapping.

In Oracle Fusion General Ledger, users may come across different errors while creating mapping between Primary to Secondary Ledger. This is attributed to not properly defined steps before you finally create mapping.

For more information, please see the portlets error log for an entry beginning with ADF_FACES-60096 Server Exception during PPR #5

Prerequisite to start creating Ledger mapping is -

Define Ledgers,  Specify Ledger Options and complete the Accounting setups for both Primary Ledger and Secondary Ledger. Both Chart of Account should be defined in well planned manner with rightly selected value sets attached to different segments.

Properly defined values for different value sets and specify Financial Category and Account Type specially for Account Value Set as shown below-

Enter required information for primary Ledger and attach already defined Chart of Account as shown below and save your work. Similarly define Secondary Ledger.

Once you are done with defining Different Ledgers, Review and Submit Accounting Configuration for Ledgers. On successful submission, a confirmation message appears.

Next step is to create Chart of Account Mapping before you start creating Ledger Mapping

• Give name & brief description of COA mapping & the same will appear in LoV while creating mapping
• Carefully choose your target COA and source of COA.
• While creating COA mapping, properly define segments Rules and Account Rules of Mapping.

Finally navigate to Map Primary to Secondary Ledger screen and choose Chart of Account Mapping created above and save your work.

Features of Chart of Accounts Mapping

Supports the ability to create relationship between a source chart of accounts to a target chart of accounts to allow for creating journals to book general ledger entries using an alternative chart of accounts.

This is accomplished by either using segment rules, account rules, or a combination of both.

Where is Chart of Accounts Mapping used?

It is used by the posting program in propagating general ledger entries from the primary ledger to the chart of accounts used by the secondary ledger, providing the means to map the primary ledger chart of accounts to that of the secondary ledger. Used by both balance transfer programs for balance level secondary ledgers as well as cross ledger transfers, whereby balances from one ledger are copied to another ledger.

What are segment rules?

Segment rules serve to map each segment of the target chart of accounts to an account value or segment in the source account.

• Action 1 Three different mapping actions are available:

• Action 2 Assign a constant value for a segment in the target chart of accounts.

Action 3 Copy the value from the source segment to the corresponding target segment. Use hierarchical roll up rules when a specific parent source value and all of its child segment values are mapped to a given detail target segment value. This provides the ability to process groups of source segment values in one single roll up rule.

What if hierarchical mappings of chart of account values change over period of time?

Define parent source values in roll up rules with date effective versions of a hierarchy. Then use the accounting date from the journal entries to reference the chart of accounts mapping that falls within the date effectivity of the hierarchy. This gives the additional benefit of self maintaining mappings since the hierarchies referenced change with time and the applicable child values are processed automatically.

You can also define account rules as part of a chart of accounts mapping. Account rules map a complete target account combination against one or more source account code combinations.

Add comment