cancel
Showing results for 
Search instead for 
Did you mean: 

Credit blocks after ATP BOP Run

SAPSupport
Employee
Employee
0 Kudos
836

We don't understand why sales order changes triggered via ATP BOP Run are causing credit blocks.


------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

Accepted Solutions (1)

Accepted Solutions (1)

SAPSupport
Employee
Employee
0 Kudos

Please note that credit check can be re-triggered with a BOP ATP execution because it can change credit check relevant fields and thus the sales document can be a subject for new credit checks. This way credit block can possibly occur again based on the current credit situation of the relevant customer.
During an ATP run, not only confirmed quantity changes can trigger new credit checks, but date (and price) changes to any item's schedule lines in the sales document can also contribute to this behavior as they are also relevant data for credit management point of view.
Please also note that for these cases, we recommend our customers to use a 'No check' routine in transaction OVA8 to skip the credit checks when this specific background process is executed on the sales documents.

See further information about how to use no check routines in the below SAP Notes:

2469457 - Bypass credit check in custom routine in SAP Credit Management(FSCM)
895630 - Use of the requirement "No check"
502930 - New credit status although 'No check' is programmed

The re-triggering of credit checks during ATP is the standard behavior and it can only be avoided via custom no check routines.
Please contact your local consultant and developers to apply such custom routine in OVA8 for the relevant CCAr/Risk Category/Credit Group and test the behavior first in a test environment of yours.

Answers (0)