Ansicht
Dokumentation

SIMG_CFMENUOPP1BADI - Business Add-Ins for Requirements Planning

SIMG_CFMENUOPP1BADI - Business Add-Ins for Requirements Planning

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.
SAP E-Book

In requirements planning, Business Add-Ins (BAdIs) are available for the following functions:

BAdIs Used in Classic MRP

Note

This activity is only relevant if you plan some of your materials using classic MRP. If you plan all your materials using MRP live, see below.

  • General requirements planning

  • Requirements planning planning evaluation (PP-MRP-BD)

  • Requirements planning procurement proposal (PP-MRP-PP)

  • Requirements planning planning execution (PP-MRP-PR)

  • Planning File Entries (MRP Records) (PP-MRP-PR)

  • Long-term planning / simulation (PP-MP-LTP)

  • Order report (PP-MRP-PE)

BAdIs Used in MRP Live

  • Enhancement Spot ES_PPH_MRP_BADI

Method READ_MAT_MRP_CTRL_PARAMS: This method is called after MRP Live on Hana has computed the MRP relevant master data for all the materials provided to some MRP Live step. The set of materials of materials for this step is provided in parameter IT_SEL. You can change the MRP parameters for the materials by changing the table CT_CTRL. You can also remove entries for CT_CTRL so that a particular material/plant/MRP area combination is not planned at all.

  • PPH_MRP_NETTING_BADI

Method NET_REQ_CALC: This method is called before the actual netting takes place. You can use it to implement your own way of creating receipts for the provided requirements. For a correct integration into the SAP standard coding you must: Provide the result of your calculation in parameters CT_RECEIPTS and CT_NET_REQS; Remove the materials for which you have done the netting from parameter CT_MAT_CTRL. This way the standard netting routine will no longer consider the materials already worked on.

  • PPH_MRP_LOTSIZING_BADI

Method LOT_SIZE_CALC: This method is called before the actual lot sizing takes place. You can use it to implement your own way of creating lots for the provided receipts. For a correct integration into the SAP standard coding you must: Provide the result of your lot sizing in parameter CT_RESULT; Remove the materials for which you have done the lot sizing from parameter CT_MATB_CTRL. This way the standard lot sizing will no longer consider the materials already worked on.

  • PPH_MRP_POSTPROCESSING_BADI

Method CHANGE_PURREQ: This method is called during post processing of the purchase requisitions created by MRP Live on Hana. It can be used to fill custom fields present in table EBAN or EBKN, or even to change any field of these tables. The method is called for each purchase requisition after the SAP code has computed all fields of EBAN and EBKN.

  • PPH_MRP_REUSE_BADI

Method REUSE_CHECK: This method is called after MRP Live on Hana has done a reuse check (for planning mode 1 only). The only use case of the method is to clear the flag CT_THE_INDEX_NEW-REUSE and CT_THE_INDEX_OLD-REUSE in those cases where reuse would be possible but shall not be done for some special reason.

  • PPH_MRP_RUN_BADI

Method MDPS_ADJUST: This method is called after MRP Live on Hana has computed the list of MRP elements to be considered during planning for the materials in IT_CTRL. You can change the MRP elements in table CT_MDPS. The logical key of this table is field THE_INDEX. It is extremely important that this field is unique! So, in case you want to add rows, make sure that in the end THE_INDEX is still unique.

Method PURREQ_BEFORE_UPDATE_ADJUST: This method is called when MRP Live on Hana has computed the list of purchase requisitions to be created (eventually including provided components for subcontracting) and deleted. You can change the entries in the result tables. The logical key of the tables is field THE_INDEX. It is extremely important that this field is unique! So, in case you want to add rows, make sure that in the end THE_INDEX is still unique.

Method PLANORD_BEFORE_UPDATE_ADJUST: This method is called when MRP Live on Hana has computed the list of planned orders to be created and updated. You can change the entries in the result tables. The logical key of the tables is field THE_INDEX. It is extremely important that this field is unique! So, in case you want to add rows, make sure that in the end THE_INDEX is still unique.

Method PLAN_FILE_ADJUST: This method can be used to change plan file entries before MRP Live on Hana writes them to the database. In parameter CT_PLAN_FILE entries can be added if a material is to be planned a second time for example. In this case add a line with the respective key and set GSAEN = ‘X’ and KZKUP = ‘Y’.

  • PPH_MRP_SOURCING_BADI

Method SOS_DET_ADJUST: This method can be used to change the sourcing result. For example, you can switch from external procurement to inhouse production or vice versa by changing the contents of the tables CT_NEWLOT_SOS_F (external) and CT_NEWLOT_SOS_E (inhouse) respectively. The logical key of the tables is field THE_INDEX. It is extremely important that this field is unique! So, in case you want to add rows, make sure that in the end THE_INDEX is still unique for each table.

  • PPH_MRP_UPDATE_BADI

Method PURREQ_UPDATE: This method contains all purchase requisitions created or updated or deleted. The ones to be deleted are still in the database table, the new or updates ones are already changed on the database. This method can be used to change additional custom tables for purchase requisitions.

  • Enhancement Spot ES_PPH_MRP_DISPATCHER_BADI

BAdIs Used in both Classic MRP and MRP Live,,






rdisp/max_wprun_time - Maximum work process run time   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Length: 13258 Date: 20240523 Time: 211818     sap01-206 ( 174 ms )