SCM670 Global Available to Promise GlobalATP

SCM670 Global Available-toPromise (Global ATP) SCM670

Release 640 04/06/2006

0 SCM670 Global Available-to-Promise (Global ATP)

SCM670

Global Available-to-Promise (Global ATP)

THE BEST-RUN BUSINESSES RUN SAP SAP AG 2003  SAP AG©2003  SAP AG

  

System – SAP R/3 Enterprise 2003/Q4 Material number 50062901

0.2 Copyright

Copyright 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

 SAP AG 2004

  

       



Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and

SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

0.3 Course Prerequisites

Required:  SCM600 Processes in Sales and Distribution Recommended:  SCM605 Sales  SCM200 Supply Chain Planning Overview  SCM210 Master Data Integration

 SAP AG 2003

0.4 Target Group

Participants  Project team members responsible for implementing the SAP APO component Global Available-to-Promise (Global ATP)

Duration  3 days

 SAP AG 2003



The training materials are not teach-yourself programs. They complement the course instructor's explanations. Your materials include space for noting down any additional information.



There may not be sufficient time during the course to complete all the exercises. The exercises are intended to be additional examples that are dealt with during the course. Participants can also use them to deepen their knowledge after the course.

1 Course Overview

Contents:  Course goals  Course objectives  Course content  Global ATP within Supply Chain Management

 SAP AG 2003

(C) SAP AG

SCM670

1

1.2 Course Goals This course will prepare you to:  Make reliable delivery commitments using Global ATP, transportation and shipment scheduling, the simulation methods, and backorder processing  Describe the integration of Global ATP with online transaction processing (OLTP) system environments  Explain and configure the basic and advanced Global ATP methods  Utilize the simulation function in Global ATP  Set up and execute backorder processing  Explain and set up transportation and shipment scheduling

 SAP AG 2003

(C) SAP AG

SCM670

2

1.3 Course Overview: Objectives

At the conclusion of this unit, you will be able to:  Summarize the characteristics and functions of Global ATP, define ATP concepts, list the benefits of ATP, and illustrate applications of ATP in SAP APO  Explain the basic architecture of Global ATP in SAP APO and describe the OLTP integration scenario  Describe the various basic and advanced check methods and recognize the need for the large variety of availability checks in Supply Chain Management

 SAP AG 2003

(C) SAP AG

SCM670

3

1.4 Course Content

Preface Unit 1

Course Overview

Unit 6

Unit 2

Global ATP / OLTP Interface

Rules-Based Availability Check

Unit 7

Check Method Selection

Production Within the ATP Check

Unit 8

Backorder Processing

Unit 9

Scheduling

Unit 3 Unit 4

Product Availability Check

Unit 5

Check Against Product Allocations Appendix

 SAP AG 2003

(C) SAP AG

SCM670

4

1.5 Course Overview Diagram

1

Course Overview 2 2

Global ATP / OLTP Interface 3 3

Check Method Selection 4

Product Availability Check

5 Check Against Product Allocations 6 7 8 9

Rules-Based Availability Check Production Within the ATP Check

Backorder Processing

Scheduling

 SAP AG 2003

(C) SAP AG

SCM670

5

1.6 Business Scenario

 Maxitec Ltd. is a manufacturer of personal computer products and pumps. The company intends to implement SAP APO to significantly improve the accuracy of its responses to customers with regard to product availability during sales order processing.  Insufficient stock in individual distribution centers makes the company consider other availability check options in addition to checking plant stock: for example, delivering from other locations, providing product upgrades, or manufacturing the product.

 SAP AG 2003  SAP AG

(C) SAP AG

SCM670

6

1.7 Business Scenario (2)

 Their goal is to improve global customer response and delivery performance by providing reliable dates for the supply chain plans from DP, SNP, and PP/DS. Furthermore, some products face restrictions caused by seasonal demand fluctuation and therefore require customer-based and region-based checks against product allocations.  To allow Maxitec Ltd. to make sales commitments in its operative system, it needs monitoring tools and decision support methods.  The company operates with different OLTP source systems and requires global checks.

 SAP AG 2003

(C) SAP AG

SCM670

7

1.8 Global Available-to-Promise (Global ATP)

Make ATP ATP request request

+20 -10

Sales

Confirmation Confirmation +10

 Global, cross-location, real-time ATP check  Basic methods  Advanced methods:  Combinations of basic methods  Rules-based availability check  Capable-to-Promise (CTP)  Multilevel ATP check  Integration of legacy systems

 SAP AG 2003

  

 

Availability checks are triggered by events in the OLTP system – either the SAP R/3 system or a legacy system – and an ATP request is sent to SAP APO for all SAP APO-relevant products in the order. An ATP check is an online search used for verifying that the requested product can be provided by the company in the quantity requested and on the date requested by the customer. In many OLTP systems, ATP-specific functions are limited or nonexistent. ATP functions as previously known from SAP R/3 allowed product selection and single manual substitution at plant level (one item during the ATP check). Infinite capacity usually had to be assumed in assembly order processing. A capacity check was only possible when manufacturing orders or manufacturing order networks were generated directly. The ATP check uses PP/DS functions for production. By applying rules-based ATP, it is possible to check for alternative products in alternative locations, as well as to consider production across all product levels.

(C) SAP AG

SCM670

8

1.9 Possible Documents for Global ATP in SAP APO

It is possible to use the following documents for Global ATP:  SD documents (for example, sales order, delivery)  Stock transfers (stock transport requisitions, in-plant stock transfer reservations)  Component check (production order, planned order, subcontract procurement processing ...)  Inventory Management (goods issue check MM, reservation)

 SAP AG 2003

(C) SAP AG

SCM670

9

1.10 Global ATP in Supply Chain Management  Immediate delivery commitment response to customer  Decision support for complex order processing with conflicting delivery commitments  Highly integrated with: 

Demand Planning ⇒ Forecast consumption / evaluation



Supply Network Planning ⇒ Distribution & production networks



Production Planning / Detailed Scheduling ⇒ Current and future production plans



OLTP ⇒ Sales orders and Inventory Management

 SAP AG 2003

Global ATP in SAP APO provides information on product availability from the entire supply network. The likelihood of making a successful commitment and of having short delivery processing times varies depending on the check method used.  Global ATP is highly integrated in all SAP APO application components, thus ensuring that the ATP check requirements are fulfilled. This integration can include the following:  Demand Planning forecasts can be used as a basis for checks against sales orders when no supply plan exists, such as in a make-to-order environment.  Supply network plans can be examined at alternative distribution centers and plants, with the option of checking for alternative products.  Production Planning and Detailed Scheduling (PP/DS) plans can be examined for detailed production plans, and automatic planning can check if an additional production plan can be scheduled for the requirement. 

(C) SAP AG

SCM670

10

1.11 ATP Embedded in SAP APO Architecture SAP Advanced Planning and Optimization SC Cockpit & Network Design

ATP

APO Database (BW techniques available)

Demand Planning (uses BW)

Supply Network Planning

Production Planning & Detailed Scheduling

SAP liveCache

Transport. Planning & Vehicle Scheduling

APO Optimizers

Queued RFC (tRFC)

BAPI

Mapping, Connectivity

Business Application Progr. Interface

SAP R/3

SAP BW

Legacy OLTP

Non-R/3 OLTP

Non-R/3 OLTP

 SAP AG 2003

(C) SAP AG

SCM670

11

1.12 Basic Method: Product Availability Check SAP APO

SAP R/3 Enterprise

Check product Y in location ‘Plant Hamburg’ (plant 1000) Receipts

SD: Sales order Item 10: Material X Item 20: Material Y

Time Issues

Local ATP server: Check Check material X in plant plant 1000  SAP AG 2003

The example shows a sales order consisting of two items:  Material X is a non-APO material and is therefore checked locally.  Material Y (in SAP R/3) is checked as product Y in the corresponding location using time series in SAP APO.  Time series include all selected types of stock and all receipts and issues selected for the actual check. Therefore, time series represent planned stock and scheduled supply orders at any point on the time axis. Using time series, ATP calculates if the new order can or cannot be confirmed for the requested date.  A local ATP server is recommended for the availability check of large data quantities in SAP R/3 (see SAP Note 99999). 

(C) SAP AG

SCM670

12

1.13 Advanced Method: Product Availability Check + Check Against Product Allocations November

December

Incoming sales order 1000 t 750 t 500 t 250 t First delivery

Second delivery Time

Product allocation check Availability check 750 tons are available. However, only 500 tons are allocated to this customer in the November period.  SAP AG 2003

The example shows an advanced method:  Step 1: Product availability check  Step 2: Check against product allocations (the check against product allocations is also referred to simply as "product allocation“)  The stock level of 250 tons in the December period is the remainder of the previous total stock of 750 tons after 500 tons have been promised to the customer (product allocation). In total, 750 tons are delivered in two parts. 

(C) SAP AG

SCM670

13

1.14 Advanced Method: Rules-Based ATP

Alternative PPM explosion

Finished product from sales order

e tiv ) a rn t(s te uc l A od pr

Problem: Insufficient stock quantity

Possible solution: Step 1: Alternative product Step 2: Procurement from different location Step 3: Production with alternative PPM

Alternative location(s)

 SAP AG 2003

Rules-based availability checking is an iterative process. Rules stored in the system determine the next checking step in each case.  Possible subsequent checking steps include:  Substitution (alternative product)  Sourcing (alternative location)  If production is called within the rules-based availability check, alternative production process models (PPMs) can be checked. 

(C) SAP AG

SCM670

14

1.15 Advanced Method: Capable-to-Promise (CTP) Sales order R/3

APO

Confirmation SD SD

ATP request

ATP ATP No ATP

Planned orders

Planned orders

MRP

Make

Production Production Planning/ Planning/ Detailed Scheduling Scheduling Update time series

 SAP AG 2003

If a product is not available and there is not enough planned stock, Global ATP can trigger production directly.  Global ATP calls a corresponding method for order entry in PP/DS. This schedules an order for the requested quantity on all resources in the PPM, taking into account the free capacity. It also checks the availability of products in the bill of material.  The result is transferred to ATP, which updates the sales order after confirming the delivery proposal. SAP APO uses this confirmation to update the ATP time series. PP/DS sends the simulated planned orders to the SAP R/3 system, where an additional planning run explodes the non-SAP APO materials of the SAP R/3 bill of material (BOM), if required. 

(C) SAP AG

SCM670

15

1.16 Backorder Processing

Backorder items

 The order order item item is is not confirmed confirmed in in full full  The requested requested delivery date for an an order item item is is not not confirmed confirmed  There There are are overconfirmations

Backorder processing

 SAP AG 2003

Backorder processing is an availability check tool that allows you to diagnose backorders and overwrite the committed quantity that resulted from the last availability check. You can redistribute the confirmed quantity for one or several products over selected customer requirements.  You can perform backorder processing:  Interactively  In the background (batch mode) – including simulation  As a combination of interactive backorder processing and backorder processing in the background 

(C) SAP AG

SCM670

16

1.17 Course Overview: Summary

You are now able to:  Summarize the characteristics and functions of Global ATP, define ATP concepts, list the benefits of ATP, and illustrate applications of ATP in SAP APO  Explain the basic architecture of Global ATP in SAP APO and describe the OLTP integration scenario  Describe the various basic and advanced check methods and recognize the need for the large variety of availability checks in Supply Chain Management

 SAP AG 2003

(C) SAP AG

SCM670

17

2 Global ATP / OLTP Interface

Contents:  Basic concepts of the SAP APO Core Interface  Data transfer using integration models  Specific data channels for Global ATP

 SAP AG 2003

(C) SAP AG

SCM670

1

2.2 Global ATP / OLTP Interface: Objectives

At the conclusion of this unit, you will be able to:  Explain the basic interface functions between Global ATP and the OLTP systems  Determine source and target systems within complex system environments  Guarantee a data supply to the SAP APO system by transferring master and transaction data from the OLTP systems  Return planning results from the SAP APO system to the OLTP systems

 SAP AG 2003

(C) SAP AG

SCM670

2

2.3 Global ATP / OLTP Interface: Course Overview Diagram 1

Course Overview 2 2

Global ATP / OLTP Interface 3 3

Check Method Selection 4

Product Availability Check

5 Check Against Product Allocations 6 7 8 9

Rules-Based Availability Check Production Within the ATP Check

Backorder Processing

Scheduling

 SAP AG 2003

(C) SAP AG

SCM670

3

2.4 Global ATP / OLTP Interface: Business Scenario

 Maxitec Ltd. intends to use ATP in an integrated, networked system. Their ATP system uses execution data from OLTP systems (such as SAP R/3) and other legacy systems as a basis for planning.  The company will use the numerous interface functions to initially load data about products, locations, routings, BOMs, and current orders from the OLTP systems into SAP APO.  The planning data in both SAP APO and the OLTP systems must be synchronized.

 SAP AG 2003

(C) SAP AG

SCM670

4

2.5 Interface Scenario

SAP R/3 Non-R/3 System

LO

SD HR

BAPI

Plug-In with CIF

BAPI

(Core Interface)

BAPIs

SAP APO BAPI

 SAP AG 2003



You have to distinguish between two main integration concepts:  Integration of SAP R/3 >= 3.1I through the SAP APO Core Interface (as part of SAP R/3 Plug-In)  Integration of any type of OLTP legacy system (also SAP R/3 < 3.1I and SAP R/2) through Business Application Programming Interfaces (BAPIs).

(C) SAP AG

SCM670

5

2.6 Global ATP in a Multisystem Environment OLTP

Global APO Server CIF

R/3 4.5 B

SCC

SAP liveCache

DP SNP PP/DS Global ATP

CIF

R/3 Enterprise R/3 4.6 B/C

Local ATP Server

Data Objects CIF

R/3 4.0 B

BAPI

BAPI

Legacy

Third Party

BAPI

CIF

CIF

R/3 3.1 I

BAPI

R/2 CRM

 SAP AG 2003

The SAP APO Core Interface (APO CIF) is a standardized interface solution that enables you to integrate SAP APO with the SAP R/3 release levels shown above. As an SAP R/3 add-on, APO CIF is part of the SAP R/3 Plug-In that interconnects all mySAP.com components with SAP R/3.  The setup and utilization of distributed applications is based on ALE technology. The basic concept of Application Link Enabling (ALE) is the guarantee of a distributed but integrated SAP installation. 

(C) SAP AG

SCM670

6

2.7 Connection Between SAP R/3 and SAP APO SAP R/3

•• •• ••

SAP APO

Customizing Customizing Master Master data data Transaction Transaction data data

Plug-In Plug Plug-In

CIF Selectionand extraction of data

Remote FunctionCall (RFC) Publish

•• Customizing Customizing •• Master Master data data •• Transaction Transaction data data

 SAP AG 2003



An SAP R/3 system and an SAP APO system are connected by an RFC connection (RFC = Remote Function Call). Data selected by APO CIF is transferred through this connection.

(C) SAP AG

SCM670

7

2.8 Business System Group BSG 1

R/3

BSG 2

R/3 Mat. No. A

APO

Mat. No. A

Mat. No. ? Customer Exit Customer Exit

R/3

BSG 3

Mat. No. 4711

 SAP AG 2003

Several SAP R/3 systems can be connected with an SAP APO system. Some products are planned in the SAP R/3 systems under different material numbers. There are two scenarios:  An identical material number in two different SAP R/3 systems describes two different materials.  Two different material numbers in two SAP R/3 systems describe the same material.  This means that the SAP R/3 material numbers cannot simply be transferred to the SAP APO system, because they are not unique.  To guarantee a unique naming environment for master data in distributed system landscapes, business system groups are defined as areas with the same naming convention.  The material numbers are converted by means of a customer exit between the business system groups.  

(C) SAP AG

SCM670

8

2.9 Data Transfer: Integration Model Master data = Factory model Transaction data = Business transaction

Generate Activate Change

Integration model 2: • Orders (per type)

Integration model 1: • Products • Components • Work centers • Routings • Bills of material

Set up selection variants

Consistency check

 SAP AG 2003



  





An integration model gathers all data (filter objects) to be transferred in one chunk from SAP R/3 to SAP APO. The integration model has a name and is related to a target system. You can use selection variants to define relevant objects for the different planning processes in SAP APO. You start the data transfer by activating the generated integration model. Master data is broken down into subcategories like work center, bill(s) of material, routings, and so on. Filter objects in existing integration models can be added / excluded. To achieve maximum flexibility and performance for the data transfer, you can generate as many integration models as necessary and then activate them. The number of data objects to be included in the transfer is restricted to the various planning and optimizing operations. You can create more than one version for an integration model, but only one can be active at a time. Interface extension with Plug-In  The interface extension allows the transfer of non-standard data from SAP R/3 to SAP APO and vice versa.  Originally developed for industry solutions, the interface extension also allows special data to be transferred from a standard SAP R/3 system.  The extensions are realized by customer exits and BAPIs. The integration model is used for both the initial data transfer and the change transfer.

(C) SAP AG

SCM670

9

2.10 CIF Technology: Integration Model

Data channels relevant for Global ATP  To use the entire scope of Global ATP in SAP APO, you must set up the following data channels in the Core Interface on the SAP R/3 side: 

ATP check



ATP Customizing



Customizing for product allocation



Product allocations

 SAP AG 2003



For detailed information, see the integration scenarios for ATP. Integration scenarios are part of the SAP APO online documentation.

(C) SAP AG

SCM670

10

2.11 CIF Technology: Integration Model (2)

Meaning of ATP-relevant checkboxes in the integration model  ATP check By selecting the ATP check and selecting the materials and plants, you determine that the availability check is performed for these material/plant combinations.  ATP Customizing The setup of the data channel for ATP Customizing allows the Customizing settings to be transferred to SAP APO. The settings are transferred with the initial data transfer from SAP R/3 to SAP APO.

 SAP AG 2003



In the global settings for ATP in the SAP APO system, you can prohibit the import of Customizing data. This may be necessary if you have to transfer (activate) an integration model for the second time (for example, if there are master data changes) and you do not want to destroy the existing setup of Customizing data in SAP APO.

(C) SAP AG

SCM670

11

2.12 CIF Technology: Integration Model (3) Meaning of ATP-relevant checkboxes in the integration model for product allocation  Customizing for product allocation

This is for setting up a data channel for Customizing data related to the product allocation procedure (relevant if maintained in the SAP R/3 system).  Product allocations

This is for setting up a data channel for the check against product allocations (if maintained in the SAP R/3 system). Note: You can prevent the SAP APO system from importing Customizing data from the connected OLTP system via the integration model (SAP APO Customizing -> Global Available-to-Promise (Global ATP) -> Global Settings)  SAP AG 2003



Customizing for the check against product allocations is handled differently than “normal” ATP Customizing:  Selecting the relevant checkboxes only opens the channels.  You still have to manually start the transactions.  Reason: If you have a longer planning cycle in SAP R/3, you can determine individually when you want to send the relevant information to SAP APO, without deactivating the integration model in urgent cases.



Customizing for the check against product allocations The actual Customizing data for product allocation has to be transferred separately by using the transaction QTSP. The individual product allocation procedure is transferred together with the material master.



Product allocations Data for product allocation has to be transferred separately using the transaction QTSA.



You can protect the SAP APO system from a Customizing import by maintaining the relevant global settings.

(C) SAP AG

SCM670

12

2.13 Notes: Locking Within Rules-Based ATP  For consistent results, you need to activate the quantity lock in SAP R/3 (checking group).  The Customizing parameter for temporary quantity assignments should always be set in SAP APO. SAP SAP R/3 R/3 Customizing Customizing -> Sales Sales and and Distribution  Basic Functions Functions -> Availability Availability Check Check and Transfer of of Requirements Requirements -> Availability Availability Check Check -> Availability Availability Check Check with ATP ATP Logic Logic or or Against Against Planning -> Define Define Checking Checking Groups

SAP APO Customizing -> -> Global Available-to-Promise (Global ATP)  General Settings -> -> Maintain Global Settings for Availability Check

 SAP AG 2003

(C) SAP AG

SCM670

13

2.14 Master and Transaction Data in SAP R/3 and SAP APO OLTP

APO

SAP liveCache

Planned order

Order (planned)

Sales order

Order (sales)

•

Time series and order network update

• •

Production order

Order (production)

Material master

Product master

Plant

Location

Routing, BOM

Production process model

Info structure

Product allocation group

 SAP AG 2003





  

Using various Customizing steps, a reciprocal system connection is set up that enables data relevant to the planning process to be transferred from the executing SAP R/3 system to SAP APO, and the results of the planning process to be returned to SAP R/3. A sales order created in the SAP R/3 system is transferred to SAP APO and modeled in the appropriate time series. Procurement, stock transfer, and planned orders created in SAP APO are passed back to the OLTP system as corresponding planned orders. Planned orders can be converted into production orders in SAP APO. Production orders are always confirmed in the OLTP system (execution function). Information from the OLTP material master is passed to the SAP APO product master. Information from the OLTP plant is mapped in SAP APO by the location. SAP R/3 routings and BOMs are linked to SAP APO through the production process model. The SAP R/3 info structure corresponds to the product allocation group in SAP APO and can be transferred from SAP R/3 to SAP APO.

(C) SAP AG

SCM670

14

2.15 Global ATP / OLTP Interface: Summary

You are now able to:  Explain the basic interface functions between Global ATP and the OLTP systems  Determine source and target systems within complex system environments  Guarantee a data supply to the SAP APO system by transferring master and transaction data from the OLTP systems  Return planning results from the SAP APO system to the OLTP systems

 SAP AG 2003

(C) SAP AG

SCM670

15

3 Check Method Selection

Contents:  The check instructions 

Selection of a basic method



Selection of an advanced availability check method

 The business event  The check mode  Determination of the check mode from the requirements class (SAP R/3)

 SAP AG 2003

(C) SAP AG

SCM670

1

3.2 Check Method Selection: Objectives

At the conclusion of this unit, you will be able to:  Explain the basic concepts of the basic availability check methods  Explain the basic concepts of the advanced availability check methods  Determine the selection of the check method  Explain the significance and determination of the check mode and business event

 SAP AG 2003

(C) SAP AG

SCM670

2

3.3 Check Method Selection: Course Overview Diagram 1

Course Overview 2 2

Global ATP / OLTP Interface 3 3

Check Method Selection 4

Product Availability Check

5 Check Against Product Allocations 6 7 8 9

Rules-Based Availability Check Production Within the ATP Check

Backorder Processing

Scheduling

 SAP AG 2003

(C) SAP AG

SCM670

3

3.4 Check Method Selection: Business Scenario

 Maxitec Ltd.'s product spectrum and business processes are heterogeneous. The demands on the availability check therefore vary, depending on the product and possibly the transaction.  Maxitec Ltd. decides to use various availability check methods.

 SAP AG 2003

(C) SAP AG

SCM670

4

3.5 Basic Methods of the Availability Check

Product availability check

Check against product allocations

?

Obj ect

Check against the forecast

 SAP AG 2003

Product availability check or availability check based on ATP quantities:  The ATP (Available-to-Promise) quantity is calculated from warehouse stock, planned receipts (production orders, purchase orders, planned orders, and so on), and planned issues (sales orders, deliveries, reservations, and so on). For this type of availability check, the system dynamically checks stock and planned goods movements for each transaction – either with or without using the replenishment lead time. Planned independent requirements are not taken into account.  Availability check against product allocations:  You can allocate materials using any criteria. The availability check is successful if there is a product allocation for this transaction in the relevant period and this product allocation has not yet been consumed by other requirements. The check against product allocations is used in situations where supply is smaller than demand to prevent one customer (or a few customers) from buying the complete quantity and other requirements not being satisfied.  Availability check against the forecast:  In the check against the forecast, the system checks against a planned independent requirement created for an anonymous market, which is usually not customer-specific (for example, in the strategy planning without final assembly, if production is only carried out to the stocking level). The planned independent requirement results from demand management and is used for non-order-specific planning of expected future sales quantities. 

(C) SAP AG

SCM670

5

3.6 Advanced Availability Check Methods Production (CTP or MATP) Rules-based availability check Combination of basic methods 1.

?

2. Obj ect

3.

Combination of basic methods, rules, and/or production

1. 2. Obj ect

3.  SAP AG 2003



The advanced availability check methods include:  The combination of basic methods For example, first, you can execute a check against product allocations. You then check the resulting confirmed quantities against the relevant ATP quantity within the product availability check.  Production (Capable-to-Promise) CTP means calling Production Planning and Detailed Scheduling (PP/DS) directly during an ATP check. You can set that PP/DS is called when the requested product is not completely available, in order to produce the remaining quantity or to procure it externally. Unlike in the multilevel ATP check (MATP), PP/DS planned orders or purchase requisitions, which are visible and are taken into account in planning, always result immediately during the CTP process. A feasible planned order is determined in PP/DS from the result of scheduling these planned orders (taking capacities and the product availability into account). A confirmation can then be made against this planned order.  Production (multilevel ATP check) The multilevel ATP check is used in production processes where a large part of the value-added activity arises at final assembly. The assemblies on the lower production levels are already produced or procured before the sales order arrives. Final assembly is only started when a sales order arrives. The critical factor in production is component availability. In contrast to Capable-to-Promise (CTP), no receipt elements are created in the SAP APO order network during the multilevel ATP check. Instead, the check results are stored in the ATP tree structure. Receipt elements are only generated later when the ATP tree structure is converted in PP/DS. This allows improved performance during

(C) SAP AG

SCM670

6

the check. However, statements on capacity availability and scheduling cannot be as detailed as in CTP.  Rules-based availability check You use the rules-based availability check to automatically or manually optimize the process for deciding between alternatives using predefined rules. If a product is not available, for example, you can check substitutes for availability or you can check the availability of the original product in other locations. Another option would be to select alternative PPMs within the framework of production. These alternatives are stored in master data (rules) and determined specifically for a transaction (condition technique).

(C) SAP AG

SCM670

7

3.7 Check Instructions Deciding on the check method

Obj ect

Access 1 = 1st Cond it ion

I.

Access 1 = 1st Cond it ion

II.

Access 2 = 2n d Co ndit ion Access 3 = 3rd Con dit i on Access 4 = 4t h Con dit io n Access 1 = 1st Cond it ion Access 1 = 1st Cond it ion Access 2 = 2n d Co ndit ion Access 3 = 3rd Con dit i on Access 4 = 4t h Con dit io n

  SAP AG 2003

The check instructions determine the type and scope of the availability check. In the check instructions, you define which availability check method you want to use.  If you want to perform the check on the basis of a basic method, you choose the basic method here (product availability check, check against product allocations, or check against the forecast).  If you want to check on the basis of the advanced methods, you have the following options:  You can combine basic methods in any way by defining the check sequence. If you do not set the Neutral results indicator, the result of the availability check of the previous step is the starting point for the check in the next check step. If you set the Neutral results indicator for a basic method, the result of this basic method has no effect on the final result. If the neutral result of a basic method is smaller than the final result, a message is displayed. If you have set the Neutral results indicator for all basic methods of a check, the final result is always the original and complete requirement quantity.  You can also call the rules-based availability check from the check instructions. If the Rules-Based ATP indicator is set, the system tries to determine one or more rules using the condition technique. The rules are master data. Possible product and location substitution relationships are defined there. If the call to production has been defined, alternative PPMs can also be defined in the rules. If you do not set the Start Immediately indicator, the difference between the requested quantity of the transaction and confirmed quantity from the check step(s) of the basic method(s) is transferred to the rule(s) for checking. If the Start Immediately indicator is set, the rules-based availability check is called immediately with the requested quantity of the transaction; in other words, without a check of 

(C) SAP AG

SCM670

8

any other activated basic methods. If the result of the rule interpretation is a calculation profile (for example, a consumption horizon), the system checks the original requirement while taking account of the calculation profile.  The production capability (CTP or MATP) is an additional check method that can be called if the basic checks fail. However, production can also be started immediately. If production is only called after an availability check, you have two options:  Production is started after execution of all basic methods in the check instructions for the partial quantity of the original requirement quantity that could not be confirmed in the previous checks: You have to bear in mind that when several basic methods are used, the confirmable quantities from step n represent the requirement for the basic method in step n+1.  Production is started for the partial quantity of the ATP requirement quantity that could not be confirmed by the product availability check: The ATP requirement quantity is the quantity that could be confirmed by preceding basic methods. If the product availability check is the first basic method, the ATP requirement quantity corresponds to the original requirement quantity.  Caution: It is not possible to call production and the rules simultaneously from the same check instructions. If you want the rules-based availability check and production to be combined with one another, you can determine other check instructions using the rules. Production is called from these check instructions or called directly from the rule within the context of the location determination activity.  In the normal sequence of events, a basic check (with or without production) is performed first. Only after the basic checks have failed to come up with the necessary committed quantity are the rules used to search for other locations and products (substitutions). The rules can also check for production in other locations.

(C) SAP AG

SCM670

9

3.8 Determination of the Check Instructions

Check mode

Business event

Check instructions

 SAP AG 2003

The determination of the check instructions depending on the business event and the check mode means that the type and scope of the availability check can be controlled depending on the calling process and/or the material.  Settings for determining the check instructions can exist in the basic configuration, in the product master, and in the location determination activity (integrated rule maintenance). The settings of the location determination activity are used by the availability check during location substitution in Global ATP. 

(C) SAP AG

SCM670

10

3.9 Business Events Define business events for each situation in which the OLTP can send an ATP request:

Sales order

Business events influence: Production order

 Check instructions  Check control  Scope of check

Delivery

 SAP AG 2003

Business events are defined in the OLTP system and used in SAP APO. A business event identifies the type of transaction that initiates the ATP check. Current business events available in SAP R/3 include:  Sales order  Production order (creation and release)  Delivery  The business event is transferred to the ATP check in SAP APO. In SAP APO, the business event is used together with the other ATP settings to determine the entire check rule control.  The business event corresponds to the checking rule in SAP R/3 and is transferred to SAP APO using SAP APO CIF.  

(C) SAP AG

SCM670

11

3.10 Determination of the Business Event

R/3

APO

Transaction:

Sales document

ABAP

Checking rule

CIF

Business event

 SAP AG 2003

You should be aware that each application has to define its own checking rules. The checking rule for the reservations is defined in Customizing for production orders, for example.  In contrast, in Sales and Distribution the checking rule is defined internally for each application and cannot be changed. 

(C) SAP AG

SCM670

12

3.11 Check Mode Grouping indicator for products and (indirectly) also for transactions Check mode Assignment mode Production type Check mode text

Product Product master master

Check mode

Availability check is called using SD in SAP R/3:

 Entry in the product master is ignored  SAP R/3 SD requirements class is transferred to SAP APO as check mode

 SAP AG 2003

The check mode is a grouping indicator for products. Together with the business event, it defines which check instructions are used for a group of products.  The check mode corresponds to the requirements type with the requirements class in SAP R/3. The requirements type is transferred with the requirements class from SD at runtime. No other applications transfer requirements classes. In this case, the check mode is read in the SAP APO product master. In the case of rules-based ATP, this also applies to the subsequent requirements (substitutions). For this reason, you should have entered the check mode in the location-specific product master.  In addition, the check mode can control the following:  If production is called within the availability check (controlled using the check instructions or the location determination activity), you make decisions here about the type of production that is used. The standard production type calls CTP, while the multilevel ATP check production type calls the multilevel ATP check.  The assignment mode determines which type of forecast (without assembly) is consumed by the sales orders. Only one type of consumption behavior is possible for each requirements strategy.  In the case of a requirements strategy for variant configuration, should only the product characteristics selected by the customer be transferred to SAP APO, or should both the characteristics and the configured BOM be transferred? Within normal variant-configured strategies, both the characteristics and the configured BOM are transferred. 

(C) SAP AG

SCM670

13

3.12 Planning Strategy and Requirements Class Planning strategy: Material master record

Planning strategies represent the business procedures for planning production quantities and dates 30Productionby lot size ...

...

20Make-to-order production

MRP group

40Planning with final assembly

10Net requirements planning

70Planning at assembly level

Requirements class: Demand management? Procurement after sales? ...?

Strategy group

Material type

...

Procurement beforesales? ATP? Consumption of planned independent requirements by customer requirements?

...?

 SAP AG 2003

Planning strategies represent the business procedures for planning production quantities and dates. In SAP R/3, a broad spectrum of production planning strategies is available offering numerous options from pure make-to-order production to make-to-stock production:  The planning strategy defines whether the production program is created on the basis of sales orders and / or sales forecast values.  The planning strategy defines the stocking level for the products. In other words, either finished products are stored or assemblies are stored. These assemblies are then finally assembled when a sales order arrives.  The planning strategy defines whether and how customer requirements consume planned independent requirements.  Using the planning strategy, you can define in SAP R/3 whether you want to perform an availability check for a material and, if so, which basic method should be used.  The planning strategies available for a material are listed in Customizing.  A planning strategy can be assigned to a material using a strategy group.  Various requirements types are defined for each of these strategies and each requirements type is assigned to a requirements class that contains the actual control parameters. 

(C) SAP AG

SCM670

14

3.13 Determination of the Requirements Class in SAP R/3 SD Order Order Material Material

Material master record

SAP SAP R/3 R/3 Customizing Customizing Strategy

Strategy group MRP group Material type

Requirements type

 

MRP type

Requirements class



Forecast Customer requirements

 

Availability check Type ? Transfer of requirements

 SAP AG 2003

The material and / or the transaction can determine whether an availability check and / or a transfer of requirements can take place. You can define this in the requirements class.  Determining the requirements class using the material.  If the strategy group is not maintained, it is determined using the MRP group.  If the MRP group is not defined, the system uses the material type instead of the MRP group to determine the strategy group (the material type has to be maintained as the MRP group).  A requirements type is determined using the strategy. Among other things, the requirements type defines the requirements type for the customer requirement.  First, an attempt is made to determine a strategy using the strategy group from the material master.  The requirements class is determined using the requirements type for the customer requirement. 

(C) SAP AG

SCM670

15

3.14 Determination of the Requirements Class in SAP R/3 SD Order Order Material Material

Material master record

SAP SAP R/3 R/3 Customizing Customizing Item category determination TA/Norm/.../.../ TAN

Requirements class Requirements type

 

MRP type



Availability check Type ? Transfer of requirements

 SAP AG 2003

Determining the requirements class using the transaction: If no requirements class can be determined using the material, the system tries to determine a requirements type / requirements class using the item category (document) and the MRP type (material master).  If this is not possible, the system tries to determine a requirements type / class using just the item category.  If none of the attempts to determine a requirements class are successful, or if the availability check and/or the transfer of requirements is deactivated in the requirements class that is determined, the transaction is not relevant for the availability check and/or the transfer of requirements.  The Source field can be used to choose an alternative search strategy. You also have the option to prioritize the determination of the requirements type/class using transactions. 



(C) SAP AG

SCM670

16

3.15 Master Data Integration ATP

 Check mode in SAP APO corresponds to the requirements class in SAP R/3  Determination of requirements class from strategy group or material type in material master 

CIF supports this determination during the transfer of the material master

 Check mode in SAP APO product master is filled automatically 

Consequence: ATP in SAP APO can be used without any further data maintenance

 SAP AG 2003

(C) SAP AG

SCM670

17

3.16 Check Method Selection: Summary

You are now able to:  Explain the basic concepts of the basic availability check methods  Explain the basic concepts of the advanced availability check methods  Determine the selection of the check method  Explain the significance and determination of the check mode and business event

 SAP AG 2003

(C) SAP AG

SCM670

18

3.17Check Method Selection: Exercises Unit: Check Method Selection

At the conclusion of this exercise, you will be able to: •

Select the availability check method by configuring the check instructions

•

Define how the relevant check instructions are determined

•

Determine the requirements type / class in SAP R/3

Maxitec Ltd.'s product spectrum and business processes are heterogeneous. The demands on the availability check therefore vary, depending on the product and possibly the transaction. Maxitec Ltd. decides to use various availability check methods.

Your instructor will assign the group number (##) that you need for all exercises in this course. 3-1 Create a new check mode YXX check mode group ##. Replace XX with 50 + ##. The sales orders should not consume the forecast. Choose Capable-to-Promise as the production type. Save. Confirm the Prompt For Customizing Request. In this exercise, you only create this check mode so that each group number has its own check instructions defined with this key. These check instructions cannot (yet) be used within the availability check. In practice, you configure a requirements class and the determination of this requirements class in SAP R/3 and transfer this requirements class to SAP APO by means of SAP APO CIF. This is the only way to guarantee that the relevant check control is determined from the OLTP. 3-2 A product availability check should be executed that is dependent on the check mode YXX and the checking rule A (sales order) parameters. Neither the rules nor production should be called. Create a new check control using the key check mode YXX and checking rule A and define the product availability check. Save. Confirm the Prompt for Customizing Request.

(C) SAP AG

SCM670

19

3-3 Set up an advanced availability check method. A check against product allocations should be performed first. Afterwards, the quantities confirmed from the check against product allocations should undergo a product availability check. Neither the rules nor production should be called. Change the check control you just defined accordingly. Save. Confirm the Prompt for Customizing Request. 3-4 Set up an advanced availability check method. A product availability check should be performed first. If the product availability check cannot confirm the complete requirement quantity, the rules-based ATP check should be started. If rules-based ATP cannot confirm the complete requirement quantity either, the original product should be procured or produced in the original location. Production or procurement should not be called directly from the availability check. Change the check control you just defined accordingly. Save. Confirm the Prompt for Customizing Request. 3-5 Set up another advanced availability check method. A check against product allocations should be performed first for the requirement. The quantities confirmed from the check against product allocations should then undergo a product availability check. If the original requirement cannot be covered, production should be called directly from the availability check. Production should be started after the check against product allocations and the product availability check have been executed. The rules should not be called. Change the check control you just defined accordingly. Save. Confirm the Prompt for Customizing Request.

(C) SAP AG

SCM670

20

3-6 Display the ATP data that has been determined for product T-F11## in location 2400. 3-6-1 Which check mode was assigned to your product in location 2400? _______________________________________________________________ 3-6-2 You call the availability check from an SD application in SAP R/3. Is the check mode defined in the SAP APO product master relevant for determining the check instructions? _______________________________________________________________ 3-6-3 How is the check mode that is relevant for determining each check instructions determined if the availability check is called from an SAP R/3 SD application? _______________________________________________________________ 3-6-4 Create a sales order for 10 pieces of your product T-F11## in the SAP R/3 system. Log on to the SAP R/3 system. Call the transaction VA01 (Create Sales Order). Enter the following data: Field Name or Data Type

Values

Order Type

OR

Standard order

Sales Organization

2400

Italy, Milan

Distribution Channel

10

Final customer sales

Division

00

Cross-division

Sold-To Party

2402

Jashanmal Int Tra Co

PO Number

PO-##

Requested Delivery Date

One week from today’s date

Delivering Plant

2400

DC Milan

Material

T-F11##

Maxitec R-3100

Quantity

10

Note: The delivering plant for the order item should appear by default when you press Enter. Verify that 2400 has been selected. If 2400 has not been selected, correct the field value. Choose Enter. Choose Enter if you receive the message, “Change in invoice date: The billing date is redetermined.” This message has no impact on the ATP check. Which requirements type has SAP R/3 determined for the product T-F11##? _______________________________________________________________ Do not save the order! If you have already saved the order, please delete it. If you have any problems, ask the instructor.

(C) SAP AG

SCM670

21

3-6-5 To which requirements class is this requirements type assigned in SAP R/3 Customizing? _______________________________________________________________ Note: This requirements class is transferred to SAP APO within the availability check as a check mode and controls the selection of the check instructions. 3-7

Check the configuration of the requirements class / check mode determination in SAP R/3. 3-7-1 To do so, go to the material master for material T-F11## in plant 2400. Display the MRP 3 tab page. Has the strategy group been maintained? Which strategy group is it? _______________________________________________________________ 3-7-2 If no strategy group had been maintained in the material master, which parameter would the system use to try and determine the strategy group? _______________________________________________________________ 3-7-3 Which tab page in the material master contains the MRP group? _______________________________________________________________ 3-7-4 What is the main strategy of the strategy group 10, make-to-order production? To find out, go to the definition of the strategy groups in SAP R/3 Customizing. _______________________________________________________________ 3-7-5 Which requirements types does the strategy 10, make-to-stock production, use to plan the planned independent requirements and the customer requirements? _______________________________________________________________ _______________________________________________________________ 3-7-6 Which requirements class is assigned to the requirements type KSL? _______________________________________________________________ 3-7-7 Have a look at requirements class 030. Has the availability check been activated there? _______________________________________________________________ Has the transfer of requirements been activated for requirements class 030? _______________________________________________________________

(C) SAP AG

SCM670

22

3-8

Create a sales order for 10 pieces of your product T-AS5## in the SAP R/3 system. 3-8-1 Call the transaction VA01 (Create Sales Order). Enter the following data: Field Name or Data Type

Values

Order Type

OR

Sales Organization

1000

Distribution Channel

12

Division

00

Sold-To Party

2300 Motomarkt Heidelberg

PO Number

PO-##

Requested Delivery Date

Three weeks from today’s date

Delivering Plant

1000

Material

T-AS5##

Quantity

10

Standard order

Note: The availability check is performed for material T-AS5## in SAP R/3 because it is not part of an active integration model. The delivering plant for the order item should appear by default when you press Enter. Verify that 1000 has been selected. If 1000 has not been selected, correct the field value. Choose Enter. Choose Enter if you receive the message “Change in invoice date: The billing date is redetermined.” This message has no impact on the ATP check. Which requirements type has SAP R/3 determined for the product T-AS5##? _______________________________________________________________ 3-8-2 To which requirements class is this requirements type assigned in SAP R/3 Customizing? _______________________________________________________________ Save the sales order. Note down the order number: _______________________________________________________________ Note: This requirements class is transferred to SAP APO within the availability check as a check mode and controls the selection of the check instructions. 3-8-3 Check the configuration of the requirements class / check mode determination in SAP R/3. To do so, go to the material master for material T-AS5## in the plant 1000. Display the MRP 3 tab page. Has the strategy group been maintained? _______________________________________________________________

(C) SAP AG

SCM670

23

3-8-4 If no strategy group had been maintained in the material master, which parameter would the system use to try and determine the strategy group? _______________________________________________________________ 3-8-5 Which tab page in the material master contains the MRP group? Has the MRP group been maintained? _______________________________________________________________ 3-8-6 How does the system determine the requirements type / class? _______________________________________________________________ _______________________________________________________________ 3-8-7 What is the MRP type for material T-AS5## in plant 1000? _______________________________________________________________ 3-8-8 What is the item category for item 10 of the sales order? _______________________________________________________________ 3-8-9 Examine the transaction-based determination of the requirements type in SAP R/3 Customizing. _______________________________________________________________ A requirements class is assigned to this requirements type. When you call the availability check in SAP APO, this requirements class would be transferred to SAP APO as the check mode.

(C) SAP AG

SCM670

24

3.18Check Method Selection: Solutions Unit: Check Method Selection

Your instructor will assign the group number (##) that you need for all exercises in this course. 3-1

Create a new check mode YXX check mode group ##. Replace XX with 50 + ##. The sales orders should not consume the forecast. Choose Capable-to-Promise as the production type. Save. Confirm the Prompt for Customizing Request. Choose SAP APO Implementation Guide (IMG): SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP Check) → General Settings → Maintain Check Mode. Choose New Entries. Enter YXX as the check mode. (Replace XX with 50 + ##) Assignment mode:

No assignment

Production type:

Standard

Check mode text:

Check mode group ##

Save your entries. In this exercise, you only create this check mode so that each group number has its own check instructions defined with this key. These check instructions cannot (yet) be used within the availability check. In practice, you configure a requirements class and the determination of this requirements class in SAP R/3 and transfer this requirements class to SAP APO by means of SAP APO CIF. This is the only way to guarantee that the relevant check control is determined from the OLTP.

(C) SAP AG

SCM670

25

3-2

A product availability check should be executed that is dependent on the check mode YXX and the checking rule A (sales order) parameters. Neither the rules nor production should be called. Create a new check control using the key check mode YXX and checking rule A and define the product availability check. Save. Confirm the Prompt for Customizing Request. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP Check) → General Settings→ Maintain Check Instructions. Choose New Entries. Enter the check mode YXX as check mode. Enter the business event A. Note: The letters below in parentheses do not actually appear on the Check Instructions screen – they are given here to complete the on-screen abbreviations. Product check:

First step

Product allocation (check):

No check

Forecast (check):

No check

Rules-based ATP (check):

Do not select

Start product(ion):

Availability check only, no production

The remaining parameters in the check instructions are not relevant and you can leave the default values as they are. Save the check instructions. Go back to the Implementation Guide (IMG).

(C) SAP AG

SCM670

26

3-3

Set up an advanced availability check method. A check against product allocations should be performed first. Afterwards, the quantities confirmed from the check against product allocations should undergo a product availability check. Neither the rules nor production should be called. Change the check control you just defined accordingly. Save. Confirm the Prompt for Customizing Request. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP Check) → General Settings → Maintain Check Instructions. Select check mode Y## / business event A. Choose Details (magnifying glass icon). Change the check instructions. Note: The letters below in parentheses do not actually appear on the Check Instructions screen – they are given here to complete the on-screen abbreviations. Product check:

Second step

Product allocation (check):

First step

Forecast (check):

No check

Rules-based ATP (check):

Do not select

Start product(ion):

Availability check only, no production

The remaining parameters in the check instructions are not relevant and you can leave the default values as they are. Save the check instructions. Go back to the Implementation Guide (IMG).

(C) SAP AG

SCM670

27

3-4

Set up an advanced availability check method. A product availability check should be performed first. If the product availability check cannot confirm the complete requirement quantity, the rules-based ATP check should be started. If rules-based ATP cannot confirm the complete requirement quantity either, the original product should be procured or produced in the original location. Production or procurement should not be called directly from the availability check. Change the check control you just defined accordingly. Save. Confirm the Prompt for Customizing Request. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP Check) → General Settings → Maintain Check Instructions. Select check mode Y## / business event A. Choose Details (magnifying glass icon). Change the check instructions. Note: The letters below in parentheses do not actually appear on the Check Instructions screen – they are given here to complete the on-screen abbreviations. Product check:

