Availability Check (ATP) & Transfer of Requirement (TOR)


Types of Availability Check in Sales and Distribution

ProcessingThere are three types of availability check:
_ Check on the basis of the ATP quantities
_ Check against product allocation
_ Check against planning
The following SD-specific control features need to be maintained in Customizing:

_ Checking group

The checking group controls whether the system is to create individual or collective

requirements in sales and shipping processing. In addition, a material block for the

availability check with transfer of requirements can be set here. The checking group can

also be used to deactivate the availability check. This option was created especially for

the assembly order so that when the bill of material is exploded in the assembly order,

the individual components, if necessary, can be classified as non-critical parts as far as

procurement is concerned.

The checking group specifies in combination with the checking rule the scope of the

availability check. It is proposed in the material master record on the basis of the material

type and the plant, and copied into the sales and distribution documents.  It is specified in MMR in MRP3 screen, availability check tab.

_ Checking Rule

You use the checking rule to control the scope of the availability check for each

transaction in sales and distribution. You also specify whether the check should be

carried out including or excluding replenishment lead time. The individual checking rules

define by transaction, which kinds of stocks and inward – outward movement(receipts and issues) of goods should

be taken into account for the availability check.

_ Schedule line category

You can control with the schedule line category whether an availability check and

transfer of requirements should be carried out in the sales documents. The possible

settings for this at schedule line level are dependent on the settings in the requirements

class which is determined from the requirements type of the material.

_ Delivery item category

The delivery item category can be used to control whether an availability check takes

place in deliveries.

Requirements type

The various requirements are identified by their requirements type. The requirements

type refers to the requirements class and its control features. it is assigned to requirement class.

_ Requirements Class

The requirements class contains all control features for planning such as relevance for

planning, requirements planning strategy and requirements consumption strategy. In

addition, it is specified at a global level whether an availability check is to take place for

the material in the sales and distribution documents on the basis of the ATP quantity

(ATP = available to promise) and whether requirements are to be passed on. A finer

degree of control can be obtained for sales documents using the schedule line category.

 Replenishment lead time is only included in the check performed on the basis of the
ATP quantity.

An availability check can only be carried out if the following prerequisites have been fulfilled:

_ The control elements described above for the availability check must be maintained in

Customizing for Sales and the relevant assignments made to the sales transactions

_ The availability check must be switched on at requirements class level and – for theavailability check in the sales documents – at schedule line category level

A requirements type must exist by which the requirements class can be found

_ A plant must be defined. It can either be proposed from the customer or material master

record or can be entered manually in the document._ A checking group must be defined in the material master record on the Sales/plant data

screen in the Availability check field  
Configuring entries of the Availability CheckIMGàSDàBasic fncsàAvailability check and TORàAvailability checkàAvailability check with ATP logic or against planningàDefine checking groups

You can use SAP std checking groups of 01 for summarized reqts or 02 for daily reqts or u can create ur own.

The columns total sales and total deliveries are selection options whereby u can configure a checking rule to sum up reqts to post to MRP either individually or by day or week.

Column 5, Block qty; set this block if u want several users to be able to process the material simultaneously in different transactions without blocking each other. The No Check indicator is used when u want a material to not be relevant for an ATP check.

Defining a material block for other users. The Block checkbox is an indicator that enables u to block the particular material from being checked for availability if it is already being checked at the same time by another user.Defining the default value for checking groups. However should no entry exist for the checking group in the material master record, one can set a default value per material type and plant.
Controlling the availability check. In this section, u tell the system what stock on hand and what inward and outward movements of stock it must take into account when performing the availability check. These settings are based on the checking group that is assigned to the material master record and the checking rule that is predefined and assigned to the sd transaction. The carry out control for the availability check must be maintained for both the sales order and delivery.


IMG à SD à Basic fncs à Availability check and TOR à TOR

A line item in the sales order creates a schedule line. The schedule lines in the sales order transfer the requirements through to MRP. You can select the docs on which you want the TOR to happen. For ex, not for quotations.

The TOR aims to ensure the ordered materials are available for the requested delivery date. The TOR can be set for individual or for collective requirements (materials masteràsales/plant view).

  The TOR is dependent on the following data:

The reqts type, reqts class, checking group and schedule line category.

The reqts type and class are determined in the strategy group (material masteràMRP3)

 For TOR to be carried out, a few criteria need to be met:

Plant assigned to line item level, schedule line category should be switched on at TOR, TOR must be switched on at the reqts class level, checking group must be defined and allocated to the material master record (sales/plant view in the availability check field)  
The reqts class is the controlling factor for the availability check and the TOR for all sd types. 
Configuring the TOR:

1)      Use std 041 reqts class or copy and rename it. Use the indicators to select if this reqts class must carry out an availability check and/or a TOR.

2)      Define the reqts types. A reqts type is allocated to a single reqts class and not vice versa. It is based on the item category and the MRP type of the material.

3)      Assign the rqts type to the relevant item category in the sales order and the MRP type found on the material master record.

You can select an alternative search strategy where u assign the reqts type to item category and MRP type. Can select source as 0, 1 or 2. (1 = Item type and MRP type strategy).

4)      The TOR and Availability check can be selected/de-selected at the schedule line category level.

5)      Block qty confirmation in delivery blocks. This is used to block the reservation of the TOR from MRP.

6)      Maintain requirements for TOR. Requirements can be used to determine that the TOR to MRP is not carried out unless a number of conditions are met. 
Availability Overview = CO09 à order qty, sd doc no, item no, requirements class.

Stock requirements list = MD04 à sd no or dly no, line item, schedule line placing the demand

Stock overview = MMBE à total stock per company, then plant followed by storage location, and finally a breakdown per batch.

6 thoughts on “Availability Check (ATP) & Transfer of Requirement (TOR)”

  1. Hi all,

    Availability check refers to the confirmation towards customer. In order to do that availability check, we need to send the customer’s requirement (requested delivery date and quantity) to PP&MM. Here in TOR, Requirement means the customer’s requirement. Hense transferring the customer’s requirement to PP&MM, in order to do the availability check.

    Thanks & Regards

  2. Availability check is a process where the system checks if the material would be available on the customer requested quantity on the requested date.

    TOR is transfer of requirement, which is a process where the information about the customer requested quantity is transferred to MRP. Typically, TOR happens before Availability Check.


  3. presentation of topicstepwise is good. as fas as the availlability concept is concerned it is good. iam yet to go through other topics. pls. let me know have you covered EDI-idoc earlier. if so how can i see those topics. kindly do the needful. Thank you.

Leave a Comment