'BAPI_GOODSMVT_CREATE' takes more time for creating material document

[Former Member]

Hi Experts,

I m using 'BAPI_GOODSMVT_CREATE' in my custom report, it takes more time for creating Material documents.

Please let me know if there is any option to overcome this issue.

Thanks in advance

Regards,

Leo

[yuri_ziryukin]

What do you mean with "it takes more time"? More than what?

Normally the performance of standard BAPI (especially as old as this one) is already optimized and issues occur either due to the data volumes or to the improper usage of the BAPI.

[Former Member]

Hi,

Actually, once the BAPI process is success, I have used 'BAPI_Transaction_commit' with wait = 'X'.

So it is taking around 10 secs to update all the relevant tables like MSEG and LTAK.

Please let me know how to optimize this.

Thanks in advance.

Regards,

Leo

[Former Member]

Hi,

please check if some of following OSS notes are not valid for your problem:

[Note 838036 - AFS: Performance issues during GR with ref. to PO|https://service.sap.com/sap/support/notes/838036]

[Note 391142 - Performance: Goods receipt for inbound delivery|https://service.sap.com/sap/support/notes/391142]

[Note 1414418 - Goods receipt for customer returns: Various corrections|https://service.sap.com/sap/support/notes/1414418]

The other idea is not to commit each call, but executing commit of packages e.g. after 1000 BAPI calls.

But otherwise, I am afraid you can not do a lot about performance of standard BAPI. Maybe there is some customer enhancement which is taking too long inside the BAPI, but this has to be analysed by you. To analyse performance, just execute your program via tr. SE30.

Regards

Adrian

[yuri_ziryukin]

Hello Leo,

do you really need to wait for the COMMIT to finish? Are you accessing newly saved entries later in your program? If not - you can remove the "WAIT" flag and in that case your program will trigger the COMMIT without waiting for it to finish.

Otherwise I'm afraid you'll need to trace the program and analyze the performance of the update task.

Regards,

Yuri

[eduardo_hinojosa]

Hi Leo,

Do a trace with ST05 as Yuri suggests. Futhermore, check how your system updates LIS. Check in tcode SM50 if you have any kind of bottleneck with tables Sxxx (where xxx are numbers). It's not usual, but also check if your system is updating COPA documents.

I hope this helps you

Regards

Eduardo

[former_member202771]

Leo, were you able to find the cause and resolve it ?

Thanks,

Anil