This blog post is a part of series with special consideration for high-level data migrations to Oracle Cloud ERP. Previously, we shared a blog post Oracle Cloud ERP Data Migration Recommendations and Best Practices focusing on the data migration across the Cloud ERP. The blog post and an associated whitepaper provided guidance on the approach to convert master and transactional data for business objects in Oracle Cloud Applications, across business functions in Financials, Procurement, Project Management, and related HCM business objects (Employees, Locations). It provided an overview of the methods and techniques to convert the intended business objects across the various Cloud ERP products. 

In this post, we will discuss additional considerations for your high-volume data migrations, focusing on Payables. There are multiple use cases and related configurations that contribute to the shape, scope, and performance of transaction imports. The considerations discussed in this post are intended to be generic and do not relate to a specific organization or industry. 

The specific objects we will review in this blog are: 

  • Open Invoices, Debit and Credit Memos.  

Convert open transactions or remaining balances from partial payments. If that is applicable to you, follow these recommendations:

  • Complete configuration for enterprise structure, Reference Data Set and Payables setups for the business units. 
  • Extract open transactions from legacy systems and transform the format to prepare for conversion. 
  • Complete conversion of suppliers. 
  • Create the account combinations in advance of your data conversion. Use the Import Account Combinations FBDI to create the combinations. 

Best practices for Import Payables and Validate Payables Invoices

  • Use import set and invoice group parameters to allow you to submit the Import Payables Program in parallel.  You can submit up to 20 jobs in parallel with different business units, import sets and import group. 
  • Use one worker for processing, if the invoices count is less than 10k on a single group 
  • Disable document sequencing for conversion
    • Your legacy application should have already sequenced these transactions.
    • Gapless sequencing forces the import process to process invoices one by one rather than in bulk.
  • Do not calculate tax during import. Transaction and withholding tax calculation during import impacts overall performance. 
    • Set the interface invoice attribute “Calculate Tax During Import” flag to “N” to avoid tax calculation during the import process (Invoice Validation will calculate tax by default).  Leaving it null could cause performance issues on the Invoice Import Program.
    • Calculating tax during conversion will add additional overhead
  • Disable the “Import Payables Invoices Report” during migration to further optimize performance. This can be done by enabling the Dev ‘Optin’  AP_34765384 and will help manage the ESS queue.  For the steps to enable this, please log a service request.
  • Set profile: AFLOG_MODULE to ‘XYZ’ at user level (for the user that submits the job) if there are any performance issues. This should be monitored every 30 days and reset since the profile resets every 30 days.  (when setting this profile, verify the reset of 30 days).
  • Ensure table statistics are gathered to prevent performance degradation before starting the migration.  
    • This also applies to running Validate Payables and Create Accounting; there should be no stale stats on AP or XLA tables.

Best practices for Approvals

 

  • When you migrate data from legacy systems to Fusion, follow the instructions to skip approvals in the following note:
    • AP: How to Make Approval Status ‘Not Required’ By Invoice Source  (KB21351)    

Best practices for Create Accounting 

General Tips

  • Assign similar invoices to the same batches to take most advantage of parallel processing.  Pay special attention to:
    • PO and Non PO matched invoices
    • Invoices matched to the same PO (Do not reference or match invoices to the same PO across batches running in parallel.)
    • Invoices for the same supplier
    • Do not run invoice validation and invoice approval in parallel

Conclusion 

Carefully plan and test your data migrations. If you are converting high data volumes, we recommend that you review and follow our recommendations above.  For additional information Data Migrations, please review our whitepaper: Oracle Cloud ERP Data Migration Recommendations and Best Practices on Cloud Customer Connect.