Professional Documents
Culture Documents
Gatp PDF
Gatp PDF
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 Checking and Materials Planning.................................................................................................17
Definition: replenishment lead time ........................................................................................................................18
Use 2: Flexible Planning ...........................................................................................................................................18
Total sales order requirements ................................................................................................................................18
Use..........................................................................................................................................................................18
Definition: summarized requirements .....................................................................................................................18
Total delivery requirements ....................................................................................................................................18
1
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
Use..........................................................................................................................................................................19
Material block in availability check with transfer of qties .........................................................................................19
Procedure ...............................................................................................................................................................19
Example ..................................................................................................................................................................19
No availability check ................................................................................................................................................19
Dependencies .........................................................................................................................................................19
Availability check with cumulative, confirmed quantities .........................................................................................20
Example ..................................................................................................................................................................20
Recommendation ....................................................................................................................................................21
Use..........................................................................................................................................................................21
Availability with cum. quantities: Response to shortfall ...........................................................................................21
Use..........................................................................................................................................................................21
Dependencies .........................................................................................................................................................22
Indicator for relevance during check 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 of the availability check..............................................................................................................................25
Use..........................................................................................................................................................................25
Block indicator for availability and requirements .....................................................................................................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 For Availability Check ..................................................................................................................28
Checking Group for Availability Check .....................................................................................................................30
Use 1: Availability Checking and Materials Planning.................................................................................................30
Use 2: Flexible Planning ...........................................................................................................................................30
Checking Rule for Availability Check ........................................................................................................................30
2
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
...............................................................................................................................................................................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,
GLOBAL AVAILABLE TO PROMISE
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,
GLOBAL AVAILABLE TO PROMISE
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,
GLOBAL AVAILABLE TO PROMISE
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 deactivated. Manually, APO configuration
needs to be updated for any changes in ECC ATP configuration.
2. Minimum bucket period for gATP is 1 day.
3. Temporary quantity assignment (TQA) indicator if you want to make it possible for 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 forecast check. Activate RBA indicator is also 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 plant 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 global 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 product allocation object
15. Wild card is used to determine the product allocation of non-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 substituted 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,
GLOBAL AVAILABLE TO PROMISE
2016
10
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
(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 SAP live Cache, which processes large volumes of data 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).
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 proposed. The ATP quantity referenced during the product availability
check is based on categories defined in Scope of Check.
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 from alternative sites to customers. In addition, it permits
certain products to be substituted as required to successfully satisfy customer demands. RBA is beneficial for Distributors, consumer
product goods Industries
11
January 13,
GLOBAL AVAILABLE TO PROMISE
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 changed. 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 difference 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 information about the functionality.
Backorder Processing
The basic idea of backorder processing is to carry out a new ATP check for a set of order 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 documents, and schedule them.
12
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
Integration
Calling the ATP check from SAP APO
Function Required Component
Purchasing (MM-PUR)
Purchasing (MM-PUR)
13
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
14
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
In this logic, the system does not 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 re ceipt
that lies directly before a sales order which has already been confirmed is no longer sufficient to cover the requirement.
The following example should clarify this point:
In this example, the first sales order was completely confirmed when the planned order lay before sales order 1 on the time axis. Then,
the planned order was rescheduled out so that it now lies after the delivery date of sales order 1 on the 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 order has been rescheduled. Therefore,
the sum of all the confirmed quantities exceeds the sum of all receipts.
With the cumulation of quantities, you can avoid such inconsistencies asyou can control exactly how the system is to carry ou t 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 cumulated
ATP quantity. This means that the new sales orders can only be confirmed 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 ATP 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 checking logic)
15
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
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 summarized requirements or individual requirements for each checking group. Changing the method of summing
up requirements results in a change in the information contained in the record. When 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,
GLOBAL AVAILABLE TO PROMISE
2016
1. Specifies whether and how the system checks availability and generates 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, curre nt, 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 bottom-
up approach to planning is possible. The system can be configured so that target values set at one organizational 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 sales 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. Flexible
planning offers options for customized configuration. Planning in standard SOP is based on product group hierarchies and is performed
level by level. Flexible planning is performed on hierarchies containing chosen organizational levels, for example, sales organization,
distribution channel, material, and plant. In flexible planning, users can define the content and layout of planning screens.
The component can run in a distributed environment using Application Link Enabling (ALE).
Return->
Definition: Sales_&_Operations Planning
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 planning
(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,
GLOBAL AVAILABLE TO PROMISE
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.
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 removed.
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 checking group.
19
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
Starting from the delivery date of the sales order and looking in the past, the system checks to see whether ATP quantities exist. If it
actually finds an ATP quantity, it is reduced by the new sales order. Sales orders can only 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 quantity 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 explain this situation:
Situation 1
Committed
MRPelemt Recpt/Reqmt ATP qty Cum. ATP qty
qty
Stock 100 0 0 -
PlOrd 100 0 -100
SalesOrd -200 - - -200
Situation 2
MRPelemt Recpt/Reqmt ATP qty Cum.ATP qty Committed qty
Stock 100 0 0 -
SalesO1 -200 -100 -100 -200
PlOrd 100 0 0 -
SalesO2 -100 - - 100
20
January 13,
GLOBAL AVAILABLE TO PROMISE
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 the sales order 1. For the new sales
order 2, an ATP quantity of 100 exists as the moved planned order is now 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 following 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 sum 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 requirements 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 requirement 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 possible:
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,
GLOBAL AVAILABLE TO PROMISE
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.
22
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
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 order, 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.
23
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
Return->
Definition: material_master_record
24
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
25
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
26
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
27
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
28
January 13,
GLOBAL AVAILABLE TO PROMISE
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 original field led to sales and delivery requirements being selected, an
unselected field leads to unselected fields in the conversion program.
29
January 13,
GLOBAL AVAILABLE TO PROMISE
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 checking rules for each individual application. Therefore, you define the checking rule for 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,
GLOBAL AVAILABLE TO PROMISE
2016
32
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
33
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
Requirements class
Key which specifies the planning strategy internally within the system.
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 requirements for the material.
If this assignment is not required, 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.
34
January 13,
GLOBAL AVAILABLE TO PROMISE
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 schedule line level, whether or not 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.
35
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
36
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
37
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
38
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
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 schedule line level, whether or not you
require transfer of requirements for the relevant transaction.
39
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
40
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
41
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
42
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
43
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
44
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
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 carried out for the transactions.
You can find the business transactions in the APO planning system (Field BPROC) under:
Global ATP -> Settings -> Rule-based ATP -> Conditions -> Assign rule strategy.
45
January 13,
GLOBAL AVAILABLE TO PROMISE
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 using the order type for the sales order from which calling takes place.
46
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
47
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
48
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
49
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
50
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
51
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
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,
GLOBAL AVAILABLE TO PROMISE
2016
54
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
55
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
56
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
Import Customizing
The indicator specifies if the Customizing 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 indicator, the Customizing d ata is
imported.
ATP: Accept Schedule Lines According to Time
Confirmed schedule lines in the sales order 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 ad opted
based on the day or on the time.
If the indicator is set, the sales order 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 be 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 following (partially) confirmed schedule lines are created:
57
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
ATP Buckets:
Use
You specify the time here at which the bucket limit for issues lies in the ATP time series.
58
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
Position the limit so that it lies at a time with few issues (for example, at night). As the ATP 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 d esired 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 orders, which are still updated in the bucket for the
previous day, are in the availability overview before the actual availability date.
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 for 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 bucket (12 hours for 1 bucket
per day).
Dependencies
Concurrent requirements are due at the end of each receipt bucket in the product availability check.
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 bucket 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.
Controls whether the bucket limit for issue elements is to be evaluated for all locations in UTC time or for each location in the summer
time of the local time zone.
Use
We recommend that you set this indicator.
Dependencies
59
January 13,
GLOBAL AVAILABLE TO PROMISE
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 behavior once you have activated.
For more information about activating 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.
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, you 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 for 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 Chicago at 05:00 UTC.
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. The 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 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 receipt and issue buckets is 04:00 UTC, there are 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.
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 proportionately to the daily produced quantity according to planning.
60
January 13,
GLOBAL AVAILABLE TO PROMISE
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 over 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 product 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 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.
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 buckets.
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 progressive logic.
Conservative Logic Only
The time series are set up specifically for the conservative 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 behavior 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,
GLOBAL AVAILABLE TO PROMISE
2016
62
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
63
January 13,
GLOBAL AVAILABLE TO PROMISE
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 system 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 fields (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 field 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,
GLOBAL AVAILABLE TO PROMISE
2016
65
January 13,
GLOBAL AVAILABLE TO PROMISE
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 view 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 corresponding access sequence.
5. Choose Program -> Execute
66
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
67
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
68
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
69
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
70
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
71
January 13,
GLOBAL AVAILABLE TO PROMISE
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.
72
January 13,
GLOBAL AVAILABLE TO PROMISE
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 variant 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,
GLOBAL AVAILABLE TO PROMISE
2016
75
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
76
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
77
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
78
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
79
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
80
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
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.:
a. ATP Check
b. ATP Customizing
5. 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:
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
8. How does Method of ATP check determined in APO?
Ans.: ATP check method (Product check, allocation check, check against forecast, Ruled based ATP, 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 check 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,
GLOBAL AVAILABLE TO PROMISE
2016
Ans.:
82
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
Ans.: a
83
January 13,
GLOBAL AVAILABLE TO PROMISE
2016
Ans.: b
Ans.: a
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 order line item based on SO document type.
Ans.: a
Ans.: b
Ans.: a
Ans.: MATP
Ans.: Maintain production type in check mode and “C – Multi Level ATP Check” is set for MATP and standard for CTP.
52. What is a backorder?
Ans.: The order which have not been confirmed fully.
53. Name modes of executing backorder processing.
Ans.:
a. Immediate Update
b. Simulation Mode
c. With Post processing mode
54. How is backorders picked up for backorder processing?
Ans.: Based on filter and sort profile
55. How is prioritization of backorders done for backorder processing?
Ans.: Based on sort profile mentioned in variant.
56. What is sales order scheduling?
Ans.: Scheduling is used to determine Transportation Planning date, Material availability date, loading date and goods issue
dated based on requested delivery date considering transportation planning time, Material pick / pack time, loading time and
GI time.
57. What is the formula for calculating good issue date on a sales order schedule line using backward scheduling?
Ans.: Goods Issue Date = Requested delivery date (RDD) – Transport Planning Date
85