Skip to Content
Former Member
Jul 15, 2009 at 06:51 PM

Standard tcode FBL5N dump in pre production.


I am getting a dump when I execute the standard tcode FBL5N (Customer line item) with one company code. FBL5N tcode is not at all giving dump in production system, however it dumps in pre production.

The dump exists in the function module : fdm_local_get_objects_range while executing the SELECT stmt

*SELECT * FROM fdm_dcobj*


WHERE logsys LIKE i_logsys

AND obj_type LIKE i_obj_type

AND obj_key IN it_range_obj_key

AND relation LIKE i_relation

AND case_guid_loc IN it_guid

AND is_confirmed LIKE i_confirmed

AND is_voided LIKE i_voided.

Do I need to search for sap note ?

Below is dump analysis

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in procedure "FDM_LOCAL_GET_OBJECTS_RANGE" "(FUNCTION)", nor was it propagated by

a RAISING clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

The SQL statement generated from the SAP Open SQL statement violates a

restriction imposed by the underlying database system of the ABAP


Possible error causes:

o The maximum size of an SQL statement was exceeded.

o The statement contains too many input variables.

o The input data requires more space than is available.

o ...

You can generally find details in the system log (SM21) and in the

developer trace of the relevant work process (ST11).

In the case of an error, current restrictions are frequently displayed

in the developer trace.

How to correct the error

The SAP Open SQL statement concerned must be divided into several

smaller units.

If the problem occurred due to the use of an excessively large table

in an IN itab construct, you can use FOR ALL ENTRIES instead.

When you use this addition, the statement is split into smaller units

according to the restrictions of the database system used.

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following