Product/Topic: EDIFACT – ORDRSP (D.01B)
Article Link: https://help.truecommerce.com/en/articles/16257771-edifact-ordrsp-d-01b-purchase-order-response
The EDIFACT Order Response (ORDRSP) (D.01B) message is a United Nations (UN) standard Electronic Data Interchange (EDI) message used by a seller to respond to a buyer's Purchase Order or Purchase Order Change Request (ORDCHG). It communicates whether the order is accepted, rejected, or accepted with amendments — both at the overall message level and at the individual line-item level.
Understanding the structure of the ORDRSP message is important when configuring, mapping, or troubleshooting Purchase Order Response transactions within your EDI setup. The D.01B release includes an expanded segment group structure over earlier versions, supporting a wider range of line-level response actions including quantity variances, substitutions, amended pricing, delivery scheduling, and acceptance with changes across both the header and detail sections.
Transaction Overview
Field | Value |
Standard | EDIFACT |
Message Type | ORDRSP |
Version / Release | D.01B |
Controlling Agency | UN (United Nations) |
Purpose | Purchase Order Response |
Message Structure
The ORDRSP message is divided into three primary sections: Header, Detail, and Summary.
Header Section
Contains message identification, dates, references, parties, tax and currency information, payment terms, transport, packaging, scheduling, pricing, allowances and charges, and regulatory requirements. This section establishes the full context of the seller's response to the Purchase Order.
Detail Section
Contains individual line-item responses — the specific goods or services being responded to, including confirmed quantities, amended pricing, quantity variances, substitutions, taxes, allowances, scheduling, and related line-level information.
Summary Section
Contains section control, message-level totals, control totals, allowance and charge summaries, and the message trailer that closes and validates the Purchase Order Response.
Message Function Behavior
The BGM segment carries the message function code that defines the overall intent of the response. The following codes are used in ORDRSP (D.01B):
Function Code | Description |
12 | Not processed — message received and understood but not yet processed by the seller application |
27 | Not accepted — seller declines the order or requested order change |
28 | Accepted with amendment in heading section |
29 | Accepted without amendment |
30 | Accepted with amendment in detail section |
34 | Accepted with amendments in both heading and detail sections |
Required Segments
The following segments are required in every ORDRSP (D.01B) message.
Segment | Description |
UNH | Message Header — identifies the message as ORDRSP D.01B UN |
BGM | Beginning of Message — includes response type, function code, and reference number |
DTM | Date/Time/Period — at least one occurrence; identifies the order response date |
UNS | Section Control — separates the Detail and Summary sections |
UNT | Message Trailer — closes the transaction and verifies segment count |
Note: CNT (Control Total) is conditional in the base D.01B standard, not mandatory. Trading-partner implementation guides may impose stricter requirements than the base standard.
Header Segments
The segments in the following table appear in the Header section and provide supporting information about the Purchase Order Response.
Segment | Description |
PAI | Payment Instructions |
ALI | Additional Information |
IMD | Item Description |
FTX | Free Text Notes |
GIR | Related Identification Numbers |
Segment Groups
Segment Groups (SG) are logical groupings of related segments within the ORDRSP (D.01B) message.
Segment Group | Name | Key Segments |
SG1 | References | RFF, DTM |
SG2 | Adjustment Details | AJT, FTX |
SG3 | Parties | NAD, LOC, FII |
SG4 | Party References | RFF, DTM |
SG5 | Party Documents | DOC, DTM |
SG6 | Contact Information | CTA, COM |
SG7 | Duty/Tax/Fee Details | TAX, MOA, LOC |
SG8 | Currencies | CUX, PCD, DTM |
SG9 | Payment Terms | PAT, DTM, PCD, MOA |
SG10 | Transport Information | TDT |
SG11 | Transport Locations/Dates | LOC, DTM |
SG12 | Delivery Terms | TOD, LOC |
SG13 | Packaging | PAC, MEA |
SG15 | Equipment / Handling | EQD, HAN, MEA, FTX |
SG16 | Scheduling Conditions | SCC, FTX, RFF |
SG19 | Allowances / Charges | ALC, ALI, DTM |
SG25 | Requirements and Conditions | RCS, RFF, DTM, FTX |
Detail Section — Purchase Order Response Line Items (SG26)
The SG26 loop contains the individual line-item response details of the Purchase Order Response. Each iteration of the Line Item (LIN) segment represents one line item being responded to. The LIN segment carries the line-level action request code, which determines how the seller is responding to that specific line.
Line-Level Segments
Segment | Description |
LIN | Line Item — identifies the line item and carries the line-level action request code |
PIA | Additional Product Identification — alternate product codes and identifiers |
IMD | Item Description — free-form or coded description of the item |
MEA | Measurements — physical measurements associated with the line item |
QTY | Quantity — confirmed or amended quantities for this line item |
QVR | Quantity Variances — communicates a variance from the originally ordered quantity |
MOA | Monetary Amount — monetary amounts per line item |
DTM | Date/Time/Period — confirmed or amended dates associated with the line item |
GIN | Goods Identity Number — serial or batch numbers for goods |
DOC | Document/Message Details — line-level document references |
FTX | Free Text — additional free-text notes at the line level |
Line-Level Response Codes
The following action codes are carried on the LIN segment and define the seller's response for each individual line item:
Code | Description |
4 | No action |
5 | Accepted without amendment |
6 | Accepted with amendment |
7 | Not accepted |
10 | Not found |
11 | Not amended / transmitted for information or positioning |
Line-Level Segment Groups
The following segment groups support individual line-item responses within the SG26 loop:
Segment Group | Name | Key Segments |
SG27 | Product Characteristics | CCI, CAV, MEA |
SG28 | Payment Terms | PAT, DTM, PCD, MOA |
SG29 | Adjustment Details | AJT, FTX |
SG30 | Price Details | PRI, CUX, APR, RNG, DTM |
SG31 | References | RFF, DTM |
SG32 | Packaging | PAC, MEA, QTY, DTM |
SG35 | Destination / Quantity | LOC, QTY, PCD, DTM |
SG36 | Duty/Tax/Fee Details | TAX, MOA, LOC |
SG37 | Line-Level Parties | NAD, LOC, FII |
SG41 | Allowances / Charges | ALC, ALI, DTM |
SG47 | Transport Information | TDT |
SG49 | Delivery Terms | TOD, LOC |
SG51 | Scheduling Conditions | SCC, FTX, RFF |
SG53 | Requirements and Conditions | RCS, RFF, DTM, FTX |
SG54 | Stages / Amortization | STG |
SG55 | Stage Quantities and Amounts | QTY, MOA |
Summary Section
The Summary Section closes out the ORDRSP message and provides control and totals information:
UNS — Separates the Detail section from the Summary section
MOA — Provides conditional message-level monetary totals
CNT — Provides conditional control totals for the message
SG56 — Provides allowance and charge summaries (ALC, ALI, MOA)
UNT — Closes the transaction and verifies segment count
Implementation Notes
Important: This article describes the base UN/EDIFACT D.01B ORDRSP structure. It is not a substitute for a trading partner-specific specification guide.
The BGM message function code and LIN action request codes together determine whether the response is a simple acknowledgement, a rejection, or an amended response. When mapping or testing, validate trading partner-specific qualifiers, code lists, repetition limits, and envelope requirements in addition to the base D.01B structure.
Additional Resources
rev. 08/07/26