BASIS Report Custom development ALV report

Failed IDocs Aging Report by Partner and Message Type

Short answer: A custom ALV report that lists inbound and outbound IDocs in an error status or waiting too long for processing, with partner, message type, last status message and age in hours, and counts the IDocs failing with the same error. In the morning the integration team sees on one screen which error is piling up at which partner and starts with the oldest IDoc.

Estimated effort
M · 4–6 working days
System
ECC and S/4HANA
Tables
4
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

WE02/WE05 list IDocs by status and date and BD87 offers reprocessing; but neither calculates the age of an IDoc in hours, groups and counts IDocs with the same error message for the same partner and message type, or flags IDocs stuck in status 30 or 64 for too long. Emailing the error summary to the partner owner is not available either.

Who uses it? Integration and EDI teams, BASIS support and business units exchanging orders, invoices or delivery notes by IDoc.

Closest standard alternatives

  • WE02 Display IDoc. Lists IDocs by status and date; no age, count of the same error or flag for stuck IDocs.
  • BD87 Status Monitor for ALE Messages. Reprocesses failed IDocs; it does not give an error summary per partner or email distribution.

Tables used

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

TableRoleJoinSystem
EDIDCIDoc Control RecordIDoc control record: status, direction, message type, partners, creation time (driving table)—ECC + S/4
EDIDSIDoc Status RecordsIDoc status records: last error message and dateEDIDS-DOCNUM = EDIDC-DOCNUMECC + S/4
EDP21Partner Profile: InboundInbound partner profile: process codeEDP21-SNDPRN = EDIDC-SNDPRN AND EDP21-SNDPRT = EDIDC-SNDPRT AND EDP21-MESTYP = EDIDC-MESTYPECC + S/4
EDP13Partner Profile: Outbound (Technical Parameters)Outbound partner profile: receiver port and basic typeEDP13-RCVPRN = EDIDC-RCVPRN AND EDP13-RCVPRT = EDIDC-RCVPRT AND EDP13-MESTYP = EDIDC-MESTYPECC + S/4

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_CREDTCreation dateRange / multipleEDIDC-CREDATYes10.11.2026 – 17.11.2026
S_STATIDoc status (blank = error list)Range / multipleEDIDC-STATUSNo51, 56, 02, 29
S_MESTYMessage typeRange / multipleEDIDC-MESTYPNoORDERS, INVOIC, DESADV
S_SNDPRNSender partnerRange / multipleEDIDC-SNDPRNNo—
S_RCVPRNReceiver partnerRange / multipleEDIDC-RCVPRNNo—
P_STUCKAdd IDocs stuck in status 30 and 64Checkbox—NoX
P_MINAGEStuck threshold (hours)Single value—No2
P_SUMMShow partner + message type + error summaryCheckbox—No—

Output columns

#ColumnSource
1IDoc numberEDIDC-DOCNUM
2DirectionEDIDC-DIRECT
3StatusEDIDC-STATUS
4Message typeEDIDC-MESTYP
5Basic typeEDIDC-IDOCTP
6Sender partnerEDIDC-SNDPRN
7Receiver partnerEDIDC-RCVPRN
8Created onEDIDC-CREDAT
9Created atEDIDC-CRETIM
10Last status dateEDIDS-LOGDAT
11Message classEDIDS-STAMID
12Message numberEDIDS-STAMNO
13Status textEDIDS-STATXT
14Age (hours)Calculated Now − EDIDC-CREDAT/CRETIM
15IDocs with same errorCalculated Number of IDocs in the same partner + message type + STAMID/STAMNO group

Sample output

IDoc numberDirectionStatusMessage typeBasic typeSender partnerReceiver partnerCreated onCreated atLast status dateMessage classMessage numberStatus textAge (hours)IDocs with same error
0000000004812345251ORDERSORDERS05EDI_ANADOLUNKDCLNT10011/15/202608:14:2211/15/2026V1382Material FG-5003 is not defined for the sales organization4914
0000000004812402251INVOICINVOIC02TEDARIK_DELTANKDCLNT10011/16/202622:40:1011/16/2026M8321Invoice amount out of tolerance; item blocked113
0000000004812450102DESADVDELVRY07NKDCLNT100LOJ_MARMARA11/17/202601:05:0011/17/2026E0028Error passing to port; RFC destination not reachable827
0000000004812471256DEBMASDEBMAS07CRM_SISTEMNKDCLNT10011/17/202606:30:4511/17/2026E0400Inbound partner profile not found31
A view built with fictional sample data; not real system data.

How does the report work?

  1. IDocs in error statuses within the selected creation date range are read from EDIDC: outbound 02, 04, 05, 25, 26, 29; inbound 51, 56, 60, 61, 63, 65 (the list is configurable).
  2. Depending on the selection, stuck IDocs are added: status 30 (outbound, ready for dispatch) and 64 (inbound, ready to be processed) older than the hour threshold.
  3. The status record with the highest counter (COUNTR) of each IDoc is read from EDIDS: message class (STAMID), message number (STAMNO), first variable (STAPA1), status text and date.
  4. Age (hours) = now − CREDAT/CRETIM. The number of IDocs in the same partner + message type + STAMID/STAMNO group is calculated.
  5. The process code is added from EDP21 for inbound IDocs and the port from EDP13 for outbound IDocs; IDocs without a partner profile are flagged separately.
  6. In summary mode one row = partner + message type + error; in detail mode one row = IDoc. Double-clicking the IDoc number opens WE02, an action button opens BD87 for the selected IDocs.

Performance notes

Narrow EDIDC by status and creation date and use the index on the status field. Read EDIDS only for the selected IDocs with FOR ALL ENTRIES and pick the latest record in ABAP. Data segments (EDID4) are not read. On systems with heavy EDI traffic, limit the date range to 7 days.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants
  • Double-click drill-down to the document Double-clicking the IDoc number opens WE02; selected IDocs are passed to BD87.
  • Export to Excel
  • Runs as a background job
  • Send the result by email The error summary per partner is sent to the partner owner defined in the settings table.

Authorization objects

  • S_IDOCMONIIDoc monitoring: display by message type and partner
  • S_IDOCCTRLAccess to the IDoc control record and partner profiles

Frequently asked questions

Does the report reprocess IDocs automatically?

No, the report only lists and passes the selected IDocs to BD87. Reprocessing should be a deliberate decision, for example after master data has been corrected. If needed, a scheduled automatic retry for specific error messages can be added as a separate job.

Is the business data inside the IDoc shown?

The basic version reads only control and status records; order or invoice segments are not read. This keeps the report fast and only monitoring authorization is needed.

Can it be used on S/4HANA as well?

Yes. EDIDC, EDIDS and the partner profile tables are the same in S/4HANA. Even when integration comes through middleware (e.g. SAP Integration Suite), the report covers it as long as it is processed as an IDoc.

Packages that include this solution

BASIS Package Custom

Basis Daily System Check Pack

A five-component pack that turns the Basis team's morning check into one list: cancelled and long-running background jobs, scheduled jobs running …

5 components · v1.0

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: Failed IDocs Aging Report by Partner and Message Type