Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Fusion Accounting Hub & R12 Co-Existence Offering

4,582 views

Published on

Presentation explaining the Fusion Accounting Hub and R12 co-existence offerring

Published in: Technology, Business
  • Login to see the comments

Fusion Accounting Hub & R12 Co-Existence Offering

  1. 1. #Consulting #Technology #Product Development Author: Dereck De Almeida http://orabot.me/ Fusion Accounting Hub & R12 CoExistence Offering November, 2013 Copyright © Dereck De Almeida All rights reserved.
  2. 2. Fusion Accounting Hub Co-Existence Overview R12 Sub-Ledgers Fusion Sub-Ledgers (Not Configured) (AP, AR, CE, PAY, HRMS etc.) External Applications R12 Accounting Hub Fusion Accounting Hub Sub-Ledger Accounting Sub-Ledger Accounting General Ledger General Ledger Spreadsheet Manual Journals Essbase Reporting DRM Copyright © Dereck De Almeida All rights reserved.
  3. 3. Considerations • Key Points – The standard co-existence functionality transfers balances from R12 to the Fusion General Ledger – The drill through functionality in the Fusion General Ledger journals inquiry page launches the account enquiry page in R12, you must manually enter the period, currency, ledger and accounting range you want to query – Where access and identity management have not been implemented the user most logon to R12 using their R12 credentials before the account enquiry page is launched – The Fusion General Ledger includes a live embedded essbase cube which is updated real-time when posting journals in Fusion – Reporting is done in the Fusion General Ledger where a number of reporting tools are available such as BI Publisher, BI Answers and Financial Reporting – Journals which complete in error during the journal import execution on Fusion cannot be corrected using the journal import errors correction page and must be transferred again or updated directly on the interface table using SQL Copyright © Dereck De Almeida All rights reserved.
  4. 4. What is Golden Gate? • • Golden Gate is a log based real-time change data capture, golden gate works by analyzing the transaction logs generated every time you transact on your database and applies these transactions to your target database Runtime parameters allow you to control various aspects of golden gate synchronization, such as: – – – • • • Data selection, mapping, transformation and replication Error reporting and logging Resource usage Goldengate is a non-instrusive, low-impact application used for synchronizing data across multiple sources with sub-second latency. Goldengate allows simple transformation, maintains transactional integrity and is resilient against interruptions and failures Oracle provides the configuration files containing the runtime parameters which control the data selection, mapping, transformation and replication required for the co-existence offering so you will not require specialized skills for the installation and configuration of Oracle Goldengate Your database must be in archive log mode Copyright © Dereck De Almeida All rights reserved.
  5. 5. How Does Golden Gate Work? http://www.slideshare.net/ablyth/oracle-goldengate
  6. 6. How is the data transferred from R12 to Fusion?  Initial Load    Initial load is run on the command line as part of the Oracle Goldengate installation The initial load replicates the Fusion setup data for ledger, calendar and period configuration GL_XFR_LEDGERS, GL_XFR_CALENDARS and GL_XFR_PERIODS tables in R12 are populated with the setup data after the initial load has completed Oracle Goldengate will replicate any incremental setup changes after the initial load (New Periods, Ledgers etc.) Copyright © Dereck De Almeida All rights reserved.
  7. 7. How is the data transferred from R12 to Fusion?  Mapping The R12 co-existence patch introduces a number of pages which are used to map the R12 setup data to the Fusion setup data replicated during the initial load Copyright © Dereck De Almeida All rights reserved.
  8. 8. How is the data transferred from R12 to Fusion?  Transfer In R12 there are two concurrent requests “Fusion Balance Transfer Incremental” and “Fusion Balance Transfer Full” which are run to transfer the balances from R12 to Fusion • These concurrent requests write balance data to the GL_XFR_INTERFACE table on R12. The mapping data is used to apply any required transformations on period, ledger, calendar etc.  Goldengate monitors the transaction logs for this table and once a record is commited 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 Copyright © Dereck De Almeida All rights reserved.
  9. 9. How is the data transferred from R12 to Fusion?  Journal Import Records populated on both GL_INTERFACE and GL_XFR_INTERFACE in Fusion are processed by the standard Journal Import routine and imported into the Fusion General Ledger Copyright © Dereck De Almeida All rights reserved.
  10. 10. How is the data transferred from R12 to Fusion? Standard Behaviour Copyright © Dereck De Almeida All rights reserved.
  11. 11. Key Table Structures – Fusion Applications • • • • GL_XFR_SOURCE_SYSTEMS – Identifies the R12 Instance GL_XFR_SYSTEM_LEDGERS – Lists the Ledgers configured in Fusion Applications GL_XFR_TRACKING – Tracking Information for Journal Import run on Fusion General Ledger GL_XFR_INTERFACE – Structured almost identical to the GL_INTERFACE table this table contains the journals which will be imported into the Fusion General Ledger Copyright © Dereck De Almeida All rights reserved.
  12. 12. Key Table Structures – R12 • • • • • • • • • • GL_XFR_SOURCE_SYSTEMS – Identifies the R12 Instance GL_XFR_LEDGER_MAPPINGS – Maps R12 Ledgers to Fusion Ledgers GL_XFR_CALENDAR_MAPPINGS – Maps R12 Calendar to Fusion Calendar GL_XFR_PERIOD_MAPPINGS – Maps R12 Period Names to Fusion Period Names GL_XFR_CCID_MAPPINGS – Maps R12 Code Combinations to Fusion Code Combinations GL_XFR_LEDGERS – List of Ledgers configured in Fusion GL_XFR_CALENDARS – List of Calendars configured in Fusion GL_XFR_PERIODS – List of Periods configured in Fusion GL_XFR_TRACKING – Tracking Information for Journal Import run on Fusion General Ledger GL_XFR_INTERFACE – Structured almost identical to the GL_INTERFACE table this table contains the journals which will be imported into the Fusion General Ledger Copyright © Dereck De Almeida All rights reserved.
  13. 13. Customizing the Drill Behaviour • Key Points – Requires additional configuration on R12, customizations are generally not supported by Oracle Support – Transferring of the R12 journals instead of incremental balances to Fusion General Ledger preserves the R12 journal information in Fusion General Ledger (Category, Batch Name, Journal Name, Reference Columns etc.) – Patch 14830189 delivers functionality to add a custom hook in the Fusion journals screen on the amount field for non standard journal sources. Patch 14330256 includes revised R12 sub-ledger account inquiry page which allows us to pass arguments when calling the page – The reference columns on the imported journal lines in Fusion contain the data required to link back to the R12 journals – On Fusion a custom jsp is deployed, the custom jsp references the data stored in the Fusion journal line reference columns and passes this data as arguments when calling the R12 sub-ledger accounting enquiry screen – Custom Reporting in Fusion Applications can use the reference columns to drill back to R12 and retrieve information directly from the sub-ledgers. Copyright © Dereck De Almeida All rights reserved.
  14. 14. Customizing the Drill Behaviour Standard Behaviour Custom Behaviour Copyright © Dereck De Almeida All rights reserved.
  15. 15. Customizing the Drill Behaviour The journal data in Fusion now appears as it was created in R12 allowing you to search using the R12 journal name, batch, category etc Copyright © Dereck De Almeida All rights reserved.
  16. 16. Customizing the Drill Behaviour Hook for non-standard Oracle journal sources delivered as part of the enhancement request in patch 14830189 Copyright © Dereck De Almeida All rights reserved.
  17. 17. Customizing the Drill Behaviour Assess and Identity Management must be configured to eliminate the need for the user to sign-on using their R12 local login Copyright © Dereck De Almeida All rights reserved.
  18. 18. Customizing the Drill Behaviour Reference data on Fusion journal lines used to pass the arguments when calling the page in R12 Custom jsp invoked by clicking on the journal line amount in Fusion calls the R12 sub-ledger accounting enquiry page for the relevant journal line in Fusion Copyright © Dereck De Almeida All rights reserved.
  19. 19. Customizing the Drill Behaviour Data Model Copyright © Dereck De Almeida All rights reserved.
  20. 20. Patches • • Patch 12871487: Oracle General Ledger and Oracle Fusion Accounting Hub Integration Patch 14330256: ENH:DRILLDOWN FROM FUSION GL JOURNAL LINES DIRECTLY TO THE R12 SLA LINES Copyright © Dereck De Almeida All rights reserved.
  21. 21. References • • • • • • Fusion Accounting Hub (FAH) in a Coexistence Scenario (Doc ID 1275111.1) Where To Setup The Fusion to EBS Co-Existense Ledger Mapping Setups? (Doc ID 1428150.1) EBS - Fusion GL Transfer: Golden Gate Data Transfer Report (Doc ID 1475490.1) Drill Down From Fusion General Ledger To EBS R12 Is Not Showing Any Data (Doc ID 1480297.1) FAQ For R12 Populating GL_INTERFACE Table and Assigning Values to Optional Columns Such as Reference Fields (Doc ID 578959.1) Configuring Oracle GoldenGate to Integrate the E-Business Suite General Ledger with Fusion Accounting Hub (Doc ID 1324692.1) Copyright © Dereck De Almeida All rights reserved.
  22. 22. Q&A Questions ? Copyright © Dereck De Almeida All rights reserved.

×