Urgent Change - Charm Customizing Issues

[Pradeepgali]

Hi Everyone,

We are trying to customize the urgent charm processes as follows (ZMHF)

1. Select Action ‘Pass Correction To Test’ from the Action button dropdown & Hit Save

2. A batch job runs every 5 minutes and moves transport of copies of the Transports from Dev to QA

3. If Testing is successful, the status will be changed to ‘Successfully Tested

4. The Change Manager will select ‘Release for Production’; the status will change to ‘Authorized for Import’ and notify the IT Operator (Basis Team) to move the Transport. This step releases the Transport, moves the Transport to QA and to the Prod buffer.

But unfortunately this is not working for us. When we mark "Successfully Tested" It is showing error messages stating that "Not all transport requests are yet released" even though the tasks are released.

Kindly let us know how we can correct this.  Please find the attached error message as well as our current settings.

Thanks

GVP

[Pradeepgali · Accepted solution]

Hi Everyone,

We went with the default but still we are able to implement Transport of Copies feature  for Urgent Change ZMHF

E0001 0 CREATE_HF

E0001 20 SET_BO_LINKS

E0002 30 SAVE_PARTNER

E0002 40 SET_BO_LINKS

E0004 10 SAVE_PARTNER

E0004 20 COPY_ALL

E0005 10 RELEASE_ALL

E0005 20 IMPORT_TEST

E0005 30 SAVE_PARTNER

E0006 10 IMPORT_PROD

E0006 20 SET_PREDOC

E0008 5 SET_PREDOC

E0008 10 CLOSE_TSK_LS

E0010 10 CLEAR_EMPTY

E0010 20 SET_PREDOC

E0010 30 CLOSE_TSK_LS

Thanks

Pradeep

[Pradeepgali]

Hi Vivek,

I agree. In our case we did implement Transport of Copied for both Normal and Urgent and it is working fine.

Thanks

Pradeep

[Former Member]

Hi Pradeep,

may I ask you how?

Best regards

Rene

[Vivek_Hegde]

Hi Pradeep,

There is no Transport of Copies feature available for Urgent Change ZMHF.

Regards,

Vivek

[Pradeepgali]

Hi Everyone,

The job SM:TMWFLOW_CMSSYSCOL is working fine.  The below sequence works fine with UC but the problem is when the change manager marks it E0005(Successfully Tested) it is releasing the parent transport(RELEASE_ALL)

E0001      0      CREATE_HF

E0001      20    SET_BO_LINKS 

E0002      30    SAVE_PARTNER

E0002      40    SET_BO_LINKS

E0004      10    SAVE_PARTNER

E0004      30    COPY_ALL

E0005      10    RELEASE_ALL

E0005      20    CLEAR_EMPTY

E0005      20    IMPORT_TEST

E0005      30    SAVE_PARTNER

E0006      10    IMPORT_PROD

E0006      20    SET_PREDOC

E0008      5      SET_PREDOC

E0008      10    CLOSE_TSK_LS

E0010      10    CLEAR_EMPTY

E0010      20    SET_PREDOC

E0010      30    CLOSE_TSK_LS

We want to change this processes.

Only when the change manager marks it E0009(Authorized for Production) then only the parent transport should release. Hence we made the below change after which we are getting the errors as per the attachment.

E0001      0        CREATE_HF
E0001      20      SET_BO_LINKS 
E0002      30      SAVE_PARTNER
E0002      40      SET_BO_LINKS
E0004      10      SAVE_PARTNER
E0004      30      COPY_ALL

E0005      20      CLEAR_EMPTY
E0005      20      IMPORT_TEST
E0005      30      SAVE_PARTNER
E0006      10      IMPORT_PROD
E0006      20      SET_PREDOC
E0008      5       SET_PREDOC
E0008      10     CLOSE_TSK_LS
E0009      10     RELEASE_ALL
E0010      10     CLEAR_EMPTY
E0010      20     SET_PREDOC
E0010      30     CLOSE_TSK_LS

My question is how can we correct the processes...

Regards

[former_member202726]

I'm going to preface this by saying I have no idea whether or not you can get this to work.

I would suggest adding another CLEAR_ENTRY line.

    E0009      20     CLEAR_ENTRY

The check for transports being imported is under "Change Request Management Framework" "Make Settings for Change Transaction Types" "Assign Conditions."  Have you moved the TR_REQUEST line there as well?  (Actually, I would advise first changing it to a Warning)

[former_member202726]

Sorry, when I wrote CLEAR_ENTRY, I meant CLEAR_EMPTY.

[Former Member]

hi Pradip,

1820635: How to analyze errors when changing the status of a ChaRM correction

[Pradeepgali]

Thanks for sharing the note unfortunately it didn't help us .

As per SAP standard I see that Under status E0004 or E0005  we need to have the action RELEASE_ALL or RELEASE_REQU. Can't this be changed in the way I suggested,

Regards

[former_member202726]

More information about what system logs, application logs, security traces, and ABAP dumps tell you might be helpful, both in the solution manager system and the managed system.

I'm currently not even sure if the problem is that the transport isn't being released, or that it is released but ChaRM doesn't know it.

[Former Member]

Hi,

I have seen this issue when the transport couldn't reach to production buffer.

Can you please check if the job  SM:TMWFLOW_CMSSYSCOL in Solman system is running fine.

Please check log for this job.

Regards,

Anjali.