SAP Note

718260 - Released documents are not checked

Version 6 Validity: 08.10.2010 - active

Language English

Header Data
Released On 08.10.2010 11:58:53
Release Status Released for Customer
Component
SD-BF-CM Credit Management
Priority
Recommendations / Additional Info
Category
Consulting

Symptom
Documents are released from the credit block. Later, these documents are processed again. It is not
clear when these documents are subjected to a new credit check and when they are not.

Other Terms
T691F-CRPRC, T691F-TAGEF, OVA8, VBAK-CMFRE, VBAK-AMTBL, AMTBL, SD_ORDER_CREDIT_CHECK,
SD_DELIVERY_CREDIT_CHECK, NO_CHECK, DELIVERED_VALUE

Reason and Prerequisites

The automatic credit control is active. The documents have the status "Transaction released" (VBUKCMGST = 'D').

Solution
During further processing of documents that have already been released, the system checks if the
credit check must be carried out again or not. Two criteria are relevant for the decision:

The value of the document for the release (VBAK-AMTBL)

When the document was released (VBAK-CMFRE)

If the document value has increased compared to the release value or if the release is too old, the
system carries out a new credit check.The decision is carried out in two steps:
1. Is the document value lower than the release value?
2. Is the release too old?
If both of these conditions apply in this sequence, the system does not carry out a new credit
check. Therefore, this refers to an AND operation between the two conditions in this sequence.
Customizing
In Customizing of the automatic credit control (Transaction OVA8), you can enhance the limits for
the two conditions under "Released documents are still unchecked".
1. You can define an allowed deviation in % for the release value.
2. You can define a number of days for the release date.
Examples
Settings under "Released documents are still unchecked"
Deviation %= 12
Number of days = 2
l

The release value of a sales order is 10,000. After the release, you change the sales order and
increase the price.The credit value of the sales order is then 11,000.As a result, the
credit value only exceeds the release value by 10 %.
If the document is only released on the previous day, the release is not too old. Both
conditions are met. The credit check is not carried out again.
If the document was already released five days ago, the release is older than two days. The
credit check is carried out for the document again.
The release value of a sales order is 5,000. The sales order is changed to increase the
quantity. As a result, the sales order has a credit value of 7,000. The credit value is now more
than 12% higher than the release value.
A credit check is carried out for the sales order again even if the release took place within
the previous two days.

A sales order is released. However, the requested quantities can only be partially
confirmed.The release value of the sales order is 1,000 since the system calculates the value
based on the confirmed quantities (see Note 377165).
During rescheduling, all requested quantities are fully confirmed. The document value is now
12,000 due to the confirmed quantity. As a result, the current document value exceeds the
release value by more than 12%. The credit check is carried out again.
Note 100861 describes this problem in more detail.
A sales order is released and receives a release value of 20,000.On the same day, you change
the sales order to enter an additional text item.As a result, the document value does not
change. A credit check is not carried out again for the sales order since both conditions are
filled.
If the text item is not entered until three days after the release, the document value still
does not change. However, the release is older than two days. The credit check is carried out
for the document again.

Additional comment 1: Check for documents checked with OK

The described logic applies only for documents that have been released. Documents that are in the
credit status "Transaction is OK" (VBUK-CMGST = 'A') are not subject to the settings under "Released
documents are still unchecked".
l

Example:
A sales order is created and receives the credit status "Transaction is OK".Afterwards, the
credit representative reduces the credit limit for this customer so that the credit limit used
exceeds the credit limit. The sales order is processed again and a text is defined.The credit
value of the sales order does not change. Despite this, a credit check is carried out and the
document is credit blocked.

Additional comment 2: Check for day of release

On the day of the release, no further credit check occurs if the document value has not increased
compared to the release value.This also applies when you create a delivery for a released sales
order.
l

Example:
A sales order is created and credit blocked. The credit representative releases the sales
order.Later the credit limit for this customer is reduced.Now the customer has used up his
or her credit limit. Documents that are newly created are credit blocked.
The sales order is then delivered.Since the delivery is created on the day of the release and
the document value has not changed compared to the release value, no further credit check occurs
for the delivery.

Note 52637 and Note 588226 provide a modification whereby the documents are also checked on the day
of the release.
Additional comment 3: Check for partially delivered sales orders (see Note 433294)
For orders that are already partially delivered and are then changed, the system also checks whether
the current document value is larger than the release value.In this case the credit value of the
delivery is subtracted from the release value since the document value is also reduced by the value
of the delivery.The system only takes into account deliveries that have been created after the
release.The release date is relevant in this case.
However, if the delivery is created on the day of the release, the system can no longer recognize
whether the delivery was created before or after the release.Therefore, deliveries from the day of
the release are always subtracted from the release value.
As a result, a new credit check may be carried out although the check should not occur.
l

Example:
A sales order is created and credit blocked. The sales order is then released and delivered.
Another item is added to the delivered sales order.As a result, the order is credit blocked
again. The order is released. Another sales order change results in a further credit block
although the value of the sales order has not increased compared to the release value.
This happens only if all postings occur on the same day.

For technical reasons, this system behavior cannot be changed. For security reasons, it is
preferable for the system to carry out a credit check if there is any doubt (has the delivery from
the day of the release been created before or after the release?).
Additional comment 4: Exceptions
The logic "Released documents are still unchecked" is invalid if the credit check is triggered
manually. This is the case for a new credit check in the VKM* transactions or for reorganization of
the credit data with the report RFDKLI20 (see Note 485305).

Validity
This document is not restricted to a software component or software component version

References

This document refers to:

SAP Notes
895630 Use of the requirement "No check"
862183 Sales document is checked again on the day of the release
807979 Partial delivery: Renewed check of released documents
588226 New credit check at day of release
566097 Setting a requirement over the credit management check
502930 New credit status although 'No check' is programmed
485305 Report RFDKLI20 changes credit status in spite of release
433294 Credit check despite release logic for partial delivery
377165 Update open credit values for credit management
100861 Release of blocked sales orders - loop check
52637 Modification note: Further check for delivery

This document is referenced by:

SAP Notes (13)
566097 Setting a requirement over the credit management check
588226 New credit check at day of release
1277392 Credit check when creating a purchase order
895630 Use of the requirement "No check"
889182 Sales order with down payment is checked again
862183 Sales document is checked again on the day of the release
807979 Partial delivery: Renewed check of released documents
52637 Modification note: Further check for delivery
433294 Credit check despite release logic for partial delivery
100861 Release of blocked sales orders - loop check
377165 Update open credit values for credit management
502930 New credit status although 'No check' is programmed
485305 Report RFDKLI20 changes credit status in spite of release