The purpose of this page is to explain how the transfer of requirements works in SD.Availability check can only be carried out if transfer of requirements take place for goods from sales to purchase or production.
What is Transfer of Requirements
Requirement produced in Sales & Distribution needs to be transferred to the planning of material requirement to ensure that the ordered quantities are available for delivery to the Customer on time. This is called Requirements Transfer (TOR).
Types of Transfer of Requirements
Individual Requirements: For every sales document that is created a TOR occurs. The benefit is that one can locate the source document by searching for each condition in the availability summary.
Collective Requirements: Collective requirement incorporates many quantities of records, based on parameters such as plant, batch, place of storage, date, transaction and class of specifications. Collective requirements may be created either daily or weekly. The source documents which trigger the collective specifications can not be explicitly defined but can be determined from the order list for the content. Collective requirements combine various requirements based on the following criteria:
- Storage Location
- Transaction &
- Requirement class
Such requirement can be defined either daily or weekly. Documents which trigger collective requirements can not be identified directly, but can be traced through a list of material orders
Control of TOR(Transfer of Requirements)
The control features specific to Sales and Distribution need to be maintained in Customizing
Requirements Class: The Requirements class contains all planning control functionality. Therefore, it is defined at a global level whether the quality test for the material in the sales and distribution documents will take place on the basis of the ATP quantity (ATP = available to promise) and whether the requirements should be passed on
Requirements type: The requirement type are defined by a form of requirement. Form of requirements refers to the class of requirements and their control functions
Schedule line category: Schedule line category monitors how the specifications should be reviewed for availability and moved to the sales documents
Checking group: It checks whether the system is designed to create individual or collective sales and shipping requirements
Transfer of Requirements Configuration
Defining the Requirements Classes: Requirement class criteria is the main component in TOR. This is focused on the Sales document. These requirement classes are also used in PP, so make sure that PP and MM are involved in any changes you envisage in the SD module
IMG-Sales & Distribution-Basic Functions-Availability Check & TOR-TOR -Define Requirement Classes
Defining the Requirements Type:The relationship between requirement type and requirements classis many to one
IMG-Sales & Distribution-Basic Functions-Availability Check & TOR-TOR -Define Requirement Types
- Assign Requirements Type:Assign requirement type to the relevant item category in the sales order and the MRP type found on the material Master Record
IMG-Sales & Distribution-Basic Functions-Availability Check & TOR-TOR -Determination of requirement types using transaction
Defining Procedure For Each Schedule Line Category:We deactivate a setting at the schedule line level only where it is already set at the class level of requirements.
IMG-Sales & Distribution-Basic Functions-Availability Check & TOR-TOR -Define Procedure For Each Schedule Line Category
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 delivery is blocked. We have the provision of setting this for different reasons and at different transactions
IMG-Sales & Distribution-Basic Functions-Availability Check & TOR-TOR -Block quantity confirmation in delivery blocks
Maintain Requirements for Transfer of Requirements:In the same way as the requirements used in the access sequence, that is, the transaction to be carried out must be subject to a number of preconditions, requirements may be used to determine that the TOR to MRP is not carried out unless a number of conditions are met
IMG-Sales & Distribution-Basic Functions-Availability Check & TOR-TOR -Maintain Requirements for Transfer of Requirements
Prerequisite for TOR
- TOR needs to be switched on at Requirements class and Schedule line category level for proper processing.
- The plant must be defined at the item level in the sales document.
- Checking group must be defined in material master in Sales/plant view.
Happy Learning ..!!
Now you may follow these tutorial links to learn more about
- Available to Promise (ATP) in SAP
- Replenishment lead time (RLT)
- SAP Sales Integration with other Modules
- SD Advanced Pricing
- SAP S/4HANA
- User exit in sap
- SAP Fiori App
- SAP Fieldglass
- SAP Customer Engagement & Commerce Suite(CEC Suite)
- Hybris Marketing
- Third-Party Sales in SAP