Transfer of Requirements and Availability check

Table of Contents

TRANSFER OF REQUIREMENTS AND AVAILABILITY CHECK.......................................................2

CONFIGURATION SETTINGS FOR TOR........................................................................................... 4

2.1. DEFINE REQUIREMENTS CLASSES:..............................................................................4

Transfer of Requirements and Availability check

2.2. DEFINE REQUIREMENTS TYPES..................................................................................4

2.3. DETERMINATION OF REQUIREMENTS TYPES USING TRANSACTIONS...........................................5
2.4. DEFINE PROCEDURE FOR EACH SCHEDULE LINE CATEGORY...................................................6
2.5. BLOCK QUANTITY CONFIRMATION IN DELIVERY BLOCKS......................................................8
2.6. MAINTAIN REQUIREMENTS FOR TRANSFER OF REQUIREMENTS:..............................................9
2.7. MAINTAIN REQUIREMENTS FOR PURCHASE AND ASSEMBLY ORDERS:.......................................10

CONFIGURATION SETTINGS FOR AVAILABILITY CHECK...........................................................11

Transfer of Requirements and Availability check

3.1. DEFINE

CHECKING GROUPS:....................................................................................12

3.2. DEFINE MATERIAL BLOCK FOR OTHER USERS................................................................13

3.3. CARRYOUT

CONTROL FOR AVAILABILITY CHECK:............................................................13

3.4. DEFINE PROCEDURE BY REQUIREMENTS CLASS:.............................................................15

3.5. DEFINE

PROCEDURE FOR EACH SCHEDULE LINE.............................................................16

3.6. DETERMINE PROCEDURE FOR EACH DELIVERY ITEM CATEGORY............................................16

3.7. CHECKING RULE FOR UPDATING BACK ORDERS..............................................................17
3.8. DEFINE DEFAULT SETTINGS...................................................................................17

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Transfer of Requirements [SD + MM + PP]: As the end user specifies the customer material number in the
sales order system has to confirm the quantity in a particular day. So, as to confirm the quantity on a particular
day (customer requested delivery date) system should know the requirements of the particular material for
sales order or delivery.
System can get the requirements of the order/delivery of a material by a function called Transfer of
Requirements (TOR).

Transfer of Requirements and Availability check

TOR carries out requirements of order to MRP and creates a demand. Once TOR creates a demand with MRP,
then system can carryout availability check for particular material for particular order? During carrying out the
availability check function system tries to determine ATP (Available to Promise) quantity.
System calculates ATP quantity by taking Warehouse stock plus planned receipts minus planned issues.
ATP quantity = Warehouse stock + planned receipts Planned issues.
Planned receipts: Planned orders, Production orders, Purchase requisitions, Purchase orders, Stock in transfer,
Stock in transit, Stock at inspection, etc.

Transfer of Requirements and Availability check

Planned issues: Sales orders, Deliveries, etc.

System creates a demand with MRP by requirement type 041.
Path to see the requirement type is sales order overview screen (VA01)
type 041.

Procurement tab

At the same line system shows ATP quantity also.

The requirement type points to requirement class that defines requirement class:

Requirement

Transfer of Requirements and Availability check

Whether availability check is carried out for a transaction,

Whether the requirement is relevant for MRP,
The allocation indicator from the sales view, which controls the settlement of the customer
requirements with a planned independent requirement,
Whether the item is to be settled to an auxiliary account assignment, the settlement profile, and the
result analysis key

Transfer of Requirements and Availability check

NOTE: The TOR and Availability check are controlled globally using the requirement class for all sales
documents. Depending upon the transaction we can deactivate these functions in the schedule line category of
sales document.
Ex: For inquiry and quotation system need not to carryout TOR and availability check functions. So that we
can deactivate these two controls in the definition of the schedule line category, as these controls directly
proposed from the requirement class into schedule line category.

Transfer of Requirements and Availability check

Requirement type: Requirement type is going to be determining by item category + MRP type as a one of the
factor.
Ex: Requirement type = Item category group + MRP type
041 = TAN + PD
System determines requirement type by following a search strategy like below:
(1) It first searches the strategy group from MRP3 view in material master.
(2) If strategy group has not been maintained, then it will go to the MRP group in the MRP1 view of
material master.

Transfer of Requirements and Availability check

(3) If MRP group has not been maintained system uses material type instead of MR group (Ex:
Finished product, etc).
(4) If no requirement type is found here, then the system assumes a special rule that is Item category
and MRP type.
(5) If this is not possible, then system tries to find out the requirements only with item category.
(6) Finally system assumes that this transaction is not relevant for TOR and availability check.

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Configuration settings for TOR

2.1.Define Requirements Classes:
Transaction code: OVZG
Path:
IMG
Sales and Distribution

Transfer of Requirements and Availability check

Basic functions
Availability check and Transfer of Requirements
Transfer of Requirements
Define requirements classes
Choose standard requirement class 041from position button
Select it and click on details icon
Check
o Availability
o Requirement transfer

