Ansicht
Dokumentation

"Rescheduling: Bottom-Up" Heuristic (Enhanced) ( RELNAPO_401_PPS_BOTTOMUP )

CPI1466 during Backup   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Short text

"Rescheduling: Bottom-Up" Heuristic (Enhanced)

Use

Using a heuristic based on the algorithm /SAPAPO/HEU_MIN_PEG_GIV_SUPPLY, for example, using the standard heuristic SAP_PP_009, you can reschedule dependent and stock transfer requirements of PP/DS orders so that, as far as possible, they can be covered in time by the existing SNP and PP/DS receipts. The following enhancements have been made for SAP APO 4.0:

• Sort sequence for requirements

To determine which dependent and stock transfer requirements can be covered, the heuristic assigns SNP or PP/DS receipts to the requirements of SNP and PP/DS orders. Until now, the heuristic first processed the requirements with a fixed pegging relationship to a receipt in the sequence of the requirements dates/times. Then the heuristic processed the requirements without fixed pegging relationships in a time sequence. As of SAP APO 4.0, you can use the sort sequence in the heuristic settings to define the sequence in which the heuristic processes requirements without fixed pegging relationships. Apart from sorting the requirements according to requirement date/time and priority, you can sort them according to whether the affected PP/DS orders contain deallocated operations or have the status output firmed.

• Assignment strategy

Until now, the heuristic assigned the receipts to a requirement according to the availability date/time; that is, the earliest receipt first, and if this was not sufficient, then the next receipt, and so on. As of SAP APO 4.0, you can define an assignment strategy in the heuristic settings. In addition to the FIFO strategy implemented up until now, another strategy is available, which the heuristic can use to assign the requirement receipts that are as timely as possible. The heuristic starts from the requirements date/time and searches into the past for receipts. If it does not find sufficient receipts here, it starts from the requirements date/time and searches into the future for receipts. If the requirement can be covered, the heuristic tries to shift the requirement to the latest availability date/time of the receipts that it assigned to the requirement, just as in the FIFO strategy.

• Processing horizon

Until now, the heuristic only took account of requirements and receipts in the planning period when assigning receipts to requirements and when rescheduling requirements. As of SAP APO 4.0, you can use a processing horizon to further restrict the relevant period; the heuristic only considers requirements and receipts that are in the overlap period between the planning period and the processing horizon. The end of the processing horizon is defined by the PP/DS planning time fence, the planned delivery time or a time interval that you have entered in the heuristic settings. While uncovered requirements in the planning period retained their requirements date/time previously, as of SAP APO 4.0 the heuristic tries to shift uncovered requirements to the end of the processing horizon. In an ideal situation, shortages no longer arise in the processing horizon as of SAP APO 4.0.

• Enhancement of the evaluation

The evaluation that is available for the heuristic run in interactive planning has been structured more clearly. In addition, the evaluation shows

• Which receipts the heuristic has assigned to a requirement

• The date on which the heuristic has actually rescheduled a requirement

(Rescheduling to the desired date/time - the latest availability date/time of the receipts assigned to the requirement - is not always possible.)

• Strategy settings

In the heuristic settings, there is a new tab page Strategy. On this tab page, you can define the strategy settings that the heuristic should use for rescheduling orders. After the upgrade to SAP APO 4.0, you can either use the strategy settings from the heuristic, or work with the strategy profile as before. For more information on strategies in SAP APO 4.0, see the release information Strategy Settings for PP Heuristics.

• BAdIs

You can use the new BAdI /SAPAPO/RRP_BOTTOMUP as of SAP APO 4.0 to modify the requirement and receipt elements to be taken into account (FILTER_IO_NODES method), their sort sequence (SORT_IO_NODES method), and the processing of orders with uncovered requirements (CHECK_IO_RESCHEDULE method). The EVALUATION method is available for modifying the evaluation for the heuristic run. You can use this method to prepare (for example, filter) the results of the heuristic run, or to further process them, (for example, trigger follow-up actions, depending on the results).

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

In the standard system, a heuristic based on the algorithm /SAPAPO/HEU_MIN_PEG_GIV_SUPPLY works as in SAP APO 3.1. In other words, requirements are sorted according to requirements date/time, the FIFO strategy is used for receipts as the assignment strategy, and there is no processing horizon. This also applies to the SAP standard heuristic SAP_PP_009. If you want to implement the new heuristic functions, create an individual heuristic with the desired heuristic settings in Customizing for Production Planning and Detailed Scheduling under Maintain Heuristics.

Further Information

System documentation for the heuristic SAP_PP_009

Fill RESBD Structure from EBP Component Structure   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 6382 Date: 20240426 Time: 163725     sap01-206 ( 158 ms )