GL Journal Data Migration Strategy
GL Journal Data Migration Strategy
GL Journals
Presenter’s Name
Presenter’s Title
Organization, Division or Business Unit
Month 00, 2022
Moving Data with Care and
Precision
We’re getting closer to the final technology configuration. But
first we must securely migrate legacy data. This is an exciting
yet complex process that must be handled with precision and
care. Follow the steps and note the considerations outlined in
this document to maintain security and reduce risk as you
migrate data to new systems.
The following is intended to outline our general product direction. It is intended for information purposes only,
and may not be incorporated into any contract. 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, timing
and pricing of any features or functionality described for Oracle’s products may change and remains at the sole
discretion of Oracle Corporation.
• Accounting Calendar must • 1+ year history; go-live Jul 2014. First accounting period is Jan 2012 with Dec 2012 for
Time Period accommodate first historical period closing balance
• Balance Sheet accounts only • Assets, Liabilities and Equity accounts including closing retained earnings balance, e.g.
Opening Balance • Balance by “company” Cash, Prepaid Expenses, Receivables, Payables, Loans, Share Capital, Retained
• Closing balance of old system Earnings
• Accounting Calendar must • 1+ year history; go-live Jul 2014. First accounting period is Jan 2012 with Dec 2012 for
Time Period accommodate first historical period closing balance
Source Systems for GL Journals Identify the Accounting Date that will be used for Open Balance
conversion
• Identify the source systems that brings open balances for
each of the Business Unit. • The best practice is to use the same accounting date as of
Source system
Primary ledgers, Secondary ledgers and Reporting
ledgers • This will facilitate easy reconciliation with Source system
• Identify the number of ledgers that are available in Source Disable Document Sequence and Accounting Sequence for
system and decide its mapping to target ledger. journals before Conversion and enable after Conversion is
complete
Identify the list of Currencies to be configured for
exchange rates Identify the Cross validation Rules for restricted Account Code
Combinations
Identify the types of GL Accounting Calendars to be
configured and their format Supporting Reference/Descriptive Information and
Reconciliation Reference
Chart Of Account structures
• Identify the additional non-financial information that needs to
• Identify and finalize the Global Chart Of Account structure,
be brought along with each of the Source account balances as
example, number of segments, size, etc.
Supporting Reference/Descriptive Information in GL.
• Number of Regional COA structures and their Mappings to
• Identify the reconciliation reference in source system, which
Global COA
needs to be attached to each of the source account balances.
Data Cleansing • Avoid duplication, e.g. 2 Accounts with similar names may be 1 Account • Quality of converted data
• GL configurations including Org structure, COA etc. are in place. Segment Values
shouldn't be a parent value and it should not be disabled or end-dated.
• Accounting Period is open for the accounting date.
• Currency conversion rates are loaded for all the required dates for conversion, in
case of foreign currency Journals
• Journal Sources and Journal Categories should exist in the System.
• The Ledger ID value need not be provided. Instead of that as per the Oracle
configurations, the "Ledger Name" has to be populated in a different column in the
Journal Import Template. The "Ledger Name" is recommended to be populated
instead of Ledger ID.
• Recommended to bring in the Entered Debit and Entered Credit Amounts from the
Legacy System.
• All dates should be in YYYY/MM/DD format.
• Entered Debits should equal Entered Credits and Accounted Debits should equal
Accounted Credits. In case of journals in the Ledger Currency, the Entered
Debit/Credit should be same as Converted Debit/Credit.
• Provide the Journal Entry Reversal Flag in REFERENCE7 if the journal must be
reversed and Reversal Criteria Set is not used. Journal Reversal Method
Pre-Validation Guidebook is
(REFERENCE9) and Journal Entry Reversal Microsoft Excel
Period (REFERENCE8) should be populated
attached here
if REFERENCE7 is Y. Worksheet
Confidential – © 2022 Oracle Internal/Restricted/Highly Restricted
Data Validation
OCS is responsible for doing detailed validation of below
items.
Reconciliation
Client is responsible for doing detailed reconciliation.
Reconciliation includes detailed validation of data in the
source system with the data loaded in ERP cloud.
Reconciliation includes following tests:
Reconciliation Metrics
• Reconciliation metrics for quantity and control totals can be documented in the given format.
Count Reconciliation
Data File System
Journal Batches
Journal Headers
Journal Lines
Journal References in
any
Retain source data file Retain all standard and Retain reconciliation Retain Retain all
along with Business custom conversion file conversion mapping details
Confirmation for the reports (Refer to data • The conversion related
validation proofs used in data
extracted data validation/reconciliation reconciliation reports needs
and sign-off transformation
• The source date file having
slide for list of reports) to be retained for an agreed
references with during extraction
business confirmation needs • The conversion related period.
read access to with read access
to be retained for an agreed standard and custom reports
Auditors. to Auditors.
• The Auditors should have
period. from target system needs to be complete access to such files.
• The Auditors should have retained for an agreed period.
Period name should match with System configured name. Conversion Period should be either in
Incorrect Period Name/ Closed Period status
2 ‘Open’ status or ‘Future Enterable’ status
6 Incorrect Journal Source/Category Journal Source/Category should match with System configured name
COA combination should match with system configured values/combination. The COA code
Invalid COA code value or combination/ Restricted COA code
7 combination should not violate any valid CVR rules applicable for conversion.
combination
Insufficient User Access to Roles and Ledgers The User should have sufficient privileges to create journals
8
Amount should have the same digit precision as defined at the currency
9 The entered amount does not have the correct currency precision
The DR side and CR side amounts should balance in Entered and Accounted Currency, for each
Unbalanced Journals
10 journal, unless a Suspense account is configured to auto balance
Interface Group Identifier ( column BO in FBDI) should be a "NUMBER". Also, Provide unique inteface
11 Incorrect Group Identifier group identifier for each file
1 2 3 4 5 6 7 8 9
Extract & Receive Pre-Import Import GL Validation Resolve Reconciliati Create/ Reverse AP
Validate Data Validation Journals in Errors & on Import Journals in
Data Extract ERP Cloud Reload data Journals and GL
post in GL
Notes
• Pre-Import Validation - Load to Interface and run sql for major errors, configuration pre-requisites
• Days are indicative and will be modified based on the scope and data volumes
• For each conversion cycle, data changes up to 2 iterations are expected and planned for