Beruflich Dokumente
Kultur Dokumente
Seguir
Hello Oracle Retail Fans. I’m restricting this article, since it was originally written. Oracle released
Data Conversion Toolkit since RMS 12.0.3 for the automatic data conversion from the legacy
system. The latest version of this tool is available in RMS 13.x version too. Though we have this
Toolkit available, still we need to write multiple other scripts for the data migration as toolkit doesn’t
support migrating dynamic/transactional data.
Please do note that this post is a continuation of Oracle Retail Merchandising System Deep
Dive article and if you are a beginner, you may want to visit Oracle Retail Merchandising System
Overview article before proceeding on this article, however, it is not completely necessary.
Data Migration should be treated as a small parallel project along with the complete implementation
and can be broadly categorized in 4 phases:
Identifying the actual data requirements for the target applications along with all associated data
mappings, assumptions, issues, process flows, data volumes, dependencies and data cleansing
requirements are the main task in the Requirement Definition and Design phase. Following is the
brief approach, should be followed for this phase:
Determine Data Conversion Scope based on the designed functionality of RMS
Determine the All Configuration Options
Determine Conversion Environment Configuration Strategy
Specify Target Data Requirement and the mode of conversion for each table’s field in the
functional area.
Identify the data source (existing source systems) that will be used to populate the Target
1 of 5 22-Jan-19, 10:09
Complete Oracle Retail Tutorials and Training Materials by Nageshwar ... https://oretail.blogspot.com/2014/08/oracle-retail-mom-data-migration-k...
applications.
If data is not available in source systems, it should be created manually in flat files or in
spreadsheets.
Identify and compare the Data Volume and Complexity of the data structures (source and
target systems).
Using the target data requirements which are already identified, map the fields to the
current source system.
Determine if any transformation required between source and target data systems.
Develop a data conversion functional design document for each functional
area. Document should specify overall conversion process (automated/manual) for each
functional area.
Document specifies all the data extract and transform requirements based on the
mapping exercise and also provides the solution approach to all conversion functional
issues.
Identify all the pre and post dependency of each functional area conversion.
Document all default values and any data validation requirements.
Understand data model of each functional area in source system.
Document the data cleansing requirements available and identified at this stage.
Create validation approach for conversion results done my Merchandise toolkit and
manual conversion.
Plan all the validations which are not supported by toolkit with proper business
acceptance.
Plan all the static/transaction tables which need to be reloaded each time in every
environment.
Get the Sign Off on each functional design document.
The entire source data for data conversion should be broadly classified into the three types
described below:
Reference – the application’s configuration data, which controls how the application functions
and is referenced during general operations (e.g. calendar, functions, error messages, and
system options)
Foundation – the business data which is generally non-historic and has a low rate of change
(e.g. hierarchies and suppliers) also known as Master Data. This may be further classified
as dynamic or static, depending on the rate of change. Static data changes hardly ever or
rarely.
2 of 5 22-Jan-19, 10:09
Complete Oracle Retail Tutorials and Training Materials by Nageshwar ... https://oretail.blogspot.com/2014/08/oracle-retail-mom-data-migration-k...
Transactional / Dynamic Data – the business data that has a higher rate of change and
contains transactional information about the daily functioning of the business (e.g.
purchase orders, transfers, and inventory management transactions)
Potential Issue
Action Plan
Responsible Party/Person
On-line application testing – users will test the on-line application to ensure
that it performs as required with the converted data.
Validation built in to the Merchandising Conversion Toolkit.
Data calculations – various aggregations of quantitative data can be performed
on both Oracle Retail and source applications and then compared
On-line samples – on-line sampling in RMS and the source application(s) will
be performed to check for errors / inconsistencies
The degree of testing will be based on the sensitivity of the data and the volumes to be
tested
3 of 5 22-Jan-19, 10:09
Complete Oracle Retail Tutorials and Training Materials by Nageshwar ... https://oretail.blogspot.com/2014/08/oracle-retail-mom-data-migration-k...
The Business representatives, who will in turn sign off the data, will perform most of the
data validation activities supported by the data conversion team
Business acceptance / sign off should involve compiling all the output from the data
validation activities. These will be reviewed and signed off by the Business executives
indicating that the data is accurate and will be accepted for ongoing business operations
The detailed Business acceptance requirements will generally be defined during the build
phase after the detailed conversion requirements have been completed and agreed. The
Business acceptance requirements will normally include the following:
Pls feel free to comment if you have any questions. Let me know if any additional detail required.
What's Related?
4 of 5 22-Jan-19, 10:09
Complete Oracle Retail Tutorials and Training Materials by Nageshwar ... https://oretail.blogspot.com/2014/08/oracle-retail-mom-data-migration-k...
5 of 5 22-Jan-19, 10:09