‎2012 Sep 12 8:37 AM
Hello,
We habe Problems with Using the BAPI bapi_salesorder_createfromdat2 after Updating our Kernel last week.
System A (with Kernel Update) --> no manuel Conditions will be save in the salesorder
System B (without Kernel Update) --> saves the Conditions we are given to the BAPI.
The Call of that BAPI is in both System completely the same. we havent changes the calling while that ERP-Update.
SPAU was made and all modification were assumed.
I've checked the internal Table for Conditions from FM SD_SALES_DOCU_MAINTAIN who is called in bapi_salesorder_createfromdat2 and they look like that:
the FM SD_SALES_DOCU_MAINTAIN have been changed after that ERP-Update from last User SAP. So something changed! But what??
If i insert the conditions with VA02 in that created salesorder manually, everything works fine. So the condition-finding seems to be fine.
What have been changed in BAPI bapi_salesorder_createfromdat2?
What is the Problem? If you need any more informations, like the calling from that BADI, just let me know and i will post it !
thanks a lot
‎2012 Sep 12 4:01 PM
Hello,
I resolved the issue on my own *happy*.
Problem was, that we delivery the structure "logic_switch" which contains the field PRICING(pricing type).
after our erp-update (SP 20 for SAP_APPL 6.00 and SP 21 for SAP_APPL 6.00) the BAPI "bapi_salesorder_createfromdat2" seems to handle the structure logic_switch in a different way.
now we call the bapi without that structure logic_switch and the manuel conditions are saved in the created salesorder.
‎2012 Sep 12 4:01 PM
Hello,
I resolved the issue on my own *happy*.
Problem was, that we delivery the structure "logic_switch" which contains the field PRICING(pricing type).
after our erp-update (SP 20 for SAP_APPL 6.00 and SP 21 for SAP_APPL 6.00) the BAPI "bapi_salesorder_createfromdat2" seems to handle the structure logic_switch in a different way.
now we call the bapi without that structure logic_switch and the manuel conditions are saved in the created salesorder.