SAP SD SUPORTE: Transfer of Requirements

Purpose

The purpose of this page is to explain how the transfer of requirements works in SD / LE side and what needs to be checked in case of problems realted to the transfer of requirements.

Overview

Requirements are generated in SD side if you create e.g. a sales order, delivery... etc.
Requirement is a set of data which includes the information which quantity of which material at which date is required.
The transfer of requirements controls which sales and/or delivery requirements should be written to table VBBE or VBBS.

Typical issues and their solution

Regarding requirements transfer, the following issues can happen:

sales documents & deliveries are not displayed in transaction MD04, CO06 & CO09
entries in table VBBE / VBBS are not created
system confirms more than available
ATP Check does not consider confirmed sales orders & deliveries.

There are various reasons that can cause the above described problems, namely:

wrong customizing
inconsistencies
fixed date & quantity in combination with 0 confirmation
transfer of requirements for sales documents and deliveries is not relevant anymore.

To tackle a requirements transfer related issue, the following actions should be carried out:

STEP 1 – checking the settings in the schedule line category:

In transaction VOV6, if the field "Req./Assembly" is switched off, the transfer of requirements will not be carried out.

STEP 2 – checking the settings in the requirements class:

In transaction OVZG, if the field "Req. transfer" is switched off, transfer of requirements will not be carried out.

STEP 3 – checking the settings related to requirements class determination:

If the system cannot find a requirements class, the transfer of requirements will not be carried out. A requirements class needs to be assigned to a requirements type (transaction OVZH). In case of sales documents, table VBAP / field BEDAE contains the requirements type. In case of delivery documents, table LIPS / field BEDAR LF contains the requirements class. If one of the previously mentioned fields is empty (does not get filled), you need to check your customizing and/or user exits. For more information on how the requirements class is getting determined, please consider SAP Note 207942 - MRP: Problems with requirements from sales order/delivery.

STEP 4 – checking the settings related to availability check control:

In transaction OVZ2, there is an option to determine which type of records should be used for the requirements transfer by maintaining column "TotalSales" and "TotDlvReqs".

The user can choose from 4 different options:

A = Single records
B = Total records per day
C = Total records per week, reqs date on Monday of current week
D = Total records per week, reqs date on Monday of fol. week

In case of single records (A), requirement entries will be added to table VBBE. In case of summarized records (B,C,D), requirement entries will be added to table VBBS. SAP strongly recommends to use single records instead of summarized ones. This option shows document/item/schedule line numbers in transaction MD04, CO06 & CO09, while the setting summarized records does not have this option (for more information on this behavior, please consider SAP Note 1649669 - Sales order number or delivery number is not displayed in transaction MD04). Please note that if "TotalSales" and "TotDlvReqs" fields are not maintained, the system will not be able to determine which table (VBBE or VBBS) should be used, therefore the transfer of requirements will not be carried out.

STEP 5 – checking order probability related settings:

Order probability is calculated by two variables. The first variable is the "Order probab." field in the Customer Master (transaction XD02).

The second variable is the "Probability" field assigned to the sales document type (transaction VOV8).

The probability on item level is calculated by multiplying these two variables. In case of quotations and inquiries, if the calculated order probability equals to 0, no requirements transfer will be carried out. This setting only applies for quotations and inquiries, and has no effect on sales orders. You can check the order probability for a sales document in table VBAP, field AWAHR.

STEP 6 – checking the document settings:

• If the Fixed date & quantity indicator is set and the concerned schedule line has no confirmed quantity, no transfer of requirements will be carried out.
• If the Fixed date & quantity AND the credit check is activated, and the customer exceeds its credit limit, the system will change the confirmed quantity to "0" during saving the document, therefore no transfer of requirements will be carried out.

• If the Fixed date & quantity, the Delivery block and the Confirmation block is set, the system will change the confirmed quantity to "0" during saving the document. Please, read the related SAP Note 1642465 - Transfer of requirement of sales documents even though delivery or credit block is set.

• If the reason for rejection is set, no transfer of requirements will be carried out.

• Deleted sales order and delivery items are erased from table VBBE & VBBS, therefore these documents are not displayed in transaction MD04, CO06, and CO09 anymore. Delivery documents disappear from table VBBE & VBBS after posting Goods Issue.

STEP 7 – looking for inconsistencies:

For information on how to search for & eliminate inconsistent / obsolete lock entries that can have a negative impact on availability check, please check the WIKI page titled Inconsistencies.