GATP

January 13, 2016

GLOBAL AVAILABLE TO PROMISE

Table of Contents Important Points: .....................................................................................................................................................9 Global Available To Promise (GATP) Overview .......................................................................................................11 Introduction: Global Available To Promise .............................................................................................................11 GATP Methods can be classified into three areas: ..................................................................................................11 Product Check .........................................................................................................................................................11 Product Allocation Check (PAL) ...............................................................................................................................11 Check against Forecast ...........................................................................................................................................11 Rules-Based ATP .....................................................................................................................................................11 Capable-to-Promise (CTP) .......................................................................................................................................12 Multilevel ATP ........................................................................................................................................................12 CTP and ML-ATP .....................................................................................................................................................12 Transportation and Shipment scheduling ...............................................................................................................12 Backorder Processing..............................................................................................................................................12 Integration ..............................................................................................................................................................13 Calling the ATP check from SAP APO ......................................................................................................................13 Calling the ATP check from SAP R/3........................................................................................................................13 gATP Configuration Settings in ECC:........................................................................................................................14 Availability Check and Transfer Requirements .......................................................................................................14 Checking Groups: ....................................................................................................................................................14 Define Checking Groups..........................................................................................................................................14 Checking Group for Availability Check .....................................................................................................................17 Definition: materials planning .................................................................................................................................17 Definition: Sales & Operations Planning...................................................................................................................17 Use 1: Availability Availability Checking and Materials Materials Planning................................. Planning................................. ........................... .....................................17 ........................ .............17 Definition: replenishment lead time ........................................................................................................................18 Use 2: Flexible Planning ...........................................................................................................................................18 Total sales order order requirements requirements........................... ......................... .................................................. ......................... ......................... .......................... 18 Use..........................................................................................................................................................................18 Definition: summarized requirements .....................................................................................................................18 Total delivery requirements ....................................................................................................................................18 1

January 13, 2016


Use..........................................................................................................................................................................19 Material Material block in availability availability check with transfer of qties .......................... ......................... ......................................19 ......................... .............19 Procedure ...............................................................................................................................................................19 Example ..................................................................................................................................................................19 No availability check ................................................................................................................................................19 Dependencies .........................................................................................................................................................19 Availability check with cumulative, confirmed quantities quantities .......................... .................................................. ......................... ......................... .............20 Example ..................................................................................................................................................................20 Recommendation ....................................................................................................................................................21 Use..........................................................................................................................................................................21 Availability with cum. quantities: quantities: Response to shortfall ................................................. ........................ ......................... ..........................................21 ......................... .................21 Use..........................................................................................................................................................................21 Dependencies .........................................................................................................................................................22 Indicator for relevance relevance during check against against planning .......................................... ................................................... ......................... .......................... 22

Availability Check and Transfer Requirements .......................................................................................................23 Material Block For Other Users: ..............................................................................................................................23 Define Material Block For Other Users.....................................................................................................................23 Definition: material master record ..........................................................................................................................23 Initiator Initiator of the availability check......................... .................................................. ......................... ......................... ................................................... ......................... .......................... 25 Use..........................................................................................................................................................................25 Block indicator indicator for availability and requirements requirements ......................... ................................................... ......................... .......................... .........................25 ........................ .25 Procedure ...............................................................................................................................................................25

Availability Check and Transfer Requirements .......................................................................................................25 Checking Group for Default Value: .........................................................................................................................25 Define Checking Groups Default Value ....................................................................................................................26

Availability Check and Transfer Requirements .......................................................................................................27 Carry out Control for Availability Check: .................................................................................................................27 Carry Out Control Control For Availability Availability Check .......................... .................................................. ......................... ......................... ......................... .............28 Checking Group for Availability Check .....................................................................................................................30 Use 1: Availability Availability Checking and Materials Materials Planning..................................... Planning..................................... ........................... ......................... ........30 Use 2: Flexible Planning ...........................................................................................................................................30 Checking Rule for Availability Check ........................................................................................................................30 2

January 13, 2016


Use 1: Availability Checking .....................................................................................................................................31 Use 2: Flexible Planning ...........................................................................................................................................31

Availability Check and Transfer Requirements .......................................................................................................32 Procedure by Requirement Class: ...........................................................................................................................32 Define Procedure By Requirements Class ...............................................................................................................33 Requirements class .................................................................................................................................................34 SD availability check ................................................................................................................................................34 Transfer of requireme requirements nts / Begin assembly order from SD........................ SD................................................. ......................... ......................................34 ......................... .............34 Example ..................................................................................................................................................................35 Allocation Indicator .................................................................................................................................................35 Product allocation active .........................................................................................................................................35 ICON Availability Check ...........................................................................................................................................36

Availability Check and Transfer Requirements .......................................................................................................36 Procedure For Each Schedule Line Category: ..........................................................................................................36 Define Procedure Procedure For Each Schedule Line Category Category .......................................... ................................................... ........................ ........................... ....37 Schedule line category ............................................................................................................................................38 Use..........................................................................................................................................................................38 Availability check for sales .......................................................................................................................................38 Example ..................................................................................................................................................................38 Transfer of requireme requirements nts / Begin assembly order from from SD............................................. SD................... .......................... ..........................................38 ......................... .................38 Example ..................................................................................................................................................................39 Product allocation active .........................................................................................................................................39

Availability Check and Transfer Requirements .......................................................................................................39 Procedure For Each Delivery Item Category: ...........................................................................................................39 Determine Procedure Procedure For Each Delivery Delivery Item Category Category ........................................ ............... .................................................. ......................... .......................... 40 Delivery item category ............................................................................................................................................40 Use..........................................................................................................................................................................40 Example ..................................................................................................................................................................40 Procedure ...............................................................................................................................................................40 Switch off off availability check for for delivery item ........................... ................................................. ........................ ......................... .......................... ....41

Availability Check and Transfer Requirements .......................................................................................................41 Checking Rule for Updating Back Orders: ...............................................................................................................41 3

January 13, 2016


Checking Rule For Updating Backorders ..................................................................................................................41

Availability Check and Transfer Requirements .......................................................................................................43 Default Settings: .....................................................................................................................................................43 Define Default Settings ............................................................................................................................................43

Availability Check and Transfer Requirements .......................................................................................................44 Define Business Transaction: ..................................................................................................................................44 Define business transaction .....................................................................................................................................45 ATP: Business Transaction Transaction for ATP ATP .......................... .......................... ................................................. ........................ ......................... ......................45 Use..........................................................................................................................................................................46

Availability Check and Transfer Requirements .......................................................................................................46 Assign Business Transaction to Sales Order Type: ..................................................................................................46 Assign business transaction transaction to sales sales order type ........................... ......................... .......................... ......................... 46 Sales document block ..............................................................................................................................................47 Use..........................................................................................................................................................................47 Procedure ...............................................................................................................................................................47

Process Order / Operations / Availability Check / Checking Group ........................................................................48 Checking Group: .....................................................................................................................................................48 Define Checking Group ...........................................................................................................................................48 Process Order / Operations / Availability Check / Checking Rule ...........................................................................49 Checking Rule: ........................................................................................................................................................49 Define Checking Rule ..............................................................................................................................................50 Process Order / Operations / Availability Check / Scope of Check ..........................................................................51 Scope of Check: .......................................................................................................................................................51 Define Scope of Check ............................................................................................................................................52 Process Order / Operations / Availability Check / Checking Control .......................................................................52 Checking Control:....................................................................................................................................................52 Business function (for availability check) .................................................................................................................53

Process Order / Operations / Availability Check / Checking Rule for Back Order Processing .......................... ........53 Checking Rule for Backorder Processing: ................................................................................................................53 Define Checking Checking Rule for Backorder Processing Processing ................................................ ................................................... ......................... .......................... ....54

gATP Configuration Settings in APO:.......................................................................................................................56 Global Available to Promise (Global ATP) ...............................................................................................................56 4

January 13, 2016


Maintain Global Setting for Availability Check: ......................................................................................................56 Maintain Global Settings for Availability Check ........................................................................................................56 Import Customizing .................................................................................................................................................57 Use..........................................................................................................................................................................57

ATP: Accept Schedule Lines According to Time .......................................................................................................57 Use .........................................................................................................................................................................57 Dependencies .........................................................................................................................................................57 Example ..................................................................................................................................................................57 Should Pegging Information be transferred to SAP R/3? ..........................................................................................58 Lifetime of Cross-System Correction Requirements .............................................. ...................................................58 Bucket Limit for Issue Elements ...............................................................................................................................58

...............................................................................................................................................................................58 Use..........................................................................................................................................................................58 Dependencies .........................................................................................................................................................59 Shift Receipt Bucket ................................................................................................................................................59

...............................................................................................................................................................................59 Use..........................................................................................................................................................................59 Note ........................................................................................................................................................................59 Dependencies .........................................................................................................................................................59 Example ..................................................................................................................................................................59 Local Time Zones .....................................................................................................................................................59

5

January 13, 2016


...............................................................................................................................................................................59 Use..........................................................................................................................................................................59 Dependencies .........................................................................................................................................................59 Example ..................................................................................................................................................................60 Number of Buckets Per Day .....................................................................................................................................60

...............................................................................................................................................................................60 Use..........................................................................................................................................................................60 Dependencies .........................................................................................................................................................60 Example ..................................................................................................................................................................60 Distribution Key Active in Time Series......................................................................................................................60

...............................................................................................................................................................................60 Use..........................................................................................................................................................................60 Dependencies .........................................................................................................................................................61 Value Assignment of Bucket Limits in Product Availability .................................... ...................................................61 Use..........................................................................................................................................................................61 Dependencies .........................................................................................................................................................61 See also ...................................................................................................................................................................61

Global Available to Promise (Global ATP) ...............................................................................................................62 6

January 13, 2016


Rule Based Availability Check: ................................................................................................................................62 Define Condition Table ............................................................................................................................................62 Name of the condition field .....................................................................................................................................63 Use..........................................................................................................................................................................63 Example ..................................................................................................................................................................63 Condition Table .......................................................................................................................................................64 Definition ................................................................................................................................................................64 Use..........................................................................................................................................................................64 Procedure ...............................................................................................................................................................64

Global Available to Promise (Global ATP) ...............................................................................................................65 Maintain Access Sequences: ...................................................................................................................................65 Maintain Access Sequences .....................................................................................................................................65

Global Available to Promise (Global ATP) ...............................................................................................................67 Maintain Condition Type: .......................................................................................................................................67 Maintain Condition Type .........................................................................................................................................68

Global Available to Promise (Global ATP) ...............................................................................................................68 Maintain Rule Strategy: ..........................................................................................................................................68 Maintain Rule Strategy ............................................................................................................................................69 Rule Strategy Defines Number of Substitutions .......................................................................................................69 Use..........................................................................................................................................................................69

