3726779 - badi mmim_item_provide_data not invoked in 'manage material document for reservation' app

• The issue involves the implementation of BADI with Extension Point ID MMIM_ITEM_PROVIDE_DATA for updating custom Material document Item fields.
• The BADI is triggered during Goods Issue from MIGO but does not get invoked when Goods Issue is performed from the 'Manage Material Document for Reservation' (F7279) App.

SAP S/4HANA Cloud Public Edition

1. Implement BADI with Extension Point ID MMIM_ITEM_PROVIDE_DATA.
2. Perform Goods Issue for a Material document from MIGO and observe that the BADI gets triggered.
3. Perform Goods Issue from 'Manage Material Document for Reservation' (F7279) App and observe that the BADI does not get invoked.

The BADI MMIM_ITEM_PROVIDE_DATA is designed to modify user entries specifically for the MIGO application. It is not intended to be invoked by the 'Manage Material Document for Reservation' (F7279) App.

1. Refer to the official documentation of the BADI MMIM_ITEM_PROVIDE_DATA for further clarification on its intended functionality.

2. As stated in the documentation, this BAdI is designed to modify user-entries. In the case of cancelling a material document in MIGO, the user does not have the option to enter or modify the values during the cancellation process. Consequently, the modified values from the BAdI will not be posted.

   This behavior is by design. Therefore, when the cancellation document is posted, the custom fields retain the same values that were originally stored in the initial material document.

Refer to: Official documentation for BADI MMIM_ITEM_PROVIDE_DATA

Refer to: Help documentation for 'Manage Material Document for Reservation' application

badi mmim_item_provide_data, manage material document for reservation, migo, goods issue, extension point, custom material document item fields, F7279 app, badi not invoked, public cloud, s/4hana , KBA , MM-IM-GF-2CL , Basic Functions (Public Cloud) , Problem