Invoice cancellation issues

[former_member125661]

We have a strange situation where we have an invoice with over 40000 line items and we are trying to get this invoice cancelled in production.

/n VF11 times out in foreground. We created a Wrapper program that calls the BAPI_BILLINGDOC_CANCEL1. It worked for a whole. But lately this also fails - 'Internal session terminated with runtime error EXPORT_TOO_MUCH_DATA (see ST22) ' error.

This is the ST22 log :

  Termination occurred in the ABAP program "SAPLMCS6" - in

   "MCV_STATISTICS_INVOICE".

  The main program was Z******..

  In the source code you have the termination point in line 657

  of the (Include) program "LMCS6U04".

  The program "SAPLMCS6" was started as a background job.

Can we somehow skip this FM call MCV_STATISTICS_INVOICE in debug mode in prod ? Not sure what this function module does. Can this be skipped during the BAPI_BILLINGDOC_CANCEL1 call ? Any tips is welcome.

Thanks,

S

[former_member125661]

Guys.We tried all the above . Finally, SAP suggested us to skip 'MCV_STATISTICS_INVOICE’ in debug mode and increased the dialog timeout period from 10 mins to 1 hours and that did the trick. We canceled this invoice with 40000 line items.

[eduardo_hinojosa]

Hi

It's related with the update of SIS (sales information system). Can you copy or upload the dump? Check also the tcode SM13.

Regards

Eduardo

PD: I forgot, surely it is a SIS updated syncronous.

[former_member125661]

Here is the ST22 dump.

[eduardo_hinojosa]

Hi

Try to do it again when you are alone in the system, perhaps there was a strong concurrence of users/processes in the system, before to do new settings in the system.

I hope this helps you

Regards

Eduardo

[eduardo_hinojosa]

Hi

I forgot it. Run tcode MCVV for the original invoice and check what happens. It tells you what SIS tables will be updated for this billing document. Do the same with a cancellation invoice.

Regards

Eduardo

[arindam_m]

Hi,

Its a buffer overflow issue. This occurs when data selected exceeds max size of 2GB. If possible please split the input data and process. Should help.

Cheers,

Arindam

[Former Member]

This is something new, i have came across......

I hope the correction are itself given in the dump file you have attached may work for you.

	How to correct the error
	1. Data must be distributed into portions of 2GB
	2. 3 possible solutions:
	- Either increase the sequence counter (field SRTF2) to include INT4
	or
	-export less data
	or
	-distribute the data across several IDs

Regards,

Rahul

[former_member125661]

Guys.We tried all the above . Finally, SAP suggested us to skip 'MCV_STATISTICS_INVOICE’ in debug mode and increased the dialog timeout period from 10 mins to 1 hours and that did the trick. We canceled this invoice with 40000 line items.