TRANSFER OF REQUIREMENTS AND AVILABILITY CHECK

Its integration between MM, PP, and SD as the end user specifies the customer material number
in sales order system has to confirm the quantity in a particular day. So as to confirm the
quantity on a particular day. So system should know the requirement of the material and
delivery date.

During availability check function system tries to determine ATP (availability to promise)
quantity

ATP quantity= warehouse stock + planned receipts planned issues

Path to see the requirement type in sale order overview screen (VA01) procurement
tabrequirement type 041

At the same line system shows ATP quantity also

NOTE: TOR and availability check are controlled globally using the requirement class for all sales
documents. Depending upon transaction we can deactivate this function in the schedule line
category of sales document.

System determines requirement types by following a search strategy likes below

It first search the strategy group from MRP3 views in material master
If it has not been maintained then it will go to the MRP group in the MRP1 view of the
material
If the group has not been maintained system uses material type instead of MR group
If no requirement type is found her then the system assumes a special rule that is item
category and MRP type
If this not possible then system tries to find out the requirements only with in the item
category
Finally system assumes that this transaction is not relevant for TOR and availability
check.

Define requirement class [OVZG]

1. Path: IMG S & D B & F Availability check and transfer of requirement Transfer of
requirement Define requirement class choose standard requirement class 041 from
position button Select it and click on details icon Check
Availability
Requirement transfer
Product allocation
Save and Exit

Note: These values will be proposed in to definition of the schedule line category

Define requirements types [OVZH]

Path: IMG S & D B & FAvailability check & TORTOR Define requirements
typeschoose requirement type 041 from position buttonassign our requirement class

Save & Exit

Determination of requirements types using transaction

Path: IMG S & DB & F Availability check and TORTOR Determination of requirement
types using transition Choose item category TAN and MRP type PD and assign requirement
type 041.
Save & Exit

Define procedure for each schedule line category

Path: IMG S & D B & F Availability check and TORTOR Define procedure for each
schedule line category

Choose the schedule line category CP from the position button check availability check
TOR check Production allocation Save & Exit

Block quantity configuration in delivery blocks

Path: IMG S & DB & F Availability check and TORTOR Block quantity confirmation in
delivery blocks Deliveries: Blocking reasons/criteria
Choose blocking reasons/criteria from position button check confirmation block, picking
block, goods issue block for our credit limit Save & Exit

Maintain requirements for transfer of requirements [OVB8]

Here we can maintain our own requirements for TOR

Path: IMG S & D B & F availability check and TOR TOR Maintain requirements for
transfer of requirements

Requirement 102- that prevents reservations from being created in the event of a credit block

Save & Exit

Maintain requirements for purchase and assembly orders [OVB5]

Path: IMG S & D B & F availability check and TORTOR Maintain requirements for
purchase and assembly orders

Save & Exit

Availability check

In SAP availability check can be carried out in sales orders and deliveries for an item, and also it
creates MRP records and passes them into materials requirement planning.

Availability check is carried out at plant level.

Availability check can be carried out by:

1. With ATP logic or against planning

2. Against product allocation
3. Rules based availability check

Define checking group [OVZ2]

Path: IMG S & D B & F Availability check and TOR Availability check availability check
with ATP logic or against planning Define checking groups define checking group by which
we specify the type of requirements that system has to create during sales order or delivery
document processing Requirement can be individual requirements or summarized
requirements individual requirements are created for each sales document

Save & Exit

Define material block for other users

Path: IMG S & D B & F Availability check and TOR Availability check Availability check
with ATP logic or against planningDefine material block for other users.
Here we define checking group and initiator.

Whether the material master record should be blocked for other order during availability
check
If it is blocked we cannot create two orders for the same material at the same time
specify 02 = individual requirements initiator [A], check block
Save & Exit

Define checking groups default values

Path: IMG S & D B & F Availability check and TOR Availability check Availability check
with ATP logic or against planningDefine checking groups default values

In this step we define the checking group that the system proposes when a new material master
record. The default values depend on the material type and plant.

Specify material type EX: FERT, plant and requirement type (02) or (01)
Save & Exit
Carry out control for availability check [OVZ0]

Path: IMG S & D B & F Availability check and TORAvailability check Availability check
with ATP logic or against planningDefine procedure by requirement class

Check for availability check, TOR, Product allocation

Save & Exit

Define procedure for each schedule line

Path: IMG S & D B & F Availability check & TOR Availability checkAvailability check
with ATP logic or against planningDefine procedure for each schedule line category

This process also proposed from TOR only

Save & Exit

Determine procedure for each delivery item category

In this step we can switch on/ off the availability check for particular item in delivery

Path: IMG S & D B & F Availability check & TORAvailability check Availability check
with ATP logic or against planning Determine procedure for each delivery item category

Save & Exit

Checking rule for updating back order

Path: IMGS & DB & FAvailability check & TORavailability check Availability check
with ATP logic or against planningchecking rules for updating back order

Here we need to assign our plant to checking rule [A] SD order

Checking rule A for order & B for delivery

Save & Exit
Define default settings

In this step we can propose the result of the availability check and we can set the indicator for
fixing the date quantity and rules.

Path: IMG S & D B & F Availability check and TOR Availability checkAvailability check
with ATP logic or against planning Define default settings

Here in this step we need to specify our sales organization and check fixed date and quantity
and Availability checking rule

Save & Exit

Now raise the order using VA01 and check TOR and availability check is working or not