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.

Read more: What is the testing process like? When does the first CRP start?

eprentise software works within the E-Business Suite and the standard, out-of-the-box functionality. There is an optional customization metadata analysis to document database objects that are not part of the E-Business Suite. eprentise does not change any source code, packages, or SQL code in an E-Business Suite environment. That means that any interfaces to third party systems, enhancements, non-standard reports, and bolt-on software are outside the scope of what eprentise will address in your transformation project. You will need to determine if these are impacted by the eprentise transformation of the EBS, and adjust or fit them to the new EBS environment.

Read more: What kind of consolidation decisions and work will the software do automatically or will the eprentise team do for us? What will we have to do?