What are Your Data Retention Options for E-Business Suite Legacy Data When Moving to Oracle Cloud ERP?

Keep EBS with read only access on existing on-premise system 

• EBS data and applications stay on-premise

• Enable EBS system with “read only’ access after cut-over to cloud.

• Retain all EBS data and access the data in read only mode after cut-over to cloud.
• View transactions via UIs and retain reporting capability on historical data.
• Use existing EBS Person Data Removal Tool for obfuscation of data to address local data protection requirements.
• Use existing EBS purge and archive capabilities, if needed.
• No need for additional user training.

Requires:

• ongoing maintenance of EBS 

• in-house hardware 

• EBS Applications and DBA skills

• effort to setup “read only” access responsibilities and update of user assignments

Low

Move EBS instance to Oracle Cloud Infrastructure (OCI)

• EBS historical data and applications move to OCI.
• Enable EBS system with “read only’ access after cut-over to cloud.

• No need for on-premise hardware to support EBS system.
• Retain all EBS data and access the data in read only mode after cut-over to cloud.
• View transactions via UIs and retain reporting capability on historical data.
• Use EBS Person Data Removal Tool for obfuscation of data to address local data protection requirements.
• Use existing EBS purge and archive capabilities
• No need for additional user training

Requires:

• EBS Applications and  DBA skills
• effort to setup “read only” access responsibilities and update of user assignments.

Medium

Backup historical data and build inquiry and reports on the data

• Backup EBS historical data (not EBS applications) to a database.

• The database could be third-party, or it could be Oracle Autonomous Database on OCI which includes Oracle APEX reporting tool.

• Build selected inquiry forms and reports on top of the database data, as needed for the purpose of data retention inquiry and reporting.

   

• Retain all historical EBS data.
• Consider the Oracle Autonomous Database as it provides a self-driving data platform with little maintenance.
• Back up database to Object Storage.
• Use APEX reporting tool to build custom reports on top of EBS historical data.
• If you purchase a consulting service offering, it usually includes backup of historical ERP data to a database. Basic security framework such as IDCS, means users are granted access to specific sets of data.  A certain number of ERP reports and inquiry UIs are usually included. These would typically cover:
  • GL balances, movements, and journal details, including  attachments.
  • Purchase Orders
  • AP invoices, including attachments.
  • AR invoices
  • Expense reports, including attachments
  • and more…

• May need IT staff to develop additional reports.
• IT staff must understand table relationship for historical data to build additional reports.
• No solution to obfuscate data to address local data protection requirements.
• No purge and archive capabilities.

Medium

Combine EBS and Cloud Apps data in data warehouse

• Recommended for customers who need to combine historical and Oracle Cloud ERP data.
• Create an EBS historical data set to ensure data integrity.
• Combine historical and Oracle Cloud ERP data for management reporting purposes.
• You could extract historical data with ETL tools to populate any data warehouse of your choice.

• Get a jumpstart for Oracle Cloud ERP data analysis with Oracle Fusion Analytics prebuilt applications.
• Both EBS historical data and Oracle Cloud ERP data can be available for combined analysis in a data warehouse, such as Oracle Analytics Cloud Platform.
• Extract and load EBS historical report summary for P&Ls and Balance Sheets for year-on-year comparison to a data warehouse  as a customized data set.
• Extract and load EBS ERP historical transactional data to support your management reporting needs.
• To help you better understand Oracle Analytics Platform and Oracle Fusion Analytics prebuilt applications, refer to this blog post (4 parts): Extending Fusion Analytics – Part 1 of 4 (oracle.com)

• High effort to migrate EBS ERP historical data.
• Effort to build reports for EBS ERP historical data, as no standard reports available.
• Risk of double counting data due to potential data overlap when combining EBS historical data and Cloud ERP data for analysis.
• Oracle Analytics Cloud Platform does not support binary data such as attachments.
• No solution to obfuscate data to address local data protection requirements.
• No purge and archive capabilities.