The testing process is similar to the testing that you would do for any other change to your E-Business Suite. In most cases, you start with a development or configuration phase, possibly with a data conversion phase, followed by the actual E-Business Suite testing. The EBS testing is known as the System Integration Test, Conference Room Pilot, or User Acceptance Test. With eprentise you first configure then run the transformation, which is like a data conversion. You will test the results of the transformation. Then you run tests in EBS against the transformed EBS database. Since eprentise is rules-based software, you quickly can change the transformation if you don’t like the results.

The following diagram is an overview of testing an eprentise transformation and the subsequent E-Business Suite testing.

(click image for a larger view)

This is an overview of the process steps. 

1. Freeze and save the initial state E-Business Suite test instance.
2. Create a baseline set of E-Business Suite trial balance and other reports you will use later to verify the results of the transformation. Usually we recommend the trial balance reports from each module, and then other reports that you would use when you close a period. Depending on what you want to change, you might generate some other more detailed listing reports within each module.
3. Run eprentise Metadata Analysis.
4. Create a test clone of the initial state test instance.
5. Run eprentise and use the different eprentise rule templates to define the transformation.
6. Run eprentise and execute the transformation rules against the test clone.
7. Run the same set of EBS trial balance and other reports against the transformed EBS database. Metadata Analysis also provides comparison reports on the initial state test instance and the transformed E-Business Suite environment.
8. Compare and reconcile the initial state baseline reports and the transformation reports.
9. This completes the transformation testing phase, and you will either cycle through adjustments to the transformation and retesting, or initiate the EBS functionality testing.
10. Start a Conference Room Pilot to give the users an opportunity to complete process cycles (order-to cash, procure-to-pay, etc.) with the changed data. If the results are not what you expect, then you will create a new rule and start the testing process again.
11. After the eprentise Transformation and EBS CRP testing are complete, test the interfaces and third-party systems with the changed database as part of your integration testing process.
12. Finally, when everything has been updated, then the users will conduct the UAT with the fully integrated changed data.