In inserting operations, such as INSERT or APPEND,Īnd in change operations using MODIFY, the secondary table key administration of unique keys is updated immediately In all statements that change the content or structure of an internal table, the internal administration of the secondary table key (hash administration or secondary table index) is updated automatically as follows: SORT, COLLECT, or PROVIDE, secondary keys are not explicitly supported. In statements where these additions have not been introduced, such as The rows to be deleted can be specified using a secondary key. The rows to be modified can be specified using a secondary key. Only a secondary key for the source table can be specified here, onto which multiple rows are appended. The position they are inserted at is determined solely using the primary key and the primary index. Key for the source table can be specified here, from which multiple rows are copied. The processing order and conditions can be controlled using a secondary table key. The rows to be read can be specified using a secondary key. It is set to 0 for access using a hash key. The system field sy-tabix is now filled with reference to the table index used. Using a table key when indexes are specified. The table index used can now also be specified explicitly Keyname can be used to specify the name of the key to be used statically or dynamically.Īt the same time, statements that previously only accessed the primary key have been enhanced so thatĪccess to secondary keys is also possible. The following additions have been introduced for statements that access rows of internal tables: Secondary keys can be specified generically for standalone table types. Technical type attributes of an internal table. The previous table index, which exists only for index tables, becomes the Is created for each sorted secondary key of an internal table. This can be replaced with an alias name in theĮnhanced definition of the primary table key in Release 7.0, EhP2. ![]() At the same time, what was previously the table key became the primary table key, and a predefined name for it, primary_key, was introduced. An internal table can have up to 15 secondary table keys with different Table keys can be defined for internal tables withĪs well as in ABAP Dictionary. ![]() To be able to efficientlyĪccess an internal table with different keys, and to also allow efficient key access to standard tables, secondary table keys were introduced. Also, standard tables were always searched linearly during key access. Any search key could be entered when accessing internal tables, but this was not veryĮfficient. ![]() Previously, each internal table had just one To specify the WHERE condition in a cond_syntax data object dynamically. All rights reserved.įrom Release 7.0, EhP2, the statements LOOP SAP NetWeaver AS ABAP Release 751, ©Copyright 2017 SAP AG.
0 Comments
Leave a Reply. |