We have GRC 10.1 SP23 installed. Development for ARA and EAM is done in Dev1 and the transport path is Dev1 > QA1 > Prod1. We currently have 8 internal SAP applications who have deployed ARA and EAM in this landscape. One of our customers, instead of activating Process Controls in Dev1, used an existing development client that we had planned to sunset (Dev2) and created the transport path from Dev2 > QA1 > Prod1. (There is no transport path from Dev2 > Dev1.) This customer is doing PC development in Dev2 and is currently the only one executing controls in Prod1.
Our concern is whether is it prudent to maintain 2 separate development clients; 1 for PC (Dev2) and 1 for ARA and EAM (Dev1). We are concerned about possible shared tables and configuration and whether transports we make from Dev1 > QA1 > Prod1 could be overwritten by transports from Dev2 > QA1 > Prod1 (or vice versa). At this time we only have 1 customer executing controls in Prod1, but foresee that the other 7 customers will deploy PC during the next year.
We would appreciate input on whether this dual development landscape could be problematic and if, so, why it would be problematic. We are trying to decide whether to mandate that this customer move from Dev2 to Dev1 for their PC development but need to more clearly understand the risks and benefits of the current environment as well as identify strategies for moving from Dev2 to Dev1.
If anyone has any suggestions, advice or could point us to documents to review, we would sincerely appreciate it.
Thank you!
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.