SAP ABAP Data Element ONVBA (Availability check with cumulative, confirmed quantities)
Hierarchy
BBPCRM (Software Component) BBPCRM
   CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
     VZ (Package) Application development R/3 RV central functions
Basic Data
Data Element ONVBA
Short Description Availability check with cumulative, confirmed quantities  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type ONVBA    
Data Type NUMC   Character string with only digits 
Length 1    
Decimal Places 0    
Output Length 1    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 Accumul. 
Medium 15 Accumulation 
Long 20 Accumulation 
Heading Acc 
Documentation

The following problem may occur if committed quantities are not cumulated:

Starting from the delivery date of the sales order and looking in the past, the system checks to see whether ATP quantities exist. If it actually finds an ATP quantity, it is reduced by the new sales order. Sales orders can only reduce ATP quantites whose date lies before the the delivery date.

In this logic, the system does not take the committed quantity of already created sales orders into account. If receipts are displaced and/or reduced in the past, it is possible that the ATP quantity of the receipt that lies before a sales order is now too small to cover this sales order quantity although it has already been completely confirmed.

Example

The following example should explain this situation:

Situation 1

MRPelemt Recpt/Reqmt        ATP qty    Cum.ATP qty    Committed qty

Stock    100    0    0        -

PlOrd    100    0    -100   

SalesOrd    -200    -    -        -200

Situation 2

MRPelemt Recpt/Reqmt        ATP qty    Cum.ATP qty    Committed qty

Stock    100    0    0        -

SalesO1    -200    -100    -100        -200

PlOrd    100    0    0        -

SalesO2    -100    -    -        100

In situation 1, the first sales order is completely confirmed when the planned order lay before sales order 1 on the time axis. In situation 2, the planned order has been moved on the time axis so that it now lies after the delivery date of the sales order 1. For the new sales order 2, an ATP quantity of 100 exists as the moved planned order is now completely available again as according to ATP logic it can no longer be used to cover sales order 1.

In this example, a inconsistency occurs with the confirmations as the planned order has been moved - the sum of the confirmed quantities exceeds the sum of all receipts.

To correct this inconsistency, you have the following options:

  • carry out the planning run
  • carry out rescheduling
  • backorder processing

Availability checking taking cumulated confirmed quantities into account

The function, "checking taking cumulated confirmed quantities into account" should avoid such inconsistencies as you can set how the check is to be carried out when creating or changing sales orders:

  • Check taking cumulated confirmed quantities into account

    In the availability check in the sales order, the system takes the sum of all previously confirmed quantities into account when calculating the cumulated ATP quantity. This means that new sales orders can only be confirmed if the sum of all receipts exceeds the sum of the confirmed quantities.

  • Check taking cumulated requirements quantities into account

    In the availability check in the sales order, the system takes the sum of all open requirements quantities to date into account when calculating the cumulated ATP quantity. This means that new sales orders can only be confirmed if the sum of all receipts exceeds the sum of all requirements quantities.

With these new ATP checking procedures, you have the following setting options when creating /changing a sales order:

  • Cumulation of the confirmed quantities when creating and changing.
  • Cumulation of the requirement quantity when creating, no cumulation when changing.
  • Cumulation of the requirement quatity when creating, cumulation of the confirmed quantity when changing.
  • No cumulation (old checking logic).

Recommendsation

You are recommended to work with the cumulation of the requirement quantities when creating sales orders.

You are recommended to work with the cumulation of the confirmed quantities when changing sales orders.

Use

The setting that you make here is valid in

  • Sales order processing
  • Production order processing for order reservations

History
Last changed by/on SAP  19961029 
SAP Release Created in