E071K table — Transport request key entries for table content

One row in E071K represents one recorded key of a table entry that was included in a transport request or task at the point a customizing change was saved and the table maintenance tool captured it for transport with row-level granularity, rather than as a whole-table object. This happens for tables flagged for key-based transport recording in the table maintenance generator. The row does not contain the changed field values themselves, only the key that identifies which row of the target customizing table was touched. The actual before and after values live in the table's own transported data, not in E071K. This table exists purely to let the transport system know precisely which rows of which table to move when the corresponding object entry in E071 points at a table content object rather than a full dictionary object.

Always start from a known TRKORR or a small set of them, this table is not selective on anything else and a full scan on a long-lived system is expensive. MANDT is usually a fixed value since transport control tables are typically maintained client-independently or in client 000, so it rarely helps narrow a selection. TABKEY cannot be filtered on individual key field values because it is one flat padded string, so any filtering on a business key has to happen after fetching rows for the relevant TRKORR and decoding TABKEY using the target table's key layout pulled from the data dictionary. Join to E071 first to confirm the object name before attempting to interpret TABKEY, otherwise the padding and field order will be wrong.

Symptom: a customizing change to one row of a table was made and released, but the target system does not show it after import. Find the request in E070/E071 by object name and object type, note its TRKORR. Select E071K where TRKORR equals that value and check whether an AS4POS matches an E071 entry for the table in question, then decode TABKEY against the table's key fields. No matching entry means the row was never captured into that request, so the fix is in the change recording step, not the import.

E071K is a Basis pool table belonging to the Change and Transport System and is unaffected by the S/4HANA data model changes that touch business tables. It exists in S/4HANA with the same structure and the same role. There is no CDS compatibility view for it because it is infrastructure metadata, not business data, and the transport tooling that reads and writes it has not changed shape across releases.

The Basis or transport team owns this table operationally, since it is written by the transport organizer and table maintenance generator machinery, not by application configuration. Functional consultants only look at it when tracing a specific transport gap for a customizing row, and even then the answer usually comes from the request contents shown in the transport organizer rather than a direct table read.

E071 holds the parent object entry that names the table and object type this key belongs to. E070 is the request or task header, and E070C carries its client attribute. Table maintenance generator screens invoked through table maintenance transactions write these entries automatically when a customizing change is saved with transport recording active, and the transport organizer transactions are where consultants actually inspect and manage the object list rather than querying E071K directly.