Skip to Content
avatar image
-2
Former Member

Message VF 073 Pricing error in item 000001

HI Experts..

In the VF02 i have given the Billing document number..and then i press the ReleaseToAccounting button on the screen..Then i got the "

Pricing error in item 000001

". I debugged the standard code..there i found that if VBRP-UVPRS field is 'X' then it throws that message..If the field UVPRS in VBRP is space then i am not getting any error...so please help me to resolve this problem..When will this field UVPRS will become 'X' in VBRP table..

Thanks in Advance.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Jul 27, 2017 at 02:08 PM

    As you could probably guess from the field description, UVPRS is a field to mark pricing incompletion :)

    When it is 'X' - the document is incomplete, when it is ' ' - it is OK from pricing perspective.

    Pricing incompletion can occur for example, when you set a condition type as mandatory in the pricing procedure, but it is not determined in the sales document. In this case an end user can find it easily by navigating to conditions screen (you get a message 'Pricing Error: Mandatory Condition XXXX is missing'). Another way to set pricing incompletion is via a VOFM routine, which forces KOMP-CEPOK to 'B' - this is how customer expected price conditions EDI1 and EDI2 work. Users usually find these by checking first the conditions in with a red icon. Since you have debug authorizations, debugging is another way to find out which condition is causing problems, I suppose (I have not used it for this specific purpose, though).

    Add comment
    10|10000 characters needed characters exceeded

    • You are repeating the same test/statement as before and I am unsure, that you read and understood what I wrote.

      It is not uvprs causing issues, it is what causes uvprs to become 'X' and this is most often configuration or master data or custom code.

      In order to find out from where the problem with pricing originates, you need to know well the configuration (procedure, condition types, routines, copy controls) and, if you suspect non-standard logic - exits.

      It seems to me, that you are not a functional SD consultant, otherwise you would have gone through the configuration before posting the question and, most likely, you would not have resorted to debugging. The easiest way is to ask a colleague locally to help you out.

      If you cannot find anyone in your company, who is familiar with SD pricing and if you feel very comfortable with debugging, then you can follow the wiki guide, which is specifically for the error, which you posted about (I am not posting the link on purpose, so that so that I don't deprive you from searching for it by yourself), or you can go via the longer route - checking out potential exits in PRCAT transaction and reading the blog Pricing Programs and their logic – Help for debugging.

      A fair warning (I hope, unnecessary one) - while debugging, do not change any values and save the document, unless you are 100% sure, that you know what you are doing.

  • Jul 31, 2017 at 08:55 AM

    Search Google with the text "xvbrp-uvprs X", so that you will find a Wiki. Take the inputs from there, if you issue is still not addressed

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Thanks for reply.

      Checked for "xvbrp-uvprs X and found its creating issue cause of Pricing type.

      Thanks,

      Amol

  • Jul 27, 2017 at 02:58 PM

    Did you check in sale order where you should be having an incompletion log for pricing ?

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Lakshmipathi,

      Thanks for reply.

      Checked in sale order no incompletion log for pricing.

      Thanks,

      Amol