X12 transaction guide · Ordering

EDI 517 Material Obligation Validation

The X12 document used to verify the continued need for open orders, confirm quantities and priorities, and request reinstatement of orders.

Sent by
Supply system or requisitioner
Received by
Requisitioner or supply system
Standard
ANSI ASC X12

What is an EDI 517?

The EDI 517 Material Obligation Validation is the ANSI X12 transaction set used to verify the continued need for open orders, confirm open order quantities and priorities, and request reinstatement of orders cancelled in error, among other functions.

In large supply systems, orders can stay open for months while items are backordered. Periodic validation asks requisitioners whether they still need each item, so stock is not shipped to units that no longer need it and scarce items go to real demands.

How the EDI 517 worksDiagram of the EDI 517 Material Obligation Validation. Supply system or requisitioner sends it to requisitioner or supply system. It usually follows 511. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BR (Beginning Segment for Material Management). 3 optional loops are listed by their first segment.How the EDI 517 worksMaterial Obligation Validation: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS511RequisitionEDI 517SENDERSupply system orrequisitionerRECEIVERRequisitioner or supplysystem997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code MVGS … GETransaction set 517ST … SEHEADINGBRBeginning Segment for Material Management+ 2 optional loops, starting with:LMN1DETAIL+ 1 optional loop, starting with:QTYBlue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 517. Your trading partner's implementation guide adds its own requirements.
How the EDI 517 worksDiagram of the EDI 517 Material Obligation Validation. Supply system or requisitioner sends it to requisitioner or supply system. It usually follows 511. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BR (Beginning Segment for Material Management). 3 optional loops are listed by their first segment.How the EDI 517 worksMaterial Obligation Validation: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWS511RequisitionEDI 517SENDERSupply systemor requisitionerRECEIVERRequisitioner orsupply system997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code MV (GS … GE)Transaction set 517 (ST … SE)HEADINGBRBeginning Segment forMaterial Management+ 2 optional loops, starting with:LMN1DETAIL+ 1 optional loop, starting with:QTYBlue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 517. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 517, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 517 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Validating open backorders
  • Confirming quantities and priorities
  • Requesting reinstatement of cancelled orders

Where it fits in the document flow

Usually follows 511 Requisition
This document 517 Material Obligation Validation
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 517 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BR
  • LM
  • LQ
  • N1
  • QTY
  • FA1
  • FA2
  • SE

Practical example

The 517 in practice

A central supply system has 200 backordered requisitions for a unit. It sends the unit a 517 listing the open orders and asking it to confirm each. The unit confirms 150, cancels 45 no longer needed and changes the priority of five, and the supply system updates its backorders.

Implementation

Implementation considerations for the 517

  • Respond to validation requests within the deadline.
  • Cancel orders that are no longer needed.
  • Keep priorities aligned with actual needs.
  • Reconcile validated orders with local records.

Related transactions

Related ordering documents

All 13 ordering documents

Need help with the EDI 517?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.