Skip to end of metadata
Go to start of metadata


  1. Cluster tables

    • In cluster table the records having the same key are stored in a single key in the cluster. One consequence:
    • DATA l_sdata TYPE EDI_SDATA.
    • SELECT SINGLE sdata
      INTO l_sdata
      FROM edid4
      WHERE docnum = i_edidc-docnum
        AND counter = '000'
        AND segnum = i_edidc-countr
        AND segnam =  SPAN
      Unknown macro: { font-family}
      Unknown macro: { color}
    • If there is an overflow of the data records a continuation record is created with the same table key, the code will trigger a runtime error DBIF_RSQL_INVALID_RSQL / Exception CX_SY_OPEN_SQL_DB. I used this work around
    •   SPAN
      Unknown macro: { font-family}
      Unknown macro: { color}
      Unknown macro: { color}
            SELECT sdata INTO l_sdata UP TO 1 ROWS
              FROM edid4
              WHERE docnum = i_edidc-docnum
                AND counter =  SPAN
      Unknown macro: { font-family}
      Unknown macro: { color}
                AND segnam = 'E1EDL24'.
  2. Unknown User (iorcaj4)

    can we create cluster & poled tables?

  3. Unknown User (f2edt4a)

    What is lock objects?

    A lock object is a virtual link of several SAP tables which is used to synchronize simultaneous access by two users to the same set of data ( SAP lock concept).

    Locks are requested and released in the programming of online transactions by calling certain function modules which are automatically generated from the definition of the lock objects. These lock objects must be explicitly created in the ABAP Dictionary.

    To set locks, you must perform the following steps:

  4. Unknown User (s6tb1nx)

    This is really cool. One can have very good insight in the data dictionary. It really helped me solving some of my interview questions.

    Thanks SDN, thanks Wiki.