Transfer of Requirements and Availability check

o Product allocation

Transfer of Requirements and Availability check

Save and Exit

NOTE: These values will be proposed into definition of the schedule line category.

2.2.Define Requirements Types

Transaction code: OVZH
Path:

Transfer of Requirements and Availability check

IMG
Sales and Distribution
Basic functions
Availability check and Transfer of Requirements
Transfer of requirements
Define requirements types
Choose requirement type 041 from position button
Assign our requirement class

Transfer of Requirements and Availability check

Save and Exit

Transfer of Requirements and Availability check

2.3.Determination of requirements types using transactions

Path:

IMG
Sales and Distribution
Basic functions
Availability check and Transfer of Requirements
Transfer of requirements

Transfer of Requirements and Availability check

Determination of requirement types using transaction

Choose item category TAN and MRP type PD

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Save and Exit

2.4.Define procedure for each schedule line category

Transfer of Requirements and Availability check

Here we specify for the respective schedule line categories of the sales documents whether an availability
check and TOR functions should be carried out or not
It offers a fine-tuning to TOR and availability check functions at schedule line category level.
We can only deactivate an option that we selected in the requirement class level. But we cannot activate it.
Ex: We activated TOR and availability check functions in the requirement class level, and we can deactivate at
schedule line category level. But this deactivation will not affect the requirement class.

Transfer of Requirements and Availability check

NOTE: If we do not activate these functions in the requirements class level and you tried to activate in the
schedule line category, then system would not accept it (if will not effect).
Use: If we want to implement availability check function without TOR function at requirement class level,
TOR and availability check functions should be activated and TOR function should be deactivated at schedule
line category level

Path:

Transfer of Requirements and Availability check

IMG
Sales and Distribution
Basic functions
Availability check and Transfer of Requirements
Transfer of requirements
Define procedure for each schedule line category

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

2.5.Block quantity confirmation in delivery blocks

Path:

IMG
Sales and Distribution
Basic functions
Availability check and Transfer of Requirements
Transfer of requirements
Block quantity confirmation in delivery blocks

Transfer of Requirements and Availability check

Deliveries: Blocking reasons/Criteria

When requirements transferred to MRP, the confirmed quantity is also reserved for confirmed sales documents.
If the transactions are blocked for delivery the required stock will be blocked. So it cannot be used elsewhere in
the system. To prevent this, we can block the TORs for delivery block in this step.

Transfer of Requirements and Availability check

In this case the order quantity will still be transferred to MRP as a requirement. But it will not be reserved. We
can see this one by going to change mode of the sales document in the schedule lines that specifies zero (0) or
confirmed quantity.
When the block is removed the availability check is automatically carried out by the system, and also we may
push back the material staging date by number of days.
NOTE: We can carryout availability check at anytime in spite of these blocks if transaction permits. Then
system creates a temporary schedule lines with confirmed quantities, which are then removed when the
document is saved.

Transfer of Requirements and Availability check

Choose blocking reasons/Criteria from position button

Ex: 01 = Credit limits
Check
o Confirmation block
o Picking block
o Goods issue block

Transfer of Requirements and Availability check

Save and Exit

Transfer of Requirements and Availability check

2.6.Maintain requirements for Transfer of Requirements:

Here we can maintain our own requirements for TOR

Transaction code: OVB8

Path:
IMG
Sales and Distribution

Transfer of Requirements and Availability check

Basic functions
Availability check and Transfer of Requirements
Transfer of Requirements
Maintain requirements for Transfer of requirements
Ex: Requirement 102 That prevents reservations from being created in the event of a credit
block
Save and Exit

Transfer of Requirements and Availability check

2.7.Maintain requirements for purchase and assembly orders:

Transaction code: OVB5
Path:
IMG
Sales and Distribution
Basic functions

Transfer of Requirements and Availability check

Availability check and Transfer or Requirements

Transfer of Requirements
Maintain requirements for purchase and assembly orders
Ex: 102 = Purchase requisition
105 = Assembly
106 = Block construction

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Save and Exit

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Configuration settings for Availability check

In SAP availability check can be carried out in the 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.

SD settings:
(1) Define requirement class:
(2) Define checking group:

Transfer of Requirements and Availability check

That determines standard Replenishment Lead Time (RLT) [together with MRP group], and the type of
requirement records.
Ex: Individual records or summarized records to be created.
(3) Define checking rule: It determines the scope of the availability check and whether or not RLT should be
taken into consideration.
Material master record specifications: We should specify the below settings to carryout availability check and
TOR.
(1) Checking group: (Sales/Plant data view or MRP2)

Transfer of Requirements and Availability check

(2) MRP group: (in MRP1 view) system uses this group to determine requirement type relevant for
transaction.
(3) Strategy group: It will be used as an alternative to MRP group.
Availability check can be carried out by:
(1) With ATP logic or against planning:

Transfer of Requirements and Availability check

