Skip to main content

Lessions Learned in Upgrade to R12

Lessions Learned in Upgrade to R12

Backgund:

  • Oracle upgraded to R12 in January 2010 after the books were closed.
  • It took 3.5 days to do the upgrade.
  • Winrunner scripts were used for automated testing.
  • Manual testing was done for the more complex modules.
  • The upgrade added 1.3 terabits of data.
  • Upgraded to R12 from Sep 09 - Mar-11.; Version 12.01 RUP2 and RUP3.
  • Rehearsed pre and post upgrade steps.
  • Oracle upgraded AP, AR, AP, OIE, GL, CM, Procurement, Workflow, AME, OM, etc...CRM apps were also moved from the CRM Suite e-Business Suite to Siebel.
R12 Upgrade Approach:
  • Considered the project as a technical upgrade
  • Only implemented mandatory functionality
  • Migrated 8 years of SLA data
  • Updated test plans
  • Parallel testing
  • Identify features that can be implemented prior to R12
  • New features (TCA for customers) is mandatory in R12
  • Implemented Multi-org access control
  • Setup Ledger sets
  • Replaced custom code with standard code
  • Copy of the database prior to the upgrade
Project Management and Testing Strateg:
  • Identified a Project Manager to oversee all of the upgrade activities
  • Program office to work with both the functional and technical teams
  • Full end to end testing
  • Weekly meetings and status reports
Lessons Learned:
  • Close out any open Workflow transactions. No transactions can be in transit.
  • Make sure the interfaces are cleared
  • Stop any pending or scheduled concurrent manager processes
  • Update request sets
  • Print off any reports used for reconciliation, print off before the upgrade. (IT should take the lead on doing this.)
Sub-ledger Accounting (SLA):
  • SLA sits between the sub-module and the GL
  • All sub-ledger data is stored in SLA
  • SLA holds the true accounting and passes the summary to the GL
  • Reconciliation reports will need to be redone based on the SLA tables.
  • AR and PA autoacccouting rules will remain intact (except intercompany.)
  • You can store alternative accounting in the SLA tables for transactions
  • R12 has a feature for updating invalid code combinations
  • Run Create Accounting (or Sub Accounting in AR) move the data from the sub-ledger to the SLA and the SLA to the GL.
  • Oracle also suggests running the create accounting process throughout the month into SLA.
  • Consider parallelization (multiple threads) with the create accounting process
  • sub-ledger period close exceptions report (provides clear view of the exceptions.)
The Global Accounting engine (AX)
  • All statutory SOB's become secondary ledgers
  • Need to setup sequences
  • Reports are all XML based in R12. Oracle suggested ramping up XML knowledge.
EBtax
  • Tax setup is migrated from 11i to R12
  • Clean-up your tax setup before the update
  • Single global tax engine for AP and AR
Payments (AP)
  • All payments format files are now XML. Any payment format files will not upgrade
  • The 11i files will not upgrade
  • New user interface

TCA (AR)
 
  • Remove all code dependent on backward compatible views in R12
  • New web-based interface for maintaining parties and party sites
Procurement and Iexpense
  • Cleanup catalog, supplier data
  • Consider any 11i per Diem and mileage schedules
  • Remove any expenses that are in transit. They should all be paid or withdrawn.
Intercompany Accounting:
  • Clean-up Intercompany rules
  • Setup distribution accounting and clearing rules using R12 transaction account functionality
Customizations:
  • Review your customizations and ensure they are still needed.
  • R12 has many XML reports that can be easily updated by the user
Other considerations
  • Ensure there is a monthend protocol
  • Run create accounting daily
  • Ensure a request set is created to include create accounting and the transfer to the GL as well as the exception report
  • Ebtax and SLA are new shared modules
  • PA: Post upgrade run the UPG: Upgrade transaction attributes program for historical transactions.
  • IN AP, remember the Payments module is completely reworked.
  • Volume test to find performance issues
  • Scrambling of credit card data
Critical success factors
  • Buy in from all stakeholders
  • Detailed project planning and communications
  • Multiple practice rounds of performing the upgrade
  • Detailed inventory of patches
  • Proper tracking of status and issue reporting
  • Strong user involvement in all phases of the project. There are changes in business process and new forms. User should know how to use these forms.
  • Focus on testing
  • Robust end to end testing
  • Document any reconciling items prior to the R12 upgrade
There is a white paper on Metalink called "R12 Best Practices." The presenter highly recommends this white paper.
Labels:

Comments

Post a Comment

Popular posts from this blog

Create Accounting for a Payment generates errors 95333 and 95359

Create Accounting for a Payment generates errors 95333 and 95359 Error: 95333: A conversion rate does not exist to convert USD to AUD for the conversion type Corporate and conversion date 20-MAR-09 for line -25. Please use the Daily Rates form in General Ledger to enter a conversion rate for these currencies, conversion date and conversion type. 95359: There is no accounted amount for the subledger journal entry line. Please inform your system administrator or support representative that: The source assigned to the accounting attribute Accounted Amount has no value for extract line number 88547. Please make sure the source assigned to the accounting attribute Accounted Amount has a valid value, or assign a different source to this accounting attribute. Solution: 1. Specify a conversion rate for the currencies and conversion date mentioned in the error message 95333 Navigation under the General Ledger responsibility: Setup > Currencies > Currency Rates Manager > Daily Rates ...
15 comments
Read more

Public API’s for FA Transactions

Public API’s for FA Transactions So far Oracle FA is have all the good things except the lack on reporting.Oracle FA is now offer lot of public API's that can be used to interfacing with third party or Oracle application other modules. Here are some of transaction's API's:   Additions API if you have requirement to add assets directly via PL/SQL then use  FA_ADDITION_PUB.DO_ADDITION. If you have selected the Allow CIP Assets check box on the Book Controls window of a tax book when adding CIP assets using the Additions API, the this API automatically adds those CIP assets to that tax book at the same time that they are added to the corporate book. Adjustments API you can make cost adjustments to your assetsdirectly via PL/SQL using  FA_ADJUSTMENT_PUB.DO_ADJUSTMENT  for any  process adjustment. Detail can be found in appendix H) You can use this API if you have a custom interface that makes it difficult to use with the existing Oracle Assets interfaces for adjusti...
Post a Comment
Read more

AP Table Relation Oracle Apps

AP Table Relation Oracle Apps ORACLE PAYABLE TABLE RELATION Source Table Dependent Table Condition AP_INVOICE_LINES_ALL AIL ZX_LINES_SUMMARY ZLS AIL.invoice_id = ZLS.trx_id and  ZLS.application_id  = 200 and  ZLS.entity_code  = 'AP_INVOICES' and  ZLS.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.summary_tax_line_id = ZLS.summary_tax_line_id AP_INVOICE_LINES_ALL AIL ZX_LINES ZL AIL.invoice_id = ZL.trx_id and  ZL.application_id  = 200 and  ZL.entity_code  = 'AP_INVOICES' and  ZL.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and  AIL.line_number = ZL.trx_line_number AP_INVOICE_DISTRIBUTIONS_ALL AID ZX_REC_NREC_DIST ZD AID.invoice_id = ZD.trx_id and  ZD.application_id  = 200 and  ZD.entity_code  = 'AP_INVOICES' and  ZD.event_class_code  in ('STANDARD INVOICES', 'PREPAYMENT INVOICES', 'EXPENSE REPORTS') and...
Post a Comment
Read more