TOR and availability check

[Former Member]

Hi,

I am getting confused while understanding the Configurations for TOR and availability check. Can anyone help me by forwarding the relevent configuration guides to my email i.e evikrantvij@gmail.com

Thanks in advance,

Vikrant

[Former Member]

email sent.

Regards,

Rajesh Banka

Reward suitable points.

[Former Member]

HI Vikrant,

TOR:

The MRP department is informed about the quantities and deadlines by which incoming orders

should be delivered. The system checks the availability of the goods based on the requested

delivery date of the customer and creates MRP records which contain all necessary information

for passing on to planning. It ensures that the goods are available in time for the delivery.

Materials planning transfers the reported requirements and creates orders or purchase

requisitions from them etc.

For controlling transfer of requirements, you have to carry out the following steps:

1. Each requirement type has to be allocated to one requirement class only.

2. The transfer of requirements must be switched on at requirements class level, the sales

documents at schedule line level.

3. You must define a check group. It is possible to have this check group proposed for the

initial creation of a material master record.

4. Note that a plant must exist for transfer of requirements to be carried out at document

item level.

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.

Reward points if it helps

Regards

Srini

[Former Member]

HI

SENT MAIL REWARD IF HELPS

[Former Member]

<b>ATP</b>

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:

_ <b>Checking group</b>

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.

_ <b>Checking Rule</b>

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.

_ <b>Schedule line category</b>

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.

_ <b>Delivery item category</b>

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

place in deliveries.

<b>Requirements type</b>

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

type refers to the requirements class and its control features.

_ <b>Requirements Class</b>

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.

<b>Prerequisites</b>

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

<b>Configuring entries of the Availability Check</b>

IMG&#61664;SD&#61664;Basic fncs&#61664;Availability check and TOR&#61664;Availability check&#61664;Availability check with ATP logic or against planning&#61664;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.

<b>Defining a material block for other users</b>. 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.

<b>Defining the default value for checking groups</b>. 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.

<b>Controlling the availability check</b>. 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.

<b>TOR</b>

IMG &#61664; SD &#61664; Basic fncs &#61664; Availability check and TOR &#61664; 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&#61664;sales/plant view).

<b>The TOR is dependent on the following data</b>:

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

The reqts type and class are determined in the strategy group (material master&#61664;MRP3)

<b>For TOR to be carried out, a few criteria need to be met</b>:

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.

<b>Configuring the TOR</b>:

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 &#61664; order qty, sd doc no, item no, requirements class.

Stock requirements list = MD04 &#61664; sd no or dly no, line item, schedule line placing the demand

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

Regards,

Rajesh Banka

Reward suitable points.

[Former Member]

mail sent , check your mail.

Reward points if helpful.

Regards

AK