b.santos/abap-cheat-sheets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update content

Browse Source
This commit is contained in:
danrega
2023-02-24 15:23:59 +01:00
parent 6e13f60a28
commit e0d61e3d12
4 changed files with 1405 additions and 1012 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
01_Internal_Tables.md
View File

@@ -136,7 +136,7 @@
- are optional for all table categories.
- can be unique/non-unique sorted keys or unique hash keys.
- have a self-defined name. An alias name can also be specified.
- A secondary table index is created internally for each sorted secondary key. This allows index access to hashed tables via the secondary table key is possible. In this case, `sy-tabix` is set.
- A secondary table index is created internally for each sorted secondary key. This allows index access to hashed tables via the secondary table key. In this case, `sy-tabix` is set.
- When accessing internal tables using the secondary table key, the key name (or the alias if specified) must be specified. They are not selected automatically. If no secondary key is specified in a processing statement, the primary key or primary table index is always used. If you want to make use of this key in ABAP statements, for example, `READ`, `LOOP AT` or `MODIFY` statements, you must specify the key explicitly using the appropriate additions, for example, `WITH ... KEY ... COMPONENTS` or `USING KEY`.
- Use cases:
- To improve read performance.
@@ -1416,7 +1416,7 @@ the content are removed, but the memory space initially requested remains
allocated. If the table is filled again later, the memory space is still
available, which is a performance advantag over
clearing an internal table with `FREE`. Such a statement also
deleted the table content, but it also releases the memory
deletes the table content, but it also releases the memory
space.
``` abap