Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

BAPI_SALESORDER_CREATEFROMDAT2 condition value is auto determined.

Former Member
0 Likes
3,861

Hi All,

when i am creating SO through BApi.

and i pass condition type as

Condition item numberCondition typeCondition rateCurrency Key
ITM_NUMBERCOND_TYPECOND_VALUECURRENCY
10PR00100EUR
10EK02110EUR
10ZCOS120EUR

The value of ZCOS get redetermined as EK02 . then manually it has to be changed in va02 as 120 .
i want it to be updated through BApi itself.

still its not happening..

And yes i have tried giving counters and filling cond_inx with update flag as .... 'I'  , 'U'


correct answer will be rewarded



1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
2,435

Did you check the importing parameter LOGIC_SWITCH.

Here you can pass how the pricing should behave. Take help from you functional person to understand how the values in PRICING field behave (DATA element KNPRS ). Documentation is also there for the same.

Hope this helps.

3 REPLIES 3
Read only

0 Likes
2,435

Hi,

     I don't think there is a error in programing,condition types are determined by the system

ref the links :

https://scn.sap.com/thread/1759308

Condition Technique in Calculations and Price Determination - Strategic Sales - SAP Library

it is automatically changed in your code because the for the particular material the condition type has already been defined .

In va02 if the condition type is already defined it will be a non editable field.

so if condition type is not defined the system takes the value passed by you else it takes the value that has been already defined.

Hope this helps.

correct me if i am wrong

Read only

Former Member
0 Likes
2,436

Did you check the importing parameter LOGIC_SWITCH.

Here you can pass how the pricing should behave. Take help from you functional person to understand how the values in PRICING field behave (DATA element KNPRS ). Documentation is also there for the same.

Hope this helps.

Read only

0 Likes
2,434

the correct answer was using pricing condition as 'G' in logic_switch