TOR

[Former Member]

Hi,

can any one explain me transfer of requiremnt? how it works and how to configure?

[Former Member · Accepted solution]

Hi,

And also go thru below details it is help full.

Materials Requirements Planning (MRP) and Transfer of Requirements (TOR).

1. A schedule line in a sales order represents the customers intended delivery date and quantity to be delivered. In a standard sales order processing, the system transfers requirements (TOR) to Material Requirement Planning (MRP).

2. MRP - then determines if there is enough quantity of stock available for the scheduled delivery date. The TOR aims to ensure that the materials ordered are ready for the requested delivery date.

3. The TOR is closely integrated to Materials Management and Production Planning modules – thus it must be configured in association with the respective teams.

4. The TOR can be set either for individual requirements or for collective requirements in MMR (Sales: general/plant and MRP3 views).

5. Individual requirements are the transference of requirement to MRP for each schedule line of the sales order. An advantage of this is that the availability overview (CO09 – logistics – material management – environment – stock – availability overview) will show the order quantity, sales document number, item number and requirements class for each schedule line for which a demand has been created.

6. Collective requirements are a collective grouping of requirements created either daily or weekly that are transferred to MRP; but the documents processed in collective requirements cannot be individually identified from the availability overview (CO09). Collective requirements are useful to a business that deals with a large volume of sales orders per day, as it allows the business to have a clearer view of the availability overview and speeds up the response time within the system as well.

7. The system will automatically create individual requirements (irrespective of the collective requirements indicated in MMR) in case of special stock items such as consignment, returnable packaging, make to order stock etc.

8. The control elements that are used for Transfer of Requirements (TOR) and Availability Check are –

the requirements class

the requirements type

the checking group

the schedule line category

9. The requirements class is the controlling factor for TOR and the availability check for all sales document types. It determines if the system has to perform TOR, Availability check and product allocation to any particular sales order.

10. The requirements class is determined from the requirements type of the material.

11. The checking group in general is the criterion that groups together all the checking rules from all application areas for a material. In conjunction with the checking rule, it defines the scope of the availability check for each business event; that is, which stocks, goods receipts and goods issues are taken into account in the availability check, and whether replenishment lead time is checked. The checking group must be defined and allocated to the material master record in the sales: general/plant view in the availability check field.

12. for TOR to be carried out, you need to ensure the following criteria are met –

The TOR must be switched on at the requirements class level.

The schedule line category must be switched on for the TOR (fine tuning).

A plant must be assigned to the sales document line item level.

A checking group must be defined and allocated to the material master record in the sales: general/plant view in the availability check field.

Planning materials –

It is possible to create a common planning material and assign similar materials to it (MRP 3).Independent requirements are created for the planning material to cover the requirements that are expected for the materials assigned to the planning material. This means that you do not have to create independent requirements for each material. Instead create a material and assign the same to the planning material already created with similar properties.

A valid material master record must exist for the planning material in the planning plant. The material master record of the planning material cannot contain a planning material as this procedure can only be carried out at single-level.

An appropriate strategy group must also be entered in the MRP 3 screen for planning with planning materials. The strategy group groups all the planning strategies that can be used for a particular material. The planning strategy represents the procedure used for planning a material and is (technically speaking) controlled by the MRP types.

Consumption mode defines whether and in which direction on the time axis – from the requirements date (corresponds to the date when the sales order items were created) the consumption of customer requirements with planned independent requirements should occur. Consumption period must exit between 1 and 999 days.

Backward consumption only: starting from the requirements date, backward consumption is carried out within the relevant consumption period specified in MMR i.e. the system reduces the planned independent requirements that lie in the past. Likewise forward consumption only represents – starting from the requirements date, the system reduces the independent requirements that lie in the future within the consumption period.

Backward/forward consumption: in this case backward consumption is performed first and forward consumption is performed later depending on the availability of the independent requirements in the past. Forward/backward consumption is vice-versa of the above.

Stock requirements list –

1. Stock requirements list is the central table for planning and stock control. It is invaluable to the interpretation of the available stock and the situation of stock levels in a plant.

2. Menu path: MD04 – logistics – material management – inventory management – environment – stock – stock requirements list. Here you can see the order number or delivery number as well as the line item and schedule line placing the demand on the given plant. It also shows the required and available quantity of material per order.

3. Another view of the stock situation in plant can be obtained from MMBE (stock overview). This view will show you total stock per company code, then at the plant, storage location and at batch level.

4. A useful tool in MMBE is material movements, which can be viewed by selecting stock line and proceeding to environment, material movements.

Configuring Transfer of Requirements –

1. IMG – sales & distribution – basic functions – availability check & TOR – transfer of requirements – define requirements classes.

2. Requirements class – (OVZG) is the controlling factor for the availability check and TOR for all sales documents. It determines whether the system should perform the transfer of requirements, availability check and product allocation when a sales order is created.

3. The system uses the entries used at this level as default and brings the data into the sales order. The same entries made at the schedule line category level (VOV6) are only used to fine tune the entries previously made at the requirements class level. The standard requirement class is 041 (order/delivery requirement).

4. Requirements type – (OVZH) – (displayed in the sales order beside schedule line category) requirements types identify the different requirements, such as sales order requirements, delivery requirements or individual customer requirements. The requirements types can be changed, for example, in order to represent customer-specific terms.