Global Available to Promise (Global ATP) ...............................................................................................................70 Maintain Rule Strategy: ..........................................................................................................................................70 Assign Rule Strategy or Rule Strategy Sequence ......................................................................................................70 Definition: technical scenario ..................................................................................................................................70 Definition: business transaction...............................................................................................................................71 Definition: action type .............................................................................................................................................71 Rules-based ATP: Calculation Profile........................................................................................................................72 Definition ................................................................................................................................................................72 Note ........................................................................................................................................................................72 Dependencies .........................................................................................................................................................72 Preselection of Suitable Substitutions......................................................................................................................72 Use..........................................................................................................................................................................72 7

January 13, 2016


Dependencies .........................................................................................................................................................72

Global Available to Promise (Global ATP) ...............................................................................................................73 Back Order Processing: ...........................................................................................................................................73 Maintain Filter Type ................................................................................................................................................73

Global Available to Promise (Global ATP) ...............................................................................................................75 Back Order Processing: ...........................................................................................................................................75 Define Sort Profile ...................................................................................................................................................75

Global Available to Promise (Global ATP) ...............................................................................................................76 Back Order Processing: ...........................................................................................................................................76 Parallelizing Backorder Processing...........................................................................................................................77

Global Available to Promise (Global ATP) Questionnaire: ......................................................................................81

8

January 13, 2016


Important Points: 1. During implementation, ECC ATP configuration needs to be transferred once through CIF and in APO gATP global setting configuration setting, “Import Customization” allowed indicator needs to be activated. After implementation, both CIF and APO gATP global setting configuration setting, “Import Customization” needs to be de activated. Manually, APO configuration

needs to be updated for any changes in ECC ATP configuration. 2.

Minimum bucket period for gATP is 1 d ay.

3.

Temporary quantity assignment (TQA) indicator if you want to make it possible fo r several users to check the same planning

object simultaneously and nevertheless obtain consistent results from the availability check (It should be available in gATP global setting configuration (Table - /SAPAPO/ATP00)). 4.

Terminology APO Vs ECC: a.

Business Event – Checking Rule (A,BO, PP, Etc.)

b.

Check Mode – Requirement Class (030, 010, etc.)

c.

ATP Group - Availability Check (01, 02, etc)

5.

Transaction code for CIF in ECC is CFC9

6.

Check instruction is updated with combination of check mode and business event. Check instruction control is for the sequences to check Product availability check, product allocation check and f orecast check. Activate RBA indicator is a lso an important parameters.

7.

Production type and rounding procedure is the important parameters of check mode. Assignment mode field does not have impact in gATP.

8.

In case of in-house production, ATP horizon is the total replenish lead time, and for external procured material ATP Horizon = Planed Delivery Time + GR Processing Time + PR creation date for p lant from ECC configuration

9.

Planning horizon calendar needs to be created manually in APO.

10. ATP categories represents the MRP element (Like, PO, PR, SO, etc.) 11. Allocation procedure can be transferred from ECC material master (Basic Data Views) at gl obal level. 12. Product allocation group is grouping of catalogs (Characteristics) for condition record (access sequences) 13. Allocation procedure needs to be assigned manually in APO at location level. 14. KONOB is field catalog for pr oduct allocation object 15. Wild card is used to determine the product allocation of no n-specified CVC 16. Product allocations are saved per object for a characteristics combination in the product allocation group. Production allocation object is the key field for product allocation record 17. Rule based ATP check is used for: a.

Product Substitution

b.

Location Substitution

c.

PPM (PV) Substitution

18. Business event (Availability Check) and Check Mode (Requirement Class) can be maintained in location su bstituted activity. 19. Business transaction creation and assignment with SO document type in ECC is required for Rule Based ATP. 20. Characteristics data type should be matched with ECC data element. E.g. customer number should be maintained with leading zeros same as ECC. 21. Calculation profile is used to control early / delay delivery and is assigned with rule 22. Manufacturing location and distribution center location are added in filter of BOP 23. Design steps for BOP: a.

Design filter

b.

Design sort profile

c.

Define variant with filter and sort profile

d.

Define variant for BO processing job

9

January 13, 2016


24. Sales order scheduling considers below d ates: a.

Delivery date

b.

Goods issue date

c.

Loading date

d.

Material availability date

e.

Transportation planning date

25. Sales order scheduling considers below times: a.

Transportation time

b.

Goods issue time

c.

Loading time

d.

Material staging (Pick & Pack) time

e.

Transportation planning time

26. Shipping calendar should be assigned with location 27. Planning calendar is created in APO by assaying ECC f actory calendar 28. Scheduling procedure is standard and new scheduling procedure can’t be created. Only, we need to assign condition table to access sequences to scheduling p rocedure.

10

January 13, 2016


Global Available To Promise (GATP) Overview Introduction: Global Available To Promise (GATP) in APO supports online searches to determine if requested products are available at specific times in quantities that satisfy customer demand. GATP processes are run via S AP live Cache, which processes large volumes of d ata and enables data sharing across several applications. GATP meets the challenge of providing availability information across a global enterprise. The concept of available to promise (ATP) used in Sales and Distribution (SD) module in SAP R/3 provides check capabilities that deliver results for basic business scenarios. More complex scenarios, however, require more robust capabilities to make delivery commitments that are in line with the real-world demands. In short, global scenarios require global solutions. Global ATP — or GATP — takes advantage of SAP APO technology and picks up where the SAP R/3 ATP solution leaves off. Following are the functionalities using GATP allows you to answer questions related to promising products to your customers. GATP quickly makes information available to provide real-time optimized decision support. It offers the functionality to perform availability checks which consist of online searches that determine if requested products are available at requested times in the quantities that satisfy customer demand. GATP can be used for Sales Order, Scheduling Agreement, Delivery, stock transfer orders and production orders (for their input components).

GATP Methods can be classified into three areas: 1.

Basic methods and their combination (product check, product allocation, and ch eck against forecast)

2. 3.

Rules-based ATP (RBA) ATP integrated with production

4.

You can combine several GATP methods to provide more advanced capabilities.

Product Check A basic product availability check generates positive results if the so-called ATP quantity for a product is available on the requested delivery date. If it is not available, a new delayed delivery date is pro posed. The ATP quantity referenced during the product availability check is based on categories defined in Scope of Check.

Product Allocation Check (PAL) The second basic method is product allocation (PAL). Using information in the DP module, PAL lets you know your availability to promise when sales orders compete for quantities in a constrained supply chain. New products, production downtimes, and other factors lead to fluctuating demands, which can affect product supply. For these situations, PAL provides a tool to ensure a better distribution of the total amount when a company cannot deliver the full available quantity to a customer. Check against Forecast The last method on the list is a check against forecast. It provides a check method that is especially important in make-to-order environments, where inventory is not available to confirm the quantity ordered by the customers. In this case, the quantity confirmation is performed against the forecast. Like PAL, this fu nctionality is integrated with the DP module.

Rules-Based ATP An ordinary ATP check is restricted to the requested location product and checks only the according time series. Using rules-based ATP it is possible to substitute both the location and the product. In branched supply chain networks, rules-based ATP allows companies to take full advantage of multiple shipping assets to ship goods f rom alternative sites to customers. In addition, it permits certain products to be substituted as req uired to successfully satisfy customer demands. RBA is benef icial for Distributors, consumer product goods Industries

11

January 13, 2016


Capable-to-Promise (CTP) CTP technology taps into SAP APO Production Planning and Detailed Scheduling (PP/DS) functionality. CTP triggers an online check when a sales order is created. If the supply cannot cover the new demand, the PP/DS functionality is called on as a part of the ATP check. Product Master- PP/DS Tab - PP Plng Procedure determines the action in CTP. Example - Cover Dependent Requirements Immediately option is selected, a product heuristic for a specific product is called immediately when a sales order is created or ch anged. In general, the PP planning procedure determines the actions to be executed after a planning event like - sales order creation, goods movement, planned order change, etc. CTP is beneficial for Steel manufacturers, paper, chemical Industries. Please refer SAP Note#426563 for additional information. Multilevel ATP The basic idea of the multi-level ATP is to confirm a customer request if the components for the product are available in time (i.e. taking the lead-time to produce the finished product into account). Basically, multilevel ATP explodes a bill of material (BOM) for the assembled product, then checks the availability of each item at the component level. A multilevel ATP check determines the availability of each component required by the finished good. A big differ ence between this check and CTP is data is stored in the ATP tree. It's a new object that prevents the creation of the receipt elements generated by CTP. It is especially helpful for business scenarios that require products to be configured for individual customers (assemble-to-order scenarios). If component availability is the critical factor for your planning, multilevel ATP is the best option. Because CTP focuses on detailed scheduling strategies, it is the best choice when bottlenecks are the critical factor. SAP note 480292, Multilevel ATP documentation also provides helpful info rmation about the functionality.

CTP and ML-ATP In a make-to-order environment there are no receipts per definition. The idea of an ATP check is therefore not to check whether there are receipts for the requested product but whether there is enough available capacity to produce the product and/or whether the required components are available. This can also be done using third option - ATP check against allocations, where the allocations represent an aggregated capacity. Transportation and Shipment scheduling The transportation and shipment scheduling is an integral part of the availability check in APO, and calculates the time difference between the requested delivery date at the customer site and the required material availability date at the factory. In between the requested delivery date and the material availability date the goods issue date, the loading date and the transportation planning date are scheduled. The scheduling starts from the requested delivery date and time. The requested delivery date is meant as the date when the material has to arrive at the customer site. This is the date which is entered in the sales order.

Backorder Processing The basic idea of backorder processing is to carry out a new ATP check for a set of or der items. This way backorder processing can also be used to distribute quantities in case of shortage (resp. lateness) according to priorities. Backorder processing is usually performed in the background, but interactive backorder processing is also possible. Basically, BOP consists of three steps: Filter the treated elements, sort those sales do cuments, and schedule them.

12

January 13, 2016


Integration Calling the ATP check from SAP APO Function · Capable-to-Promise (CTP) · Multilevel ATP check

Required Component Production and Detailed Scheduling (PP/DS)

ATP Check in the Order Backorder processing in Vehicle Scheduling

Transportation Planning/Vehicle Scheduling (TP/VS)

Calling the ATP check from SAP R/3 Component Sales and Distribution Processing (SD-SLS)

Planned Order Processing (PP-MRP)

Further Information Availability Check and Requirements

Availability Check According to ATP Logic Availability Check for the Components in the Planned Order

Production Order Processing (PP-SFC) Purchasing (MM-PUR) Demand Management (PP-MP-DEM) Inventory Management (MM-IM)

Availability Check for Materials Purchasing (MM-PUR) Availability Check Availability Check Material Availability Check

Batch Management (LO-BM)

Batches in Sales Processing

Calling the ATP check from other components using the BAPI Apo Atp Check (execution of an ATP check); business object BUS10400

Component SAP Customer Relationship Management (SAP CRM)

Further Information Availability Check

13

January 13, 2016


gATP Configuration Settings in ECC:

Availability Check and Transfer Requirements Checking Groups: SPRO -> Sales and Distribution -> Basic Functions -> Availability Check and Transfer Requirements -> Availability Check -> Availability Check with ATP Logic o r Against Planning -> Define Checking groups

Define Checking Groups In this IMG section you define checking groups with which you specify the type of requirements records the system is to create when processing sales orders or d eliveries. Sales order requirements and delivery requirements can be controlled separately. You can create the fo llowing requirements records: 



Individual requirements records In individual requirements records, a requirement is created for each SD document. The respective entry in the stock/ requirements overview identifies the order quantity and the document which gave rise to the req uirement. Summarized requirements r ecords Summarized requirements records group together or update several requirements under certain conditions in the material master record (plant, date, pro cedure, requirement class). There are two types of summarized requirements records: o Summarized requirements records for each day o Summarized requirements records for each week Monday of the current week or Monday of the following week is regarded as a requirement date.

14

January 13, 2016


Availability check taking c umulated confirmed quantity into account If confirmed quantities are not cumulated, the following problem may occur: Starting from the delivery date of the sales order and working backwards, the system checks whether ATP quantities exist. If such quantities do exist, the new sales order will reduce these ATP quantities. Here, sales orders can only reduce the ATP q uantities if they lie before the delivery date. In this logic, the system does n ot take the confirmed quantity of sales orders that have already been created into account. If, in the past, receipts were either moved forward or backward and/or they were reduced, it is possible that the ATP quantity of the receipt that lies directly before a sales ord er which has already been confirmed is no longer sufficient to cover the requirement. The following example should clarify this point:

MRP elemt

Recpt/Reqmt ATP qty Cumul. ATPqty Confirmed qty

Stock

100

0

0

-

SALES ORD 1 -200

-100

-100

-200

PLND ORD

0

0

-

0

0

100

100

SALES ORD 2 -100

In this example, the first sales order was completely confirmed when the p lanned order lay before sales order 1 on the time axis. Then, the planned order was rescheduled out so that it no w lies after the delivery date of sales order 1 on th e time axis. For the new sales order 2, the ATP check comes up with an ATP quantity of 100 as the rescheduled planned order is now completely available again and according to the ATP logic, sales order 1 cannot be covered by this receipt. In this particular example, the confirmation situation is no longer up-to-date as the planned o rder has been rescheduled. Therefore, the sum of all the confirmed quantities exceeds the sum of all receipts. To solve this problem, you have the following options:  carry out the planning run reschedule   carry out backorder processing With the cumulation of quantities, you can avoid such inconsistencies asyou can control exactly how the system is to carry out the check:  Availability check taking cumulated confirmed quantity into account When creating/changing a new sales order, the system includes all the quantities confirmed to date when calculating the cumul ated ATP quantity. This means that the new sales orders can only be con firmed if the sum of the receipts exceeds the sum of the confirmed quantities.  Availability check taking cumulated requirements quantities into account When creating/changing a new sales order, the system includes the sum of all open requirements quantities when calculating the cumulated ATP quantity. This means that new sales orders can only be confirmed if the sum of the receipts exceeds the sum of the requirements quantities. You can make the following settings for this new AT P checking logic when creating/changing a sales order: cumulate the confirmed quantities when creating and changing   cumulate the requirements quantity when creating, no cumulation when only making changes  cumulate the requirements quantity when creating and cumulate the confirmed quantity when making changes  no cumulation (old ch ecking logic)

15

January 13, 2016


Determining the checking group The checking group is determined depending on the material type and plant and is proposed in the material master record. The section "Define the checking group for each material type" describes how to allocate checking group to material type and plant. Together with the checking rule, the checking group determines the scope of the availability check. Note For procedures relevant to requirements which lead to special stock (e.g. make-to-order production), the system automatically creates individual requirements records, even if the configuration was set in the material master record or via the checking group for summarized requirements records. Warning You can use either su mmarized requirements or individual requirements for each checking group. Changing the method of su mming up requirements results in a change in the information contained in the record. Wh en you change from individual to summarized requirements, you lose the assignment to sales orders, for example. Actions 1. Check to what extent you can use the configurations set for the checking groups in the standard version of the SAP System. 2. Enter the method of summing up for each checking group when creating a sales order document or a delivery. 3. If necessary, activate the cumulation of confirmed quantities.

16

January 13, 2016


Checking Group for Availability Check This field has two uses:

1.

Specifies whether and how the system checks availability and gener ates requirements for materials planning.

Definition: materials planning Material Requirements Planning (PP-MRP) A generic term for the activities involved in creating a master production schedule or an external procurement plan for all the materials in a plant or company. Materials planning is also referred to as material requirements planning. Return-> Definition: Materials planning 2.

In Flexible Planning, defines - together with the checking rule - the different MRP elements that make up this key figure. The sum of these elements gives the key figure.

Definition: Sales & Operations Planning Sales and Operations Planning (PP-SOP) A forecasting and planning tool for setting targets for sales, production, and other supply chains based on historical, current, or estimated data. Resource planning can be performed to determine work center capacities and other resources required to meet targets. SOP supports high-level planning of complex planning hierarchies and detailed planning of finished products. A top -down or a bottomup approach to planning is possible. The system can be configured so that target values set at one or ganizational level are distributed (aggregated and disaggregated) automatically to all other organizational levels in the hierarchy, for example, to all distribution channels, materials, and plants in a s ales organization, or so that each level is planned separately. Sales & Operations Planning includes: standard SOP and flexible planning. Standard SOP comes preconfigured with the system. F lexible planning offers options for customized configuration. Planning in standard SOP is based on p roduct group hierarchies and is performed level by level. Flexible planning is performed on hierarchies containing chosen organizational levels, for example, sales org anization, distribution channel, material, and plant. In f lexible planning, users can define the content and layout of p lanning screens. The component can run in a d istributed environment using Application Link Enabling (ALE). Return-> Definition: Sales_&_Operations Planning

Use 1: Availability Checking and Materials Planning Use The value you enter for use 1 (see above) is a def ault value which defines:  Which MRP elements (for example, purchase orders, reservations) the system includes in the availability check  Whether the system checks availability only until the end of the replenishment lead time or whether it checks availability over the entire period for which MRP elements exist  Whether the system generates individual requirements or summarized requirements if you enter sales order s or deliveries for the material

17

January 13, 2016


Definition: replenishment lead time Material Requirements Planning (PP-MRP) The total time for the in-house production or for the external procurement of a product. In in-house production, the replenishment lead time is determined to co ver all BOM levels. SCM-Supply Chain Planning and C ontrol (SRD-SCM-SCP) The amount of time between deciding to reorder a product and when it is back in stock and ready to use. Return -> Definition: Replenishment_lead_time

Use 2: Flexible Planning Dependencies If you use this field to define the MRP elements of a key figure for Flexible Planning, you must also select Document KF in the Customizing parameters of the information structure.

Total sales order requirements Specifies the kind of requirements that the system automatically generates during sales order processing.

Use You can specify either Individual requirements Summarized requirements If you specify summarized requirements, you can further specify whether the requirements are totaled daily or weekly. Definition: summarized requirements Sales and Distribution (SD)  

Material requirements in a plant that have been summarized over a specified period and transferred as a total to materials pl anning (MRP). The system creates a line in the requirements/stock overview for each total of summarized requirements. This can be, for example, the total requirements for one day or one week. The system summarizes according to the following criteria:  Plant  Date  Transaction  Requirement type and planning type Return-> Definition: Summarized requirements Total delivery requirements Specifies the kind of requirements that the system automatically generates during delivery processing.

18

January 13, 2016


Use You can specify either Individual requirements Summarized requirements If you specify summarized requirements, you can further specify whether the requirements are totalled daily or weekly.  

Material block in availability ch eck with transfer of qties Block on the material which is only in place during the availability check.

Procedure Set this block if you want several users to be able to process the material simultaneously in different transactions without blocking each other. Example You create an order for Material 1. As specified in the settings, material 1 is blocked during the availability check. The quantity reserved for this transaction is recorded in the blocking table. Any other user processing the material at that time receives this information. This complements the information gained from the availability check and gives a more accurate picture of the current availability situation. After the availability check has been completed, the block is r emoved.

No availability check This indicator switches off the availability check according to ATP logic for the checking group concerned.

Dependencies If this indicator is selected, the settings for the indicator, "Availability check with cumulated, committed quantities" and "Availability with cumulated quantities: reaction to missing quantity" are not relevant for this ch ecking group.

19

January 13, 2016


Availability check with c umulative, confirmed quantities The following problem may occur if committed quantities are not cumulated:

Starting from the delivery date of the sales order and looking in the past, the system checks to see whether ATP quantities exis t. If it actually finds an ATP quantity, it is redu ced by the new sales order. Sales orders can on ly reduce ATP quantities whose date lies before the delivery date.

In this logic, the system does not take the committed quantity of already created sales orders into account. If receipts are displaced and/or reduced in the past, it is possible that the ATP q uantity of the receipt that lies before a sales order is now too small to cover this sales order quantity although it has already been completely confirmed. Example The following example should exp lain this situation:

Situation 1 MRPelemt Recpt/Reqmt

ATP qty Cum. ATP qty

Stock

100 0

0

PlOrd

100 0

-100

SalesOrd

-200 -

Committed qty

-

-

-200

Situation 2 MRPelemt Recpt/Reqmt

ATP qty Cum.ATP qty Committed qty

Stock

100

SalesO1

0

0

-

-200 -100

-100

-200

PlOrd

100

0

0

-

SalesO2

-100 -

-

100

20

January 13, 2016


In situation 1, the first sales order is completely confirmed when the planned order lay before sales order 1 on the time axis. In situation 2, the planned order has been moved on the time axis so that it now lies after the delivery date of t he sales order 1. For the n ew sales order 2, an ATP quantity of 100 exists as the moved planned order is n ow completely available again as according to ATP logic it can no longer be used to cover sales order 1. In this example, a inconsistency occurs with the confirmations as the planned order has been moved - the sum of the confirmed quantities exceeds the sum of all receipts. To correct this inconsistency, you have the fo llowing options: carry out the planning run   carry out rescheduling  backorder processing Availability checking taking cumulated confirmed quantities into account The function, "checking taking cumulated confirmed quantities into account" should avoid such inconsistencies as you can set how the check is to be carried out when creating or changing sales orders:  Check taking cumulated confirmed quantities into account In the availability check in the sales order, the system takes the su m of all previously confirmed quantities into account when calculating the cumulated ATP quantity. This means that new sales orders can only be confirmed if the sum of all receipts exceeds the sum of the confirmed quantities. 

Check taking cumulated requirements quantities into account In the availability check in the sales order, the system takes the sum of all open requirements quantities to date into account when calculating the cumulated ATP quantity. This means that new sales orders can only be confirmed if the sum of all receipts exceeds the sum of all requ irements quantities.

