Integrating Custom Sub-Ledgers with EBS Using BI Applications Financial Analytics

03/09/2012 Jamie Adams, Laxmi Vara Prasad Duvvuri AST Corporation

Agenda
Scenario Previous Options Proposed Solution/Approach

Overview of EBS GL Posting Overview of Financial Analytics

EBS Setups Required

Data Model Design OBIEE Development (RPD & Webcat) Reporting

References Q&A
2

Scenario

Problem Statement
Applicable to Organizations with Business cycles that use Legacy/Third party Systems in conjunction with Oracle Applications

Oracle Application GL Module is the Centralized repository for Balances (Actuals, Encumbrances & Budgets)

All Third Party/Legacy Accounting data is posted to Oracle GL Periodically

Users require Drilldown functionality for Custom Sub-Ledger Data

Accounting and Posting

Sub-Ledger#1

Transfer Accounting entries

Accounting & Posting

All accounting distributions are stored in respective subledgers Posted to GL All Reports are Generated from Oracle GL

Sub-Ledger#2

Transfer Accounting entries

Journal Posting

Oracle General Ledger Interface

Oracle General Ledger

Sub-Ledger#3

Transfer Accounting entries

Oracle EBS Subledgers

Transfer Accounting entries

Drilldown Feature

Sub-Ledger Accounting Entries

Drilldown

Ability to View Sub-Ledger Distributions/Transaction details pertaining to a Journal Entry In Oracle Applications drilldown is supported for various SubLedgers

Sub-Ledger Accounting Entries Sub-Ledger Accounting Entries Sub-Ledger Accounting Entries Sub-Ledger Accounting Entries text Sub-Ledger Accounting Entries Sub-Ledger Accounting Entries text Journal Lines General Ledger Balances Journal Lines

Journal Lines

Sub-Ledger Accounting Entries

Previous Options

Previous Options & Pain Points

In a World without Oracle Business Intelligence Applications Businesses would have had to Develop custom User Interface to Support Sub-Ledger reporting needs Manual Effort required during Reconciliation/Period Close activity Maintain and Support Multiple Systems Extensive customization of EBS

Proposed Solution/Approach

Oracle Applications - GL Posting & Drilldown

10

GL Posting Process - Recap

GL Posting Recap
EBS Sub-Ledgers

All accounting distributions are stored in respective sub-ledgers Accounting is created in SLA Accounting entries are periodically aggregated (based on business needs) Entries are periodically transferred to GL Interface Journal Import creates the Journal entries Journals are posted to GL Balances
Tables

Receivables

Payables

Purchasing

Inventory

Sub-Ledger Accounting Module

GL Interface

Create Accounting GL Transfer Journal Import

GL_INTERFACE Interface Table GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES Journals GL_IMPORT_REFERENCES Reference table GL_BALANCES GL Balances

GL Journal Entries

GL Balances

Journal Posting

11

GL Posting Process Data Flow

12

Financial Analytics Overview - Key Tables

13

Oracle BI Applications Data Model

14

General Ledger Balance

Fact Table W_GL_BALANCE_F

Stores the current balance for general ledger accounts Posted records are considered for calculating the balances Actual balance entries are stored
Granularity

Code Combination, Ledger and Period

EBS Source Table

ETL

GL_BALANCES This table gets populated by extracting the Actual Balance entries from GL Balances

Key Dimension Tables

W_LEDGER_D W_MCAL_DAY_D W_GL_ACCOUNT_D

15

GL Detail Transactions
Fact Table W_GL_OTHER_F

Stores all Journal Entries from GL Stores LOC Amount and DOC Amount OOTB Supports Actuals only

Granularity

Data is stored at JE_LINE_NUM

Source Tables

GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES

ETL Logic

Extracts all GL Journal entries

16

W_GL_LINKAGE_INFORMATION_G Explained
Helper table Links GL Ledger Journals in W_GL_OTHER_F to SL transactions No direct join between W_GL_OTHER_F and W_GL_LINKAGE Linking is enabled for W_AP_XACT_F, W_AR_XACT_F, W_GL_COGS_F or W_GL_REVN_F Sourced from GL_IMPORT_REFERENCES in EBS Supports PSFT as well
17

Metadata Modeling

Model

Join

18

W_GL_ACCOUNT_D

19

W_GL_ACCOUNT_D Explained
GL Account String is also known as Code Combination Sourced from GL_CODE_COMBINATIONS_KFV Stores all Code combinations Primary key Code Combination ID Works in conjunction with W_GL_SEGMENT_D & W_HIERARCHY_D W_GL_SEGMENT_D All values are stored W_HIERARCHY_D All hierarchies are stored

Tables are linked using Segment Code and Value set ID

20

Metadata Model
Fact to GL Account Link GL Account to Segment, Hierarchy Link

21

Custom Sub-Ledgers

22

Custom Sub-Ledgers
Following features are mandatory in Custom SL Data All Sub-Ledger data should be stored on Oracle Database. Accounting String (Code Combination Structure and Values of each Segment) should be same across all Sub-Ledger Systems All Distributions should be aggregated at (but not limited to)

Date All Segments of COA Currency Amount Unique Identifier for each batch Other References to sub-ledger data

Maintain record of batches (Unique Identifiers) interfaced Simple Program to Export the data from Sub-Ledger tables to GL Interface
23

EBS Setups

24

EBS Setups
Following Setups are Mandatory in EBS GL Custom GL Journal Source that includes all the References required

Import References should be enabled for all the sources

Journals should not created for Partially interfaced data

25

Datawarehouse Extensions

26

Datawarehouse Extensions
Following are the key Extensions Required in DW Design transaction tables to store the custom sub-ledger detailed transactions All tables should be designed to store GL Journal references Following are the key extensions required in OBIA DW Extend W_GL_LINKAGE_INFORMATION_G table to support additional import references setup in EBS Linkage (W_GL_LINKAGE_INFORMATION_G.JOURNAL_LINE_INTEGRAT ION_ID) information should be resolved appropriately in Custom SL Tables

High Level architecture diagram is shown in the next slide

27

High Level Architecture of DW

Custom Sub-ledgers
Transfer to GL GL_INTERFACE

EBS

Single Database to store all Reporting data

Custom ETL/ELT OBIA ETL

Custom SL tables can be persisted in OBIA Schema Single Execution plan/data load process can be used to load data into DW

Datawarehouse

AR

AP

GL

Custom Sub-Ledger Data

BI Apps

P&S

Inventory

HR

28

Data Sample

W_GL_ACCOUNT_D All Code combinations W_GL_OTHER_F Stores all Journal Entries W_GL_LINKAGE_INFOR MATION_G Reference table Custom SL DW Fact Table Transaction table to store custom SL Distributions/Transactions

29

OBIEE Modeling

30

OBIEE Modeling

Model the Repository using Oracle recommended Best Practices to support Custom Sub-Ledger Tables Additional Attributes included in the existing BI Applications tables

31

Reporting

32

Reporting
Key Reports required are GL Balances report (P&L or Balance Sheet)

GL Journal Details Report (Include Journal Integration ID)

Custom Sub-Ledger Distributions Report (Include Journal Integration ID) Enable navigation on Journal Integration ID in Journal Details Report to Distributions report

Screenshots of the functionality is shown in the next slide

33

Drilldown in BI Applications

Typical Drilldown can be achieved as shown below GL Balances to GL Journals GL Journals to SL Distributions

34

References

35

References

Oracle BI Applications Documentation Oracle EBS Documentation

36

37