The document discusses the transfer of requirements (TOR) process in SAP. TOR transfers the requirements from a sales order to materials requirements planning (MRP). This allows MRP to plan for meeting the demand created by the sales order. The key steps are: 1) TOR creates a demand in MRP from the sales order requirements. 2) MRP then checks availability by comparing warehouse stock, planned receipts and planned issues. 3) Configuration is required to define requirement classes and types to determine how requirements are transferred to MRP. 4) Schedule line categories and delivery blocks must also be configured to control the TOR process.

1. TRANSFER OF REQUIREMENTS
By Srinivasulu Algaskhanpet (Sr. SAP SD Consultant) Page 1
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 in 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 carries out requirements of order to MRP and creates a demand. Once TOR creates a
demand with MRP, then system can carry out availability check for particular material for
particular order. During carrying out the availability check function system tries to determine
ATP quantity.
ATP quantity = Warehouse stock + Planned receipts - Planned issues
Planned receipts: Planned orders, production orders, purchase requisitions, purchase orders,
stock in transfer, stock in transit etc.,
Planned Issues: Sales orders, deliveries etc.,
Pre-Requisites for TOR:
1. In Schedule line category
Check availability and requirement

2. TRANSFER OF REQUIREMENTS
By Srinivasulu Algaskhanpet (Sr. SAP SD Consultant) Page 2
2. In Material Master under sales general/plant data maintain availability check or
checking group.
3. Requirement type should be determined into sales document. The criteria to determine
requirement type in sales document is:
I. Strategy Group II. MRP Group III. Item category + MRP Type
4. In requirement class
Check availability and requirement

3. TRANSFER OF REQUIREMENTS
By Srinivasulu Algaskhanpet (Sr. SAP SD Consultant) Page 3
Configuration steps for TOR:
1. Define Requirement Classes:
Path: SPRO > S&D > Basic functions > Availability check and Transfer of Requirement >
Transfer of Requirements > Define Requirement Classes
Requirement Class is the controlling factor for the availability check and transfer of
requirement.
Requirement class actually controls whether to pass sales order requirement to MRP or not.
It also controls whether to pass the requirement as normal stock or special stock.
011 - Delivery requirement KEB - IPO
041 - Order/Delivery requirement 040 - Make to order

4. TRANSFER OF REQUIREMENTS
By Srinivasulu Algaskhanpet (Sr. SAP SD Consultant) Page 4
2. Define Requirement Type:
Path: SPRO > S&D > Basic functions > Availability check and Transfer of Requirement >
Transfer of Requirements > Define Requirement Types
The purpose of requirement type is it helps to determine requirement class into sales
document.
A requirement type is assigned to a single requirement class., however, a requirement class
may be assigned to more than one requirement type.
The requirement type is displayed in sales order.
The standard requirement types are:
011 - Delivery requirement
041 - Order/Del. requirement
KE - Make to order
KEB – IPO
3. Determination of requirement types using transaction:
Here we assign MRP type "PD" to our item category "TANS"
TANS + PD = 041

5. TRANSFER OF REQUIREMENTS
By Srinivasulu Algaskhanpet (Sr. SAP SD Consultant) Page 5
Note: In origin of requirement (Q) if we assign "1" then system will give first preference to
"Item cat group + MRP Type" while determining requirement type in to sales document.
4. Define procedure for each schedule line category:
Path: SPRO > S&D > Basic functions > Availability check and Transfer of Requirement >
Transfer of Requirements > Define procedure for each schedule line category
In this configuration step check availability and requirement in schedule line category.
5. Block quantity confirmation in delivery blocks:
Path: SPRO > S&D > Basic functions > Availability check and Transfer of Requirement >
Transfer of Requirements >Block quantity confirmation in delivery blocks
In this step we can block quantity confirmation for delivery.
6. Maintain requirements for TOR:
Path: SPRO > S&D > Basic functions > Availability check and Transfer of Requirement >
Transfer of Requirements >Maintain requirements for TOR
Q. Client requirement is if sales order is blocked for credit, he wants to block the confirmations?
Where is the control?

6. TRANSFER OF REQUIREMENTS
By Srinivasulu Algaskhanpet (Sr. SAP SD Consultant) Page 6
A. Routine no: 101
7. Maintain requirements for purchase and assembly order:
Q. In third party and IPO process if order is blocked for credit, system should not generate
purchase requisition?
A. In TOR Routine no: 102
Exercise:
Create Order and check whether system is determining requirement type into sales document
or not.
We can see the requirement type under procurement tab.