With these new ATP checking procedures, you have the following setting options when creating /changing a sales order: Cumulation of the confirmed quantities when creating and changing.   Cumulation of the requirement quantity when creating, no cumulation when changing.  Cumulation of the requirement quatity when creating, cumulation of the confirmed quantity when changing.  No cumulation (old checking logic). Recommendation You are recommended to work with the cumulation of the r equirement quantities when creating sales orders. You are recommended to work with the cumulation of the confirmed quantities when changing sales orders. Use The setting that you make here is valid in  Sales order processing  Production order processing for order reservations Availability with cum. quantities: Response to shortfall This indicator controls whether an output is issued when there is a material shortage.

Use The following entries are po ssible: Even when there is a shortage, no output is issued. When there is a shortage, output is issued with the information that the total of inward goods movement is less than the confirmed/required quantity.  

21

January 13, 2016


Dependencies This indicator for controlling issue of output can only be used if you are processing using cumulation of confirmed quantities or of required quantities. Indicator for relevance during check against planning The indicator specifies in which cases the availability of a material must be checked against planning (planned independent requirements) within the framework of a component availability check.

The possible settings are:

  

Do not check, the component is not checked against planning. Always check, the component is always checked against planning. Check, only if du mmy, the component is only checked against planning if it is a dummy component.

22

January 13, 2016


Availability Check and Transfer Requirements Material Block For Other Users: SPRO -> Sales and Distribution -> Basic Functions -> Availability Check and Transfer Requirements -> Availability Check -> Availability Check with ATP Logic o r Against Planning -> Define Material Block for O ther Users

Define Material Block For Other Users In this IMG activity you define for each checking group and initiator whether the material master record should be blocked for other orders during the availability check. If it is blocked, you cannot create two orders for the same material at the same time. Using the Initiator field you can define the block separately for sales and shipping. Example A block may, for example, be necessary if the material stock is low. In theory, if the material were not blocked during the availability check, two orders could be confirmed with the result that the quantity available is not sufficient for both orders. Note You cannot yet change the values for the field "Initiator of the availability check" (sales ord er, delivery note) in the configuration menu. Actions If appropriate, set a block for the combinations of checking group and initiator. Specifiy whether this is relevant for Sales or Shipping.

Definition: material master record Logistics - General (LO)

A data record containing all the basic information required to manage a material. This data is sorted according to various criteria including data of a descriptive nature (such as size, dimension and weight) and data with a control function (such as material type and industry sector). In addition to this data, which can be directly maintained by the user, it also contains data that is automatically updated by the system (such as sto ck levels).

23

January 13, 2016


Return-> Definition: material_master_record

24

January 13, 2016


Initiator of the availability check Specifies which kind of processing (sales, delivery, or materials reservation) initiates the availability check. Use The initiator lets you, for example, apply one kind of availability check during delivery processing and another during sales order processing.

Block indicator for availability and requirements Indicates whether, during the availability check, the material is blocked for other users. The block remains until the transaction responsible has been saved. It is set at material-plant level. Procedure If you select this field, the material is blocked during the availability check and other users cannot: Make changes in the material master record Create purchase orders for the material Create orders for the material If you do not select this field, the material is not blocked during the availability check. In this case, if many users are simultaneously checking availability, the results of the checks may not be reliable.   

Availability Check and Transfer Requirements Checking Group for Default Value: SPRO -> Sales and Distribution -> Basic Functions -> Availability Check and Transfer Requirements -> Availability Check -> Availability Check with ATP Logic o r Against Planning -> Define Checking Group For Default Value

25

January 13, 2016


Define Checking Groups Default Value In this IMG activity, you define the checking group that the system proposes when you create a new material master record. Yo u can overwrite the default value for the checking group in the material master record. The default value depends on the material type and plant. The SAP R/3 System copies this value to the SD documents, thereby proposing a certain extent of the availability check. Requirements You have defined your material types and plants. Actions 1. Make sure that the system proposes the checking groups you require for the availability check in the material master (under sales: general/plant data). 2. Check which checking groups are to be valid for which material types in the different Plants 3. Assign a default checking group to the material types in the individual plants. You can en ter a default value for each material type. For a definition of checking groups, see the IMG activity Define checking groups. 4. Make sure that the availability check indicator is maintained in the material master.

26

January 13, 2016


Availability Check and Transfer Requirements Carry out Control for Availability Check: SPRO -> Sales and Distribution -> Basic Functions -> Availability Check and Transfer Requirements -> Availability Check -> Availability Check with ATP Logic o r Against Planning -> Carry out Contro l for Availability Check

27

January 13, 2016


Carry Out Control For Availability Check In this IMG step, you define checking rules for the availability check and allocate them to a checking group. The checking rule specifies the scope of the availability check for the respective transactions in sales and distribution by specifying precisely which stocks, receipt and issue elements should be taken into account during the availability check. Every checking rule is allocated to a checking group: together these two elements determine the final inspection requirements. In addition, the checking rule includes a specification whether or not an availability check should take into account the replenishment lead time. Currently, the checking rule is predefined in SD. When specifying the inspection scope for a certain checking rule, you can currently select the following receipts and issues: purchase orders production orders purchase requisitions planned orders dependent requirements reservations dependent reservations sales requirements delivery requirements SD requirements (= sales requirements and delivery requirements) reduce an available stock or inward stock movement on the material availability date so that other issues cannot access the reserved quantity. When specifying the inspection scope for a certain check rule, you can currently select the following stock elements: Safety stock (to be maintained in material master record, MRP data) Stock in transfer in the receiving plant Stock in quality inspection Blocked stock Replenishment lead time The replenishment lead time specifies the time which is n eeded to order or produce a certain material. The system determines the replenishment lead time as follows: For internally procured materials the replenishment lead time is determined from the in-house production time and the goods receipt processing time or alternatively from the total replenishment lead time, if it is specified. For externally procured materials the replenishment lead time is determined from the goods receipt processing time and the processing time for purchasing. In this IMG step, you control whether or not the replenishment lead time should always be taken into account. If you select the field, the replenishment lead time will NOT be taken into account during the availability check. If the field remains unselected, the replenishment lead time will automatically be included in the availability check. If you carry out the availability check using the replenishment lead time, you should plan ahead in regular intervals (on a daily basis for individual and daily requirements, on a weekly basis for weekly requirements) to prevent a shortage and therefore a p ossi ble delivery block. This shortage could occur if the delivery date of a sales order, which was confirmed the previous day for the replenishment lead time, is already within the replenishment period on the current day and therefore results in a sh ortage. Note For transactions which create individual stocks, such as production-to- order, consignment stock processing or returnable packaging processing, the availability check is carried out for the individual stock depending on the respective special stock indicator. Actions 1. Check the configurations for the checking groups which are contained in the standard SAP R/3 System.         

   





2. Make sure that the ch ecking group is maintained in the material master records. Depending on the plant, you can specify a checking group for each material type (see section "Specifying a checking group for each material type "). 3. Select the individual stock elements as well as the receipts and issues which should be taken into account during the availability check. 4. Select the field for replenishment lead time if you do NOT want to take the replenishment lead time into account. 5. If your release was updated after 2.0, you must check the indicators for sales and delivery requirements.

28

January 13, 2016


Before, these sales requirements had to be maintained in a joint field and were first subdivided into two separate fields for Release 2.1. In the release update, a selected or iginal field led to sales and delivery requirements being selected, an unselected field leads to unselected fields in the conversion program.

29

January 13, 2016


Checking Group for Availability Check This field has two uses: 1. Specifies whether and how the system checks availability and generates requirements for materials planning. 2. In Flexible Planning, defines - together with the checking rule - the different MRP elements that make up this key figure. The sum of these elements gives the key figure.

Use 1: Availability Checking and Materials Planning Use The value you enter for use 1 (see above) is a default value which defines:  Which MRP elements (for example, purchase orders, reservations) the system includes in the availability check  Whether the system checks availability only until the end of the replenishment lead time or whether it checks availability over the entire period for which MRP elements exist  Whether the system generates individual requirements or summarized requirements if you enter sales order s or deliveries for the material Use 2: Flexible Planning Dependencies If you use this field to define the MRP elements of a key figure for Flexible Planning, you must also select Document KF in the Customizing parameters of the information structure.

Checking Rule for Availability Check Use 1: 1. This rule defines the checking procedure to be used for the availability check (or in Inventory Management, the missing parts check) in individual applications.

30

January 13, 2016


Use 2: 2. It defines, together with the checking group, the different MRP elements that make up this key figure in Flexible Planning.

Use 1: Availability Checking Use Along with the checking group, the checking rule specifies the final procedure for checking. Note Note that you must define check ing rules for each individual application. Therefore, you define the checking rule f or reservations via the configuration menu for production orders, for example. On the other hand, in Sales and Distribution, the checking rule is specified internally within the system and cannot be changed. To check the availability of a material, you must enter a checking group in the material master record (in the field Availability check ). Examples You can use the checking rule and group to determine:  Which receipts (for example, purchase orders or production orders) should be taken into account in the availability check Which issues (for example, sales orders or dependent requirements) should be taken into account in the availability check  Use 2: Flexible Planning Dependencies If you use this key to define the MRP elements of this key figure for Flexible Planning, you must also select the indicator Document KF in the Customizing parameters of the information

31

January 13, 2016


Availability Check and Transfer Requirements Procedure by Requirement Class: SPRO -> Sales and Distribution -> Basic Functions -> Availability Check and Transfer Requirements -> Availability Check -> Availability Check with ATP Logic o r Against Planning -> Define Procedure by Requirement Class

32

January 13, 2016


Define Procedure By Requirements Class In this IMG activity you define for each requirements class whether an availability check and/or transfer or requirements should be carried out. The settings defined here correspond to the requirements class settings at a global level. T he se ttings are automatically copied into the definition of the requirements class and vice versa. Actions 1. Check the extent to wh ich you can copy the settings for the requirements class which are defined in the standard v ersion of the SAP R/3 System. 2. If necessary, change the standard settings by indicating for each requirements class whether an availability check and/or transfer or requirements should be carried out.

33

January 13, 2016


Requirements class Key which specifies the planning strategy internally within the sys tem. One or more requirements types can be allocated to the requirements class. Planning strategies and requirements are linked via the requirements type.

SD availability check You must carry out an availability check for the corresponding transaction. If the indicator is not set and if the assignment of independent requirements planning is active, then an availability check is carried out against planned requ irements for the material. If this assignment is not requ ired, no check takes place. The type of check is proposed by the system. Each check can be switched off (but not on) by transaction in both sales and shipping.

Transfer of requirements / Begin assembly order from SD Transfer of requirements is to be carried out for the respective transaction.

34

January 13, 2016


