Oracle R 11.

5
Global Accounting Engine
Education
Rossella Piccirilli Feb 2010
Learning Objectives

 At the end of this session you should be able to:

– Describe the features of Global Accounting Engine
– Describe the business needs
– Discuss the Implementation steps Integration
– Discuss Troubleshooting/Diagnostics

2
Agenda

 Global Accounting Engine Overview

 Global Accounting Engine Demonstration

3
Functional Agenda

 Detailed Description of Each Feature

– Feature and Key Concepts
– Deep Dive
– Demonstration
– Implementation Considerations
– Troubleshooting/Diagnostics

4
Features Summary

 Global accounting engine is a tool/module that allows to comply with accounting

regulations of specific countries. Some accounting entries are legal in one
country but not in other countries.
 The Global Accounting Engine was originally developed to meet the business
requirements of specific countries like Italy France Spain and Portugal
 The Global Accounting Engine is also needed for European foreign subsidiaries
as they are required to do reporting in foreign countries.
 Each subledger transaction, that requires accounting, is represented by a
complete and balanced AX journal entry that is stored in the global accounting
engine tables.
 The Global Accounting Engine replaces the Transfer to General Ledger program
that is used in each subledger application for one subledger and one set of
books.
 Global Accounting Engine is being replaced in R12 by the SLA Subledger
accounting functionality.

5
 Global Accounting Engine
Integrates with Receivables Payables and Inventory

SOB Set of Books What it is Some Benefits

French Rules
Plan Comptable
French Calendar • Subledger Daybooks • Meet Statutory
EUR (AX Journals for requirements for the
subledger entries) submission of
• Statutory Reports, reporting to local
Dr Cr
inquiries, open items, authorities
• Multiple • Corporate Rules =
AX Journals Representations Accounting
• Double posting to set of Standardization
books • Local Rules =
Improved Local
Compliance
• Improved Audit-
ability
Payables Invoice

6
Global Accounting Engine General Architecture
Global Accounting Engine

AX
Transactions
Event
translation
and posting
to GL
GL Posting

7
Major Features
 Multiple Accounting Representations – AX allows Multiple accounting
representations and enable corporations to design and implement global
accounting policies independently from considerations that apply to
subsidiaries operating in other countries, or in highly regulated vertical
markets.
 Analytical Criteria – Analytical criteria enables users to easily report, inquire
and analyze financial and operational data across subledger applications.
 Inquiries, Drilldown and Reporting – The Global Accounting Engine
Architecture provides detailed subledger accounting reports and inquiries that
satisfy local fiscal and business requirements for detailed reconciliation
between subledger transactions and General Ledger.

8
Key Concepts

 Event Model: AX Event Type: for each transaction type, defines possible
actions with accounting significance
 Synchronous posting: possibility to post journals from subledgers to more than
one set of books. The functionality ensures that either journals are posted to
all set of books or to none
 Accounting drilldown: like for subledger tranfer program it is possible to
drilldown inquiry from subledgers to GL and viceversa
 Global Accounting Engine provides a process for closing periods that ensures
a complete and gapless numbering is generated as required in some
countries
 Print specific reports that comply with local statutory requirements (Italian
Journal Book)

9
Key Concepts: Event Types

Event types are seeded data which the Global Accounting Engine uses to
classify and translate events into subledger accounting entries.

Event types are predefined in the system and a translation program

compiles after you assign a rule set to your set of books and freeze the
Subledger Setup window.

Translation schemes are linked to event types and are a component of the
rule set that you assigned. The translation schemes tell the Global
Accounting Engine how to translate event types into accounting entries.

10
Key Concepts: Event Types

 Payables events (some samples)

– CASH_ADJUSTED (Modifying or voiding current payments)
– CASH_APPLIED (Creating or applying current payments)
– NON_CASH_ADJUSTED (Adjusting invoices, prepayments, and
memos)
 Receivables events (some samples)