(2) Against product allocation: It will be used, when the shortage of the supply of the material. During sales
order processing an availability check can be carried out against product allocations. The result of this check
informs whether an order requirement can be confirmed according to product quantity allocated to customer.
(3) Rules based availability check: With this check we can carryout availability check in several plants and
with several alternative materials. It will be useful in the APO (Advanced Planner and Optimizer).

Transfer of Requirements and Availability check

3.1.Define checking groups:

Transaction code: OVZ2
Path:

Transfer of Requirements and Availability check

IMG
Sales and Distribution
Basic functions
Availability check and Transfer of Requirements
Availability check
Availability check with ATP logic or against planning
Define checking groups
Define checking groups by which we specify the type of requirements that system has to create
during sales order or delivery document processing

Transfer of Requirements and Availability check

Requirements can be individual requirements or summarized requirements

Individual requirements are created for each sales document
Summarized requirements are a group of requirements for a particular material. Summarized
requirements are again two types:
(1) Summarized requirements per each day.
(2) Summarized requirements per each week.

Transfer of Requirements and Availability check

System gives the message for blocked requirement for the user.

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Save and Exit

3.2.Define material block for other users

Path:

Transfer of Requirements and Availability check

IMG
Sales and Distribution
Basic functions
Availability check and Transfer of Requirements
Availability check
Availability check with ATP logic or against planning
Define material block for other users.

Here we defined each checking group and initiator.

Transfer of Requirements and Availability check

Whether the material master record should be blocked for other orders 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]
Block

Transfer of Requirements and Availability check

Save and Exit

Transfer of Requirements and Availability check

3.3.Carryout control for availability check:

Transaction code: OVZ9
Path:
IMG
Sales and Distribution
Basic functions

Transfer of Requirements and Availability check

Availability check and Transfer or Requirements

Availability check
Availability check with ATP logic or against planning
Carryout control for availability check

We define the checking rules for availability check and allocate them to the checking group.

Transfer of Requirements and Availability check

The checking rule specifies the scope of the availability check for the respective transactions in SD by which
we can tell to the system, which kind of planned receipts and planned issues we should take into account
during availability check.
Every checking rule allocated to checking group. These two elements control the availability check.
Ex: Checking group 02 = Individual requirement.
Checking rule 01

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Save and Exit

3.4.Define procedure by requirements class:

Transaction code: OVZ0
Path:

Transfer of Requirements and Availability check

IMG
Sales and Distribution
Basic functions
Availability check and Transfer of Requirements
Availability check
Availability check with ATP logic or against planning
Define procedure by requirements class

Transfer of Requirements and Availability check

The settings that we see in this step copied from globally specified settings that are (TOR) transfer of
Requirements.
Ex: 041 check
Availability check
TOR
Product allocation

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Save and Exit

Transfer of Requirements and Availability check

3.5.Define procedure for each schedule line

Path:

IMG
Sales and Distribution
Basic function
Availability check and Transfer of Requirements
Availability check

Transfer of Requirements and Availability check

Availability check with ATP logic or against planning

Define procedure for each schedule line category
These settings also proposed from TOR only.

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Save and Exit

3.6.Determine procedure for each delivery item category

In this step we can Switch on or Switch off the availability check for particular items in the delivery.
Ex: For return orders we should switch off.

Path:

Transfer of Requirements and Availability check

IMG
Sales and Distribution
Basic functions
Availability check and Transfer of Requirements
Availability check
Availability check with ATP logic or against planning
Determine procedure for each delivery item category
Leave Avail check off blank

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

Save and Exit

3.7.Checking rule for updating back orders

Path

IMG
Sales and Distribution
Basic functions
Availability check and Transfer of Requirements

Transfer of Requirements and Availability check

Availability check
Availability check with ATP logic or against planning
Checking rule for updating back orders
We assign a checking rule to a plant. The checking rule that we entered here is used in the production planning.
During back order processing (CO06) and the availability overview (CO09) we should make sure that we are
not using any checking rules that deviate from the SD configurations.
Checking rule A for orders, and B for deliveries

Transfer of Requirements and Availability check

Save and Exit

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

Transfer of Requirements and Availability check

Path

IMG
Sales and Distribution
Basic functions
Availability check and Transfer of Requirements
Availability check
Availability check with ATP logic or against planning
Define default settings

Transfer of Requirements and Availability check

(A)

Fixed date and quantity: We specify for a sales area whether the delivery dates and quantities
confirmed after availability check should be set.
(B) Rules for transferring the availability results: Here we can specify the system response to shortage
for a sales area.
Ex: One time delivery or full delivery in the dialog box.
Choose our sales area
Fixed date and quantity
Specify the system responses in the case of the shortage of the material in availability checking rule [D]
= Dialog box for delivery (one time delivery).

Transfer of Requirements and Availability check

Transfer of Requirements and Availability check

When we have insufficient stock (Ex: 100 quantity in the storage location) and the system response is D (one
time delivery) and order quantity in VA01 is 200. Then system confirms only 100.
Save and Exit