Skip to Content
Sep 30, 2014 at 09:33 AM



Hi Friends,

Need your suggestion.

We see dumps with error “SAPSQL_INVALID_FIELDNAME’’ from last two weeks in Production .

These dumps are capture with a system user id , while performing something in Marketing area.

User ID: system user , might be the process performing from WEB ( Online mode ).

We don’t have any idea on process steps how these dumps are occurring.

We implemented a note 1762464 related to similar dump but still we see dumps , daily count more than 200 in Production system for the same user.

If you have any clue on this , please share .

thank you in advance. Please let us know if more details are needed.



Dump data as follows:

Category ABAP Programming Error
ABAP Program %_T012YL
Application Component Not Assigned
Date and Time 30.09.2014 08:58:10

Short text
A dynamically specified column name is unknown.

What happened?
Error in the ABAP Application Program

The current ABAP program "%_T012YL" had to be terminated because it has
come across a statement that unfortunately cannot be executed.

What can you do?
Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.

Error analysis
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_DYNAMIC_OSQL_SEMANTICS', was
not caught in
procedure "DYNAMIC_SELECTION" "(FORM)", nor was it propagated by a RAISING
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:
An Open SQL clause was specified dynamically. The contained field name
"UP" does not exist in any of the database tables from the FROM clause.

How to correct the error

Check the field name in the SELECT clause.

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

"%_T012YL" or "%_T012YL"

If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

2. Corresponding system log

Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File

3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More

4. Details about the conditions under which the error occurred or which
actions and input led to the error.

The exception must either be prevented, caught within proedure
"DYNAMIC_SELECTION" "(FORM)", or its possible occurrence must be declared in
RAISING clause of the procedure.
To prevent the exception, note the following: