When is a Legacy Archive not a Legacy Archive?

As has been discussed in previous posts, the Inoapps Archiving Solution has been one of the most successful of the Inoapps Products Portfolio over the years. Since its launch, it has allowed many of our customers to retire their Oracle E-Business Suite (EBS) estates, reducing their cost of ownership while retaining access to their most valuable data for audit and compliance purposes.

However, the variety of use cases that our customers continue to bring to us for the solution never ceases to amaze the team here at Inoapps. Over the course of the last two weeks alone, we have had three new scenarios arise that we never intended as use cases for the solution.

1. Divestment

A long standing Inoapps customer is divesting one of their business units off to a third party, while continuing to use Oracle EBS for the remaining organizational units. The project required the extraction of a wide variety of data entities for migration to a new ERP application, along with the need to deliver audit and tax compliance. 

The divested business unit needed to be able to report on seven years of historic filings to allow full compliance with any requests they receive. The Inoapps Archiving Solution is the perfect platform to achieve these aims, as it enables the divested business to meet its reporting obligations while segregating the retained business units.

Inoapps Archiving Solution: the perfect solution for business divestment

2. Performance optimization

Performance optimization in an Oracle EBS world is somewhat a dark art, with many different options and approaches. A recent customer was committed to a ‘purge and remove’ strategy, and wanted to carry out a wholescale deletion of historic data from their instance. 

Aside from the need to ensure this was carried out in a fully compliant and approved manner to ensure ongoing support obligations aren’t negated, the customer also wanted the ability to report on the purged and redacted data. 

This apparent contradiction was easily accommodated through the use of the Inoapps Archiving Solution. A copy of the full EBS instance was archived prior to the purge and redaction exercise, allowing fully compliant reporting to be achieved, while enabling the performance optimizations outcomes to be realized.

Inoapps Archiving Solution: the perfect solution for performance optimization

3. Project risk mitigation

The data migration workstream of any transformation project will always represent one of the most complex and highest risk aspects of the project. Migrating large volumes of data from EBS into Oracle Cloud will always be challenging, especially when data volumes are large and complex. 

However, organizations also need to be able to meet their audit and compliance reporting requirements in the period subsequent to any migration. Therefore, any migration strategy that relies on the migration of current or active transactions only will leave the challenge of how to deliver historic reporting with partial data sets. 

A recent EBS to Cloud migration customer raised this exact issue: how to report on Accounts Payable (AP) compliance with data sourced from EBS and Cloud. The solution was simple. The historic EBS instance was migrated to the Inoapps Archiving Solution post cutover. The current and active AP transactions were migrated to Cloud. An Oracle Analytics Cloud Service (OACS) framework was then put in place to allow consolidated AP Invoice reporting to take place across any data from the last seven years, irrespective of whether the transaction happened before or after cutover. 

Inoapps Archiving Solution: the perfect solution to mitigate risk of EBS to Oracle Cloud migrations

The award winning Inoapps Archiving Solution continues to go from strength to strength. If your organization is considering its options for a reporting archive, contact the experts at Inoapps for a chat.