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


Need to enhance a project where,


Initially no price was added to this BAPI.

Now i added a condition price by defaulting the condition type.

The condition price is showing 10 times more, e.g 100 is shown as 1000.

Is this expected? in that case do i need to devide price by 10 and then send to BAPI?

Also intially pricing condition use to appear by default to the SO created by this BAPI. This condition type still exists. How to remove it?

I know that this BAPI is obsolete, but it is already in use.

Your help will be greately appreciated.

And points will be awarded.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Sep 22, 2006 at 11:26 AM


    do you also put in the currency?? if not this could be the reason of the increasing of the condition amount. Try to put in the currency in ORDER_ITEMS_IN-CURRENCY

    and now give me the points 😉))

    good luck!

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member


      Since the BAPI is calling by 3rd party, that is very difficult for your to trace why does the defaulted condition type being included during the call. Thus i would suggest below:

      1. Check on the 3rd party side on the input passed in.

      2. If confirm they didn't pass in any suspicious input, then you need to debug the BAPI FM during the 3rd party call. Under the BAPI u may need to code an infinity loop at the begining of the FM.


      data: a type i value 0.
        if a = 1.

      after activate your FM, ask the 3rd party trigger the BAPI call, then you may need to goto tcode SM50 you will get a dialog session being hold for the BAPI. Note: you can determine the correct dialog work process by determine the program name or user id. Then highlight it, goto menu Program/session->Program->Debugging. Immediately an addition popup will bring you to the BAPI FM debugging mode. And you will notice you will stuck in the DO~ENDDO loop where you coded as above. change the value of variable A to 1, then you can continue debug the FM for where is the cause of defaulted condition type coming from.

      FYI, above is applicable for the BAPI calling within SAP itself.

      Hope it helps.

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.