Ansicht
Dokumentation

RM_PERFORMANCE_DREQ - BAdI: Dependent Requirement Adjustment in the Confirmation

Fill RESBD Structure from EBP Component Structure   General Material Data  
This documentation is copyright by SAP AG.

Application component: PP-REM-ADE

Function group: BARM

With the Business Add-In (BAdI) RM_PERFORMANCE_DREQ, as long as certain prerequisites are fulfilled, you can improve the performance of the confirmation in Repetitive Manufacturing. The confirmation function is not changed as long as these circumstances are observed.

Only activate the Business Add-In if you

• use make-to-stock repetitive manufacturing

• use confirmations for reporting points

• reduce planned orders to confirmed production versions only

• can guarantee that

• confirmations are always executed without specifying a planned order and

• planned orders are not manually shifted or reexploded.

If the prerequisites are only fulfilled for certain assemblies, then you can activate the Business Add-In from the method ACTIVATE_FILTERING_PO, depending on the assembly.

Performance is improved by activating the Business Add-In, especially if

• the relevant BOMs contain many components ( >> 100 components)

• many planned orders lie within the planning horizon (>>10 planned orders)

• many confirmations with small partial quantities are executed.

Before you activate the Business Add-In, create an SQL trace of a representative confirmation. A significant improvement to performance can only be achieved if long reading periods to the database table RESB are observed in the SQL trace.

If the prerequisites are violated because, for example, a planned order was shifted manually, start report RMSERI35 for the corresponding assembly.The report re-establishes the time-reduction sequence:

• The present reduction of dependent requirements within the planning horizon is therefore discarded.

• With the reporting point quantities, all dependent requirements within the planning horizon are reduced again, starting with the dependent requirements of the oldest planned orders.

We recommend that you schedule report RMSERI35 regularly for activated BAdIs.

• The Business Add-In is not active in the standard system.

• The Business Add-In is not filter-dependent.

• The Business Add-In cannot be used more than once.

A car manufacturer produces five hundred vehicles of one particular type (material) per day. Daily lot sizes are used in planning, there is therefore one planned order of 500 pieces per day. The planning horizon equals 30 days, and 2000 components are used for each car. Each planned order creates 2000 dependent requirements. The 500 vehicles are confirmed individually.

At least 30 planned orders therefore exist within the planning horizon. Without using the Business Add-In, all components of the 30 planned orders are read for each confirmation: 500 confirmations per day, each with 30*2000 = 60.000 read accesses to the dependent requirements. This number still has to multiplied with the number of reporting points on the line.

Reading all dependent requirements within the planning horizon can be avoided if you can prevent confirmations on one particular planned order. If this can be excluded, the dependent requirements are then always reduced in the time sequence: The reduction starts with the dependent requirements of the oldest planned orders. To redetermine the withdrawal quantities of the dependent requirements, only the oldest dependent requirements are relevant.

In the example, only 1*2000 = 2000 read accesses to the dependent requirements per confirmation take place after activating the Business Add-In.

Documentation for BAdI method ACTIVATE_FILTERING_PO

Addresses (Business Address Services)   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 4739 Date: 20240606 Time: 191803     sap01-206 ( 84 ms )