cancel
Showing results for 
Search instead for 
Did you mean: 

SQL error "-904" occurred when accessing table "MARA "

Former Member
0 Kudos

Hi Gurus,

i am getting error in ST22  please find the log.

Runtime Errors    DBIF_RSQL_SQL_ERROR
Exception          CX_SY_OPEN_SQL_DB
Date and Time      22.11.2015 10:08:21

Short text

    SQL error 904 occurred when accessing table "MARA ".

What happened?

    One of the columns addressed in a table or view

    does not exist in the database.

    table) exists in the ABAP/4 Dictionary, but not in

    the database.

What can you do?

    If this error occurred in ABAP/4 Open SQL, there is an inconsistency

    between the ABAP/4 Dictionary and the database.

    You can resolve this by converting the table in the database

    to the definition in the ABAP/4 Dictionary.

    To do this, call Transaction SE11 and then select

    Utilities --> Database utility.

    Please make a note of the actions and input which caused the error.

    -

    To resolve the problem, contact your

    SAP system administrator.

    Select the "Print" function to obtain a hardcopy of the

    current termination message.

How to correct the error

    Database error text........: "ORA-00904: "EMP_ADD": invalid identifier"

    Internal call code.........: "[RSQL/READ/MARA ]"

    Please check the entries in the system log (Transaction SM21).

    You may able to find an interim solution to the problem

    in the SAP note system. If you have access to the note system yourself,

    please use the following search criteria:

    "SAPLMG21" "DBIF_RSQL_SQL_ERROR"

    If you cannot solve the problem yourself, please send the

    following documents to SAP:

    1. A hard copy print describing the problem.

       To obtain this, select the "Print" function on the current screen.

    -

    2. A suitable hardcopy prinout of the system log.

       To obtain this, call the system log with Transaction SM21

       and select the "Print" function to print out the relevant

       part.

    3. If the programs are your own programs or modified SAP programs,

       supply the source code.

       To do this, you can either use the "PRINT" command in the editor or

       print the programs using the report RSINCL00.

    4. Details regarding 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

   "SELECT_SINGLE" "(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... "eccidsserver"

    Network address...... "192.168.0.2"

    Operating system..... "Windows NT"

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

    Hardware type........ "4x Intel 801586"

    Character length.... 16 Bits

    Pointer length....... 32 Bits

    Work process number.. 1

    Shortdump setting.... "full"

    Database server... "ECCIDSSERVER"

    Database type..... "ORACLE"

    Database name..... "EC6"

    Database user ID.. "SAPSR3"

    Char.set.... "C"

    SAP kernel....... 700

    created (date)... "Apr 2 2006 23:08:16"

    create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

    Database version. "OCI_10103_SHARE "

    Patch level. 52

    Patch text.. " "

    Database............. "ORACLE 9.2.0.*.*, ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*"

SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"

Memory consumption
Roll.... 8176
EM...... 5226120
Heap.... 0
Page.... 16384
MM Used. 2382520
MM Free. 751520

User and Transaction

Client.............. 811
User................ "BKPP"
Language key........ "E"
Transaction......... "MM01 "
Program............. "SAPLMG21"
Screen.............. "SAPLMGMM 0060"
Screen line......... 51

