Professional Documents
Culture Documents
Purpose: This document provides an overview of features and enhancements included in Release 12. It is intended solely to help you assess the business benefits of upgrading to Release 12. Disclaimer: This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.
Agenda
Introduction to Subledger Accounting
Background Key Business Messages Impacted Applications
Agenda
Introduction to Subledger Accounting
Background Key Business Messages Impacted Applications
Background
Projects
Assets
Receivables
Payables
Payroll
Purchasing Inventory
8
Leasing
Background
Issues with this Approach:
Inconsistencies in Accounting Generation
Summary vs. Detail Direct to General Ledger vs. Open Interface
Inconsistent Drilldown from General Ledger Inconsistent Mechansims for Controlling Accounting
FlexBuilder Account Generator Automatic Offsets Etc.
Background
Requirement for Multiple Accounting Representations
Certain European countries require statutory accounting in addition to corporate requirements Similar requirement in certain regulated industries (e.g. Insurance) Global Accounting Engine (AX) introduced to address European requirement Non-AX customers use consulting extensions and/or Global Consolidation System (GCS)
10
Projects
Assets
Receivables
Payables
Payroll
Purchasing Inventory
11
Leasing
Rule-based accounting engine, toolset & repository supporting Oracle E-Business Suite modules
Allows multiple accounting representations for a single business event, resolving conflicts between corporate and local fiscal accounting requirements
Retains the most granular level of detail in the subledger accounting model, with different summarization options in the General Ledger, allowing full auditability and reconciliation Introduces a common data model and UI across subledgers, replaces various disparate 11i setups, providing single source of truth for financial and management analysis
12
13
14
Invoice# 100 Ledger: US Corporate Supplier: ABC Networks GL Date: 2-Mar-2006 Invoice# 100 Supplier: ABC Networks
DR
4 Liability 01-LIAB-200
$1710
15
This is a transaction
SLA provides a distinction between a transaction and the accounting representation of the transaction Accounting distributions did not necessarily go away
Needed for upgrade customers Needed as starting point for SLA (Dont want to force customers to define their own SLA rules) In some cases, necessary to allow user input
Most default SLA rules just pass through the distribution accounts (where applicable) If you modify SLA rules, the ultimate accounting entry may not match the distributions. OK because distribution accounts are just defaults
(New Slide)
17
Better, Richer Information: Automatically capture detailed information to drive financial and management reporting without cluttering up your general ledger Improved Control: Control every transaction that impacts your accounts and drive consistency across the enterprise
Business Agility: React quickly to accounting rule changes, regulatory shifts, and new information requirements without involvement from IT
Clear, Easy Reconciliation: The link between general ledger balances and underlying transactions is maintained automatically for internal and external audit purposes
Copyright 2006, Oracle. All rights reserved.
18
Account for any transaction from any application and centralize accounting policies and processing
Enable compliance with multiple legislative, industry or geography requirements concurrently in a single instance through configurable rules
Streamline accounting processing Provide GL to subledger transaction reconciliation platform by maintaining link between transaction and accounting data Increase transparency and enable full auditability of the transaction and accounting data through the new data model
19
Oracle Receivables
Oracle Projects
rules Predefined Validations Date effective policies Sophisticated error handling Full audit trail Bidirectional drilldowns
Information Delivery
Oracle Payables
Subledger Accounting
Detailed Journal Entries Configurable Reference
Information Consistent Balances On-line inquiries
Analytics
Oracle Payroll
Regulatory Reporting
20
Account for any transaction from any application and centralize accounting policies and processing
Enable compliance with multiple legislative, industry or geography requirements concurrently in a single instance through configurable rules
Streamline accounting processing Provide GL to subledger transaction reconciliation platform by maintaining link between transaction and accounting data Increase transparency and enable full auditability of the transaction and accounting data through the new data model
21
$
Simultaneous Accounting for All Entities
$
French IAS Plan Comptable French Calendar
22
Account for any transaction from any application and centralize accounting policies and processing
Enable compliance with multiple legislative, industry or geography requirements concurrently in a single instance through configurable rules
Streamlined accounting processing Provide GL to subledger transaction reconciliation platform by maintaining link between transaction and accounting data Increase transparency and enable full auditability of the transaction and accounting data through the new data model
23
24
Account for any transaction from any application and centralize accounting policies and processing
Enable compliance with multiple legislative, industry or geography requirements concurrently in a single instance through configurable rules
Streamline accounting processing Provide GL to subledger transaction reconciliation platform by maintaining link between transaction and accounting data Increase transparency and enable full auditability of the transaction and accounting data through the new data model
25
26
Impacted Applications
General Ledger Payables Receivables Projects Assets Costing OPM Public Sector/Federal
Payroll Property Manager Loans Lease Management (Post R12) Cash Management Globalizations Intercompany
27
Agenda
Introduction to Subledger Accounting
Background Key Business Messages Impacted Applications
28
Subledger
A transactional application that generates accounting impact Used to store detailed information not needed for a general ledger Subledgers post summarized activity to a general ledger periodically to maintain centralized account balances for the company Example: The A/R subledger stores receivables by customer, but this detail is not needed in a general ledger
29
30
SLA JE #2
GL Date: 01/27/07
SLA JE #3
GL Date: 01/27/07
GL JE #1
GL Period: Jan-07
101.100.63580.0000.720.000.000 101.100.22100.0000.000.000.000
(New Slide)
31
SLA GL Flow
Journal Import
SLA Journal Entry
(New Slide)
32
Journal Import
SLA Journal Entry
Journal Import
SLA Journal Entry
(New Slide)
33
Journal Import
SLA Journal Entry
(New Slide)
34
Journal Import
SLA Journal Entry
(New Slide)
35
Journal Import
SLA Journal Entry
Journal Import
SLA Journal Entry
(New Slide)
36
Journal Import
SLA Journal Entry
(New Slide)
37
Translation
GL Balances
Journal Import
SLA Journal Entry
(New Slide)
38
Event Model
Applications must tell SLA when an event has occurred. When a user runs the SLA Create Accounting program, it processes all events with the appropriate status
39
Event Classes
Payables
Invoice Debit Memo Prepayment Payments Refunds
Assets
Additions Adjustments Capitalization Depreciation
etc.
Receivables
Invoice Deposit Receipt Bill Receivable
40
Event Types
AP Invoice Events
Validated Adjusted Cancelled
FA Depreciation Events
Depreciation Rollback depreciation
AR Receipt Events
Created Applied Unapplied Updated Reversed
etc.
41
Sources
Identified by application development teams and made available as data in SLA for:
Deriving accounts Inclusion in descriptions Conditial logic: generate a journal line if distribution type = accrual
Mapped to specific SLA accounting attributes such as account, amount, GL Date, conversion rate type, etc.
42
Sources
43
Accounting Attributes
AR_CASH_RECEIPTS_ALL.RECEIPT_DATE AP_INVOICE_LINES_ALL.ACCOUNTING_DATE AR_CASH_RECEIPTS_ALL.AMOUNT AP_INVOICE_LINES_ALL.AMOUNT
(New Slide)
44
Accounting Attributes
45
Agenda
Introduction to Subledger Accounting
Background Key Business Messages Impacted Applications
46
Line Type
47
Line Type
48
Determine the accounting class Set under which conditions the rule will create a line Define the values needed for entry line generation, such as amount, currency, conversion rate information Control behavior for certain features i.e. multiperiod accounting, business flows, line merging and summarization
49
50
51
52
53
54
(New Slide)
55
Chart of Accounts:
Generic
Specific
Yes
Yes
Yes for Any Segment
No
No
Yes
Yes
(New Slide)
56
Description
57
Define how the description on a journal entry or on each of its lines will be built:
Constant Source Value
58
59
Identify the journal line types, descriptions, and account derivation rules that will be used to create a journal entry for a particular event type Generic or specific for a chart of accounts Define processing options for advanced features such as Multiperiod Accounting and Business Flows
60
61
Sources
Transaction Objects
62
Sources
Transaction Objects
63
Agenda
Introduction to Subledger Accounting
Background Key Business Messages Impacted Applications
64
Subledger Balances
Subledger Balances
Journal Import
SLA Journal Entry Balance Calculation SLA Balances
(New Slide)
66
67
68
Supporting References
Transaction attributes can be identified as supporting references and stored on journal entries. In this case:
SLA maintains subledger balances for each supporting reference value and account.
This can apply to balance sheet as well as income statement accounts. In the latter case, subledger balances are reset automatically at fiscal year end. Formerly (in 11i FSAH) known as analytical criteria.
69
Supporting References
SLA JE #1 Invoice No: 136274 101.100.63580 101.100.22100 GL Date: 01/27/07 6,000 EUR 6,000 EUR 3rd Party: Fender Product: X8F54 Buyer: Smithers
SLA JE #2
GL Date: 01/27/07
3,000 EUR 3,000 EUR
SLA JE #3
GL JE #1
GL Period: Jan-07
101.100.63580 101.100.22100
(New Slide)
70
Supporting References
71
72
73
74
New Reports
XML Publisher Reports
Journal Entries: Listing of subledger journal entries Account Analysis: Listing of beginning and ending balances from General Ledger with merge of subledger and General Ledger journal entries Open Account Balances (a.k.a. Trial Balance): Listing of open balances by third party (leverages business flows) Third Party Balances: Balances by third party control account and third party Period Close Exceptions Report: Listing of transactions / subledger journal entries that have not yet been posted to General Ledger
(New Slide)
75
(New Slide)
76
(New Slide)
77
(New Slide)
78
All reports are native to XML Publisher All extracts are very fat, i.e. they include a tremendous amount of data that is not displayed by default but can be added by simple template modifications Journals and Account Analysis reports include GL journals for non-SLA sources Open Account Balances Listing is based on Business Flows
It replaces (and genericizes) the AP Trial Balance. You must create a report definition in advance
(New Slide)
79
New Reports
XML Publisher Reports
Journal Entries: Listing of subledger journal entries Account Analysis: Listing of beginning and ending balances from General Ledger with merge of subledger and General Ledger journal entries Open Account Balances (a.k.a. Trial Balance): Listing of open balances by third party (leverages business flows) Third Party Balances: Balances by third party control account and third party Period Close Exceptions Report: Listing of transactions / subledger journal entries that have not yet been posted to General Ledger
80
Agenda
Introduction to Subledger Accounting
Background Key Business Messages Impacted Applications
81
Dual Posting
Ledger: FR Statutory GL Date: 2-Mar-2006 Invoice Internal Identifier: 1001 Invoice Internal Identifier: 1001
Invoice# 100 Ledger: US Corporate Supplier: ABC Networks GL Date: 2-Mar-2006 Invoice# 100 Supplier: ABC Networks
DR
4 Liability 01-LIAB-200
$1710
82
Draft Accounting
83
Online Accounting
84
Straight-Through Accounting
85
Straight-Through Accounting
Journal Import
SLA Journal Entry
(New Slide)
86
Replacement Accounts
When you disable an account in General Ledger, you can specify a replacement account SLA and GL will both use the replacement account when generating a journal entry which uses the disabled account This helps avoid a common source of errors (and Service Requests)
87
Replacement Accounts
88
Intended to address statutory requirements in certain countries This is in addition to Document Sequencing, available in 11i
89
90
Business Flows
01-EXP-200 DR CR 01-EXP-240 DR CR
Invoice #100
$800
Invoice #100
$200
Invoice #100
$1000
01-LIAB-200 DR CR $800 Payment 1101 $400 for Invoice #100 Invoice #100 Payment 1101 for Invoice $100 #100 01-LIAB-240 DR CR $200 Invoice #100
$500
01-CASH-200 DR CR $400 Payment 1101 for Invoice #100 01-CASH-240 DR CR $100 Payment 1101 for Invoice #100
91
Multi-period Accounting
You can spread a transaction amount across multiple periods, for example to recognize a revenue or expense over time.
92
Accrual Reversals
93
You can enter manual entries in SLA, similar to GL journal entries Manual subledger journal entries must be posted to GL like any other subledger journal entry Unlike GL journal entries, subledger journal entries are identified by a subledger journal source (e.g. Payables)
94
Error Handling
If the accounting program cannot generate any journal entry (for any ledger), it completes with status Error The accounting program generates an execution report detailing any errors To avoid errors, keep in mind:
Accounting rules are pre-validated When you disable an account, you can specify a replacement account
95
Diagnostics Framework
The diagnostics framework captures all sources passed to the accounting program This allows you to validate whether the Accounting Program is doing the correct thing There is performance overhead associated with this, so only enable it when needed.
96
Diagnostics Framework
Accounting Program
Diagnostic Extract
Diagnostic tables
97
Agenda
Introduction to Subledger Accounting
Background Key Business Messages Impacted Applications
98
Customer Impact
Users can optionally copy and then modify the seeded SLA rules Users do not need to modify any responsibilities
If using custom menus or responsibilities, you may need to add SLA forms/reports/programs to the custom responsibilities
Accounts on transaction distributions are now default accounts; seeded rules use these accounts when generating entries. If customer modifies the rules to derive a different account, then there will be a discrepancy between the transaction distribution and journal entries.
Copyright 2006, Oracle. All rights reserved.
99
Customer:
(New Slide)
100
Customer
Defines event model and sources for each transaction source Creates code to raise FSAH events where needed Maps sources to accounting attributes Defines Accounting Methods Builder rules Defines supporting references if desired Enables control accounts if desired Etc.
(New Slide)
101
Upgrade Considerations
By default, the R12 upgrade migrates at least 6 periods of accounting entries from each application to the SLA data model. You can modify this if desired. For prior periods, the historical data is preserved. You can drill from General Ledger to the historical transactions using standard GL drilldown You can upgrade prior periods by request during uptime
102
Agenda
Introduction to Subledger Accounting
Background Key Business Messages Impacted Applications
103
Demonstration Flow
Enter an invoice and validate it Create accounting and post to GL View SLA journal entry and T-account Query entry in GL and drill back to SLA entry and to invoice Modify AMB Rules:
Journal Line Type Account Derivation Rule Journal Entry Description
Construct a rule for Invoice Validation event Create accounting and post to GL View SLA journal entry and compare against first entry
104
Agenda
Introduction to Subledger Accounting
Background Key Business Messages Impacted Applications
105
Agenda
Introduction to Subledger Accounting
Background Key Business Messages Impacted Applications
106
107
Resources
108
QUESTIONS ANSWERS
109