Performance issue while create billing doc or invoice

[Former Member]

Hi All,

The program SAPLXEDF contains the include LXEDFU02 which includes the user exit EXIT_SAPLVEDF_002.

We have implemented the above mentioned user exit which is used for updated the segments of IDOC.

However, this user exit is triggering multiple times raising the performance issue. Please provide us an alternative way to update the IDOC segments of Billing doc.

Thanks

With Regards

Tirumula Rao Chinni

[eduardo_hinojosa]

Hi,

Surely you know Note 562193 - EDI: Filling segments in customer function '002'. If you doesnt know, read it, I think that it's relevant:

"As the system calls the CUSTOMER FUNCTION for each qualifier, use the CHECK_XFELD or CHECK_YFELD commands and the relevant queries to make sure that your qualifier is only filled once for each segment. "

You have a sample of coding for include ZXEDFU02 in this note.

I hope this helps you

Regards

Eduardo

[Former Member]

Thanks Eduardo.

Your comments are very helpful to me, once again thanks.

However the issue is while create billing document it is showing the success message,

even if the document is doesn't exist physically.

The created document is able view after 15 to 20 mins, may after proceeding EDI segments.

Could we commit the billing document first? So the user can view in system after immediate the success message appears.

Thanks,

With Regards

Tirumula Rao Chinni

Edited by: Tirumula Rao Chinni on Feb 3, 2011 5:45 PM

[eduardo_hinojosa]

Hi,

I think that you have problems of performance.

Check these notes to find the bottleneck:

Note 118743 - Collective note performance in SD

Note 1166340 - Performance during release to Accounting

Note 103212 - Bad performance during SD document update

and related notes.

If you are using COPA, see

Note 553626 - FAQ Note Profitability Analysis (CO-PA)

Note 74486 - INFO: Overview of consulting notes for CO-PA

In the other hand, it'd be good to do a trace with ST05 with a little example. Perhaps you have a bottleneck in a enhancement, BADI or VOFM subroutine.

During the billing, check the SM50 and try to detect a bottleneck (if you see the process a lot of time with a table). If you see that the bottleneck is in NRIV see Note 678501 - System stoppage, locks on table NRIV and related notes.

If you are using SIS, check how you are updating the infostructures. See Note 204130 - SIS update: Collective note.

Check too locks with SM12 while users are billing. The result of SM13 perhaps helps you.

My suggestion is split taskes, invoice, after release FI documents (tcode VFX3) and finally the output messages.

I hope this helps you

Regards

Eduardo