Chram 4 system Landscape

[Former Member]

Dear Friends,

One of our syetem has 4 system landscape and we have activated the same for chram process

Dev -> QA -> Pre-PRD -> PRD

Dev has the system Role as Source system

QA and Pre-PRD has the system role Target system

PRD has the system rolePRoduction system

We have observed a scenario where

I import the request to QA from dev and then I put back the UC to Indevelopment status.

When I try to import the request once again to QA system without modifying the old request or creating a new request,

Import is happening to Pre-Prd system and not to QA system.

But incase of resetting the status back to Indevelopment after moving to QA. I create a new transport request and try to move to QA and the objects are moved to QA and not to pre-prd system.

Can any one suggest how to avoid import to pre-prd directly.

Regards

Lohith

[Former Member]

When I try to import the request once again to QA system without modifying the old request or creating a new request,
Import is happening to Pre-Prd system and not to QA system.

If you detected that your change "A1" was not successfull in QA you have to set the change back to in development. This will get you back to edit your change "A" in Development. Once you have made further changes to your change "A" and want to test it in QA another copy - "A2" - will be imported to QA. This will last until your change was successfull in QA.

This process ensures that only your successfull "A`n" change will be migrated to production and all other copies "A`n-1" wont be moved to production.

Nesimi

[Former Member]

Hi Nesemi,

Thanks for your reply.

As you have said "This process ensures that only your successfull "A`n" change will be migrated to production and all other copies "A`n-1" wont be moved to production".

Here, before testing if the User by mistake, has set the status to Indevelopment, and when he tries to do a reimport to QA the request is getting imported to Pre-Prd. So in this case before succesfull testing, the objects are moved to Pre-PRD system.

Our main concern is that the PRD and Pre-PRD systems should be coinsistant. Is there any configurations availble where I can unlock the task list of the second target system( Pre-PRD) only on successfull testing in QA.

Regards

Lohith

[Former Member]

Hi Lohith

are you very sure that you have set your change A1 back to in development and this really triggered the import to pre-prod?

do you have a job scheduled to import periodically all successfull QA transport into preprod? Or you automatically let them import? This you can check via STMS

have you defined a new system role called "PREPROD" in SMSY and declared that as a production system?

regards

nesimi

[Former Member]

Hi Nesimi

Setting the status to Indevelopment does not trigger the import. After setting the status to indevelopment when I try to execute the action "Pass correction to test" this will import my request to Pre-PRD but does not to QA system.

No, we do not have any job scheduled for import to Pre-Prd system automatically. We have incorporated a status in UC "Pass correction to Pre-Prd" which will import the request to pre-prd system. This action is visible in he action list only when UC is successfully tested in QA system.

We have defined the new system as PREPROD and have declared it as a Target system and not Production system.

Regards

Lohith