Objects Overlapping in Open Transport Requests Report
Short answer: A custom ALV report that lists cases where the same program, table, class or customizing object is contained in more than one transport request, with request owner, status, description and package. Before an import into production, the risk of moving changes in the wrong order or taking an unfinished change live becomes visible in advance.
- Estimated effort
- M · 4–6 working days
- System
- ECC and S/4HANA
- Tables
- 5
- Scope
- Global
- Built by
- NeKuDos Teknoloji
- Last updated
Why is the standard not enough?
The object search tool in SE03 shows which requests contain an object, but it works one object at a time; SE10 lists requests by owner. No standard screen compares the objects of all selected open requests and returns the requests that carry the same object in one list. Teams do this check by hand before a release or skip it. The custom report finds overlaps automatically and assigns a risk level.
Who uses it? BASIS and release management teams, ABAP development leads and the change advisory board (CAB).
Closest standard alternatives
Tables used
The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.
| Table | Role | Join | System |
|---|---|---|---|
| E070Transport Request and Task Headers | Request and task header: type, status, owner, date, target system (driving table) | — | ECC + S/4 |
| E071Object Entries of Transport Requests | Object list of the request | E071-TRKORR = E070-TRKORR | ECC + S/4 |
| E07TShort Texts of Transport Requests | Request description | E07T-TRKORR = E070-TRKORR AND E07T-LANGU = SY-LANGU | ECC + S/4 |
| TADIRDirectory of Repository Objects | Package and original system of the object | TADIR-PGMID = 'R3TR' AND TADIR-OBJECT = E071-OBJECT AND TADIR-OBJ_NAME = E071-OBJ_NAME | ECC + S/4 |
| TLOCKChange and Transport System: Lock Table | Request currently holding the repository lock | TLOCK-OBJECT = E071-OBJECT AND TLOCK-TRKORR = E070-TRKORR | ECC + S/4 |
Selection screen parameters
| Parameter | Description | Type | Reference field | Required | Example |
|---|---|---|---|---|---|
| S_TRKORR | Transport request | Range / multiple | E070-TRKORR | No | DEVK9* |
| S_AS4USR | Request owner | Range / multiple | E070-AS4USER | No | — |
| S_AS4DAT | Last changed on | Range / multiple | E070-AS4DATE | No | 01.09.2026 – 17.11.2026 |
| S_DEVCL | Package | Range / multiple | TADIR-DEVCLASS | No | — |
| S_OBJECT | Object type | Range / multiple | E071-OBJECT | No | PROG, CLAS, TABL |
| P_RELDAY | Released requests to include (last N days) | Single value | — | No | 30 |
| P_OPENON | Only objects in at least two open requests | Checkbox | — | No | — |
Output columns
| # | Column | Source |
|---|---|---|
| 1 | Program ID | E071-PGMID |
| 2 | Object type | E071-OBJECT |
| 3 | Object name | E071-OBJ_NAME |
| 4 | Package | TADIR-DEVCLASS |
| 5 | Request | E070-TRKORR |
| 6 | Description | E07T-AS4TEXT |
| 7 | Owner | E070-AS4USER |
| 8 | Status | E070-TRSTATUS |
| 9 | Last changed | E070-AS4DATE |
| 10 | Target system | E070-TARSYSTEM |
| 11 | Locking request | TLOCK-TRKORR |
| 12 | Requests containing object | Calculated Number of different requests carrying the same R3TR object |
| 13 | Risk | Calculated Two open requests: Medium; released + open: High; different owners: +1 level |
Sample output
| Program ID | Object type | Object name | Package | Request | Description | Owner | Status | Last changed | Target system | Locking request | Requests containing object | Risk |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| R3TR | PROG | RM_SALES_COMMISSION | SD_REPORTS | DEVK904512 | Commission report: region filter | GYILDIZ | D | 11/14/2026 | QAS | DEVK904512 | 2 | High |
| R3TR | PROG | RM_SALES_COMMISSION | SD_REPORTS | DEVK904388 | Commission report: currency fix | OAKIN | R | 11/05/2026 | QAS | 2 | High | |
| R3TR | TABU | T001W | DEVK904530 | New plant 3000 | HKURT | D | 11/16/2026 | QAS | 2 | Medium | ||
| R3TR | TABU | T001W | DEVK904533 | Plant address update | HKURT | D | 11/16/2026 | QAS | 2 | Medium |
How does the report work?
- Requests and tasks in the selection are read from E070 (TRFUNCTION: K workbench, W customizing and their tasks); tasks are linked to their parent request (STRKORR). By default, modifiable requests (TRSTATUS D) and requests released (R) in the last N days are included.
- The objects of each request are read from E071. LIMU sub-objects (for example REPS, METH, TABD) are mapped to their R3TR object, so different parts of the same program count as the same object.
- Objects are grouped; if two or more requests carry the same object, an overlap is written. Customizing table contents are compared on table level without going into the E071K keys.
- Risk: Medium if both requests are open; High if one is released and the other is open (if the older version is imported later, it can overwrite the newer change); one level higher if the requests belong to different developers.
- Package and original system are added from TADIR, the request holding the repository lock from TLOCK and the request description from E07T.
- The result is shown in ALV grouped by object; double-clicking the request number opens SE09/SE10.
Performance notes
Narrow E070 by date, user and status; read E071 only for the selected requests with FOR ALL ENTRIES. For very large customizing requests, comparison on table level is enough; key-level comparison can be kept as an optional extension.
Features
- ALV list (sort, filter, subtotals)
- User-specific layout variants
- Double-click drill-down to the document Double-clicking the request number displays it in SE09.
- Export to Excel
- Runs as a background job
- Send the result by email The overlap list can be sent before the weekly release meeting.
Authorization objects
- S_TRANSPRTDisplay authorization for transport requests
Frequently asked questions
Is the report run in the production system?
No, it runs in the development system, because open requests and their object lists are kept there. Which requests have been imported into production comes from the STMS import queue and can be added to the report in a second phase.
Do different methods of the same class count as an overlap?
Yes. LIMU sub-objects (for example methods of a class) are mapped to their R3TR object; if two methods of the same class were changed in two requests, it is listed as an overlap and the sub-objects are shown in the detail.
Are customizing overlaps visible as well?
Yes, customizing requests are read too. The basic version compares on table level, so different keys in the same table also appear as an overlap. Key-level comparison can be added as an extension.
Related reports
Cancelled and Long-Running Background Jobs Report
A custom ALV report that lists background jobs that were cancelled, are still running or finished far above their usual runtime, with the step …
Let us build this report for your system
Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.