Skip to Content
author's profile photo Former Member
Former Member

Message VM021 SAP Credit management active: Credit limit check not supported

Hello Experts,

In a upgrade from ECC5 to ECC6 (technical) there is a sales order type which is raising message VM021, and therefore the credit limit check is not being done. Message:

Short Text

SAP Credit Management active: Credit limit check not supported


SAP Credit Management is active.

The "Simple Credit Limit Check", that is, the characteristics

'A' (Execute credit limit check and warning)

'B' (Execute credit limit check and error)

'C' (Execute credit limit check and delivery block)

maintained in Customizing "Assign Sales- and Delivery Documents" (transaction OVAK), are not supported.


In the Customizing tree, go to

Financial Supply Chain Management --> Credit Management --> Integration with Accounte Receivable Accounting and Sales --> Integration with Sales --> Assign Sales- and Delivery Documents

and maintain the credit limit check for order types. Use characteristic 'D' (Credit Management: Automatic credit check).

Indeed the sales order type in question has "C" in QA (as well in PRD). However in PRD the credit check is being normally done while in QA it is not, raising the warning message above.

I've tried to search for SAP notes related to it but found none. Can you please advise? If this change is indeed necessary (from "C" to "D") I would like to have a SAP note where this is clearly stated.

I've checked OVA7, OVA8, VOV4, OVAK, VOV8 and they are equal both in QA as in PRD.

Text Removed

Message was edited by: G Lakshmipathi

Please dont add such text

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Jun 26, 2012 at 07:39 PM

    You may check OSS Note 876599 - SAP credit management: Several errors for additional help.


    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 27, 2012 at 03:44 AM

    First try to analyse the issue in debug mode with the help of ABAPer both in Quality and Production clients. I am sure, definitely, some customization would be different between these two clients and that is why, system is not behaving properly. Still if you are unable to find out the root cause, better to raise OSS note. Needless to mention, if your issue is resolved due to SAP's inputs, try to update here which will be helpful to all.

    G. Lakshmipathi

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 03, 2012 at 11:05 AM

    Hello all,

    Herewith the input from SAP:

    "Thank you for providing me with example. I checked it on your

    TQ4 system. The issue occurs because there is the active

    implementation for the follow BADI.

    BADI: UKM_FILL (Implementation ZUKM_CREDENTIALS is active and will

    be called ).

    Due that the system assumes that the FSCM is activated. Please

    check it and deactivate the implementation, than the issue should be


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.