Requisition
A Requisition transaction set communicates a request for materials, goods, or services from one party to another. Typically sent by a buyer or requisitioning organization to a supplier or fulfillment center, this transaction can be initiated independently or in response to a purchase order, contract, or internal requirement. The BR segment (Beginning Segment for Material Management) establishes the requisition context and direction, while the N1 loop (Name) identifies key parties such as the requester, recipient, and ship-to locations. The LX loop contains line-item details for each requisitioned item, including reference identifications via the N9 segment and specific item data through the PO1 segment.
Consider a manufacturing company, Precision Parts Inc., that needs to requisition components from its approved supplier, Global Distributors Ltd. Precision Parts sends a 511 transaction set specifying 500 steel fasteners, 200 aluminum brackets, and 50 gasket assemblies, each with its own line item in the LX loop. The BR segment indicates this is a formal requisition, the N1 loop identifies Precision Parts as the requester and Global Distributors as the fulfillment center, and the PO1 segments in each LX loop provide catalog numbers and specifications. Global Distributors receives the 511 and uses it to prepare and ship the requested materials to Precision Parts’ warehouse.
Requisition (RN511) contains 2 tables (Heading, Detail), 8 loops, and 43 segments. Sign up free or login to view every table, loop, and element in full, as well as download it in Markdown or console (text) formats.
Sign up free to see the full RN511 reference
See every segment, loop, and element across all 2 tables. Download it as a diagram or Markdown, or use the tedi CLI to access the full X12 reference from your terminal.