release strategy in MB21

[Former Member]

Hi all

Please help me to create a release strategy for MB21.

My requirement is after creating a reservation from MB21 there will be a release strategy so the higher authority can release that reservation before the MIGO.

currently, after creating reservation  from MB21 The MIGO can be done done. I want to release that reservation then MIGO.

Please help to solve this problem.

Moderator message : Not directly related to ABAP development, requirements dumping not allowed, discussion locked.

Message was edited by: Vinod Kumar

[Former Member]

Hi all

Please help me to create a release strategy for MB21.

My requirement is after creating a reservation from MB21 there will be a release strategy so the higher authority can release that reservation before the MIGO.

currently, after creating reservation  from MB21 The MIGO can be done done. I want to release that reservation then MIGO.

Please help to solve this problem.

Moderator message : Not directly related to ABAP development, requirements dumping not allowed, discussion locked.

Message was edited by: Vinod Kumar

[joao_sousa2]

The way I've done this in the past is:

• Select a field in the reservation;
• Use a field exit to make it disabled for the common user;
• Give the person responsible for the approval access to this field;
• Create an approval report that changes this field to "released" value;
• Implement a BADI for MIGO (and MIGO related) that checks this value;

I don't remember what field I used but this was the concept. As an alternative you can create a custom Approval Z table, and implement a validation in MIGO that makes sure there is an entry in this approval table.

[Former Member]

Hi Joao

Thanks for your reply.
kindly tell me the particular BADI for MIGO. Where I can check the condition while entering the reservation number.