Search EDIBlogs

11 results for “850

Transaction850 — Purchase OrderThe X12 850 is the electronic purchase order a buyer sends to a supplier to request goods or services, replacing paper or PDF POs with a structured, machine-readable document.ArticleX12 850 Purchase Order: Complete EDI GuideA complete, segment-by-segment walkthrough of the X12 850 Purchase Order — what it is, how it's structured, how to map it, and how to troubleshoot the errors that show up most often in production.Transaction855 — Purchase Order AcknowledgmentThe X12 855 is the supplier's formal response to an 850 Purchase Order, confirming, changing, backordering, or rejecting each line item.TransactionORDERS — Purchase Order MessageUN/EDIFACT ORDERS is the international equivalent of the X12 850 — a structured purchase order used widely across Europe and global trade lanes.ArticleEDIFACT ORDERS: A Complete Guide to the International Purchase Order MessageHow UN/EDIFACT ORDERS compares to the X12 850, its segment structure, and what to watch for when trading with European and global manufacturing partners.ArticleEDI Mapping Explained: From ERP Fields to X12 and EDIFACT SegmentsA practical guide to how EDI mapping actually works — the concepts, common source formats, and a worked example translating SAP IDoc fields into an X12 850.GlossaryGS (Functional Group Header)Marks the start of a functional group — a batch of one or more transaction sets of the same type (e.g., all 850s) — within an X12 interchange.GlossaryPO1 (Baseline Item Data)The X12 850 segment representing a single line item on a purchase order, including quantity, unit price, and product identifiers.GlossaryBEG (Beginning Segment for Purchase Order)The X12 850 segment that carries the purchase order number, type, and date, marking the start of the transaction's business content.GlossaryTranslationThe runtime process of converting data from one format to another according to a mapping specification — for example, converting an internal order record into an X12 850 file.GlossaryLoopA repeating group of segments in an EDI transaction, such as the PO1 loop in an 850 (one per line item) or the HL loop in an 856 (one per hierarchical level).