First step

Product allocation (check):

No check

Forecast (check):

No check

Rules-based ATP (check):

Select

Remaining requirement:

Create remaining requirement for source location product

Start product(ion):

Availability check only, no production

The remaining parameters in the check instructions are not relevant and you can leave the default values as they are. Save the check instructions. Go back to the Implementation Guide (IMG).

(C) SAP AG

SCM670

28

3-5

Set up another advanced availability check method. A check against product allocations should be performed first for the requirement. The quantities confirmed from the check against product allocations should then undergo a product availability check. If the original requirement cannot be covered, production should be called directly from the availability check. Production should be started after the check against product allocations and the product availability check have been executed. The rules should not be called. Change the check control you just defined accordingly. Save. Confirm the Prompt for Customizing Request. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP Check) → General Settings → Maintain Check Instructions. Select check mode Y## / business event A. Choose Details (magnifying glass icon). Change the check instructions. Note: The letters below in parentheses do not actually appear on the Check Instructions screen – they are given here to complete the on-screen abbreviations. Product check:

Second step

Product allocation (check):

First step

Forecast (check):

No check

Rules-based ATP (check):

Do not select

Remaining requirement:

Do not create remaining requirement

Start product(ion):

First availability check, then production

Production time:

After executing all basic methods

The remaining parameters in the check instructions are not relevant and you can leave the default values as they are. Save the check instructions. Go back to the Implementation Guide (IMG).

(C) SAP AG

SCM670

29

3-6

Display the ATP data that has been determined for product T-F11## in location 2400. Choose SAP APO Easy Access menu: Master Data → Product. Enter T-F11## as the product. Select the Location view and enter 2400 as the location. Choose Display to display the product data. Go to the ATP tab page. 3-6-1 Which check mode was assigned to your product in location 2400? 030 3-6-2 You call the availability check from an SD application in SAP R/3. Is the check mode defined in the SAP APO product master relevant for determining the check instructions? No 3-6-3 How is the check mode that is relevant for determining each check instructions determined if the availability check is called from an SAP R/3 SD application? The SAP R/3 SD requirements class is transferred to SAP APO as check mode 3-6-4 Create a sales order for 10 pieces of your product T-F11## in the SAP R/3 system. Log on to the SAP R/3 system. Call the transaction VA01 (Create Sales Order) in SAP R/3. Enter the following data: Field Name or Data Type

Values

Order Type

OR

Standard order

Sales Organization

2400

Italy, Milan

Distribution Channel

10

Final customer sales

Division

00

Cross-division

Sold-To Party

2402

Jashanmal Int Tra Co

PO Number

PO-##

Requested Delivery Date

One week from today’s date

Delivering Plant

2400

Material

T-F11## Maxitec R-3100

Quantity

10

DC Milan

Note: The delivering plant for the order item should appear by default when you press Enter. Verify that 2400 has been selected. If 2400 has not been selected, correct the field value. Choose Enter.

(C) SAP AG

SCM670

30

Choose Enter if you receive the message “Change in invoice date: The billing date is redetermined.” This message has no impact on the ATP check. Which requirements type has SAP R/3 determined for the product T-F11##? Go to the Procurement tab page. The requirements type is KSL. Do not save the order! If you have already saved the order, please delete it. If you have any problems, ask the instructor. 3-6-5 To which requirements class is this requirements type assigned in SAP R/3 Customizing? Choose SAP R/3 Implementation Guide (IMG): Sales and Distribution → Basic Functions → Availability Check and Transfer of Requirements → Transfer of Requirements → Define Requirements Types. Search for requirements type KSL in the list. Requirements class:

030

Note: This requirements class is transferred to SAP APO within the availability check as a check mode and controls the selection of the check instructions. 3-7

Check the configuration of the requirements class / check mode determination in SAP R/3. 3-7-1 To do so, go to the material master for material T-F11## in the plant 2400. Display the MRP 3 tab page. Has the strategy group been maintained? Which strategy group is it? Choose SAP R/3 Easy Access menu: Logistics → Sales and Distribution → Master Data → Products → Material → Other Material → Display. Material: T-F11## Choose Select view(s). Choose the MRP 3 view. Enter the plant 2400. Choose Enter to confirm your entries. Strategy group: 10: Make-to-stock production 3-7-2 If no strategy group had been maintained in the material master, which parameter would the system use to try and determine the strategy group? The MRP group 3-7-3 Which tab page in the material master contains the MRP group? The MRP 1 tab page

(C) SAP AG

SCM670

31

3-7-4 What is the main strategy of the strategy group 10, make-to-order production? To find out, go to the definition of the strategy groups in SAP R/3 Customizing. Choose SAP R/3 IMG: Production → Production Planning → Demand Management → Planned Independent Requirements → Planning Strategy → Define Strategy Group. Select 10: make-to-stock production. Choose Details (magnifying glass). The main strategy is: 10: Make-to-stock production 3-7-5 Which requirements types does the strategy 10, make-to-stock production use to plan the planned independent requirements and the customer requirements? Choose SAP R/3 IMG: Production → Production Planning → Demand Management → Planned Independent Requirements → Planning Strategy → Define Strategy. Select strategy 10: make-to-stock production. Choose Details (magnifying glass). Requirements type for planned independent requirements: LSF: Make-to-stock production Requirements type for customer requirement: Sale from stock without independent requirements reduction

KSL:

3-7-6 Which requirements class is assigned to the requirements type KSL? Choose SAP R/3 IMG: Sales and Distribution → Basic Functions → Availability Check and Transfer of Requirements → Transfer of Requirements → Define Requirements Types. Search for requirements type KSL in the list. Requirements class: 030 3-7-7 Have a look at requirements class 030. Has the availability check been activated there? Choose SAP R/3 IMG: Sales and Distribution → Basic Functions → Availability Check and Transfer of Requirements → Transfer of Requirements → Define Requirements Classes. Search for requirements class 030 in the list. Choose Details (magnifying glass). Availability check:

Activated

Has the transfer of requirements been activated for requirements class 030? Requirements transfer:

(C) SAP AG

Activated

SCM670

32

3-8

Create a sales order for 10 pieces of your product, T-AS5##, in the SAP R/3 system. 3-8-1 Call the transaction VA01 (Create Sales Order). Enter the following data: Field Name or Data Type

Values

Order Type

OR

Sales Organization

1000

Distribution Channel

12

Division

00

Sold-To Party

2300 Motomarkt Heidelberg

PO Number

PO-##

Requested Delivery Date

Three weeks from today’s date

Delivering Plant

1000

Material

T-AS5##

Quantity

10

Standard Order

Note: The availability check is performed for material T-AS5## in SAP R/3 because it is not part of an active integration model. The delivering plant for the order item should appear by default when you press Enter. Verify that 1000 has been selected. If 1000 has not been selected, correct the field value. Choose Enter. Choose Enter if you receive the message “Change in invoice date: The billing date is redetermined.” This message has no impact on the ATP check. Which requirements type has SAP R/3 determined for the product T-AS5##? Go to the Procurement tab page. The requirements type is 011. 3-8-2 To which requirements class is this requirements type assigned in SAP R/3 Customizing? Choose SAP R/3 IMG: Sales and Distribution → Basic Functions → Availability Check and Transfer of Requirements → Transfer of Requirements → Define Requirements Types. Search for requirements type 011 in the list. Requirements class: 011 Save the sales order. Note down the order number: _______________________________________________________________ Note: This requirements class is transferred to SAP APO within the availability check as a check mode and controls the selection of the check instructions.

(C) SAP AG

SCM670

33

3-8-3 Check the configuration of the requirements class / check mode determination in SAP R/3. To do so, go to the material master for material T-AS5## in the plant 1000. Display the MRP 3 tab page. Has the strategy group been maintained? Choose SAP R/3 Easy Access menu: Logistics → Sales and Distribution → Master Data → Products → Material → Other Material → Display. Material: T-AS5## Choose Select view(s). Choose the MRP 3 view. Enter the plant 1000. Choose Enter to confirm your entries. Strategy group: No strategy group 3-8-4 If no strategy group had been maintained in the material master, which parameter would the system use to try and determine the strategy group? The MRP group 3-8-5 Which tab page in the material master contains the MRP group? Has the MRP group been maintained? The MRP 1 tab page Choose SAP R/3 Easy Access menu: Logistics → Sales and Distribution → Master Data → Products → Material → Other Material → Display. Material: T-AS5## Choose Select view(s). Choose the MRP 1 view. Enter the plant 1000. Choose Enter to confirm your entries. MRP group: No MRP group 3-8-6 How does the system determine the requirements type / class? Using the transaction; that is, using the MRP type from the material master and the item category from the sales order. 3-8-7 What is the MRP type for material T-AS5## in location 1000? The MRP type is on the MRP 1 tab page in the material master. Choose SAP R/3 Easy Access menu: Logistics → Sales and Distribution → Master Data → Products → Material → Other Material → Display. Material: T-AS5## Choose Select view(s). Choose the MRP 1 view. Enter the plant 1000. (C) SAP AG

SCM670

34

Choose Enter to confirm your entries. MRP type: VB 3-8-8 What is the item category for item 10 of the sales order? Call the transaction VA02 (Change Sales Order). Enter your order number. Choose Enter to confirm your entry. The item category is on the overview screen at item level: TAN 3-8-9 Examine the transaction-based determination of the requirements type in SAP R/3 Customizing. Choose SAP R/3 IMG: Sales and Distribution → Basic Functions → Availability Check and Transfer of Requirements → Transfer of Requirements → Determination Of Requirement Types Using Transaction. Locate the item category TAN and the MRP type VB. Requirements type: 011 A requirements class is assigned to this requirements type. When you call the availability check in SAP APO, this requirements class is transferred to SAP APO as the check mode.

(C) SAP AG

SCM670

35

4 Product Availability Check

Contents:  Basic concept and logic of the product availability check  Setup of the product availability check  Check with or without using the checking horizon  Determination of the scope of check  Shortage check  Simulation of the availability check

 SAP AG 2003

(C) SAP AG

SCM670

1

4.2 Product Availability Check: Objectives

At the conclusion of this unit, you will be able to:  Set up and use the product availability check  Describe the philosophy of time series in SAP liveCache and their role in availability checking  Use the simulation function of the availability check

 SAP AG 2003

(C) SAP AG

SCM670

2

4.3 Product Availability Check: Course Overview Diagram 1

Course Overview 2 2

Global ATP / OLTP Interface 3 3

Check Method Selection 4

Product Availability Check

5 Check Against Product Allocations 6 7 8 9

Rules-Based Availability Check Production Within the ATP Check

Backorder Processing

Scheduling

 SAP AG 2003

(C) SAP AG

SCM670

3

4.4 Product Availability Check: Business Scenario

 At Maxitec Ltd., you need an overview of both onhand and planned stock over a period of time. The availability check prevents sales order commitments from exceeding available stock or supply plans.  For some products, orders lying beyond a period of 10 days can be confirmed definitively because the products can either be produced or procured by then.

 SAP AG 2003

(C) SAP AG

SCM670

4

4.5 Concept of the Product Availability Check

Receipts Stock

Planned order

Purchase requisition

Time Sales order generating the ATP check

Today

Planned deliveries

Issues

 SAP AG 2003

The product availability check is successful if a sufficient (cumulated) ATP quantity of the product is available on a date derived from the delivery date requested by the customer (the material availability date).  The data required for the check is transferred from the OLTP system(s) to SAP APO and modeled there in SAP liveCache as a time series.  The following information is required: stock information, planned receipts, and planned requirements, as well as the related times on the time axis. 

(C) SAP AG

SCM670

5

4.6 Basic Rules of the Product Availability Check Availability Availability check check

X

 The product availability check is successful if a sufficient (cumulated) ATP quantity is available on the material availability date.  The scope of the ATP quantity is defined individually for each company (scope of check).  The scope of check is defined in relation to transactions and/or products.  The (cumulated) ATP quantity is time-based.  Issues always try first to consume the most recent receipt.  There is no pegging.  SAP AG 2003

(C) SAP AG

SCM670

6

4.7 Check Logic

Receipts Stock 100 100 PC PC

Planned order Purchase order

70 70 PC PC

50 50 PC PC

Time

30 30 PC PC

Sales order

Issues Cumulated ATP quantity

100 PC

120 PC

190 PC

 SAP AG 2003



The product availability check is successful if a sufficient cumulated ATP quantity is available on the material availability date determined from the requested delivery date.

(C) SAP AG

SCM670

7

4.8 Check Logic (2)

Receipts Stock 100 100 PC PC

Planned order Purchase order

70 70 PC PC

Av y che Ava aila ilabilit bility check ck

50 50 PC PC X 30 30 PC PC

? ?

Sales order

Issues Cumulated ATP quantity

110 110 PC PC

New sales order 100 PC

120 PC

190 PC

 SAP AG 2003

(C) SAP AG

SCM670

8

4.9 Check Logic (3)

Receipts Stock 100 100 PC PC

Planned order Purchase order

70 70 PC PC

50 50 PC PC

Time

30 30 PC PC

Sales order

Issues Cumulated ATP quantity

110 110 PC PC

Sales order 80 PC

 SAP AG 2003

(C) SAP AG

SCM670

9

4.10 Controlling the Product Availability Check

Ch Che eck ckm mo od de e

== requirements requirements class class SAP SAP R/3 R/3

Bu sine en Busin esse ssev ve ntt

ATP ATPgro roup

== checking checking rule rule SAP SAP R/3 R/3

== checking checking group group SAP SAP R/3 R/3

Check instructions

Check control

Product availability check

Scope Scope of of check check

 SAP AG 2003

  

You select the check method for the availability check in the check instructions. The type and scope of the product availability check is determined by the check control. The business event and the ATP group determine the check control; that is, the product availability check can be controlled individually depending on the transaction and/or the product (or the product group).

(C) SAP AG

SCM670

10

4.11 ATP Group

ATP Group

02

Maintain ATP Group Cumulation Response Text for ATP Group

Basic ATP settings:  Cumulation: Indicator for the shortage check  Response to shortfall when using ATP with shortage check -> A dialog box appears

 SAP AG 2003

The ATP group is a grouping at product level. It controls the cumulative ATP check processing and, in conjunction with the business event, also dictates the scope of the ATP check.  The shortage check is sometimes referred to as Online vs. Batch, because it enables a similar behavior in online processing to the backorder processing carried out in batch mode. It prevents the confirmation of new items, thus allowing free quantities to be reserved for existing orders. Backorder processing redistributes available quantities. 

(C) SAP AG

SCM670

11

4.12 Check Control

ATP Group

02

Individual requirements

Business Event

A

SD order

ATP Check Control: General No Sublocation Check No Version Check Consider Checking Horizon Receipts from Past Checking Horizon GR

 SAP AG 2003

 

  



The sublocation level is a storage subset of the APO location. It is interpreted as a storage location if the ATP category comes from SAP R/3. A requirement can be checked at location and sublocation level. The definition of the product version (which is interpreted as a batch if the ATP category is from SAP R/3) comes from the OLTP system. If a requirement for which a product version has been specified is transferred to ATP in SAP APO, it can be checked at both the product and version levels. Requirements lying after the checking horizon at the time of the check are always considered available if this option is active. An ATP check using the receipts from the past option determines if receipts with receipt dates in the past should be taken into account in the confirmation of a requirement. Consider past receipts:  A Consider past receipts with message  B Past receipts not considered  C Past receipts not considered with message The horizon for missing parts at goods receipt determines how many days in the future will be checked for shortages (using goods receipt postings in Inventory Management).

(C) SAP AG

SCM670

12

4.13 ATP Time Series in SAP liveCache Individual time series for each:  Product

Product Product A

 Location

Location 1

 Sublocation  Product version  Characteristics combination

Location 2 Sublocation 01

Sublocation 02

 SAP AG 2003











The product availability check uses time series that represent the receipts and issues for a product. Individual time series exist on product, location, sublocation, and version level. The sublocation and version correspond to the storage location and the batch respectively in SAP R/3. In SAP APO, planning is executed at product location level. The identification of ATP time series is also based on these terms. Furthermore, ATP supports additional organizational levels, as in SAP R/3:  The sublocation (in SAP R/3 = storage location)  The product version ( in SAP R/3 = batch)  The characteristics combination (does not exist in SAP R/3) ATP in SAP APO evaluates these levels according to the level of detail by which the incoming requirement is specified. All organizational levels that may contain elements are taken into account, with the minimum quantity on each date being finally confirmed. Example I: A sales order specifies a product version, but no sublocation is given. The product is not configured, therefore no characteristics exist. In this case, the ATP check is carried out at these levels:  Product / location  Product / location / product version Example II: A sales order specifies a product version and a sublocation. Again, the product is not configured therefore no characteristics exist. In this case, the ATP check is carried out at these levels:  Product / location  Product / location / product version

(C) SAP AG

SCM670