The selection of this indicator is the precondition for transfer of requirements. You can deactivate transfer of requirements at schedule line level. Conversely, it can simply be left inactive at schedule line level, as long as it is not already activated in the requirements class. Example You do not set an indicator for maintaining the requirements class: Transfer of requirements is not carried out, irrespective of the specification you make at schedule line level for the transaction. You set an indicator for maintaining the requirements class: In this case you can still decide at sched ule line level, whether or n ot you require transfer of requirements for the relevant transaction.

Allocation Indicator Controls the consumption of customer requirements with planned independent requirements whereby the customer requirements type is only allocated one consumption strategy.

Product allocation active Product allocation active

35

January 13, 2016


ICON Availability Check

Availability Check and Transfer Requirements Procedure For Each Schedule Line Category: SPRO -> Sales and Distribution -> Basic Functions -> Availability Check and Transfer Requirements -> Availability Check -> Availability Check with ATP Logic o r Against Planning -> Define Procedure for Each Schedule Line Category

36

January 13, 2016


Define Procedure For Each Schedule Line Category c ategories of the sales documents whether an availability check and/or In this IMG step, you specify for the respective schedule line categories transfer of requirements should be carried out. These configurations configurations are only relevant for the sales documents. The fine tuning of the availability check for sales documents that you carry out here depends on their global configuration at requirements class level: You can only deactivate an option selected at requirements class level, but you cannot activate it. You can only activate an an option if it is already activated at requirements class level. Example You want to implement an availability availability check without transfer of requirements for sales information. At requirements class lev el, the availability check and the transfer of requirements must be active. You therefore deactivate the transfer of requirements in the corresponding schedule line category. Requirements The schedule line categories must already have been defined (see section Defining and allocating schedule line categories). The defined schedule line categories are automatically automatically displayed for maintaining. maintaining. Actions 1. Specify for each schedule line category whether an availability availability check and/or and/or a transfer of requirements should be carried out. Keep in mind that the configuration that you set depends on the global configurations at requirements class level.

37

January 13, 2016


Schedule line category A classification that distinguishes between different kinds of schedule line. The category determines how the system processes the schedule line. Use The schedule line category determines, for example, whether the system passes on requirements to materials requirements plann ing (MRP).

Availability check for sales You must carry out an availability availability check for the following transaction. The indicator is determined as a proposal in conjunction with the r espective requirements requirements type. It can b e changed in individu al shipping transactions. However, only one r estriction is effective. Example You do no t set an indicator indicator for maintaining maintaining the requirements type. In this case, no availability availability check is carried out. T his i s independent of the selection in the respective transaction. You set an indicator for maintaining the requirements type. In this case you can decide whether or not you require an availability check for the r elevant transaction. transaction.

Transfer of requirements / Begin assembly order from SD Transfer of requirements is to be carried out for the respective transaction. The selection of this indicator is the precondition for transfer of

38

January 13, 2016


Requirements. You can deactivate transfer transfer of requirements at schedule line level. Conversely, it can simply be left inactive at schedu le line level, as long as it is not already activated in the requirements class. Example You do not set an indicator for maintaining the requirements class: Transfer of requirements is not carried out, irrespective of the specification you make at schedule line level for the transaction. You set an indicator for maintaining maintaining the requirements class: In this case you can still decide at schedule line level, whethe r or not y ou require transfer of requirements for the relevant transaction.

Product allocation active Product allocation active

Availability Check and Transfer Requirements Requirements Procedure For Each Delivery Item Category: SPRO -> Sales and Distribution -> Basic Functions -> Availability Check and Transfer Requirements -> Availability Availability Check -> Availability Check with ATP Logic o r Against Planning -> Define Procedure for Each Delivery Line Item Category

39

January 13, 2016


Determine Procedure For Each Delivery Item Category In this step, you can switch off the availability availability check f or particular item categories categories in delive ries. The availability availability check sh ould be switched off for transactions such as returns delivery.

Delivery item category A classification classification that distinguishes between different types of delivery items (for example, return items and text items). Use The delivery item category determines how the system processes an item. Example If, for example, you identify an item as as a return item, you tell the system, in this case, that the item is not relevant for p icking. Procedure The system proposes a d elivery item category. category.

40

January 13, 2016


Switch off availability check for delivery item

Availability Check and Transfer Requirements Checking Rule for Updating Back Orders: SPRO -> Sales and Distribution -> Basic Functions -> Availability Check and Transfer Requirements -> Availability Check -> Availability Check with ATP Logic or Against Planning -> Checking Rule for Updating Back Orders

Checking Rule For Updating Backorders In this IMG step, you assign a checking rule to a plant. The checking rule specifies for the individual applications the checking rule according to which the availability check is carried out. The checking rule is described in the section "Carry out control of the availability check". Note The checking rule entered here is used in production planning. During backorder processing (CO06) and the availability overview (CO09), you should make sure that you are not using any checking rules that deviate from the SD configurations (c hecking rule A for orders and checking rule B for deliveries). Actions Specify a checking rule for each plant.

41

January 13, 2016


42

January 13, 2016


Availability Check and Transfer Requirements Default Settings: SPRO -> Sales and Distribution -> Basic Functions -> Availability Check and Transfer Requirements -> Availability Check -> Availability Check with ATP Logic o r Against Planning -> Define Default Settings

Define Default Settings In this menu option, you specify certain defaults for the availability check. For each sales area which is a combination of sales organization, distribution channel and division, you can set an indicator for fixing the date and quantity as well as a rule for transferring the results of the availability check. Fixed date and quantity In this field, you specify for a sales area whether the delivery dates and delivery quantities confirmed after an availability 

check should be set. 

Rule for transferring the availability results In this field, you can specify the system response to shortage for a sales area. The following responses are possible: o o

The system displays the different options (for example, one-time delivery, full delivery) for selection in a dialog box. The system automatically chooses an option (for example, confirmation of a delivery proposal).

Actions 1. Specify for each sales area whether you want to fix the date and the quantity. 2. Specify for each sales area whether a system response should be issued if the availability check shows a shortage, and if so which.

43

January 13, 2016


Availability Check and Transfer Requirements Define Business Transaction: SPRO -> Sales and Distribution -> Basic Functions -> Availability Check and Transfer Requirements -> Availability Check -> Rule Based Availability Check -> Define Business Transaction

44

January 13, 2016


Define business transaction In this step you can define the business transactions. These transactions must also be available in the APO planning system. Here the availability check control is c arried out for the transactions. You can find the b usiness transactions in the APO planning system (Field BPROC) under: Global ATP -> Settings -> Rule-based ATP -> Conditions -> Assign rule strategy .

ATP: Business Transaction for ATP This entry makes it possible to use the availability check settings in the APO planning system for this ord er type.

45

January 13, 2016


Use Using the business transaction, you can control in which business contexts a rule -based availability check is carried out. A rule-based availability check is therefore, as a rule, not sensible for a rush order. When called from the ERP system, this value is created u sing the order type for the sales order from which calling takes place.

Availability Check and Transfer Requirements Assign Business Transaction to Sales Order Type: SPRO -> Sales and Distribution -> Basic Functions -> Availability Check and Transfer Requirements -> Availability Check -> Rule Based Availability Check -> Assign Business Transaction to Sales Order Type

Assign business transaction to sales order type In this IMG activity, you assign the actions you defined previously to the order types. This activates the availability check settings for this order type that were maintained in the APO planning system.

46

January 13, 2016


Sales document block Determines whether the sales document is blocked for u se. Use If you block a sales document type, users cannot create new sales documents of this type. Sales documents created before you set the block can still be ch anged and displayed. Procedure If you want to block the sales document type, mark the f ield.

47

January 13, 2016


Process Order / Operations / Availability Check / Checking Group Checking Group: SPRO -> Production Planning for Process Industries -> Process Order -> Operations -> Availability Check -> Define Checking Group

Define Checking Group In this step, you define checking groups. You must allocate each material you want checked for availability to a checking group. You can allocate the material in the material master. The checking group group’s together materials checked according to the same criteria. Materials can be grouped accord ing to material type and/or MRP type, for example. You can also use the checking group to control whether the quantities confirmed in the availability check are to be locked During the check the normal ATP quantity or the cumulated ATP quantity is to be used. Notes You allocate the checking group to the material in the material master under the availability check field in the MRP data screen. If you have not maintained a checking group for a material, the material will not be checked f or availability. Activities Define the necessary checking rules.  

48

January 13, 2016


Process Order / Operations / Availability Check / Checking Rule Checking Rule: SPRO -> Production Planning for Process Industries -> Process Order -> Operations -> Availability Check -> Define Checking Rule

49

January 13, 2016


Define Checking Rule In this menu option, you can define checking rules from the point of view of the following applications: Sales MPR Process order processing Inventory management You can thus carry out various application-related checks for a material. Activities 1. For the company, define whether you need to ch eck on a differentiated basis for each application. 2. Define the checking rules.    

50

January 13, 2016


Process Order / Operations / Availability Check / Scope of Check Scope of Check: SPRO -> Production Planning for Process Industries -> Process Order -> Operations -> Availability Check -> Define Scope of Check

51

January 13, 2016


Define Scope of Check In this menu option, you define the check scope. Checking group and checking rule together specify the scope of the check. You can specify the following: which elements relevant to MRP (inward goods movements/outward goods movements) are taken into account (for example, purchase requisition, purchase order, p lanned order) which stock categories are taken into account whether replenishment lead time is checked Actions Specify which inward goods movements and which outward goods movements are to be included in the availability check which stocks are to be included in the availability check whether the check should take into account the replenishment lead time Whether the availability should always be checked at plant level. 

 

   

Process Order / Operations / Availability Check / Checking Control Checking Control: SPRO -> Production Planning for Process Industries -> Process Order -> Operations -> Availability Check -> Define Checking Control

52

January 13, 2016


Business function (for availability check) Key which identifies a business transaction, such as "Create order" or "Release order".

Process Order / Operations / Availability Check / Checking Rule for Back Order Processing Checking Rule for Backorder Processing: SPRO -> Production Planning for Process Industries -> Process Order -> Operations -> Availability Check -> Define Checking Rule For Backorder Processing

53

January 13, 2016


Define Checking Rule for Backorder Processing In this menu option, you can determine a checking rule p er plant for backorder handling. The checking rule determines the scope of check for backorder handling. Recommendation We recommend that you use the s ame checking rule for backorder handling as you do for availability checks. Actions Define the necessary checking rules.

54

January 13, 2016


55

January 13, 2016


gATP Configuration Settings in APO:

Global Available to Promise (Global ATP) Maintain Global Setting for Availability Check: SPRO -> Advanced Planning and Optimization -> General Settings -> Maintain Global Settings for Availability Check

Maintain Global Settings for Availability Check In this IMG activity, you maintain the global settings for the availability check. These include: Import Customizing data using the CIF integration model in the connected OLTP system: allowed/not allowed Define bucket parameters For more information, see the documentation for Global Available-to-Promise (Global ATP) under Define Buckets for ATP  

Time Series .

