Oracle EBS Data Archiving & Purging - enquero
Transcript of Oracle EBS Data Archiving & Purging - enquero
MANAGING DATA GROWTH IN ORACLE EBS WITH DATA ARCHIVING AND PURGING
Client Overview: Goals:
Value Delivered :
Industry:
Client Passion:
Location :
Sporting goods
Global
Manufacturing & Retail
The client is a leading manufacturer and seller
of sporting goods and gears. With operations
across the world and over four decades of
revolutionizing gaming accessories, they have
established themselves as one of the iconic
names in the industry.
The client had been on Oracle EBS 12.1.3 for
4 years and the exponential data growth was
creating database overhead.
Given the importance of Oracle E-Business Suite applications, it is obvious that the volume of data within them is growing at a staggering rate.
Improve Performance
Save Maintenance Cost
Improve Customer Experience
improvement in
order fulfilment
25% saved in ATP
process
11hrs
Better customer
experience with
lead time shrinkage
Reduction in
infrastructure
maintenance cost
DATA ARCHIVE AND PURGE FORMANUFACTURING & RETAIL COMPANY
Challenges:The client's database was housing a massive
6.2 TB of Oracle Application data footprint.
Data growth was 16% every quarter. The client
had undergone a recent separation from its
parent company and needed a better way of
handling “Archive”, “Purge” and “Retrieve”
activities for Order and Inventory Management
Modules. The key challenges were:
Solution:
A P P R O A C H
Identifying the client's parent company specific information and related transactions
Additional infrastructure and maintenance cost, maintaining parent company data
Slow performing and error prone databases due to huge data volume
Low capacity for development instances
•
•
Enquero demonstrated its solution strategies
and execution methods through thorough
analysis of client’s business use cases. Purge and
Archive framework was implemented with
minimum local deviations.
Our team archived client’s own data of closed
orders, which was crowding the working systems
but were necessary to be maintained for audit
and statutory requirements. They purged the
parent company data to decrease database
overloading. The challenges were addressed in
the following manner:
Identified brand specific information and transactions by:
Researching Item taxonomy in the client
organization
Evaluating systematic strategy to identify brands
and related transactions
Slow performance and low capacity of the development instance were solved by:
Evaluating strategy to purge the data in batches,
thereby, increasing the capacity in each iteration
Developing proof of concept with small batch size
for client review and approval
Leveraging standard solution for optimized API
performance
Data Archiving and Purging:
Ability to identify Sales Orders to build a Purge Set
A custom wrapper leveraging the basic functionalities
of the APIs implemented to build the Purge Set as per
customer’s specific selection criteria
Features to handle exceptions and report errors
for specific users and responsibilities
A subset of the purged records was archived for
historical reporting, thus, decreasing load on
transactional database
•
•
•
•
•
•
•
•
•
•
•
[email protected] +1 (408) 215-4814 www.enquero.com
DATA ARCHIVE AND PURGE FORMANUFACTURING & RETAIL COMPANY
Formulated mechanism to archive
data in Archival system with Database
structure same as seeded Oracle EBS
Built mechanism to retrieve the data
from Archive Instance whenever
needed