follow the breadcrumbs v1.0 - sequencing in oracle ebs 11i and r12
DESCRIPTION
Oracle R12 Document and Journal Sequencing, Audit Trail - Challenges and SolutionsPresentation at Collaborate 2014 Conference. Changes EBS 11I versus R12.TRANSCRIPT
#C
14
LV
REMINDER
Check in on the COLLABORATE mobile app
#C
14
LV
Follow the Breadcrumbs!
Prepared by:René Römbell / Christian Aderbauer / Hans KolbePrincipal ConsultantCelantra Systems
An Overview Through Document Sequencing
Session ID#:14560
#C
14
LV
2
Agenda
■ Introduction About the Presenters Company Information
A presentation about sequencing – Who cares? Sequencing Classification & Requirements – Why, When?
■ Sequences R12 – Constraints / Solutions ▪ 11I versus R12
■ Options to simplify Org Structure Implementation Impact – Celantra’s Automatic Sequencing Engine - Examples
■ Questions
#C
14
LV
3
San Francisco, CA 94114 +1 415 824 8344 [email protected] http://www.celantrasystems.com
Global Implementations and Process Alignment: Plan, Design, and Execute
Celantra Systems provides innovative solutions to today’s most vexing issues in multi-national ERP configurations. Celantra specializes in helping large organizations tackle the challenges of operational efficiency and process synchronization while improving and automating financial, legal, and trade compliance. Celantra has a proven track record of success in simplifying multi-national implementations, reducing implementation timeframes, and satisfying challenging local in-country requirements.
We address and specialize in Legal and Operational Structure design to support
operational efficiency and reporting compliance Languages and International Document Formats Global Chart of Accounts and Financial Reporting Tax, Statutory, Trade and Customs compliance Intercompany automation and reconciliation Transfer price elimination (Profit in Inventory) Integration with Boundary Systems Instance Strategy and Design IFRS and Multi-GAAP Accounting Project planning, system design, program management, and
supplementary staffing assistance.
Celantra Systems Customers
#C
14
LVAbout the Presenter: Hans Kolbe
■ Hans Kolbe has managed and advised global software implementation projects for over 15 years. His extensive knowledge on Oracle applications is combined with a formal background as a German attorney, trained in international and comparative law.
■ Chair of Multi-National SIG Group
■ Specialist in Intercompany and multi-org configurations, international compliance and transaction tax
■ www.celantrasystems.com
■ 415-730-1131
Visit the Celantra Booth 1055 at Collaborate 2014
4
#C
14
LVChristian Aderbauer
■ Christian Aderbauer, a native of Germany, is based in Boston, MA. He has been working with Oracle EBS since 1996. He was Oracle Principal consultant until 2002.
■ His extensive knowledge on Oracle applications and tools is combined with a deep understanding of functional, technical and project management challenges.
■ Over the last few years he has specialized on rapid pan-European and Asia-Pac implementations for US companies.
■ Christian has become one of the key contacts for Celantra Systems projects with international manufacturing and intercompany components.
■ Email: [email protected]
#C
14
LV
6
Sequencing – Who cares? Why a presentation?
#C
14
LV
7
Because we need a solution for international implementations
And Oracle’s EBS functionality was missing critical functionality in 11I
and in R 12
There are improvements …..
But…….for an efficient org model
We need a little more
#C
14
LV
8
Traditional Silo Model1 Ledger-1 Legal Entity-1 Operating
Unit
SecondaryLedger Primary
Ledger
Secondary Ledger Primary
Ledger
Secondary Ledger Primary
Ledger
Secondary Ledger Primary
Ledger
SecondaryLedger Primary
Ledger
LE
OU
LE
OU
LE
OU
LE
OU
LE
OU
#C
14
LV
New Cross Legal Entity Operating Unit (CLEO)
1 Ledger-n Legal Entities-1 Operating Unit
SecondaryLedgerSecondary
LedgerSecondaryLedgerPrimary
Ledger
LE LE LE
OU
LE LE
#C
14
LV
10
Requirement: Sequencing Why?
#C
14
LV
11
Reasons for Sequencing
■ Audit Trail▪ Identify a document to be able to uniquely
reference and retrieve it
▪ Examples: Order numbers, file references, Serial numbers
■ Ordering▪ Ability to retrieve the initial sort order of a batch of documents
▪ Examples: Chapters in a book, line numbers
■ Completeness / Proof of Change▪ Ability to verify if a document is missing or added
▪ Examples: Book pages
#C
14
LV
12
Requirement: Sequencing When?
#C
14
LV
13
Events for Sequencing■ Receiving a document
▪ To simplify the reference to a document they might be sequenced in the receiving process
■ Enter or generate a document▪ If documents are entered or generated in an IT Systems a
document sequence is useful for audit trail. If gapless sequencing is used delayed document entries can be identified.
■ Account a document▪ If the accounting is not done during the document capture, the
accounting process can result in a new document sequence requirements especially if changes to the original document can generate additional accounting entries
■ Report a Document▪ If a batch documents needs to be filed in a way that it can be
proofed regarding additions or deletions, additional sequencing might be required
#C
14
LV
14
Document , Accounting and Reporting sequences in R12
#C
14
LV
15
R12 Types of Sequencing
■ Document Sequencing▪ Sequences assigned during capturing of transactions
■ Accounting Sequencing▪ Sequences assigned during SLA accounting process or during
GL posting
■ Reporting Sequencing▪ Sequences assigned after period closure of ledger period
▪ Reopening of ledger period will delete sequence
#C
14
LV
16
Sequencing Overview
#C
14
LV
17
Constraints - Solutions
#C
14
LV
18
R12 Sequencing
■ All sequences are defined on Ledger Level▪ If sequencing is planned for a Primary Ledger which is shared
cross multiple Operating Units and/or multiple Legal entities the following workarounds might be considered.— Document sequences:
Define different document categories by Operating Unit/Legal entity and assign the sequences to the categories.Use Forms personalization to assign the corresponding document categories.
— Accounting and Reporting sequences:Consider to create a Secondary Ledger for each Legal entity and mark only the corresponding Balancing segment values as fiscal which belong to the Legal entity which should be sequenced
#C
14
LV
19
We suggest a more efficient org and legal entity structure
#C
14
LV
20
Traditional Silo Model1 Ledger-1 Legal Entity-1 Operating
Unit
SecondaryLedger Primary
Ledger
Secondary Ledger Primary
Ledger
Secondary Ledger Primary
Ledger
Secondary Ledger Primary
Ledger
SecondaryLedger Primary
Ledger
LE
OU
LE
OU
LE
OU
LE
OU
LE
OU
#C
14
LV
New Cross Legal Entity Operating Unit (CLEO)
1 Ledger-n Legal Entities-1 Operating Unit
SecondaryLedgerSecondary
LedgerSecondaryLedgerPrimary
Ledger
LE LE LE
OU
LE LE
#C
14
LV
22
Challenges for CLEO Model in international implementations
■ Sequencing: Document, Accounting and Reporting Sequences
▪ Celantra’s Automatic Sequencing Engine available
▪ Optional – on-line sequencing / month-end sequencing
▪ Optional – update sequence number column / or custom table linked to transaction
▪ Dynamic user defined country rules
▪ Sequencing by LE or Tax Registration available
#C
14
LV
23
Automatic Sequencing Engine - GL
GL Journal Sequencing - Standard Configuration
Country Gapless by Legal Entity
Secondary Ledger
Sorted by which date
Reset sequence at Financial Year end
Belgium Yes YES GL Date No
France Yes YES GL Date No
Germany Yes YES GL Date No
Ireland No No None No
Italy Yes YES GL Date Yes
Netherlands Recommended YES GL Date No
Spain Yes YES GL Date No
#C
14
LV
24
Automatic Sequencing Engine – AP
AP VAT Sequencing - Standard Configuration
Country Sequence Required Method Sort by which
DateReset sequence at Financial Year end
Belgium Yes Direct – By Transaction Type GL Date No
France Yes Direct – By Transaction Type GL Date No
Germany Yes Direct GL Date No
Ireland No Direct GL Date No
Italy Yes Direct – By Transaction Type and EU zone Transaction Date Yes
Netherlands Recommended Direct None No
Spain Yes Direct – By Transaction Type GL Date No
#C
14
LV
25
Example Rule: multiple VAT / Tax Registration Sequencing - AR
#C
14
LV
26
Example Rule: multiple VAT / Tax Registration Sequencing - AP
#C
14
LV#
C1
4LV
Please complete the session evaluationWe appreciate your feedback and insight
You may complete the session evaluation either on paper or online via the mobile app