topic Re: Performance Issue when Using BAPI in Application Development and Automation Discussions

Performance Issue when Using BAPI

Former Member — Tue, 13 Sep 2011 13:17:25 GMT

Hi All,

We are creating sales order via BAPI. We are expecting around 2000 per file. At the start of the processing, it creates about 20 orders in a minute. However, as the file progresses, the performance is really degrading. It creates about 5-6 orders in a minute. Is there any idea on how to improve the performance? Is it because of the memory allocation used by the BAPI? BAPI_TRANSACTION_COMMIT is used every after SO is created. I have seen that this BAPI is refreshing the buffers used. Will this suffice? How do I free up the memory used by the BAPI each time I create a new order? I am suspecting this has something to do with memory allocation in the BAPI. I have already used the STARTING NEW TASK with the BAPI, on the hope that it will improve the performance.

Any help is appreciated.

Thanks,

Louisse

Edited by: Louisse Heartsdale on Sep 13, 2011 3:17 PM

Re: Performance Issue when Using BAPI

yuri_ziryukin — Tue, 13 Sep 2011 14:01:48 GMT

Hello Louisse,

one possible solution would be to reprogram your sales order creation for parallel processing in separate dialog work processes.

Please refer to this documentation:

http://help.sap.com/saphelp_nw04/helpdata/en/fa/096e92543b11d1898e0000e8322d00/frameset.htm

Kind regards,

Yuri

Re: Performance Issue when Using BAPI

Former Member — Tue, 13 Sep 2011 14:03:52 GMT

Did you doa trace using ST05?

Sure you dont want to modify the BAPI, but still if you find out what takes him so long (probably some of the selects inside), you could get an idea if providing additional info could speed up those selects.

Maybe additional data could help you to hit a index for big selects and so speed up the process.

But until you dont know WHAT exactly is beeing slow, it´s quite hard to generate an idea on how to speed things up.

Re: Performance Issue when Using BAPI

yuri_ziryukin — Tue, 13 Sep 2011 14:18:23 GMT


Did you doa trace using ST05?

Most probably ST05 will not help in this case as I expect the database time to be constant.

Re: Performance Issue when Using BAPI

Former Member — Tue, 13 Sep 2011 14:38:32 GMT

Hi,

Currently, this is already being done in my code:

CALL FUNCTION 'Z_V_BAPI_SO_CREATEFROMDAT2_RFC'

STARTING NEW TASK 'TASK' DESTINATION 'NONE'

PERFORMING bapi_salesorder_create ON END OF TASK

EXPORTING

order_header_in = wa_header

order_header_inx = wa_headerx

logic_switch = wa_bapisdls

TABLES

return = t_return

order_items_in = t_items

order_items_inx = t_itemx

order_partners = t_partners

order_schedules_in = t_schedules

order_schedules_inx = t_schedulesx

order_conditions_in = t_conditions

order_conditions_inx = t_conditionsx

order_text = t_texts

extensionin = t_extensionin.

This will already trigger parallel tasks. But the performance is still the same.

Any inputs?

Thanks,

Louisse

Re: Performance Issue when Using BAPI

Former Member — Tue, 13 Sep 2011 15:43:40 GMT

Hello,

We have had to deal with a requirement to process create 12,000 orders per night, with up to 45,000 on occasions. We used the standard BAPI, BAPI_SALESORDER_CREATE_FROM_DAT2. The process creates about 15 orders a second in batch. Among the techniques we used were:

Chop the data up into 3 sets and have 3 batch jobs running in parallel on the DB server. We were able to do this as the batch load on the machine is low at the time these jobs run. We call BAPI_TRANSACTION every 100 orders.

We did extensive run time analysis of the BAPI, BAPI_SALESORDER_CREATE_FROM_DAT2 and found that program exits were doing unnecessary extra reads of tables such as KNA1 when the front end program calling the BAPI was already doing this.

We found the BAPI spent time calling routines that weren't needed (eg. LIS and Inbound Deliveries). We were unable to see how to switch these off, nor did we want to go 'inside' the BAPI to use the internal FM that SAP would use the create the sales order.

The sales orders were very simple (no more than 5 lines), but most were rush orders meaning that we were creating a delivery as well.. There was no availability checking.

Re: Performance Issue when Using BAPI

volker_borowski2 — Tue, 13 Sep 2011 18:59:54 GMT

Hi,

starting fast and getting slower suggests (sorry if some of these sound stupid, I am just brainstorming here):

- File being read from the beginning each time.

- intermediate result being selected into internal table in a loop and not cleared for next iteration (table gets bigger each loop)

- SAP - enqueues not released fast enough causing contention

Second thing:

Your calling new tasks with customer function module and call the BAPI as end-of task.

How do you keep track, that all started childs have finished?

Shouldn't you call a customer function on end-of-task to count down that alll tasks are finished

so that your memory is not released too early...

...build packages

loop at packages

increase counter

start new task with package (end-of task -> call customer fm, that does processing and decreases counter)

endloop

wait until counter = 0

Volker

Re: Performance Issue when Using BAPI

Former Member — Wed, 14 Sep 2011 02:09:34 GMT

Hi Volker,

Can you provide more context on this? I am not familiar how to do your suggestion.

Thanks,

Louisse

Re: Performance Issue when Using BAPI

yuri_ziryukin — Wed, 14 Sep 2011 06:45:49 GMT


Hi Volker,
> 
> Can you provide more context on this? I am not familiar how to do your suggestion.
> 
> Thanks,
> Louisse

Hello Louisse,

this is all described in the SAP documentation which I linked in my first reply.

