topic Re: ABAP DUMP in Application Development and Automation Discussions

ABAP DUMP

adigha1524_6 — Tue, 05 Oct 2021 11:42:49 GMT

I made a change to add field and pull data in report, I didn't get any error in dev system but I got such error in live system. what could be the reason.

Re: ABAP DUMP

former_member660513 — Tue, 05 Oct 2021 11:55:14 GMT

If you look at the last sentence in the screenshot, it says it. The ABAP code in the report is obvously building a dynamic Open SQL statement( a SELECT ?), probably the code is concatening a string that will then sent to the database, and this string contains too many selections/is too long. In Open SQL there are restrictions on the size and number of selection field values( for example in a SELECT statement ) .

Re: ABAP DUMP

Sandra_Rossi — Tue, 05 Oct 2021 12:13:28 GMT

SAPSQL_STMNT_TOO_LARGE happens if the user selects too many criteria values or if the program does the same. You may only reduce the risk, not eliminate it.

See more:

Re: ABAP DUMP

Dominik_Tylczynski — Tue, 05 Oct 2021 15:56:53 GMT

Another common cause of SAPSQL_STMNT_TOO_LARGE is SQL with FOR ALL ENTRIES IN with a large internal table.

Re: ABAP DUMP

matt — Tue, 05 Oct 2021 16:09:50 GMT

You really prefix a FORM name with f_? What else could it be? You do know that no new development should use Forms. They're obsolete.

Re: ABAP DUMP

former_member39056 — Tue, 05 Oct 2021 20:23:44 GMT

You can have an idea of length of generated SQL by having look into "Database Interface Information" in ST22.

Then you can calculate which parameter caused the issue, and limit of number of conditions for the parameters.