What is the testing process like? When does the first CRP start?
The following diagram is an overview of testing an eprentise transformation and the subsequent E-Business Suite testing.
This is an overview of the process steps.
- Freeze and save the initial state E-Business Suite test instance.
- 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.
- Run eprentise Metadata Analysis.
- Create a test clone of the initial state test instance.
- Run eprentise and use the different eprentise rule templates to define the transformation.
- Run eprentise and execute the transformation rules against the test clone.
- 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.
- Compare and reconcile the initial state baseline reports and the transformation reports.
- This completes the transformation testing phase, and you will either cycle through adjustments to the transformation and retesting, or initiate the EBS functionality testing.
- 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.
- 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.
- Finally, when everything has been updated, then the users will conduct the UAT with the fully integrated changed data.
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?
The business users need to make decisions about what the target environment looks like, criteria about what makes a duplicate, which standards eprentise should enforce, and any “rules” like revenue recognition rules, allocation formulas, security rules, or workflows.
Once the eprentise software knows what the target is, then it generates the code to change the source to the target. It does not know the business or best practices for an industry.
The customer needs to know how to set up and implement E-Business Suite to get the desired result. That includes knowledge of how organization units or sets of books work, what is a roll-up group, how to define a flexfield, how to allocate costs, how to move an asset to a new category, or how to drill down to sub ledger detail.
How do eprentise and FlexField software affect change management processes and systems for regulatory compliance (Sarbanes-Oxley)?
How will I know if the eprentise transformation works?
Are the support services provided by eprentise subject to Service Organization Controls reporting standards level 2 (SOC2)?
eprentise is a provider of software and the services and support solely involved in using eprentise software. As such, eprentise is not considered a service organization and does not fall under the scope of auditor reporting for service organizations (SOC 1, 2 or 3). All services and support are provisioned through either a VPN connection or through a remote web session such as WebEx. At no point does eprentise take custodianship of or offsite possession of client data or responsibility for internal controls over financial reporting. At all points during the project, specific to the use of eprentise software, the client remains responsible for the testing and validation of the resulting database changes affected by eprentise software as they relate to internal controls over financial reporting.