Mass bill EA26 batch job taking long time

[Former Member]

Hi All,

Mass bill batch job (T code EA26) is taking long time. We deleted entries from EITERDK table for simulation document and reversal invoices as these are not suppose to be printed. After deletion of these entries, Mass bill batch job is taking longer time to complete. Previously it was completing in 20 mins and after deletion of entries in EITERDK its taking more than 30 mins.

Thanks in advance.

Regards

Santosh

[Former Member]

Hi Santosh,

I think you mustn't delete entries from EITERDK because this table is used by EA26 as index to print bills.

Moreover, simulation document or reversal invoices are not printed so It is not necessary to delete theses lines.

I you want to remove / not select some bills you have to make filter on EITR (with FAEDN for example)

Regards,

Mathieu

[william_eastman]

Santosh:

A few things.

• REASIMDEL program is available to delete table entries from simulation documents.
• EITERDK table is the trigger table for printing, not invoicing, and should not have meaningful impact on the invoicing process.
• Have you checked your parallel processing intervals?  is there one which is taking longer than others OR are all of them taking longer?  It could be that more work is required. It could be that a change was made which forces more work during invoicing, e.g. clearing, interest, dunning

Please look at those and eliminate them as causes.

regards,

bill.

[Former Member]

Santosh, whats your scenario?:

1)      are you in go-live process and you are having the firsts invoicing process executions?

2)      … or your production process performance suddenly got slow?

If 1- scenario applies to you, you have to find the correct balance in the technical settings for your invoicing performance. Like any other mass activity, this is done by defining:

• the proper interval size
• the required load distribution (servers-jobs, blocksize)

These definitions may vary from one business to other due the business size itself and the nature of the billing schema of each business. The definition of the load distribution (servers x jobs, block size) must be done by or with your system administrator due these are a limited resource. Also when you start or schedule a process of this kind you must be sure that there are the enough free batch-workprocess to attend the load distribution definition.

Here is an example: In CompanyA to assure the daily load of 65.000bills got invoiced in the average expected time of 20minutes, the technical settings of the tx. EA26 are set to: IntervalSize=1000, load distribution=8x15 (serversXjobs) and a blocksize=1000.

If 2- scenario is your condition, then functionally changes have been done or there is a change on the process infrastructure.

The Log settings may cause a performance variation, more log messages may require more time.

PD: Please don’t delete EITR entries!!