X12 transaction guide · Ordering

EDI 511 Requisition

The X12 document used to requisition material and equipment from a supply distribution system for immediate use or for stock.

Sent by
Requisitioning unit or customer
Received by
Supply distribution system
Standard
ANSI ASC X12

What is an EDI 511?

The EDI 511 Requisition is the ANSI X12 transaction set used to requisition material and equipment from a supply distribution system, either for immediate consumption or for stock against projected requirements.

It was developed for large logistics systems, such as military supply chains, where units order parts from a central supply system rather than directly from vendors. Requisitions carry priorities, required delivery dates and fund codes, and their status is followed through the supply process. Status advice follows each requisition.

How the EDI 511 worksDiagram of the EDI 511 Requisition. Requisitioning unit or customer sends it to supply distribution system. It usually starts the exchange. It is usually followed by 527 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BR (Beginning Segment for Material Management) and the required N1 loop with N1 (Party Identification). 2 optional loops are listed by their first segment.How the EDI 511 worksRequisition: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 511SENDERRequisitioning unit orcustomerRECEIVERSupply distributionsystem997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY527Material Due-In andReceipt997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code RNGS … GETransaction set 511ST … SEHEADINGBRBeginning Segment for Material ManagementRequired loop N1 · repeats up to 20N1Party Identification+ 1 optional loop, starting with:LMDETAIL+ 1 optional loop, starting with:LXBlue 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 511. Your trading partner's implementation guide adds its own requirements.
How the EDI 511 worksDiagram of the EDI 511 Requisition. Requisitioning unit or customer sends it to supply distribution system. It usually starts the exchange. It is usually followed by 527 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BR (Beginning Segment for Material Management) and the required N1 loop with N1 (Party Identification). 2 optional loops are listed by their first segment.How the EDI 511 worksRequisition: who sends it, where it fits andwhat the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 511SENDERRequisitioningunit or customerRECEIVERSupplydistributionsystem997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY527Material Due-In and Receipt997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code RN (GS … GE)Transaction set 511 (ST … SE)HEADINGBRBeginning Segment forMaterial ManagementRequired loop N1 · repeats up to20N1Party Identification+ 1 optional loop, starting with:LMDETAIL+ 1 optional loop, starting with:LXBlue 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 511. Your trading partner'simplementation guide adds its own requirements.

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

  • Ordering parts from a central supply system
  • Replenishing unit stocks
  • Requisitioning equipment for projects

Where it fits in the document flow

This document 511 Requisition

Structure

Mandatory segments in the 511 (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
  • LX
  • N9
  • QTY
  • REF
  • FA1
  • FA2
  • SE

Practical example

The 511 in practice

A maintenance unit needs a replacement pump for a vehicle. Its supply system sends a 511 requisition to the central supply system with the part number, quantity, priority and delivery location. The supply system issues the part from a depot and reports its status.

Implementation

Implementation considerations for the 511

  • Use the supply system's part numbers and priority codes.
  • Validate funding before submitting requisitions.
  • Track requisition status through delivery.
  • Cancel requisitions that are no longer needed.

Need help with the EDI 511?

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