What are the ideal SAP system conditions for a successful root cause analysis?

At first access must be provided to the productive system.
The correct level of authorisation is important to ensure that transactional data cannot be created, changed or deleted. Therefore the required access should match the profiles of the “Order To Cash” and “Procure To Pay” SAP support team members. It should not be possible to debug the productive system.

The actual analysis should be performed in an environment that is a direct copy of the production system. It is important to ensure that the most recent customising and development changes are taken into account when executing the root cause analysis.
The required authorisation level matches the profiles of the most senior power user in the “Order To Cash” and “Procure To Pay” team member. All system customising and developments can be viewed. It must be possible to change variables when debugging the system as that would benefit the quality of the proposed resolution. Finally it would be beneficial to be able to collect data from the system by means of SAP/Query functionality.

Immediate on site functional and technical support is provided when necessary.
Although the assessment of the system will be done in isolation, some assistance might be required when specialised knowledge of the company specific developments is vital in order to find the root cause for compliance breaches. Access to support resources is expected within the hour upon request.

Tags: