E071 table — Transport request object list table

Each row in E071 represents a single object entry attached to a transport request or task header stored in E070. When a developer or functional consultant makes a change and it gets recorded against a request, CTS writes one entry here identifying the object type and name, the function performed on it (insert, delete, etc), and whether it is locked for editing. A request with fifteen changed objects has fifteen rows in E071 sharing the same TRKORR. This table does not tell you whether the request was released or imported into any target system, only that the object was assigned to it at some point in the development system. That information lives elsewhere, in E070 and the import history tables.

Always restrict by MANDANT if the system is multi-client, though in most landscapes development and its requests live in a single client so this rarely changes the result. The table is not huge in most systems but a query without a TRKORR or OBJ_NAME restriction against a system with a long development history will scan a large number of rows. Restrict on OBJECT and OBJ_NAME together when hunting for a specific program or table, since OBJ_NAME alone is not unique across object types. Restricting on TRKORR is the fastest and most common access path since it is the leading part of the key.

To confirm whether a specific program was included in a known transport, select E071 with OBJECT equal to PROG and OBJ_NAME equal to the program name, then check which TRKORR values come back. Cross-check each TRKORR against E070 to see its status and target system. If no rows return at all, the object was never captured in any request in this client, which usually means the change was made directly in a client not meant for development, or was reverted before release.

E071 is unchanged in shape and role on S/4HANA. The Change and Transport System infrastructure carried forward without redesign, and the object list table continues to be written by the same standard tools whenever a developer or functional user assigns a change to a transport request or task. No compatibility view is needed because this is core Basis infrastructure rather than an application table subject to the S/4HANA data model simplification.

This is a Basis or CTS administrator question first, since they own the transport landscape and import history, but the functional or development consultant who made the change is the one who can confirm what object name and type to search for. Disputes about whether a change reached a target system are resolved by combining E071 with the request status in E070 and the actual import log for that system.

E070 is the request header table joined by TRKORR and is the natural first stop after E071. E071K holds Customizing key entries for the same requests when the change is table-content based rather than repository-object based. TADIR provides the current repository status of any object found in E071. Transport requests and tasks are created and released through the standard transport organizer transaction, and objects are assigned to them automatically whenever they are changed in the ABAP Workbench or Customizing.