972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

EDIFACT message guide · Ordering

ORDCHG Purchase order change request

The UN/EDIFACT message a buyer sends to request changes to, or cancellation of, a purchase order already sent.

Sent by
Buyer
Received by
Seller or supplier
Standard
UN/EDIFACT · Batch message
X12 equivalent
860 Purchase Order Change Request

What is the EDIFACT ORDCHG message?

ORDCHG is the UN/EDIFACT purchase order change request message. The directory defines it as a message from the buyer to the seller, specifying details of the buyer's request to change a purchase order. Changes can add, cancel or alter lines, or change header data such as dates and delivery locations.

Because it is a request, the seller confirms or rejects the change, usually with an ORDRSP. Some partners prefer to resend a complete ORDERS with a replacement function code instead of using ORDCHG, so the change method is an important part of any agreement.

How the EDIFACT ORDCHG message worksDiagram of the UN/EDIFACT ORDCHG Purchase order change request message. Buyer sends it to seller or supplier. It usually follows ORDERS. It is usually followed by ORDRSP. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: UNS (Section control). 17 conditional segment groups are listed by their trigger segment.How the EDIFACT ORDCHG message worksPurchase order change request: who sends it, where it fits and what the directory marks mandatory1 WHERE IT FITSUSUALLY FOLLOWSORDERSPurchase orderORDCHGSENDERBuyerRECEIVERSeller or supplierCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYORDRSPPurchase orderresponse2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDsUNB … UNZMessage ORDCHGUNH … UNTSTART OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSUNSSection control+ 17 conditional groups, starting with:RFFAJTNADTAXCUXPYTTDTTODPACEQDSCCAPRALCRCSEFILINBlue box: mandatory segment group. Conditional groups are listed by the trigger segment that starts them; a group is sent only when its data applies.Conditional segments outside groups are not drawn.Structure: mandatory segments and groups in the UN/EDIFACT directory D.21A listing for ORDCHG. Your trading partner's implementation guide adds itsown requirements.
How the EDIFACT ORDCHG message worksDiagram of the UN/EDIFACT ORDCHG Purchase order change request message. Buyer sends it to seller or supplier. It usually follows ORDERS. It is usually followed by ORDRSP. Inside the UNB and UNH envelopes, the directory D.21A requires, in the start of message: BGM (Beginning of message) and DTM (Date/time/period) and body and segment groups: UNS (Section control). 17 conditional segment groups are listed by their trigger segment.How the EDIFACT ORDCHGmessage worksPurchase order change request: who sends it,where it fits and what the directory marksmandatory1 WHERE IT FITSUSUALLY FOLLOWSORDERSPurchase orderORDCHGSENDERBuyerRECEIVERSeller orsupplierCONTRL syntax report back, if agreedUSUALLY FOLLOWED BYORDRSPPurchase order response2 WHAT DIRECTORY D.21A REQUIRESInterchange: sender and recipient IDs(UNB … UNZ)Message ORDCHG (UNH … UNT)START OF MESSAGEBGMBeginning of messageDTMDate/time/periodBODY AND SEGMENT GROUPSUNSSection control+ 17 conditional groups, starting with:RFFAJTNADTAXCUXPYTTDTTODPACEQDSCCAPR…Blue box: mandatory segment group. Conditionalgroups are listed by the trigger segment thatstarts them; a group is sent only when its dataapplies. Conditional segments outside groups arenot drawn.Structure: mandatory segments and groups in theUN/EDIFACT directory D.21A listing for ORDCHG.Your trading partner's implementation guide adds itsown requirements.

How to read this diagram: the top row shows who sends ORDCHG, 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 ORDCHG 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.

Expand diagram Download SVG

When it is used

  • Changing quantities or delivery dates on an open order
  • Adding or cancelling order lines
  • Cancelling a whole order

Where it fits in the message flow

Usually follows ORDERS Purchase order
This message ORDCHG Purchase order change request
Usually followed by ORDRSP Purchase order response

Structure

Mandatory segments in ORDCHG (directory D.21A)

In UN/EDIFACT directory D.21A, the ORDCHG message has 185 segment positions arranged in 60 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
  • DTM
  • UNS
  • UNT

Practical example

ORDCHG in practice

A fashion retailer moves a promotion forward by a week. Its buying system sends an ORDCHG to the garment supplier for the affected order, bringing the delivery date forward and increasing two lines. The supplier checks capacity and replies with an ORDRSP accepting the date and one increase but not the other.

Implementation

Implementation considerations for ORDCHG

  • Agree whether changes use ORDCHG or a replacement ORDERS.
  • Identify each changed line with the original line number.
  • Agree a cut-off for changes, such as despatch, and how later changes are handled.
  • Process the supplier's response before treating the change as accepted.

How ECOM helps

Automate ORDCHG with ECOM

Solution

Order-to-Cash Automation

Automate the flow from purchase order to payment across every customer channel.

Solution

Procure-to-Pay Automation

Automate purchasing, receiving and supplier invoicing across EDI, portals and documents.

Industry

Retail

Retail and eCommerce EDI for suppliers and retailers, from purchase order to payment, with compliance built in.

Compare X12 and EDIFACT, or see answers to general questions in the EDI FAQ.

Related messages

Related ordering messages

All 7 ordering messages

Need help with ORDCHG?

ECOM maps, tests and monitors EDIFACT messages for your trading partners and integrates them with your ERP.

Request a Demo Contact us