SAP Note 19295 - SIS: Updating even rejected items

Symptom:

If you reject a sales order item (by setting the reason for rejection), the key figures for incoming orders are not reduced in the information structures.

Cause and prerequisites

This is intended to be this way.
The key figures for incoming orders are to be interpreted as gross key figures for incoming orders in this case. All sales order items that are available in the system are used to generate the key figures for incoming orders (providing, this was allowed in SD Customizing for all sales order types and item categories).
Deleted sales order items still reduce the key figures for incoming orders.

CAUTION:

1. In the standard system, the Sales Information System does not take field MCVBAP-ABGRU into account, that is, all key figures are updated. The open items and values, however, are excluded from this since these are not calculated for completed items (overall delivery status MCVBUP-LFGSA = "C") and rejected items have the status "C".

2. In Customizing of the reason for rejection (Transaction OVAG), you can control whether the values of the rejected items are cumulated on the header level. If this is deactivated, during the update of, for example, the net value (NETWR) from the item level, the reason for rejection is not taken into account (see point 1). However, it is taken into account during the update of the net value from the header level since VBAK-NETWR only results from the total of the items which are not rejected.

3. If you set a reason for rejection for a partially delivered item, in general, incorrect figures occur in the statistics. The reason for rejection does NOT refer to the remaining quantity but to the entire item!!! Consequently, it also does not make sense to set a reason for rejection for partially delivered items if only the remaining quantity should be rejected. Instead of setting a reason for rejection, then the quantity itself should be reduced.

Solution

If you do not want to allow the update of rejected items, you can prevent this by means of a condition in the update rules.
To do this, define a condition which allows the update only if the item field "Reason for rejection" (field name ABGRU) is not filled, that is, it is initial.

Example for the ABAP/4 program code in a condition:

IF mcvbap-abgru IS INITIAL.
returncode = 0.
ELSE.
returncode = 4.
ENDIF.

• If you want to post the amounts already delivered for rejected items into the statistics, you can use the following formula to do this:
  
  Example for the ABAP/4 program code in a formula:
  
  IF mcvbap-abgru IS INITIAL.
  formula_value = mcvbap-kwmeng.
  ELSE
  formula_value = mcvbapf-erlmenge_l.
  ENDIF.
  
  IMPORTANT: THIS IS PURELY A CONSULTING SOLUTION. NO GUARANTEE IS MADE THAT mcvbapf-erlmeng_l IS CORRECTLY FILLED FOR ALL ORDER TYPES/BUSINESS OPERATIONS (in particular, SCHEDULING AGREEMENTS). Therefore, you should test the update for all relevant business operations. There is no SAP support for update problems that occur when using the formula provided.
  
  However, you can complete the update rules for key figures for incoming orders only for your own info structures. You cannot change the update rules of standard info structures.

Additional key words

Reason for rejection, SIS, update, incoming order