topic Re: BAPI_SALESORDER_CREATEFROMDAT2 condition value is auto determined. in Application Development and Automation Discussions

BAPI_SALESORDER_CREATEFROMDAT2 condition value is auto determined.

Former Member — Tue, 13 Oct 2015 10:56:06 GMT

Hi All,

when i am creating SO through BApi.

and i pass condition type as

Condition item number	Condition type	Condition rate	Currency Key
ITM_NUMBER	COND_TYPE	COND_VALUE	CURRENCY
10	PR00	100	EUR
10	EK02	110	EUR
10	ZCOS	120	EUR

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

Re: BAPI_SALESORDER_CREATEFROMDAT2 condition value is auto determined.

sundaramoorthy_ramalingam — Tue, 13 Oct 2015 11:45:11 GMT

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

Re: BAPI_SALESORDER_CREATEFROMDAT2 condition value is auto determined.

Former Member — Tue, 13 Oct 2015 11:51:29 GMT

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.

Re: BAPI_SALESORDER_CREATEFROMDAT2 condition value is auto determined.

Former Member — Tue, 13 Oct 2015 13:16:45 GMT

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