Multilevel ATP Check in Two Steps

To guarantee that the validity of a plan (BOM, PPM or runtime object) is not violated, and the lead times match the confirmation dates calculated in the multilevel ATP check at header level, the multilevel ATP check is always executed in two steps, provided the result of the "first" multilevel ATP check contains partial confirmation quantities and dates.

You can configure how the second step of the multilevel ATP check should be carried out in the check instructions for the finished product or header material using the parameters CompRemainReqmt (Remaining requirements of a component requirement group) and Conversion (Conversion mode of ATP tree structures).

In SAP APO Customizing, choose Start of the navigation path Global Available-to-Promise (Global ATP) Next navigation step General Settings Maintain Check Instructions End of the navigation path .

Process

In an initial step, a plan explosion and scheduling are carried out for the header material. Component requirements and component requirement dates of the header material are generated. The component requirements of the header material (requirements group) are checked according to the check methods set in the check instructions. Of course, a rules-based ATP check can also be executed at component level. If a rules-based ATP check is carried out for a component, the system searches for a substitute product or a substitute location, for example, according to the Customizing settings. A multilevel ATP check can be carried out for the substitution. For further information see Rules-Based ATP Check at Component Level.

The check result consists of confirmed quantities or partial quantities and dates for the requirement group at header level.

The setting in the conversion mode now defines which confirmed quantities or partial quantities and dates are included as new requirements in the second step of the multilevel ATP check. There is a further plan explosion and scheduling in a second step, with component requirement quantities and component requirement dates of the header material generated and checked again. In this case, however, the requirement quantity for the header material must be completely confirmed for the requirements date. There should be no partial confirmation quantities and dates. If there is a quantity that is still open, you can configure beforehand in the CompRemainReqmt field in Customizing how the system should deal with this open quantity.

Conversion Mode

The Conversion parameter in the check instructions of the header material determines for which confirmation rows, which resulted from the ATP check at header level in the first step, planned orders should be generated. There are the following options:

1 planned order for the requested date using the quantity confirmed through the first step of the check for this date (if no confirmation > 0 exists for the requested date, no order is created)
1 planned order for the total confirmation date using the total requested quantity (if the first step has produced no total confirmation, a planned order is not generated)
1 planned order for each confirmation date using the quantity confirmed in the first step for this date.

Starting from this setting, the corresponding confirmations of the first step are taken as requirements date and requirement quantity for the header material in the second step of the ATP check. A new plan explosion is then carried out using the requirement data. Within the ATP Controller, new requirement groups (component requirements for the header material) are created and checked. In this second step of the check, however, at header level, the complete requirement quantity must be confirmed for each requirement group that has resulted from such a plan explosion. Otherwise, the entire check result of this requirement group is rejected.

Remaining Requirement for Component Requirement Groups

The Rem. Reqmt (remaining requirement) parameter for component requirement group in the check instructions of the header material determines how the system deals with the quantity for which a successful check could not be carried out in the 2nd step. There are the following options:

Create remaining requirement at header level
If a rules-based ATP check is not carried out at header level, the result is a remaining requirement at header level. When the user transfers the result, there is an open quantity in the document that could not be confirmed.

If a rules-based ATP check is carried out, the remaining quantity is passed on to the subsequent substitutions (that are still to be checked) or to the remaining requirement of the rules-based ATP check (RBA remaining requirement). If creation of the remaining requirement is not configured for the rules-based ATP check, no remaining requirement is generated for the quantity remaining from the multilevel ATP check. In other words, there is no open quantity in the sales order.

Example: Confirmation after multilevel ATP check with rules-based ATP check at header level (with RBA remaining requirement)

Item	Product	Requirement Quantity	Confirmed Quantity
Main item 10	LUZ-FERT01	100	0
Subitem 11	LUZ-FERT02	80	80
Subitem 12	LUZ-FERT02	20	0

Example: Confirmation after multilevel ATP check with rules-based ATP check at header level (without RBA remaining requirement)

Item	Product	Requirement Quantity	Confirmed Quantity
Main item 10	LUZ-FERT01	100	0
Subitem 11	LUZ-FERT02	80	80

Create remaining requirement at component level
A new plan explosion is carried out using the quantity remaining from the first step of the multilevel ATP check and the original requested date at header level. Afterwards, a requirement group is generated from the components. However, no new ATP check is carried out for the components. In the document, the requirement is confirmed (confirmation of the requirement in the delivery proposal and transfer of the result in the document). The planned order, however, that is created in PP/DS for the open quantity, is unconfirmed at header and component level. It gains the status checked and unconfirmed. The quantity that could not be confirmed by the ATP check is nevertheless taken into account by ATP, since it is the requested quantity and not the confirmed quantity that is relevant for receipts.

An alert is generated in the Alert Monitor when the document is saved.
Create remaining requirement at component level for last possible date of checking horizon (reduce confirmation)
The remaining requirement is created at component level for a later point in time than the requested date. The system calculates this point in time starting from the checking horizon for the components from the product master. The earliest production date is the date of the unconfirmed planned order, provided that all components are available until the date of their checking horizon.

You can use the Business Add-In (BAdI) BAdI: Change Checking Horizon of MATP Components, if you want to set up your own calculation logic that the system uses to calculate the requested date. To call the BAdI, in Customizing for SAP Supply Chain Management (SAP SCM) choose Advanced Planning and Optimization Global Available-to-Promise (Global ATP) Enhancements ATP Controller Remaining Requirement for Multilevel ATP Check .

Note Note

If you want to use this function, you have to activate the business function SCM-APO-ATP, Usability and Various Functions (SCM_APO_ATP_1).

End of the note.

Example

The example should illustrate how the requirements and confirmations come into being within the multilevel ATP check. The examples do not show how the confirmations look in the document. The confirmed quantities or partial quantities can be seen there in the schedule lines for an item and/or subitem.

For more information, see the documentation for SAP ERP Central Component under How Sales Documents are Structured.

1. Step of the Multilevel ATP Check

Within the multilevel ATP check, the plan for a requirement at finished product level of 100 PC for 01.10. is exploded.

The plan explosion produces the following three component requirements:

Result of the plan explosion: Component requirements

Component	Requirements Date	Requirement Quantity
Component 1	15.09.	100
Component 2	20.09.	50
Component 3	25.09.	200

The ATP check for the components produces the following result:

Result of the ATP check for the components

Component	Requirement Date	Requirement Quantity	Confirmed Date	Confirmed Quantity
Component 1	15.09.	100	15.09.	10
			20.09.	90
Component 2	20.09.	50	20.09.	20
			25.09.	20
			30.09.	10
Component 3	25.09.	200	25.09.	200

The following result is produced at header level:

Result of the ATP check for the header material

Requirement Date	Requirement Quantity	Confirmed Date	Confirmed Quantity
01.10.	100	01.10	10
		06.10	70
		11.10.	20

If this confirmation was used in PP/DS at header level to create 3 planned orders for the relevant confirmations, the danger would be that the validity of the plan would be violated. The plan has been exploded for 01.10. with quantity 100, but the planned orders would be created for other dates and only with partial quantities. Furthermore, the requirements dates of the dependent requirements would probably no longer be correct (the first planned order would have a quantity of 10). Within the plan explosion, however, the requirements dates of the components have been determined for the quantity 100, based on lead time scheduling. In general, the runtime for the quantity 10 is lower, however. In other words, the requirements dates of the dependent requirements would be too early.

2. Step of the Multilevel ATP Check

After the first step, the following result was produced at header level:

Result of the ATP check for the header material

Requirement Date	Requirement Quantity	Confirmed Date	Confirmed Quantity
01.10.	100	01.10	10
		06.10	70
		11.10.	20

In the conversion mode in the check instructions, you chose Create Several Plnd Ords (1 Plnd Order Per Partial Confirm.).

The multilevel ATP check produces the following result in the second step:

Result of the ATP check for the header material

Requirement Date	Requirement Quantity	Confirmed Date	Confirmed Quantity
01.10.	100	01.10	10
		06.10	70

The ATP check only ran successfully for the two confirmations 10 for 01.10. and 70 for 06.10. The requirement of 20 for 11.10. could not be confirmed.

If it has been defined that the remaining requirement should be created at header level, the confirmation at header level (the request is still 100 for 01.10.) is, in total:

Result of the ATP check for the header material: Remaining requirement at component level

Requirement Date	Requirement Quantity	Confirmed Date	Confirmed Quantity
01.10.	100	01.10	30 (= 10 + 20)
		06.10	70

The 20 pieces at header level are confirmed in the document for the original requested date (01.10.). When the ATP tree structure is converted, an unconfirmed planned order is created for 20 header materials with component requirements. This planned order has the status "Checked and Confirmed".

If it has been defined that the remaining requirement should be created at header level, and the rules-based ATP check is not being used, this results in the following confirmation at header level:

Result of the ATP check for the header material: Remaining quantity at header level (without rules-based ATP check)

Requirement Date	Requirement Quantity	Confirmed Date	Confirmed Quantity
01.10.	100	01.10	10
		06.10	70

There is an open quantity of 20.

If it has been defined that the remaining requirement should be created at header level, and the rules-based ATP check is being used, this results in a confirmation at header level: The requirement quantity however, is adjusted to 80 (that is, 10+70) as at 01.10. The remaining quantity of 20 for 01.10. is passed on to the following substitution or to the remaining requirement defined for the rules-based ATP check. If no remaining requirement is defined, this quantity expires.

Result of the ATP check for the header material: Remaining requirement at header level (with rules-based ATP check)

Requirement Date	Requirement Quantity	Confirmed Date	Confirmed Quantity
01.10.	80	01.10	10
		06.10	70

Result of the ATP check for substitution header material B (with RBA remaining requirement)

Requirement Date	Requirement Quantity	Confirmed Date	Confirmed Quantity
01.10.	8	01.10	8
01.10.	12	0	0

Result of the ATP check for substitution header material B (without RBA remaining requirement)

Requirement Date	Requirement Quantity	Confirmed Date	Confirmed Quantity
01.10.	8	01.10	8