FB01 or FB60

Question

Hi all,
While posting invoice i.e FB01,fb60 and FB70 with tax code getting below dump and without tax code we are not getting dump.
untime Errors         SAPSQL_INVALID_FIELDNAME
xcept.                CX_SY_DYNAMIC_OSQL_SEMANTICS
ate and Time          30.11.2011 19:06:31
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
    "WERKS" does not exist in any of the database tables from the FROM clause.
Missing RAISING Clause in Interface
    Program                                 SAPLV61Z
    Include                                 LV61ZU01
    Row                                     260
    Module type                             (FORM)
    Module Name                             SEL_KONDTAB
Trigger Location of Exception
    Program                                 SAPLV61Z
    Include                                 LV61ZU01
    Row                                     701
    Module type                             (FORM)
    Module Name                             SEL_KONDTAB
Please let us know  the reason for the same.
Thanks
Chinna

Answer 1

HI,
The error you are facing is usually caused by one of the
following reasons:
1. Inconsistencies in your access sequences and condition tables.
2. Program error in SEL_KONDTAB.
To rule out the program error possibility, please implement the
corrections from the following SAP Note:
  #1493481 - Short dump for multiple-value access and access type "A"
In case the problem persists after that, it might be related to the
following actions:
1. Deleting a condition table (which is referred to in an access
   sequence) before removing this table from the access sequence itself.
2. Using an access sequence which is not generated yet, so the system
   already tries to use it while the entries in the corresponding table
   aren't there yet.
Please check this customizing in transactions V/05, V/06 and V/07. In
order to solve this problem, please follow these steps:
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 found in step 2 exist in access
   sequence table to which condition type is assigned.
4. Delete the access which contains fields not in T681-KOTAB.
Please carry out the above actions and redo the test.
Regards
Madhu M