BASIS Report Custom development ALV report

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

  • SE03 Transport Organizer Tools. The object search tool shows the requests of one object; it does not compare all open requests in bulk.
  • SE10 Transport Organizer. Lists requests by owner and status; it does not show object overlaps between requests.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
E070Transport Request and Task HeadersRequest and task header: type, status, owner, date, target system (driving table)—ECC + S/4
E071Object Entries of Transport RequestsObject list of the requestE071-TRKORR = E070-TRKORRECC + S/4
E07TShort Texts of Transport RequestsRequest descriptionE07T-TRKORR = E070-TRKORR AND E07T-LANGU = SY-LANGUECC + S/4
TADIRDirectory of Repository ObjectsPackage and original system of the objectTADIR-PGMID = 'R3TR' AND TADIR-OBJECT = E071-OBJECT AND TADIR-OBJ_NAME = E071-OBJ_NAMEECC + S/4
TLOCKChange and Transport System: Lock TableRequest currently holding the repository lockTLOCK-OBJECT = E071-OBJECT AND TLOCK-TRKORR = E070-TRKORRECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_TRKORRTransport requestRange / multipleE070-TRKORRNoDEVK9*
S_AS4USRRequest ownerRange / multipleE070-AS4USERNo—
S_AS4DATLast changed onRange / multipleE070-AS4DATENo01.09.2026 – 17.11.2026
S_DEVCLPackageRange / multipleTADIR-DEVCLASSNo—
S_OBJECTObject typeRange / multipleE071-OBJECTNoPROG, CLAS, TABL
P_RELDAYReleased requests to include (last N days)Single value—No30
P_OPENONOnly objects in at least two open requestsCheckbox—No—

Output columns

#ColumnSource
1Program IDE071-PGMID
2Object typeE071-OBJECT
3Object nameE071-OBJ_NAME
4PackageTADIR-DEVCLASS
5RequestE070-TRKORR
6DescriptionE07T-AS4TEXT
7OwnerE070-AS4USER
8StatusE070-TRSTATUS
9Last changedE070-AS4DATE
10Target systemE070-TARSYSTEM
11Locking requestTLOCK-TRKORR
12Requests containing objectCalculated Number of different requests carrying the same R3TR object
13RiskCalculated Two open requests: Medium; released + open: High; different owners: +1 level

Sample output

Program IDObject typeObject namePackageRequestDescriptionOwnerStatusLast changedTarget systemLocking requestRequests containing objectRisk
R3TRPROGRM_SALES_COMMISSIONSD_REPORTSDEVK904512Commission report: region filterGYILDIZD11/14/2026QASDEVK9045122High
R3TRPROGRM_SALES_COMMISSIONSD_REPORTSDEVK904388Commission report: currency fixOAKINR11/05/2026QAS2High
R3TRTABUT001WDEVK904530New plant 3000HKURTD11/16/2026QAS2Medium
R3TRTABUT001WDEVK904533Plant address updateHKURTD11/16/2026QAS2Medium
A view built with fictional sample data; not real system data.

How does the report work?

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Package and original system are added from TADIR, the request holding the repository lock from TLOCK and the request description from E07T.
  6. 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

BASIS Report Custom ALV report

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 …

TBTCO · TBTCP · TRDIRT

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.

Related report: Objects Overlapping in Open Transport Requests Report