cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

STRING_SIZE_TOO_LARGE dump while running SAPLTREX_EXT_PE programme in backround

Former Member
0 Kudos
1,164

Hi,

Our programme SAPLTREX_EXT_PE is working fine with low volume datas but it generates ABAP programming error when data volume is high.

part of the dump log is like that:

Category           ABAP programming error
Runtime Errors     STRING_SIZE_TOO_LARGE
ABAP Program                         SAPLTREX_EXT_PE

Application Component             BC-TRX-API

We search Sap notes but couldn't find any solutions that fixes our problem. Remedies about same runtime error STRING_SIZE_TOO_LARGE is typed  but the ABAP programme is different.

In our scenerio RSPLS_PLSEQ_EXECUTE  is submitted in order to run a BPC planing order in backround. There is function in this planing order that

is written by FOX.

System information:

Sap netweaver 7.5 On Hana

BPC embeded is activated

Basis Batch level: 750      02

Please advise me.

best regards.

Accepted Solutions (0)

Answers (1)

Answers (1)

gregor_dieckmann
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Ismail,

check the short dump (the one you have only posted the header information here) in ST22, there you can find more information, e.g. part of the call stack and the an extract of the variables. There you may find the name and program with the string variable that caused the memory dump.

Regards,

Gregor

Former Member
0 Kudos

Hi Gregor,

The log I posted was from st22. We couldn't find any solutions by searching with these keywords.

Best regards

İsmail

gregor_dieckmann
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Ismail,

yes, I know. I wanted to point out that the ST22 dump contains much more information than just the header part you used in the screen shot. In your case this is a generic memory dump. Further down you find other sections, e.g. 'Information on where termination', there you see the a code snippet where the dump was triggered; in addition the section 'Active Calls/Events shows the call stack and in section 'Chosen Variables' one may find the variable name of the string that caused the dump.

From this information experts might guess what happend.

Regards,

Gregor

Ask a Question