Technical Setup

In addition to the above configuration and transaction there is specific technical setup that must be done in the SAP development system and transported through the SAP environments together with the other PreBilt transports.

BAdi activation

The below BAdi implementations need to be created in SE19 by a technical resource as part of the project setup, so that the dynamic bins are created when material documents are created in the standard SAP code. If the BAdi implementations do not allow the /TCTM/ BAdi supplied classes then a z version will need to be created by copying the TCTM classes and these assigned to the BAdi implementations created.

• BAdi MB_GOODSMOVEMENT using BAdi definition MB_DOCUMENT_BADI and the TCT supplied class /TCTM/IMB_BADI_MB.

• BAdi LE_SHP_DELIVERY_PROC using BAdi definition LE_SHP_DELIVERY_PROC and the TCT supplied class /TCTM/IMB_BADI_VL.

For BAdi MB_GOODSMOVEMENT, the code is inside the following method:

• IF_EX_MB_DOCUMENT_BADI~MB_DOCUMENT_BEFORE_UPDATE

For BAdi LE_SHP_DELIVERY_PROC, the code is inside the following methods:

• IF_EX_LE_SHP_DELIVERY_PROC~DELIVERY_FINAL_CHECK

• IF_EX_LE_SHP_DELIVERY_PROC~SAVE_AND_PUBLISH_DOCUMENT

• IF_EX_LE_SHP_DELIVERY_PROC~SAVE_DOCUMENT_PREPARE

Enhancement point activation

Another enhancement implementation is required for IMMB when using the Physical Inventory app with IM Multi Bin storage locations.

• ENHANCEMENT-POINT MM07IFB0_02 SPOTS ES_SAPMM07I.

This needs to be updated with the following code in order to release the inventory lock on IMMB quants and update bin quantity when posting or deleting an inventory document:

* Handle IMB updates when deleting, posting etc.
  /tctm/srv_imb_utils=>pi_post( EXPORTING is_tm07i = tm07i
                                          is_ikpf  = xikpf
                                          it_iseg  = xiseg[]
                                          is_zikpf = zikpf
                                          it_ziseg = ziseg[] ).