13

 Product / location / sublocation  Product / location / product version / sublocation  Conclusion: The higher the specificity of the requirement, the larger the number of checks that have to be carried out.

(C) SAP AG

SCM670

14

4.14 Aggregation of Time Series in SAP liveCache Aggregate each receipt (issue) according to:  Category  Time unit

 Cumulative, rather than individual, quantities are checked – high performance  SAP AG 2003

(C) SAP AG

SCM670

15

4.15 Checks Using Checking Horizon Method for checking against the replenishment lead time Product availability check only in checking horizon

50 50 50 50

20 20 20 20

Checking Horizon

Outside the checking horizon, confirmation without check

∞

 SAP AG 2003

The checking horizon defines a time interval (check date + period) in which a product availability check can be carried out. If the requirements date lies within this time interval, the check is carried out. Requirements that lie after the end of the checking horizon are not checked, which means they are confirmed in full. The checking horizon can be used to model the replenishment lead time, for example.  The following prerequisites must be met for using the checking horizon:  The checking horizon and the checking horizon calendar must be entered in the location-specific product master data.  The checking horizon must be activated in Customizing for the check control. 

(C) SAP AG

SCM670

16

4.16 SAP R/3 Replenishment Lead Time and SAP APO Checking Horizon R/3

APO

In-house production Replenishment lead time (if MRP 3 defined in SAP R/3)

Checking horizon Or

In-house production + Goods receipt processing time

Checking horizon

External procurement Purchasing processing time + Planned delivery time + Goods receipt processing time

Checking horizon

 SAP AG 2003

(C) SAP AG

SCM670

17

4.17 Check Control -> Scope of Check

Include (or exclude) any of the SAP R/3 and external categories Cat. AD CA CC AJ xy

Description Production order (released) Stock in transfer (loc. to loc.) Valuated, unrestrictedunrestricted-use stock Planned order (firmed) Legacy II

Grouping of unique checks for combinations of ATP group and business event

 SAP AG 2003

You define the calculation of the ATP quantity yourself. In other words, you can make a distinction between product availability checks with different degrees of "safety" (that is, ranging from conservative checks to checks with risk).  This means that depending on the aims of the check, other stock types, receipt types, and requirement types are included in the scope of check. These MRP elements are described as categories in the SAP APO system.  Depending on the transaction and/or product (or product group), you can choose between checks with different degrees of "safety." 

(C) SAP AG

SCM670

18

4.18 ATP Categories ATP categories

R/3 categories Cat. AC AD AG AI AJ

Description Production order (created) Production order (released) Purchase requisition Planned order (not firmed) Planned order (firmed)

External categories • APO categories • Legacy categories Cat. xx xy EE ...

Description Legacy I Legacy II SNP: Planned order

MRP elements  SAP AG 2003

ATP categories of different requirement/procurement elements allow you to choose the specific types of stock or planned receipts to be included in or excluded from the basic ATP check. You can use either SAP R/3 ATP categories or externally-defined categories.  Over 60 ATP categories, which can be transferred to SAP APO, are currently defined in SAP R/3.  You can define external categories to integrate legacy systems with ATP, which means that APO categories are defined in the configuration table for external categories. These external ATP categories in SAP APO are mapped to the non-R/3 categories.  In SAP APO 3.0, the category CB Safety Stock cannot be used to force the system to check the ATP quantity with or without safety stock (as is possible in SAP R/3). The safety stock in SAP R/3 is not real stock, but rather a number used to reduce the existing stock. At present, the ATP quantity is checked in SAP APO without safety stock; in other words, safety stock is not available. A forthcoming SAP APO release will add this feature. 

(C) SAP AG

SCM670

19

4.19 Shortage Check

Receipt 1

Situation 1

Issue A

Receipt 1

Receipt 1

Situation 2 Issue B Issue A

 SAP AG 2003

 







In situation 2, a discrepancy in the confirmation has been caused by the postponement of the receipt. Consequently, total confirmed quantities exceed total receipts. There is a shortage. If a planned receipt is postponed to any date after the confirmation date, the sales order confirmation is retained, even though not enough stock exists to cover the requirement. This is because changing the receipt does not automatically change the order. A new order created in this situation might also be confirmed because of the postponed receipt, and thus lead to an overconfirmation. This situation results from the check logic in the ATP check. Issues always try first to consume the ATP quantity of the most recent receipt. At the time of the check for planned issue A, planned receipt 1 is scheduled before the planned issue. The issue could be confirmed because the ATP quantity for receipt 1 is positive and larger than planned issue A. As long as receipt 1 is scheduled before issue A, its ATP quantity is reduced by issue A. If receipt 1 is shifted to a time after issue A, its ATP quantity increases because the "relationship" to issue A only ever points in a backward (time) direction. Receipt 1 has a positive ATP quantity again, although the cumulated ATP quantity is now negative. Issue B can now be confirmed after the postponed receipt 1 because this receipt has a positive ATP quantity. You have the following options for removing this inconsistency:  Executing the planning run  Rescheduling  Backorder processing Since these functions require a lot of time, it is possible that orders, whose entry dates indicate that they cannot be delivered, are delivered. The shortage check excludes this situation from the very start.

(C) SAP AG

SCM670

20



The shortage check is activated in Customizing for the ATP group. There are two different shortage checks:  Check taking account of the cumulated confirmed quantities: During the calculation of the cumulated ATP quantity, the system takes account of the sum of all previously confirmed quantities. In other words, new sales orders can only be confirmed when total receipts exceed total confirmed quantities.  Check taking account of the cumulated requirement quantities: When calculating the cumulated ATP quantity, the system takes account of all open requirement quantities. In other words, new sales orders can be confirmed when total receipts exceed total requirement quantities.

(C) SAP AG

SCM670

21

4.20 Simulation Function

ATP

Date/Quantity

 Product

 Requirement date

 Location



Material availability date

 Sublocation



Requested delivery date

 Version



Goods issue date

Check control

 Requirement quantity

 Check mode  Business event  With requirement quantities

 SAP AG 2003

The simulation function allows you to quickly investigate the effects of several potential planning scenarios.  You can execute several types of simulated product availability checks. You can implement either:  A simulated availability check according to ATP logic  A simulated check against product allocations  A simulation of a combination of basic methods  A simulated, rules-based availability check 

(C) SAP AG

SCM670

22

4.21 Location-Specific Product Master ATP

Complete the fields in the ATP view:

Product master

 ATP check mode If no other check mode is sent from the OLTP system  ATP group  Checking horizon As replenishment lead time  Checking horizon calendar Applied to checking horizon

 SAP AG 2003

Products and locations are created in the OLTP system and have to be transferred to SAP APO. If SAP R/3 is the OLTP system, the CIF integration model is used. Other products can use a variety of BAPIs that are delivered with SAP APO.  The SAP R/3 requirements class of the actual business process is matched to the SAP APO check mode. The check mode determines important planning criteria, such as forecast consumption and the means of production (CTP or MATP). In conjunction with the business event, it defines the type of check instructions.  The ATP group is a grouping at product level. It controls cumulative ATP check processing and, in conjunction with the business event, also dictates the scope of the ATP check.  The checking horizon/calendar sets a limit beyond which every requirement is considered to be able to be confirmed. 

(C) SAP AG

SCM670

23

4.22 Characteristics-Based ATP

R/3

APO

Customizing Customizing

-> -> Cross-Application Cross-Application Components Components -> -> Classification Classification System System

Customizing Customizing

-> -> Basis Basis Settings Settings

  Maintain Maintain classification classification in in the the SAP SAP R/3 R/3 material material master master (SAP (SAP Easy Easy Access) Access) -> -> Logistics Logistics ->> Supply Chain Planning Supply Chain Interfaces Interfaces -> -> Core Core Interface Interface Advanced Planning Advanced Planning and and Optimization Optimization

  Define Define Class Class System System (CDP (CDP or or Classical Classical Characteristics) Characteristics) -> -> Global Global ATP ATP Check Check -> -> Product Product Availability Availability Check Check   Maintain Maintain Characteristics Characteristics View View

  Generate Generate and and activate activate integration integration model model (incl. (incl. char. char. & & class) class)

 SAP AG 2003



To perform characteristics-related postings (receipts, stocks, and issues) in the time series, activate the ATP characteristics view.  If you activate or delete an ATP characteristics view, data might not exist in SAP liveCache for products in the ATP characteristics view.  Transaction data might not be transferred from the OLTP system to the SAP APO system during activation or deactivation. Changes to transaction data are also not permitted.  SAP recommends that you work with separate integration models for master data and transaction data when transferring data from the SAP R/3 system to the SAP APO system using the APO Core Interface.



You must be aware of the following when creating characteristics in the SAP R/3 system:  The characteristics must be unique in the value assignment. In other words, you must set the Single Value indicator, as this ensures that the characteristics can only be assigned a single value.  You must set the Input Required indicator. This indicator defines whether the value must be assigned to the characteristic.  Interval values are not allowed for numerical values.

(C) SAP AG

SCM670

24

 Additional values are not allowed.

(C) SAP AG

SCM670

25

4.23 Supply Chain Cockpit ATP is fully integrated in the navigation component

ATP button ATP alerts for product shortfall  Start Alert Monitor 

ATP queries from context menu  

ATP situation ATP simulation

 SAP AG 2003

Global ATP is fully integrated into the Supply Chain Cockpit. ATP simulations are also possible from the Supply Chain Cockpit.  The ATP situation shows all ATP quantities for the selected combination of product and location on the map.  Using the ATP simulation, you can execute a complete ATP check, including checking with rulesbased strategies.  Both queries can be executed using the selection from the network map or the work area section of the navigation component.  There are three ATP alert types in the Alert Monitor. They are also displayed on the ATP button, which you can use in the control panel in navigation.  

(C) SAP AG

SCM670

26

4.24 Product Availability Check: Summary

You are now able to:  Set up and use the product availability check  Describe the philosophy of time series in SAP liveCache and their role in availability checking  Use the simulation function of the availability check

 SAP AG 2003

(C) SAP AG

SCM670

27

4.25Product Availability Check: Exercises Unit: Product Availability Check

At the conclusion of this exercise, you will be able to: •

Set up the product master for the product availability check

•

Set up the product availability check

•

Verify the inventory situation of a product in the SAP APO system and the OLTP system

•

Simulate an availability check for a material in SAP APO

•

Perform a real-time availability check from a sales order in the SAP R/3 transaction system

Maxitec Ltd.uses SAP R/3 and SAP APO to plan all delivery-related tasks in the supply chain. When an availability check is performed at sales-order entry in the OLTP system, a product availability check is performed on the SAP APO server. Some products are checked using the checking horizon. This check is performed automatically when sales documents (for example, a sales order) are created in the OLTP system. In this exercise, you want to set up Customizing for checks against the ATP quantity for the PC product T-F11##. To verify and test these settings, you also want to simulate an ATP check for the PC product in SAP APO. You will use T-F11## as your PC product, where ## is your group number. In addition, you will use location 2400 Milan as your distribution center (DC). This product and distribution center are used throughout these exercises.

(C) SAP AG

SCM670

28

