Oracle Retail: Data Migration - Req Def and Design Phase

This is continuation of my blog Oracle Retail: Data Migration Strategy for MOM dated October 3, 2008, I'm going to discuss the first phase of the Data Migration for the MOM i.e. Requirement Definition and Design phase. 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:

1. Determine Data Conversion Scope based on the designed functionality of RMS
2. Determine the All Configuration Options
3. Determine Conversion Environment Configuration Strategy
4. Specify Target Data Requirement and the mode of conversion for each table’s field in the functional area.
5. Identify the data source (existing source systems) that will be used to populate the Target applications.
6. If data is not available in source systems, it should be created manually in flat files or in spreadsheets.
7. Identify and compare the Data Volume and Complexity of the data structures (source and target systems).
8. Using the target data requirements which are already identified, map the fields to the current source system.
9. Determine if any transformation required between source and target data systems.
10. Develop a data conversion functional design document for each functional area. Document should specify overall conversion process (automated/manual) for each functional area.
11. 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.
12. Identify all the pre and post dependency of each functional area conversion.
13. Document all default values and any data validation requirements.
14. Understand data model of each functional area in source system.
15. Document the data cleansing requirements available and identified at this stage.
16. Create validation approach for conversion results done my Merchandise toolkit and manual conversion.
17. Plan all the validations which are not supported by toolkit with proper business acceptance.
18. Plan all the static/transaction tables which need to be reloaded each time in every environment.
19. Get the Sign Off on each functional design document.

Feel free to share your views if anything more required for this stage.

— Share It —

• Facebook
• Twitter
• Google+
• Linkedin
• Pin It

About Nagesh Mishra

Nagesh Mishra - A Passionate Oracle Retail Certified Professional with more than 17 years of overall experience in IT industry and more than 15 years of domain expertise in Oracle Retail Applications. Worked extensively in diversified fields of Product Implementation, Business Consulting, Pre-Sales, Application Software Development, Maintenance and Support and Re-Engineering Oracle Retail projects.