Note We recommend that you transfer Customizing data once only. If the Customizing data is transferred a second time, existing settings are liable to be overwritten. Requirements Make sure that the updating of ATP time series is activated. You set this indicator in Model and Planning Versio n Management from the SAP Easy Access screen by choosing Master Data -> Planning Version Management - > Model and Version Management .

56

January 13, 2016


Import Customizing The indicator specifies if the Cu stomizing data of the availability check is imported from a connected system.

Use If you set the indicator, the import of the Customizing data is prevented. If you do not set the ind icator, the Customizing d ata is imported. ATP: Accept Schedule Lines According to Time Confirmed schedule lines in the sales ord er of the connected OLTP system (SAP R/3) based on the time.

Use The indicator defines if the confirmed schedule lines of the sales orders in the connected OLTP system (SAP R/3) should be adopted based on the day or on the time. If the indicator is set, the sales ord er adopts the changes of the confirmed schedule lines or the confirmations for a time other than the desired delivery time, to the exact second. In the sales order a second schedule line is created for the same day, but created with a different time, or the times of the confirmed schedule lines can b e changed. If the indicator is not set, only one schedule line exists in the sales order if the desired delivery day can be kept, or only changes to the confirmed schedule lines are adopted that are at least one day different from the desired delivery date. Dependencies If confirmed schedule lines should be created based on the time, this can lead to several confirmed schedule lines for a request schedule line being created per day in the sales order, and in the item overview the impression is given that no confirmation could be made according to what was requested. In addition, the data volume of the SAP R/3 database tables VBEP and VBBE will increase significantly, since each schedule line is represented with a data record in these tables. The same effect will also occur for the APO liveCache and for the database table /SAPAPO/SCHEDLIN. Example 



Request:

Confirmation Situation:

100 pieces for 01.01.2002 12:00 50 pieces for 01.01.2002 14:00 30 pieces for 01.01.2002 16:00 20 pieces for 01.01.2002 18:00 If this indicator is NOT set, the request schedule line is confirmed and no further schedule lines are created: 100 pieces for 01.01.2002 12:00 If this indicator is set, the f ollowing (partially) confirmed schedule lines are created:

57

January 13, 2016


00 pieces for 01.01.2002 12:00 50 pieces for 01.01.2002 14:00 30 pieces for 01.01.2002 16:00 20 pieces for 01.01.2002 18:00 Should Pegging Information be t ransferred to SAP R/3? Defines if pegging information should be transferr ed to a connected OLTP system.

Lifetime of Cross-System Correction Requirements

ATP Buckets:

Bucket Limit for Issue Elements

Use You specify the time here at which the bucket limit for issues lies in the ATP time series.

58

January 13, 2016


Position the limit so that it lies at a time with few issues (for example, at night). As the AT P time series cannot take account of summer time, the limit cannot always lie exactly at midnight. Dependencies The local time zones indicator decides whether the value specified here in UTC time or in the local time zone is interpreted. If you use totally conservative logic to evaluate the bucket and create sales orders without immediate scheduling, you can acquire a confirmation for the desired availability date by setting the bucket limit later than midnight (local time); therefore, the desired date at midnight still falls in the bucket for the previous day. If you put the bucket limit later than midnight (local time), the displayed dates of o rders, which are still updated in the bucke t for the previous day, are in the availability overview before the actual availability date.

Shift Receipt Bucket

Use You specify here the number of hours by which the bucket limit of the ATP time series for receipt elements is shifted towards the bucket limit for issue elements. You can achieve synchronous ATP time series f or receipts and issues by shifting by 0 hours, and asynchronous ATP time series using a value between 0 hours and 24 hours. If the shift is larger than the bucket size (24h / /SAPAPO/BUCKS_PER_DAY), it is calculated according to the bucket size. Note SAP recommends that you use synchronous ATP time series, or shift the receipts by half the length of the b ucket (12 hours for 1 bucket per day). Dependencies Concurrent requirements are due at the end of each receipt bucket in the product availability che ck. You can only make changes to the planned parameters. The changes only affect the system response after activation. For more information about the activation of bucket parameters, see the SAP Library under SAP Advanced Planning and Optimization (SAP APO) -> Global Available-to-Promise (Global ATP) -> Settings for Global ATP -> General Settings for Global ATP -> Definition of Buckets for ATP Time Series -> Activation of Bucket Parameters for ATP Time Series . Example The limit of the issue bu cket is at 06:00 UTC; the receipts are shifted 4 hours. Receipt elements and concurrent requirements are thus valuated in the product availability check at 02:00 UTC. Local Time Zones

Controls whether the bucket limit for issue elements is to be evaluated for all locations in UTC time or for each location in the su mmer time of the local time zone. Use We recommend that you set this ind icator. Dependencies

59

January 13, 2016


ATP buckets cannot take account of summer time. For this reason, the regulation for local time zones is taken from planning. In this way, the system ensures that midnight local time is always on the right date. You can only make changes to the planned parameters. The changes only have an effect on system b ehavior once you have activated. For more information about activating bucket parameters, see the SAP Library under SAP Advanced Planning and O ptimization (SAP APO) -> Global Available-to-Promise (Global ATP) -> Settings for Global ATP -> General Settings for Global ATP -> Definition of Buckets for ATP Time Series. Note: Since the system only determines time zones when creating a pegging area, it only considers changes to the time zone of a location for newly added products or individual sections. For this reason, yo u should also reactivate the bucket parameters when you change the time zone of a location to make sure that all products in this location use the time zone that you have just set. Example You have defined a bucket limit for midnight local time f or receipts and issues. In this case, the bucket limit for a plant in Germany is at 22:00 UTC, in Buenos Aires at 02:00 UTC and in Ch icago at 05:00 UTC.

Number of Buckets Per Day

Specifies how many ATP buckets are created per day and thus the accuracy with which the product availability check counts. The standard value is 1. This means that the product availability check is exact to the day. Use We recommend that you keep the standard value 1, as a value greater than 1 leads to performance problems. The bucket size is calculated as follows: 24 hours/number of buckets per day. In the case of 3 buckets, the bucket size is thus 8 hours, for example. Dependencies If you have set the indicator distribution key active in time series , the value must be 1. Th e bucket size has an effect on the way the system interprets the indicator shift receipt bucket. You can only make changes to the planned parameters. The changes only have an effect on system behavior once you have activated. For more information about activating bucket parameters, see the SAP Library under SAP Advanced Planning and O ptimization (SAP APO) -> Global Available-to-Promise (Global ATP) -> Settings for Global ATP -> General Settings for Global ATP -> Definition of Buckets for ATP Time Series -> Activation of Bucket Parameters for ATP Time Series . Example The limit of the receipt and issue buckets is 04:00 UTC, there ar e 4 buckets per day. In this case, requirements before 04:00 UTC are evaluated at 22:00 on the previous day, and requirements between 04:00 and 10:00 at 04:00 UTC.

Distribution Key Active in Time Series

Controls how the system incorporates the finished products of process orders that stretch over several days into ATP time series. Use If you do not set the indicator, the system incorporates the finishes products at the end of the order into the ATP time series. If you set the indicator, it incorporates them p roportionately to the daily produced quantity according to planning.

60

January 13, 2016


Activation of this indicator affects performance slightly because each capacity change requires adjustments. Therefore, activ ate the indicator only for process orders that stretch ov er several days. Dependencies If you set this indicator, you must use day buckets ( number of buckets per day = 1). The most sensible parameter combination consists of working with local ( local time zones = 'X'), synchronous ( shift receipt bucket = 0) buckets that end at midnight ( Bucket limit for receipt elements = 00:00). In the case of this parameter combination, the quantity of a prod uct produced on one day is available for requirements on the following day. You can only make changes to the planned parameters. The changes only have an effect on system behavior once you have activated. For more information about activating bucket parameters, see the SAP Library under SAP Advanced Planning and O ptimization (SAP APO) -> Global Available-to-Promise (Global ATP) -> Settings for Global ATP -> General Settings for Global ATP -> Definition of Buckets for ATP Time Series -> Activation of Bucket Parameters for ATP Time Series .

Value Assignment of Bucket Limits in Product Availability Defines the restrictions by which the product availability check is to evaluate ATP time series.

Use Here, you define how ATP time series are evaluated in the product availability check. Requirements are valuated at the end of the corresponding receipt bu ckets. The following options are available for valuating receipt buckets: No Restriction The time series can be used for all ATP groups. 







Progressive Logic Only The time series are set up specifically for the pro gressive logic. Conservative Logic Only The time series are set up specifically for the co nservative logic. Exact Data Only The time series are set up specifically for exact data. The bucket boundaries are relevant, for example, for grouping several

partial confirmations on the same day.

Dependencies You can use synchronous receipt and issue buckets in combination with all time series. You must use asynchronous ATP time series in combination with the conservative logic only. If you use synchronous ATP time series with the progressive calculation, the system beh avior corresponds to the behavior in the ERP system. See also For more information, see SAP Library for SAP Supply Chain Management under SAP Advanced Planning and Optimization (SAP APO) -> Global Available-to-Promise (Global ATP) -> General Settings for Global ATP -> Maintain Global Settings -> Buckets for ATP Time Series -> Valuation of Receipts and Issues in Buckets.

61

January 13, 2016


Global Available to Promise (Global ATP) Rule Based Availability Check: SPRO -> Advanced Planning and Optimization -> Rule Based Availability Check -> Define Condition Table

Define Condition Table A condition table defines the combination of fields (key) that lable an individual condition record. The system stores the specific condition data that you have entered in the system in a condition record. Activities 1. Create a field catalog. In this way, you d efine the fields that you can select fo r rules-based ATP (usage "O") when creating or maintaining a condition table. Choose New Entries. o Generate the selection list using the F4 input help. o Choose the fields you want to use as parameters in the condition tables by means of a double-click. These fields are filled with values from the calling OLTP system during runtime. o Save your entries. 2. Create a condition table for rules-based ATP. o

o o o o

o

Specify the name of the table you want to create. Specify whether you want to create the table with or without a validity period. Specify a description for the condition table. Select the desired fields for the condition table from a list of the allowed fields in the field catalog. See also consultant note 514353. Generate the new condition table

62

January 13, 2016


Name of the condition field This indicator specifies fields that you can choose when creating or maintaining a condition table. Use When you create or maintain a condition table, you only see the fields specified for a specific combination of use and application. These fields are also used by the access sequences when searching for valid condition records during the processing of the conditions. Example Using the field catalog, you determine which fields can be u sed for the condition technique. For example, when the field values of the sales order correspond to the condition records at runtime, the condition record that was found specifies the rule to be used in the availability check.

63

January 13, 2016