Your instructor will assign the group number (##) that you need for all exercises in this course. 4-1

Display the ATP data that has been determined for product T-F11## in location 2400. 4-1-1 Which ATP group has been assigned to your product in SAP APO for location 2400? ATP group in SAP APO: _______________________________________________________________ Remain on the ATP view of the product master for the next step. 4-1-2 Which calendar and replenishment lead time are used when the availability check is performed with reference to the replenishment lead time? Checking horizon (replenishment lead time): ___________________________ Checking horizon calendar: ___________________________________________ Exit the product master.

4-2

Display the ATP categories (stock, receipts, and issue elements) configured in SAP APO. 4-2-1 Which category is used for valuated, unrestricted-use stock? _______________________________________________________________ 4-2-2 Which category is used for the purchase requisition? _______________________________________________________________ 4-2-3 Which category is used for the sales order? _______________________________________________________________

4-3

Display the business event for a sales order. 4-3-1 Which business event is defined for the standard SD (sales) order? _______________________________________________________________ Upon creation of a sales order for material T-F11##, business event A and requirement class 30 are passed from SAP R/3 to SAP APO. The business event and the requirement class determine the type of availability check to be performed.

(C) SAP AG

SCM670

29

4-4

Display the availability check methods performed for check mode 030 and business event A. Note: The letters below in parentheses do not actually appear on the Check Instructions screen – they are given here to complete the on-screen abbreviations. 4-4-1 Product check: _______________________________________________________________ 4-4-2 Product allocation (check): _______________________________________________________________ 4-4-3 Forecast (check): _______________________________________________________________ 4-4-4 Rules-based ATP (check): _______________________________________________________________ 4-4-5 Start product(ion): _______________________________________________________________

4-5

Using business event A and ATP group 02, identify the configuration parameter that determines whether the checking horizon (total replenishment time) is used in determining product availability. 4-5-1 Which parameter determines if the checking horizon is used in product availability checking? _______________________________________________________________ Remain on this screen for the next exercise.

4-6

Review the scope of the availability check for ATP group 02 and business event A. Which of the following elements are included in the scope of check? 4-6-1 Sales orders? _________________________________________________ 4-6-2 Customer quotations? ________________________________________________ 4-6-3 Released production orders? ____________________________________ 4-6-4 Restricted-use inventory stock? ______________________________________________

(C) SAP AG

SCM670

30

4-7

Have a look at the ATP quantity for material T-F11## in location 2400 (Milan DC) in SAP APO. Enter the following data: Field Name or Data Type

Values

Product

T-F11##

Maxitec R-3100

Location

2400

Milan

Business Event

A

Sales order

4-7-1 How large is the ATP quantity in DC 2400 Milan? _______________________________________________________________ 4-8

Use the SAP APO simulation component to check if an order for 75 pieces of product TF11## can be delivered next week from location 2400 (Milan DC). Enter the following data: Field Name or Data Type

Values

Product

T-F11##

Maxitec R-3100

Plant/DC (location)

2400

Milan

Check Mode

030

Business Event

A

Material Availability Date

Monday next week

Requirement Quantity

75 PC

Sales order

4-8-1 Can all 75 pieces of the product be delivered next week? _______________________________________________________________

(C) SAP AG

SCM670

31

4-9

Create a sales order for 75 pieces of product T-F11## in SAP R/3. Have a look at the ATP check results. Log on to the SAP R/3 system. Call the transaction VA01 (Create Sales Order). Enter the following data: Field Name or Data Type

Values

Order Type

OR

Standard order

Sales Organization

2400

Italy, Milan

Distribution Channel

10

Final customer sales

Division

00

Cross-division

Sold-To Party

2402

Jashanmal Int Tra Co

PO Number

PO-##

Requested Delivery Date

One week from today’s date

Delivering Plant

2400 DC Milan

Material

T-F11## Maxitec R-3100

Quantity

75

4-9-1 What are the results of the availability check? _______________________________________________________________ _______________________________________________________________ 4-9-2 How many schedule lines are there, and what are their dates? _______________________________________________________________ _______________________________________________________________ Save the sales order. 4-10

After saving the SAP R/3 sales order, have a look at the inventory situation of your material in SAP APO. Use the Product View to display your inventory status. Enter planning version 000, product T-F11##, and location 2400. 4-10-1 What is the current inventory of the product? _______________________________________________________________ _______________________________________________________________ 4-10-2 What are the current requirements for the product? _______________________________________________________________ _______________________________________________________________

(C) SAP AG

SCM670

32

4.26Product Availability Check: Solutions Unit: Product Availability Check

You will use T-F11## as your PC product, where ## is your group number. In addition, you will use 2400 Milan as your distribution center. This product and distribution center are used throughout these exercises. Your instructor will assign the group number (##) that you need for all exercises in this course. 4-1

Display the ATP data that has been determined for product T-F11## in location 2400. Choose SAP APO Easy Access menu: Master Data → Product. Enter T-F11## as the product. Select the Location view and enter 2400 as the location. Choose Display to display the product data. Go to the ATP tab page. 4-1-1 Which ATP group has been assigned to your product in SAP APO for location 2400? ATP group in SAP APO: 02 Remain on the ATP view of the product master for the next step. 4-1-2 Which calendar and replenishment lead time are used when the availability check is performed with reference to the replenishment lead time? Checking horizon (replenishment lead time): 10 Checking horizon calendar: No calendar Exit the product master.

(C) SAP AG

SCM670

33

4-2

Display the ATP categories (stock, receipts, and issue elements) configured in SAP APO. To access the SAP APO configuration, choose Tools → AcceleratedSAP → Customizing → Project Management. Choose SAP Reference IMG on the Customizing: Project Administration screen. Choose SAP APO Implementation Guide (IMG): → SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → General Settings → Maintain Category. If necessary, double-click SAP Categories to access this view. Scroll down in the table on the right-hand side as necessary. Select the category CC. Choose Details (magnifying glass). Have a look at the following fields: Category Type, MRP Element, and R/3 Object. Repeat for categories AG and BM. 4-2-1 Which category is used for valuated, unrestricted-use stock? CC 4-2-2 Which category is used for the purchase requisition? AG 4-2-3 Which category is used for the sales order? BM Go back to the Implementation Guide (IMG).

4-3

Display the business event for a sales order. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → General Settings → Maintain Business Event. 4-3-1 Which business event is defined for the standard SD (sales) order? A Upon creation of a sales order for material T-F11##, business event A and requirement class 30 are passed from SAP R/3 to SAP APO. The business event and the requirement class determine the type of availability check to be performed. Go back to the Implementation Guide (IMG).

(C) SAP AG

SCM670

34

4-4

Display the availability check methods performed for check mode 030 and business event A. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → General Settings → Maintain Check Instructions. Select check mode 030 / business event A. Choose Details (magnifying glass). Note: The letters below in parentheses do not actually appear on the Check Instructions screen – they are given here to complete the on-screen abbreviations. 4-4-1 Product check:

First step

4-4-2 Product allocation (check):

No check

4-4-3 Forecast (check):

No check

4-4-5 Rules-based ATP (check):

Do not select

4-4-6 Start product(ion):

Availability check only, no production

Go back to the Implementation Guide (IMG). 4-5

Using business event A and ATP group 02, identify the configuration parameter that determines whether the checking horizon (total replenishment time) is used in determining product availability. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Product Availability Check → Maintain Check Control. If necessary, double-click ATP Check Control: General to display this view. Select ATP Group 02 / business event A. Choose Details (magnifying glass). 4-5-1 Which parameter determines if the checking horizon is used in product availability checking? Consider CH Remain on this screen for the next exercise. ASK THE INSTRUCTOR TO ACTIVATE THE Consider CH INDICATOR (if it is not already activated).

4-6

Review the scope of the availability check for ATP group 02 and business event A. Select ATP group 02 / business event A Double-click ATP Check Control: Scope of Check in the left column. Which of the following elements are included in the scope of check? 4-6-1 Sales orders?

Yes, ATP category BM

4-6-2 Customer quotations?

Yes, ATP category BL

4-6-3 Released production orders?

Yes, ATP category AD

(C) SAP AG

SCM670

35

4-6-4 Restricted-use inventory stock?

No, category CK is not listed

Exit the IMG.

(C) SAP AG

SCM670

36

4-7

Have a look at the ATP quantity for material T-F11## in location 2400 (Milan DC) in SAP APO. Choose SAP APO Easy Access menu: Global ATP → Reporting → Product Availability. Enter the following data: Field Name or Data Type

Values

Product

T-F11##

Maxitec R-3100

Location

2400

Milan

Business Event

A

Sales order

Choose Execute. 4-7-1 How large is the ATP quantity in DC 2400 Milan? 50 PCS 4-8

Use the SAP APO simulation component to check if an order for 75 pieces of product TF11## can be delivered next week from location 2400 (Milan DC). Choose SAP APO Easy Access menu: Global ATP → Reporting → ATP Simulation. Enter the following data: Field Name or Data Type

Values

Product

T-F11##

Maxitec R-3100

Location

2400

DC Milan

Check Mode

030

Business Event

A

Material Availability Date

Monday next week

Requirement Quantity

75 PC

4.8.1

Sales order

Can all 75 pieces of the product be delivered next week?

No, 50 pieces are confirmed for next Monday and an additional 25 pieces are confirmed for the end of the checking horizon. Choose Continue without confirming.

(C) SAP AG

SCM670

37

4-9

Create a sales order for 75 pieces of product T-F11## in SAP R/3. Have a look at the ATP check results. Log on to the SAP R/3 system. Call the transaction VA01 (Create Sales Order). Enter the following data: Field Name or Data Type

Values

Order Type

OR

Standard order

Sales Organization

2400

Italy, Milan

Distribution Channel

10

Final customer sales

Division

00

Cross-division

Sold-To Party

2402

Jashanmal Int Tra Co

PO Number

PO-##

Requested Delivery Date

One week from today’s date

Delivering Plant

2400

DC Milan

Material

T-F11##

Maxitec R-3100

Quantity

75

Note: The delivering plant should appear by default when you choose Enter. Verify that 2400 has been selected. If 2400 has not been selected, correct the field value. Choose Enter. Choose Enter if you receive the message “Change in invoice date: The billing date is redetermined.” This message has no impact on the ATP check. 4-9-1 What are the results of the availability check? 50 pieces can be confirmed for next Monday and an additional 25 pieces can be confirmed for the end of the checking horizon. Choose Delivery Proposal on the APO Availability Check: Delivery Proposal screen to accept the delivery proposal. 4-9-2 How many schedule lines are there, and what are their dates? Two schedule lines on the dates – delivery date, checking horizon date Choose your item on the Create Standard Order: Overview screen. Select Schedule lines for items at the bottom of the screen or choose Goto → Items → Schedule Lines. Save the sales order.

(C) SAP AG

SCM670

38

4-10

After saving the SAP R/3 sales order, have a look at the inventory situation of your material in SAP APO. Use the Product View to display your inventory status. Choose SAP APO Easy Access menu: Production Planning → Interactive Production Planning → Product View. Enter planning version 000, product T-F11##, location 2400. 4-10-1 What is the current inventory of the product? 50 pieces 4-10-2 What are the current requirements for the product? 75 pieces: 50 pieces on the first confirmed material availability date and 25 pieces on the second confirmed material availability date

(C) SAP AG

SCM670

39

5 Check Against Product Allocations

Contents:  Product allocation object  Characteristics  Product allocation group  Product allocation procedure  Consumption

 SAP AG 2003

(C) SAP AG

SCM670

1

5.2 Check Against Product Allocations: Objectives

At the conclusion of this unit, you will be able to:  Define the object and the characteristics of the check against product allocations (the check is also referred to simply as "product allocation")  Assign product allocation objects, product allocation groups, and product allocation procedures to products  Describe the interaction of the planning area in Demand Planning with product allocation planning  Prepare and implement product allocation in ATP

 SAP AG 2003

(C) SAP AG

SCM670

2

5.3 Check Against Product Allocations: Course Overview Diagram 1

Course Overview 2 2

Global ATP / OLTP Interface 3 3

Check Method Selection 4

Product Availability Check

5 Check Against Product Allocations 6 7 8 9

Rules-Based Availability Check Production Within the ATP Check

Backorder Processing

Scheduling

 SAP AG 2003

(C) SAP AG

SCM670

3

5.4 Check Against Product Allocations: Business Scenario

 Maxitec Ltd.'s production output is smaller than market demand. To prevent the first customer exhausting all of your stock, you define product allocations by various characteristics such as customers, regions, and sales channels.  You plan necessary sales restrictions as product allocations in Demand Planning planning areas.  Additional product allocation problems with regard to the limited availability of components procured from a supplier can also cause sales constraints in future periods.

 SAP AG 2003

(C) SAP AG

SCM670

4

5.5 What Is Product Allocation?

 Managing demand (requirements) when there is constrained supply

DEMAND

SUPPLY 6/01

7/01

8/01

9/01

 SAP AG 2003



Competitive order processing that aims to deliver the requested quantity to the customer at the requested time demands precise planning and control mechanisms. Unpredictable problems, such as breakdowns in production or increased demand, can lead to critical situations in order processing and must be brought under control before they develop further.



Product allocation provides this sort of control, and enables your company to avoid critical situations in demand and procurement. An equal allocation of products in short supply must be possible, as must a speedy reaction to bottlenecks and changing market situations.

Depending on the period, you can allocate products for specific customers or regions. If you use product allocation in situations in which a product is in short supply, you can avoid allocating the entire available quantity to the first customer, which would either delay the confirmation of subsequent sales orders, or make confirmation impossible.  The product allocation function allows you to manage the supply of scarce products to customers so that each customer receives an allocated amount.  A product allocation check can act as a secondary check against the quantity requested in the sales order. First, a basic ATP check can be performed against stock and receipts possibly resulting in a lower confirmed quantity due to inadequate stock. This confirmed quantity can be checked against the product allocation quota, possibly further reducing the confirmed quantity. 

(C) SAP AG

SCM670

5

5.6 Check Against Product Allocations

Quantity

June ‘01

July ‘01

Aug. ‘01

Sep. ‘01

Product allocation quantity

Requested quantity

Used product allocation quantity = actual order quantity

Confirmed quantity

Time

 SAP AG 2003

The control process for product allocation enables the user to manage product allocations at specific product levels and for various product groups. Product allocation encompasses internal product allocations for sales organizations and distribution channels, as well as for external customer groups and specific customers.  The system also takes into account the different control phases that exist for product allocations during the overall constraint period. There might be phases without constraints or the reason for the check against product allocations may change over time. 

(C) SAP AG

SCM670

6

5.7 Elements of the Check Against Product Allocations

Product master record ____________ ____________ Procedure ____________ Connection to product allocationgroup

Procedure Obj. 1

12.01

Procedurestep Obj. 2 determines Obj. 3 prod.alloc. group

06.02

Production method Component

12.02 Specific type of material

Characteristic hierarchyfor object

Plannedprod. allocationobject Product Timeseries of planned a lloca tion time allocations inplanning Product se ries area allocationgroup

Allocated quantity

Committed quantity

Requirement

 SAP AG 2003

Product allocations are assigned to a product allocation object. The product allocation object is the reason for allocating quantities, and can be one of the following:  Product (personal computer) or a product group  Component (processor)  Season (summer, winter)  Production line  The reason for product allocations may vary in different phases of the product life cycle.  This figure above shows the data flow: The product master determines the product allocation procedure. Each step in the procedure represents a product allocation group with an associated product allocation object and a set of characteristics for planning a time series of product allocation quantities.  The planning area is where you plan the planned product allocation quantities for the characteristics of the product allocation group. This data has to be copied to the product allocation group on an on-going basis. 

(C) SAP AG

SCM670

7

5.8 Product Allocation Object

JUNE Mo Tu We Th Fr Sa Su

Update date

Work center problems

WEEK:

21

22

Component shortage

23

24

25

26

 SAP AG 2003

 

 



The system takes into account different product allocation control phases during the overall constraint period. You can assign several product allocation objects to the product allocation procedure. A validity period exists for each object. The system determines the relevant object on the basis of the check date. The system then uses this object to determine the corresponding planning hierarchy that contains the product allocations. Objects are always valid from the end date of the last object. To switch off the product allocation for a certain period, you have to define a dummy object and set it to inactive. The system allows three types of check dates:  Delivery date  Material availability date  Planned goods issue date You can maintain time-dependent conversion factors for your product allocation objects in Customizing.

(C) SAP AG

SCM670

8

5.9 Product Allocation Group ATP time series in SAP liveCache with the product allocation object as “key” Contains group of characteristics and key figures  Characteristics: define the product allocation criteria  Key figures: planned and committed quantities

Defines controls for accessing product allocation data  Communication structure  Check date

Product Allocation Group

 Time buckets profile  Fiscal year variant  Consumption period

Characteristics Object VKORG KUNNR Product allocation quantities Values Month Month Month Month

 SAP AG 2003



The product allocation function combines planning tools with real-time ATP functionality. The info structure is partially replaced by the product allocation group. The product allocation group defines a group of characteristics and is used for saving product allocation quantities with their assignments.



Within the product allocation group, the planning hierarchy is replaced by the characteristics combination. The characteristics combination contains the values of the characteristics from the current sales order and, as such, corresponds to the lowest level of the planning hierarchy in which all characteristics are assigned.

(C) SAP AG

SCM670

9

5.10 Product Allocation Procedure Product allocation procedure = Multilevel product allocation Sales order: 100 pieces Customer Region Product Alloc atio n Obj ect

Distribution Channel

50 pieces

Product Allocation Obj ec t

70 pieces 60 pieces Confirmed quantity: 50 pieces (= Logical ‘AND’)

 SAP AG 2003

     

Product allocation procedures are formed from multiple steps of product allocation groups. When a new order is checked, each step (product allocation group) is evaluated sequentially. The result of the preceding step is applied to the subsequent step. The final result of the product allocation check in the product allocation procedure is calculated from a logical ‘AND’ offered by each of the product allocation groups. In the example shown, the smallest quantity (50 pieces) is determined by the product allocation group with regard to the customer characteristics combinations. In SAP APO, you can use a sequence of product allocation procedures to confirm additional quantities that have been planned in a different planning area. Product allocation procedures containing more than one allocation group are only possible for a cumulated check against product allocations.

(C) SAP AG

SCM670

10

5.11 Relationship Between Document and Product Allocation Quantity Order

Order characteristics:

Material master rec.

VKORG: 2400

4711

KUNNR: 2402

Prod. All. Proced.

Delivery date: April

Prod. Alloc. Procedure Step:

HOMEPC

Planning Area Prod. All. Grp

Product Allocation Group Characteristics: Object Values:

VKORG KUNNR Product allocation quantities

HOMEPC

2400

2402

HOMEPC

2500

2300

100

100

50

50

March April

50

100

50

50

May

J une

SAP AG 2003



The product allocation procedure groups products for the purpose of product allocation. Using the product allocation procedure, you control if a check against product allocations is performed for this product and, if so, against which product allocation quantity.



The product allocation procedure sets up the connection between the product and the related product allocation quantity in the product allocation group.

(C) SAP AG

SCM670

11

5.12 Requirements Class  SAP APO - The requirements class and the schedule line type in SAP R/3 can be used as criteria to decide if the procedure from SAP R/3 or from SAP APO should be used.  If product allocation is deactivated in the requirements class or in the schedule line type in SAP R/3, the procedure from SAP APO is used. If product allocation is activated in the requirements class and in the schedule line type in SAP R/3, then the procedure from SAP R/3 is used.

R/3

Customizing -> Sales and Distribution

Basic Functions -> Availability Check and Transfer of Requirements -> Availability Check -> Availability Check Against Product Allocation -> -> Define Flow According To Requirement Category -> Process Flow For Each Schedule Line Category  SAP AG 2003

(C) SAP AG

SCM670

12

5.13 Discrete Product Allocation

750

Available product allocation:

500

* 250 unused pieces

Order qty

Prod. alloc. qty

250

500 pieces

from March are not available

0

March April May

June

July

Current period

 SAP AG 2003

There are two product allocation methods in the system:  Discrete product allocation  Cumulative product allocation (also available in SAP R/3 since version 4.0)  If you do not set the Cumulative indicator in the Customizing activity Maintain Product Allocation Procedure within the step definition, the system uses the discrete product allocation method.  Using this discrete method, the system offsets the quantity confirmed in the sales document against the product allocation quantity. The system only uses the product allocation quantity from the current and future periods (unused product allocation quantities from past periods are not taken into account). If you use this discrete method, you cannot use the following product allocation functions:  Consumption periods  Product allocation steps – only one step is allowed 

(C) SAP AG

SCM670

13

5.14 Cumulative Product Allocation

1500

Available product allocation:

1000

750 pieces * 250 unused pieces

500

from March are available

0

March April

May

June

July

Current period

 SAP AG 2003

If you set the Cumulative indicator in the Customizing activity Maintain Product Allocation Procedure, the system uses the cumulative product allocation method.  Cumulative product allocation allows you to use:  Product allocation steps: You can define multiple product allocation steps with different product allocation groups.  Consumption periods: You can define a number of past and future periods to be used as valid consumption periods.  The number of past periods identifies the number of periods before the product allocation date in the order that can be used for calculating unused product allocations. The unused product allocation quantities of these past periods are then cumulated before product allocation is checked for the current period.  The number of future periods identifies the number of periods after the product allocation date in the order and can be used to calculate future product allocations. If the requested quantity is not confirmed within the future periods, it remains unconfirmed. 

(C) SAP AG

SCM670

14

5.15 Product Allocation: Consumption Period -2 months

+1 month

40 20 40 20

80

40

March

20

April

May

June

July

Order 100 pieces  SAP AG 2003

If you are using cumulative product allocation, you can define a consumption period for each product allocation group.  The consumption period determines how many past and future periods are taken into account in the check against product allocations.  Unused product allocation quantities from past periods are cumulated.  Future periods can only be used for creating a delivery proposal consisting of multiple partial deliveries. 

(C) SAP AG

SCM670

15

5.16 Sequence of Product Allocation Procedures Product allocation procedure 1

Sales order: 100 pieces

(Product master) Product allocation procedure 2 (Additional procedure(s), read from product allocation procedure sequence specified in product master)

Customer Region Distribution channel

Product Allocation Obj ect

Product Allocatio n Obj e ct

50 pieces 70 pieces 60 pieces

Sales organization Country Product Allocatio n Obj ect

Distribution channel

Product Alloc atio n Obj ect

40 pieces 35 pieces 45 pieces

Confirmed quantity: 50 + 35 = 85 pieces (= Logical ‘OR’)  SAP AG 2003

The remaining open quantity from the previous check of the product allocation procedure is cumulated for the next entry in the sequence of product allocation procedures.  The system ignores the entry for the product allocation procedure in the product master record if it is also included in the sequence of product allocation procedures.  The final result of the product allocation check in the product allocation procedure is calculated as the logical ‘OR’ offered by each of the product allocation procedures. 

(C) SAP AG

SCM670

16

5.17 Product Allocation Group: Planning Data in ATP Plan product allocations in the planning area or in the SAP R/3 info structure using characteristics Transfer planning allocations to internal structures in SAP APO – product allocation group Product allocation group Characteristics combination: Product allocation object, customer group, customers

O,A,A1 O,A,A2 O,A,* 150 pcs 250 pcs 600 pcs

O,B,B1 O,B,B2 O,B,* 400 pcs 300 pcs 600 pcs

O,*,* 2700 pcs

Value of characteristics specified in planning Collective characteristics maintained in planning  SAP AG 2003



This lowest level includes all characteristics combinations that represent the "nodes" of the planning tree.

(C) SAP AG

SCM670

17

5.18 Check Against Product Allocations: Planning

Product allocation object O Customer group

A 1000 pcs

B 1300 pcs

∗ 2700 pcs

Customers

A1 A2 ∗ 150 pcs 250 pcs 600 pcs

B1 B2 ∗ 400 pcs 300 pcs 600 pcs

∗ 2700 pcs

Value of characteristics specified in planning Remaining collective characteristics maintained in planning  SAP AG 2003

You can maintain product allocations for customer groups or sales organizations, for example, as well as for individual customers. The system can then perform availability checks in conjunction with product allocation checks.  In planning (Demand Planning, SAP R/3, or external), you establish a hierarchy with product allocation quantities for specific characteristic values. In addition, you can define collective characteristics.  For product allocation in SAP APO, however, only the lowest level is visible.  In Demand Planning (DP), as in flexible planning, all levels can be planned and downloaded into a product allocation group. 

(C) SAP AG

SCM670

18

5.19 Connection of Product Allocation Group to Planning Area Planning book I

Planning book II

Planning Planning area area Time series

SAP liveCache

Connection to planning area

Planning area Version number InfoObjects

Determine/Assign  Object  Characteristics  Key figure  Time buckets profile Prod. alloc. group no.

 SAP AG 2003

Object Char.1 Char.2 Char.3

KONOB Customer Sales org. Region



In this step, you maintain the planning area assignment to the product allocation group. The assignment of the planning area is required because the characteristics of the product allocation group have different names than those of the InfoObjects in the planning area. You must assign all characteristics of a product allocation group to an InfoObject. You can assign an InfoObject to several characteristics.



However, it is not necessary to assign a characteristic to every InfoObject. The system aggregates or disaggregates (depending on the copying direction) using InfoObjects that have not been assigned.



In planning, characteristic values are saved in either planning areas or in SAP R/3 info structures. This planning data is transferred to the product allocation group.



A product allocation time series is chosen in the check against product allocations using a characteristics combination. The check is then performed against this time series. If the characteristics combination has been defined, all product allocation quantities can be planned (for example, from the market level to the customer level).

An active check against product allocations is carried out through the sales order together with the availability check. Based on the check date (delivery date, goods issue date, material availability date), you can ensure that the required quantity does not exceed the product allocation quantity.  There are two modes of connection to planning areas; it is possible to switch between modes: 

(C) SAP AG

SCM670

19

 Asynchronous connection: Copying of data from and to planning areas with the advantage that planning and availability checks take place separately and there are no locking issues  Synchronous connection: Direct access to planning results in the planning area – no copying necessary

(C) SAP AG

SCM670

20

5.20 Data Transfer from Planning Area Planning book I

Planning book II

Planning Planning area area Time series

SAP liveCache

Copy  Object  Characteristic  Product allocation quantity  Incoming orders quantity

Planning area Planning version Time buckets profile Fiscal year

Product allocation group Object Char.1 Char.2 Char.3

KONOB Customer Sales org. Region

 SAP AG 2003



If you have made the connection to the planning area, you can decide whether, in product allocation, the data access should take place directly in the planning area (that is, online in SAP liveCache) or if you want to check in the product allocation group. If you check in the product allocation group, the characteristic values and the product allocation quantities must be transferred from DP to the product allocation group. The data is transferred either manually or in the background using the following reports:  Transfer data from planning area  Characteristics combination from planning area



You can find these reports in the SAP Easy Access menu under Global ATP -> Environment -> Product Allocations -> Connection.

(C) SAP AG

SCM670

21

5.21 Data Transfer to Planning Area Planning book I

Planning book II

Planning Planning area area Time series

SAP liveCache

Planning area Planning version Period: from ... to

Copy  Product allocation quantity  Incoming orders quantity  List of new characteristic combinations Product allocation group Object Char.1 Char.2 Char.3

KONOB Incoming orders qty Customer 20 Customer group 15 Region 20

 SAP AG 2003



In this step, you copy the product allocation quantities to a planning area. If you carry out planning again, you must copy the data (incoming order quantities and, if necessary, existing product allocation quantities) from the product allocation group to the planning area. Afterwards, you carry out planning against the updated history and copy the planned product allocation data from the planning area to the product allocation group.



From the SAP Easy Access menu, choose Global ATP -> Environment -> Product Allocations -> Connection -> Transfer Data to Planning Area.



In the Transfer Scope frame, you can set the following indicators:  Transfer incoming orders quantities: If you have set this indicator, the incoming orders quantities are included when data is copied from the product allocation group.  Transfer product allocations: If you have set this indicator, the product allocation quantities are included when the data is copied from the product allocation group.

(C) SAP AG

SCM670

22

5.22 Downloading Information from the SAP R/3 System

R/3

 

(OLTP) (OLTP)

Info structure incl. characteristic values Planning hierarchy

Customizing settings  Structure  Objects  Procedures

APO

Integration model (CIF)

Planning area

 SAP AG 2003

Product allocation characteristics are defined in SAP R/3 using info structures. These characteristics can be transferred to SAP APO, where the product allocation information is stored in the product allocation group in SAP liveCache and can be used for the ATP check. The following transactions are relevant for the data transfer:  Transaction QTSA for the transfer of product allocation quantities from the SAP R/3 info structure to the SAP APO product allocation group  Transaction QTSP for the transfer of product allocation procedures from SAP R/3 to SAP APO  After the transfer of SAP R/3 Customizing, internal technical objects such as translation tables, access coding, and so on, are generated automatically. If there is a transport error, the time stamps for the objects must be reset. 

(C) SAP AG

SCM670

23

5.23 Product Allocation Determination

Sales order

Date 7/01

Product master

Product allocation procedure

Procedure sequence

Product allocation procedure

Procedure step

Paint= Vacation= 9/01– 11/01 6/01– 8/01 3/01 – 5/01

Prod. alloc. object

Product allocation group

Paint Vacation

Prod. alloc. time series

 SAP AG 2003

     





Upon entry of the sales order into the OLTP system, the product allocation procedure is read from the ATP product master record. If a sequence of product allocation procedures exists, the subsequent procedures are read from this product allocation sequence. There could be a number of steps for each product allocation procedure. Each step is associated with a product allocation group. In each product allocation group there may be multiple product allocation objects that cover a corresponding data area. For each product allocation object, there is a time series of planned product allocation quantities associated with a set of characteristics. The first procedure is determined from the ATP tab page in the product master, corresponding to the product of the sales order item. If the location-dependent product allocation procedure is missing, then the location-independent procedure is used. The first step in the procedure is examined. Based on the sales order date, a valid product allocation object and its associated characteristics/time series is examined, if and only if there is a matching characteristic with or without the wildcard character. If there are matching characteristics and remaining available quantities, a product allocation is made. If the first step fails, the second/next step is examined. Each step should be designed to check for product allocation objects with fewer or more general characteristics (Example: From customer/DC level in step 1 to DC level only).

(C) SAP AG

SCM670

24

5.24 Check Against Product Allocations: Summary

You are now able to:  Define the object and the characteristics of the check against product allocations (also referred to as "product allocation")  Assign product allocation objects, product allocation groups, and product allocation procedures to the product master  Discuss the planning-data-related interaction of the planning area and product allocation  Prepare and implement product allocation in ATP

 SAP AG 2003

(C) SAP AG

SCM670

25

5.25Check Against Product Allocations

Exercises

Unit: Check Against Product Allocations

At the conclusion of this exercise, you will be able to: •

Set up Customizing for product allocation checks

•

Plan the product allocations on the basis of Demand Planning planning areas

•

Transfer product allocations from Demand Planning planning areas to the product allocation group

•

Use the Global ATP simulation component for availability checks that are restricted by product allocations

At Maxitec Ltd., all products are planned and checked for availability in SAP APO. Due to capacity and component limitations some products cannot be produced in large enough quantities to meet growing customer demand. Maxitec Ltd. has decided to manage ATP quantities for these products using the product allocation function in SAP APO. Your task is to set up Customizing for checks against product allocations for the PC product T-F12##. To verify the settings, you also have to simulate an ATP product allocation check for the PC product in SAP APO. You will use T-F12## as your PC product, where ## is your group number. In addition, you will use location 2400 as your distribution center (DC). This product and distribution center are used throughout these product allocation exercises. 5-1

Display the configuration for the check against product allocations and verify that the required data has been set up to perform an ATP check. 5-1-1 Verify that the following characteristics have been set up in the field catalog for use in ATP product allocation checks: Sold-To Party _____________________________________________ Product __________________________________________________ Sales Organization _______________________________________ 5-1-2 Verify that HOMEPC has been defined as the product allocation object (characteristic) value. If you cannot find it, notify the instructor. Do not add the value yourself, as this value is used by all course participants.

(C) SAP AG

SCM670

26

5-2

Create product allocation group S140##. Use the material availability date as your check date and indicate that the product allocation values will be maintained in monthly time buckets. Assign the characteristics product allocation object, sold-to-party, product, and sales organization to the product allocation group. Allow orders to consume permitted product allocations in the future. 5-2-1 Create your product allocation group. The product allocation group is used for saving product allocation quantities and their assignments. Using a characteristics combination (the values of characteristic from the current sales order), the system chooses the correct product allocation for allocation checking. Choose Enter to acknowledge the warning that an error occurred when generating internal objects. 5-2-2 Assign the characteristics product allocation object, sold-to-party, product, and sales organization to your new product allocation group. Characteristic

Sequence

Description

KONOB

1

Prod. allocation obj.

KUNNR

2

Sold-to party

MATNR

3

Product

VKORG

4

Sales organization

Choose Enter to acknowledge the warning that an error occurred when generating internal objects. From the New Entries screen, return to the overview screen for the product allocation group definition by twice selecting Back. 5-2-3 Define the consumption period for your product allocation group for forward consumption of one period, and without past periods.

(C) SAP AG

SCM670

27

5-3

Define a new product allocation procedure: P140##. Allow a cumulative check to be performed. Define your new product allocation group, S140##, as the first step of this procedure. Define HOMEPC as the characteristic value controlling the use of the product allocation procedure. 5-3-1 Create your procedure, P140##, with description Procedure ##. Select cumulative product allocation. 5-3-2 Create the step for your procedure. Step

Step Name

Product Allocation Group

Wildcard Character

10

First step

S140##

#

Choose Save. Confirm the Prompt for Customizing Request. 5-3-3 Define HOMEPC as the characteristic value controlling the use of the product allocation step sequence Select your new product allocation step, S140##. Double-click Control. Choose New Entries. Insert the object in the procedure. Valid to

Object

Active

Factor

31.12. current year

HOMEPC

Yes

1

Choose Save. Confirm the Prompt for Customizing Request.

(C) SAP AG

SCM670

28

5-4

Create a connection between the planning area and your product allocation group. The product allocation quantities planned in exercise 5-6 are saved in a planning area. To be able to use the values for product allocation, you must transfer the results to your product allocation group. This step links the characteristics and quantities of the planning area to the characteristics and quantities of the product allocation group. 5-4-1 Assign the planning area ATP_ALLOCATION to the product allocation group S140##. Product Allocation Planning Area Group S140##

Version

Time Buckets Profile

ATP_ALLOCATION

5-4-2 Define the link between the product allocation group characteristics and planning area characteristics. Characteristic

InfoObject

KONOB

9AKONOB

KUNNR

CUST

MATNR

9AMATNR

VKORG

9AVKORG

5-4-3 Define the link between product allocation group key figures and planning area key figures. Key Figure

InfoObject

AEMENGE

PC29Q

(Actual sales qty CBF)

KCQTY

PC30Q

(Open allocation qty CBF)

Choose Save. Confirm the Prompt for Customizing Request.

(C) SAP AG

SCM670

29

5-5

Generate the objects for your product allocation group S140##. The product allocation process uses objects that are dependent on Customizing. The Customizing objects are generated as follows: •

Automatically when the Customizing settings are saved

•

Manually using this program if you have transported the Customizing settings from another system to SAP APO

•

Manually using this program if you have implemented an SAP Note in the source code

The objects translation table, access coding, search help, and display screen are generated automatically according to the settings you made in the product allocation group. On execution of this function, all objects whose time stamps are invalid are generated again. If you want to generate all internal objects, you must first reset the time stamp for these internal objects (separate menu path). 5-6

Create a product allocation that limits customer 2402 in sales organization 2400 to a quantity of 50 pieces of product T-F12## per month. This allocation is valid for four months, starting next month. 5-6-1

Product allocation quantities are maintained in Demand Planning planning areas. Planning book ATP_ALLOC and planning area ATP_ALLOC have been assigned to your user ID for this exercise. Next M

M+1

M+2

M+3

50

50

50

50

Actual Data Planned

Save your product allocations. 5-6-2

(C) SAP AG

Since your are populating the Product Allocation Time Series Asyncronously (batch), you must identify the characteristic combinations that will be valid for this procution allocation procecdure. Copy the characteristic combinations from your planning area ATP_ALLOCATION to your allocation group S140##.

SCM670

30

5-7

Transfer your planned product allocation quantities from your planning area to the product allocation group. In the previous steps of this exercise, you did the following: •

Linked the planning area and the product allocation group

•

Regenerated our product allocation group objects

•

Planned the product allocations in the planning area

In this step, you will transfer the planned quantities entered into your planning area (in step 5-6) to the product allocation group for the ATP check. Planning Area:

ATP_ALLOCATION

Planning Version:

000

Product Allocation Group:

S140##

Copy product allocation object:

Do not set this indicator.

Period:

Choose Enter. A time period appears. Enter a period from the start of next month to the end of next month + 3.

Indicators at bottom of screen: Do not set these four indicators. Choose Enter. If there are no errors, choose Execute. 5-8

Assign the product allocation procedure to the product master. Determine the ATP group and the check mode assigned to your product, T-F12##, in location 2400. Enter the product allocation procedure, P140##, in the Loc-dep. Proced. (location-dependent product allocation procedure) field. 5-8-1 Have cross-location product allocation procedures been defined? _________________________________________________ 5-8-2 Has a location-dependent product allocation procedure been previously defined? _________________________________________________ 5-8-3 Which ATP group is valid for this product? _________________________________________________ Which check mode is valid for this product? _________________________________________________ Save the product master T-F12##.

(C) SAP AG

SCM670

31

5-9

Using the check mode determined in the previous exercise step, review the check instructions to determine which ATP check methods are used when a sales order (business event) is processed. Note: In this exercise step, you do not want to execute any rules nor do you want to plan production. 5-9-1 Which check instructions must exist for the check against product allocations to be successful? Product check: _____________________________________________________ Check against product allocations: _____________________________________________________ Rules-based ATP check: _____________________________________________________ Start production: _____________________________________________________

5-10

Examine the SAP APO product allocation report for an overview of the time series for the product allocation group S140##, the planned and remaining product allocation quantities, and the incoming sales order quantities for product T-F12##. Enter the following data on the initial screen: Product Allocation Group:

S140##

Product:

T-F12##

The corresponding product allocation procedure and the first product allocation step appear automatically in the relevant fields. Choose Enter. A separate section appears for the product allocation group. Enter the characteristic values for: Sold-To Party:

0000002402

Product:

T-F12##

Product Allocation Object:

HOMEPC

Sales Organization:

2400

To review the current status of the product allocation quantity, choose Product Allocation Group.

(C) SAP AG

SCM670

32

5-11

Perform an ATP simulation for your product T-F12## and DC location 2400 (Milan). Enter a required quantity of 300 pieces for the first Monday of next month. Enter the following information: Product:

T-F12##

Location:

2400

Check Mode:

030

Business Event:

A

Material Availability Date:

First Monday of next month

Requirement Quantity:

300

Unit:

PC

Choose Execute. A dialog box appears in which you can enter the characteristic values for product allocation. Define the following characteristics: Sold-To Party:

0000002402

Product:

T-F12##

Sales Organization:

2400

5-11-1

What are the results of the ATP check? 1.3.1

(C) SAP AG

____________________________________________________

SCM670

33

5.26Check Against Product Allocations Solutions Unit: Check Against Product Allocations

5-1

Display the configuration for the check against product allocations and verify that the required data has been set up to perform an ATP check. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Product Allocations → Maintain Field Catalog. 5-1-1 Verify that the following characteristics have been set up in the field catalog for use in ATP product allocation checks: Sold-To Party

Yes

Product

Yes

Sales Organization

Yes

Note: New characteristics must be entered directly from the communication structure /SAPAPO/KOMGO into the catalog table using New Entries. For more information, see the Global ATP documentation. 5-1-2 Verify that HOMEPC has been defined as the product allocation object (characteristic) value. If you cannot find it, notify the instructor. Do not add the value yourself, as this value is used by all course participants. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Product Allocations → Maintain Product Allocation Object. Note: The product allocation object is a special characteristic used by the check against product allocations. It is predefined by SAP as the characteristic KONOB.

(C) SAP AG

SCM670

34

5-2

Create product allocation group S140##. Use the material availability date as your check date and indicate that the product allocation values will be maintained in monthly time buckets. Assign the characteristics product allocation object, sold-to-party, product, and sales organization to the product allocation group. Allow orders to consume permitted product allocations in the future. 5-2-1 Create your product allocation group. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Product Allocations → Maintain Product Allocation Group. The product allocation group is used for saving product allocation quantities and their assignments. Using a characteristics combination (the values of characteristic from the current sales order), the system chooses the correct product allocation for allocation checking. Choose New Entries. Enter your product allocation group, S140##. Do not select the Check planning area or Use config. char. (Use configuration characteristics) indicators. In the Check Date field, enter MBDAT (material availability date). Note: Comm. Structure (Communication Structure) is filled automatically with MCVBEP. Enter Month in the Time bkts prfl (Time buckets profile) field. Save the product allocation group. Create a new Customizing request number and confirm the Customizing request. Choose Enter to acknowledge the warning that an error occurred when generating internal objects. From the product allocation group details screen, go back one step to the overview screen.

(C) SAP AG

SCM670

35

5-2-2 Assign the characteristics product allocation object, sold-to-party, product, and sales organization to your new product allocation group. From the product allocation group overview screen: Select your product allocation group, S140##, and choose Characteristics. Choose New Entries. Acknowledge the warning that the characteristics of the product allocation object are missing from the product allocation group. Enter the following characteristics. Note: The KONOB characteristic that corresponds to the product allocation object appears automatically with sequence number one. After selecting each characteristic from the field input help (F4), enter a sequence number. Characteristic

Sequence

Description

KONOB

1

Prod. allocation obj.

KUNNR

2

Sold-to party

MATNR

3

Product

VKORG

4

Sales organization

Choose Enter and then Save. Confirm any prompts for Customizing request. Translation, search, coding, and screens are generated. Choose Enter to acknowledge the warning that an error occurred when generating internal objects. From the New Entries screen, choose Back (twice) to return to the screen for defining the product allocation group. 5-2-3 Define the consumption period for your product allocation group for forward consumption of one period, and without past periods. Select the product allocation group S140##. Double-click Consumption Period. Choose New Entries. Enter the product allocation group S140##. Select the W/oPastPer (No consumption in past periods) indicator for your product allocation group, S140##. Enter forward consumption of one period. Choose Save. Acknowledge the warning. Go back to the Implementation Guide (IMG).

(C) SAP AG

SCM670

36

5-3

Define a new product allocation procedure: P140##. Allow a cumulative check to be performed. Define your new product allocation group, S140##, as the first step of this procedure. Define HOMEPC as the characteristic value controlling the use of the product allocation procedure. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Product Allocations → Maintain Product Allocation Procedure. 5-3-1 Create your procedure, P140##, with the description Procedure ##. Select cumulative product allocation. Choose New Entries. Select the Cumulative indicator. Choose Enter to register the line. 5-3-2 Define the sequence for your procedure. Select your new procedure. Choose Step Sequence. Disregard the message, “No entries found that match selection criteria.” Choose New Entries. Enter the following data for the step: Step

Step Name

Product Allocation Group

Wildcard Character

10

First step

S140##

#

Choose Save. Confirm the Prompt for Customizing Request. 5-3-3 Define HOMEPC as the characteristic value controlling the use of the product allocation step sequence. Select your new product allocation step, 10. Double-click Control. Acknowledge warning, “Individual entries cannot be taken over into the change request.” Choose New Entries. Insert the object in the procedure. Valid to

Object

Active

Factor

31.12. current year

HOMEPC

Yes

1

Choose Save. Choose Back to go back to the Implementation Guide (IMG), acknowledging any warnings as you do so.

(C) SAP AG

SCM670

37

5-4

Create a connection between the planning area and your product allocation group. The product allocation quantities planned in exercise 1-6 are saved in a planning area. To be able to use the values for product allocation, we must transfer the results to your product allocation group. This step links the characteristics and quantities of the planning area to the characteristics and quantities of the product allocation group. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Product Allocations → Maintain Connection to Planning Area. 5-4-1 Assign the planning area ATP_ALLOCATION to the product allocation group S140##. Choose New Entries. Product Allocation Planning Area Group

Version

Time Buckets Profile

S140##

000

M

ATP_ALLOCATION

5-4-2 Define the link between the product allocation group characteristics and planning area characteristics. Select the product allocation group and double-click Characteristics on the left of the screen. Choose New Entries and make the following assignments: Characteristic

InfoObject

KONOB

9AKONOB

KUNNR

CUST

MATNR

9AMATNR

VKORG

9AVKORG

Choose Save. Confirm the Customizing request. Go back one step to the product allocation group assignments screen. 5-4-3 Define the link between product allocation group key figures and planning area key figures. Select your new assignment of product allocation group to planning area. Double-click Key Figure on the left of the screen. Choose New Entries and make the following assignments: Key Figure

InfoObject

AEMENGE

PC29Q

(Actual sales qty CBF)

KCQTY

PC30Q

(Open allocation qty CBF)

Choose Save.

(C) SAP AG

SCM670

38

5-5

Generate the objects for your product allocation group S140##. The product allocation process uses objects that are dependent on Customizing. The Customizing objects are generated as follows: •

Automatically when the Customizing settings are saved •

Manually using this program if you have transported the Customizing settings from another system to SAP APO

•

Manually using this program if you have implemented an SAP Note in the source code

The objects translation table, access coding, search help, and display screen are generated automatically according to the settings you made in the product allocation group. On execution of this function, all objects whose time stamps are invalid are generated again. If you want to generate all internal objects, you must first reset the time stamp for these internal objects (separate menu path). Choose SAP APO Easy Access menu: Global ATP → Environment → Product Allocations → Generation → Generate Objects. Enter your product allocation group S140##. Under Generation from, set the following indicators: Translation table Access coding Search help Display screen Characteristics combinations Choose Execute. A log report appears.

(C) SAP AG

SCM670

39

5-6

Create a product allocation that limits customer 2402 in sales organization 2400 to a quantity of 50 pieces of product T-F12## per month. This allocation is valid for four months, starting next month. 5-6-1

Product allocation quantities are maintained in Demand Planning planning areas. Planning book ATP_ALLOC and planning area ATP_ALLOC have been assigned to your user ID for this exercise. Choose SAP APO Easy Access menu: Demand Planning → Planning → Interactive Demand Planning. Choose the plan ATP_ALLOC in the selection area for the planning book / data view. Double-click the data view ALLOCATIONS to display the fields for the key figure values. Choose Selection Window in the top-left selection area. An Object Selection dialog box appears. Enter the following data in this dialog box: Show field:

APO Product

APO Planning Version:

000

APO Product:

T-F12##

Product Allocation Object: HOMEPC Sales Organization:

2400

Sold-To Party:

2402

Choose Enter. The Show field characteristic value T-F12## is now displayed in your selection area. Double-click product T-F12##. The table on the right-hand side of the screen is now ready for input. Enter planned product allocations of 50 pieces for four months starting from next month. Do not enter any data in the actual data (actual sales quantity). M+1

M+2

M+3

M+4

50

50

50

50

Actual data Planned Save your allocations.

(C) SAP AG

SCM670

40

5-6-2

Since your are populating the Product Allocation Time Series Asyncronously (batch), you must identify the characteristic combinations that will be valid for this procution allocation procecdure. Copy the characteristic combinations from your planning area ATP_ALLOCATION to your allocation group S140##. Choose SAP APO Easy Access menu: Global ATP → Environment → Product Allocations → Connection → Characteristic Combination From Planning Area. Planning Area:

ATP_ALLOCATION

Product Allocation Group:

S140##

Indicators at bottom of screen:

Do not set any indicators.

Choose Enter. If there are no errors, choose Execute. 5-7

Transfer your planned product allocation quantities from your planning area to the product allocation group. In the previous steps of this exercise, you did the following: •

Linked the planning area and the product allocation group

•

Regenerated our product allocation group objects

•

Planned the product allocations in the planning area

In this step, you transfer the planned quantities entered into our planning area (in step 5-6) to the product allocation group for the ATP check. Choose SAP APO Easy Access menu: Global ATP → Environment → Product Allocations → Connection → Copy Data from Planning Area. Planning Area:

ATP_ALLOCATION

Planning Version:

000 – Fills in automatically

Product Allocation Group:

S140## – Fills in automatically

Copy product allocation object:

Do not set this indicator.

Period:

Choose Enter. A time period appears. Enter a period from the start of next month to the end of next month + 3.

Indicators at bottom of screen:

Do not set these four indicators.

Choose Enter. If there are no errors, choose Execute.

(C) SAP AG

SCM670

41

5-8

Assign the product allocation procedure to the product master. Determine the ATP group and the check mode assigned to your product, T-F12##, in location 2400. Enter the product allocation procedure, P140##, in the Loc-dep. Proced. (location-dependent product allocation procedure) field. Choose SAP APO Easy Access menu: Master Data → Product. Enter your product, T-F12##, and your location, 2400. Select the Location indicator. Choose Change. Go to the ATP view in the product master. Enter the product allocation procedure, P140##, in the Loc-Dep. Proced. (locationdependent product allocation procedure) field. This field should be empty. 5-8-1 Have cross-location product allocation procedures been defined? No 5-8-2 Has a location-dependent product allocation procedure been previously defined? No 5-8-3 Which ATP group is valid for this product? 02 5-8-4 Which check mode is valid for this product? 041 Save the product master T-F12##.

(C) SAP AG

SCM670

42

5-9

Using the check mode determined in the previous exercise step, review the check instructions to determine which ATP check methods are used when a sales order (business event) is processed. Note: In this exercise step, you do not want to execute any rules nor do you want to plan production. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → General Settings → Maintain Check Instructions. 5-9-1 Which check instructions must exist for the check against product allocations to be successful? Product check:

First step

Check against product allocations:

Second step

Rules-based ATP:

Do not select

Start production:

Availability check only, no production

ASK THE INSTRUCTOR TO MAKE ANY NECESSARY CHANGES TO THIS GENERAL SETTING. Confirm the Customizing request. In addition, ask the instructor to deactivate the checking horizon in the check control for the ATP group 02 / business event A.

(C) SAP AG

SCM670

43

5-10

Examine the SAP APO product allocation report for an overview of the time series for the product allocation group S140##, the planned and remaining product allocation quantities, and the incoming sales order quantities for product T-F12##. Choose SAP APO Easy Access menu: Global ATP → Reporting → Product Allocations. Enter the following data on the initial screen: Product Allocation Group:

S140##

Product:

T-F12##

The corresponding product allocation procedure and first product allocation step appear automatically in the relevant fields. Choose Enter. A separate section appears for the product allocation group. Enter the characteristic values for: Sold-To Party:

0000002402

Product:

T-F12##

Product Allocation Object:

HOMEPC

Sales Organization:

2400

To review the current status of the product allocation quantity, choose Product Allocation Group.

(C) SAP AG

SCM670

44

5-11

Perform an ATP simulation for your product, T-F12##, and DC location 2400 (Milan). Enter a required quantity of 300 pieces for the first Monday of next month. Choose SAP Easy Access menu: Global ATP → Reporting → ATP Simulation. Enter the following information: Product:

T-F12##

Location:

2400

Check Mode:

041

Business Event:

A

Material Availability Date:

First Monday of next month

Requirement Quantity:

300

Unit:

PC

Choose Execute. A dialog box appears in which you can enter the characteristic values for product allocation. Define the following characteristics: Sold-To Party:

0000002402

Product:

T-F12##

Sales Organization:

2400

5-11-1

What are the results of the ATP check? 50 confirmed for the current month, and 50 for next month

(C) SAP AG

SCM670

45

6 Rules-Based Availability Check

Contents:  Rule maintenance  Rule determination

 SAP AG 2003

(C) SAP AG

SCM670

1

6.2 Rules-Based Availability Check: Objectives

At the conclusion of this unit, you will be able to:  Explain the substitution options and define them in the form of rules in the system  Explain and define the methodology and technology of ATP rule determination  Set up condition records for rule determination

 SAP AG 2003

(C) SAP AG

SCM670

2

6.3 Rules-Based Availability Check: Course Overview Diagram 1

Course Overview 2 2

Global ATP / OLTP Interface 3 3

Check Method Selection 4

Product Availability Check

5 Check Against Product Allocations 6 7 8 9

Rules-Based Availability Check Production Within the ATP Check

Backorder Processing

Scheduling

 SAP AG 2003

(C) SAP AG

SCM670

3

6.4 Rules-Based Availability Check: Business Scenario

 At Maxitec Ltd., a basic ATP check for a customer's requested product in a requested location could not confirm a large enough quantity.  You know of alternative locations that can be checked and also alternative products that can be used to substitute the original product.  You want Global ATP to consider these alternative combinations automatically and check availability.  If you cannot find enough of the requested product to fill the order, you want the system to come up with a proposal to produce the product at the nearest production plant.

 SAP AG 2003

(C) SAP AG

SCM670

4

6.5 Rule Maintenance: Objectives

At the conclusion of this topic, you will be able to:  Explain and define product substitution  Explain and define location determination  Explain and define the PPM substitution  Describe and set up the calculation profile and rule control

 SAP AG 2003

(C) SAP AG

SCM670

5

6.6 Rules-Based ATP Multilevel availability check – Visualization through the “ATP decision cube”

Alternative PPM explosion

Finished product from sales order

Alternative dimensions for advanced methods:  Alternative product  Alternative location  Alternative PPM explosion within production

 Determine path in the "cube" Alternative location(s) Alternative product(s)  SAP AG 2003

 



 



Rules-based availability checking is an iterative process. Rules and the corresponding check results determine the subsequent checking steps in each case. Possible subsequent checking steps include:  Product substitution  Location substitution  PPM substitution, if production is started All subsequent checking steps span the three-dimensional area shown in the illustration above. You can move in any direction and combine any dimensions, for example:  Procure or substitute from an alternative location  Produce in another plant The system stops searching when a check step provides an acceptable result (calculation profile). If no other setting is active, the system summarizes the results of each step until the requested quantity is satisfied. If SD is used in SAP R/3, this leads to the generation of subitems in the corresponding sales order. Rules-based ATP from SAP R/3 is currently only supported by sales order processing in SD and within the multilevel ATP check.

(C) SAP AG

SCM670

6

6.7 Rules-Based ATP: Example

Alternative PPM explosion

Finished product from sales order

Problem Quantity of the item in stock is insufficient in original location. Different basic ATP checks have to be performed in different locations.

Alternative locations Separatelocation activity check instructions Alternative product(s)

Solution  Product substitution  Procurement of substitute product from alternative location  Then production of substitute product in another location

 SAP AG 2003

For example, for a rule from the original product, checking starts in the original location and then checks the following options:  An alternative product in the original location  An alternative product in an alternative location  Production of an alternative product in a third location  This process is only supported in sales order processing and within the multilevel ATP check. 

(C) SAP AG

SCM670

7

6.8 Elements of the Rule re edu c e o r pr re du edu proce itution ure c o t n ed pr on atio t subs n proc i t n i u le stit eterm roduc titutio ol rofi b p u d n p ts n io n bs ntr duc ocatio ocatio PM su le co lculat o r u a 1. P 2. L 3. L 4. P 5. R 6. C

Rule 1

P1

L1

Rule 2

P2

L2

PPM

Rule 3 Rule 4

LP4

R1

B1

R2

B2

R3

B3

R1

B4

 SAP AG 2003

Rules-based ATP checks are based on multiple rules that are executed sequentially. Each rule consists of at least one of the following:  Calculation profile (the results of which are accepted during a check)  Product substitution procedure  Location determination procedure  Location product substitution procedure (as alternative to product substitution and location determination procedure)  PPM substitution procedure  If you use either a product rule or location rule, you must also create rule control parameters (instructions on how to combine the lists of alternative locations and products).  It may be necessary to use several rules, meaning that the strategy used for the customer has to be changed gradually if his/her request cannot be satisfied by an initial approach that only uses substitutions.  A rule is created in integrated rule maintenance (Master Data -> Rule Maintenance). It can be assigned to several processes because rule determination, which has to be executed for an ATP request, is performed in a separate step.  

(C) SAP AG

SCM670

8

6.9 Product Substitution Procedure

Alternative products 

Different types: 0 Substitution chain (including: end of substitution) 1 Network 2 Fan-shaped structure



Control Product Substitution Valid from Valid to T-F13##

T-F14##

Costs

01/01/2001 12/31/2001 10

Reason 0001

 SAP AG 2003

Product substitution procedures allow you to define and control the possible product substitutions that can be made during an ATP check. In addition, product substitution procedures allow you to define a validity period.  In substitution procedures of the type 0 (chain), you cannot enter any costs because the sequence of the substitutions is fixed. 



The selection indicator for chains gives you the opportunity to reflect a technology change within a selection of products. The indicator defines with which product in the product list the substitutions start. Moreover, this indicator can only be evaluated for access strategies 01 and 04.



You should be aware that the requirement quantities and the confirmed quantities from the ATP check always refer to the base unit of measure of the products involved. In a product substitution, the units of measure are not converted if the units change within a substitution.

(C) SAP AG

SCM670

9

6.10 Location Determination Procedure

Location determination procedure 

Determine types: 0 Substitution chain (only serial structures allowed) 1 Network (no restrictions defined) 2 Fan-shaped structure (only single-level substitutions allowed)

 SAP AG 2003



 

   

The location and product substitution procedures and the combination of the resulting lists were introduced to simplify maintenance of the resulting substitutions of location products. The system automatically generates a sequence. With this technique, you do not have to maintain each substitution manually (although this is also possible). A type is assigned to each location determination procedure. The determination type defines the possible combinations of location and product substitutions that are evaluated in a subsequent step. There are four determination types:  Chain  Fan-shaped structure  Network  List: For determining a primary location if called from a system that does not support or determine locations by itself, such as a customer relationship management (CRM) system. You must assign a determination type to each new location determination procedure that you create. The location determination type defines the possible combinations of location and substitute location. If you define the substitution chain as the type of location determination procedure, you must enter the required substitute location directly below the original location in the list. If you select the fan-shaped structure or the network as the type of location determination procedure, you must specify several substitute locations for one location in the same field. The substitute sequence is controlled by costs in the control parameters.

(C) SAP AG

SCM670

10

6.11 Location Substitution: Activity Control Location Substitution Activity Valid from Valid to 2400

2500

0001

01.01.2001 31.12.2001

Costs 10

 Activity: 

Direct delivery



Start production

Original location

0 Availability check 1 Availability check first, then production

1. substitution: ATP check

2 Production directly 

Means of transport



Business event



Check mode

2. substitution: Production

 SAP AG 2003

You create new location determination procedures on the Maintain Location Determination Procedure screen.  You can further restrict location determination by defining a specific validity period for each entry in the substitution list. During a check, this period is then evaluated with the requested delivery date or the corresponding material availability date. These dates have to be within the specified period.  In the standard system, for the confirmation, the ATP check currently only considers the ATP quantities of those receipts within the defined period. All other elements are excluded, which can mean that existing stock is not taken into account if today’s date is not within the relevant interval.  In an activity, you maintain several actions to be taken if a location determination is carried out. These include: 

 Calling production  Business event: This can influence which check control and which scope of check are used. In conjunction with the check mode, it can also determine which check instructions to follow.  Check mode for the location determination activity: For the location determination, you determine which basic method or combination of basic methods you want to use in the availability check.

(C) SAP AG

SCM670

11

 Means of transport in third-party order processing: Third-party in this context stands for confirmation and delivery from a substituted location. The means of transport is then evaluated for transportation and shipment scheduling from the delivering location to the customer.  You can control substitution processing by specifying costs for each entry in fan-shaped structures. The system sorts the results list according to the costs (ascending).

(C) SAP AG

SCM670

12

6.12 PPM Substitution Transportation zone

Determination type for fulfillment

Ship-to

1 FP

Local stock Plant A

6

5

FP SFP Prod

2

SFP Prod Plant B

4

Transport

Stock in transit

3

FP

Many criteria exist

FP = Finished Product / SFP = Semifinished Product / Prod = Production  SAP AG 2003



You can define the production level and method in the rule by saving several PPMs for a location product in a PPM substitution procedure.



To do so, create a PPM substitution procedure in integrated rule maintenance. In this PPM substitution procedure, you can enter several production process models for each location product. You assign a PPM substitution procedure to a rule. Note that the system still requires another substitution procedure in addition to the PPM substitution procedure.



If you wish to carry out a PPM substitution, you must have configured production so that Production Planning and Detailed Scheduling (PP/DS) can be called. SAP recommends that you configure production using the location determination activity in integrated rule maintenance. This means that an ATP check can be carried out for a missing PPM in the substitution procedure without PP/DS being called. If you have configured production in the check instructions, PP/DS is still called for a missing PPM (PPM is initial).



Note: This option is only valid if no more than one substitution is allowed.

(C) SAP AG

SCM670

13

6.13 PPM Substitution Procedure

 Definition of a PPM substitution procedure  Assignment of multiple PPMs to location products within a procedure  Assignment of levels to define a sequence 

Levels are interpreted by their value.



The processing sequence can be defined.

 SAP AG 2003



You define whether or not the PPM substitution procedure should work with a substitution procedure.



PPM substitution procedure using substitution procedure (standard case):  If you want the system to find PPMs for the substitutions, then the rule must contain other substitution procedures in addition to the PPM substitution procedure. The location products in the PPM substitution procedure must match the substitutions in content.



PPM substitution procedure without substitution procedure:  The PPM substitution procedure normally always needs another substitution procedure. You can, however, work without an additional substitution procedure if you have set the Start immediately rule in the check instructions. You maintain the check instructions in SAP APO Customizing under Global ATP -> General Settings -> Maintain Check Instructions.  The rule evaluation is then carried out immediately and only on the generating requirement. Ensure that a PPM is maintained for the corresponding requested location product.  Set the Rules-based ATP indicator in the check instructions.  You have created a rule control that defines the evaluation of several procedures (a substitution procedure and a PPM procedure). In this rule control, you also select a substitution level for the PPM substitution.

(C) SAP AG

SCM670

14

6.14 Rule Control

 Product/location and PPM procedure: Evaluation strategy 

Management of the individual procedures of a rule

 Combination of product and location substitutions 

Access strategy of substitution lists



Combination of substitution lists

 PPM substitutions: Substitution level

 Controls the results of the entire rule

?  SAP AG 2003

 

  

Settings for the rule control consist of general settings, a list sequence, product strategy, and location strategy. The general settings allow you to specify if the rule control is inclusive or exclusive and to specify a maximum number of substitutions to be carried out in an ATP check.  Currently, this number can be 0 when there are no restrictions and 1 when there is only one substitution.  This indicator is evaluated at rule level; that is, if you specify more than one rule, the result may contain more than one substitution. The list sequence defines the sequence in which product substitution lists and location determination lists are taken into account together. The product strategy defines the sequence in which alternatives are processed in a specific product substitution list. The location strategy defines the sequence in which alternatives are processed in a specific location determination (substitution) list.

(C) SAP AG

SCM670

15

6.15 Evaluation Strategy Product substitution procedure

Location determination procedure

Cost evaluation: Relevant for the network and fan-shaped structure types Evaluation of the access strategies Qualification of products and locations

Creation of combination lists: There are always two lists

Combination of both lists: Intersection, union, complement

Result: Sequence of substitution steps (location products)  SAP AG 2003

(C) SAP AG

SCM670

16

6.16 Rule Control: Access Strategy 01 Work forward 02 Work backward from input, then forward from input 03 Work forward from input, cyclic 04 Work backward 05 Work backward from input, then forward from input 06 Work backward from input, cyclic 07 Work forward from input 08 Work backward from input 09 Start from top of list 10 Start from bottom of list

Product substitution Location determination Location product substitution

11

22

33

44

55

66

77

88

99

10 10

 SAP AG 2003

Rule control strategies (product strategy and location strategy) control check processing in a single list. Therefore, a product strategy controls check processing in a product substitution list, and the location strategy controls processing in a location determination list.  Six of the possible strategies (for either products or locations) are described below:  Strategy one checks sequentially, working from the top of the list to the bottom.  Strategy two starts the sequential checking at the input value in the list and works toward the bottom of the list. If the product is not found, the check returns to the input value and continues to check sequentially working toward the top of the list.  Strategy three starts the sequential checking at the input value in the list and works toward the bottom of the list. If the product is not found, the check returns to the top of the list and continues working down toward the input value.  Strategy four starts the checking at the bottom of the list working backward toward the top.  Strategy five starts the sequential checking at the input value and works backward toward the top of the list. If the product is not available, the check returns to the input value and continues working toward the bottom of the list.  Strategy six starts the sequential checking at the input value and works backward toward the top of the list. If the product is not found, the check returns to the bottom of the list and works backward toward the input value. 

(C) SAP AG

SCM670

17

6.17 Rule Control: Combination of Substitution Lists

Products

Qualified product / location Combination options Union Complement?

Union

Qualified Product = Input product

Complement

Locations Qualified location = input location  SAP AG 2003



Defining qualified products and locations: The qualified product or location is used to restrict the substitution list. You can qualify an element in a substitution list (product and/or location). The respective substitution list is then restricted to this element for the combination.



Defining the combination of the product and location list: You define how you want the lists generated by the combination sequence to be combined. The system always generates two ordered lists from location products when you apply the combination sequence to the substitution lists. For example, for the setting Locations in products, and then products in locations, the first list consists of locations in products, while the second consists of products in locations.  Union: Standard setting: All elements from the second list that are not contained in the first list are added to the first list.

(C) SAP AG

SCM670

18

6.18 Rule Control: Combination of Substitution Lists (2)

Products

Qualified product / location Combination options Intersection Complement?

Qualified Product = Input product

Intersection Complement

Locations Qualified location = input location  SAP AG 2003



Intersection: The system deletes all elements not contained in the second list from the list generated first.



Complement of the combination of the product and location list: The indicator controls whether the system issues the results list or its complement. The results list is the location product list generated by the system after the Combination (of the location and product lists) step. If you have set the indicator, the system issues the complement of the results list.

(C) SAP AG

SCM670

19

6.19 Rule Control: Combination of Substitution Lists (3) Qualified product with all locations ... Qualified product 1 / location A and B Union Result:

1A 1B 2A 3A 2B 3B

Second list

Products

Products

1A First list

3 2

3

2A 3A

2

1B

1A

1

1B

2B

1

3B A

B

Locations

A

B

Locations

 SAP AG 2003



Defining the combination sequence of locations and products: All locations in the location substitution list are combined with the products from the restricted product substitution list (locations in qualified products).



Use the rule evaluation if you want to display a complete list of substitute location products for the corresponding rule.



Procedure: 1. From the SAP Easy Access menu, choose Master Data -> Rule Maintenance -> Integrated Rule Maintenance. 2. Choose Maintain Rule in the Overview frame and double-click the rule you want to evaluate. 3. Choose Evaluate Rule in the Details frame. 4. Enter the requested location product and choose Enter. 5. Choose Start evaluation. An ordered list of all substitute location products is displayed.

(C) SAP AG

SCM670

20

6.20 Rule Control: Combination of Substitution Lists (4) Qualified location with all products ... Qualified product 1 / location A and B Union Result:

First list

1A 2A 3A 1B 2B 3B

Products

Products

1A 3

2A 3A

2

1B 2B

1

Second list

3 2

1A

1

1B

3B

A

B

A

Locations

B

Locations

 SAP AG 2003



Defining the combination sequence of locations and products: All products in the product substitution list are combined with the locations from the restricted location substitution list (products in qualified locations).

(C) SAP AG

SCM670

21

6.21 Rule Control: PPM Substitutions Check all production levels for every location

Level 10

FP

20

ATP

ATP

ATP

CTP

CTP

CTP

CTP

CTP

CTP

PPM 1 30 PPM 2 FP = finished product / PPM = production process model / CTP = Capable-to-Promise  SAP AG 2003

 

If a level is not present for a specific location product, this location product is not evaluated. In this example, the production methods are evaluated first.

(C) SAP AG

SCM670

22

6.22 Rule Control: PPM Substitutions (2) Check all locations first for the same production level and then for a different production level Level 10

FP

20

ATP

ATP

ATP

CTP

CTP

CTP

CTP

CTP

CTP

PPM 1 30 PPM 2 FP = finished product / PPM = production process model / CTP = Capable-to-Promise  SAP AG 2003

If a level is not present for a specific location product, this location product is not evaluated.  The following process is an example from the paper-processing industry where you first try to find the finished product in different locations. If the system is not able to confirm, it searches for a way to cut the paper from reels and, finally, to produce new paper. Therefore, the sequence of the evaluation is set so that locations are evaluated first. 

 A location product list is created from the procedures given in the rule. This can be either a location determination procedure and/or a product substitution procedure or, alternatively, a location product substitution procedure. The sequence of the location products is calculated using the rule control of the current rule, while taking into account the requested location product.  In the second step, the PPM substitutions are built on the basis of the ordered location product list. This means that if a location product is missing in the basic quantity, it is not included in the check, even if there is a row for it in the related PPM substitution table. The system searches the PPM substitution procedure for suitable entries for each location product of the basic quantity (suitable entry means the same location product). If no suitable entry exists within the PPM substitution procedure, this location product is removed from the basic quantity and is not checked. If one or more suitable entries exist in the PPM substitution procedure, one or more complete substitutions (consisting of location product, level, and PPM) are added to the results list.

(C) SAP AG

SCM670

23

6.23 Calculation Profile  Allowed delay:

Allowed early confirmation

Accepted delay of a delivery

Allowed delay

 Allowed early confirmation: Accepted number of days for early delivery

Requested date

 Consumption limit: Number of days that prevents a requirement using receipts/stock that are too early

 Indicator: Valid Value maintained is taken into account in (follow-up) checks

Consumption limit Requested date

 SAP AG 2003

You can create new calculation profiles in the Maintain Calculation Profile screen.  The calculation profile allows you to control and set limits on substitution processing in a rule procedure if check results are accepted.  Calculation profiles are not taken into account during the evaluation of an exclusive rule. You cannot assign the calculation profile to an exclusive rule because the conditions you defined in the calculation profile always refer to the location products that resulted from rule evaluation.  For each new calculation profile that you create, you can define how long the system confirms forward and backward from the requested date given by the business event. 

(Note: Do not confuse this with the absolute validity periods that you can specify for substitutions. This is a range of days that moves forward with the requested delivery date of the orders.)  Allowed delay: This enables you to permit delivery of a substitution even after a period of days. If you set this indicator, you must also specify how long the delivery may be delayed (that is, the number of days allowed by this calculation profile).  Allowed early confirmation: This allows you to permit early delivery (confirmation) of an order for the ATP check. If you set this indicator, you must also specify how early the delivery may be (that is, you specify the number of days allowed by this calculation profile). – Note: At present, SD in SAP R/3 is not able to handle early confirmations so do not maintain this value. (C) SAP AG

SCM670

24

 Backward consumption limit: This allows you to specify a time horizon that prevents stock or early receipts from being consumed by orders that lie far in the future.  Note: These options behave similarly to the validity periods with which you are familiar from substitutions; that is, if both periods are specified, they are evaluated together.  The Valid indicator indicates that the value has been maintained. This is necessary so that you can distinguish between an entered value of 0 (which means that no deviation from the request is allowed), and an unspecified value (internally, this is treated like 0, but in this case is regarded as not relevant). If you enter a figure for the periods, the system sets this indicator automatically.

(C) SAP AG

SCM670

25

6.24 Calculation Profile (2)

Number of delivery splits allowed Package size of a partial delivery Overdelivery

 SAP AG 2003



The number of partial deliveries restricts the delivery proposals generated for each check. If the number of possible schedule lines exceeds the allowed number, all further confirmations are added to the latest possible confirmation date, if this is allowed by the check methods in use. If this is not the case, the check is terminated and an additional check is started, if required.



Note: If you want to use ATP rules (in SAP APO) for package size and/or overdelivery, this may lead to unexpected results, which are nevertheless correct, as the following examples show.  For a package size of 12 together with an order quantity of 100, the request is regarded as satisfied if 96 are available (overdelivery not allowed). In this case, the SAP R/3 sales order, for example, never gets the complete confirmation status.  For a package size of 12 together with an order quantity of 100, the request is regarded as satisfied if 108 are available, provided that overdelivery of at least 8 percent is allowed. The system confirms 108, even though the quantity requested was only 100.

(C) SAP AG

SCM670

26

6.25 Rule Maintenance: Summary

You are now able to:  Explain and define product substitution  Explain and define location determination  Explain and define the PPM substitution  Describe and set up the calculation profile and rule control

 SAP AG 2003

(C) SAP AG

SCM670

27

6.26 Rule Determination: Objectives

At the conclusion of this topic, you will be able to:  Explain the methodology and technology of ATP rule

determination  Describe a field catalog and implement a condition table  Define an access sequence and condition type for ATP

rule determination  Set up condition records for rule determination  Define the activation process for rules-based ATP

 SAP AG 2003

(C) SAP AG

SCM670

28

6.27 ATP Rules

Rule A

Alternative PPM explosion

Rule C

Rule B

Alternative location(s)

Alternative product(s) Rule "A" Rule "B" Rule "C"  SAP AG 2003

You have defined many different rules. The prerequisites for which rule(s) is/are used to check availability can be made dependent on any criteria and controlled specifically to a transaction. The condition technique is used for this.  Different transactions may require different rules. For example, identical orders placed simultaneously by the same customer could require different checking rules if one of the orders is a rush order.  Moreover, it may be necessary to apply more than one of the rules you previously defined. A flexible sequence of rules then provides the desired result. 

(C) SAP AG

SCM670

29

6.28 Condition Table Definition of characteristics that determine rule usage

Field catalog:  Sales organization  Division  Distribution channel  Sold-to party  Order type  Product  Item category

Condition table 301 Key fields  Sales organization  Sold-to party  Product

Condition table 301 Condition table 100 Key fields: VKORG/AG/Product:

Key fields: VKORG / Product:

Rule "A"

Rule "B" Rule "C"  SAP AG 2003

   



You can make the usage of a rule dependent on certain characteristics or criteria by using the condition table. You can set up several condition tables in your system. Only specific condition tables are searched during a rules-based ATP check. Access sequences are used to control this. The system checks on the basis of transactions (in other words, using the information from each document) whether there are rules defined that are dependent on a specific key field value. You determine the sequence of the key fields according to when they were copied from the field catalog. If you want to change this sequence, you must delete the corresponding condition table and then create a new one. The condition table cannot be changed after it has been generated. However, you can delete the condition table at any time. To change the format of the fast entry screen, choose Technical View from the Create Condition Tables screen. When formatting, you have the following options: To... Do this… Display the field as a header row leave the Rows field blank. Display the field as an item row set the Rows indicator. Display the text for an item row set the Text indicator.

(C) SAP AG

SCM670

30

6.29 Defining Rule Determination In the condition table, define condition records that, in turn, define the specific access to a rule. Enter the condition type (access sequence) and specific characteristic values.

Condition table 301 Assign a rule to a characteristic value  Sales organization 1000 Rule B  Sold-to party 4711  Product P-103

Condition table 301

For each condition type Condition table 100

Key fields: VKORG/AG/Product: 1000/ 4711/ P-103

Key fields: VKORG / Product: 1000 / P-103 2000 / M-111

Rule "B"

For each condition type

Rule "A" Rule "C"

 SAP AG 2003



A rule (used in the ATP check) is assigned to a value of key fields from a condition table if the values of the key combinations match the field values of the sales order.

(C) SAP AG

SCM670

31

6.30 Execution of Rule Determination Sales order OR VKORG: 1000 AG: 0815 Item 1 P-103 10 PCS

The relevant rules are determined and then evaluated depending on the characteristics of the transaction that calls the availability check. Condition table 301

For each condition type Condition table 100

Key fields: VKORG/AG/Product: 1000/ 4711/ P-103

Key fields: VKORG / Product: 1000 / P-103 2000 / M-111

Rule "B"

For each condition type

Rule "A" Rule "C"

 SAP AG 2003

When searching a condition table, the system finds a condition record that matches the specific field values from the sales order that triggered the ATP check.  At runtime, each successful access to a condition record returns a rule. This is taken into account in the current ATP check. 

(C) SAP AG

SCM670

32

6.31 Configuration: Check Instructions Sales order OR VKORG: 1000 AG: 0815 Item 1 P-103 10 PCS

Condition table 301

Check instructions Checkmode Business event

Rules-based ATP Result: Calling rules-based ATP

For each condition type Condition table 100

Key fields: VKORG/AG/Product: 1000/ 4711/ P-103

Key fields: VKORG / Product: 1000 / P-103 2000 / M-111

Rule "B"

For each condition type

Rule "A" Rule "C"

 SAP AG 2003



The rules-based ATP check is only executed if the call to rules-based ATP is defined in the relevant check instructions.

(C) SAP AG

SCM670

33

6.32 Configuration: Determining the Rule Strategy Sales order OR VKORG: 1000 AG: 0815

Checkinstructions Checkmode

Item1 P-103 10PCS

Business event

Rules-based ATP

Result: Calling rulesbased ATP

Determining therule strategy using:  Technical scenario  Business transaction  Operation

Rulestrategy

Change View "Assign Rule Strategy": Overview

Condition table 301

For each condition type Condition table 100

Key fields: VKORG/AG/Product: 1000/ 4711/ P-103

Key fields: VKORG / Product: 1000 / P-103 2000 / M-111

Rule "B"

For each condition type

Rule "A" Rule "C"

 SAP AG 2003

 









A prerequisite for rule determination is determination of the rule strategy. A technical scenario calls ATP. You can specify in which technical scenarios the rules-based ATP check is executed. Examples: User transactions (AA), EDI (DD), internet functions, or batch processing (BB). If the OLTP system is an SAP R/3 system, you must maintain the business transaction and assign it to an order type. In SAP R/3, in Customizing for Sales and Distribution, choose Basic Functions -> Availability Check and Transfer of Requirements -> Availability Check -> Rules-Based Availability Check -> Define Business Transaction / Assign Business Transaction to Sales Order Type. If you want to execute the rules-based availability check within multilevel ATP for the finished product and/or the components, you have to define a business transaction for multilevel ATP. In SAP APO Customizing, choose Global Available-to-Promise (Global ATP) -> Rules-Based Availability Check -> Create Business Transaction for Multilevel ATP Check. Examples of action types: Create (A), change (B), copy (C). Note: This value is determined by the application calling from SAP R/3. You can use your own values for simulations in SAP APO. In the Handling of CP field, you can define whether the calculation profiles of the rules involved should be handled as “supplements” or “substitutes”. You use this field to control how to use several calculation profiles that originate from gradual accesses. You can choose if a subsequent rule overwrites or supplements. This means that a calculation profile can be evaluated in an access, and the result is applied to the next location and product substitution rule.

(C) SAP AG

SCM670

34

6.33 Configuration: Rule Strategy Sales order OR VKORG: 1000 AG: 0815

Checkinstructions Checkmode

Item1 P-103 10PCS

Business event

Rules-based ATP

Result: Calling rulesbased ATP

Rule strategy

Condition table 301

Determining therule strategy using:  Technical scenario  Business transaction  Operation

Condition type Condition type ...

Condition type 1

Condition 1

Condition type 2

Condition 2

For each condition type Condition table 100

Key fields: VKORG/AG/Product: 1000/ 4711/ P-103

Rulestrategy

Key fields: VKORG / Product: 1000 / P-103 2000 / M-111

Rule "B"

For each condition type

Rule "A" Rule "C"

 SAP AG 2003

The rule strategy (also known as the condition procedure) identifies the steps to be followed during the rule determination process. Each step is a condition type.  You use the rule strategy to identify the steps to be taken.  Typically, only one condition type is necessary for each rule strategy, though SAP APO supports several. This is because the flexibility provided by the access sequence (to handle multiple dependencies) makes more than one condition type unnecessary.  A condition determines under which circumstances an access from the system to a specific condition type is excluded. 

(C) SAP AG

SCM670

35

6.34 Configuration: Access Sequence Sales order OR VKORG: 1000 AG: 0815 Item1 P-103 10PCS

Business event

1. Access sequence to thecondition tables 2. Which sales order data is used to fill thekeys of theconditiontables to search for rules stored there?

Condition table 301

Determining therule strategy using: Rules-based ATP  Technical scenario Result: Calling rules-  Business transaction  Operation based ATP Checkinstructions

Checkmode

Rulestrategy Cond.type

ACC

Cond.type ...

ACC

Access sequence (ACC) 1. Access: 2. Access: 3. ...

For each condition type Condition table 100

Key fields: VKORG/AG/Product: 1000/ 4711/ P-103

Key fields: VKORG / Product: 1000 / P-103 2000 / M-111

Rule "B"

For each condition type

Rule "A" Rule "C"

 SAP AG 2003







 

The access sequence is an ordered list of condition tables used to search for condition records that match the values of the order. Finding a matching condition record is vital for identifying the correct rule procedure to be used in a specific ATP check. The access sequence gives the SAP APO rule determination process flexibility for handling conditional dependencies. This is because more than one condition table can be specified in an access sequence. However, not all condition tables have to be listed in an access sequence. Moreover, several condition tables could contain records. Therefore, the access sequence makes it possible to determine several rules. Access sequences can be defined after the necessary condition tables have been created. To do so, enter a key and description for the access sequence and then go to the individual accesses. Choose the New Entries field to create condition table entries. After completing this step, proceed to the field view and choose Save to generate the access sequence. If you go back to the previous screen (Accesses), you will notice that the access and condition table numbers can no longer be changed. This means that the generation has been completed successfully. The condition can prevent the corresponding access being executed. Conditions are not currently supported. The Exclusive indicator stops stepwise evaluation of the condition tables at runtime after the first successful access has been made.

(C) SAP AG

SCM670

36

6.35 Configuration of Condition Technique: Summary

Activation: AA | AAAA | A Rule strategy/ prod. alloc. proced.: GEOATP

Condition type: GEOC

Access seq.: SOSO

OLTP: Sales order incl. values, reqmnts class

Access 1 = 1st condition Access 2 = 2nd condition

Determination: Sales office: CASF Sales organization: USSO Rule:

Basic ATP settings (check mode/ business event) RBA

WEST01

Condition: Condition: CONDITION CONDITION TABLE TABLE 650 650 Sales Sales office office Sales Sales organization organization

Access 3 = 3rd condition Access 4 = 4th condition

Rule Rule (WEST01 (WEST01 -- inclusive) inclusive) Rule Rule control control RH01 RH01

Location Location det. det. procedure procedure WEST_LOC01 WEST_LOC01

Prod. Prod. substit. substit. procedure procedure LA-NB8 LA-NB8

Calculation Calculation profile profile CALC01 CALC01

 SAP AG 2003







 

The condition technique allows various events to be triggered from a transaction depending on any criteria. For the rules-based availability check, this means that different availability check rules can be used for the check depending on the characteristics of the transaction (for example, the order). The rule strategy is determined in the condition technique using:  A technical process  A business process  A specific activity This definition is referred to as activation of rule processing. A rule strategy refers to at least one condition type. Each step is called a condition type. The strategy is activated by parameters provided by the calling application. If sales order processing in SAP R/3 is calling, the system determines the activity and the technical process, whereas the business process is determined from the order type in SAP R/3. Each condition type is assigned an access sequence. The access sequence is an ordered list of condition tables used to search for a condition record that matches the values of the order. Once a matching condition record has been found, the system identifies a rule to be used in the next checking step. For example, the rule could require a product substitution, an alternative location, and so on.

(C) SAP AG

SCM670

37

6.36 Rule Determination: Summary

You are now able to:  Explain the methodology and technology of ATP

rule determination  Describe a field catalog and implement a condition

table  Define an access sequence and condition type for

ATP rule determination  Set up condition records for rule determination  Define the activation process for rules-based ATP

 SAP AG 2003

(C) SAP AG

SCM670

38

6.37 Rules-Based Availability Check: Summary

You are now able to:  Explain the substitution options and define them in the form of rules in the system  Explain and define the methodology and technology of ATP rule determination  Set up condition records for rule determination

 SAP AG 2003

(C) SAP AG

SCM670

39

6.38Rule Maintenance: Exercises Unit: Rule Maintenance

At the conclusion of this exercise, you will be able to: • Configure a rule – product substitution procedure, location determination procedure, using rule control and the calculation profile Maxitec Ltd.’s PC products are available in two distribution centers 2400 Milan and 2500 Amsterdam. Your task is to define the correct product/location substitution within the rule PROC##. In addition, you have to set up the rule control and the calculation profile. You create PROC## as the rule, where ## is your group number. In addition, you use the locations 2400 Milan and 2500 Amsterdam as your two distribution center substitutions. The data given below is used throughout these exercises. The substitution should be performed in the following manner: 1. Check product T-F13## in location 2400 (Milan). 2. Check product T-F13## in location 2500 (Amsterdam). 3. Check product T-F14## in location 2400 (Milan). 4. Check product T-F14## in location 2500 (Amsterdam). 6-1

Set up a product substitution procedure called PS## for two materials. You want to check the availability of product T-F13##. If T-F13## is not available, check the availability of product T-F14##. Use T-F13## → T-F14## when creating this profile. 6-1-1 Is a code required for the product substitution reason? _______________________________________________________________

(C) SAP AG

SCM670

40

6-2

Set up the location determination procedure LS## from location 2400 (Milan) to location 2500 (Amsterdam). You want to check the availability at DC location 2400 Milan first. If the stock is not available at 2400, check the availability at location 2500 Amsterdam. Use 2400 → 2500 when creating this profile. 6-2-1 Which ATP checks are controlled explicitly by activity 0001 in the location determination? Product Check: ____________________________________________________ Product Allocation: _________________________________________________ Start Production: _______________________________________________

6-3

Create a rule control, RC##, to determine the way the substitution lists are accessed and combined. Both product substitution and location determination lists should be traversed starting from the top of the lists. There should be no qualifying restrictions on the product and location lists. Use the sequence option – Combine qualified product with all locations, then qualified locations with all products. Use Union to combine the location and product lists. 6-3-1 If a sales order comes in for T-F14## (location DC 2500 Amsterdam), which product and location are checked first, based on these rule control settings? Product: __________________________________________________________ Location: _________________________________________________________

6-4

Set up a calculation profile, CP##. The calculation profile should only allow confirmations within a three-month period starting from the check date. Confirmations can be 30 days after the requested delivery date. Note: You may get an error message after completing and saving the calculation profile. You are then required to enter a Late Demand Fulfillment strategy on the next calculation profile tab page as a required field entry. Choose Save again. 6-4-1 If the overdelivery is 10 percent, and the package size is eight, what is the maximum confirmed quantity that is possible for an order quantity of 100? Maximum confirmed quantity: ________________________________________

(C) SAP AG

SCM670

41

6-5

Create rule PROC##. The rule must be defined as “inclusive” and contain the product substitution procedure PS## and location determination procedure LS##. In addition, you have to assign the rule control RC## and calculation profile CP## to the rule PROC##.

6-6

Simulate the rule PROC## using the Evaluate Rule function in integrated rule maintenance. Examine the result: It is an ordered sequence of products and locations. 6-6-1 What is the sequence of the requirements? ___________________________________________________ ___________________________________________________ ___________________________________________________ ___________________________________________________

(C) SAP AG

SCM670

42

6.39Exercises Unit: Rule Determination

At the conclusion of this exercise, you will be able to: • Set up determination of a rule during sales order entry • Use the simulation component of the rules-based ATP check • Execute the rules-based availability check in SAP APO based on a sales order from SAP R/3 • Identify which order items the system creates in the rules-based availability check (RBA) Maxitec Ltd. wants you to set up the criteria for determining the rule PROC##. Assume that the following events will be sent from SAP R/3 to SAP APO when the simulative and actual OLTP availability check is executed: Technical Scenario: AA Business Event: A## Activity: A You will use PROC## as your rule, 2402 Jashanmal International Trading Company, Dubai, as your customer, and T-F13-## as your PC product (## is your group number). This information is used throughout these exercises. General starting instructions for calling the Implementation Guide (IMG) and calling Global ATP configuration: Choose Tools → Business Engineer → Customizing. Choose SAP Reference IMG on the Customizing: Project Administration screen. 6-7

Create the condition table 7##, with the fields Product and Sold-to party. 6-7-1 For a condition record to be correct in condition table 7##, should both the product and sold-to party match the sales order values (a logical AND)? ________

(C) SAP AG

SCM670

43

6-8

Create an access sequence, AS##, with a single action, using table 7##. Access No.

Table

10 Choose Enter. Confirm the information message that states that the development class of condition table 7## is local. Select the row for access number 10 on the right-hand side and double-click Fields (on the left) to drill down to the field level (this step is necessary for technical reasons). In the Prompt for Customizing Request that appears: a) Choose Create Request. Enter the short description Changes Group ## and save your entry. b) After the request number is generated, choose Continue. The message Data saved appears. c) Go back to the Implementation Guide (IMG). 6-8-1 If several condition tables are used, how should the subsequent condition table look in condition matching: less restrictive (fewer fields) or more restrictive (more fields)? _______________________________________________________________ 6-9

Create the condition type CT## and link it to access sequence AS##. Ctyp (Condition type)

Access Sequence

CT##

AS##

Enter the description Group ##. In the Prompt for Customizing Request that appears: a) Choose Own requests. b) From Own requests, choose the number with the changes for group ##. Choose Continue. The message Data saved appears. c) Go back to the Implementation Guide (IMG).

(C) SAP AG

SCM670

44

6-10

Create the rule strategy STR##. Assign the condition type CT## to the procedure STR##. Note: To drill down to the next level (10), select the strategy row you just created for STR## and double-click Control on the left of the screen.) Choose New Entries and enter the data shown in the table below. Strategy

Description

STR##

Strategy ## LevelCnt. (Condition counter) Leave blank

6-11

Ctyp (Condition type)

Description and Condition

CT##

Leave blank

Create event AA-A##-A and assign the procedure STR## to the events AA-A##-A. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Rules-Based Availability Check → Assign Rule Strategy. Choose New Entries. Technical scenario

AA

Note: Enter this value.

Business transaction

A##

Note: Enter this value.

Action type

A

Note: Enter this value.

Strategy

STR##

Use the input help (F4)

Handling of CP

Substitute

Proposed as default

Choose Save and confirm the Prompt for Customizing Request number that appears. Go back to the Implementation Guide (IMG). 6-11-1

If only a single rule is called, does it matter if the handling of CP (calculation profile) is “substitute” or “add”? _____________________________________________________________

(C) SAP AG

SCM670

45

6-12

For condition type CT##, define the assignment between characteristics delivered by the sales order and their specific values, for execution of a single rule. Enter the following data for condition type CT##: Field Name or Data Type

Values

Product

T-F13##

Sold-To Party

0000002402

Rule

PROC##

6-13

Have a look at the activation of rules-based ATP in the check instructions that correspond to the check mode (050) of your product, T-F13##.

6-14

Make sure that the Consider CH (consider checking horizon) indicator is deactivated for the relevant check control (you should do this for ATP group 02 and business event A).

6-15

Use the simulation component to verify the configuration of the rule and rule determination. The simulation should be performed for a value of the product T-F13## and location DC 2400 Milan. Enter the following characteristic values to enable the simulation: Operation-dependent activation parameters: AA – A## – A Use Sold-to party 0000002402 Jashanmal International Trading Company. Enter your product, T-F13##. The Global ATP graphic appears. Enter the following additional data for the simulation: Business Event: Check Mode: Date: Quantity:

A 050 300 pieces

6-16

Define the business transaction A## in SAP R/3 Customizing.

6-17

Assign the business transaction to the order type ZA## Trade Fair## Order.

(C) SAP AG

SCM670

46

6-18

Now you can create a sales order in SAP R/3. The sales order should be for customer 2402 Jashanmal International Traders, for the material T-F13##, and for a quantity of 300 pieces. The sales order data is given in the table below: Call the transaction VA01 (Create Sales Order). Enter the following data: Field Name or Data Type

Values

Order Type

ZA##

Sales Organization

2400

Distribution Channel

10

Division

00

Sold-To Party

2402

PO Number

PO-##

Requested Delivery Date

A week on Monday

Plant

2400

Material

T-F13##

Quantity

300 PC

(C) SAP AG

SCM670

47

6.40Rule Maintenance: Solutions Unit: Rule Maintenance

You create PROC## as a rule, where ## is your group number. In addition, you use the locations 2400 Milan and 2500 Amsterdam as your two distribution center substitutions. The data given below is used throughout these exercises. The substitution should be performed in the following manner: 1. Check product T-F13## in location 2400 (Milan). 2. Check product T-F13## in location 2500 (Amsterdam). 3. Check product T-F14## in location 2400 (Milan). 4. Check product T-F14## in location 2500 (Amsterdam). 6-1

Set up a product substitution procedure called PS## for two materials. Choose SAP APO Easy Access menu: Master Data → Rule Maintenance → Integrated Rule Maintenance. You want to check the availability of product T-F13##. If T-F13## is not available, check the availability of product T-F14##. Use T-F13## → T-F14## when creating this profile. Choose the Maintain Product Substitutions tab page on the left of the screen. Choose Create New Procedure. Enter PS## as the name of the substitution procedure, 0 as the type (substitution chain), and Group ## as the product procedure text. Choose Enter. Blank lines, in which you can enter the products, appear on the right of the screen. Enter the products T-F13## and T-F14##. Enter any reason code in the Reason column field. Choose Save. 6-1-1 Is a code required for the product substitution reason? No, if you do not enter a code, the initial value 000 is transferred from SAP APO to SAP R/3. However, a substitution reason must be maintained there with the code 000.

(C) SAP AG

SCM670

48

6-2

Set up the following location determination procedure LS## from 2400 Milan to 2500 Amsterdam. You want to check the availability at DC location 2400 Milan first. If the stock is not available at 2400, check the availability at location 2500 Amsterdam. Use 2400 → 2500 when creating this profile. Choose the Maintain Location Determination Procedure tab page on the left of the screen. Choose Create New Procedure. Enter LS## as the name of the location determination procedure, 0 as the type (substitution chain), and Group ## as the location procedure text. Choose Enter. Blank lines, in which you can enter the locations, appear on the right of the screen. Enter the locations 2400 and 2500. Use activity 0001. Do not choose Enter again because this will make an additional (superfluous) row appear. Choose Save.

6-2-1 Which ATP checks are controlled explicitly by activity 0001 in the location determination? To answer this question, we need to examine the location determination activity. If you are still on the Maintain Location Determination Procedure tab page, choose Profiles & Parameters. Choose the Maintain Location Determination Activity tab page on the left of the screen. Select activity 0001 and choose Change current activity. Product check: No – Business event and check mode are not stated Product allocation: No – Business event and check mode are not stated Start production: Yes – Activity 0001 does not allow the production check

(C) SAP AG

SCM670

49

6-3

Create a rule control, RC##, to determine the way the substitution lists are accessed and combined. Both the product substitution lists and location determination lists should be traversed starting from the top down. There should be no qualifying restrictions on the product and location lists. Use the sequence option – Combine qualified product with all locations, then qualified locations with all products. Use Union to combine the location and product lists. Choose Profiles and Parameters (top left). Choose the Maintain Rule Control tab page on the left of the screen. Create Rule Control RC##. Choose Create New Rule Control and enter RC## and description Group ##. Choose Enter. For the product substitution, use the access strategy Start from top of list. For the location substitution, use the access strategy Start from top of list. Choose No Restrictions for the qualified product. Use No Restrictions for the qualified location. Use the sequence option – Combine qualified product with all locations, then qualified locations with all products. Use Union to combine the production and location lists. Ignore the PPM substitutions levels for now. Choose Save. 6-3-1 If a sales order comes in for T-F14## (location DC 2500 Amsterdam), which product and location are checked first based on these rule control settings?

(C) SAP AG

Product:

T-F13##

Location:

2400, DC Milan

SCM670

50

6-4

Set up a calculation profile, CP##. The calculation profile should only allow confirmations within a three-month period starting from the check date. Confirmations can be 30 days after the requested delivery date. Choose the Maintain Calculation Profile tab page on the left of the screen. Choose Create New Calculation Profile. Enter CP## and calculation text Group ##, then choose Enter. Enter 30 days as the Allowed Delay. Enter 90 days as the Consumption Limit. Select the Valid indicator for both these rows. Choose Save. 6-4-1 If the overdelivery is 10 percent, and the package size is eight, what is the maximum confirmed quantity that is possible for an order quantity of 100? Maximum confirmed quantity: 104

6-5

Create rule PROC##. The rule must be defined as “inclusive” and contain the product substitution procedure PS## and location determination procedure LS##. In addition, you have to assign the rule control RC## and calculation profile CP## to the rule PROC##. Go back to the rules by choosing Rules and Substitutions. Choose the Maintain Rule tab page on the left of the screen. To create a rule, choose Create New Rule. Enter the name PROC ## for the new rule and the description Group ##. Select the Rule Type “inclusive” in the Rule tab page on the right of the screen. Choose Enter. Assign the product profile PS## to the rule PROC## as the product substitution procedure. Assign the location profile LS## to the rule PROC## as the location determination procedure. Assign the rule control RC## to the rule PROC##. Choose Enter to display the combination and sequencing details. Assign the calculation profile CP## to the rule PROC##. Choose Save.

(C) SAP AG

SCM670

51

6-6

Simulate the rule PROC## using the Evaluate Rule function in integrated rule maintenance. While the rules are still being displayed on the left in integrated rule maintenance, select PROC##, and choose the Evaluate Rule tab page on the far right. Make sure that PROC## is selected as your standard rule value for the simulation. Enter T-F13## and 2400 as the requested product and location for the evaluation. Choose Enter. Choose Start Evaluation to start the simulation. Examine the result. 6-6-1 What is the sequence of the requirements? There is an ordered sequence of products and locations. The ATP of T-F13## is evaluated at locations 2400 and 2500 first, before the product substitution TF14## is considered for ATP at locations 2400 and 2500.

(C) SAP AG

SCM670

52

Solutions Unit: Rule Determination

General starting instructions for calling the Implementation Guide (IMG) and calling Global ATP configuration Choose Tools → Business Engineer → Customizing. Choose SAP Reference IMG on the Customizing: Project Administration screen. IMG path: SAP APO Implementation Guide (IMG) → SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Rules-Based Availability Check → Define Condition Table. 6-7

Create the condition table 7##, with the fields Product and Sold-to party. Select the activity Create Condition Table (Usage “O”) in the dialog box. Choose Choose. Enter 7## in the Table field and choose Enter. Choose Continue in the dialog box containing the Validity period indicator. Assign the product and sold-to party fields either by double-clicking the field name in the right-hand column or by placing the cursor on the field and choosing Select field. Choose Generate (confirm the next warning message with Enter). When asked for the Development class in the dialog box that appears, choose Local object. A log is generated. Choose Back twice and choose Cancel (X) in the dialog box. 6-7-1 For a condition record to be correct in condition table 7##, should both the product and sold-to party match the sales order values (a logical AND)? Yes

(C) SAP AG

SCM670

53

6-8

Create an access sequence, AS##, with a single action, using table 7##. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Rules-Based Availability Check. Choose Maintain Access Sequences. Confirm the information message that appears: “Table is cross-client.” Create the access sequence AS##. To do so, choose New Entries. Enter the description Group ##. Choose Enter. Assign the condition table 7## to access sequence AS##. To do this, select the access sequence AS## on the right of the screen and double-click Accesses (on the left) to get to next lower level of the table. Choose New Entries. Access No.

Table

10

7##

Choose Enter. Confirm the information message that states that the development class of condition table 7## is local. Select the row for access number 10 on the right-hand side and double-click Fields (on the left) to drill down to the field level (this step is necessary for technical reasons). Choose Enter. Choose Save. In the Prompt for Customizing Request that appears: a) Choose Create Request. Enter the short description Changes Group ## and save your entry. b) After the request number is generated, choose Continue. The message Data saved appears. c) Go back to the Implementation Guide (IMG). 6-8-1 If several condition tables are used, how should the subsequent condition table look in condition matching: less restrictive (fewer fields) or more restrictive (more fields)? Less restrictive

(C) SAP AG

SCM670

54

6-9

Create the condition type CT## and link it to access sequence AS##. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Rules-Based Availability Check. Choose Maintain Condition Type. Choose New Entries. Condition Type

Access Sequence

CT##

AS##

Enter the description Group ##. Choose Save. In the Prompt for Customizing Request dialog box: a) Choose Own requests. b) From Own requests, choose the number with the changes for group ##. Choose Continue. The message Data saved appears. c) Go back to the Implementation Guide (IMG). 6-10

Create the rule strategy STR##. Assign the condition type CT## to the procedure STR##. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Rules-Based Availability Check → Maintain Rule Strategy. To assign the condition type CT## to the procedure STR##, choose New Entries. Enter the strategy and description as shown in the table below. Choose Enter to register the line input. The line can now be selected for the next step. Note: To drill down to the next level (10), select the strategy row you just created for STR## and double-click Control on the left of the screen.) Choose New Entries and enter the data shown in the table below. Strategy

Description

STR##

Strategy ## Level

Cnt. (Condition counter)

Ctyp (Condition type)

Description and Condition

10

Leave blank

CT##

Leave blank

Choose Save and confirm the Prompt for Customizing Request number that appears. The message “Data saved” appears. Go back to the Implementation Guide (IMG). (C) SAP AG

SCM670

55

6-11

Create event AA-A##-A and assign the procedure STR## to the events AA-A##-A. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Rules-Based Availability Check → Assign Rule Strategy. Choose New Entries. Technical scenario

AA

Note: Enter this value.

Business transaction

A##

Note: Enter this value.

Action type

A

Note: Enter this value.

Strategy

STR##

Use the input help (F4)

Handling of CP

Substitute

Proposed as default

Choose Save and confirm the Prompt for Customizing Request number that appears. Go back to the Implementation Guide (IMG). 6-11-1

If only a single rule is found, does it matter if the handling of CP is “substitute” or “add”? No – CP sets the standards of acceptability of an availability check proposal for all product/location requirement groupings within a single rule. If multiple rules are set, then the “Add” setting can make sure that the CPs of multiple rules are all adhered to simultaneously.

6-12

To execute a single rule, you define the assignment between characteristics from the sales order and their specific values. From the SAP Easy Access menu, choose Master Data → Rule Maintenance → Create Rule Determination. Enter the condition type CT##. Choose Enter. Enter the following data: Field Name or Data Type

Values

Product

T-F13##

Sold-To Party

0000002402

Rule

PROC##

Choose Save. Go back to the Implementation Guide (IMG).

(C) SAP AG

SCM670

56

6-13

Have a look at the activation of rules-based ATP in the check instructions that correspond to the check mode (050) of your product T-F13##. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → General Settings → Maintain Check Instructions. Select check mode 050 / business event A and set the indicator for rules-based ATP (RBA), if required. Ensure that the product check is the first step. Set the step for product allocation to No check. Choose Save. Go back to the Implementation Guide (IMG).

6-14

Make sure that the Consider CH (consider checking horizon) indicator is deactivated for the relevant check control (you should do this for ATP group 02 and business event A). Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Product Availability Check → Maintain Check Control. Select ATP Group 02 / business event A. Choose Details. Deactivate the Consider CH indicator. Choose Save. Go back to the Implementation Guide (IMG).

6-15

Use the simulation component to verify the configuration of the rule and rule determination. The simulation should be performed for a value of the product T-F13## and location DC 2400 Milan. Choose SAP APO Easy Access menu: Global ATP → Reporting → ATP Simulation. Enter the data for your product T-F13## and location 2400. Choose check mode 050. Choose business event A. Use next Monday’s date as the material availability date. Enter 300 PC as the required quantity. Choose Execute. Enter the following characteristic values to enable the simulation: Operation-dependent activation parameters: AA – A## – A Use Sold-to party 0000002402 Jashanmal International Trading Company. Enter your product T-F13##. The Global ATP graphic appears.

(C) SAP AG

SCM670

57

6-16

Define the business transaction A## in SAP R/3 Customizing. Choose SAP R/3 IMG: Sales and Distribution → Basic Functions → Availability Check and Transfer of Requirements → Availability Check → Rules-Based Availability Check → Define Business Transaction. Choose New Entries. BT:

A##

Business transaction text:

ATP Group ##

Save your entries. 6-17

Assign the business transaction to the order type ZA## Trade Fair## Order. Choose SAP R/3 IMG: Sales and Distribution → Basic Functions → Availability Check and Transfer of Requirements → Availability Check → Rules-Based Availability Check → Assign Business Transaction to Sales Order Type. Locate sales document type ZA## in the list. Choose Details (magnifying glass). Scroll to the bottom of the screen and enter the business transaction A## in the Business Transaction field. Save your entries.

6-18

Now you can create a sales order in SAP R/3. The sales order should be for customer 2402 Jashanmal International Traders, for the material T-F13##, and for a quantity of 300 pieces. The sales order data is given in the table below: Call the transaction VA01 (Create Sales Order). Enter the following data: Field Name or Data Type

Values

Order Type

ZA##

Sales Organization

2400

Distribution Channel

10

Division

00

Sold-To Party

2402

PO Number

PO-##

Requested Delivery Date

A week on Monday

Plant

2400

Material

T-F13##

Quantity

300 PC

(C) SAP AG

SCM670

58

(C) SAP AG

SCM670

59

7 Production Within the ATP Check

Contents:  Capable-to-Promise (CTP)  Multilevel ATP check (MATP)

Contents:  SAP AG 2003

(C) SAP AG

SCM670

1

7.2 Production Within the ATP Check: Objectives

At the conclusion of this unit, you will be able to:  Set up the call to production from the availability check  Distinguish between the goals of Capable-to-Promise and multilevel ATP  Describe the Capable-to-Promise and multilevel ATP processes  Set up the multilevel ATP check

 SAP AG 2003

(C) SAP AG

SCM670

2

7.3 Production Within the ATP Check: Course Overview Diagram 1

Course Overview 2 2

Global ATP / OLTP Interface 3 3

Selection of Check Method 4

Product Availability Check

5 Check Against Product Allocations 6 7 8 9

Rules-Based Availability Check Production Within the ATP Check

Backorder Processing

Scheduling

 SAP AG 2003

(C) SAP AG

SCM670

3

7.4 Production Within the ATP Check: Business Scenario

 First, Maxitec Ltd. executes a product availability check for its products. If the requirement cannot be confirmed, selected products are procured or produced directly from the availability check. The confirmation can be made immediately against the planned receipt (purchase requisition or planned order).  Depending on the products, there are two different production bottlenecks at Maxitec Ltd.: 

For some products, component availability is not important within production. However, production puts a lot of pressure on production resources.

 SAP AG 2003

(C) SAP AG

SCM670

4

7.5 Production Within the ATP Check: Business Scenario (2)



The time dependencies of the individual production steps are demanding and have to be considered.



Other products are just produced through straightforward assembly. Maxitec Ltd. has almost unlimited assembly capacity; however, these products make great demands on the availability check. For this reason, individual unavailable components are substituted if required.

 SAP AG 2003

(C) SAP AG

SCM670

5

7.6 Capable-to-Promise SD order

Product availability check

Cumul. X ATP quantity

PP/DS PPM

Source determination PPM explosion

SD order Delivery proposal: Stock against planned order

Detailed Scheduling: Component availability check: net req. calc. Res. av. chk: compl. PP/DS det.sched.func. Temporary planned order + planned independent requirements

Save SD order

Planned order + planned independent X requirements

Production order

Production order

 SAP AG 2003

Components Quantities  Resource requirements  Operations  

SAP APO

Explanation of abbreviation: Res.av.chk: compl. PP/DS det.sched.func. = resource availability check: complete PP/DS detailed scheduling function

Global ATP uses the PP/DS functions within the Capable-to-Promise scenario in SAP APO to propose feasible delivery dates.  To propose feasible delivery dates, the system takes into account:  The production process model (bill of material and production routing information) of the product  The component availability (net requirements calculation only)  Unallocated production capacity  Production lead times  Calling production using CTP focuses on the detailed scheduling strategies and not on the component availability check. Therefore, you should use this method if the bottleneck factor in production is that the lack of available capacity is restricting the production options, and not when the bottleneck factor is the component availability. 

(C) SAP AG

SCM670

6

7.7 Multilevel ATP Check SD order

Product availability check

Cumul. X ATP quantity

PP/DS PPM

Source determination PPM explosion Determination of component quantities and requirement dates Scheduling/resource availability check: Infinite / function constraints Compon. avail. chck: compl. ATP functions SD order Delivery proposal

Correlation calculation Availability finished product

Save SD order

ATP tree structures

Components Quantities  Resource requirements  Operations  

1. Step 2. Step?

Conversion?

SAP APO

 SAP AG 2003

Production through MATP focuses on the component availability check. The availability check is able to use the entire scope of function of Global ATP (including the rules-based ATP check). In comparison to CTP, however, the detailed scheduling strategies are restricted.  Multilevel ATP assumes that resources have infinite capacity. Scheduling corresponds to lead time scheduling. For this reason, this production scenario is used if the bottleneck factor in production is the component availability, but the resource capacity does not restrict production. 

(C) SAP AG

SCM670

7

7.8 Multilevel ATP Check in Two Steps 1. Step

PPM explosion / scheduling Component requirements and requirement dates Availability check for components Result: confirmed quantities and dates for the header material

Partial quantities and dates?

Yes

No

End

2. Step Check instructions: conversion mode for ATP tree structures New PPM explosion / scheduling with selected quantity/date Component requirements and requirement dates Availability check for components Result: confirmed quantities and dates for the Remaining header material requirement?  SAP AG 2003

To guarantee that the validity of the PPM is not violated and the runtimes match the confirmation dates calculated in the multilevel ATP check at header level, the multilevel ATP check is always executed in two steps, provided the result of the first check contains partial confirmation quantities and dates.  You can define how you want the second step of the multilevel ATP check to be carried out in the check instructions for the finished product or header material using the parameters Compnts Remain. Reqmt (Remaining requirement of a component requirement group) and Conversion Mode ATP TreeStruct. (Conversion mode of ATP tree structures). 

(C) SAP AG

SCM670

8

7.9 ATP Tree Structures

In contrast to CTP, no receipt elements are created in the SAP APO order network during the multilevel ATP check.Instead, the check results are stored in the ATP tree structure.

 ATP tree structures are used to store data not transferred directly to the OLTP system.  ATP tree structures are not taken into account in planning.  Dependent requirements are not visible in planning before the conversion of the ATP tree structures.  Receipt elements are created in PP/DS after the ATP tree structures are converted.

 SAP AG 2003

(C) SAP AG

SCM670

9

7.10 Conversion of ATP Tree Structures

PP/DS creates the procurement proposals for requirements (stocktransport requisitions or planned orders) by converting the ATP tree structures.

 The following horizons and dates determine the time at which the conversion takes place: 

PP/DS horizon



Scheduling horizon for converting ATP tree structures



Requirement dates in the ATP tree structure

Immediate conversion on saving the SD order Later conversion (online or in the background)  SAP AG 2003

PP/DS immediately converts the ATP tree structure when the sales order is saved in the following cases:  If the earliest requirement date at component level is in the scheduling horizon  If the latest requirement date at finished product level is in the PP/DS horizon  If none of the conditions is met on saving the sales order, the system saves the ATP tree structure in SAP APO. In this case, you can convert the ATP tree structure online or in the background when one of the conditions listed above is fulfilled. An offset is available here for the horizons to allow you to perform an earlier conversion.  You maintain the scheduling horizon for the conversion of the ATP tree structures in Customizing for Production Planning and Detailed Scheduling under Maintain Global Parameters and Defaults. You maintain a location-product-specific PP/DS horizon in the location product master. If a location-productspecific PP/DS horizon does not exist, the system uses the PP/DS horizon of the planning version. You maintain this in model and planning version management.  The scheduling horizon is deleted after PP/DS has converted the ATP tree structures. 

(C) SAP AG

SCM670

10

7.11 Comparison of CTP and MATP MATP

CTP

Executionof availability check at componentlevel

All availability checkmethods

Net requirements calculation

Characteristics-dependent planning

No

Yes

Schedulingthefinished product

To-the-day

To-the-second

Check results

ATP tree structures

PP/DS plannedorders PP/DS purchase requisitions

Display of thecheck results

Integratedintheresults overview

Separate planninglog

Performance

Better

Worse

Consideration of capacities

Infinitescheduling

Finiteschedulingon theresources, if necessary

Dailyproductionrateusingproduct allocation atcomponentlevel Schedulingcomponents

Simplelead timescheduling

Detailed Scheduling

Lot sizes

Lot-for-lotquantity only

Lot-sizecalculation

 SAP AG 2003

(C) SAP AG

SCM670

11

7.12 Configuration of CTP and MATP: Check Mode

:

Check mode

050

Maintain check mode Assignment mode Production type Check mode text

Production type

Multilevel ATP check

MATP

Production type

Standard

CTP

 SAP AG 2003

 

The check mode for the finished product has to support the production type of multilevel ATP or CTP. The check mode for the component only has to support the production type of multilevel ATP or CTP if this component is also the header of an additional bill of material and you want to perform a multilevel check.

(C) SAP AG

SCM670

12

7.13 Configuration of CTP and MATP: Check Instructions Check instructions

:

Production Start production Prod. time

Location determination activity

Re-create receipt elements

?

Start product.

Is production called? When is production called?

Prod. time

At which point in the availability check and for which quantity should production be started?

Re-create receipt elements

Make-to-order production only: Do you want to delete existing receipt elements or ATP tree structures before a new check?

 SAP AG 2003

Select the Start production indicator (First availability check, then production). You can choose one of the following options for the time of production:  After executing all basic methods: The quantity requested for production is the original requirements quantity less the total quantity confirmed through the basic methods. The confirmed quantity results from the quantity that can be produced, plus the total quantity that can be confirmed from the basic methods. The sequence of basic methods has no effect on the quantity produced and/or confirmed.  After executing product availability check: The quantity requested for production is the requirements quantity transferred to the product availability check, less the quantity that can be confirmed at the finished product stage. The confirmed quantity is the sum of the total quantity of the product availability check that can be confirmed at finished product stage, plus the quantity that can be produced. The selection and sequence of basic methods is relevant.  Setting the Production time indicator is not relevant for the other values of the Start production indicator.  Using the location determination activity in integrated rule maintenance, you can determine if PP/DS is called in location determination when the Global ATP rules are being used.  In a substitution group, in which you only want to call PP/DS for a few location determinations, location determination activities of the type Availability check only, no production have to be maintained explicitly. Another possibility is, of course, to completely switch off the call to PP/DS in the check instructions. 

(C) SAP AG

SCM670

13

7.14 Configuration MATP: Check Instructions

Check instructions

:

Multilevel ATP check Components Remaining Reqmt Conversion Mode - ATP Tree Struct. Business Event Multilevel ATP

Components Remaining Reqmt

Defines how the system should deal with the requirement quantity that cannot be confirmed in the second step of the multilevel ATP check

Conversion Mode - ATP Tree Struct.

Controls the second step in MATP

Business Event Multilevel ATP

Special business event for controlling the component availability check

 SAP AG 2003

Compnts Remain. Reqmt (remaining requirement of a component requirement group): This field determines how the system should deal with the requirement quantity that cannot be confirmed in the second step of the multilevel ATP check:  Create remaining requirement at header level  Create remaining requirement at component level  Conversion mode for ATP tree structures: In this field, you define the confirmations for which you want the planned orders to be created in Production Planning and Detailed Scheduling (PP/DS) after the ATP tree structure is converted. Depending on this setting, the system uses the relevant confirmations from the first step of the multilevel ATP check as requirements date and requirement quantity for the second step of the multilevel ATP check. In the second step, the BOM is exploded anew in PP/DS, the ATP tree structure is adjusted in accordance with the new requirements groups, and a new ATP check is performed for the components. The complete requirement quantity must be confirmed for the requirements date. Otherwise, the check result is rejected. The system's handling of the unconfirmed quantities depends on the setting in the Compnts Remain. Reqmt field.  Business Event Multilevel ATP: You use a special business event for multilevel ATP in the check instructions if you want to distinguish between the check control for the components and the check control for the finished product. If you have not entered a specific business event for multilevel ATP in the check instructions, the system uses the business event to determine the check control for the multilevel ATP check. The following functions are supported at component level: 

(C) SAP AG

SCM670

14

   

A different scope of check in the product availability check Check against the forecast Check against product allocations (but only with the characteristics product and location) Rules-based ATP check

(C) SAP AG

SCM670

15

7.15 Production Within the ATP Check: Summary

You are now able to:  Set up the call to production from the availability check  Distinguish between the goals of Capable-toPromise and multilevel ATP  Describe the Capable-to-Promise and multilevel ATP processes  Set up the multilevel ATP check

 SAP AG 2003

(C) SAP AG

SCM670

16

7.16Production Within the ATP Check: Exercises Unit: Production Within the ATP Check

At the conclusion of this exercise, you will be able to: • Set up the call to production directly from the availability check • Distinguish between Capable-to-Promise and the multilevel ATP • Set up the essential requirements for both production options in PP/DS • Analyze and interpret the results of the availability check Maxitec Ltd.'s product spectrum and business processes are heterogeneous. The demands on the availability check therefore vary, depending on the product and possibly the transaction. Depending on the products, there are two different production bottlenecks at Maxitec Ltd.. For some products, component availability is not important within production. However, production puts a lot of pressure on production resources. The time dependencies of the individual production steps are demanding and have to be considered. If production is started directly from the availability check for these products, Capable-to-Promise is used. Other products are produced through straightforward assembly. The assembly capacity of Maxitec Ltd. is almost without limit. These products make great demands on the availability check, however. For example, individual unavailable components may be substituted by other components. For that reason, the multilevel ATP check is used for these products. Your instructor will assign the group number (##) that you need for all exercises in this course. Note: Check whether the user parameter /SAPAPO/WHAT_PL is set to D in the user master record for your user in the SAP APO system. If not, enter the user parameter. If the parameter is not set accordingly, you cannot display a planning log in the APO Availability Check: Results Overview. Choose System → User Profile → Own Data Tab page:

Parameters

Parameters:

/SAPAPO/WHAT_PL

Value:

D

(C) SAP AG

SCM670

17

Choose Save.

(C) SAP AG

SCM670

18

Capable-to-Promise (CTP): 7-1

Analyze the prerequisites for Capable-to-Promise. 7-1-1 Have you set the PP/DS: Change Planning Active indicator in the active PP/DS version? _______________________________________________________________ 7-1-2 Have a look at the PP planning procedure for product T-F2## in location 2300. Change the PP planning procedure to 3: Cover Dependent Requirements Immediately. _______________________________________________________________

7-2

Have a look at the Customizing settings for the availability check. 7-2-1 Examine the check instructions with check mode 050 / business event A. Product check: First step Product allocation (check): None Forecast (check): No check Rules-based ATP (check): Select Start immediately: Do not select Start product(ion): Availability check only, no production The remaining check instruction parameters are not relevant. Note: In this exercise, production is not called from the respective check instructions. As you will see as the exercise progresses, production is started from a location determination activity for the relevant rule. Therefore, this availability check is a combination of rules-based ATP and CTP. 7-2-2 Examine the check control for the product availability check for the ATP group 02 and the business event A. The checking horizon (CH) must not be considered. _______________________________________________________________

(C) SAP AG

SCM670

19

7-3

Enter a sales order in SAP R/3. Call transaction VA01 (Create Sales Order). Enter the following data: Field Name or Data Type

Values

Order Type

OR

Standard order

Sales Organization

2400

Italy, Milan

Distribution Channel

10

Final customer sales

Division

00

Cross-division

Sold-To Party

2401

Napoli Export

PO Number

PO-##

Requested Delivery Date

One week from today’s date

Delivering Plant

2400

DC Milan

Material

T-F2##

Pump PRECISION 102

Quantity

20

Choose Enter if you receive the message, “Change in invoice date: The billing date is redetermined.” This message has no impact on the ATP check. Analyze the “APO Availability Check: Results Overview.” _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ Stay in transaction VA01 (Create Sales Order). Do not save the order yet! 7-4

Analyze the product view for product T-F2## in location 2300. _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________

7-5

Now save your sales order from exercise 7-1. Order number: _______________________________________________________

(C) SAP AG

SCM670

20

7-6

Analyze the product view for product T-F2## in location 2300 after you have saved the order. _____________________________________________________________________ _____________________________________________________________________

7-7

Analyze the settings for Capable-to-Promise. 7-7-1 Which requirements type was determined for the second subitem in your sales order? _______________________________________________________________ 7-7-2 To which requirements class is this requirements type assigned in SAP R/3 Customizing? _______________________________________________________________ Note: This requirements class is transferred to SAP APO within the availability check as a check mode and controls the selection of the check instructions. 7-7-3 Which type of production has been defined for check mode 050 in SAP APO? _______________________________________________________________ 7-7-4 Is production called from the relevant check instructions? Analyze the relevant check instructions. _______________________________________________________________ 7-7-5 How or from where is production started for the location product T-F2## / 2300 within the availability check? _______________________________________________________________ _______________________________________________________________ _______________________________________________________________

(C) SAP AG

SCM670

21

Multilevel ATP check: 7-8

Analyze the main prerequisites for the multilevel ATP check. 7-8-1 Examine the production process model for the product T-F3## in location 1000. Which components does the product T-F3## consist of? _______________________________________________________________ _______________________________________________________________ _______________________________________________________________ 7-8-2 Check the production process model for component T-B1## in location 1000. Which components does this product consist of? _______________________________________________________________ _______________________________________________________________ 7-8-3 Verify which settings are necessary in the product master using the header material T-F3## in location 1000 as an example. Have a check mode and an ATP group been maintained? Check Mode: ______________________________________________________ ATP Group: _____________________________________________________ Has the PP/DS horizon been maintained? PP/DS Horizon: _________________________________________________ 7-8-4 Has a production calendar been created for scheduling in the location master for location 1000? Production Calendar:______________________________________________ 7-8-5 Examine the scheduling horizon for the multilevel ATP check. This should be smaller than or the same size as the PP/DS horizon. Scheduling horizon for ATP tree structures: _________________________

(C) SAP AG

SCM670

22

7-9

Have a look at the Customizing settings for the multilevel ATP check. 7-9-1 Which production type has been defined for the check mode ZZZ? Production type: __________________________________________________ 7-9-2 Examine the Customizing settings for the check instructions with check mode ZZZ / business event A. Note: The letters below in parentheses do not actually appear on the Check Instructions screen – they are given here to complete the on-screen abbreviations. Product check: _________________________________________ Product allocation (check): _________________________________________ Forecast (check): _________________________________________ Rules-based ATP (check): _________________________________________ Start product(ion): _________________________________________ Production time: _________________________________________ Compnts Remain. Reqmt: _________________________________________ Conversion Mode – ATP Tree Structure: _________________________________________ Business Event Multilevel ATP: _________________________________________ The remaining parameters in the check instructions are not relevant and you can leave the default values as they are.

(C) SAP AG

SCM670

23

7-10

Enter a sales order in SAP R/3. Call transaction VA01 (Create Sales Order). Enter the following data: Field Name or Data Type

Values

Order Type

OR

Standard order

Sales Organization

1000

Germany, Frankfurt

Distribution Channel

10

Final customer sales

Division

00

Cross-division

Sold-To Party

1000

Becker, Berlin

Ship-To Party

1000

Becker, Berlin

PO Number

PO-##

Requested Delivery Date

Two weeks from today’s date

Material

T-F3##

Quantity

15 PC

Choose Enter if you receive the message, “Change in invoice date: The billing date is redetermined.” This message has no impact on the ATP check. Analyze the “APO Availability Check: Results Overview.” _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________ Save the order. Order number: ______________________________________________________________ 7-11

Analyze the product view for product T-F3## in location 1000. _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________

7-12

Display the ATP tree structure that has just been generated. _____________________________________________________________________ _____________________________________________________________________ _____________________________________________________________________

(C) SAP AG

SCM670

24

(C) SAP AG

SCM670

25

7.17Production Within the ATP Check: Solutions Unit: Production Within the ATP Check

Your instructor will assign the group number (##) that you need for all exercises in this course.

Capable-to-Promise (CTP): 7-1

Analyze the prerequisites for Capable-to-Promise. 7-1-1 Have you set the PP/DS: Change Planning Active indicator in the active PP/DS version? Choose SAP APO Easy Access menu: Master Data → Planning Version Management → Model and Version Management. Double-click the active version 000 in the navigation area. The PP/DS: Change Planning Active indicator is set. 7-1-2 Have a look at the PP planning procedure for product T-F2## in location 2300. Change the PP planning procedure to 3 Cover Dependent Requirements Immediately. Choose SAP APO Easy Access menu: Master Data → Product. Enter T-F2## as the product. Select the Location view and enter 2300 as the location. Display the product data by choosing Change. Go to the PP/DS tab page. PP planning procedure: 3: Cover dependent requirements immediately If a different planning procedure has been defined, change the product master accordingly.

(C) SAP AG

SCM670

26

7-2

Have a look at the Customizing settings for the availability check. 7-2-1 Examine the check instructions with check mode 050 / business event A. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP Check) → General Settings → Maintain Check Instructions. Select check mode 050 / business event A. Choose Details (magnifying glass icon). Product check:

First step

Product allocation (check):

No check

Forecast (check):

No check

Rules-based ATP (check):

Select

Start immediately:

Do not select

Start product(ion):

Availability check only, no production

The remaining check instruction parameters are not relevant. Note: In this exercise, production is not called from the respective check instructions. As you will see as the exercise progresses, production is started from a location determination activity for the relevant rule. Therefore, this availability check is a combination of rules-based ATP and CTP. 7-2-2 Examine the check control for the product availability check for the ATP group 02 and the business event A. The checking horizon (CH) must not be considered. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Product Availability Check → Maintain Check Control. Select the ATP group 02 / business event A. Choose Details. Deselect the Consider CH indicator ______________________________

(C) SAP AG

SCM670

27

7-3

Enter a sales order in SAP R/3. Call transaction VA01 (Create Sales Order). Enter the following data: Field Name or Data Type

Values

Order Type

OR

Standard order

Sales Organization

2400

Italy, Milan

Distribution Channel

10

Final customer sales

Division

00

Cross-division

Sold-To Party

2401

Napoli Export

PO Number

PO-##

Requested Delivery Date

One week from today’s date

Delivering Plant

2400

Material

T-F2## Pump PRECISION 102

Quantity

20

DC Milan

Choose Enter if you receive the message, “Change in invoice date: The billing date is redetermined.” This message has no impact on the ATP check. Analyze the “APO Availability Check: Results Overview.” Display all the subnodes. To do so, choose Display All Subnodes. An advanced availability check method is executed. First, a product availability check is executed for the source location product T-F2## / 2400. To check, choose Product Availability Overview in the first results row. A cumulated ATP quantity cannot be determined for the location product T-F2## / 2400. The system now calls the rules-based ATP check and the rule TF2##_2400 is determined using the condition technique. To examine this, choose Rule in the first results row. The Rule Maintenance screen appears. First, a location substitution is executed on location 2500. Go to the location substitution procedure for rule TF2##_2400. A product availability check is then executed. The activity 001 is assigned to location 2500. Choose Profiles and Parameters to go to the maintenance screen for location determination activities. The location determination activity 001 controls “availability check only, no production.” To return to the APO Availability Check: Results Overview screen, choose Back. The cumulated ATP quantity on the material availability date is 10 pieces. The first delivery proposal is thus 10 pieces of T-F2## from location 2500. To verify this, choose Product Availability Overview in the second results row.

(C) SAP AG

SCM670

28

The next substitution step is now executed. Location 2500 is substituted by location 2300. A product availability check is executed here first. Go to the location substitution procedure for the rule TF2##_2400. The activity 002 is assigned to location 2300. Choose Profiles and Parameters to go to the maintenance screen for location determination activities. The location determination activity 002 controls “first availability check, then production.” To return to the APO Availability Check: Results Overview screen, choose Back. There is no cumulated ATP quantity for the product T-F2## in location 2300. For this reason, production is now called directly from the availability check (Capable-to-Promise). This means that a temporary planned order is created in location 2300 for 10 pieces of product T-F2##. The confirmation is made based on this planned order. The second delivery proposal is therefore T-F2## from location 2300. To verify this, choose Planning Log. If required, double-click the rows with the green dot in the navigation area to read the message text. To return to the APO Availability Check: Results Overview screen, choose Back. Copy the delivery proposals into the order. To do so, choose Copy All. Confirm the message that states that a new price determination will be executed. The delivery proposals are shown as subitems in the order. Stay in transaction VA01 (Create Sales Order). Do not save the order yet! 7-4

Analyze the product view for product T-F2## in location 2300. Choose SAP Easy Access menu: Production Planning → Interactive Production Planning → Product View. Planning Version:

000

Product:

T-F2##

Location:

2300

Choose Enter. You see a (temporary) planned order for 10 pieces and a related planned independent requirement that protects the planned order from concurrent accesses. The planned order and the related planned independent requirement were created directly from the availability check. 7-5

Now save your sales order from exercise 7-1. Order number:________________________________________________________ Choose Save in transaction VA01.

(C) SAP AG

SCM670

29

7-6

Analyze the product view for product T-F2## in location 2300 after you have saved the order. You see your sales order as a requirement. The requirement coverage element is the planned order. The planned independent requirement has been deleted.

7-7

Analyze the settings for Capable-to-Promise. 7-7-1 Which requirements type was determined for the second subitem in your sales order? Call the transaction VA03 (Display Sales Order). Enter your order number. Choose Enter. Go to the Procurement tab page. The requirements type is KSV. 7-7-2 To which requirements class is this requirements type assigned in SAP R/3 Customizing? Choose SAP R/3 IMG: Sales and Distribution → Basic Functions → Availability Check and Transfer of Requirements → Transfer of Requirements → Define Requirements Types. Search for requirements type KSV in the list. Requirements class: 050 Note: This requirements class is transferred to SAP APO within the availability check as a check mode and controls the selection of the check instructions. 7-7-3 Which type of production has been defined for check mode 050 in SAP APO? Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → General Settings → Maintain Check Mode. Select check mode 050 and choose Details. Production type: standard = (Capable-to-Promise) 7-7-4 Is production called from the relevant check instructions? Analyze the relevant check instructions. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → General Settings → Maintain Check Instructions. Select the entry check mode 050 / business event A and choose Details. Start production: Availability check only, no production In other words, production is not started from the check instructions. 7-7-5 How or from where is production started for the location product T-F2## / 2300 within the availability check?

(C) SAP AG

SCM670

30

From the location determination activity 002 that is assigned to the location substitution 2300 in the location determination procedure for the rule TF2##_2400. (See 7 - 1)

(C) SAP AG

SCM670

31

Multilevel ATP Check: 7-8

Analyze the main prerequisites for the multilevel ATP check. 7-8-1 Examine the production process model for the product T-F3## in location 1000. Which components does the product T-F3## consist of? Choose SAP APO Easy Access menu: Master Data → Production Process Model → Production Process Model. Select Choose Plan Through PPM. Product:

T-F3##

Location:

1000

Choose Display. Choose the Products tab page. T-B1## / T-B23## / T-B3## / T-B4## 7-8-2 Examine the production process model for component T-B1## in location 1000. Which components does this product consist of? Choose SAP APO Easy Access menu: Master Data → Production Process Model → Production Process Model. Select Choose Plan Through PPM. Product:

T-B1##

Location:

1000

Choose Display. Choose the Products tab page. T-T1## / T-T2## 7-8-3 Verify which settings are necessary in the product master using the header material T-F3## in location 1000 as an example. Have a check mode and an ATP group been maintained? Has the PP/DS horizon been maintained? Choose SAP APO Easy Access menu: Master Data → Product. Enter T-F3## as the product. Select the Location view and enter 1000 as the location. Choose Display to display the product data. Go to the ATP tab page. Check Mode: ZZZ ATP Group: 02 Go to the PP/DS tab page. PP/DS Horizon: 30 (C) SAP AG

SCM670

32

Note: If you have not entered a PP/DS horizon in the location product master, the system uses the PP/DS horizon from the planning version.

(C) SAP AG

SCM670

33

7-8-4 Has a production calendar been created for scheduling in the location master for location 1000? Choose SAP APO Easy Access menu: Master Data → Location → Location. Enter 1000 as the location. Choose Display. Go to the Calendar tab page. Production calendar: LOC1000 7-8-5 Examine the scheduling horizon for the multilevel ATP check. This should be smaller than or the same size as the PP/DS horizon. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO)  Supply Chain Planning → Production Planning and Detailed Scheduling (PP/DS) → Global Settings → Maintain Global Parameters and Defaults. Scheduling horizon for ATP tree structures: 30 7-9

