VF02: abap error after clicking release

[Former Member]

Hi gurus,

I'm doing SD billing. After billing doc is created via VF01, i tried to release the billing document to get the FI/CO documents created, but the error occurred, paste log as following

Runtime Errors         SAPSQL_INVALID_FIELDNAME
Exception              CX_SY_DYNAMIC_OSQL_SEMANTICS


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.

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
    "RKE_BESKZ" 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
    keywords:

    "SAPSQL_INVALID_FIELDNAME" "CX_SY_DYNAMIC_OSQL_SEMANTICS"
    "SAPLV61Z" or "LV61ZU01"
    "SEL_KONDTAB"


Information on where terminated
    Termination occurred in the ABAP program "SAPLV61Z" - in "SEL_KONDTAB".
    The main program was "SAPMV60A ".

    In the source code you have the termination point in line 709
    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
     declared
    in the RAISING clause of its signature.

    The procedure is in program "SAPLV61Z "; its source code begins in line
    266 of the (Include program "LV61ZU01 ".

Source Code Extract

Line  SourceCde

  679                  up to 1 rows
  680                  where kappl  = se_kappl
  681                  and   kschl  = se_kschl
  682                  and   datbi >= se_date
  683                  and   datab <= se_date
  684                  and   (coding_tab).
  685           h_subrc = sy-subrc.
  686         else.
  687           select * from (t681-kotab) appending table <cond_tab>
  688                  where kappl  = se_kappl
  689                  and   kschl  = se_kschl
  690                  and   datbi >= se_date
  691                  and   datab <= se_date
  692                  and   (coding_tab).
  693         endif.
  694
  695         if select_split ne 0 and h_subrc ne 0.
  696           modify coding_tab from coding_alter index select_split.
  697           select * from (t681-kotab) appending table <cond_tab>
  698                  up to 1 rows
  699                  where kappl  = se_kappl
  700                  and   kschl  = se_kschl
  701                  and   datbi >= se_date
  702                  and   datab <= se_date
  703                  and   (coding_tab).
  704         endif.
  705       endif.
  706     else.
  707       if t681-ksdat is initial.
  708         if not <entrytab> is assigned.
">>>>>           select * from (t681-kotab) appending table <cond_tab>
  710                  where kappl  = se_kappl
  711                  and   kschl  = se_kschl
  712                  and   (coding_tab).
  713         else.
  714           select * from (t681-kotab) appending table <cond_tab>
  715                  for all entries in <entrytab>
  716                  where kappl  = se_kappl
  717                  and   kschl  = se_kschl
  718                  and   (coding_tab).

can anyone tell me what should this problem be?

TIA.

Any responses will be awarded,

Regards,

Samson

[alex_zheng · Accepted solution]

Hi Samson,

In most cases, this problem occurs because of the fact that one tries to delete a condition table (which is referred to in an access sequence) before removing this table from the access sequence itself. An other possibility is that the referring access sequence is not generated yet and that the system already tries to use it while the entries in the corresponding table aren't there yet.

Please check this customizing in tx V/05, V/06 and V/07.

What you need to do is:

***********************

1. find out the access sequence which is used.

2. check all the fields in each access of the access sequence

3. Make sure that all the fields in 2. above exist in asscess sequence

table to which condition type is assigned.

4. delete the access which contains fields not in T681-KOTAB.

Regards,

Alex

[Lakshmipathi]

I believe the error comes due to some problem in pricing. You can check some of the following notes.

1) 549164

2) 398553

3) 387408

4) 1259298

5) 1072012

6) 558411

7) 504501

😎 599404

9) 638113

What I also feel is that in debugging mode, you once again do the same process and check with your ABAPer where exactly the problem is. He / she can definitely find out the root cause.

thanks

G. Lakshmipathi

[Former Member]

Hi, consult ur abaper and get the following checked. ur problem is solved.

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

The main program was "SAPMV60A ".

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

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

declared

in the RAISING clause of its signature.

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

266 of the (Include program "LV61ZU01 ".

hope this will help u

sadanandam kasarla

[Former Member]

Hi sadanandam,

thanks for your reply,

i've gone thru that program and checked the program which is purely sap standard without any changes by our abaper.

previously this problem occurred because of the condition table is not generated. i generated following condition tables, and system worked well for some while. but the problem occurred again, and whatever i did can not let system work well again. pls help.

TCD TABLE

V.N3 600

OV06 511

OV06 521

OV17 800

OV17 801

Rrds,

samson