Skip to Content
0
Jan 13, 2012 at 07:59 PM

Performance issue on commit work after BAPI_SALESORDER_SIMULATE

521 Views

Hello,

We use FM BAPI_SALESORDER_SIMULATE to gather the prices of all our active materials per active customer to be used by a 3rd party program. The results are inserted or modified into a custom DB table depending on if the customer already exist in the table already.

The program usually takes 7+hrs to run whether or not there was an insertion or modification to the custom table. If we clear the table the program takes 4hrs to run reinsert all of the customer/material prices.

I found that it takes approximately 1 and a half hours to preform the "commit work" even if no modifications are made to the DB table.

Can you suggest a reason why the commit takes so long and if there are any known ways of decreasing the time?

Nicholas

Edited by: Nicholas Archer on Jan 13, 2012 9:00 PM