Skip to Content
author's profile photo Former Member
Former Member

Availablity check with ATP logic

Hi everybody

Can any one tell me where where we assign Checking rule (A - sales order) in availablity check.

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 06:04 AM
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 06:05 AM

    hi srikanth,

    go through the below details.


    Types of Availability Check in Sales and Distribution


    There 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.

    _ 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 stock and inward and outward movement 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.

    _ 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 the

    availability 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 Check

    IMG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.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 05, 2007 at 06:15 AM


    We will asign this to checking group for Av check in img-sd-bf-av check

    htis checking group inturn assigned to MM

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 05, 2007 at 06:28 AM

    dear srikanth

    please gothough this


    To confirm the quantities for a particular line item in the sales order on particular day system carried out transfer of requirements (TOR) & AVAILABILITY check, so has to confirm the quantity on particular day as system should know what are there requirement of the sale order and delivery with MRP then system carries out availability check function, to confirm the quantity on particular day. Depending upon the IMG setting system carries out availability check function based on 3 methods:

    A) Availability Check with ATP logic or against planning:

    In ATP logic systems ATP Qty while carrying out availability check function for

    Particular line item (ATP qty=warehouse stock +planned receipts planned issues)

    Planned Receipts: EX: - purchase requisitions, purchase orders, stock in transfer stock at inspection etc.

    Planned Issues: - EX: - open sales order & open delivers

    B) Availability check against product allocation:

    Availability check can be carried out against product allocations in which system automatically restrict the user to confirm the quantity beyond reserved quantities per particular customer. EX:- Availability qty =100, existing orders=10,then system automatically distributes to items evenly to the sales order.

    C) Rule based Availability check:

    Rule based availability check can be carried out based on the business transaction.

    EX: - For normal sales order system has to carry out availability check for special sales order ex: - cash sales and rush order systems need not to be carry out availability check,

    In rule based availability check system in which system carried out Global availability to promise in all plants. In this check system transfers the requirements to APO system where GATP takes place and the result of the availability check transferred to R/3 system. This process takes place with the transaction code CIF(central inter face) inR/3.After carrying out availability check function system proposes(by using ATP logic) default values of ATP check result to the user in a dialog box, in which system gives the choice to the user to take the decision in contest of insufficient stock.

    a) One time delivery:

    If the user chooses one time delivery and the order Quantity is 100 units system confirms 50 units then systems automatically confirms as a zero. If the user saves the document with the zero confirm qty then system trace the sales order as aback order (V_RA), which can be confirmed later by RESCHEDULLING (V_V2).

    b) Complete Delivery:

    If order Qty=100, Availability stock = 50, system says that remaining can be given after one week. Then if the user selects this option then system push up existing confirmed qty to after one week and the total qty can be confirmed after one week only.

    c) Delivery Proposal:

    If order qty=100, system confirms 50, and remaining 50 can be confirmed after one week. If the user chooses this option then system confirms 50 Qty today allows the user to delivery 50 quantities today remaining 50 can be delivered after one week.


    Define Requirement Class:

    Path: Img  S&D  Basic functions  Availability Check & Transfer of requirements  Transfer of requirements  Define Requirement classes

    Requirement classes control MRP, Requirement consumption, strategy, relevance for planned. It specifics whether the availability check & TOR to be Called out for transactions. Ex: Sales Order

    It determines whether requirements relevant for MRP or not, the allocation indicator from the sales view which controls the settlement of customers requirements with planned independent requirements. It determines the item b to be settled as an availability heck. Assignment, the settlement profiles the results analysis key. The TOR and Availability check functions are globally controlled using the requirement class for all the Sales documents. The values from the Requirements class are transferred to scheduled the of the sales documents class are transferred to scheduled the of the sales document default values and can be over written there.

    Define Requirements Classes:

    Requirement class defines whether the system has to carry out availability check based on the STP Qty. Ex:

    Define Requirement Types:

    Here we define requirement type, Ex: and Assign to Requirement class that we defined in the promote step.

    Determination of Requirement types using Transaction:

    Requirement type is going to be determined for sales document by following a search strategy. .

    First System checks strategy group in MRP3 view if it trend requirement type then system takes from it, otherwise.

    It will go to MRP group in MRP1 view, otherwise

    It will check to Material type, otherwise

    It will go to item Category + MRP type, otherwise

    It will go to Item category only, otherwise

    Finally system determines the transaction b not relevant for TOR & Availability check.

    Choose Item category TAN+MRP type PD=Requirement type =0

    Define Procedure for each schedule the category:

    Here we define respective schedule the category of the sales documents, whether an availability check and TOR should be carried out. This setting is relevant for sales documents only. It is fine tuning of availability check for sales documents TOR & Availability check function can be activated at sales order level those are proposed in to schedule line category level. If u wants to deactivate TOR availability check function at schedule the category level and want to deactivate at requirement class level it b impossible.

    Ex: If u wants to check availability w/o transferring the requirement we can use it.

    Choose schedule line category CP & Activate Availability check, requirement & Product Allocation

    Block Quantity confirmation in delivery Blocks:-

    When we transfer requirements to MRP then confirmed quantities is also reserved for confirmed sales documents, if transaction is blocked for delivery the reserved quantities are also blocked so that the conformed quantities cannot be used by any other purpose. So has to avoid this situation we can block the transfer of requirements(TOR) for delivery blocks, in this case requirements transferred to MRP but will not be reserved, that will be cleared once we save the documents then system shows confirmed qty as zero.

    When we remove the delivery block then system automatically carries out availability check & confirms the qty.

    A) Deliveries: Blocking region for sales Area:

    Here we define blocking regions for TOR ex:-credit limits

    B) Reasons for scope of delivery blocks: TOR. Block:

    Ex: - 01 credit limits-check confirmation block.

    Maintain Requirements for TOR:-

    Here we can define our own requirement with the help of ABAPer for TOR

    Ex: - a) 102- prevent reservation in the event of credit block

    b) 102-purchase requisitions.

    System doesn’t create purchase requisitions for sales order line items if it has a credit limit.

    Availability check:

    Configuration setting:-

    Availability check with ATP logic or against planning:-

    A) Define checking group:

    Checking group defines what kind of requirement record system use to create when sales order & deliveries are processed for this material. We can create 2 kinds of requirements records

    Individual requirement records: that means system creates requirement record for each S&D document.

    Summarized requirement Records: That means system creates requirement records under certain condition in the material master record. There are 2 type of summarized requirement record:

    Summarized requirement records for each day.

    Summarized requirement records for each week

    Define checking Action;

    Here we define 01- daily requirement -B 02- Individual requirements -A

    Where B-total record per day

    A-single record per day

    B) Define material Block for other users:

    When 2 users tries to confirm the quantities for the sales order for same material at a time system will be confused to confirm the quantities both sales orders. So has to avoid this kind of situation we can block the materials from confirming the quantities for 2 users at a check, check block

    C) Define checking group default values:

    Checking group is going to be determined depending upon the material type & plant.

    -Go to new entries, specify material type, ex;-FERT

    & plant = checking group of availability check: 02

    D) Carry out for Availability check:

    Here we define checking rule for the Availability check & allocate them to the checking group. The checking rules specify the scope of the availability check. For a respective transaction, means which planned receipts & planned issues systems has to taken into consideration and also it determines whether system has to take RLT into consideration.

    *Select checking group of availability check-02, checking rule=01

    *Go to details icon, & check which planned receipts & planned issues system has taken into consideration for availability check

    *save it, exit.

    E) Define procedure by Requirement class:

    Here we define requirement class whether on availability check & TOR should be carried out the setting that we carries out at requirement class level they are at global level. There settings automatically copied into define from of requirement class and vice versa.

    *Choose requirement class: 041 & check availability check & TOR (requirement)

    F) Define procedure for each schedule line category:

    Here we carry out fine tuning setting for availability check at schedule line category level. Here we define whether system has to carry out Availability check for particular transaction.

    Ex: - if we want to implement availability check w/o TOR for a particular transaction. According to settings at requirement class level TOR & availability check function activate & those setting will be copied into the schedule time category by default, so that at schedule line category level we deactivated TOR

    G) Determine procedure for each Delivery Item category:

    Here we switch on or switch off availability check functions of a delivery item category

    *choose item category ‘TAN’. & specify the appropriate value.

    H) Checking group for updating back orders:

    Here we assign checking group to a plant that rule specifies for individual application, according to which the availability check is carried out;

    I) Define Default settings:

    Here we define the result of the availability check.

    *Choose your sales Area, & check fixed dates& Qty options & specify ‘D’ or ‘E’

    Where: D- Dialog box in the case of shortages (one time delivery)

    E- Dialog box in the shortages (delivery proposal).

    rewards if it helps


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.