The heuristic is used as part of a repair-based planning process consisting of the heuristic, capacity leveling, and deployment. The heuristic run processes each planning location sequentially and determines sourcing requirements. The heuristic processing groups all demands for a given product at a location into one demand for the bucket. The heuristic run determines valid sources of supply and corresponding quantity based on pre-defined percentages for each source of supply (quota arrangements), or procurement priorities for transportation lanes and production process models (PPMs) or production data structures (PDS). The demands are then passed through the supply chain to calculate a plan. However, this plan is not necessarily feasible. The planner can then use capacity leveling to adjust the plan and formulate a feasible plan.
Both the key figures upon which the heuristic is based and the planning horizon are determined by the planning book. Macros can also be used to define how you want to calculate general key figures such as Total Demand and Stock on Hand, or product-specific key figures such as Safety Stock, Reorder Point, and Target Stock Level (for more information, see Advanced Macros and SNP Functions).
Process
...
1. You run the heuristic.
2. You run capacity leveling.
3. You run deployment.
4. You run the Transport Load Builder (TLB).
The Heuristic Run Process Flow
The heuristic plans all distribution demands for all locations within the distribution network before exploding the BOM and processing dependent demand at the production locations. The system explodes the BOM only when you choose a multilevel heuristic run.
Factors Considered in Processing
· Location products
· Low-level codes of the location products
· Valid production process models (PPMs)
· Valid transportation lanes
· Quota arrangements or procurement priorities
· Lead times
· Calendars
· Lot size rules
· Scrap
· Component availability
· SNP demand profile
· SNP supply profile
· Demand profile
Other Considerations
· The heuristic run considers all demand for a given product/location combination within one period as one demand.
· The heuristic planning sequence is governed by the low-level codes of the location products. For more information, see Low-Level Code Determination.
· The initial solution produced by the heuristic run may not be feasible because the system assumes that capacity is infinite. The planner must then adjust the plan by leveling resource capacity. For more information, see Capacity Leveling.
· The heuristic run results do not include pegging orders back to the original individual requirement because requirements are bucketed.
See also:
Running the Heuristic in the Background
Deployment:
After production is complete, deployment determines which demands can be fulfilled by the existing supply. If there are insufficient quantities available to fulfill the demand or the quantities available exceed the demand, deployment makes adjustments to the plan created by the SNP run.
The deployment run generates deployment stock transfers based on the SNP stock transfers that were created during the SNP run. The Transport Load Builder (TLB) then uses these deployment stock transfers to create transport loads, thus generating TLB shipments.
You can run deployment from the interactive planning table in Supply Network Planning (from the SAP APO Easy Access menu, choose Supply Network Planning ® Planning ® Interactive Supply Network Planning), or as a background job (from the SAP APO Easy Access menu, choose Supply Network Planning ® Planning ® Supply Network Planning in the Background ® Deployment or Deployment Optimization).
Prerequisites
You cannot use deployment for stock transfers involving storage location MRP areas. For more information, seeStock Transfer with Storage Location MRP Areas.
Features
Deployment Heuristic
The deployment heuristic creates a distribution plan for one product at one location. If the available quantities are insufficient to fulfill the demand, the system uses fair share rules to determine the distribution plan. However, if there is more supply than is necessary to meet demands, the system uses push rules to determine the distribution plan. You define fair share and push rules in the SNP deployment profile. For more information, see Deployment Heuristic.
Real-Time Deployment
This variant of the deployment heuristic is used to execute deployment based on the most recent results from the SNP run. Here, the system considers the current demand situation at the destination locations by first executing an SNP run between the source location and its associated destination locations before the actual deployment run.
When using fair share rule B (see Deployment Profiles), it is particularly important that distribution is based on the most exact calculation of target and planned stock levels possible.
Deployment Optimization
The deployment optimizer creates a distribution plan for all the products you chose in all the chosen locations of the supply chain model. In the main, the deployment optimizer bases its decisions on all the costs defined in the supply chain model (such as transportation and storage costs), as does the SNP optimizer. It also takes into account the following factors:
· Fair share rules and push rules
· Constraints such as transportation capacity, storage capacity, and transportation lot sizes.
You make most of the deployment optimization settings in the SNP deployment optimizer profile. For more information, see Deployment Optimization.
See also:
Deployment Heuristic
Running the Deployment Heuristic
Deployment Heuristic Profiles
Deployment Optimization
Running Deployment Optimization
Deployment Optimizer Profiles
Hope this will help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.