Review: make table choices explain themselves

Table category, keys, and row-processing syntax should follow the actual access pattern. A concise expression can be useful, but a safe missing-row policy and clear mutation boundary matter more than minimizing lines of code.

The interactive quiz below uses original questions and explains each answer. It checks knowledge in the browser; it does not execute ABAP.

Sources

• SAP Samples: Internal Tables
• SAP Samples: Internal Tables — Grouping

Developer practice · ABAP

Practice: complex internal table knowledge check

Answer these original review questions about internal-table design and processing.

1. Which table category supports access by both index and key?

STANDARD or SORTEDHASHED onlyOnly an ABAP database table

2. What is a hashed table's primary key required to be?

UniqueEmptyA database index

3. What can happen when a table expression finds no row?

It can raise CX_SY_ITAB_LINE_NOT_FOUNDIt always returns the first rowIt creates a missing row

4. When does ASSIGNING make sense in a loop?

When intentionally modifying the current table lineWhen the source table is in a databaseWhen the loop should create a new table

5. What is a secondary key useful for?

An additional access path when measured usage justifies its costMaking all reads constant-timePersisting the internal table

6. What must be true before using FILTER with a key?

The source table has a compatible sorted or hashed keyThe table has no keyEvery row must be unique

7. Why add a tie-breaker to a sort?

To define a predictable order for rows with equal primary sort valuesTo change a standard table into a hashed tableTo avoid declaring a line type

8. Does GROUP BY require matching rows to be adjacent beforehand?

No; grouping forms groups by the specified keyYes, every table must first be sortedOnly for hashed tables

Check answers

Choose one answer for each question.