Showing results for 
Search instead for 
Did you mean: 

ABAP run time error

Former Member
0 Kudos

Dear ALL,

When we are creating sales order after entering sold-to-party, Material & Quantity when we press ENTER key That time

we are getting following run time error

Hoe to resolve this?



Date and Time 15.01.2009 16:04:19

Short dump has not been completely stored (too big)

Short text

A dynamically specified column name is unknown.

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLV61Z" 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 "SEL_KONDTAB" "(FORM)", 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:

An Open SQL clause was specified dynamically. The contained field name

"ALAND" 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



"SAPLV61Z" or "LV61ZU01"


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

"SEL_KONDTAB" "(FORM)", or its possible occurrence must be declared in the

RAISING clause of the procedure.

To prevent the exception, note the following:

System environment

SAP-Release 700

Application server... "slgsap-prd"

Network address...... ""

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "8x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "SLGSAP-PRD"

Database type..... "MSSQL"

Database name..... "PRD"

Database user ID.. "prd"

Terminal................. "SD0123l"

Char.set.... "C"

SAP kernel....... 700

created (date)... "May 6 2008 00:13:21"

create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"

Database version. "SQL_Server_8.00 "

Patch level. 159

Patch text.. " "

Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0"

Memory consumption

Roll.... 16192

EM...... 20949200

Heap.... 0

Page.... 196608

MM Used. 15928048

MM Free. 828016

User and Transaction

Client.............. 900

User................ "ADMIN"

Language key........ "E"

Transaction......... "VA01 "

Transactions ID..... "03F0E2DD6B35F16CBBFF002219897F24"

Program............. "SAPLV61Z"

Screen.............. "SAPMV45A 4900"

Screen line......... 930

Information on where terminated

Termination occurred in the ABAP program "SAPLV61Z" - in "SEL_KONDTAB".

The main program was "SAPMV45A ".

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

of the (Include) program "LV61ZU01".

The termination is caused because exception "CX_SY_DYNAMIC_OSQL_SEMANTICS"

occurred in

procedure "SEL_KONDTAB" "(FORM)", but it was neither handled locally nor


in the RAISING clause of its signature.

The procedure is in program "SAPLV61Z "; its source code begins in line

260 of the (Include program "LV61ZU01 ".

Source Code Extract

Line SourceCde

642 if se_prestep = yes or

643 se_read_only_one_record = yes.

644 if t681-ksdat is initial.

645 if se_read_all_prestep is initial.

646 select * from (t681-kotab) appending table <cond_tab>

647 up to 1 rows

648 where kappl = se_kappl

649 and kschl = se_kschl

650 and (coding_tab).

651 h_subrc = sy-subrc.

652 else.

653 select * from (t681-kotab) appending table <cond_tab>

654 where kappl = se_kappl

655 and kschl = se_kschl

656 and (coding_tab).

657 endif.


659 * it is enough to find one record in prestep

660 * (care must be taken with pool tables - depending on database this

661 * will cost performance instead of saving)

662 if select_split ne 0 and h_subrc ne 0.

663 modify coding_tab from coding_alter index select_split.

664 select * from (t681-kotab) appending table <cond_tab>

665 up to 1 rows

666 where kappl = se_kappl

667 and kschl = se_kschl

668 and (coding_tab).

669 endif.

670 else.

671 if se_read_all_prestep is initial.

>>>>> select * from (t681-kotab) appending table <cond_tab>

673 up to 1 rows

674 where kappl = se_kappl



Edited by: Akshay Dalal on Jan 17, 2009 6:25 AM

Edited by: Akshay Dalal on Jan 17, 2009 6:30 AM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Dear Akshay,

First of all, I would recommend to contact your BASIS-Admin.

However, meanwhile, you may analyse ABAP-Short Dump with -

T. Code: ST22 or SM21

Alternatively, It would be much better is your post your query to [Forum: SAP NetWeaver Administrator|;

I think, most genuine solutions would be obtained from there, only.

Best Regards,


Note: You may report the error to SAP, also.

Answers (4)

Answers (4)

Former Member
0 Kudos


Former Member
0 Kudos


Former Member
0 Kudos

Dear ,

Can anybody having solution on this issue



Edited by: Akshay Dalal on Jan 18, 2009 5:38 AM

Former Member
0 Kudos

Dear Akshay,

check your condition types, Access sequence & condition table assigned to it.



Active Contributor
0 Kudos

Dear Akshay,

We will NOT be able to provide you with a solution on this forum, because we have no clue what configuration do you have in your system and what user exits or other custom development may have been done in your specific system.

Lakshmipathi has already correctly pointed to a similar post. You might want to get an ABAPer to set a breakpoint just before the error occurs, then he/she might provide you with more information, which may (or may not) be helpful.

There is obviously something wrong in the pricing condition either on configuration level or in a user exit. If you write to SAP (which you should, because it's a standard program), they will ask to connect to your system, because they don't have any chrystal balls over there either.

Just in case - before going any further, try running the program RV80HGEN (in the test system, of course), which re-generates requirements and formulas. Sometimes it helps, although I doubt that it is the case here.

Also if you've used some custom (Z...) fields in the pricing configuration, that's where the problem is most likely.

Active Contributor
0 Kudos

Dear Akshay

Check this thread and go through the comments of Clemens

[ runtime error |]


G. Lakshmipathi