Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

problme while creating data in additional data for infotype 1001 with a custom relationship into

Former Member
0 Kudos
239

i have a custom relationship ZNI, which has some additional data which will be stored in a additional table along with link to infotype HRP1001.

While inserting record i getting this error dump.

any help will be appreciated

Category               Error in Database Interface

Runtime Errors         DBIF_RSQL_INTERNAL_ERROR

Date and Time          14.06.2012 23:10:36

here is more description fro ST22

Short text
    Internal error when accessing a table.

What happened?
    The current ABAP/4 program terminated due to
    an internal error in the database interface.

What can you do?
    Note which actions and input led to the error.

    For further help in handling the problem, contact your SAP administrator.

    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
Error analysis
    An internal error in the database interface occurred during access to
    the data of table "/NAKISA/THRADZNH".

    The situation points to an internal error in the SAP software
    or to an incorrect status of the respective work process.

    For further analysis the SAP system log should be examined
    (transaction SM21).

    For a precise analysis of the error, you should supply
    documents with as many details as possible.

How to correct the error
    Start the work process involved and repeat the action that lead to the
    error.
    If the error position is in a program that you can change, you can try
    to create preliminary solution:  Reformulate the database command by
    varying the properties such as individual record access instead of
    input/output via internal tables, the structure of the selection
    conditions (WHERE clause), nested SELECT loops instead of FOR ALL
    ENTRIES and other such variations.

    Please check the entries in the system log (Transaction SM21).
    Check the entries in the developer trace of the work process involved
    (transaction ST11).
    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:

    "DBIF_RSQL_INTERNAL_ERROR" " "
    "SAPLRHAP" or "LRHAPF1K"
    "ADATA_DB"

    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
    (Unconverted)".

    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
    (Unconverted)".

    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
    Utilities->Upload/Download->Download".

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

Information on where terminated
    Termination occurred in the ABAP program "SAPLRHAP" - in "ADATA_DB".
    The main program was "RS_TESTFRAME_CALL ".

    In the source code you have the termination point in line 60
    of the (Include) program "LRHAPF1K".

Source Code Extract

Line  SourceCde

   30         READ TABLE adata_tab WITH KEY i77ar-relat
   31                    BINARY SEARCH TRANSPORTING NO FIELDS.
   32         CHECK sy-subrc EQ 0.
   33         ad_index = sy-tabix.
   34 *        REFRESH ADATA_DB.                                  "ANDUNI
   35
   36         CREATE DATA type_dbtab TYPE                         "ANDUNI
   37                          STANDARD TABLE OF (i77ar-dbtab).   "ANDUNI
   38         ASSIGN type_dbtab->* TO <adata_db>.                 "ANDUNI
   39         ASSIGN adata_db TO <adata_db_wa>                    "ANDUNI
   40                            CASTING TYPE (i77ar-dbtab).      "ANDUNI
   41
   42         DO adata_tab_lines TIMES.
   43           READ TABLE adata_tab INDEX ad_index.
   44           IF sy-subrc GT 0 OR adata_tab-relat NE i77ar-relat.

   45             EXIT.

   46           ENDIF.

   47           IF adata_tab-opera EQ ad_opera.

   48             adata_db-mandt   = rhap_upd_client.

   49             adata_db-adatanr = adata_tab-adatanr.

   50             adata_db-adata   = adata_tab-adata.

   51 *            APPEND ADATA_DB.                               "ANDUNI

   52             APPEND <adata_db_wa> TO <adata_db>.             "ANDUNI

   53           ENDIF.

   54           ad_index = ad_index + 1.

   55         ENDDO.

   56 *        DESCRIBE TABLE ADATA_DB LINES ADATA_DB_LINES.      "ANDUNI

   57         DESCRIBE TABLE <adata_db> LINES adata_db_lines.     "ANDUNI

   58

   59         IF adata_db_lines GT 0.

>>>>>           INSERT (i77ar-dbtab) CLIENT SPECIFIED

   61 *                               FROM TABLE ADATA_DB.        "ANDUNI

   62                                FROM TABLE <adata_db>.       "ANDUNI

   63

   64 *         ----------------------------------------------------- "ANDASSERT

   65           ASSERT ID hrbas_infty_update SUBKEY g_assert_subkey

   66                  FIELDS sy-subrc sy-batch sy-binpt sy-calld sy-host

   67                         sy-dbcnt i77ar-dbtab <adata_db>

   68                  CONDITION sy-subrc = 0.

   69 *         ----------------------------------------------------- "ANDASSERT

   70

   71         ENDIF.

   72       ENDLOOP.

   73 *     Einfügen der neuen ADATANR's in HRIADATANR

   74       DESCRIBE TABLE ins_hriadatanr LINES ins_hriadatanr_lines.

   75       IF ins_hriadatanr_lines GT 0.

   76         INSERT hriadatanr CLIENT SPECIFIED

   77                           FROM TABLE ins_hriadatanr.

   78

   79 *       -----------------------------------------------------   "ANDASSERT

Mani

1 ACCEPTED SOLUTION

Abhijeet-K
Active Participant
0 Kudos
69

Hi Mani,

The error seems to be data related. Can you check the content of table <adata_db> before the INSERT statement? As the statement has CLIENT SPECIFIED in it, I guess, you need to supply the client (sy-mandt), when you are updating this table. If you are not calling this routine directly, see the call stack where it is being filled and supplied.

2 REPLIES 2

Abhijeet-K
Active Participant
0 Kudos
70

Hi Mani,

The error seems to be data related. Can you check the content of table <adata_db> before the INSERT statement? As the statement has CLIENT SPECIFIED in it, I guess, you need to supply the client (sy-mandt), when you are updating this table. If you are not calling this routine directly, see the call stack where it is being filled and supplied.

0 Kudos
69

Thanks Abhijeet, i seen some values in Additiona table structure which i am not passing in. I just recreated the table and it works after that.

Mani