BF-Transfer of Requirement

Transfer of Requirement:
Transfer of required quantity and dates of a sales document to materials planning department.

Types of TOR :
TOR with individual requirement – Requirement based on each schedule line in sales order is transferred.
TOR with collective requirement – combine several requirement based on daily or weekly.
Collective requirement can be transferred according to following criteria:
- Plant, Batch, Storage Location, Date, Transaction, Requirement class.

The system creates individual requirement for special stocks even if collective requirement is specified.

Controlling element of TOR and Availability check:
Requirement class: the transfer of requirement must be switched on at requirement class level.
Requirement Type: the requirement type must exist which should determine requirement class.
Plant: A Plant must be defined at item level in sales order.
Checking Group: A checking group must be defined in the material master record. (Ex. 01 coll. Req. 02 Ind. Req.)
Schedule line Category: the TOR must be switched on at schedule line level.

Stock Requirement Display – MD04
It displays requirement of orders, schedule line its.
Availability Overview: CO09

Configuration:
- Define Requirement Class
- Define Requirement Type – just assign Req. type to Req. class.
- Determination of requirement types using transaction – how the req. type is determined in the document. “Item category + MRP type = Req. Type”
- Define procedure for each schedule line. Activate TOR and avail check for Schl. Line.(check box)
- Block quantity confirmation in delivery blocks – in delivery blocks we can blocks delivery creation for a different blocking reason. Means we can sale the sales order but can not create delivery unless we remove the delivery block. However it does not block the TOR and qty confirmation, but in certain block like due to Credit problem, we need to block the TOR and qty confirmation also so that quantity should not be confirmed for the sales order. That we define here for every reason whether we want to block the TOR also i.e. qty confirmation. In addition to that you can define the Days up to which you want to block the qty confirmation. Suppose it takes 10 days for you to clear the matter of customer credit problem, that you can put 10 days as difference period and after 10 days it will automatically transfer the requirement and will confirm the qty.

Standard req. class:
011 – Delivery Req.
030 – Sales from stock
031 – Order requirement
039 – Service Item
040 – Make to order
041 – order/deli. Req.

How the Requirement type is determined in Documents:
1. First, an attempt is made to find a requirements type using the strategy group in the material master.
2. If the strategy group has not been maintained, the system will determine it using the MRP group.
3. If the MRP group has not been defined, the system uses the material type instead of the MRP group when accessing the corresponding control tables.
4. If no requirements type is found here, the system assumes a special rule and attempts to find a requirements type with the aid of the item category and the MRP type.
5. If this is not possible, a last attempt is made to find a requirements type with the item category only.
6. If the last attempt fails, the system declares the transaction as not relevant for the availability check or transfer of requirements

Based on Requirement Type, system defines Requirement class.