Information on where terminated

    Termination occurred in the ABAP program "SAPLMG21" - in "SELECT_SINGLE".

    The main program was "SAPMMG01 ".

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

    of the (Include) program "LMG21FSQ".

    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

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

     declared

    in the RAISING clause of its signature.

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

    270 of the (Include program "LMG21FSQ ".

Source Code Extract

Line  SourceCde

  242     spera = mara_sprtab-spera.

  243   ENDIF.

  244

  245 ENDFORM.                               " SPERRMODUS_ERMITTELN

  246

  247 *********************************************************

  248 FORM message_lock.

  249

  250   IF sy-subrc = 01.

  251 *   MESSAGE E022 RAISING LOCK_ON_MATERIAL.  mk/testweise

  252     MESSAGE e022 WITH mara_keytab-matnr sperr_user

  253                                RAISING lock_on_material.

  254   ELSEIF sy-subrc = 02.

  255     MESSAGE e021 RAISING lock_system_error.

  256   ENDIF.

  257

  258 ENDFORM.

  259

  260 *********************************************************

  261 FORM message_not_found.

  262   IF output_no_message IS INITIAL.            "wk/99a

  263     MESSAGE e305 WITH mara_keytab-matnr RAISING not_found.

  264   ELSE.

  265     RAISE not_found.

  266   ENDIF.

  267 ENDFORM.

  268

  269 *********************************************************

  270 FORM select_single.

  271

>>>>>   SELECT SINGLE * FROM mara WHERE matnr = mara_keytab-matnr

  273   .

  274

  275 ENDFORM.

  276

  277 *********************************************************

  278 FORM sperren_mara USING rcode.

  279

  280   CLEAR sy-subrc.

  281   CASE sperrmodus.

  282     WHEN sperrmodus_s.

  283 * Shared Sperre

  284       CALL FUNCTION 'ENQUEUE_EMMARAS'

  285            EXPORTING

  286                 matnr          = mara_keytab-matnr

  287            EXCEPTIONS

  288                 foreign_lock   = 01

  289                 system_failure = 02.

  290       sperr_user = sy-msgv1.           "mk/3.0E

  291     WHEN sperrmodus_e.

Contents of system fields

Name     Val.

SY-SUBRC 8

SY-INDEX 0

SY-TABIX 1

SY-DBCNT 1

SY-FDPOS 0

SY-LSIND 0

SY-PAGNO 0

SY-LINNO 1

SY-COLNO 1

SY-PFKEY MENU

SY-UCOMM

SY-TITLE Create Material (Initial Screen)

SY-MSGTY

SY-MSGID

SY-MSGNO 000

SY-MSGV1

SY-MSGV2

SY-MSGV3

SY-MSGV4

SY-MODNO 1

SY-DATUM 20151122

SY-UZEIT 100821

SY-XPROG SAPCNVE

SY-XFORM CONVERSION_EXIT

Active Calls/Events

No.   Ty.          Program                             Include                             Line

      Name

    8 FORM         SAPLMG21                            LMG21FSQ                              272

      SELECT_SINGLE

    7 FORM         SAPLMG21                            LMG21FSQ                               47

      LESEN_MARA_SINGLE

    6 FUNCTION     SAPLMG21                            LMG21U04                               64

      MARA_SINGLE_READ

    5 FORM         SAPLMG02                            LMG02F00                               57

      LESEN_MARA

    4 FUNCTION     SAPLMG02                            LMG02U03                               45

      READ_MAT_ANKER

    3 MODULE (PAI) SAPLMGMM                            LMGMMI12                               83

      LESEN_MAT_ANKER

    2 FUNCTION     SAPLMGMM                            LMGMMU01                               85

      MATERIAL_MAINTAIN_DIALOGUE

    1 MODULE (PAI) SAPMMG01                            MMG01I01                                9

      START_DIALOG

Internal notes

    The termination was triggered in function "HandleRsqlErrors"

    of the SAP kernel, in line 780 of the module

     "//bas/700_REL/src/krn/runt/absapsql.c#5".

    The internal operation just processed is "SQLS".

    Internal mode was started at 20151122100806.

    ORACLE error ORA-0904:

    "ORA-00904: "EMP_ADD": invalid identifier"

    Internal call code.........: "[RSQL/READ/MARA ]"

Thanks and Regards

Dhananjay Patil

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member207186
Contributor
0 Kudos

Hi,

regarding "ORA-00904:invalid identifier" issue, you can check carefully SAP Note below for troubleshooting:

731 - "Collective note: ORA-00904"

Regards,

Bíborka