Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Conversion Approach
Data Migration should be treated as a separate small parallel project along with the complete implementation. Scope of this document is to discuss the high level approach for the end to end data conversion from the legacy system to Oracle Retail MOM suite. Oracle released Data Conversion Toolkit from RMS 12.0.3 for the automatic data conversion from the legacy system. Latest version of this tool is available in RMS 13.1.1 version. Though we have this Toolkit available, still we need to write lot of script using SQL Developer for the data migration as toolkit doesnt support migrating dynamic/transactional data. Data Conversion for Oracle Retail can be broadly categorized in 4 phases: a) Requirement Definition and Design Phase This is the most important and crucial phage. In this phase, the detailed Data Mappings (with legacy and current system) and the strategy will be required in order to begin the detailed design process and also to produce conversion detailed designs and document procedures (manual and automated data conversion) to source, clean, convert and validate the data to be converted from the legacy systems to RMS. Identifying the actual data requirements for the target applications along with all associated data mappings, assumptions, challenges, complete process flows, data volumes, any dependencies and data cleansing requirements are the main task in the Requirement Definition and Design phase. Data Cleansing is one of the key activities which require special focus in this phase. Following is the brief approach, should be followed:
1. Determine Data Conversion Scope based on the designed functionality of RMS 2. Determine the Configuration Options for all applications 3. Specify Target Data Requirement and the mode of conversion for each tables field in the functional area.
Conversion Areas
As mentioned above, the entire data conversion for Oracle Retail MOM Suite is divided in 6 main functional areas based on foundation and transaction data. Below are the table level details which need to be populated for each functional area. There are tables (Prerequisites Tables) which should be populated before using the conversion toolkit for any functional area
2. Merchandise Hierarchy
Prerequisite Tables Required DIVISION GROUPS COMPHEAD Tables Loaded Using Oracle Conversion Toolkit DEPS CLASS SUBCLASS STOCK_LEDGER_INSERTS VAT_DEPS UDA_ITEM_DEFAULTS RPM_DEPT_AGGREGATION Post-Loaded Tables Required RPM_MERCH_RETAIL_DEF HIERARCHY_PERMISSION (Retail Security Manager [RSM] table) All department UDA defaults must be set up manually where UDA_ITEM_DEFAULTS.REQUIRED _IND = Y
3. Organizational Hierarchy
Prerequisite Tables Required CHAIN AREA Tables Loaded Using Oracle Conversion Toolkit ADDR WH WH_ADD STOCK_LEDGER_INSERTS TRANSIT_TIMES COST_ZONE COST_ZONE_GROUP_LOC REGION DISTRICT STORE_ADD STORE_DEPT_AREA Post-Loaded Tables Required DEPT_CHRG_HEAD DEPT_CHRG_DETAIL STORE_HIERARCHY COST_ZONE_GROUP (zone level pricing) Location level COST_ZONE_GROUP should have been created by the seed data installation. COST_ZONE COST_ZONE_GROUP_LOC RPM_ZONE_GROUP_TYPE RPM_ZONE_GROUP RPM_ZONE RPM_ZONE_LOCATION Optional (after running Batch) STORE_ATTRIBUTES WH_ATTRIBUTES STORE_SHIP_DATE
4. Suppliers
Prerequisite Tables Required PARTNER (required types: AG=agents, BK=advising or issuing banks, FA=factory) OUTLOC (required types: DP=discharge ports, LP=lading ports) Tables Loaded Using Oracle Conversion Toolkit SUPS ADDR (for supplier addresses) SUP_IMPORT_ATTR Post-Loaded Tables Required SUP_BRACKET_COST Optional SUP_ATTRIBUTES SUP_INV_MGMT SUP_REPL_DAY SUPP_PREISSUE SUPS_MIN_FAIL
6. Transactional Data If conversion of transaction data is in scope, they we should make sure that below tables in each functional category must be populated:
Purchase Orders PO_TYPE ORDHEAD ORDSKU ORDLOC Inventory ITEM_LOC_SOH REPL_DAY REPL_ITEM_LOC ITEM_LOC_SOH Transfers TSFHEAD VAT_HISTORY Sales TRAN_DATA_A DAILY_SALES_DISCOUNT VAT_HISTORY
Conversion Process
Though there are multiple tools available for the data conversion including oracle retail data conversion toolkit. Its always better to prefer the toolkit for the main set of tables and SQL Loader of other tables required for pre and post loading and also for transaction tables. Ensure that Merchandise applications must be installed and all seed data loaded before conversion. Bellow is standard process for the data conversion: Capture the data in Excel Templates. Convert the template into CSV File. Convert CSV file into *.dat file extension. Convert *.dat file into Pipe (|) delimited flat *.dat file. Follow the Standard naming conventions e.g. Supplier flat file name: dc_sups.dat. 6. File should be encoded in UTF-8. Character fields should not contain carriage returns which indicate a new record. 7. Copy files (have a size greater than 0) in the data directory defined in the common configuration file from where it can be read from Conversion toolkit of SQL Loader. 8. Ensure that the script file has the proper permissions: rwxrwx-r-x 9. Ensure that conversion is done sequentially for each functional area. 10. Load Prerequisites tables first using SQL *Loader before converting to main tables for any functional area. 11. Ensure that post-loading tables populated before moving to next functional area. 12. Use Oracle conversion toolkit to convert all main tables of foundation data (i.e. first 5 functional areas defined above) 13. Delete the status (*.status), discard (*.dsc), and bad (*.bad) files before running conversion toolkit 14. Include the directory where the conversion scripts will be executed in the environment path variable (PATH), 15. Follow below process to run the Conversion Toolkit: a) Run the master script using the following syntax (where > represents the UNIX or Linux command line prompt): a. dc_load_main.ksh q <sequence-file-name> b) To run individual segment wrapper scripts, the q <sequence-file-name> portion of the command line is not required. For example: a. dc_load_core.ksh 16. Validate converted data and do hot-fix if required. 1. 2. 3. 4. 5.
References:
1. 2. 3. 4. 5. Oracle Retail Merchandising Data Conversion Planning Guide Oracle Retail Merchandising Data Conversion Operations Guide Oracle Retail Documentation Oracle Metalink ERP Data Conversion
Copyright 2010 by Mahindra Satyam Computer Services. All Rights Reserved. Do not duplicate or distribute. Use and distribution limited solely to authorized personnel. Reproduction of this publication in any form without prior written permission is forbidden