Migrating data to legacy system as functional consultant |
 |
EXPERT RESPONSE FROM: Russell Arno
|
|
|
|
| > |
QUESTION POSED ON: 20 July 2006
What are the steps to be followed when migrating data from a legacy system as a functional consultant? What are the important interface tables that should be kept in mind?
|
|
| > |
EXPERT RESPONSE
As a functional consultant, leave the interface tables to the technical people. Your conversion concerns should always include (but are not limited to):
- Data cleanup
- Clean it up in the legacy system? Clean it up in Oracle? (Just be consistent!!!)
- Numbering
- Ex: Invoice numbers must be unique. Do they want Oracle to generate this, do they have their own identifier or do they require a custom solution?
- Legacy information
- Ex: The unique identifier from the legacy system may not be needed in Oracle, but it is nice to have when validating a conversion. You can store it and other legacy information in Descriptive Flexfields. If the data does not need to be seen in the application, do not enable the Flexfield so the data will remain hidden.
- Load validation
- First, know your standard Oracle reports for the module: what is on them, how they group the data and what the parameters are. Find out if there are reports in the Legacy system you can have run to compare with your Oracle reports. If the numbers on both reports match, then the load is a success.
- If you cannot use reports, then have the technical people extract the data from Oracle and compare it to the legacy data files.
- Setup
- Profile options
- Any default accounting
- Multi-Org, currencies, conversion rates
- Future needs
- Reporting
- Growth (number of transactions, purging)
- Is this a one-time conversion or will it become an ongoing interface?
Hope this helps.
|
|
|
|
|
|
|
|
Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and
answer pairs from more than 250 TechTarget industry experts.
|
|
|
|
|
|
|
|
|
|
|
|