Condition Table Definition Combination of specific fields which creates the key of a condition record. Use In a rule strategy, you define the sequence of condition types. An access sequence can be assigned to the respective condition type. This specifies where exactly the sy stem should search for the condition records which are relevant to a certain condition type. Every access in the access sequence refers to a condition table. Using the f ields (of the key, that is) defined in the table, the system can trace the valid condition records. The condition tables are used in rules-based ATP (use "O") or in transportation and shipment scheduling (use "U"). Procedure When creating a condition table, define one or several target fields as a table key. In addition, you must enter information into the system as to where it should take the target field value from. To do this, specify a source field. Source field and target fi eld are identical as a rule, but can also be different. If the target field "customer" is part of the key, you can determine, for example, that the system should use "ship-to party" as a source field and should adopt the value found there.

64

January 13, 2016


Global Available to Promise (Global ATP) Maintain Access Sequences: SPRO -> Advanced Planning and Optimization -> Rule Based Availability Check -> Maintain Access Sequences

Maintain Access Sequences Use In this IMG activity you maintain the access sequences. You use access sequences to define the following: Which condition tables are used to access the condition records The sequence of these condition tables Which field contents are used to read these condition tables You can assign multiple condition tables to an access sequence. Prerequisites You have defined condition tables. Activities To create an access sequence, proceed as follows: 1. Choose New Entries and enter an alphanumeric key (maximum four-digits) and a name.   

2. Select the entry and choose Accesses. 3. Choose New Entries. 4. In the field Sequence Number , define the sequence of the access within the access sequence. Enter a sequence number, even if you are only defining one access. Note that the sequence number must not be zero, otherwise no rules-based availability check is performed. Define the sequence number in steps of 10, so that you can insert subsequent entries. 5. In the Table field, select a condition table. As long as the Table field is switched to input-ready, the table entry canno t be found. If you h ave selected the condition table, you must select fields. If you go back, the field is no longer ready for input. 6. Set the Exclusive indicator if you d o not want further condition tables to be evaluated after the first successful access.

65

January 13, 2016


We recommend that you do not set this indicator, otherwise the evaluation of the condition tables is terminated after the first successful access. 7. Select an entry and choose Fields. As a rule, you will not be making any new entries in the v iew Change Access Fields: Overview . 8. Enter a value under Source of specific value if you want the system to overwrite the value in the field catalog and copy the specific value. By specific value, we mean the value used to fill a field when accessing the condition record. A field can either by replaced by the value of the source field or the specific value. 9. If you want to allow the initial value, set the indicator in the field Init . The initial indicator has two meanings. For one, it means that the condition table is accessed if the field in the document header or document item is initial, and its other meaning is that, during automatic return transport of data that was determined in the access, an initial value may be returned . 10. Save your entries. To mark access sequences for generation, proceed as follows: 1. Choose Utilities. The screen Access Sequences: Generation is displayed. 2. The Usage field states the area for which the condition usage is to search. Choose the value O (for rules-based ATP) or U ( for transportation and shipment scheduling).

3. The application splits the usage of a condition into multiple subareas. Use F4 input help to enter a corresponding value. 4. Use F4 input help to select a corr esponding access sequence. 5. Choose Program -> Execute

66

January 13, 2016


Global Available to Promise (Global ATP) Maintain Condition Type: SPRO -> Advanced Planning and Optimization -> Rule Based Availability Check -> Maintain Condition Type

67

January 13, 2016


Maintain Condition Type In this step, you maintain the condition type and assign it to an access sequence. Condition types are used for determining rules in the rules-based availability check. Activities To create a condition type, proceed as follows: 1. Define an alphanumeric value (maximum four-digits) and specify a name. 2. Assign an access sequence to the condition type by choosing an access sequence using the input help (F4). 3. If necessary, specify a validity period that is pro posed in the rule determination. 4. Save your entries.

Global Available to Promise (Global ATP) Maintain Rule Strategy: SPRO -> Advanced Planning and Optimization -> Rule Based Availability Check -> Maintain Rule Strategy

68

January 13, 2016


Maintain Rule Strategy In this step, you define rule strategies. The rule strategy determines the condition types and defines the sequ ence in which they are evaluated. Activities To create a rule strategy, proceed as follows: 1. Choose New Entries and enter a value. 2. Determine the rule strategy type . 3. Enter a name for the rule strategy. 4. If you want the number of substitutions to be defined by means of the rule strategy, set the indicator Rule Strategy Defines

Maximum Number of Substitutions. You can only set this indicator for inclusive rule strategies, since exclusive rule strategies simply restrict the search space of inclusive rule strategies. When setting the indicator, choose the number and entity of substitutions. These settings are valid for all rules that the system finds using this rule strategy. Note that the settings that you make here for the number of substitutions and the entity overwrite the settings that you might have made in integrated r ule maintenance. 5. Select the entry and choose Control -> New Entries. 6. In the Level field, enter the number that defines the sequence of the condition types within the rule strategy. The level number cannot be set to zero. 7. In the CTyp field, select a condition type. 8. Save your entries.

Rule Strategy Defines Number of Substitutions Indicates that the system determines the number and entity of the substitutions b y means of evaluation of the rule strategy a nd not by means of evaluation of the rules. Use If you set this indicator, the settings that you specify here for the number and entity of the substitutions apply to all rules in this rule strategy. The system overwrites the settings for the number and entity of the substitutions that you have made, as necessary, in integrated rule maintenance. Note The system only takes account of this indicator in inclusive rule strategies.

69

January 13, 2016


Global Available to Promise (Global ATP) Maintain Rule Strategy: SPRO -> Advanced Planning and Optimization -> Rule Based Availability Check -> Assign Rule Strategy or Rule Strategy Sequence

Assign Rule Strategy or Rule Strategy Sequence Use In this IMG activity, you determine the following activation parameters to determine a rule strategy or a rule strategy sequence: Technical scenario Definition: technical scenario 

70

January 13, 2016


Global Available-to-Promise (SCM-APO-ATP)

An activation parameter that is used for determining the rule strategy or the rule strategy sequence. The technical scenario corresponds to the communication technology that triggered a rules-based availability check. Possible communication technologies include:  Online dialog  Batch input  EDI The values for this parameter are transferred from the R/3 System to APO. The coding is f ixed. Online dialog: AA   Batch input: BB  EDI: DD  Backorder processing: EE Other values can be transferred from a non-R/3 System. Return -> Definition: technical scenario  Business transaction Definition: business transaction Global Available-to-Promise (SCM-APO-ATP) Activation parameter that is used for determining the rule strategy or the rule strategy sequence. The business transaction corresponds to the business context in which a rules -based availability check should be carried out. Example: The sales document type of the sales order The business transaction is created in R/3 Customizing for Sales and Distribution and assigned to an or der type. This value is transferred to APO from the calling OLTP system at runtime and determines the rule strategy in APO. Return Definition: business transaction Action type  Definition: action type Global Available-to-Promise (SCM-APO-ATP)

->

Activation parameter used to determine the rule strategy. The action type corresponds to the manipulation technique of the calling transaction. Possible manipulation techniques include creating, changing, and copying. These values are hard-coded in the SAP R/3 Sy stem and are transferred to SAP APO from the call ing application. The values are assigned by the SAP R/3 sales ord er, the SAP CRM sales order, and backorder processing in SAP APO as follows:  Create: A  Change: B  Copy: C In the case of stock transfers in SAP R/3, the value for the action type remains initial. You can use your own values for simulations on the SAP APO server. Return -> Definition: action type Activities 1. Create three activation parameters. Note that the values of the activation parameters must be the same as the values transferred from the connected OLTP system. If this is not the case, the system is unable to find any rule strategy sequences, rule strategies, or rules. 2.

Assign

a

rule

strategy

sequence

or

a

rule

strategy

to

the

activation

parameters.

Note that you can assign either a rule strategy sequence or a rule strategy to a set of activation parameters from the OLTP

system . 3. Specify how several calculation profiles that come from successive accesses behave. To do this, choose whether a subsequent calculation profile replaces or supplements the settings of the prev ious calculation profile during rule evaluation.

71

January 13, 2016


4. If you want the system to execute preselection of suitable substitutions based on the rule strategies determined, set the preselection of suitable substitutions indicator.

Rules-based ATP: Calculation Profile Definition In the calculation profile, you define conditions according to which a rules-based availability check is considered to be successfully executed. These conditions are valid for all combinations of (substitute) product and (substitute) location for the current rule and are used in the calculation of the material availability date. Note You cannot create a calculation profile in an exclusive rule. Since the calculation profile always refers to the location products determined by the rule, you should not define conditions that are to be used if there are no results (= quantity to b e excluded). The calculation profiles are not used in the calculation of the delivery dates. Dependencies In the Handling Calculation Profiles field, you define whether the system substitutes or supplements the prev ious calculation profile when several calculation profiles are evaluated.

Preselection of Suitable Substitutions Determines that the preselection of suitable substitutions is allowed. Use If you set this indicator, you switch on preselection of suitable substitutions. You are then able to select the most suitable substitution from the substitution list. If you do not set this indicator, you do n ot switch on preselection of suitable substitutions. Dependencies For the system to pres elect suitable substitutions, you must also make this setting in the check instructions. For more information, see the Implementation Guide (IMG) of SAP SCM under Maintain Check Instructions.

72

January 13, 2016


Global Available to Promise (Global ATP) Back Order Processing: SPRO -> Advanced Planning and Optimization -> Back Order Processing -> Maintain Filter Type

Maintain Filter Type In this step, you define a filter type. In a filter type, you define which characteristics can be used in a filter for backorder processing. Activities 1. Define a filter type. 2. Specify the document categories for which the filter type should be used.

73

January 13, 2016


3. Choose the characteristics of the filter type from the template structure. If you have specified several document types, you can only select the intersection of the usable characteristics as these characteristics must occur in each document category. 4. A report for the filter is generated from the filter type. The filter itself can be stored as a v ariant for the selection screen of the generated report. Generate the filter type using Tools -> Generate Filter Type and Sort Profile . Generation is only necessary if errors occur during transports to Customizing. Normally, filter types are generated automatically. The variants you have maintained up to now are not lost if only minor changes were made to the filter type.

Further notes Filter types are delivered for filtering using alerts and net change selection and order due lists.

74

January 13, 2016


Global Available to Promise (Global ATP) Back Order Processing: SPRO -> Advanced Planning and Optimization -> Back Order Processing -> Define Sort Profile

Define Sort Profile In this step, you def ine a sort profile for backorder processing. You define the processing sequence for document items in backorder processing with specifications in the sort profile. You specify characteristics, their sequence (or weighting), and the sort order in this profile. You can choose all characteristics from the template structure, and can also specify for each characteristic whether it shoul d be sorted in ascending or descending order. Special sortings (for example, non-alphabetical) can be used for some characteristics. Sorting results in a pr iority for the documents in backorder processing. Activities 1. Create a sorter. 2. Define the details of the sort profile. o o

o

Choose the characteristics. Define the order (weighting) according to which document items should be so rted in backorder processing by fixing the item. Define whether sorting should be performed in ascending or descending order, or whether sorting should be performed with special sorting. You define special sorting using Tools -> Maintain Special Sorting.