Have a look at the Customizing settings for the multilevel ATP check. 7-9-1 Which production type has been defined for the check mode ZZZ? Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP Check) → General Settings → Maintain Check Mode. Select the check mode ZZZ. Choose Details. Production type: Multilevel ATP Check

(C) SAP AG

SCM670

34

7-9-2 Examine the Customizing settings for the check instructions with check mode ZZZ / business event A. Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP Check) → General Settings → Maintain Check Instructions. Select check mode ZZZ / business event A. Choose Details (magnifying glass icon). Note: The letters below in parentheses do not actually appear on the Check Instructions screen – they are given here to complete the on-screen abbreviations. Product check: First step Product allocation (check): No check Forecast (check): No check Rules-based ATP (check): Do not select Start product(ion): First availability check, then production Production time: After executing all basic methods Compnts Remain. Reqmt: Create remaining requirement at header level Conversion Mode – ATP Tree Structure: Create several planned orders Business Event Multilevel ATP: _____________________ The remaining parameters in the check instructions are not relevant and you can leave the default values as they are.

(C) SAP AG

SCM670

35

7-10

Enter a sales order in SAP R/3. Call transaction VA01 (Create Sales Order). Enter the following data: Field Name or Data Type

Values

Order Type

OR

Standard order

Sales Organization

1000

Germany, Frankfurt

Distribution Channel

10

Final customer sales

Division

00

Cross-division

Sold-To Party

1000

Becker, Berlin

Ship-To Party

1000

Becker, Berlin

PO Number

PO-##

Requested Delivery Date

Two weeks from today’s date

Material

T-F3##

Quantity

15 PC

Choose Enter if you receive the message, “Change in invoice date: The billing date is redetermined.” This message has no impact on the ATP check. Analyze the APO Availability Check: Results Overview. Display all the subnodes. To do so, choose Display All Subnodes. In the row Schedule Line 001, you see that the complete requirement quantity can be confirmed for the requirements date, even though there is no cumulated ATP quantity available for product T-F3## on the requirements date. To verify this, choose Product Availability Overview in the first results row. A cumulated ATP quantity cannot be determined for the location product T-F3## / 1000. There can only be a confirmation for product T-F3## because the components are available and product T-F3## can therefore be produced. Examine the product availability for the component T-B23##, for example. To do so, choose Product Availability Overview. There is a sufficient cumulated ATP quantity for this component. This does not apply to component T-B1##. At first, only 10 pieces can be confirmed for component T-B1## because the cumulated ATP quantity is only 10 pieces on the requirements date. To verify this, choose Product Availability Overview. The system now checks if component T-B1## can be produced. To do so, it checks the availability of the required components (T-T1## and T-T2##) for the remaining requirement. The components are available in sufficient quantities. For this reason, an additional five pieces can be confirmed for the product T-B1##. The missing parts list also provides this information. To verify this, choose Missing Parts List. Copy the delivery proposal into the order. To do so, choose Copy All. Save the order.

