SAP Transport Request Tables: E070, E071, E07T and Related Fields
This reference lists the key fields of the SAP transport tables E070 (header), E07T (description), E071 (object list), E071K (table keys), E070C (clients) and TADIR (repository directory), plus the fixed values of TRFUNCTION and TRSTATUS. Use it to write SE16N selections or ABAP and SQL reports on transports in any NetWeaver AS ABAP or S/4HANA system.
| Table | Field or value | Meaning | Example value | Typical join or use |
|---|---|---|---|---|
E070 | TRKORR | Request or task number (header key) | DEVK900123 | Key to E07T, E071, E071K, E070C |
E070 | TRFUNCTION | Type of request or task (domain TRFUNCTION) | K | Filter K and W for requests, S, Q, R, X for tasks |
E070 | TRSTATUS | Status of request or task (domain TRSTATUS) | R | Filter D for open work, R for released |
E070 | TARSYSTEM | Transport target of the request (system, or system.client with extended transport control) | QAS | Group open requests by route |
E070 | KORRDEV | Request category: SYST (workbench) or CUST (customizing) | SYST | Split workbench and customizing counts |
E070 | AS4USER | Owner of the request or task | JSMITH | USR02 or USER_ADDR on BNAME |
E070 | AS4DATE / AS4TIME | Date and time of last change (release date once released) | 20261020 / 143005 | Date range filter for release reports |
E070 | STRKORR | Higher-level request: filled on a task, holds its parent request | DEVK900120 | E070 task.STRKORR = E070 request.TRKORR |
E07T | TRKORR + LANGU | Key of the short text table | DEVK900123 / E | E070.TRKORR = E07T.TRKORR and LANGU = sy-langu |
E07T | AS4TEXT | Short description of the request or task | MM: new release strategy | Search requests by description text |
E071 | TRKORR + AS4POS | Object list entry key (request or task plus line number) | DEVK900121 / 000001 | E070.TRKORR = E071.TRKORR |
E071 | PGMID | Program ID: R3TR (whole object), LIMU (sub-object), CORR or R3OB | R3TR | With OBJECT and OBJ_NAME matches TADIR for R3TR entries |
E071 | OBJECT | Object type | PROG, CLAS, TABL, TABU, LIMU METH | TADIR.OBJECT |
E071 | OBJ_NAME | Object name | ZMM_RELEASE_REPORT | TADIR.OBJ_NAME |
E071 | OBJFUNC | Object function: blank (normal), K (entries with keys in E071K), D (delete) and others | K | OBJFUNC = K means read E071K for the keys |
E071 | LOCKFLAG | Lock status of the object in the request | 2 | Find objects still locked in open tasks |
E071K | TRKORR, PGMID, OBJECT, OBJNAME, AS4POS | Key entries for table content objects (TABU, VDAT, CDAT); OBJNAME is the underlying table | DEVK900200, R3TR, TABU, T001W | E071 on TRKORR, E071.OBJECT = MASTERTYPE and E071.OBJ_NAME = MASTERNAME |
E071K | MASTERTYPE / MASTERNAME | Type and name of the parent object the key belongs to (table or view) | TABU / T001W | Tie key lines back to the E071 object |
E071K | TABKEY | Table key of the transported entry, starting with the client for client-dependent tables; may end in * as a generic key | 1001000 (client 100, plant 1000) | Which rows of a customizing table a request moves |
E070C | CLIENT / TARCLIENT | Source client of the request and target client | 100 / 200 | E070.TRKORR = E070C.TRKORR |
E070A | TRKORR + ATTRIBUTE + REFERENCE | Request attributes such as CTS project assignment | SAP_CTS_PROJECT | Report requests by project |
TADIR | PGMID, OBJECT, OBJ_NAME | Repository directory key for every repository object | R3TR, PROG, ZMM_RELEASE_REPORT | E071 R3TR entries |
TADIR | DEVCLASS | Package of the object | ZMM | TDEVC for the transport layer of the package |
TADIR | SRCSYSTEM | Original system of the object | DEV | Find objects whose original is not the development system |
TADIR | AUTHOR | Person responsible for the object | JSMITH | Ownership reports |
TRNSPACE | NAMESPACE | Registered namespaces in the system (for /XYZ/ objects) | /ACME/ | Check a namespace is modifiable before import or development |
TPALOG | TRKORR | tp import history and status per request and target system | DEVK900123 | Check SE11 on your release for the remaining columns |
Domain TRFUNCTION | K / W / T / C | K workbench request, W customizing request, T transport of copies, C relocation of objects without package change | K | E070.TRFUNCTION |
Domain TRFUNCTION | O / E / M | O relocation with package change, E relocation of complete package, M client transport request | O | E070.TRFUNCTION |
Domain TRFUNCTION | S / R / Q / X | Tasks: S development or correction, R repair, Q customizing task, X unclassified task | S | E070.TRFUNCTION on rows with STRKORR filled |
Domain TRSTATUS | D / L / O / R / N | D modifiable, L modifiable and protected, O release started, R released, N released with import protection for repaired objects | D | E070.TRSTATUS |
Requests and tasks both live in E070. A task has STRKORR set to its parent request; a request has STRKORR empty. Objects are recorded on the task, so to list every object of a request join E070 (tasks with STRKORR = request) to E071, and also read E071 for the request itself, which holds the objects after release. Join E070 to E07T on TRKORR and LANGU. Domain fixed values can be checked in SE11 for domains TRFUNCTION and TRSTATUS.
Need a transport release report?
Tell us your landscape and we will send a reviewed SE16N or ABAP selection over E070, E071 and TADIR for your release.
Optional. The tool and every export work without this. No spam.
How the transport tables fit together
E070 is the header: one row per request and one per task, keyed by TRKORR. A task points to its request through STRKORR. E07T holds the short text per language. E071 holds the object list: each line is a PGMID, OBJECT and OBJ_NAME, for example R3TR PROG ZREPORT or LIMU METH for a single class method. When the object is table content (R3TR TABU, VDAT, CDAT) the line has OBJFUNC K and the actual keys sit in E071K with TABKEY. E070C stores source and target client. TADIR is not a transport table but is where you go from an object to its package (DEVCLASS) and original system (SRCSYSTEM).
Worked example: all objects of released workbench requests last month
In SE16N or a query, select E070 with TRFUNCTION = K, TRSTATUS = R and AS4DATE in the month. Join E07T on TRKORR with LANGU = E for the description. For the objects, select E071 where TRKORR is either the request or any task whose STRKORR equals the request. Add TADIR on PGMID, OBJECT and OBJ_NAME to show the package. For customizing requests (TRFUNCTION = W) also read E071K to see which table rows were moved. The result is a release note: request, owner, description, object type and name, package.
- Open requests by owner: E070 TRSTATUS = D and STRKORR empty, group by AS4USER
- Who changed an object: E071 by OBJ_NAME, then E070 for owner and date
- Rows moved for a table: E071K by MASTERNAME = table name
Gotchas
Objects are recorded on tasks, and on release they are merged to the request, so counting only the request rows before release gives zero objects. TRFUNCTION values differ for tasks and requests, so always filter both TRFUNCTION and STRKORR. TARSYSTEM can hold a system plus client (QAS.100) when extended transport control is active. AS4DATE is the last change date, which becomes the release date once the request is released. E071K TABKEY can contain generic keys with an asterisk. And table names stay stable across releases, but field lists of TPALOG and attribute tables vary, so check SE11 before coding against them.
Frequently Asked Questions
Which SAP table stores transport request objects?
E071 stores the object list of each request and task, with PGMID, OBJECT and OBJ_NAME per line. For table content objects with OBJFUNC K, the individual keys of the transported rows are in E071K. Join both to E070 on TRKORR to get owner, type and status.
Which SAP table stores the transport request description?
E07T stores the short text of requests and tasks in the field AS4TEXT, keyed by TRKORR and LANGU. Join it to E070 on TRKORR and the logon language to show descriptions in a request list.
How do I find the tasks of a transport request?
Select E070 where STRKORR equals the request number. Each row returned is a task, with TRFUNCTION S, Q, R or X and its own owner in AS4USER. The request row itself has STRKORR empty.
What do the TRSTATUS values D, L, O, R and N mean?
D is modifiable, L is modifiable and protected, O means release has started, R means released and N means released with import protection for repaired objects. Check the fixed values of domain TRSTATUS in SE11 on your release to confirm.
If you want your team to ask your SAP system who changed what and when, in plain English on your own servers, we can build that over these same tables.
Related Tools
SAP Transport Return Codes Reference (tp RC 0, 4, 8, 12, 16)
Searchable table of SAP transport return codes and the most common RC 8 and RC 12 causes, with the import step, the log to open and the first fix.
SAPHow to Transport Variants, SO10 Texts, Table Entries and Layouts in SAP
One row per SAP object you must add to a request by hand: how to add it, the E071 entry it creates, the request type and the gotcha.
SAPSAP Transport Request Checklist
A step-by-step checklist for creating, releasing and importing SAP transport requests through STMS, with the critical controls flagged.
SAPSAP Transport Request Log Worksheet
An editable log of transport requests with owner, type, target system, release and import status, exportable to Excel.
More SAP tools
See all- SAP Work Process Types and SM50 Status Reference
- SAP GUI Connection Error Codes Reference (88, 10054, 10061)
- SAP NetWeaver Release to SAP_BASIS and Kernel Reference
- SAP Gateway OData Transaction Codes Reference (SEGW, /IWFND/)
- SAP Kernel Upgrade Command Generator (Linux, SAPCAR)
- SAP ABAP Extended Memory and Heap Sizing Calculator
- SAP Gateway OData Service Activation and Transport Checklist
- SAP Solution Manager 7.2 to Cloud ALM Transition Assessment
- SAP Movement Types Reference
Keep exploring
Free tools
- How to Transport Variants, SO10 Texts, Table Entries and Layouts in SAPOne row per SAP object you must add to a request by hand: how to add it, the E071 entry it creates, the request type and the gotcha.
- SAP ECC Data Dictionary and Repository Tables Reference (DD02L, DD03L, T100, E070, TSTC)Which SAP table holds table names, field lists, domain values, messages, transports and transaction codes, with key fields and join paths.
- SAP Gateway OData Service Activation and Transport ChecklistStep by step checks to activate, test and transport an OData service on SAP Gateway, embedded or hub, V2 or V4.