3. Save your entries. 4. Generate the sort profile using Tools -> Generate Filter Type and Sort Profile . Generation is only n ecessary if errors have occurred during transports to Customizing. Sort profiles are normally generated automatically.

75

January 13, 2016


Global Available to Promise (Global ATP) Back Order Processing: SPRO -> Advanced Planning and Optimization -> Back Order Processing -> Parallelizing Backorder Processing

76

January 13, 2016


Parallelizing Backorder Processing Use In this IMG activity, you activate and make settings for parallelizing backord er processing. By executing backorder processing in parallel, you can reduce the overall runtime. Note that the business function of backorder processing is not changed by p arallelization. Requirements For the processes to be executed in parallel, you must define a server group. For more information, see Create RFC Connections in the Implementation Guide (IMG) of the SAP Web Application Server . Sufficient resources ( application server and work processes) must be available to activate parallelizing backorder processing. These resources are described by the se rver group. Standard settings Parallelizing backorder processing is delivered inactively. A profile (EXAMPLE) that contains example settings for parallelization of the steps is deliv ered. You must adjust these size settings to your system landscape and its usage. Activities Area profile 1. Define a profile. 





2. Define the steps of backorder processing that are to be executed in parallel. For each of the steps, specify a maximum and

minimum group size and the minimum necessary group number. In addition, you can restrict the number of the maximum used work processes. 3. Set the indicator for the parallelization of processes. We recommend that you optimize your profile settings. 

Area activation Activate parallelizing backorder processing by selecting a prev iously defined profile and a server group. If you make the Customizing settings in a test system and then transfer them to the productive system, make sure that a server group with the same name exists in the productive system. Note that, in the following cases, yo u switch off parallelizing backorder processing manually: When calling batch backorder pro cessing o When calling the worklist of backorder processing Activation is not possible in this way. Switching off parallel execution makes sense if, in your system landscape, you have o

problems reaching other application servers. 

Area Parameters You can further influence the behavior of p arallelizing backorder processing using parameters. The following p arameters are available: o o o o o o

Restriction of field catalog Log of process runtimes switched on Filter: Parallel execution only if special criteria per item Filter: Read data from SAP liveCache before parallelization Filter: Read data from database before parallelization No parallelization in case of missing chain

Note 





You can only improve the runtime of backorder processing when it is executed in parallel in the following conditions: o Enough items exist in the worklist. o You set the group size and the number of groups in such a way that the effort needed to manage the parallel processes is not too big. Parallelizing backorder processes only parallelizes execution in SAP APO. The order documents are updated in the OLTP system per document, as hitherto. You can optimize the runtime of this part of the update by correctly setting the Queue. If you use the customer exits of backorder processing in your system, or if these have been modified, problems may occur when the steps are executed in parallel. A correct and co mplete transfer of data in function groups cannot be ensured.

77

January 13, 2016


78

January 13, 2016


79

January 13, 2016


80

January 13, 2016


Global Available to Promise (Global ATP) Questionnaire: 1.

2.

What are advantages of GATP over AT P? Ans.: GATP is the advanced version of ECCATP with below exclusive functionality: a. Location substitution ATP b. Product Substitution ATP c. PPM (Alternate Production Version) substitution d. ATP against forecast What is TQA and dependent setting in ECC for TQA to work? Ans.: TQA functionality is used to block the inventory of order quantity temporally during order processing (Creation / Change). In ECC, material block indicator should be active for availability check configuration / checking group.

3.

What is the prerequisite setting in APO to bring ATP customizing settings from ECC? Ans.: Import customizing should be allowed Global setting for availability check

4.

Name two GATP specific CIF integration models. Ans.:

5.

a. ATP Check b. ATP Customizing What is APO business event called in ECC? What are the business events of sales order & delivery? Ans.: APO Business events are known as Checking Rule in ECC and Business event for sales order is A and delivery is B.

6.

What is the ATP category of sales order? Ans.: BM

7.

How a check mode in APO product master is determined from ECC? Ans.: Check mode is determined from customer requirement class from ECC in APO product master. Requirement class is assigned with requirement type; requirement type is assigned with requirement strategy, Requirement strategy is assigned with strategy group and strategy group is assigned with material master in ECC through below three objects:

8.

a. Directly in material master (Strategy Group in MRP3 View) b. Assigning in MRP group and MRP group assignment in material master (MRP1 View) c. Default strategy group against material type How does Method of ATP check determined in APO? Ans.: ATP check method (Product check, allocation check, check against forecast, Ruled based AT P, MATP, etc.) is determined through check instruction and check instruction is maintained with combination of check mode / requirement class and business event / check rule

9.

What are the basic GATP checks? Ans.:

a. Product availability check b. Product allocation Check c. Check against forecast 10. Name three advanced GATP ch eck methods. Ans.: a. Rule based ATP b. Multilevel ATP c. CTP d. Lead time ATP 11. What are the configurations options to switch on/off ATP check for a sales order item? Ans.: a.

ATP check deactivation in Schedule line category

81

January 13, 2016


b. ATP check deactivation in requirement class c. No check activation in Availability check 12. How to switch off ATP and switch on GATP check and vice versa? Ans.: Activate/Deactivate ATP Check Integration Model 13. How is checking horizon in APO product master determined from ECC for externally procured and in-house produced materials? Ans.: a.

For in-house production, total replenishment time is considered as checking horizon in APO. If total replenishment time is not maintained in material master, it considers Inhouse production time and GR processing time b. For external procurement, it considers Planed delivery time, GR processing time and PO generation time for plant (From Configuration) 14. What are the key fields in APO pr oduct master for GATP? Ans.: a. Product allocation pro cedure b. Check mode c. ATP group d. Checking Horizon e. Checking Horizon Calendar 15. What is ATP check with ch ecking horizon? Ans.: Order confirms / determines the schedule confirmation date considering checking horizon, if product is not available. 16. What is scope of check and how is it determined? Ans.: Scope of check identifies which MRP element will be considered to calculate STOCK, RECEIPT and ISSUE SEGMENT. Scope of check is configured with combination of Business event / Checking rule and availability check / ATP group. ATP group/ Availability check is assigned in product master 17. How is ATP category in APO mapped to ECC? Ans.: ATP category is mapped against R/3 object with MRP element 18. What is the ATP category of sales order? Ans.: BM 19. What is product allocation group? Ans.: Product allocation group is the grouping of characteristics / Planning object, against which allocation is done (e.g. Allocation needs to be done against Product and Customer Or Product, Sales Or g. , Plant and Material) 20. What is the ATP field catalogue ch aracteristic for product allocation object? Ans.: KONOB 21. Name two configuration settings done in product allocation group? Ans.: a. Time bucket profile b. Consumption / Backward consumption Period c. Forward Consumption period d. Considering active and inactive allocation 22. What is connection between p lanning area and product allocation group and why is it required? Ans.: Planning area is assigned with product allocation group to determine allocation quantity through key figure against characteristics of planning area. Respective characteristic of PA is assigned with planning object (i.e., Plant, Material, Lo cation, etc.) and key figure is assigned with sales order quantity (AEMENGE) and allocation quantity (KCQTY). Sales order quantity & allocation quantity can’t be created directly in product allocation group, hence CVC & PA data needs to be transferred from

PA to allocation group. 23. How to switch on/off product allocation check for a product?

82

January 13, 2016


Ans.: By assigning allocation procedure in product master 24. What is collective product allocation and how is it set up? Ans.: The order quantity can be consumed against the product allocation quantity using different methods in product

25. 26. 27.

28.

29. 30. 31.

32. 33.

34.

35. 36. 37.

allocations. Cumulative indicator needs to b e activated in allocation procedure. Collective product allocation is used for generic customer/Planning Object, which is not included in CVC. Wild card “#” is used to d etermine the product allocation for the same. Which configuration connects product allocation object and product allocation group? Ans,: Product allocation procedure How is CVC (characteristics value combination) created in p roduct allocation group? Ans.: CVC is transferred from planning area to product allocation group. Name two types of substitution procedures in rule based ATP (RBA) check. Ans.: a. Location b. Product c. PPM What is an inclusive rule? Ans.: System determines substitute products and substitute locations through inclusive rule while system exclude substitute Products and location t hrough exclusive rules from inclusive rule. Is it possible to restrict number of substitutes to one and how? Ans.: It is possible to restrict for only one substitute rule by selecting in Rule maintenance. Name a use of rule control? Ans.: Access strategy of substitution list ( Wo rk forward from input, start from top of list, etc.) What is allowed delay in RBA and where is it set? Ans.: It determines the number of days by which the confirmed material availability date is permitted to differ from the determined material availability date for a d elayed confirmation to be permissible. It is maintained in calculation profile and calculation profile is assigned with rule. Name one use of location determination activity? Ans.: To determine separate business even t and check mode (Other than from product master) How ECC sales order type is linked to rule strategy for RBA in APO? Ans.: Business transaction is assigned to SO document type in ECC and rule strategy is assigned with business transaction in APO. How is rule for RBA determined for a sales order item? Ans.: Business transaction is assigned to SO document type in ECC and rule strategy is assigned with business transaction in APO. Sales Item category is assigned with SO document type w.r.t. material item category group. Item category is determined in sales order line item based on SO document type. How RBA is switched o n/off though configuration? Ans.: Removing business transaction in SO document type. Name the methods of calling production from GATP? Ans.: Multi level ATP, CTP and PPM substitute Which is the main constraint for CTP? a. Resource capacity b. Component availability Ans.: a

38. Which is the main constraint for MATP? a. Resource capacity b. Component availability

83

January 13, 2016


Ans.: b 39. What is the type of scheduling in CTP? a. Finite scheduling b. Infinite scheduling Ans.: a 40. What is the type of scheduling in MATP? a. Finite scheduling b. Infinite scheduling Ans.: b 41. Which method of G ATP check create ATP Tree structure? Ans.: MATP assigned with business transaction in APO. Sales Item category is assigned with SO document type w.r.t. material item category group. Item category is determined in sales o rder line item based on SO document type. 42. How RBA is switched o n/off though configuration? Ans.: Removing business transaction in SO document type. 43. Name the methods of calling production from GATP? Ans.: Multi level ATP, CTP and PPM substitute 44. Which is the main constraint for CTP? a. Resource capacity b. Component availability Ans.: a 45. Which is the main constraint for MATP? a. Resource capacity b. Component availability Ans.: b 46. What is the type of scheduling in CTP? a. Finite scheduling b. Infinite scheduling Ans.: a 47. What is the type of scheduling in MATP? a. Finite scheduling b. Infinite scheduling Ans.: b 48. Which method of G ATP check create ATP Tree structure? Ans.: MATP 49. Is TQA created in CTP? Ans.: Yes 50. Temporary Planned Independent requirement is created in CTP or MATP? Ans.: MATP 51. What is the configuration to choose production type as CTP or MATP & what is set for CTP/MATP?

84

GATP

Recommend Documents