Ansicht
Dokumentation

< ( RELNAPO_401_SNP_DISPOSTF )

< ( RELNAPO_401_SNP_DISPOSTF )

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

Short text

SNP Heuristic: Fixed Planning Sequence (Changed)

Use

Previously in Supply Network Planning (SNP), you could run a multilevel heuristic (a heuristic that also considers the bill of material (BOM) components of a product) for the entire network but not for individual locations. If you only wanted to plan a part of the supply chain model, you had to run the location heuristic many times for finished products and components, and adhere to a specific planning sequence for the location products to ensure that the demands were fulfilled correctly.

As of SAP APO 4.0, when running the heuristic in the background, you can choose whether you want the network or location heuristic to plan only the selected products or to also plan all of the associated BOM components. If you choose the new indicator Take into account found components in planning run, the location heuristic also considers the components assigned to the specified locations in the planning run. If this indicator is set for the network heuristic, the network heuristic has the same functionality as the former multilevel heuristic. The multilevel heuristic is now only available in interactive Supply Network Planning because the new indicator cannot be chosen here.

The planning sequence of the SNP heuristic is now governed by the low-level codes of location products. You can determine these before a heuristic run using the new Determine Low-Level Codes function (choose Supply Network Planning -> Planning -> Supply Network Planning in the Background -> Determine Low-Level Code). The low-level code specifies the BOM level and supply chain location at which a location product is located. The heuristic first plans the product with the highest low-level code 0 (for example, a finished product at a customer location), then the product with the second highest low-level code 1 (a finished product at a distribution center), and so on. This ensures that demand is fulfilled correctly even when a partial model has been chosen.

Effects on Existing Data

Effects on Data Transfer

Effects on System Administration

Effects on Customizing

Further Information

For more information, see SNP documentation: Low-Level Code Determination.






CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL Application Log Documentation  
This documentation is copyright by SAP AG.

Length: 2578 Date: 20240508 Time: 232048     sap01-206 ( 104 ms )