Professional Documents
Culture Documents
1-2 Perform a univariate forecast and analyze the graphic results. The seasonal pattern
that occurred in the past has been extrapolated into the future. Go back to the
planning table.
Click on the “STAT” symbol and the forecast is calculated automatically. Select
the “Switch table/graphic” button, and the forecast results plus historical data
will be displayed graphically.
To get back to the original table, click on the green “back” arrow.
1-3 For three months from now enter a manual correction of 100 pumps. Check that the
correction is automatically added to the demand plan. Save your plan.
In the “Correction” key figure, type in 100.
The total from the “Forecast” plus “Correction” key figures is displayed in the
“Demand Plan” key figure. Save your plan and exit the table.
1-5 Make sure that planned independent requirements have been created in the
LiveCache. Go to PP/DS product view for version 000, product T-F2##, and
location 2400.
Contents:
? Distribution Network and Process Flow
? Master Data Requirements
? Planning Methods
? SNP Heuristic
? SNP Optimizer
? Capable-to-Match
? Deployment (distribution detailed planning)
? SAP AG 2001
? SAP AG 2001
1 Course Overview
22 Integration and Technology
3 Modelling and Evaluation in APO
4 Demand Planning
Supply Network
5
55 Planning
Production Planning/Detailed
6 Scheduling
Transportation
7 Planning/Vehicle Scheduling
88 Global Available-to-Promise
99 Conclusion
? SAP AG 2001
? SAP AG
AG 2001
? SAP AG 2001
Planning Horizon
Demand Planning (DP)
Deployment
? SAP AG 2001
? SAP AG 2001
Production plant
Manufacturer
DC
Customer DC
Supplier plant
Supplier WH
? SAP AG 2001
? SAP AG 2001
??Production, shipping and storage calendars can be defined for each location.
??A handling and a storage resource can be associated with a location to represent aggregate handling
and storage capacity.
??The geographical data is used to position the location on the geographical map of the Supply Chain
Engineer. Predefining it as a part of the location data forces the location to be positioned at a specific
point on the map. If you leave these fields blank, they are filled automatically when you place the
location on the map.
??The VMI customer tab only applies to the location type '1010 customer'. The carrier tab is only
activated when you select the location type '1020 carrier'.
??Input fields that are not available to other location types are activated for location type '1007 MRP
area'.
??For each location you can define costs for storage, handling, procurement and production as well as
penalties for non-delivery. Procurement costs are used to select suppliers and production costs for
selecting PPMs. An integrated examination of the costs is carried out during the SNP optimization
run.
? Procurement
? Transportation method
? Products that can be carried
by a transportation method
? Transportation capacity by
volume, weight, pallets
? Transportation costs per unit,
product and transportation
method
? SAP AG 2001
??A transportation lane in APO represents a business relationship between the locations that you can
use to transport goods. The relationships and the locations represent the supply chain network. The
direction of the transportation lane from source to target location defines the material flow. These
transportation lanes enable you to:
??Define the product procurement parameters like lot sizes, cost functions, unit costs and lane
priorities
??Define the transportation methods (truck, ship, airplane, etc) for each lane and the related
parameters like transportation costs, distances and times
??Assign product-specific transportation methods
??Assign carriers to the lanes
??You can query the lane relevant data via the Supply Chain Engineer menu or on the map. For
example, you can display a list of all products that are assigned to a specific lane.
Production Transportation
Storage Handling
? SAP AG 2001
??You can model additional bottlenecks in your supply chain using bucket resources.
??For period-oriented short- and mid-term planning in Supply Network Planning you use bucket
resources that you plan in detail based on days.
??You can define the capacity of a bucket resource as
??Quantity (without time base) - this defines the transportation capacity of a truck or the storage
capacity of a warehouse, for example.
??Rate (quantity with time base) - this defines the consumption or production capacity of a resource,
for example; in other words, the quantity that is consumed or produced on a working day at the
resource.
??You can use transport bucket resources to model the capacity of transport fleets in order to avoid
overloading them.
??You can use storage bucket resources to model the capacity of storage locations in order to avoid
overloading them.
??You can use handling bucket resources to model the capacity of forklifts, conveyor belts or pipelines
in order to avoid overloading them.
Operations:
? Material staging Activities:
? Pre-assembly ? Produce ? Product In / Out
? Final assembly ? Tear down ? Relationship Sequence
? Inspection ? Queue time ? Resources
Resource consumption
? SAP AG 2001
??The detailed information required for producing a product is specified in the plan. Each plan includes
one or more operations. Each operation includes one or more activities, the components consumed
by the activity, the resources used and their sequence within the operation.
??The plans used for Supply Network Planning (SNP) are usually rougher than those used for
Production Planning/Detailed Scheduling (PP/DS). They contain:
??The variable costs contain all production costs.
??Activity type: P (system always considers operations as production)
??Consumption mode: S (system always considers consumption at start of activity)
??Resources:
Deployment
run
Check plan/
Release constraint- solve problems
based SNP plan
to DP
Finalize SNP plan
(available to PP / DS)
? SAP AG 2001
??Planned independent requirements are generat ed for SNP or PP/DS when the demand plan is
released from Demand Planning. This step can either be carried out using the demand planner or the
SNP planner.
??Performing the SNP run using the SNP Heuristic, SNP optimization, or Capable-to-Match (CTM)
results in a mid-term production and distribution plan.
??After the SNP run, check the exception messages (alerts) and resolve any problems that occur.
??The final SNP plan consists of purchase requisitions, stock transport requisitions and SNP planned
orders. You can automatically convert the SNP planned orders into PP/DS planned orders in the
production horizon. Production Planning and Detailed Scheduling (PP/DS) then starts with these
PP/DS planned orders to remove detailed constraints and bottlenecks and to create a feasible
production plan.
??The final SNP plan can be released back to DP for comparison of the unconstrained demand plan
with the feasible SNP plan. If the differences between these two plans are too great, you can use a
macro to trigger alerts so that the demand planner plans his forecasts again.
??After production planning has been completed, the deployment run confirms the stock transport
requisitions based on current supplies and demands.
??The TLB run groups the stock transport requisitions resulting from the deployment run into stock
transport orders.
??You can build stock transport orders manually for stock transport requisitions that could not be taken
into account during the TLB run due to specified threshold values.
? SAP AG 2001
2. Demand 1. Demand
no stock no stock
? SAP AG 2001
Capacity load
BACKWARD FORWARD
100 %
? SAP AG 2001
??The planner can use the following methods to adjust the plan:
??Backward shift of capacity load to satisfy demand with high priorities without due date violations.
However, rescheduling does not create any orders in the production horizon. Forward shift of
capacity load related to demand with lower priorities and minimization of due date violations
based on demand priorities.
??A combination of backward and forward shift of capacity load.
??If you choose a time-based capacity leveling option, you can select various priority rules:
??If you do not select a priority rule, the priority is determined by the system and is completely
random.
??If you choose Time-Based Capacity Leveling by decreasing order quantity, the system first adjusts
the largest order, then the second largest, and so on. If you choose Time-Based Capacity Leveling
by increasing order quantity, the system adjusts the smallest order first, then the second smallest,
and so on.
??If you choose Time-Based Capacity Leveling by decreasing stock range of coverage, the system
first adjusts the order with the largest stock range of coverage, then the one with the second largest
range, and so on. If you choose Time-Based Capacity Leveling by increasing stock range of
coverage, the system adjusts the order with the smallest range of coverage first, then the one with
the second smallest range, and so on.
??If you choose Time-Based Capacity Leveling by decreasing product priority, the system first
adjusts the order with the highest priority, then the one with the second highest priority, and so on.
If you choose Time-Based Capacity Leveling by increasing product priority, the system adjusts the
order with the lowest priority first, then the one with the second lowest, and so on. The product
priority is maintained in the product location master record on the SNP2 tab.
5. Stock transfer
4. Strategy: Search for created
surplus stock
Result: Stock
1. Demand with
highest priority,
no stock
2. Transp. lane
highest priority
??This slide shows the determination of feasible receipts for the demand with highest priority. CTM
gradually checks the feasible receipts, whereby you can define the sequence of checks via rules.
CTM takes the first feasible solution.
??CTM considers:
??Prioritized single requirements
??Production capacity and not handling, storage or transport capacities
??Splitting production between resources
??Component availability
??CTM is order -based planning that uses pegging methods to trace orders back to the individual
requirement. In Supply Network Planning no order-based planning takes place; rather, quantity
planning takes place. After the optimization run (or after the heuristic run), no information relating to
connections between particular planned production orders and original sales orders can be
determined.
? SAP AG 2001
??CTM prioritizes current demands based on order category (for example, sales order (KAUF) and
demand planning forecasts), due date and the defined priorities.
??The sequence of the priority criteria is of great importance for processing demands in the CTM run.
Note : If no priorities are set, prioritization occurs on a first come, first-served basis by due date.
??You can simulate demand prioritization and check the results.
??Below is a list of possible prioritization criteria: Maximum number of partial deliveries allowed per
item, stock / receipt / demand / forecast categories, confirmed quantity, ATP, BOP: confirmation
share, CTM quantity, order / MRP element number, order / MRP element item, date on which the
record was added, delivery group (items are delivered together), location, ATP, BOP: delivery date,
delivery priority, location, location product number priority, product priority, material staging date,
item type sales document, ATP, BOP: user exit priority, sales document type, requested quantity.
??The sort within a prioritization criterion can be descending, ascending or user-defined.
??Define your demand selection in the CTM profile. (Multilevel Supply & Demand Matching >
Planning > Planning CTM > Demands tab) or (Multilevel Supply & Demand Matching >
Environment > Current Settings > Demand Prioritization > Sort Profile)
Categorized Prioritized
Supplies Capable-to-Match Demands
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
Multi-site capacity and
11.
transportation capability check
? SAP AG 2001
??The CTM planning run is powered by the CTM engine, which matches the prioritized demands to
the available stock and receipts. Then it matches receipts and demands, taking account of production
capacities and transportation capabilities.
??Performing the CTM planning run in the SNP environment generates a mid-term production and
distribution plan.
??CTM complements SNP's multi-site supply chain planning strategies. Its purpose is to perform a
quick check of production capacities and transportation capabilities based on a preprocessed set of
categorized supplies and prioritized demands.
Product requirements
priorities, resources,
horizons
? Constraints:
? Customer priority
? Product priority
? SAP AG 2001
??The Optimizer uses linear programming to consider all relevant factors simultaneously as one
problem. The Optimizer compares alternative solutions for the incurred costs and proposes the best
feasible solution based on constraints defined in the system. You use the control costs to also
configure your priorities such as minimizing delays or minimizing on-hand stock. The Optimizer
considers all constraints in the supply chain model that were activated in the optimizer profile. As
more constraints are activated, the optimization problem becomes more complex and the time
required to solve this problem increases.
? SAP AG 2001
??Service level - optimal on this slide shows the simpler configuration made by the Optimizer. You
maintain high non-delivery costs (NC) and storage costs for the finished products via mass
maintenance. The high non-delivery costs force the Optimizer to exhaust all possible procurement
and production capacities to satisfy the demands. The storage costs make sure that procurement and
production are carried out as late as possible.
??Costs - optimal on this slide shows the more complex configuration made by the Optimizer. You
maintain realistic costs for procurement, production, transportation and storage. You model lost sales
and customer dissatisfaction via delay and non-delivery costs. In this scenario the Optimizer uses the
costs to determine the most cost-effective integrated solution.
??The result of the optimization run is an optimal solution (minimum costs or maximum profit) taking
account of planning-relevant transportation, production, storage and handling constraints. In that
sense, the solution is feasible. However, the result might be that due date constraints are violated or
safety stocks are not filled. Due dates and safety stocks are considered to be soft constraints. There
are costs associated with such violations, so the Optimizer only proposes this solution if, according
to the costs specified in the system, it is the least costly solution.
??The essence of optimization is finding the best feasible solution. For example, is it less costly to
deliver two days late or to produce three weeks early? The challenge with optimization is to properly
define the relevant costs (for example, cost of late delivery). You can fine-tune the relative
importance of different cost types via the cost profile.
Heuristic: Optimizer :
? SAP AG 2001
??The Heuristic is a rapid infinite planning method that generates alerts when there is a material
shortfall or resource overload.
??CTM is a rules-based method with extensive prioritization capabilities and finite, global planning of
production resources. CTM is order-based planning that uses pegging methods to trace orders back
to the individual requirement.
??The Optimizer considers material and resource availability simultaneously. It uses linear
programming to consider all relevant factors simultaneously as one problem. In other words, there is
no sequential processing in the determination of a solution. The Optimizer considers transportation,
production, storage, and handling costs to propose a minimum cost solution that meets the respective
constraints.
??The lack of pegging of orders back to the individual requirement has the following repercussions: In
Supply Network Planning no order-based planning takes place. After the optimization run (or after
the Heuristic run), no information relating to connections between particular planned production
orders and original sales orders can be determined (CTM can, however, provide such information via
order tracing).
Speed + - ?
Quality - + ?
Multi-level + + +
Costs - + -
? SAP AG 2001
??The performance of the three planning methods can be divided up roughly as follows: The Heuristic
is the fastest method, CTM is in the middle and the Optimizer is the most complex and the slowest
method. This is just a rule of thumb. If you plan a lot of orders per period and location product, the
performance of CTM and the Optimizer can be compared since planning in CTM is order -based.
??The quality of the heuristic planning result is poorest (infinite!), next comes CTM (rules), and you
should expect the best result from the Optimizer that weighs up all possibilities of this algorithm.
??Production resources are considered globally and finitely by the Optimizer and CTM, while the
infinite planning result of the Heuristic must be postprocessed interactively.
??Transportation,storage and handling resources can be considered globally and finitely by the
Optimizer, while the infinite planning result of CTM and the Heuristic can be postprocessed
interactively.
??All methods can plan all BOM levels automatically.
??Costs ar e only relevant to the Optimizer.
??Priorities control CTM. There are product, location, order and due date, procurement and stock
transport priorities. You set priorities for the Optimizer via the penalty costs for late delivery and
non-delivery of the location products.
??Quota arrangements are used by the Heuristic and CTM. They can be optimized using the Optimizer.
Planning Horizon
Recommended
Supply Network stock transport
Planned orders
Planning requisitions
Production Planning /
Detailed Scheduling
Firmed
stock transport
Deployment requisitions
? SAP AG 2001
??Deployment determines which demands can be fulfilled by the existing supplies. If the produced and
procured quantities as well as the demands match SNP planning, the result of deployment is a
confirmation of the SNP plan. If the available quantities are not sufficient to meet the demand, the
system makes the necessary adjustments according to whether you are executing the deployment
heuristic or deployment optimization.
??The Transport Load Builder (TLB) then groups these confirmed quantities together into stock
transport orders.
??Deployment and the TLB confirm the OLTP stock transport requisitions and can convert them into
stock transport orders or VMI sales orders. Via Customizing -> APO -> Supply Chain Planning ->
Supply Network Planning (SNP) -> Basic Settings -> Configure Transfer to OLTP Systems you can
configure if transfer should take place using deployment or the TLB.
??Deployment and TLB ar e simply used to confirm stock transfers. Everything beyond this, such as
route planning, selection of carriers and generation of deliveries and transportations in the OLTP
system, is planned in TP/VS (Transportation Planning and Vehicle Scheduling).
? Heuristic Heuristic
? Product by product
? Coverage maximization
? Cost-based optimization
? SAP AG 2001
??The deployment function in SNP determines how and when inventory should be deployed to
distribution centers, customers, and vendor-managed inventory (VMI) accounts. It produces
optimized distribution plans based on constraints (such as transportation capacities) and business
rules (such as minimum cost approach, or replenishment strategies).
??A variety of deployment strategies are used depending on the current situation (e.g., fair share, push
deployment, pull-push deployment, and minimum cost flow optimizat ion).
??The Heuristic has a hierarchical view of the supply chain network: Deployment is always carried out
from one delivery location to the receiving locations (DCs or customers).
??The deployment heuristic calculates a replenishment plan for a product in a delivery location. If the
available quantities are not sufficient to fulfill the demand, the system determines the distribution
plan based on fair share rules. If on the other hand supply exceeds demand, the system uses push
rules to determine the distribution plan. Fair share and push rules are defined in the deployment
profile.
??Deployment optimization has the integrated view of the receipt situation of all delivery locations and
the demand situation of the receiving locations.
??The deployment optimization run calculates a replenishment plan for a product in all locations within
the network. If the available quantities are not sufficient to fulfill the demand or supply exceeds
demand, the system uses minimum cost flow optimization to determine an optimum distribution plan
for the whole network at once.
??Deployment optimization works like SNP optimization except that the production and procurement
quantities are not changed.
? Fair Share
? Proportional allocation
according to demands
DC1
? Proportional allocation
according to target stock
level
? Quota arrangements Plant DC2
? Push deployment
? Based on future demands
? Quota arrangements
? SAP AG 2001
??There are several deployment and allocation strategies: fair share, push deployment, pull-push
deployment, and minimum cost flow optimization.
??If demand exceeds supply, use a fair share allocation.
??If demand is less than supply or excess inventory exists, use a push strategy to be able to transfer
stock as early as possible.
??When excess inventory exists, surplus stock can be distributed according to push logic.
??For pull/push deployment rules, the demand horizon restricts the future demands that can be
delivered early.
??Set the pull horizon on the demand profile; set the push horizon on the supply profile.
Demand
Today 05.01.2001 1000 100 (DC1)
Supply
06.01.2001 900 500 (DC2)
07.01.2001 400 800 (DC1+2)
DC1 200
DC2 600
Deployment Results
05.01.2001 Plant to DC1 100
06.01.2001 Plant to DC 2 500
07.01.2001 Plant to DC 1 100
07.01.2001 Plant to DC 2 300
? SAP AG 2001
??The slide shows the result of a deployment heuristic using the fair share rule A that is issued after
planning in the background: Today, 1000 units are available in the plant for distribution. The stock
transfer for the current deman d from DC1 can be confirmed. The stock transfer for tomorrow can
also be confirmed. The day after tomorrow, the demand exceeds the remaining quantity in the plant,
so the 400 units are distributed using the defined fair share rule A.
??You use the ATD (Available to deploy) quantity to describe the quantity that is determined in the
delivering plant for distribution and according to ATP rules. You configure the category groups in
Customizing and assign them to the locations. Receipts (ATR) are, for instance, stock, production
orders, purchase orders, etc. Issues (ATI) are reservations, etc.
? Grouped according to
? Products (transportation planner)
? Time (pull-in horizon)
? Transportation zones
? Ensures that minimum requirements
are met for:
? Volume
? Weight
? Number of pallets
? SAP AG 2001
??The primary purpose of the Transport Load Builder (TLB) is to use the results of the deployment run
(single product transport recommendations) to create multi- product transport orders in a time period
for a transportation zone. It should be ensured that:
??The transportation methods are filled to maximum capacity
??No transportation method is dispatched that is not filled to minimum capacity
??For stock transport orders that could not be satisfied during the TLB run due to specified
constraints, you can build transport orders manually
??You can create transportation zones for the TLB or transfer them from R/3. You can thereby
consolidate your transportation capabilities (for example, use one truck to deliver orders to several
locations). You can group several locations together using transportation zones (and thereby create a
zone). TLB orders for several locations are regarded as one order for a large location, although
individual purchase orders do actually exist for separate locations.
??If you want to use transportation zones, you create a location as a transportation zone in the location
master. (From the APO Easy Access menu choose Master Data -> Location. Use the input help (F 4)
in the Loc.type field of the location master and choose 1005 - transportation zone). You then assign
the relevant locations in the hierarchy master to this transportation zone (choose Master Data ->
Hierarchy). You can display these location hierarchies in the TLB interactive planning shuffler.
Full truck
(best price) Minimum capacity
Half-full
truck
Days
1 2 3
? SAP AG 2001
??In the Interactive Planning table for the TLB, you can view transport orders generated automatically
by TLB for a specific day. If the load does not meet the minimum capacity requirements specified
for a full transport load within the specified pull-in horizon, you can manually create transport orders
that are planned for later shipment and ship them early in order to build a full truck load.
? SAP AG 2001
1-2 Look at the future periods and check if the planned independent requirements you
released for the distribution centers 2400 and 2500 and the plant 1000 are
displayed. Analyze in which key figure the planned independent requirements are
shown.
Make sure that no distributed demands and production orders exist for the
production plants 1000 and 2300.
1-3 Run the network heuristic and check the situation for your product T-F2## for the
distribution center 2400.
Verify that there are now values in the Total receipts row.
Which plants are supplying the receipts?_______________
1-5 Run optimization for your product T -F2## at all locations. Load all location
products with product T -F2## into the planning table. Start the Optimizer with the
optimizer profile DISCRETE and the cost profile MASTER. Check the capacity
situation again.
1-6 Check if the receipts have been transferred to the connected R/3 System. Log on to
the R/3 System and call the stock/requirements list for your product T_F2## in
plant 1000.
1-1* Run deployment for the location 1000 for the next 100 days using mass processing.
Reduce SNP transport orders. Write down the result of the deployment run:
_______________________________________________________________
_______________________________________________________________
If you select Orders: Do not change the system will not change the
SNP transport orders.
The horizons in the training system are not realistic. In practice,
deployment is used to confirm stock transports for the next few days.
But in the course we cannot wait until the orders reach the short-term
horizon.
1-2 Look at the future periods and check if the planned independent requirements you
released for the distribution centers 2400 and 2500 and the plant 1000 are
displayed. Analyze in which key figure the planned independent requirements are
shown.
Make sure that no distributed demands and production orders exist for the
production plants 1000 and 2300.
Display the weeks in the next month and you will see the quantities in the key
figure “Total demand”. Only forecasts outside of the forecast horizon contribute
to the total demand.
Double-click on the “Total demand” row. The released data is displayed in the
key figure "Forecast". All six key figures (forecast, sales order, dependent
demand, distributed demands) contribute to the total demand.
Double-click on your product T-F2## for the distribution center 2500. Ensure
that demand is displayed.
Double-click on your product T-F2## for the plant 1000. Forecasts are displayed
but no production quantities and distributed demand.
1-4 Check the capacity situation for resources WT-L##_1000_001 and WT-
L##_2300_001 in the Capacity View. Switch data views by dragging the gre y bar
upwards on the left and double-clicking on data view SNP94(2) “CAPACITY
CHECK”.
Open the selection window and, under “Show”, select “APO Resource”. Version
000 is already displayed automatically. In the next row, enter “APO – Resource”
once again, and on the right-hand side enter your resources WT-L##*. Load the
data for a resource into the planning table sequentially. If there are any capacity
overloads, run “Capacity Leveling”.
Double-click on the data view SNP94(1) “SNP PLAN”. Open the selection
window and, under “Show”, select “APO Location product”. Version 000 is
already displayed automatically. In the next row, enter APO -Product once
again, and on the right-hand side enter your product T-F2##. Select “Adopt”,
and your selection will be adopted by the selection window.
Press the “Select all” symbol above the selection window and load the data by
pressing the “Load data” symbol.
Start the optimization run by pressing the “Optimizer” symbol.
Enter DISCRETE for the optimizer profile and MASTER for the cost profile and
press “Execute”. When the Optimizer has finished the calculation, the resulting
costs are displayed. When you have analyzed the costs, select the green arrow
BACK to return to the planning table. Now you can check the resource loads
again.
1-6 Check if the receipts have been transferred to the connected R/3 System. Log on to
the R/3 System and call the stock/requirements list for your product T_F2## in
plant 1000.
1-1* Run deployment for the location 1000 for the next 100 days using mass processing.
Reduce SNP transport orders. Write down the result of the deployment run:
_______________________________________________________________
_______________________________________________________________
_______________________________________________________________
Supply Network Planning? Planning ? SNP in the Background ? Deployment
If you select Orders: Do not change the system will not change the
SNP transport orders.
The horizons in the training system are not realistic. In practice,
deployment is used to confirm stock transports for the next few days.
But in the course we cannot wait until the orders reach the short-term
horizon.
Contents:
? Consumption of planning by sales orders for forecast-
controlled products in make-to-stock and make-to-order
production
? Simultaneous material and capacity requirements planning at
operation level in the production plant
? Tools for production planning and production scheduling
? Schedule optimization in PP/DS
? Transfer of planning results to the execution system
? SAP AG 2001
? SAP AG 2001
1 Course Overview
22 Integration and Technology
3 Modelling and Evaluation in APO
4 Demand Planning
55 Supply Network Planning
Production Planning/Detailed
66 Scheduling
6
7 Transportation Planning
88 Global Available-to-Promise
99 Conclusion
? SAP AG 2001
? SAP AG 2001
? SAP AG 2001
??Simultaneous material and capacity requirements planning: You can define resources as finite
resources in the resource master (resources critical for planning). At these resources, operations of
orders are only created if there is enough capacity available for the order quantity on the order date.
If there is not enough capacity available, the system searches for a new date, taking the capacity
situation into account.
??Automatic planning immediately: If you set this indicator for a product (PP/DS tab in the product
master), the system starts a single-level planning run for this product for each change made that is
relevant to planning (for example, a new sales order). At the same time (immediately) a multi-level
ATP check is performed for the product and for the assembly/components for which automatic
planning immediately is defined.
??Planning with exact times: Dependent requirements and orders are created with a time.
??Bi-directional propagation of order changes: If you make time-related changes to orders at, for
example, finished-product level, you can specify that the system is to automatically move the
assembly orders. If, however, there is not enough capacity at that time for the assembly orders, an
exception message can be generated or the order is not moved at finished product level. In the other
direction, moving assembly orders can have an effect on finished product orders.
??Planning alternative resources: If not enough capacity is available at a resource, the operation can
be rescheduled at alternative resources (maintained in the PPM).
??Schedule optimization: During planning, it may be that orders were generated whose order
sequence is not optimum. Therefore, you can change the sequence and resource assignment of
existing orders in the optimization run.
PP/DS SNP
Create, Create, Create, Create,
change change change change
Receipts
Mo Tu We Th
Reqmts in plant
Production horizon
(per product)
? Capacities and material are planned ? Capacities are planned in time bucket
based on exact times (to the second) profiles in an aggregated manner
? Consideration of order sequences ? Order sequences not considered
? Optimizer: Can optimize the sequence ? Optimizer: Optimizes lot sizes,
of existing orders and operations determines source of supply
? SAP AG 2001
??Ifyou decide to plan using both Supply Network Planning (SNP) and Production Planning and
Detailed Scheduling (PP/DS), the production horizon is used to separate the areas of responsibility
for these two planning functions:
??Supply Network Planning is used for medium -term to long-term planning across the whole
logistics chain (especially if several plants and distribution centers are available). Requirements
for a defined bucket (for example, day) are aggregated. In this case, it is irrelevant whether a
requirement is in an early shift or late shift since the requirements are only roughly planned, and
even the time positions of breaks are not taken into account. Furthermore, you are not only able to
perform time aggregated planning in SNP, but also period aggregated planning (if desired). You
can define bucket resources to be used for SNP which can represent, for example, the available
capacity of a whole warehouse. Since you create separate PPMs for SNP (which are usually
copied from PP/DS -PPMs), you can describe production at these bucket resources. Order
sequences play no role in the time area of SNP planning.
??PP/DS is used for short-term planning in which orders must be scheduled to the minute and order
sequences must be taken into account (sequence planning and optimization).
??As soon as a requirement is within the production horizon, it is no longer planned in the SNP
planning run, but rather in the production planning run in PP/DS. Orders can be manually created or
changed in PP/DS across the complete time axis, irrespective of the production horizon. During
automatic planning (the production planning run) in PP/DS, only orders within the production
horizon are created. In SNP, however, orders cannot be created or changed in the production horizon.
Orders that are in the production horizon and thus planned by PP/DS are still displayed in SNP as
aggregated requirements for the defined bucket.
SNP
Production horizon Create
100
Today
PP/DS Delete
Production horizon
? SAP AG 2001
??In this graphic, an order is created in Supply Network Planning using the production process model
defined in SNP. Production process models are created (the SNP-PPM can be copied from PP/DS-
PPM, which is generated via the R/3-APO interface from the R/3 routing/BOM). Bucket resources
(used only in SNP) or mixed resources (which can be used both in PP/DS and SNP-PPM) are
planned in Supply Network Planning. Orders are aggregated for each defined bucket.
??As soon as the start date of the order enters the production horizon, the SNP order is no longer
planned by SNP. The SNP order must be converted into a PP/DS order so it can be planned by
PP/DS. To do this, background conversion is available in the PP/DS menu, which can be used to
schedule periodically. The conversion creates the order again in PP/DS using the production process
model defined there. Before the conversion, the aggregated requirements are displayed in SNP as
planned production. After the conversion in PP/DS, the orders are still displayed as aggregated
requirements in SNP.
??The production horizon is defined as a number of days from the current day into the future in which
PP/DS is to be used to plan. The production horizon can be defined in Customizing for Supply Chain
Planning, in the IMG activity, Display Global Parameters and Default Values. You may also define
a production horizon for each product per location in the product master. This definition takes
priority over the Customizing definition.
Requirements
strategies
Quantity 100 Quantity ?
Date 05/10 Date ?
SD
Planned
indep. Sales
reqmts order
Production /
Purchasing Customer
? SAP AG 2001
??Requirements strategies represent the business procedure for planning production quantities and
dates. A wide variety of requirements strategies are available offering a number of different
possibilities for planning, ranging from make-to-order production to make-to-stock production.
Depending on the strategy you select, you have the following options:
??Planning specifically for the assembly, if you can plan more easily at component level. Final
assembly takes place in make-to-stock or make-to-order production.
??Stocking up of assemblies by planning at finished product level, but final assembly is not triggered
until the sales order is received. Final assembly takes place in make-to-stock or make-to-order
production.
?? Make-to-order production only, without planning the finished product or the components
??Furthermore, you can combine requirements strategies. This allows you to plan a finished product
with a requirements strategy for make-to-stock production as well as plan an important assembly that
is also sold as a spare part.
??The planning strategies available for a material can be found in APO Customizing for Master Data
(in step Determine Requirements Strategies). You can assign a requirements strategy to a material in
the Requirements strategy field. Each requirements strategy contains important control parameters
for the consumption of sales orders (or dependent requirements) and planning.
Convert Convert
??Material requirements planning deals with current and future requirements. The planned
requirements quantities trigger planning (in consumption-based planning, for example, planning is
triggered when the reorder point is not reached). Requirements elements for material requirements
planning are, for example, sales orders, planned independent requirements, dependent requirements.
??If theproduction planning run discovers shortage quantities, procurement proposals are generated:
purchase requisitions and planned orders are internal planning elements which can be changed,
rescheduled or deleted at any time.
??In the case of in-house production the system creates planned order for planning production
quantities. When planning is complete, planned orders are converted to production orders.
Dependent requirements for the planned order are converted to reservations for the production
order.
??In external procurement, the system generates a purchase requisition for planning external
procurement quantities. When planning is complete, the purchase requisition is converted to an
order. If a material exists for a scheduling agreement, scheduling agreement delivery schedules
can also be generated directly during the production planning run.
??When planning is complete, in-house production or external procurement must be triggered. For this,
??Planned orders are converted to production orders if you are working with discrete manufacturing
(order-based production)
??Planned orders are converted to process orders if you are working with process manufacturing
??Planned orders are used as a basis for production if you are working with repetitive manufacturing
(period-based instead of order -based)
??Purchase requisitions are converted to purchase orders
Availability date
Operations
Assembly of
a different 10 20
plant
10 GR processing time
GR processing time
? SAP AG 2001
??When the lot size of the planned order has been determined and the PPM has been exploded, the
production planning run calculates the dates of the planned orders.
The dependent requirement dates of the planned orders are moved to the dates of the assigned
operations (PPM). A material order appropriate for the operation is then possible.
??The system assumes material staging according to component assignments in the PPM to the
operations in the PPM. The dependent requirement dates of the BOM components are moved to the
production start dates of the operations to which they are assigned.
30
Resource 3 (finite) 30
20 20
Resource 2 (infinite)
10 10
Resource 1 (finite)
Time
? SAP AG 2001
??If a product is not available, the requirement (the sales order or dependent requirement, for example)
triggers production directly: If it triggers an order for in-house production, APO creates a planned
order for the desired quantity in PP/DS. All of the operations of the PPM are scheduled at the
resources of the PPM, and the system takes the capacity restrictions into account (available capacity
and orders that may have already been scheduled).
If the capacities are already exhausted on the desired date, the system uses simultaneous material and
capacity requirements planning to find a date on which the planned order can be created. You use the
strategy profile to define how the system is to schedule (search for a slot, infinite planning ...).
??Prerequisite:
??Maintain resources critical to planning as finite resources in the resource master. At these
resources, operations of orders are only created if there is enough capacity available for the order
quantity on the order date.
??Maintain the strategy profile with which you want to trigger the scheduling of planned orders in
planning under Global Settings in Customizing for PP/DS, in the Strategy profile field. The
default strategy profile in the delivery system is SAP002 (search for a slot backward).
Res01 P Loc 01
Order Chart
03/15/1999 03/16/1999
OrderNo Products
22 00 02 04 06 08 10 12 14 16 18 20 22 00 02 04 06 08
Chart objects
000001294 P
000001335 P
000001357 P
Product histogram
03/15/1999 03/16/1999
Product
22 00 02 04 06 08 10 12 14 16 18 20 22 00 02 04 06 08
300
Product 01 200 Different
100
Order No: 000001294 charts
Graphical object
Message bar (operation, order)
? SAP AG 2001
? SAP AG 2001
??Use: Optimization allows you to optimize the production dates/sequences and the resource
assignment of existing operations/activities which were generated by the production planning run or
manual planning. The optimizer does not create or delete orders.
The purpose of optimization is to generate feasible production plans and increase the efficiency of
production. Several optimization parameters (such as setup times, due date violations) can be
weighted in such a way that the optimized schedule comes as close to the desired results (for
example, minimum setup times) as possible. The following parameters can be taken into account in
optimization:
??Total lead time (from the start of the first operation to the end of the last operation in a schedule
within the optimization horizon). The total lead time makes a statement about the compactness of
the orders within the optimization horizon.
??Sum of setup times
??Sum of setup costs
??Maximum delay costs (maximum delay of an order compared to its requirements or due date).
??Sum of delay costs (delay compared to requirements or due dates)
??Sum of mode costs
Resource B
Resource C
Resource D
Resource E
Non-working times
Fixed operations
Operations, that may be rescheduled
Relationships
Transferred resources: B, C, D
Optimization range
? SAP AG 2001
??When you call up optimization you set theoptimization horizon (start and end) and the start date
for the optimized schedule. The optimization function reschedules orders and operations that are:
??Completely within the optimization horizon (defined by a start and an end date)
??Not fixed
??At resources which were transferred to optimization
- If you have selected resources in the planning board, only these selected resources are
transferred to the optimizer. If you have not selected any resources in the planning board, the
system transfers the resources that you specified in the work area for the planning board and the
optimizer.
In particular, the system can only reschedule an activity to alternative resources during
optimization when these resources are included in the resource selection for optimization.
??The relationships of the fixed orders and operations to the non-fixed orders and operations determine
if and by how much these orders and operations can be shifted during optimization. The optimized
schedule is, therefore, adjusted to accommodate the fixed orders and operations.
??The system does not change planning outside of the optimization window during planning. Activities
outside of the optimization window are fixed during optimization. However, the fixed activities
determine by their relationships to the non-fixed activities in the optimization range, whether and
how far these activities can be rescheduled during optimiz ation. The optimized schedule is,
therefore, adjusted to accommodate the fixed activities.
??Earliest start date for the optimized schedule: Before the optimization, you specify the earliest
date on which the optimization function can schedule the activities. You cannot enter an earliest start
date that lies in the past.
A C Requirements time B A
Setup Setup
C time A A time
B
Optimization result (with light weighting of delays)
Setup Setup
A A time B time
C
time Optimization result (without weighting of delays)
etup
timum s
Op Time
? SAP AG 2001
??Use: You can optimize the schedule for single resources based on the sum of the setup times and
sum of the setup costs. The system determines sequence dependent setup times and setup costs from
the setup matrix (which can only be maintained for single resources).
??Prerequisites:
??You have modeled the single resources and the operations that are processed at these resources
exactly as with the setup time adjustment (see the unit Simultaneous Material and Capacity
Requirements Planning).
??You strongly weighted the setup times or the setup costs in the objective function.
??Scope of function: In the objective function, the system interprets the values for the setup times and
setup costs from the setup matrix as follows:
??You enter the setup time in a unit of your choice (for example, hours or minutes) in the setup
matrix. The system uses the setup duration in seconds in the objective function. If you enter, for
example, a setup duration of 10 min utes in the setup matrix, the system uses the value of 600
(seconds) in the objective function.
??You enter the setup costs without unit of measurement in the setup matrix. In the objective
function, the system directly uses the value entered in the setup matrix. If you enter, for example,
the value 10 for the setup costs in the setup matrix, the system uses the value of 10 to calculate in
the objective function.
??Important: In the objective function, the setup costs with a value of 10 correspond to a setup
duration of 10 seconds. You must consider this relationship between setup times and setup costs
when defining the objective function, that is, when specifying the weighting for the setup times and
the setup costs.
Individual
Individual conversion
conversion Planned Production
order order
Purchase
requisition Order
Collective
Collective conversion
conversion
Planned Production
orders orders
Purchase
requisitions Orders
? SAP AG 2001
??You can trigger the conversion of planned orders and purchase requisitions to production orders or
orders directly in APO. You set the conversion indicator in APO for the orders you want to convert.
The orders are transferred to the OLTP system and converted automatically. The converted orders
are sent back to the APO System with a different ATP category (purchase requisition to purchase
order). If a planned order is converted to a production order, the dependent requirements of the
components are converted to reservations.
??You can convert planned orders and purchase requistions in one of the following two ways:
??Individually in interactive planning: In the product view and the product planning table, you can
select orders to be converted and then choose Set conversion indicator. When you save the
planning results, the orders to be converted are transferred to the R/3 System, where the
conversion will be automatically triggered. The converted orders are sent back to the APO System
with a new ATP category.
??Using mass conversion and selection criter ia (Choose Production Planning -> Manufacturing
Execution -> Conversion of Orders/Purchase Requisitions): You can set the conversion indicators
for a large number of orders or for several products. You can restrict the selection of orders to be
converted by entering the product, location, production planner and the offset for the opening
period. The opening period, which is defined in the product master on the PP/DS tab, controls
which orders are to be converted. The opening period is a number of workdays starting from the
current date. The APO System only sets the conversion indicators for orders whose order start
dates are within this period. The opening period is used both for in-house production orders and
external procurement orders.
??Prerequisites: On the PP/DS tab in the product master, you have maintained an opening period for
each product at the location level.
Offset time
Purchase requisition
Opening
period
Planning
Planned order
Production orders/
process orders Order header
Operations
Orders
Materialcomponents
Production resource/tool
Costs PlanK 20
Plnd 100
Actual 50
??APO orders contain three dates: production start, production finish, creation date. The creation date
is the date on which a planned order is to be converted to a production order or a purchase requisition
to an order. This date is based on the opening period defined in the R3 material master (SchedMargin
key field). The opening period from the SchedMargin key of the R/3 material master is transferred to
the APO product master in the R/3 APO interface (Opening field in the Horizons group box).
??As soon as the creation date of a planned order is passed on to a time horizon selected in mass
conversion, it can be converted in mass conversion. The time interval (offset time) entered in mass
conversion is always valid as of today's date. Planned orders whose creation dates are in the past are
automatically selected too.
??Planned orders are usually converted to production orders (in-house production), purchase
requisitions to purchase orders (external procurement).
??In in-houseproduction, the order type in R/3 determines whether it is a production order or a
process order. The order type is taken (in the sequence of highest priority) from the production
scheduling profile in the R/3 material master, the MRP group in the R/3 material master, and the
plant parameters in R/3-Customizing. The R/3 System decides whether a production order or a
process order is to be generated for the product.
??When the pla nned order is converted to a production order or process order, the planned order is
deleted. The related dependent requirements (material components) and any capacity requirements
are redirected to the newly created production order. The dependent requirements become
reservations.
? SAP AG 2001
1-1 In the Product View in APO, look at the planned independent requirements for
pump T-F2## at location 1000 (production plant Hamburg) .
1-1-1 Why have no planned orders been created, in the near future, for the planned
independent requirements?
_____________________________________________________
Field Values
Product
Location 1000
Production planner 0##
Planning file entry created X
Choose Execute.
1-3 In the Product View in APO, look at the planning result for the APO product T -
F2## at location 1000 (production plant Hamburg).
1-3-1 Look at the situations of the planned order for product T -F2## and check the
requirements/receipt situation for all components.
Were all requirements planned in planning?
_____________________________________________________
Look at the component list of the latest planned order within the production
horizon: Double -click on the latest planned order within the production
horizon to go to the planned order.
After double -clicking, you can see the detailed data (header data) of the
planned order on the right, and the complete structure of the planned order
on the left. On the left you can recognize the receipts, components
(requirements) and operations of the planned order.
When are the start and end dates of the planned order for the final assembly
of pump T-F2##?
_____________________________________________________
_____________________________________________________
_____________________________________________________
_____________________________________________________
After you have executed the planning run for your plant 1000 in
Hamburg, you must then reschedule the sequence of the existing
orders.
1-4 Until now, we have only created requirements and orders for pump T-F2## (white
pump). Now, create some more planned independent requirements for pump T-F4## in
plant 1000.
To demonstrate that planned independent requirements can be created not only using
APO Demand Planning, but also using R/3 Program Planning, create the planned
independent requirements manually in R/3.
1-4-1 Enter the independent requirements for material T-F4## in plant 1000 in the
R/3 program planning. In the initial screen of the transaction, enter T (day
format) in the planning period field, to select day schedule lines as the period
schedule line.
In the planning table, select the first row of the table and choose the delivery
schedule tab.
Enter the following independent requirements for pump T-F4## in plant 1000:
5 5 5 5
1-5-1 Call up the variable view of the Detailed Scheduling Planning Board. Choose
the “Pump ##” overall profile and confirm using Enter.
You see that the work area “Pump ##” was selected automatically when you
selected the overall profile “Pump ##”. This includes all resources for the final
assembly of the pumps.
Enter the detailed scheduling planning board using the selection criteria
specified above and then navigate in the planning board.
1-5-2 Look for the first orders for products T-F2## (white pump), and T-F4## (blue
pump) by selecting the respective product numbers one after the other in the
Product chart and then right-click to select "begin with first graphical object".
Look in the Resources chart to see which resources the pumps occupy. To find
out which capacity loads belong to which order in the resources chart, select the
first planned order for the product T-F2## and then right-click to select “Mark
objects for the same order”.
All capacity re quirements belonging to the order are then shown in color.
1-5-3 In the Detailed Scheduling Planning Board, you can now manually reschedule
orders/operations using Drag & Drop, or you can start the Optimizer for
automatic sequence planning.
However, only observe the planning result here, and then exit the Detailed
Scheduling Planning Board without saving.
1-1-1 Why have no planned orders been created, in the near future, for the planned
independent requirements?
For product T-F2##, a production horizon of a certain number of days has
been maintained in the product master, on the SNP2 tab. Requirements
outside this production horizon are covered by the SNP planning run.
Requirements within the production horizon are covered by the PP/DS
planning run. As only an SNP planning run was executed in the last
exercise, but not a PP/DS planning run, no planned orders are available for
any requirements within the production horizon.
1-2 APO menu path: Production Planning ? Automated Production Planning and
Optimization ? Production Planning Run
1-3-1 Look at the situations of the planned order for product T -F2## and check the
requirements/receipt situation for all components.
Were all requirements planned in planning?
After the production planning run, all the planned independent
requirements were planned.
1-3-2 When are the start and end dates of the planned order for the final assembly
of pump T-F2##?
Take the dates from the planning order header.
How many operations have been scheduled in the planned order on the
various resources?
In total, the six different PPM operations have been scheduled in the
planned order.
1-4
1-4-1 R/3 menu path: Logistics ? Production Planning ? Program Planning
? Planned Independent Requirement ? Create
1-5
1-5-1 APO menu path: Production Planning ? Interactive Production Planning
? Detailed Scheduling Planning Board
1-5-2
1-5-3
Contents:
? Route optimization
? Transportation consolidation
? Carrier selection
? Shipment tendering
? SAP AG 2001
? SAP AG 2001
1 Course Overview
22 Integration and Technology
3 Modelling and Evaluation in APO
4 Demand Planning
Supply Network
55 Planning
Production Planning/Detailed
6 Scheduling
77 Transportation
7
Planning/Vehicle Scheduling
8 Global Available-to-Promise
99 Conclusion
? SAP AG 2001
? SAP AG 2001
??The Precision Pump Company is using Transportation Planning to make optimum usage of available
capacities in trucks, trains, ships, and aircraft . Their aim is to perform planning more efficiently and
reduce costs.
??They are using Vehicle Scheduling to analyze and modify the plan that was generated during
Transportation Planning. For example using carrier selection manually to fix planning results, and
transfer them to the OLTP system for transportation execution (LES).
BW
(Monitoring) LES (Execution)
? SAP AG 2001
Unconstrained
Demand Planning Forecast
Aggregated planning
Constrained
PP/DS
Detailed planning
Constrained
Planned
Deployment deliveries
Route planning and
transportation consolidation
Planned
shipments
Transport Load
Load
TP/VS
Builder
? SAP AG 2001
??Supply Network Planning is used for long-term and mid-term planning. A big advantage of this
component is the sourcing which determines where and how a product will be procured. Sourcing is
optimized by functions such as the Transport Load Builder (TLB). Bucket capacities are used in
Supply Network Planning to plan products. These bucket capacities show the most detailed level of
daily planning.
??Vehicle Scheduling (VS) is a short-termplanning component. You can define planning horizons for
both the Supply Network Planning component and the VS component here. These horizons are all
independent of one another and have to be planned as such.
??In Vehicle Scheduling, resources and transportation processes are maintained in detail, so that
planning will be performed as precisely as possible. When orders from Supply Network Planning
become VS orders, the following happens:
??the orders are received in a specific sequence
??the exact transportation time is specified
??information and processes that were still outstanding are added (data and processes that are not
necessary for Supply Network Planning, but are for Vehicle Scheduling such as loading and
delivery activities)
Outbound
Transportation
Replenishment
zones
Inbound
? SAP AG 2001
??Customers or suppliers can be grouped into transportation zones to reduce the complexity of TP/VS
problems.
??The unbroken line is modeled and the broken lines are generated by the optimizer.
??Ifa transportation zone is loaded with customers from the R/3, an associated hierarchy is generated
automatically.
Sales orders,
stock transfers,
forecasts
Objective:
Deliveries and
transportation orders in R/3
Simultaneous route
planning and transportation Optimizer
consolidation
TLB orders
Express orders Vehicle
resources
Selection of
transportation provider
? SAP AG 2001
??Optimization in TP/VS is for optimizing transportation schedules with the assignment of vehicle
resources to orders. It takes into account the following:
??Travel from and back to the depot
??Loading and unloading time
??Order consolidation
??Reduce transportation time costs
??Reduce distance costs
??Costs for being too early/delayed
??Costs for non-delivery
??Transportation fixed costs
??Optimization can be simulated or used in the active planning version 000.
Optimization
(Route planning and
transportation consolidation)
Publication of
Shipment tendering deliveries
? SAP AG 2001
EDI
Business
Business scenario:
scenario: Business
Business scenario:
scenario:
Internet
Internet tendering
tendering Internet tendering
tendering
Create
deliveries
XML
Publish
Transportation
Transportation planner
planner
Service
Service agent
agent
HTML
Accept / Refuse
Release for
execution
? SAP AG 2001
? SAP AG 2001
Contents:
? Global ATP and Integration with OLTP
? Integration with PP/DS
? Rules-based ATP
? Product Allocations
? SAP AG 2001
? SAP AG 2001
1 Course Overview
22 Integration and Technology
3 Modelling and Evaluation in APO
4 Demand Planning
55 Supply Network Planning
Production Planning/Detailed
6 Scheduling
7 Transportation
Planning/Vehicle Scheduling8
8
88 Global Available-to-Promise
99 Conclusion
? SAP AG 2001
? SAP AG
AG 2001
R/3 APO BW
Sales Production
orders Planning and
Detailed Supply Key
Shop floor Global
Scheduling Network performance
control ATP
Planning indicators
Inventory (KPIs)
management Deployment
Transportation
processing Transportation Planning
? SAP AG 2001
??In the R/3 APO interface you can define that the ATP check of products (ATP check, ATP =
Available-to-Promise) should not be carried out in R/3 but in APO, as soon as a sales order is
created.
??Sales orders created in the OLTP system (for example, R/3 System) automatically trigger the
availability check in APO in this case. Depending on the system settings, a check can be carried out
against inventory, production plans and distribution plans.
??Plannedorders that are created via ATP integration with PP/DS can be sent back directly to the
OLTP systems.
? SAP AG 2001
??Rules-based ATP (multi-step availability check): When there is no availability, you can configure in
APO that the system should carry out the availability check for the product in another location or
else for an alternative product.
??Integration between sales and distribution and production : You can also define that the sales
order triggers production directly if a product is not available. If it triggers an order for in-house
production, APO creates a planned order for the desired quantity in PP/DS (Production Planning &
Detailed Scheduling).
??In addition, component availability can be checked (multi-level components and capacity check).
??Check against aggregated data: Planned orders and production orders are aggregrated and
represented in a time series, which can be used to evaluate the incoming requests from the sales
orders. This means that better system performance is then available.
R/3 APO
? SAP AG 2001
??Global ATP is embedded in Supply Chain Management (SCM) processes for any kind of order
processing.
??Availability
checks are triggered as events in the OLTP system - either R/3 or legacy systems - and
an ATP request for product availability is sent over to APO.
??An Available-To-Promise (ATP) check is an online search to verify the company's ability to provide
the requested product, in the requested quantity, and on the date requested by the customer.
??In many OLTP systems, ATP functionality is limited or not possible at all. In older versions of R/3,
an ATP check searched local inventories only for available products and assumed infinite capacity
when a product had to be produced. For this reason, ATP checks are carried out in APO on the basis
of time series, either in real-time or in simulation mode.
??When it comes to production, ATP makes use of PP/DS (Production Planning and Detailed
Scheduling) functionality to check against the actual order network including all constraints.
??Applying rules-based ATP is the basis for checks of alternative products in alternative locations as
well as for production.
Receipts
Further sales-
Time
related Reservation
Reservation
requirements
requirements
Issues
? SAP AG 2001
??In accordance with ATP settings in APO, you can take into account various stock, requirements and
receipts in the availability check. You can define which requirements and receipts to use as a basis
for a sales order confirmation that you want to give the customer.
??The scope of check is configured in APO Customizing.
? SAP AG 2001
??The data sent from the OLTP system is aggregated and represented in a time series consisting of the
corresponding ATP objects that are then used to evaluate the incoming ATP requests.
??The time series display (see picture above) shows the receipt elements above the line. The issue
elements are below the line.
??If the stock is zero or negative, a new order can only be confirmed for a later date.
??To differentiate between the various levels of probability with which a specific product will be in
stock in the future, there is a time series for each type of ATP category.
??Examples of ATP categories: firm planned order, consignment stock, released production order.
??To improve your system performance, ATP gives you the option to aggregate orders by reorganizing
time series'. All receipts and issues within one period are cumulated. The ATP check checks against
these aggregated quantities.
??ATP performance is reduced if you process incoming orders in individual checks.
End item of
sales order
Problem:
PPM explosion Insufficient number of pieces in stock
Possible solution:
Step 1: Alternative product
Step 2: Procurement from another location
Step 3: Production (PPM explosion)
e
tiv
rna t(s) Alternative location(s)
te c
Al odu
pr
? SAP AG 2001
??Rules-based availability checking is an iterative process. The rules stored in the system determine the
next checking step in each case.
??Possible next steps are as follows:
??Substitution (alternative product)
??Sourcing (alternative location)
??Capable-To-Promise (triggering production = creating an order)
??All of these span the three-dimensional space shown in the picture.
??The search stops when an acceptable result is provided by the check (if any number of substitution
steps is permitted).
??In the rule strategy settings, however, only one substitution can be selected. In this case the system
completes the rule evaluation. Without customer -specific coding (= customer exit) the system
chooses the first result that covers the requirement completely. By activating the customer exit you
can decide which selection is appropriate and if a dialog should be displayed. Only one result is
permitted.
??The rule strategy forms the actual rule-base for a specific check. In the simplest case, this search
strategy defines the sequence in which the system reads the individual rules.
??Each access of this sequence is performed using a combination of characteristics. When an order is
to be checked, the characteristics of the order are passed over to APO from the OLTP system.
??You can thereby define, for example, that sales orders for different sales organizations, sold-to
parties, and so on, are checked using different ATP rules. Depending on these values, the
corresponding rule is evaluated.
Sales order
Sales
Sales order
order
Production
Production Planning/
Planning/
Detailed Scheduling
Planned order
Planned
Planned order
order
? SAP AG 2001
??In the R/3-APO interface, you can specify in the integration model that the availability check (ATP
check) in the sales order is not to be performed in R/3, but rather in APO (Availability check
indicator). If you create a sales order in the R/3 System, the system first checks whether there is
enough stock available for this product. It can also check whether receipts (such as production orders
or planned orders) are scheduled before the desired date.
??For non-availability, you can specify in APO that the system is to perform an availability check for
the product in a different location or for an alternative product. Furthermore, if a product is not
available, you can define that the sales order can trigger production directly. In this case, it triggers
an order for in-house production and APO creates a planned order for the desired quantity in PP/DS.
All of the operations of the PPM are scheduled at the resources of the PPM, and the system takes the
capacity restrictions into account (available capacity and orders that may have already been
scheduled). In addition, the availability of the components can be checked (Automatic planning
indicator in the product master of the components). If the capacities are already exhausted on the
desired date, the system uses simultaneous material and capacity requirements planning to find a date
on which the planned order can be created.
??The availability date of the newly created planned order (finish date) is passed back to the R/3 sales
order and copied as the internal confirmation date. Delivery scheduling is used to determine the date
in the sales order on which the customer can receive the product. The sales employee can find this
delivery date in the R/3 sales order. When you confirm this proposed date in the sales order and save
it, the APO planned order, which was only simulated, is transferred back to R/3 and is visible there.
Resource availability
Sales order
Available 1st Loading attempt
Desired date Confirmed
Occupied Final loading and quantity qty/date
30
Resource 3 (finite) 30
20 20
Resource 2 (finite)
10
Resource 1 (finite)
10
Time
Today
? SAP AG 2001
??If a product is not available, the sales order can trigger production directly: If it triggers an order for
in-house production, APO creates a planned order for the desired quantity in PP/DS. All of the
operations of the PPM are scheduled at the resources of the PPM, and the system takes the capacity
restrictions into account (available capacity and orders that may have already been scheduled).
If the capacities are already exhausted on the desired date, the system uses simultaneous material and
capacity requirements planning to find a date on which the planned order can be created. You use the
strategy profile to define how the system is to schedule (search for a slot, infinite planning ...).
??Prerequisite:
??In the "rules-based availability check", define that production is to be triggered directly for non-
availability (this function can be used in connection with all requirements strategies in planning).
??Maintain the strategy profile with which you want to trigger the scheduling of planned orders from
the ATP integration and maintain them under Global Settings in Customizing for PP/DS, in the
Strategy profile for ATP integration field. The default strategy profile in the delivery system is
SAP001 (search for a slot backward).
??You define in APO how the availability of a sales order is checked in APO (for example, checking
against stock, checking against forecasting, checking against allocation, or checking using rules -
based ATP (also checking against alternative products/locations or triggering production from the
sales order). Here, depending on the R/3 requirements class and the business event (for example,
A = sales order, AE = make-to-order sales order, B = delivery), you can define which check if any
should be performed (check against stock, against forecasting, against allocation or rules-based
ATP). If you use rules -based ATP, the corresponding rules are selected according to material,
sales organization, sold-to party, plant, etc (condition technique).
? SAP AG 2001
??Product allocation functionality allows you to manage the supply of scarce products to customers, so
that each customer receives an allocated amount.
??Product allocations are applied to a product allocation object. The product allocation object is the
reason for allocating quantities. It could be any one of the following:
??A product (personal computer) or a product group
??A component (processor)
??A season (summer, winter)
??A production line
??The reason for product allocations may vary in different phases of the product life cycle.
??Backorder processing is one of the new availability check tools that enables you to analyze and edit
backorders and to overwrite confirmed quantities as the result of the previous ATP check. You can
redistribute the confirmed quantities of one or more products via selected customer requirements.
??Backorder processing can be executed
??In interactive mode
??In batch mode (including simulation)
??As a combination of both
??The orders to be processed are determined via a filter that is to be defined. This filter definition can
be configured by the user or you can use the standard filters provided by SAP, which filter according
to locations in which the planning situation has changed (netchange filter). They must be taken into
account again within backorder processing.
??After the orders have been selected once via the filter, they can be sorted via specific configurable
criteria.
??The orders whose delivery date now lies in the past can be scheduled in the future, if desired.
? SAP AG 2001
1-1 Create a sales order in R/3 and perform the ATP check.
Save the order. The order is transferred directly to APO after saving in R/3.
In the APO system, check the planning situation for the product T-F2## (pump) in
the locations 2400 (Milan), 2500 (Rotterdam) and 2300 (Barcelona).
1-1 Create a sales order in R/3 and perform the ATP check.
Press Enter
Save the order. The order is transferred directly to APO after saving in R/3.
Then check the planning situation in the locations 2500 and 2300.
Contents:
? ASAP SCM Implementation Philosophy
? ASAP SCM Methodology
? Objectives
? Deliverables
? Tools
? ASAP for APO
? SAP AG 2001
? SAP AG 2001
1 Course Overview
22 Integration and Technology
33 Modelling and Evaluation in APO
4 Demand Planning
55 Supply Network Planning
Production Planning/Detailed
6 Scheduling
7 Transportation Planning
88 Global Available-to-Promise
99 APO SCM Implementation 9
10
10 Conclusion
? SAP AG 2001
A supply-chain diagnostics
approach that will enable SAP to
evaluate a customer's supply
chain, identify significant issues,
estimate benefits that APO could
deliver, and develop a tailored
implementation plan that enables
customers to realize these benefits
in a short period of time
? SAP AG 2001
APO
7
8 GoLive
& Support
9
1 0 8
9
Analytical
1 0
process flows
tools
APO activity R/3 Value
matrix Questionnaires analysis
& surveys
? SAP AG 2001
P
1
P 1 P 1
D
3
ACME P
2 P 3 P
4 P
2 P
4 P 2
Taiwan
D
2 S
1 D
2 S
1 M
4 D
1 S
1 D
1 S
1 D 1
Manufacturer
Semiconductor SemiconductorL
Distributor A aCp M
t oEp Laptop
ACME A aCp M
L t oEp Distributor
Laptop Laeptatoilepr
R
Production Production (SanJose)
Distribution
(SanJose) (SanJose)
Supplier’s Customer’s
Supplier Customers ACME Customers Customer
Processes
People
Innovation
Learning
Opportunities Strategy
Products
Industry Practices
Implementations
Non-R/3 R/3 NonR/3 R/3
? SAP AG 2001
? SAP AG 2001
? SAP AG 2001
? Strategic blueprint
? Case studies
? Question & Answer database (QAdb)
? Process description
? Questionnaires
? Roadmap / project plan
? SAP AG 2001
? SAP AG 2001
? SAP AG 2001
? SAP AG 2001
? SAP AG 2001
1 Course Overview
22 Integration and Technology
3 Supply Chain Cockpit
4 Demand Planning
55 Supply Network Planning
Production Planning /
6 Detailed Scheduling
7 Deployment
88 Transportation Planning
99 Global Available-to-Promise
10
10 Conclusion 10
? SAP AG 2001
? SAP AG
AG 2001
Planning Horizon
Demand Planning (DP)
Deployment
? SAP AG 2001
Location
Aggregated actual data Future demand
Product hierarchy forecast
Sold-to party
Sales organization
Region
? Incoming orders
? Statistical forecasting
? Quantities BW
? Values ? Collaborative forecasting
R/3 ? Promotions
? Billing document
Excel
? Quantities
? Values Non-SAP system
? …
? SAP AG 2001
??The APO DP library of statistical forecasting and advanced macro techniques allows you to create
forecasts based on sales history as well as any number of causal factors, and use a consensus -based
approach to consolidate the results.
??Marketing intelligence and management adjustments can be added by using forecast overrides and
promotions.
??Aggregated actual data can be extracted from the R/3 system in exactly the same way as it can be
imported from BW, Excel, and legacy systems.
Demand Plan
Supplier Plant DC
Customer
? SAP AG 2001
Production Planning /
Supply Network Planning
Detailed Scheduling
? PP/DS planned orders ? SNP planned orders
? Purchase requisitions ? Purchase requisitions
Production Time
horizon
? SAP AG 2001
? SAP AG 2001
??Production Planning and Detailed Scheduling (PP/DS) is used mainly for short-term to-the-
minute planning (both for in-house production and external procurement) in the production plant.
PP/DS schedules and plans all oper ations of an order that are relevant for planning at the different
resources. PP/DS has the following functions:
??It generates planned orders (to plan in-house production), and purchase requisitions or scheduling
agreement schedule lines (to plan external procurement) in the event of product shortage. It uses
simultaneous material and capacity requirements planning to do this: You can define
resources as “finite” resources (planning-critical resources) in the resource master. Order
operations are only created at these resources if there is sufficient capacity for the order quantity
on the corresponding date. When there is no available capacity, the system searches for a date on
which the order operation can be carried out, taking account of the capacity situation.
??Takes order sequences into account: when new in-house production orders are created, the setup
times in the new order can be determined automatically from the setup status of the resources
(depending on the preceding order).
??It is possible to display the orders in graphic format (in the detailed scheduling planning board),
and to sequence from there. Alternatively you can use the optimizer to execute a sequencing.
??Machine scheduling optimization: during planning, it is possible for orders to be generated that
do not have an optimum order sequence. Therefore, you can change the sequence and resource
assignments of existing orders using the optimization run.
??PP/DS is a planning tool. Execution functions such as confirmations and goods receipts are
performed in the execution system (for example, R/3). Therefore, the planning results are transferred
to the execution system.
Sales orders,
stock transfers,
forecasts
Goal:
Deliveries and
transportation orders in R/3
Simultaneous route
and load/weight Optimizer
planning
TLB orders
Express orders Vehicle
resources
Selection of
transportation provider
? SAP AG 2001
Sales order
? SAP AG 2001
??Event-driven: In the R/3 APO interface you can define that the ATP check in the sales order should
not be carried out in R/3 but in APO, as soon as a sales order is created. If you create a sales order in
R/3, the system first checks if there is enough stock available for the requested product. The system
can also check if receipts (for example, production orders and planned orders) have already been
planned by the requested date.
??Time series: Planned orders and production orders are aggregrated and represented in a time series,
which can be used to evaluate the incoming requests from the sales orders.
??Rules-based ATP: When there is no availability, you can configure in APO that the system should
carry out the availability check for the product in another location or else for an alternative product.
??Integration with PP/DS : You can also define that the sales order should trigger production directly
if a product is not available. If it triggers an order for in-house production, APO creates a planned
order for the desired quantity in PP/DS. All of the operations are scheduled on the resources, and the
system takes the capacity restrictions into account (available capacity and orders that may have
already been scheduled). In addition, component availability can be checked. If the capacities are
already exhausted on the desired date, the system uses simultaneous material and capacity
requirements planning to find a date on which the planned order can be created.
The availability date of the newly-created planned order (end date) is returned to the R/3 sales order
and adopted as an internal confirmation date. Using shipment scheduling, the date on which the
product reaches the customer is determined in the sales order. In the R/3 sales order the sales
employee recognizes these proposed delivery dates.