Professional Documents
Culture Documents
Subledger Accounting
Implementation options for new R12 implementations, and R11i upgrades
Nic has been implementing, designing or developing solution architectures within the Oracle E-Business Suite arena since Release 7.
Nic spent 15 years with Oracle Consulting UK, and in his last year delivered both the R12 Awareness and Financials Accounting Hub training to consultants throughout EMEA. Since leaving Oracle Consulting UK he has worked as an independent contractor implementing:
Financials Accounting Hub at Ministerie van Landbouw, Natuurbeheer en Voedselkwaliteit; LNV (Netherlands Ministry of Agriculture, Nature and Food Quality); Subledger Accounting at LNV and Royal KPN NV (Netherlands landline and mobile telecommunications).
Nic is currently at Balfour Beatty as the R12 Solution owner delivering a common business process and share service centre based solution to 16 disparate Operating Companies in the Balfour Beatty Group.
Agenda
END USER
Import into GL
Post in GL
Financial Options
System Options Accounting Options
11i
Post in GL
Components configured and used by each Subledger separately Single journal repository (can report across subledgers using custom reports) Configuration/Setup
Event and Entity Model
Defines the Events that can happen to a document Defines Entities to extract data from the source subledger document
Sources (Fields)
Document Transaction Entity (Objects, Records)
11
Sources (Fields)
Document Transaction Entity (Objects, Records)
12
Accounting for Journals in the following subledgers of the core Financials Suite:
Assets, Cost Management*, Purchasing**, E-Business Tax, Payables, Receivables, Cash Management
*Cost Management covers Purchasing Receipts, Inventory and Manufacturing **Purchasing covers burden and encumbrance accounting for Requisitions and Purchase Orders
Transaction Account Builder only used for Financials Common Modules (Advanced Global Intercompany System (AGIS))
14
Project Expense Report Account Generator; or Prior transaction (PO related) or Expense Report Template (Expense Reports); or Distribution Set (Invoices)
Assets Payroll Projects Receivables Cash Management Leasing and Finance Management Advanced Global Intercompany System FA Account Generator, or SLA Account Derivation Rules Cost Allocation Flexfield qualifiers and Costing program AutoAccounting for Projects AR: Substitute Balancing Segment Account Generator AutoAccounting for Invoices SLA Account Derivation Rules Accounting Template Set (optional) SLA Transaction Account Builder
16
Moved Multiple Reporting Currency functionality to Reporting currency Moved Taxation functionality embedded in the subledgers to the common tax engine (E-Business Tax) Legal entities model and functionality extended into most subledgers and supports Inter- and Intra- company accounting Replaced Global Intercompany System (GIS) with Advanced Global Intercompany System (AGIS) Replaced Global Accounting Engine with Subledger Accounting
17
Your existing 11i implementation should upgrade without any changes in configuration or additional development subject to regression testing.
Factors that may change an upgrade without changes:
You have accounting (GAAP) issues that are being addressed by manual journals, that could be addressed by changing the seeded accounting You have customised any one of the Account Generators (dependent Workflow technical skills) Projects AutoAccounting (dependent on SQL technical skills) but want to revert to standard TABs and override account derivation in SLA instead You want to implement a secondary ledger with a different chart of accounts. You want implement some of the advanced features of SLA (see R12 implementation options) Note: this may still require PL/SQL technical skills to develop custom sources.
19
By default, the upgrade updates the data for the current fiscal year, as well as the necessary periods of the previous fiscal year, to ensure that at least six periods are included in the upgrade
How much data must be moved to the new model to support the business?, if more required then:
Get patch 5233248 Run SLA Pre-upgrade program to change the number of periods of data to upgrade
How much downtime is available to upgrade old data to the new model? How many old transactions could possibly be reversed or rely on previous accounted transactions in a flow? (e.g. the accounting of payments related to a payable invoices are in a flow) Mitigation: Upgrade by Request can run SLA post-upgrade program at any time to create the missing data
20
21
22
24
10023
Master Data
related to Document (e.g. Supplier)
2099
38765
476
00000
Setup Data
related to Document (e.g. Operating Unit System Options)
25
Journal
DR CR
Journal Line
10023
Master Data
related to Document (e.g. Supplier)
2072
38765
421
00000
Setup Data
related to Document (e.g. Operating Unit System Options)
Master Data
SLA Mapping Set
Document
Distributions
26
Key questions:
Do you want to prevent users entering account code combinations manually anywhere in EBS? Total Accounting Automation Do your Organisational accounting segments change frequently causing documents with long life cycles to use invalid segment values and invalid combinations in the later part of their life?
27
2. TABs calculate using setup and master data. ADRs Use TABs results at journal creation time (accept TAB defaults with minimal override in ADRs)
Oracle Product Development approach
Approach 1:
Change TABs to generate dummy account combinations, change SLA ADRs and SLA JLDs high cost, high complexity, custom development
Approach 2:
Take the seeded functionality: dont change the TABs, dont change the SLA ADRs - low cost, low complexity, no custom development Or, do as you did in 11i implementations: change the TABs, dont change the SLA ADRs - medium cost, medium complexity, custom development
28
Reconciliation References have to be populated (from a source) to use the new GL AutoReconciliation feature for each journal line.
Scenario:
Two source subledgers imported into GL via FAH Subledger A, primarily debits a control/clearing account using a Transaction Reference recorded in the reconciliation reference Subledger B, primarily credits the same control/clearing account using the same Transaction Reference recorded in the reconciliation reference Reconciliation enabled for the control/clearing account GL Automatically Reconciles journal lines that have the same reconciliation reference and the sum of the debits equal the sum of the credits Should be able to prove un-reconciled journal lines balance using reports from the source Subledgers.
29
Visible in SLA Inquiry screens Visible in GL Inquiry screens if SLA Journal Lines are not summarised
30
Visible in SLA Inquiry screens Visible in GL Inquiry screens if SLA Journal Lines are not summarised
31
Can have up to five segments Allows Journal Lines to be retrieved using this value in the SLA Inquiry screens Can be a source for a data warehouse
32
33
34