(C) SAP AG

SCM670

36

Choose Save in transaction VA01. Order number: ______________________________________________________________ 7-11

Analyze the product view for product T-F3## in location 1000. Choose SAP Easy Access menu: Production Planning → Interactive Production Planning → Product View. Planning Version:

000

Product:

T-F3##

Location:

1000

Choose Enter. You see your sales order as a requirements element. A planned order has not yet been created. The results of the ATP check have been saved in an ATP tree structure. Receipt elements are created once this ATP tree structure has been converted. Note: Depending on the scheduling horizon and the PP/DS horizon, a receipt element can be created immediately in PP/DS when the sales order is saved. In this case, the value (days) chosen in the scheduling horizon for the multilevel ATP check must be large enough so that the ATP tree structure can be converted immediately (and then deleted) and so that a procurement proposal can be generated automatically. The ATP tree structure is always converted per request schedule line of the sales order. 7-12

Display the ATP tree structure that has just been generated. Choose SAP Easy Access menu: Global ATP → Environment → Technical Monitors → ATP Tree Structures. Use your user and the generation date from today to make the selection. Choose Execute.

(C) SAP AG

SCM670

37

8 Backorder Processing

Contents:  Backorder processing 

In the background (batch)



Interactive postprocessing



In simulation

 Filter  Sorter

 SAP AG 2003

(C) SAP AG

SCM670

1

8.2 Backorder Processing: Objectives

At the conclusion of this unit, you will be able to:  Understand the consequences of revising confirmed quantities and dates in backorder processing (BOP)  Set up and use the filter to select sales orders for BOP using different criteria  Use sorting to reassign priorities of customer requirements  Simulate backorder processing  Execute batch and interactive backorder processing

 SAP AG 2003

(C) SAP AG

SCM670

2

8.3 Backorder Processing: Course Overview Diagram

1

Course Overview 2 2

Global ATP / OLTP Interface 3 3

Selection of Check Method 4

Product Availability Check

5 Check Against Product Allocations 6 7 8 9

Rules-Based Availability Check Production Within the ATP Check

Backorder Processing

Scheduling

 SAP AG 2003

(C) SAP AG

SCM670

3

8.4 Backorder Processing: Business Scenario

 Until now, Maxitec Ltd.'s orders were confirmed according to the usual ATP check principle: "first come, first served." However, Maxitec Ltd. might also want to redistribute confirmed quantities according to other priorities that override the results of the previous ATP check.  Backorder processing in Global ATP in SAP APO is able to monitor customer requirements entered (simulation) and then, through further analysis, revise or even remove backorder situations.

 SAP AG 2003

(C) SAP AG

SCM670

4

8.5 Backorder Processing

Quantity

Time

06/00

07/00

08/00

09/00

Stock Sales order

 SAP AG 2003



What is backorder processing?  Backorder processing in SAP APO fulfills a basic request to Supply Chain Management that consists of changing confirmed quantities and dates within the ATP check.  Backorder processing is essentially implemented to process entered requirements and to diagnose and cancel backorder situations.



Three functions are available for processing backorders in SAP APO:  Backorder processing  Interactive backorder processing  Interactive postprocessing of a batch run



Note: Only sales documents are taken into account.

(C) SAP AG

SCM670

5

8.6 Backorder Processing (2)

Quantity

Time

06/00

07/00

08/00

09/00

Stock Sales order

 SAP AG 2003



When is backorder processing performed?  Backorder processing can be scheduled interactively or in the background (regularly, if necessary). For example: After a planning run in PP/DS, in Supply Network Planning, or after changes in the locationspecific product master data for ATP After a changed availability situation After the arrival of late orders with high priority



Prerequisites:  Relevant settings for backorder processing  When overwriting the results of the availability check in interactive backorder processing, you must be in a position to guarantee that a receipt element being procured can be covered.

(C) SAP AG

SCM670

6

8.7 Backorder Processing (3)

Quantity

Time

06/00

07/00

08/00

09/00

Stock Sales order Planned order  SAP AG 2003



Below is a typical ATP process that results in the need for backorder processing:  You perform an availability check, for example, using the checking horizon (replenishment lead time).  There is a shortage because the checking horizon has expired and no new receipt elements are found.  You execute backorder processing and reset the confirmation of the order items so that other (as yet unconfirmed) order items can be confirmed.  The changed data can be transferred to the connected OLTP system where the actual update takes place.

(C) SAP AG

SCM670

7

8.8 Backorder Processing (4)

Quantity

Time

06/00

07/00

08/00

09/00

Stock Sales order Planned order  SAP AG 2003

(C) SAP AG

SCM670

8

8.9 Backorder Processing: The Process AMonitor

Individual

Alert Filter

Filter

PP/DS

SNP

Master data

Net Change Filter

SORT: Using priorities

Backorder processing (batch) Backorder processing (interactive)  Simulation  Interactive postprocessing  Posting of results to SAP R/3 or legacy system  SAP AG 2003

Overview of backorder processing:  Interactive backorder processing means the manual redistribution of confirmed quantities to several orders.  Batch backorder processing corresponds to rescheduling in SAP R/3.  In comparison to backorder processing in SAP R/3, backorder processing in SAP APO is enhanced by the following functions:  Filtering can be configured.  The sort can be configured.  Scheduling can be configured.  Interactive backorder processing and batch backorder processing can be combined. 

(C) SAP AG

SCM670

9

8.10 Backorder Processing: Filtering Selection using netchange (SAP standard) When a change occurs in the supply situation due to a change or a planning run in PP/DS, SNP, or in changes to the master data, the location product for backorder processing (interactive/batch) is selected or marked. A netchange indicator, which is evaluated using a filter type, is used.

Alerts analysis (SAP standard) The alerts are generated through changes in Production Planning and Detailed Scheduling (PP/DS), a change in the supply situation, or during the availability check. Within the Alert Monitor framework, interactive backorder processing can be called directly from the Alert Monitor to help cancel alerts.

Individually configurable filter

 SAP AG 2003

Integration of backorder processing execution with selection filters 

Batch backorder processing can be included in a call sequence between PP/DS or SNP and interactive backorder processing.  Selection using the netchange filter: When a change occurs in the supply situation due to a change or a planning run in PP/DS, SNP, or changes to the location-specific master data, the location product for backorder processing (interactive/batch) is selected or marked. A netchange indicator is used for the selection.  Evaluation of alerts (ATP alerts, PP/DS alerts): To start backorder processing, you can also evaluate the alerts. The alert evaluation is an alternative to the filter that selects the orders for batch backorder processing. Within the framework of the Alert Monitor, you can call up backorder processing directly to help "clean up" alerts.  If an earlier delivery is necessary, Transportation Planning and Vehicle Scheduling (TP/VS) selects orders using alerts so that the availability check for these orders can be performed later. You can configure the orders that you want to be considered in backorder processing. The orders are selected using a filter.

(C) SAP AG

SCM670

10



Note: Backorder processing for stock transport orders is not currently supported.

(C) SAP AG

SCM670

11

8.11 Backorder Processing: Filtering (2) Order categories for BOP filter

 SAP AG 2003

Filtering of order items  Configurable filter  You can use characteristic values to select the order items that you want to be considered in batch backorder processing. In a filter type, you define the order categories to be considered and the characteristics that should be used for the filtering. You can store the characteristic values that should be considered for filtering in a filter variant for the filter type. You define the filter type under Global ATP -> Environment -> Current Settings -> Filter Type.  SAP_ALERT (delivered as standard)  Orders affected by the Alert Monitor are selected using this filter.  SAP_NETCHANGE (delivered as standard)  Orders for location products, in which the netchange indicator is set, are selected.

(C) SAP AG

SCM670

12

8.12 Backorder Processing: Sorter 20 different criteria

Sort sequence ascending / descending / special sort  SAP AG 2003

Sorting orders 

You can use the entries in the sort profile to define the sequence in which the order items are processed in backorder processing. In the sort profile, you specify the characteristics, their sequence (or weighting), and the sort direction. You define the sort profile under Global ATP -> Environment -> Current Settings -> Sort Profile.

If the sorting is not sufficient (for example, for the customer number), you can define a special sorting for the characteristic values (for characteristics for which a simple sorting does not make sense). You define the special sorting under Global ATP -> Environment -> Current Settings -> Special Sorting. If you have maintained a special sorting, you can enter this in the sort profile.  If none of the existing sort options meet your expectations, you can make use of the standard customer exits (for details, see the online documentation for Global ATP). 

(C) SAP AG

SCM670

13

8.13 Backorder Processing: Execution Mode Results update Direct update of the BOP results. The allocated quantities are locked by temporary quantity assignments until the connected OLTP system has completed the update. The results can be checked subsequently in a log list.

Simulation The assigned quantities are not protected by temporary quantity assignments. The results can be checked in a log list.The results of backorder processing cannot be changed or updated interactively.

Postprocessing through interactive backorder processing The results of backorder processing are not updated immediately.They are saved in a buffer and can be further processed or rejected through interactive backorder processing.The assigned quantities are locked by temporary quantity assignments. The update can also be triggered or rejected independently of interactive backorder processing.

 SAP AG 2003

(C) SAP AG

SCM670

14

8.14 New Rule Evaluation in Backorder Processing Rule evaluation:

active

Evaluation horizon:

10 days

Today

Today + 10 days

10

10

20

10

20

30

10

Main item

20

20

30

30

10

10

Subitem

New rule evaluation

 SAP AG 2003



If the Rule Evaluation indicator is set, the rules are executed again in backorder processing in accordance with the check instructions. The new check is executed for the main item and not for the subitems (resulting from the previous check).



Using the rules evaluation horizon, you can protect items that are close to their execution from being checked with rules again. If you specify a horizon, only items with all availability dates beyond this horizon (starting from today’s date) are checked with rules. Items within this horizon undergo a “normal” ATP check at subitem level.

(C) SAP AG

SCM670

15

8.15 Backorder Processing: Distribution of Quantities

 Request  Confirmation 

Option 1: Add remaining requirements



Option 2: Confirmation, first version



Option 3: Rescheduling 

Material availability date



Goods issue date

 SAP AG 2003



Request: The quantity requested for the requested delivery date is transferred to the product availability check. The dates are redefined for all documents.



Confirmation: The availability check is performed for the confirmed quantity at the requested time. For backorders (the material availability date is past), use the Rescheduling indicator.

(C) SAP AG

SCM670

16

8.16 Backorder Processing: Distribution of Quantities (2) Option 1: Confirmation, add remaining requirements 30 50

30

50

