Skip to Content
avatar image
Former Member

Segregation of ERP environments

The organisation I work for is currently evaluating an ERP solution and one of the products is SAP. As no one on the team has much experience with SAP infrastructure design I figured I'd post a question here for some advice.

They are a bit paranoid about having any sort of testing below UAT carried out on their production network. Therefore the request is to use a separate AD domain with one-way trust from the production domain to the test domain. This is so the ERP infrastructure, including user management and authentication, can be developed and tested in isolation. This separate domain will contain test instances of the other major products that the ERP will be integrated with.

So the question for the SAP gurus is, is this advisable? Can you have your dev/test environments in one logical domain and your uat/train/production environments in another but still be able to use standard change management tools for moving changes through the environments etc or would you effectively have to run two separate instances of the ERP and if so do SAP provide tools that can migrate changes between these environments?

I hope the question makes sense. Thanks.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Jan 28, 2010 at 10:27 PM

    For change Management to work all SAP system should communicate with each other and should have common transport directory.

    The communicaton happens using hostname and system no.

    There must be a permanent network connection between the systems and transport directory shared on all environments

    You should not have problems with above.

    Add comment
    10|10000 characters needed characters exceeded