Transfer of Requirements configuration in SD
Transfer of Requirement
- Types of Transfer of Requirements
- Control of Transfer of Requirements
Types of Transfer of Requirements
Individual Requirements: A TOR occurs for each sales document that is created. The advantage is that the source document can be identified by looking in the availability overview for each requirement.
Collective Requirements: Collective requirements combine several document quantities based on criteria such as Plant, Batch, Storage location, Date, Transaction and Requirements Class. Collective requirements can either be created daily or weekly. The source documents initiating the collective requirements cannot be identified directly but can be determined from the list of orders for the material.
Control of Transfer of Requirements
The control features specific to Sales and Distribution need to be maintained in Customizing:
• Requirements Class: The requirements class contains all control features for planning. 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
• Requirements type: The requirements are identified by the requirements type. The requirements type refers to the requirements class and its control features
• Schedule line category: Schedule line category controls whether an availability check and transfer of requirements should be carried out in the sales documents
Checking group: It controls whether the system is to create individual or collective requirements in sales and shipping processing
Defining the Requirements Classes
IMG>>Sales & Distribution>>Basic Functions>> Availability Check & TOR TOR >>Define Requirement Classes
Requirements class is the key factor in the TOR. It is based on the requirement types of the sales document. These requirement classes are also used in PP, so be sure to involve PP and MM in any changes you envisage in the SD module.
Defining the Requirements Type
IMG>>Sales & Distribution>> Basic Functions>> Availability Check & TOR>> TOR >>Define Requirement Types
The relationship between requirement type and requirements class is many to one.
Assign Requirements Type
IMG>> Sales & Distribution>> Basic Functions>>Availability Check & TOR>>TOR >>Determination of requirement types using transaction
Assign requirement type to the relevant item category in the sales order and the MRP type found on the material Master Record
Defining Procedure For Each Schedule Line Category
IMG>> Sales & Distribution>>Basic Functions>> Availability Check & TOR>> TOR >> Define Procedure For Each Schedule Line Category
We deactivate a setting at the schedule line level only if it is already set at the requirements class level.
Block quantity confirmation in delivery blocks
IMG>> Sales & Distribution>> Basic Functions>> Availability Check & TOR>>TOR >> Block quantity confirmation in delivery blocks
This enables us to unreserve or not reserve any quantity that has been confirmed for an order for which a delivery is blocked.We have the provision of setting this for different reasons and at different transactions
Maintain Requirements for Transfer of Requirements
IMG>> Sales & Distribution>>Basic Functions>> Availability Check & TOR>> TOR >> Maintain Requirements for Transfer of Requirements
In the same way as the requirements used in access sequence, that is, a number of preconditions must exists of the transaction to be carried out, requirements can be used to determine that the TOR to MRP is not carried out unless a number of condition are met.
