First, data is extracted in pipe delimited test files. Then, custom programs read these files and dump this raw data in custom JDE tables. These custom tables work as a staging place for the data, which also gives way to check and verify results. Once all data is loaded to the staging area, custom JDE Universal Batch Engines (UBEs), massage the data based on the rules defined, and load the records into the respective JDE-Z tables.
Business analyst have the opportunity to verify how the records were created in the new system before finalizing. Here, programs use transformation rules for User Defined Codes (UDCs), as the JDE system use UDCs that are different from PeopleSoft. In this process, a custom application was created where the module team could configure rules independently. This gave flexibly to set up new transformation rules, and modify existing rules as need. This application is a central place for all transformation rules across different conversion programs.
This strategy was used for the following reasons: