Availability check

[former_member632507]

Dear SAP Guru,

I want to know more information about availability check and how to configure Avalibility check in system.

Points will be given

nikhil

[Former Member]

AVAILABILITY CHECK:

1. Define Checking Groups

Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Checking Groups

You define checking groups with which you specify the type of requirements records the system is to create when processing sales orders or deliveries

2. Define Material Block for Other Users

Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Material Block for Other Users.

3 .Define Checking Groups Default Value

Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Checking Groups Default Value.

4. Carry out Control for Availability Check

Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Carry Out Control for Availability Check.

5. Define Procedure by Requirements Class

Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Procedure by Requirements Class.

6. Define Procedure for Each Schedule Line Category

Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Procedure for Each Schedule Line Category.

7. Determine Procedure for Each Delivery Item Category

Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Determine Procedure for Each Delivery Item Category.

8. Checking Rule for Updating Backorders

Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Checking Rule for Updating Backorders.

9. Define Default Settings

Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Default Settings.

hi

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.

TRANSFER OF REQUIREMENT AND AVAILABILITY CHECK

To confirm the Quantities for a line item in the Sales Order, system tries to understand what kind of Material Type it is?. Depending upon the Material type (FERTS), system proposes General Item Category Group (NORM), together with other 3 factors (TA, NIL, NIL) system determines item category for a line item in the Sales Order, together with MRP type (PD or NIL) system determines Schedule Line Category (CP) if Schedule Line Category CP then SAP can understand that it has to perform transfer of requirements (TOR) Availability Check function based on the “Requirement Type” (041) which points “Requirement Class” (041) where we specify that TOR and Availability Check functions should be carried out globally.

By default these values proposed in Schedule Line Categories where Requirement Type (041) determined.

By following a search strategy system determines requirement type.

Requirement Type signifies what kind of requirements (Sales Order Requirements or Delivery Requirements).

Once the requirements are transferred to MRP then system carries out “Availability Check Functions”. While carries out available check functions system determines ATP Qty following a formula.

ATP Qty = Warehouse Stock + Planned Receipts - Planned Issues.

Availability Check is going to be controlled by taking 2 factors into consideration. That are

a. Checking Group

+

b. Checking Rule

Checking Group determines what king of requirements it has to generate. Eg: Individual Requirement or Summarized Requirements.

Checking Rule specifies Scope of the Availability Check that means what kind of MRP elements ( PR – Purchase Requisition, PO – Purchase Order, Planned Orders, Production Orders, Stock in Transfer, Stock at Inspection, Stock in Transit, Reserves, Safety Stocks, Sales Orders, Deliveries and also RLT (Replenishment) type has to taken into consideration.

If system calculated positive ATP Qty then system confirm the Qty on Requirement Delivery Date by following “Backward Scheduling” or otherwise “Forward Scheduling”. As a delivery schedule system takes material availability date, Loading date, Goods Issue date and Transportation Planning date into consideration.

If system finds Negative QTP Qty then SAP gives 3 options to the user as a “Result of Availability Check”.

a. Online Delivery

b. Complete Delivery

c. Delivery Proposal.

Date: 30.08.2006

Configuration Settings for TOR:

1. Define Requirement Class: Requirement class specifies whether TOR and Availability check carried out transactions whether requirements are relevant for MRP etc.,

Path: IMG

Sales and Distribution

Basic Functions

Availability Check and Transfer of Requirements

Transfer of Requirements

A. Define Requirement Class: Select 041 – Order / Delivery Requirement.

Go to Details icon

Check Availability

Check Transfer of Requirement.

These Requirements are copies to Schedule Line Categories by default. Where we can have fine tuning of Schedule Line Categories with respective TOR and Availability functions. That means depending up on the transaction type. This TOR and Availability Check functions can be de-activated at Schedule Line Category level then system doesn’t carryout TOR and Availability Check functions for that particular transactions. Eg: For Sales Activities.

Note: If TOR and Availability functions de-activated at Schedule Line Category level and they doesn’t effect requirement class as they are copies from requirement class only.

B. Define Requirements Type: Requirement Type identifies different types of requirements. Eg: Sales Order Requirements or Delivery Requirements or Individual Customer Requirement.

Together with Item Category + MRP Type, Requirement Type can be determine for individual transaction in Sales and Distribution.

Requirement Type is Assign to Requirement Class.

Requirement Type is allocated to single requirement class but requirement class can be assigned to several requirement types. Eg: 041 – Requirement Class. Save it and exit.

C. Determination of Requirement Types using Transaction:

To determine Requirement Type system follows a search strategy that is

1. First system checks “Strategy Group” in the Material Master from MRP3 view or else

2. It will go to MRP group from MRP1 view to find out requirement types or else

3. System tries to determine requirement type by using Material type or else

4. It will go to Item Category + MRP Type (This is S & D Assignment) or else

5. System tries to determine requirement type by using item category only or else

6. System assumes that the transaction is not relevant for TOR and Availability Check.

Item Category + MRP Type = Requirement Type.

TAN + PD = 041

TAN + NIL = 041

TAN + ND = 011 – Delivery Requirement

Path: Go to VA01 Overview Screen, Procurement Tab Requirement Type 041.

D. Define Procedure for Each Schedule Line Category: ]

In this step we can determine for respective schedule line categories of Sales Document whether Availability Check and TOR should be carries out or not.

It is only relevant for Sales Document.

It is called find tuning of Availability Check for Sales Documents. That means TOR and Availability Check functions controls can be activated at required class level and they can be de-activated at Schedule Line Categories Level if they are de-activated at requirement class level as they are copied from requirement class level.

Eg: For Sales Activities if the user wants to carry out Availability Check without TOR at Schedule Line Category Level TOD should be de-activated and Availability Check should be activated.

E. Block Qty Confirmation in Delivery Blocks:

Due to Credit Checks if Sales Document is blocked for delivery and while defining schedule line categories if TOR and Availability Check functions are activated then system carries out TOR function and transfer the requirements and reserve the stock. If Sales Document blocked for credit check the reserved stock is going to be block till the Credit Manager takes the decision unless and until the block is removed the blocked stock can not be used by anywhere so that transfer of requirement should be block. In this step we configure the system that system transfers the requirement but stock is not going to be reserve. It can be viewed when save the Sales Order as a confirmed Qty as a Zero.

Once block is removed then system immediately carries out Availability Check and system confirms Qty.

Activity:

a. Deliveries: Blocking Reason / Criteria

Eg: 01 – Credit Limits

Check Confirmation

Check Picking

Check Goods Issue

b. Reason for and Scope of Delivery Blocks: TOR Block:

Eg: 01 – Credit Limits

Check Confirmation Block

F. Maintain Requirements of TOR:

With the help of ABAPers Customers Requirements can be written (VOFM) for Transfer of Requirements. Eg: 102 that prevents reservations the event of Credit Blocks.

G. Maintain Requirements for Purchase and Assembly Orders:

Here with the help of ABAPers requirements can be written. Eg: System should not create purchase requisition or Assembly Order if Credit Limit exceeded.

Eg: Requirement Number 102 - Purchase Requisition

105 – Assembly.

Configuration setting for Availability Check with ATP Logic or against planning.

a. Define Checking Groups:

b.

c. Checking Groups specifies what kind of requirements system has to generate when the material placed in Sales Order or Delivery. That are individual requirements or summarized requirements.

Path: IMG

Sales and Distribution

Basic Functions

Availability Check and Transfer of Requirements

Availability Check with ATP Logic or Against Planning

Define Checking Groups : Here checking Groups 02 – Individual Requirements with total records for Sales Order as a A – Single Order.

Total records for deliveries as a A – Single Orders with blocking Qty requirement. This control blocks the Material which is only in place during AVT Check. It can be set if multiple users wants to access the material table simultaneously so that the user can have clear view about the Availability of the material.

b. Define Material Block for other user:

This indicator allows the users to process in different Sales Orders at a time, then without blocking the Qty for one Sales Order checking group can be set so that system carries out Availability Check for one Material after another Material.

d. Define Checking Groups Default Value:

e.

f. Depending upon the Material type system by default proposes “Checking Group” in the Material Master by default. So that depending upon the Material Type system proposes and creates requirements.

Go to New Entries

Specify Material Type FERT, Plant and Checking Group of Availability Check as a 02 – Individual Requirements. Save it and Exit.

d. Carry out Control for Availability Check:

Availability Check is going to be controlled by Checking Group + Checking Rule. Here checking group (02) assign to Checking Rule (01) select the combination and go to details icon.

e. Define Procedure by Requirements Class:

Requirement Class 041 checked with Availability Check and Transfer of Requirements.

Note: These settings copies from TOR only.

g. Define Procedure for Each Schedule Line Category:

h.

i. Here find tuning settings for Availability Check at Schedule Line Category level can be configured.

Ex: CP – Check Availability Check and Transfer of Requirements.

Note: This configuration settings are copies from TOR configuration settings.

g. Define Procedure for Each Delivery Item Category:

Here Availability Check control define delivery Item Category whether system has to carry out Availability Check or not for Delivery Item.

Choose Item Category TAN and Assign Blank, X or Y.

h. Checking Rule for Updating Back Orders:

When the Document saved with order Qty ZERO then system treats the Order as a back order. Then the back order can be completed by using concept called Re-scheduling. To update the back orders we define Checking Rule at Plant Level. Ex: Choose our Plant and Assign Checking Rule (01) save it and exit.

j. Define Default Settings:

While Carry out Availability Check system determines ATP Qty by following a formula:

ATP Qty = Warehouse Stock + Planned Receipts – Planned Issues

If ATP Qty is positive then system confirms the Qty according to required delivery date.

If ATP Qty is Negative the SAP gives 3 options (in a dialog box) to the user to take decision. That are:

1. One Time Delivery:

In One Time Delivery of Order Qty is 100 Units, Required Delivery Date is Current Date then system confirms Qty after 1 week. If the user uses one time delivery then system confirms Qty as a ZERO then it can be completed by using Back Order Processing.

2. Complete Delivery: If the user chooses this option that is 50 items today, remaining 50 items after 1 week then system confirms full Qty after 1 week. So that Order can be delivered after 1 week.

3. Delivery Proposal: The user chooses this option then 50 confirmed and delivered today and remaining 50 can be delivered after 1 week

Choose Sales Area

Check Fixed Date and Qty and Assign Rule for Transferring the Result of the Availability Check. Ex: E – Dialog Box in the case of Shortages (Delivery Proposal) save it and exit.

Note: Create one Material and raise the Sales Order without initiating the stock and check the effect.

Check Fixed Date and Qty:

This indicator signifies that the Customer concerned to accept system confirmed order qty date.

Date: 07.09.2006

Edited by: MANI ROOPA SD/MM on Apr 14, 2008 6:37 AM

[Former Member]

Hi Nikhil,

ATP

Types of Availability Check in Sales and Distribution

Processing

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.

Prerequisites

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.

TOR

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.

Regards,

Sasikanth.Ch