Status Dependent Import-(The Hidden Treasure of ChaRM) .
First time that I ear about this functionality was because Michael Vollmer advice it on this thread,
Description:
This functionality, allow you to control the import in the the SAP System/Clients at Change Document level,
Actually, when you do the import in QA, PRE and PRD environments using the task-list of the project (txcode: SCMA) , the system import all the Transports request that are inside of the queue, independently of the status of the change document. this risk if because SAP don’t check the status of the Change Documents during the import process. (Usually this happen because you are not following the Best Practices for Change Management recommend by SAP),
Example:
- You create an Urgent Correction, you make the development, the Test and everything is fine, the Urgent correction is in status “Successfully Tested” and is waiting the Change Manager to be “Authorised for Import”. Technically, the Transport is in the queue of PRD, if your project is in Test phase and now you make the go-live without moving the Urgent Correction, Solution Manager will import the transport request of the Urgent Correction in PRD, even if it’s not authorised to PRD.
- Actually after the “succesfullt Tested” status, the Normal corrections goes to PRD and you don’t have any option to stop this correction to be imported in PRE or PRD, now you can add a new status after the “Successfully Tested”,( something like “Authorised to go in Release”), then you add this new status to the Status-Dependent table, to allow the import in PRE only if is in status “Authorised for the Release”.
Customising:
You need to create 1 entry for each Project/System/Client/Role, you have the chance to use ” * ” for System/Client.
After select the entry in the import Strategy view, you can add the Change documents and the user status that you want to be allowed to be imported. 
You can check more information about this functionality on SAP Help Status-Dependent Import and the SAP Note 1708987
Wences Lacaze
Hi,
This is exactly the behaviour I want for Normal changes (ZMMJ, copy of SMMJ), but I cannot get it to work.
I have added e0016 into the import stategy table for my project with the production target system id and client and role 'P' for the correct transaction type and status profile.
Are there any additional steps required to prevent the production import job( /TMWFLOW/SCMA_TRORDER_IMPORT ) importing transports where the change doc status is only 'successfully tested' and NOT my new status ?
For example, what is required in the status attributes (change request mgmnt framework--> Define status attributes) ?
I hope someone has tried this and it works.....
Cheers,
Guy
Hey Wences,
first of all, nice document 😎 Keep it up!
However, I'm having issues seeing the screenshots. Could you please have a look at the content, so the screenshots are displayed again?
Best regards
Tobias
Sorry guys, Idon't know what happens with the pictures
I'm checking this with SAP SDN.
thxs