EDIFACT message guide · Shipping and logistics
ITRRPT In transit report detail
The UN/EDIFACT message that gives a delivery party the details of goods within grouped consignments sent through a grouping center.
- Sent by
- Delivering party, such as a grouping center
- Received by
- Delivery party, such as the consignee
- Standard
- UN/EDIFACT · Batch message
- X12 equivalent
- No direct equivalent
What is the EDIFACT ITRRPT message?
ITRRPT is the UN/EDIFACT in transit report detail message. The directory defines it as a message specifying, to a delivery party, the details of goods within grouped consignments despatched by the delivering party. It is used in a multi-step transport process involving only consignors, grouping centers and consignees.
A grouping center collects goods from several consignors and forwards them together. The in-transit report tells the consignee what is coming from which consignor in each grouped consignment, so receipt can be planned and checked.
How to read this diagram: the top row shows who sends ITRRPT, to whom, and which messages usually come before and after it. The lower part shows what the directory D.21A itself requires: the envelopes around ITRRPT and the segments and segment groups it marks mandatory. Conditional groups are listed by their trigger segment rather than drawn in full. This is the directory's minimum, not a trading partner's requirement: a message implementation guide, such as an industry subset or a partner’s own guide, usually makes some conditional groups mandatory, restricts the codes and may use an older directory.
When it is used
- Reporting goods in a grouped consignment from a grouping center
- Detailing contents from several consignors
- Planning receipt of consolidated deliveries
Where it fits in the message flow
Structure
Mandatory segments in ITRRPT (directory D.21A)
In UN/EDIFACT directory D.21A, the ITRRPT message has 85 segment positions arranged in 25 segment groups. These are the segments and segment groups marked mandatory at message level, in order; a mandatory group is shown with the segment that starts it. Segments inside conditional groups are needed only when the group is used. This is the directory’s requirement, not your trading partner’s: each partner’s message implementation guide names the directory it uses, often an older one such as D.96A or D.01B where the structure can differ, makes some conditional segments mandatory and restricts the codes.
- UNH
- BGM
- SG9 (GEI)
- UNT
Practical example
ITRRPT in practice
A retailer's suppliers deliver to a regional grouping center, which forwards combined loads to the retailer's stores. For each load, the grouping center sends the store an ITRRPT listing the goods from each supplier, with order references and quantities. The store checks the delivery against the report and confirms receipt.
Implementation
Implementation considerations for ITRRPT
- Keep consignor and order references in the report for each item.
- Send the report before the grouped consignment arrives.
- Reconcile receipts with the report and the consignors' despatch advices.
- Agree the role of the grouping center with all parties.
How ECOM helps
Automate ITRRPT with ECOM
Industry
Retail
Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.
Industry
3PL and Warehousing
Warehouse orders, shipping advice, receipts and inventory reporting between brands, 3PLs, carriers and retailers.
Solution
Logistics Automation
Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.
Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.
Related messages
Related shipping and logistics messages
Need help with ITRRPT?
ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.