Skip to Content
0
Jun 03, 2015 at 10:05 AM

Reassign of the ZMMJ document to another project (SAP Best Practice)

20 Views

Hi to all,

after you perform successful reassignment of your ZMMJ to another project this document will be solo without link to the source ZMCR (the information from where change document arrived - will be nice to have) . ZMCR can not be moved therefore you have to move just documents or transports to another project 😔

Very frequent problem is during staging/build phase customer initially overload the project, and later he wants to distribute the load with the the other existing projects.

With the possibility to reassign ZMMJ in the phase maintenance phase In Development w/o Release there are a lot of restriction

To my mind CHARM document reassignment is not best solution:

  • slightly better solution will be to do reassignment of the transport instead of complete document , then you will lose complete documentation related to the change !
  • if you change project for your Change Document then you will lose link to the ZMCR and you will have zombie ZMMJ
  • this reassignment make sense just for ZMTM Defect Correction anyway it does not belongs to ZMCR ) 😊

What will be the best approach - to deal with this solo reassigned ZMMJ in your new project environment.

Is there SAP best practice for this case?

All suggestions are more then welcomed.

Attachments

Capture222.PNG (53.5 kB)