This is just the way to control the number of parallel tasks that you kicked off.

Actually I don't see any reasons of slowing down if you work with parallel tasks (+ controlling the number of simultaniously running tasks) and properly passing all parameters to the BAPI.

If all of it is already present, then you'll have to do a series of ST12 (ABAP+SQL) trace to see where the time is spent and what functions continuously consume more and more time.

Refer to the blog of Hermann Gahm regarding ST12: /people/hermann.gahm/blog/2010/03/22/st12-150-tracing-user-requests-tasks-http

Regards,

Yuri

Re: Performance Issue when Using BAPI

Former Member — Thu, 15 Sep 2011 21:02:21 GMT

Hi Yuri,

Let me provide you more details of the program. First BAPI call is to create the sales order. Afterwhich, we have to update the created SO with the partner function Payer. This was not included in the creation of SO since if the Header and Line Item Payer is different, this will result to an error in the BAPI. Afterwhich the payer is updated, we need to update the Billing Date for the SO again. So in one order creation, there are 3 calls to BAPI.

I have nailed down the issue. When I go to change the SO, at times it is still locked after the BAPI_TRANSACTION_COMMIT. So I've used the ENQUEUE and DEQEUEUE for SO. However, using the ENQUEUE_EVVBAKE causes performance issues. SO I've tried removing it, and just leave DEQUEUE_EVVBAKE, since my goal is toreally check if the SO is still locked before I start making changes again. However, it didn't work. SO I had to put in the ENQUEUE FM again. Is there any other way that I can check whether the SO is still locked before I start making the changes?

Thanks,

Louisse

Re: Performance Issue when Using BAPI

yuri_ziryukin — Fri, 16 Sep 2011 08:31:54 GMT

Hello Louisse,

the problem of this particular BAPI is that the document is "saved" and you cannot change it in memory before the data is committed. This is not the way for example in newer SAP products like CRM.

Therefore I would like to offer you 2 solutions.

Solution 1 - change to batch input. And in batch input simulate the change of the payer and billing date like you are in VA01 transaction. This should be possible without actually saveing and committing the document inbetween.

Please note that batch input will have overhead for the PBO/PAI processing and at the end you may end up with approximately the same speed.

Solution 2 - do not work sales order by sales order doing 3 operations, instead do 1st operation for ALL sales orders, then do your second operation for all of them, then third.

Thus you'll make sure that there are no locking issues. However you have to be more careful concerning error handling.

Regards,

Yuri

Re: Performance Issue when Using BAPI

Former Member — Mon, 19 Sep 2011 01:44:19 GMT

Hi Yuri,

2 points based on your suggestions.

1. I am not aware of any BAPI or FM to mass change sales order. So am not sure how to carry out this change

2. We can't have the changes done at a later timing. We need the created SO to be changed as soon as possible. So I am not sure am not gonna go with this approach.

As far as other forums, the BAPI_TRANSACTION_COMMIT is supposed to clear all the buffers used by the BAPI. But I don't know why even if this BAPI is used, it seems the buffer memory of BAPI is still not freed.

Thanks for your input.

Regards,

Louisse

Re: Performance Issue when Using BAPI

Former Member — Mon, 19 Sep 2011 09:58:44 GMT

Maybe there are not enough processes for executing update requests?

Maybe you can try to put the command "SET UPDATE TASK LOCAL" at the beginning of your FM 'Z_V_BAPI_SO_CREATEFROMDAT2_RFC'?

Edited by: Carsten Grafflage on Sep 19, 2011 12:28 PM

Re: Performance Issue when Using BAPI

Former Member — Tue, 20 Sep 2011 18:41:51 GMT

Hi Louisse,

Probably a silly question but... are you refreshing your bapi tables after each call?

Re: Performance Issue when Using BAPI

Former Member — Wed, 21 Sep 2011 06:07:39 GMT

Hi,

Of course I refresh my internal tables. I even used FREE instead of refresh.

Thanks,

Louisse

Re: Performance Issue when Using BAPI

Former Member — Wed, 21 Sep 2011 06:08:28 GMT

Hi Carlsten,

What does this command do?

Thanks,

Louisse

Re: Performance Issue when Using BAPI

Former Member — Wed, 21 Sep 2011 07:47:41 GMT

Well, I couldn't explain it better than the documentation: http://help.sap.com/abapdocu_70/en/ABAPSET_UPDATE_TASK_LOCAL.htm

Regards,

Carsten

Re: Performance Issue when Using BAPI

Former Member — Wed, 21 Sep 2011 08:05:14 GMT

Hi Carsten,

Sorry for asking this, but would you know what's gonna be the impact if I have more than a thousand records, and then I am calling the BAPI for 1000 times as well, and I'm setting each call to local task? Will that not disrupt the flow of the program? Sorry, as I haven't used the command before.

Thanks,

Louisse

Re: Performance Issue when Using BAPI

Former Member — Wed, 21 Sep 2011 08:20:35 GMT

Hi,

OK sorry for the stupid question...;) another one however: Have you tried to use parameter WAIT of the BAPI_TRANSACTION_COMMIT?

Otherwise could you paste your main loop section here?

Kr,

Manu.

Re: Performance Issue when Using BAPI

Former Member — Wed, 21 Sep 2011 09:00:29 GMT

Let's say you have only two update processes, but you start four parallel worker processes, then two of them have always to wait for their turn (if you have to use COMMIT WORK AND WAIT). But if you use SET UPDATE TASK LOCAL, each of the parallel processes can perform his own update, without the need of the update processes. This can possibly lead to a higher system load, but may be faster.