Application Development 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
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

BAPI_SALESORDER_CHANGE

Go to solution
Former Member

‎12-22-2007 8:10 AM

0 Kudos

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?

1 ACCEPTED SOLUTION

Go to solution
Former Member

‎12-22-2007 1:32 PM

0 Kudos

Hi,

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.

Hope this helps,

Regards,

Satish....

1 REPLY 1

Go to solution
Former Member

‎12-22-2007 1:32 PM

0 Kudos

Hi,

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.

Hope this helps,

Regards,

Satish....