– NON_CASH_COMPLETE (Getting invoices, debit/credit memos,
commitments, or chargebacks entered and completed)
– NON_CASH_UPDATE (Modifying the revenue lines for accounted
invoices, debit/credit memos, commitments or chargeback)
– RECEIPT_APPLICATION (Applying, reapplying or deleting applications)

11
Key Concepts: Events vs Categories
Predefined events have to be assigned to Journal categories in order
to have the correct sequence assignment.
Translation schemes are predefined in the system

12
Functional Deep Dive Agenda

 Detailed Description of Each Feature

– Feature and Key Concepts
– Deep Dive
– Demonstration
– Implementation Considerations
– Troubleshooting/Diagnostics

13
Business Objectives

 Respect Operational diversity and statutory accounting policies

 Resolve conflicts between corporate and local fiscal requirements for
accounting (double posting)
 Provide Local Statutory reports to comply with Tax and Statutory regulations

14
Business Benefits

 Global Accounting Engine main benefit is to provide a particular transactional

set of the Oracle Financials which permits to comply with Statutory
requirements which else could not be respected
 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

15
Business Benefits

 Posting available for multiple

Transaction Systems set of books
 Predefined validations
Oracle Receivables  Full audit trail
 Accounting drilldowns Information
Delivery

Oracle Payables
Global
Accounting
Analytics
Engine
Oracle Inventory
 Detailed journal entries
 reference information
 Consistent balances Regulatory
Reporting
 On-line inquiries

16
AX Posting Daily User Interaction

END USER END USER END USER END USER

Enter/validate/ Run AX posting

approve transaction Import into Post in GL/can
GL/can be be automatic
automatic
Financial Options

System Options

Accounting
Options

17
Subledger Accounting Deep Dive Agenda

 Detailed Description of Each Feature

– Feature and Key Concepts
– Deep Dive
– Demonstration – Global Accounting Engine Payables/Receivables
– Implementation Considerations
– Troubleshooting/Diagnostics

18
Demo: Global Accounting Engine

Payables
1. Enter an invoice and validate it
2. AX posting to GL
3. View AX journal entry and t-account
4. Query entry in GL and drill back to AX entry and to invoice
5. Main reports

19
Demo Global Accounting Engine
2. Run AX Payables posting Use the specific AX
Subledger responsibility

Choose a Max processing

date
Posting can be also run in
draft mode (Transaction
will not be posted to GL)

20
Demo Global Accounting Engine
2. AX Posting to GL: Check the Posting Manager results

If no transactions are
available for posting the
GL Journal Import will
complete with warning

The event translation

report will list out the
number of translated
events/and or specific
errors failures

21
Demo Global Accounting Engine
3. View AX Journal Entry and T - Account

A valid document
The invoice has to be sequence has to be
accounted assigned (it happens
during invoice validation)

22
Demo Global Accounting Engine
3. View AX Journal Entry and T - Account

Doc sequence number: it

is different from the one
saw earlier (internal
subledger sequence)
This sequence is attached
to both subledger AX
categories assigned.
It means that AX is
numbering all subledgers’
transaction with a single
sequence.

23
Demo Global Accounting Engine
3. View AX Journal Entry and T - Account

It is possible to see the Accounting details are

GL journal only if the visible
posting has not been run
They can be see also if
in draft mode
the posting is run in draft
mode

24
Demo Global Accounting Engine
3. View AX Journal Entry and T – Account – Journal Entry Details

It is possible to see the Accounting details are

GL journal only if the visible
posting has not been run
They can be see also if
in draft mode
the posting is run in draft
mode

25
 Demo Global Accounting Engine
4. Query Entry in GL and drill back

a. GL resp Inquiry >

Account
b. Use summary
template
c. Drilldown on GL
jounals
d. Drill down on AX
Journal

26
Demo Global Accounting Engine
5. Main reports

1. Daily Journal Book – Header/Line Descriptions Report

2. Account Ledger by Account/Accounting Flexfield
Report Use the Account Ledger by Account/Accounting
Flexfield report to review all accounting lines per account
and period
3. Italian Journal Book Report: journal entries in
chronological order based on the sequence assigned by the
Italian Journal Sequencing program
4. Supplier/Customer Subledger by account This report
reconciles to your balances in the Supplier/Customer
Balance by Account/Accounting Flexfield

