on 02-24-2015 11:57 PM
Hello,
We have two ECC landscapes used for different purpose. We are planning to implement CHARM with a maintenance project for each ECC landscape for their regular set of transports.
ECC1 : DEV1-TST1-PRD1
ECC2: DEV2-TST2-PRD2
Our Customer develops a set of changes which are developed in ECC1 which should be imported into ECC2 landscape.Like
TR released from DEV1 - imported into DEV2
TR imported into TST1- imported into TST2
TR imported into PRD1 - imported into PRD2
I know that this is a strange behavior and always can be implemented manually.
Customer don't want to retrofit from DEV1 to DEV2 and go through the process again in ECC2 landscape and we dont require any approval to be imported into PRD2.
Is there any way this can be handled in CHARM or STMS?
Thanks
Murali.
Hi,
Although strange scenario and not recommended.
.
Try this.
From the solution manager create the domain link to both the landscapes, ECC1 and ECC2.
Now implement the charm in ECC1 which will follow the regular procedures however you need to forward the transport manully from ECC2 to ECC1, one good thing about this is you need not to copy the data and co files as OS level. then schedule the auto import jobs accordingly in ECC2.
However if you want to trigger the workflow parallel, it will require customization of transport routes etc which will make the scenario bit complicated.
Regards
Rishav
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.