In Part 1 of this articles, we understood about GoldenGate uses in integration with EBS and also learnt key benefits and main Table involved in EBS and Fusion Apps. In this Part-2, let’s understand how balance transfer is done and other features of using Oracle GoldenGate.

How to do Balance Transfer in EBS R12?

In R12 there are 2 concurrent request “Fusion Balance Transfer incremental “ and “ Fusion Balance Transfer Full “  which are run to transfer the balances from EBS R12 to Fusion Applications. Customers are required to do a full balance transfer at least once for each period. After that they could do incremental balance transfer. If customers decide to do a full balance transfer multiple times for a period, then it would be their responsibility to reverse any previously created transfer journals to avoid double accounting (i.e. they will have the double full balance transfer data).

These concurrent request write balance data to the GL_XFR_INTERFACE table on R12 the mapping data is used to apply any required transformation on period Ledger calendar etc. GoldenGate monitors the transaction logs for this table and once a record is committed to the table it will replicate the data to the GL_XFR_INTERFACE table on Fusion. Once the data has been replicated GoldenGate calls a stored procedure which submits journal import on Fusion. Records populated in GL_INTERFACE and GL_XFR_INTERFACE table in Fusion are processed by the standard Journal Import routine and Imported into the Fusion GL.

Registering the existing AU systems within FAH

The EBS and Fusion Accounting Hub instances are linked via a "System Identifier." The value of this identifier is not important, but this value should be same in the EBS and Fusion instances. For this, make sure that whatever value is entered in the EBS site level profile option "GL: Applications Coexistence System Identifier" is the same as that entered on the "Register Applications Coexistence Instance" user interface for the "System Identifier" field in Oracle Fusion Accounting Hub. This user interface is accessible via the Fusion Setup Manager (FSM).

For EBS, determine which Fusion ledgers may accept balance amounts by selecting the "Ledger Assignments" button and selecting which Fusion ledgers should receive the balances. Otherwise, an error will be thrown when transferring balances indicating that there are no ledgers eligible for accepting the balances.

Additionally, complete the EBS profile option: "GL: Applications Coexistence Fusion User" with the username for the Fusion user who should be able to view the results of the balance transfer. Otherwise, it will not be possible to view the results in the general ledger balance transfer report.

How is the Mapping between AU and Fusion Ledgers done?

• Normally Ledgers are mapped on a 1:1 basis - i.e. 1 AU Ledger for 1 Fusion Ledger.
• However it is possible for more than 1 AU Ledger to be mapped to single Fusion Ledger.
• It is not possible to match an AU Ledger to more than 1 Fusion Ledger.
• Ledgers must be of the same currency unless alternate currency is mapped.
• There is no Ledger type validation (secondary AU Ledger can be mapped to the primary Fusion ledger)

Once the AU instance is registered and Ledgers assigned, Filters are used to determine which GL accounts can be used by the system for each ledger. Fusion GL uses these filters to determine the source instance for drilldown and Filter values are assigned to each AU GL by highlight a row, click Actions and select Create Filters. The filter list of values contains the balancing segment values from the Fusion Ledger's Chart of Accounts.

Filter Type:

TOTAL- means that only this particular AU GL can feed into this Fusion ledger.

For example - The Fusion Ledger has three balancing segment values for 'Company'.

• 01 –Company Operations
• 02 -  State Subsidiary
• 03 – UK  Subsidiary

In this example, AU Instance can use any of these three values for booking balances and no other AU Instance can use any of them.

PARTIAL-means that only the specified balancing segment values may be used by this AU GL.

For example - Only the company segment value of '01' is assigned as a filter.

Balance transfer program will only allow journals to record balances that use a company value of 01 for this AU Instance / Fusion ledger.

How is data transferred from AU GL to Fusion GL?

Transfer between AU and Fusion GL is done in two parts.

1. Transfer to Interface Tables

2.  Import to Fusion

Transfer to Interface Tables- Two PL/SQL Concurrent Request Transfer Programs are available in AU systems from SRS.

• Fusion Transfer - Full' to transfer full balances
• Fusion Transfer - Incremental' to transfer incremental balances

These transfer programs extract balances from AU gl_balances_delta table and the standard balances table. Posting and Translation programs in EBS will be changed to populate gl_balances_delta for any AU Ledger that is mapped to a Fusion Ledger. They write the data into interface tables on both the AU and Fusion instances. These processes do not wait for Golden Gate to move the data over to Fusion or for the submission of Journal Import and processes immediately exits upon populating these tables.

Import to Fusion - Journal Import is then run on the Fusion Instance which leverages Oracle's Golden Gate technology to transfer the data in the interface tables from the AU Instance to the Fusion Instance. Golden Gate calls an API that submits Journal Import.  Golden Gate will keep the AU Interface table in sync with the corresponding Fusion interface table. This Journal Import program running on the Fusion instance, will not remove these rows from the interface tables.  Golden Gate calls an API that submits Journal Import to import the data into the fusion GL. Transformation between charts of accounts and calendars from AU to Fusion is done in AU so the full data is not required to be transferred to Fusion before transformation.

Limitations of transferring data from AU to Fusion GL's

• AU Ledgers can only transfer data to Fusion Ledgers that have the same functional currency (unless alternate currency is mapped)
• Fusion chart of accounts and value sets must be maintained in both AU and Fusion databases.
• Each AU Ledger can only be transferred to a single Fusion Ledger.
• Data that goes into a single AU period cannot be split up into multiple Fusion periods.
• Data that goes into a single AU account cannot be split up into multiple Fusion accounts.
• Each Fusion Ledger / segment value combination can only be populated with data from a single AU Instance.  However, this data may come from multiple AU Ledgers.

How data is purged from the Interface tables?

Data is left in the interface table by Journal Import for performance reasons and users can schedule the 'Fusion Transfer - Purge Interface' program to run at convenient times to delete the data. This purge program will only purge data that has been successfully imported. Only Fusion Transfer processes created data will be purged, it will not purge any other interface data. 

Add comment