Sales order 30

30

Goods receipt

20

Confirmation

 SAP AG 2003

Assumption of a new receipt that would allow completion on the requested date BOP with confirmation and option 1:  System tries to keep old confirmation  Remaining quantities are checked with the original requested date  Results  Original confirmation (30 units) still delayed  Remaining quantity (20 units) confirmed for original date  

(C) SAP AG

SCM670

17

8.17 Backorder Processing: Distribution of Quantities (3) Option 2: Confirmation, first version

30 30

50

30 30

50

Sales order 50

50

Goods receipt

30

Confirmation

30

 SAP AG 2003



The example above shows three different situations for a sales order.  Step 1: Order creation – confirmation delayed and incomplete  Step 2: First backorder processing (with confirmed quantities) confirms even later, because the example assumes that the planned receipt is delayed  Step 3: Additional planned receipts; the system confirms – after a new BOP run – for the date confirmed originally

(C) SAP AG

SCM670

18

8.18 Backorder Processing: Distribution of Quantities (4) Option 3: Confirmation, rescheduling 30 50

30

Today

30 50

Sales order 30

Goods receipt Confirmation

Today  SAP AG 2003

Rescheduling 

If you set this indicator, dates are redetermined, in principle, if the date has passed. The date can either be the material availability date or the goods issue date. The material availability date was chosen in the example given above.



If you do not set this indicator, the dates are not redetermined.



Exception: In general, dates in the past are redetermined.

(C) SAP AG

SCM670

19

8.19 Direct Update of Backorder Processing Sales and Distribution SAP R/3

SAP APO

SD Backorder processing

Document Sales orders Event Process event

Send

Write temporary quantity assignment

Update Update time series in SAP liveCache Delete temporary quantity assignment  SAP AG 2003

Process  You carry out batch backorder processing to redistribute previously confirmed quantities for the order items of backorders according to a list of priorities. 

As long as the update in the connected OLTP system is not yet completed, the assigned quantities are protected in SAP APO as temporary quantity assignments.



The changes are updated in SAP R/3.



The update is confirmed to SAP APO.



You can delete the results in the buffer. These are only used as a log.



If you have to define unexpected, short-term sales priorities, use interactive backorder processing.

(C) SAP AG

SCM670

20

8.20 Batch Backorder Processing with Postprocessing Sales and Distribution SAP R/3

SAP APO Event

SD Batch backorder processing

Document Sales orders

Event

Process event

Send

Reject

Interactive backorder processing Reserve temporary quantity assignment

Update Update time series in SAP liveCache Delete temporary quantity assignment  SAP AG 2003

Purpose 

You do not want to update the results of backorder processing directly; you want to carry out an “operative simulation” first.

Prerequisites 

You have maintained the settings for backorder processing and have orders in SAP APO.

Process 

Set the Execution mode with postprocessing parameter on the Parameters Process tab page and carry out backorder processing.



The results are not updated immediately - they are saved in a buffer.



To process the results, call the results display. The assigned quantities are protected by temporary quantity assignments.



From the results list, you can process the results using interactive backorder processing.



You can update or reject the results afterwards.



If necessary, you can delete the results list or the results in the buffer.

(C) SAP AG

SCM670

21

8.21 Backorder Processing: Summary

You are now able to:  Understand the consequences of revising confirmed quantities and dates in backorder processing (BOP)  Set up and use the filter to select sales orders for BOP using different criteria  Use sorting to reassign priorities of customer requirements  Simulate backorder processing  Execute batch and interactive backorder processing

 SAP AG 2003

(C) SAP AG

SCM670

22

8.22Backorder Processing: Exercises + Solutions Unit: Backorder Processing

A typical check at Maxitec Ltd.: Maxitec Ltd. uses SAP R/3 and SAP APO to plan all delivery-related tasks in the supply chain. On execution of the product availability check at sales order entry, the products are checked for availability with reference to the replenishment lead time. What goes wrong with delivery confirmation at Maxitec Ltd.? This check is performed automatically and always successfully when sales documents are created in the OLTP system beyond the checking horizon. After a few days, this sales order is within the checking horizon and it is possible that there are no receipts to cover the existing confirmed quantities. •

The aim of this exercise is that you become familiar with both interactive backorder processing and backorder processing in the background in SAP APO. The options, functions, and techniques that are available in these areas are more fully explored.

At the conclusion of this exercise, you will be able to:

(C) SAP AG

•

Set up backorder processing using product T-F11## as an example

•

Enter three sales orders for T-F11## in the SAP R/3 OLTP transaction system, perform “real” interactive availability checks, and make delivery commitments with corresponding schedule lines.

•

Verify that the inventory situation and existing delivery commitments for product T-F11## in both SAP APO and the OLTP system do not match the delivery priorities of the order.

•

Create a selection filter in the configuration of backorder processing in the background that selects sales orders by product number and order quantity, for example.

•

Create a sort sequence that sorts the filtered sales orders by delivery priority, for example; these delivery priorities are manually set at sales order entry in the OLTP system.

•

Perform interactive backorder processing for material T-F11## in location 2500 from SAP APO: You will then execute backorder processing in the background.

•

Verify that the exclusive quantity locks have been enforced in SAP APO for the new delivery commitments.

•

Generate the temporary backorder processing result and make permanent changes to the confirmations and the new schedule lines in SCM670

23

both the SAP APO system and the OLTP system.

Actions for this exercise: In this exercise, you will set up backorder processing using product T-F11## at location 2500 (Rotterdam). To verify and test these settings, you will first run interactive backorder processing for the PC product T-F11## in SAP APO. Afterwards, you will process the requirements in the background. Exercise data: You will use T-F11## as your product, where ## is your group number. In addition, you will use location 2500 (Rotterdam) as your distribution center (DC). This product and this plant are used throughout the backorder processing exercises. STAGE 1 – CHECKING THE CONFIGURATION OF THE PRODUCT AVAILABILITY CHECK 8-1

Examine the ATP data for product T-F11## in location 2500.

Choose SAP Easy Access menu: Master Data → Product. Enter T-F11## as the product. Select the Location view and enter 2500 as the location. Choose Display to display the product data. Go to the ATP tab page. What is the check mode? 030 Which ATP group has been defined? 02 8-2 If you create a sales order in SAP R/3 for the product T-F11## in location 2500, which check instructions are determined? Make sure that only a product availability check is executed. (in the check instructions 030/A, product allocation, rules, and production are deactivated) Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP Check) → General Settings → Maintain Check Instructions. Select check mode 030 / business event A. Choose Details (magnifying glass). Product check:

First step

Product allocation (check):

No check

Forecast (check):

No check

(C) SAP AG

SCM670

24

Rules-based ATP (check):

Do not select

Start product(ion):

Availability check only, no production

The remaining check instruction parameters are not relevant.

(C) SAP AG

SCM670

25

Examine the relevant check control for the product availability check for product TF11## in location 2500. The checking horizon should not be considered! 8-3

Choose SAP APO IMG: SAP Advanced Planning and Optimization (SAP APO) → Global Available-to-Promise (Global ATP) → Product Availability Check → Maintain Check Control. If necessary, double-click ATP Check Control: General to display this view. Select ATP group 02 / business event A. Choose Details (magnifying glass). The Consider CH indicator is not selected. STAGE 2 – INITIAL DATA ENTRY Examine the initial situation for product T-F11## by going to the product view report in the PP/DS menu: 8-4

Choose SAP APO Easy Access menu: Production Planning → Interactive Production Planning → Product View. Enter planning version 000, product T-F11##, location 2500, and choose Enter. As the initial starting value, you should find 100 pieces of initial stock for product TF11## at DC 2500. 8-5

Now enter a purchase requisition for product T-F11## in location 2500. Stay in the product view. Choose Change. Confirm the propagation range SAPALL, if required. Enter December 17 of the current year as the availability date of the purchase requisition. Enter 100 pieces as the receipt quantity. Choose location 2300 as the procurement alternative. To do so, select the first row and choose Adopt. Save your entries.

(C) SAP AG

SCM670

26

8-6

Now you have to enter three sales orders in a specified sequence. To begin entering the sales orders, you have to go to the OLTP system. Enter transaction VA01 (Create Sales Orders). Enter the following data on the initial screen: Order Type:

OR

Sales Organization:

2500

Netherlands/Rotterdam

Distribution Channel:

10

Final customer sales

Division:

00

Cross-division

The fields in which data has to be entered for each sales order are: Sold-To Party, PO Number, Requested Delivery Date, Delivering Plant, Material, Order Quantity, and Delivery Priority. The field data, which must be entered in the correct sequence for each of the three sales orders, is presented in the following table: Order Sequence

Sold-toParty / Purchase Order No.

Requested Delivery Date / Delivering Plant

Material / Quantity / Delivery Priority

Please fill in – Confirmed quantity and date for each material availability date resulting from the ATP check

1

2502

05/12/ current year

T-F11##

___80____, _05/12/200*_

80/ 3

_________, __________

T-F11##

___20____, _26/11/200*_

80/ 1

___60____, _18/12/200*_

T-F11##

___0____, _12/12/200*_

80/ 2

___40____, _18/12/200*

PO-001

2500 2

2502 PO-002

26/11/ current year 2500

3

2502 PO-003

12/12/ current year 2500

Acknowledge the dialog box that appears concerning changes to the invoice/billing date. Note: The first sales order results in a single delivery of 80 pieces. The second sales order results in two schedule lines: 20 pieces on the original requested date, and a further schedule line of 60 pieces on the purchase requisition date. The third sales order results in two schedule lines: No confirmation on the original requested delivery date, and 40 pieces on the purchase requisition date.

(C) SAP AG

SCM670

27

STAGE 3 – UNDERSTANDING THE INITIAL SITUATION VS. THE DELIVERY PRIORITIES Current scenario: Now that you have finished entering the purchase requisition and sales order data, there are 100 pieces in stock. In addition, there is a purchase requisition for 100 pieces with the receipt date of December 17 this year. Three customers have each placed an order with you for 80 pieces of T-F11##. The following table illustrates the resulting schedule lines. Enter your sales order numbers in the Customer (order #) column in the table below for handy reference – and keep the initial situation in mind. Order Sequence

Customer (order #)

Schedule Line

Requirement Quantity/Date

Confirmed Quantity/Date

Order 1

2502

1

80 05/12/200*

80

05/12/200*

1

80 26/11/200*

20

26/11/200*

60

18/12/200*

80 12/12/200*

0

12/12/200*

( Order 2

2502 (

Order 3

) )

2502 (

2 1

)

40

18/12/200*

Note: Since the scope of the ATP check does not include the checking horizon for the replenishment lead time, the last customer has an outstanding unconfirmed quantity of 40 pieces from the requested 80 pieces. We now want to manually reschedule product T-F11## so that the we obtain the following final results: A)

Order 2 (delivery priority 1): All 80 pieces are confirmed for the requested date 26.11.200*.

B)

Order 3 (delivery priority 2): 20 pieces are confirmed for the requested date 12.12.200* and 60 pieces for 18.12.200*.

C)

Order 1 (delivery priority 3): Only 40 pieces can be confirmed for 18.12.200*.

(C) SAP AG

SCM670

28

STAGE 4 – UNDERSTANDING THE EXPECTED FINAL RESULT The following table shows the schedule lines that result from backorder processing according to the delivery priorities mentioned earlier. You can use this table to understand how the final confirmation situation looks after backorder processing. Order Sequence/Delivery Priority

Customer (order #)

Schedule Line

Requirement Quantity/Date

Confirmed Quantity/Date

1/3

2502

1

0

12/05/200*

( )

2

80 012/05/200*

40

18/12/200*

2502

1

80 26/11/200*

80

2502

1

20

12/12/200*

( )

2

80 12/12/200*

60

18/12/200*

2/1

( ) 3/2

26/11/200*

STAGE 5 – MANUAL BACKORDER PROCESSING 8-7

Execute manual backorder processing. Choose SAP APO Easy Access menu: Global ATP → Backorder Processing → Interactive Backorder Processing. Enter the following: Product T-F11##, location 2500, business event A. Choose Execute. Or Choose SAP APO Easy Access menu: Production Planning → Interactive Production Planning → Product View. Enter the following: Version 000, product T-F11##, location 2500. Choose Enter and then select the ATP tab page. Choose Change on the top left of the screen. Choose Enter to accept the SAPALL propagation range. In the product or ATP views, you need to go into change mode to begin processing. To do so, choose Change/Display on the left of the product view screen.

(C) SAP AG

SCM670

29

Manual steps to achieve the desired results: 1.

Select the second schedule line of order 2 (60 pieces) and then choose Delete Schedule Line at the bottom of the screen. This frees up 60 pieces from the purchase requisition for redistribution.

2.

Select the second schedule line of order 3 (40 pieces) and then choose Delete Schedule Line at the bottom of the screen. This frees up 40 pieces from the purchase requisition for redistribution.

3.

Change the first schedule line of order 1 from 80 pieces to 0 pieces. This frees up another 80 pieces for redistribution and allows us to redistribute the quantities as desired.

4.

Change the first schedule line of order 2 from 20 pieces to 80 pieces. This means that the requested quantity for the second order can be confirmed for the requested delivery date.

5.

Change the first schedule line of order 3 to 20 pieces and select this schedule line. Choose New Schedule Line. This is the icon to the right of the trash can. Change the newly created second schedule line for order 3. Enter 18.12.200* as the requirements date and 60 pieces as the confirmed quantity. Continue processing (by confirming any messages, if required).

6.

Select the first schedule line from order 1 and choose New Schedule Line. This is the icon to the right of the trash can. Change this new second schedule line. Enter 18.12.200* as the requirements date and 40 pieces as the confirmed quantity. Continue processing (by confirming any messages, if required). Now you have manually achieved the desired results. Do NOT save your work, as we will use the same data to perform rescheduling in the background.

(C) SAP AG

SCM670

30

STAGE 6 – SIMULATIVE BACKORDER PROCESSING WITH POSTPROCESSING 8-8

Create a filter type for product T-F11## in DC 2500 that selects orders based on the selection criteria product number and order quantity. Choose SAP APO Easy Access menu: Global ATP → Environment → Current Settings → Filter Type. Choose New Entries. Enter Filter ## as the name of the filter. Choose Enter again. Select Filter ##, and double-click Order Categories on the left of the screen. Choose New Entries. Enter BM as the ATP category “sales order.” Double-click Criteria on the left of the screen. Enter the following values for the field names of these filter type criteria. Choose New Entries. MATNR

Product

WMENG

Requested quantity

MEINS

Base unit

Choose Save and confirm the Prompt for Customizing Request. Go back to the main menu. 8-9

Create a sort profile with the sales order delivery priority as the sort criterion. Choose SAP APO Easy Access menu: Global ATP → Environment → Current Settings → Sort Profile. Choose New Entries. Enter Sort ## as the name of the filter. Choose Enter again. Select Sort ##, and double-click Criteria on the left of the screen. Choose New Entries. Enter LIFPRIO (delivery priority) as the sales order sort criterion and 1 as the sequence number. You should choose the Change Sort(ing) button until you have an ascending sort order. Note: Alphanumeric fields (such as ATP category) are associated with a special sort. There are seven predefined sort criteria. Choose Save and confirm the Prompt for Customizing Request. Go back to the main menu.

(C) SAP AG

SCM670

31

8-10

Make your settings for the worklist and the variants. Choose SAP APO Easy Access menu: Global ATP → Backorder Processing → Backorder Processing Worklist. Enter Filter ## in the Filter Type field. Choose Filter. A screen appears containing three tab pages – one of these tabs is called Document. Enter the following values for the document filtering parameters listed below: Product:

T-F11##

Requested quantity:

70 to 90

Base unit of measure:

PC

Make sure that the Sales Order indicator has been selected on the Order types involved tab page. The following indicators must be selected on the Confirmation situation tab page: Requested date Delivery proposal Requested date (partial) Delivery proposal (partial) Consider partial delivery Save the data with the variant name FILTER ##. Go back to the Worklist control screen. Ensure that the Variant name field contains the name FILTER ##. Enter Sort ## in the Sort profile field. Choose Sort order. Make sure that the delivery priority is listed in the sort criteria. No name is required for the sort criteria variant. Go back to the Worklist control screen. To execute the worklist, choose Execute. Examine the worklist and the current situation. Suggestion: Expand the list using the vertical double arrow. Use the display variant to include the Delivery priority field.

(C) SAP AG

SCM670

32

8-11

Execution of backorder processing with postprocessing: Choose SAP APO Easy Access menu: Global ATP → Backorder Processing → Backorder Processing in the Background. Enter the filter type and filter type variant (both called Filter ##) created in the filter fields. Enter the sort profile (Sort ##) in the corresponding field. Select the next tab page, Parameters Process. Under Execution Mode select With postprocessing. Enter a job name (for example – Job ##) in the Name field at the top of the screen. Choose Execute. Examine the simulated results with backorder processing. Examine the backorder processing result separately.

8-12

Choose SAP APO Easy Access menu: Global ATP → Backorder Processing → Backorder Processing Result. Select your Job ## in the Name field at the top of the screen. Choose Results display. Expand the information on the results list for order confirmation. You also have the option to choose the display variant so that the delivery priority is included. Go back to the Implementation Guide (IMG). 8.13

Update the backorder processing results.

Choose SAP APO Easy Access menu: Global ATP → Backorder Processing → Update Backorder Processing. Select your Job ## in the Name field at the top of the screen. Choose Update. Go to SAP R/3 and the check results.

(C) SAP AG

SCM670

33

9 Scheduling

Contents:  Times  Dates  Determining the times  Calculating the dates

 SAP AG 2003

(C) SAP AG

SCM670

1

9.2 Scheduling: Objectives

At the conclusion of this unit, you will be able to:  Explain and set up transportation and shipment scheduling  List the activities relevant for transportation and shipment scheduling and define times (durations) in SAP APO  Define how the relevant times (durations) are determined  Understand and analyze the calculation of transportation and shipment dates

 SAP AG 2003

(C) SAP AG

SCM670

2

9.3 Scheduling: Course Overview Diagram

1

Course Overview 2 2

Global ATP / OLTP Interface 3 3

Selection of Check Method 4

Product Availability Check

5 Check Against Product Allocations 6 7 8 8

Rules-Based Availability Check Production Within the ATP Check

Backorder Processing

9 Scheduling  SAP AG 2003

(C) SAP AG

SCM670

3

9.4 Scheduling: Business Scenario

 Maxitec Ltd.'s customers expect the confirmed delivery dates to be strictly adhered to.  The worldwide distribution of customers, the use of various means of transport, heterogeneous shipping processes, and varying shipping volumes lead to very different processing times.  From experience, Maxitec Ltd. is aware of these processing times, which must be defined in SAP APO.  The relevant times must be determined based on activities, and the transportation and shipment dates have to be calculated so that transportation and shipping activities can be started on time.  SAP AG 2003

(C) SAP AG

SCM670

4

9.5 Transportation and Shipment Scheduling

Shipment scheduling: Takes account of activities required to start the shipping of the products. These include loading, picking, and packing. The material availability date and the loading date are calculated from the duration of these activities.

Transportation scheduling: Takes account of all activities required for preparing and executing the transportation. This includes transportation planning as well as the actual transportation. The goods issue date and MRP date are determined from the duration of these activities, starting from the (requested) delivery date.

 SAP AG 2003



In SAP APO, shipping activities and transportation can be scheduled automatically.



The aim of the SAP APO transportation and shipment scheduling functions is to guarantee consistent, automatic scheduling of shipping and transportation processes that occur in various systems.



Transportation and shipment scheduling take place in SAP APO if an availability check is executed in SAP APO for the products. Scheduling still takes place in the OLTP system for all other materials.



You decide for each sales document type whether transportation and/or shipment scheduling is executed.

(C) SAP AG

SCM670

5

9.6 Times (Durations)

 The transportation duration is the time required to transport a product to the customer.  The loading time is the time required to load the product.  The pick/pack time is the time required to assign goods to a shipment, to pick, and to pack.  The transportation lead time is the time required to organize the transportation of goods. This includes booking a ship and reserving a truck.  Unloading/loading time occur within the context of stock transfers.

 SAP AG 2003

Transportation and shipment scheduling are based on activities that have to be executed to allow products to be staged at the customer.  To calculate the shipping dates, SAP APO requires empirical values from the shipping department that can be defined in the form of transportation durations, loading times, pick/pack times, transportation lead times, and loading/unloading times in the system for various objects. 

(C) SAP AG

SCM670

6

9.7 Backward Scheduling Order Item Mat. Quantity RDD 10 4711 10 13.12.2005 Schedule line Delivery Order Date Qty 13.12.2005 10

Conf. Qty 10

Order date

Today

Material availability

Transportation Load planning

Goods issue

Requested delivery date

Unloading date

13.12.2005

Availability check

Transportation duration Loading time

Material availability date

Unloading duration

Transportation lead time

 SAP AG 2003



  



Pick/pack time

The material availability date is determined as a result of shipment scheduling. The product must be sufficiently available on this date so that you can deliver the product to the customer on the delivery date. The system calculates the time required for picking, packing, loading, and transporting the goods. Starting from the customer's requested delivery date, the system performs backward scheduling to calculate the material availability date. In-house activities such as picking/packing and loading are calculated on the basis of the shipping calendar entered in the location master. Transportation activities are calculated on the basis of the transportation calendar that is assigned to a transportation lane. If a transportation lane is not found or a calendar is not maintained there, the system makes a calculation without a calendar. Goods receiving hours specified by an OLTP system are supported in SAP APO. If an SAP R/3 system is connected to the SAP APO system and an unloading point is used in the SAP R/3 document, the master data (calendar and goods receiving hours) is taken into account in scheduling. If no calendar or goods receiving hours are maintained for the ship-to party in SAP R/3, the shipping calendar from the location master in SAP APO is used to restrict the goods receiving hours.

(C) SAP AG

SCM670

7

9.8 Forward Scheduling Order Item Mat. Quantity RDD 10 4711 10 13.12.2005 Schedule line DeliveryDate 13.12.2005 DeliveryDate 15.01.2006 Order date

Order Qty 10 Order Qty 0 Material availability

Conf. Qty 10 X Conf. Qty 10 Transportation planning

Load

Goods issue

Material Transportation availability planning

Requested Unloading deliverydate date Load

Today

13.12.2005 Availability check

Delivery date

Unloading date

15.01.2006

Availability check

Transportation lead time

 SAP AG 2003

Goods issue

Transportation duration Loading time

Unloading duration

Pick/pack time

If the material availability date derived from the requested delivery date is in the past or if the availability check is not successful, new material availability date(s) are determined in a successful availability check. The system uses this information to calculate a new delivery date or dates (forward scheduling).  Forward scheduling can be deactivated for each sales document type.  In extreme cases, no material availability date is determined in a successful availability check. A delivery date cannot be proposed, meaning that the schedule line remains unconfirmed. 

(C) SAP AG

SCM670

8

9.9 Defining Times (Durations) Scheduling step

Pick/pack time

PICK Scheduling step

Loading time

LOAD Scheduling step

Transportation lead time 1. Priority

Transportation duration

2. Priority

Transportation lanes Scheduling step TRAN

3. Priority

Unload

LEAD

Automatic calculation of the transportation duration

Scheduling step UNLD

 SAP AG 2003



The values of each shipment activity or transportation activity duration are defined depending on criteria in master data (scheduling steps).

(C) SAP AG

SCM670

9

9.10 Determining the Times: Condition Technique SD order

Scheduling procedure SCHEDL

Ship-To Party: 1000

Condition type: LEAD

ACC: LEAD

Deliv. Loc.: A

Condition type: PICK

ACC: PICK

Weight Grp: 500

Condition type: LOAD

ACC: LOAD

Condition type: TRAN

ACC: TRAN

Condition type: UNLD

ACC: UNLD

Access(es) No. Table Key 1

500

Ship-To/Del.Loc.

2

903

Weight Group

1. 2.

LEAD: 0.1 T

Scheduling step 903 LEAD 500 / B:

0.1 T

Scheduling step 500 LEAD 2000 / B:

0.25 T

 SAP AG 2003

Transportation and shipment scheduling with the condition technique has the following benefits:  Flexible determination of times (durations)  Use of to-the-minute times  Use of information from the OLTP system  The condition technique enables you to define specific durations (scheduling step[s]), depending on any criteria (fields from the field catalog) for each condition type (shipping or transportation activity). These durations are then determined using the characteristic values from the OLTP system.  Unloading duration, loading time, pick/pack time, and transportation lead time are determined exclusively using the condition technique.  The unloading duration is the time between the unloading date and the delivery date. It is mapped by the condition type UNLD.  The loading time is the time between the goods issue date and the loading date. It is mapped by the condition type LOAD.  The pick/pack time is the time between the loading date and the material availability date. It is mapped by the condition type PICK.  The transportation lead time is the time between the loading date and the transportation planning date. It is mapped by the condition type LEAD.  The time for the transportation is derived from the transportation duration of the transportation lane. If this is initial, or there is no transportation lane, this time is determined through the condition technique 

(C) SAP AG

SCM670

10

using the condition type TRAN. If no duration is determined here either, the duration is calculated using the distance between the start and destination locations and the average speed of the means of transport being used.  In scheduling with the condition technique, the receiving calendar is overwritten if corresponding data is transferred from an OLTP system when scheduling is called (for example, data from an unloading point with goods receiving hours of the ship-to party).  The following elements of the condition technique are fixed within scheduling:  Scheduling procedure SCHEDL  Determination of the scheduling procedure  The condition types You can also configure access sequences and condition tables.

(C) SAP AG

SCM670

11

9.11 Prerequisites for Scheduling  Activation of transportation or shipment scheduling for each sales document type in SAP R/3  Maintenance of transportation zones in the address data of the customer masters in SAP R/3  Transfer of customer with transportation zone from SAP R/3 to SAP APO by means of CIF -> Transfer of the transportation zone as a location + transfer of the customer as a location  If no customers are transferred to SAP APO, the transportation zones must be exported from SAP R/3 to SAP APO and the transportation zones assigned to locations in SAP APO. Locations of the type "transportation zone" may first have to be defined in SAP APO.  Maintenance of the geocoordinates of the locations in SAP APO  SAP AG 2003

(C) SAP AG

SCM670

12

9.12 Prerequisites for Scheduling (2)  Definition of the average speed for each means of transport in SAP APO  Creation of the SAP R/3 shipping conditions in SAP APO  Assignment of default means of transport to shipping conditions  Maintenance of weight and volume groups for scheduling  Execution of field mapping (possibly)

 SAP AG 2003

(C) SAP AG

SCM670

13

9.13 Scheduling: Summary

You are now able to:  Explain and set up transportation and shipment scheduling  List the activities relevant for transportation and shipment scheduling and define times (durations) in SAP APO  Define how the relevant times (durations) are determined  Understand and analyze the calculation of transportation and shipment dates

 SAP AG 2003

(C) SAP AG

SCM670

14

10 Appendix: Characteristics-Based Product Availability Check

 SAP AG 2003

(C) SAP AG

SCM670

1

10.2 Characteristics-Based Product Availability Check

 Product availability check at characteristic level for configured products and batches  Can be triggered at sales order entry or time of delivery  Only applies to the ATP basic method “product availability check”  Can carry out a simulative characteristics-based product availability check

 Product allocation can be carried out at characteristic level but uses other time series  Rules-based ATP does not support substitution of one characteristic value assignment by another characteristic value assignment for configured products or batches

 SAP AG 2003



Scope in SAP APO 3.0  Both configuration and classification characteristics can be used  The search strategy is at product/location level  Current restrictions: No product / location / characteristic substitutions

(C) SAP AG

SCM670

2

10.3 Integration of Characteristics in Time Series

Car / 92kW / Blue / Autom. air cond. / ...

GUID Confirmation

...

P2369ok2qn6AFW2WoSWr0m Time series

X

Stock Planned production

u. e o. an kW n on w W ut W W e m 0 e n lo k A k k ed Blu . / / 11 Gre d. / el / 75 d. / / 92 / 55 d R Y / / r / or con ine lor con or / ine con ine ine o ol ol ir ng o ir ol ng ir g ng C C A E C A C E A En E X X X X X X X X X XX X X X X XX X X X X X XX X X X X X X X X X XX X X XX X X X XX X X XX X X X X X X X X X X X X X X X X X X

 SAP AG 2003

The characteristics-based product availability check is possible for sales orders as of SAP APO release 3.0 (SP1). (Note with regard to terminology: In addition to the term “characteristics-based product availability check,” there is also the term “CDP-based availability check,” where CDP is derived from the English term “characteristics-dependent planning.”)  Note: Only the first basic method can currently be used in conjunction with CDP.  Batch classification characteristics and configuration characteristics are supported.  There is a new hierarchy level in SAP APO ATP:  Sublocation  Version  Characteristics combination  Note: The number of individual steps possible during the ATP check is increased to eight (new hierarchy level).  Although a characteristics-based product availability check is able to work with CDP characteristics as well as with iPPE (Integrated Product and Process Engineering) in principle, only CDP characteristics allow consistent processing at the present time. In comparison, the second basic method, “check against product allocations,” is able to work with both sets of characteristics.  Note: The method is only effective if the aggregation of time series is still given; in other words, the number of characteristics should not be too large. 

(C) SAP AG

SCM670

3

10.4 Selection of Characteristics for ATP APO product master Blue Color Red Green

211 054 677

Size

489 576 016 139

15 20 25 30

Qual. A B

720 955

Pack. Glass Plastic

815 005

Paper

ATP characteristics view

Char. key & ATP anchor X143CI6287G32756PD8113

211 576 720

MNO Y278HG852M88962FD4389

054 489 720

MNO P546SF143KL6287WZ5642

677 139 955

MNO

Color Size Quality MNO

632

Cat. Sloc

Vers

CC 0001 CH1 CC 0001 CH2 CC 0001 CH3

SAP liveCache

CK

P1 P2

X143... Y278... P546... -

x x x

 SAP AG 2003

  

The ATP-relevant characteristics are defined through the ATP characteristics view. Only discrete and completely specified groups of characteristics can be used. The GUID (globally unique identifier) encrypts the characteristics combination.



Based on this procedure, we recommend that you restrict the number of ATP-relevant characteristics as much as possible. On the one hand, this improves system performance; on the other hand, it ensures the suppression of the cumulation procedure in the time series if the number of characteristics combinations is too large.

 

Master data can be transferred from SAP R/3 into both systems (CDP, iPPE). In SAP APO Customizing, you have to define which classification system you want to use. Functions like characteristics propagation, characteristics-dependent pegging, and block planning can be used with CDP activated.

(C) SAP AG

SCM670

4

10.5 ATP Time Series with Characteristics

X143CI6287G32756PD8113 MNO

Cat. Sloc

Vers

CC 0001 CH1 BM 0001 CH2 CC 0001 CH3

SAP liveCache

CK

P1 P2

X143... Y278... P546... -

x x x Y278HG852M88962FD4389

P546SF143KL6287WZ5642  SAP AG 2003

Time series are displayed in the time series monitor.  Time series are displayed in the time series monitor as GUIDs. The GUID encrypts a characteristics combination. The icon Characteristics: not available or Characteristics: available appears in the time series display. If you double-click the icon, all characteristics that belong to the corresponding class are displayed. If the characteristics are not flagged as relevant for ATP – that is, if the products are not contained in any ATP characteristics view – the characteristics are displayed without valuation. 



You can call the time series monitor from the SAP Easy Access menu under Global ATP -> Environment -> Technical Monitors -> Time Series.

(C) SAP AG

SCM670

5