topic Re: BAPI_SALESORDER_CHANGE in Application Development and Automation Discussions https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/3204962#M764032 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P></P><P>Probably repeating things that you may know, but BAPI's, as their definition implies, have the same typical business logic behind them as the core transactions they represent. So, if you were to say code your changes in a BDC instead of the BAPI, you are basically going to be executing the same business logic. So, there is not a time savings there. Your other option is to update the table(s) directly, which SAP does not endorse, nor do I. If the code executes correctly with the desired results, schedule the program to run in background and run it when the system doesn't have as much traffic, perhaps at night.</P><P></P><P></P><P></P><P>Hope this helps,</P><P></P><P>Regards,</P><P>Satish....</P></BODY></HTML> Sat, 22 Dec 2007 13:32:09 GMT Former Member 2007-12-22T13:32:09Z BAPI_SALESORDER_CHANGE https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/3204961#M764031 <HTML><HEAD></HEAD><BODY><P>I was requested a program that updates Sales Order partners. I did this using BAPI_SALESORDER_CHANGE and the PARTNERCHANGES table. It works fine in DEV but in QA and later in PRD, the number of Sales Orders being updated can be huge. Foreground processing leads to time-outs. BAPIs aren't known for speedy updates but does anyone have any tips/techniques for speeding these things up?</P></BODY></HTML> Sat, 22 Dec 2007 08:10:38 GMT https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/3204961#M764031 Former Member 2007-12-22T08:10:38Z Re: BAPI_SALESORDER_CHANGE https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/3204962#M764032 <HTML><HEAD></HEAD><BODY><P>Hi,</P><P></P><P>Probably repeating things that you may know, but BAPI's, as their definition implies, have the same typical business logic behind them as the core transactions they represent. So, if you were to say code your changes in a BDC instead of the BAPI, you are basically going to be executing the same business logic. So, there is not a time savings there. Your other option is to update the table(s) directly, which SAP does not endorse, nor do I. If the code executes correctly with the desired results, schedule the program to run in background and run it when the system doesn't have as much traffic, perhaps at night.</P><P></P><P></P><P></P><P>Hope this helps,</P><P></P><P>Regards,</P><P>Satish....</P></BODY></HTML> Sat, 22 Dec 2007 13:32:09 GMT https://community.sap.com/t5/application-development-and-automation-discussions/bapi-salesorder-change/m-p/3204962#M764032 Former Member 2007-12-22T13:32:09Z