5. The first step in the process of configuring TOR is to define a requirements class (041 – standard) by copying the standard one. It contains the preconditions for performing availability check, TOR and product allocation.

6. Next step is to create a requirements type, which is based on item category and MRP type of the material and allocate the previously defined requirements class to it. A requirements class can be allocated to more than one requirements type. It is possible to change the requirements type manually at the time of creating the sales order.

7. MRP type in the MMR determines how a material is planned for requirements i.e. automatic reorder point planning, manual reorder point planning or forecast based planning.

8. Determination of requirements types using transaction: when a sales order is created, the system looks for a relevant requirement type by using its own search strategy. Either it uses the following search strategy or you can make the system skip this entire process and straight away search for item category and MRP type by selecting 1 in the Q field while configuring determination of requirements types using transaction.

9. First attempt is to find the requirements type using strategy group in MMR.

10. If strategy group is not found, it will look for MRP group (MRP group groups’ together material with similar planning requirements and allocates special control parameters for planning such as strategy group, planning horizon and the creation indicator for planning run.

11. If MRP group is not found, it will try to access MRP type.

12. If no requirements type is found using MRP type, the system will use material type when accessing the corresponding tables.

13. Failing to find the requirements type even at this stage, it will try to get the requirements type using the item category and MRP type.

14. If this doesn’t work either, then it will try to determine requirements type using only item category.

15. If the last attempt fails, the system determines the transaction is not relevant for availability check or transfer of requirements.

16. As discussed earlier TOR and availability check are fine tuned at the item category level. This is done at this stage i.e. define procedure for each schedule line category as a next step.

17. Block quantity confirmation in delivery blocks (linked to VD05 customer block): in the standard sales order processing, the system transfers the requirements to MRP, but in some cases you may need to block a transaction due to a bad result of the credit check.

18. When requirements are transferred to MRP, the confirmed quantity is also reserved for confirmed sales documents . If a transaction is blocked for delivery, the required stock will be blocked so it cannot be used elsewhere. To prevent this, you can block the transfer of requirements for a delivery block in this step.

19. You can set a limit on the number of days you would want the system to postpone this block on confirmation of requirements. This can be done by setting the number of days to the block in the Def. period column.

20. Maintain requirements for TOR: can be used to determine that the TOR to MRP is not carried out unless a number of conditions are met. For example in a standard sales order processing, a purchase order may need to be created in order to meet the demands of the customer. This purchase order is used to purchase new stock in order to meet the demand on MRP for particular customer’s sales order. Here you define requirements that must be met in order for the purchase order or assembly order to be created.

[Former Member]

Hi

Refer link below

[Lakshmipathi]

Dear Sudhi

Go through the links which will answer your question

[Working with Requirements |http://help.sap.com/saphelp_46c/helpdata/en/93/744c6c546011d1a7020000e829fd11/frameset.htm]

[Transfer Requirement |http://help.sap.com/saphelp_46c/helpdata/en/c6/f83d224afa11d182b90000e829fbfe/frameset.htm]

Thanks

G. Lakshmipathi

[Former Member]

Transfer of Requirements

By means of the transfer of requirements, the MRP department is informed about the quantities and deadlines by which incoming orders should be delivered. The system checks the availability of the goods based on the requested delivery date of the customer and creates MRP records which contain all necessary information for passing on to materials planning. The transfer of requirements ensures that the goods are available in time for the delivery. Materials planning transfers the reported requirements and creates production orders or purchase requisitions from them, for example.

The following sections on the transfer of requirements describe how to control the transfer of requirements.

The transfer of requirements is basically dependent upon the following factors:

requirements type

requirement class

check group

schedule line category

Note

The transfer of requirements is controlled globally using the requirements class which is derived from the requirements type for all sales document types. For the sales document types, fine tuning is also possible at schedule line level. This fine tuning is described in the section "Defining the procedure for each schedule line category".

Note that the requirements classes are also used in production so you should coordinate any changes to the requirements classes with production. The requirements type and, eventually, requirements class are determined in the strategy group so all changes made there should also be coordinated with production.

Requirements transferred to planning are further processed in the module MM. You must, therefore, coordinate the transfer of requirements with the module MM.

Requirements

For controlling transfer of requirements, you have to carry out the following steps:

1. Each requirement type has to be allocated to one requirement class only.

2. The transfer of requirements must be switched on at requirements class level, the sales documents at schedule line level.

3. You must define a check group. It is possible to have this check group proposed for the initial creation of a material master record.

4. Note that a plant must exist for transfer of requirements to be carried out at document item level.

Note

Requirements transferred to planning are further processed in the module MM. You must, therefore, coordinate the transfer of requirements with the module MM.

Reward if usefull

[Former Member]

Hi Friend,

The MRP department is informed about the quantities and deadlines by which incoming orders should be delivered. The system checks the availability of the goods based on the requested delivery date of the customer and creates MRP records which contain all necessary information for passing on to planning. It ensures that the goods are available in time for the delivery.

Materials planning transfers the reported requirements and creates orders or purchase requisitions from them etc.

For performing transfer of requirements, you have to carry out the following steps:

1. Each requirement type has to be allocated to one requirement class only.

2. The transfer of requirements must be switched on at requirements class level, the sales documents at schedule line level.

3. You must define a check group. It is possible to have this check group proposed for the initial creation of a material master record.

4. Note that a plant must exist for transfer of requirements to be carried out at document item level.