27
Subledger Accounting Deep Dive Agenda

 Detailed Description of Each Feature

– Feature and Key Concepts
– Deep Dive
– Demonstration
– Implementation Considerations
– Troubleshooting/Diagnostics

28
Implementation Considerations

 Setup for Global Accounting Engine to be done at SOB level and subledger
level
 Document sequences assignments are a setup prerequisite
 Multiple posting option
 Who can submit AX Payables and AX Receivables posting
 Setup a legal sequence for Statutory reporting

29
Implementation Considerations
Setup steps - prerequisites

1. Create new AX specific

Responsibility for each subledger
2. Setup Profile options values:
1. AX Application Name
2. MO: operating unit
3. Sequential numbering
3. Setup Control Accounts for
Payables and Receivables
4. Define Document Sequences
5. Create a specific document
category and legal sequence for
journal book

30
Implementation Considerations
Setup steps - prerequisites
3. Classify subledger accounts as control accounts for reconciliation reports

31
Implementation Considerations
Setup steps - prerequisites
5. Legal Sequencing program

Accounting entries can be both translated by the Global Accounting Engine as well as
manually entered into General Ledger,
Accounting entries are assigned original accounting sequence
numbers at different times, depending on the situation
In each case, accounting sequence numbers are based on
dates other than the accounting date.
The Legal Sequencing program assigns final accounting sequence numbers,
based on the accounting date, to your subledger accounting entries in the Global
Accounting Engine. With the Legal Sequencing program, the accounting sequence
numbers that are assigned to your transactions are unique and gapless within a set
of books.

32
Implementation Considerations
Setup steps

1. Setup Subledger options

2. Freeze posting
3. Start operating

33
Implementation Considerations
Setup steps
Setup legal sequencing
1. Setup Subledger options options

Add subledgers and

related SOB

Associate a rule and

posting SOBs Link categories

Decide Posting options

34
Implementation Considerations
Setup steps

1. Setup Subledger options

Associate a specific
category to all events/or
more categories to
segregate by different
sequences
Link categories the
window will open

35
Implementation Considerations
Setup steps

2. Setup Subledger options

Repeat the steps also for Receivables subledger

and for Inventory (if required
Last step is to click of ‘FREEZE button’.
Concurrent programs are run in order to
generate the AX configuration you setup

36
Implementation Considerations
Setup steps

2. Setup Subledger options

Concurrent programs are run to generate the

rules for each subledger included in the setup

37
Subledger Accounting Deep Dive Agenda

 Detailed Description of Each Feature

– Feature and Key Concepts
– Deep Dive
– Demonstration
– Implementation Considerations
– Troubleshooting/Diagnostics

38
Troubleshooting

 Everytime the AX posting is run we

need to check the event translation
report
 If any error we will check via
backend the following 4 tables:
 AX_EVENTS
 AX_SLE_HEADERS
 AX_SLE_LINES
 AX_BALANCES
 In the AX_EVENTS table we will
check for the event status as ‘E’

39
Troubleshooting: Diagnostics

Global
Accounting
Engine
Program

Concurrent
programs AX tables
outputs

1.User can correct the error

via front end based on
instructions provided in the
output file
2. A datafix is needed
40
Troubleshooting

 Please refer to the attached document

HANDLING POSTING ERRORS DOC for
visualizing some common error scenarios and
related applicable fixes

Microsoft Word
Document

41
Troubleshooting steps

 Run AX posting and view error (even translation report)

 Select via backend
 Fix issue

42
Global Accounting Engine: Debrief

 What happened?
 What did you learn?
 How can it be applied?

43
Summary

 At the end of this module you should be able to:

– Describe the new features of Global Accounting Engine
– Describe the business needs – Market Drivers
– Discuss the Implementation steps
– Discuss Troubleshooting/Diagnostics

44
Questions and Discussions

45