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

X12 transaction guide · Planning

EDI 862 Shipping Schedule

The X12 document a manufacturer sends to give suppliers firm, near-term shipping requirements, usually daily.

Sent by
Manufacturer or buyer
Received by
Supplier
Standard
ANSI ASC X12
EDIFACT equivalent
DELJIT

What is an EDI 862?

The EDI 862 Shipping Schedule is the ANSI X12 transaction set manufacturers use to give suppliers precise, near-term shipping requirements. Where the 830 provides a longer forecast, the 862 specifies exact quantities and ship or delivery dates, often by day, for the coming days or weeks.

The 862 supplements the 830 rather than replacing it. It supersedes the shipping detail of the planning schedule for the period it covers, while the 830 continues to guide longer-term planning. Suppliers ship against the 862 and confirm each shipment with an 856 advance ship notice.

How the EDI 862 worksDiagram of the EDI 862 Shipping Schedule. Manufacturer or buyer sends it to supplier. It usually follows 830. It is usually followed by 856. Inside the ISA, GS and ST envelopes, X12 release 004010 requires, in the heading: BSS (Beginning Segment for Shipping Schedule/Production Sequence) and detail: the required LIN loop with LIN (Item Identification) and UIT (Unit Detail). 3 optional loops are listed by their first segment.How the EDI 862 worksShipping Schedule: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS830Planning Schedule withRelease CapabilityEDI 862SENDERManufacturer or buyerRECEIVERSupplier997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY856Advance Ship Notice2 WHAT X12 RELEASE 004010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code SSGS … GETransaction set 862ST … SEHEADINGBSSBeginning Segment for ShippingSchedule/Production Sequence+ 1 optional loop, starting with:N1DETAILRequired loop LIN · repeats up to 10,000LINItem IdentificationUITUnit Detail+ 2 optional loops, starting with:FSTSHPBlue 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 004010 listing for the 862. Your trading partner's implementation guide adds its own requirements.
How the EDI 862 worksDiagram of the EDI 862 Shipping Schedule. Manufacturer or buyer sends it to supplier. It usually follows 830. It is usually followed by 856. Inside the ISA, GS and ST envelopes, X12 release 004010 requires, in the heading: BSS (Beginning Segment for Shipping Schedule/Production Sequence) and detail: the required LIN loop with LIN (Item Identification) and UIT (Unit Detail). 3 optional loops are listed by their first segment.How the EDI 862 worksShipping Schedule: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS830Planning Schedule with ReleaseCapabilityEDI 862SENDERManufacturer orbuyerRECEIVERSupplier997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY856Advance Ship Notice2 WHAT X12 RELEASE 004010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code SS (GS … GE)Transaction set 862 (ST … SE)HEADINGBSSBeginning Segment forShipping Schedule/ProductionSequence+ 1 optional loop, starting with:N1DETAILRequired loop LIN · repeats up to10,000LINItem IdentificationUITUnit Detail+ 2 optional loops, starting with:FSTSHPBlue 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 X12004010 listing for the 862. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 862, to whom, and which documents usually come before and after it. The lower part shows what X12 release 004010 itself requires: the envelopes around the 862 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

  • Just-in-time and just-in-sequence automotive supply
  • Daily delivery requirements for production plants
  • Short-term adjustments to the planning schedule

Where it fits in the document flow

Usually follows 830 Planning Schedule with Release Capability
This document 862 Shipping Schedule
Usually followed by 856 Advance Ship Notice

Structure

Key segments in the 862

The segments most implementations use, described in plain language. The last column shows what X12 release 004010 itself requires: "Required" marks a segment the standard requires in every 862; "Optional, common" marks a segment the standard leaves optional, or that sits in an optional loop, but that implementations often use. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, makes some optional segments mandatory and restricts the values, and requirements can differ between releases. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

SegmentNameWhat it carriesIn X12 004010
BSSBeginning Segment for Shipping SchedulePurpose code, schedule reference number, date, schedule type and the horizon start and end dates.Required
N1 loopParty IdentificationShip-to plant and supplier.Optional, common
LINItem IdentificationBuyer part number and other identifiers.Required
UITUnit DetailUnit of measure.Required
SHPShipped/Received InformationLast shipment quantity and date, used to reconcile requirements.Optional, common
FSTForecast ScheduleFirm quantities with daily or other time buckets and dates.Optional, common

Example

Sample EDI 862

A shipping schedule for part 12345-AB requiring 240 firm units (C) on each of two days (D). SHP reports the last shipment of 480 units for reconciliation.

Illustrative data only, not tied to one X12 release or trading partner. The interchange (ISA/IEA) and functional group (GS/GE) envelopes are omitted for readability.

ST*862*0001~
BSS*05*SS001*20261020*DL*20261103*20261109~
N1*ST*Example Plant*92*P01~
LIN**BP*12345-AB~
UIT*EA~
SHP*01*480*011*20261020~
FST*240*C*D*20261103~
FST*240*C*D*20261105~
SE*9*0001~
Reading a sample EDI 862, line by lineAnnotated sample EDI 862 with 9 lines. Notes explain the ST, BSS, N1, LIN, UIT, SHP, FST and SE segments.Reading a sample EDI 862, line by lineEach numbered note explains the segment on that line. The data is illustrative.ST*862*0001~11Transaction Set Header. Opens the 862 and gives it a controlnumber, which SE repeats.BSS*05*SS001*20261020*DL*20261103*20261109~22Beginning Segment for Shipping Schedule. Purpose code,schedule reference number, date, schedule type and the horizonstart and end dates.N1*ST*Example Plant*92*P01~33Party Identification. Ship-to plant and supplier.LIN**BP*12345-AB~44Item Identification. Buyer part number and other identifiers.UIT*EA~55Unit Detail. Unit of measure.SHP*01*480*011*20261020~66Shipped/Received Information. Last shipment quantity and date,used to reconcile requirements.FST*240*C*D*20261103~77Forecast Schedule. Firm quantities with daily or other timebuckets and dates.FST*240*C*D*20261105~SE*9*0001~88Transaction Set Trailer. Closes the set with the number ofsegments, including ST and SE, and the same control number.Illustrative data only, not tied to one trading partner. Envelopes (ISA/GS) are omitted for readability.
Reading a sample EDI 862, line by lineAnnotated sample EDI 862 with 9 lines. Notes explain the ST, BSS, N1, LIN, UIT, SHP, FST and SE segments.Reading a sample EDI 862, lineby lineEach numbered note explains the segment onthat line. The data is illustrative.ST*862*0001~Transaction Set Header. Opens the 862 andgives it a control number, which SE repeats.BSS*05*SS001*20261020*DL*20261103*20261109~Beginning Segment for Shipping Schedule.Purpose code, schedule reference number,date, schedule type and the horizon start andend dates.N1*ST*Example Plant*92*P01~Party Identification. Ship-to plant andsupplier.LIN**BP*12345-AB~Item Identification. Buyer part number andother identifiers.UIT*EA~Unit Detail. Unit of measure.SHP*01*480*011*20261020~Shipped/Received Information. Last shipmentquantity and date, used to reconcilerequirements.FST*240*C*D*20261103~Forecast Schedule. Firm quantities with dailyor other time buckets and dates.FST*240*C*D*20261105~SE*9*0001~Transaction Set Trailer. Closes the set withthe number of segments, including ST and SE,and the same control number.Illustrative data only, not tied to one trading partner.Envelopes (ISA/GS) are omitted for readability.

The sample is the same one shown above, with a note beside each segment the first time it appears. Segment IDs are highlighted at the start of each line; the fields after them are separated by asterisks, and each segment ends with a tilde.

Expand diagram Download SVG

Avoid problems

Common 862 errors and how to prevent them

Duplicating 830 demand

The 862 supersedes the 830's shipping detail for its horizon. Adding both double counts demand.

Ignoring the last-shipment reference

Requirements assume the customer received the last shipment listed. Reconcile against SHP before planning.

Late ship notices

Each shipment against an 862 needs an accurate and timely 856.

Trading partners

Integration guides that include the 862

  • Ford EDI integration
  • General Motors EDI integration
  • Honda EDI integration
  • John Deere EDI integration
  • Toyota EDI integration

How ECOM helps

Automate the 862 with ECOM

Industry

Automotive

Schedules, ship notices, labels, self-billing and multi-plant routing for automotive suppliers.

Solution

ERP Integration

Connect your ERP to trading partners through EDI, APIs, IDocs, files and connectors.

Product

PRISM-SCV

Order lifecycle visibility, response monitoring, routed alerts and business-identifier search across your B2B transactions.

EDI 862 FAQs

Does the 862 replace the 830?

No. It supersedes the 830's shipping detail for the short-term horizon while the 830 continues to guide longer-term planning.

Which industries use the 862?

Primarily automotive and other manufacturing supply chains with frequent, scheduled deliveries.

What is the EDIFACT equivalent of the 862?

The UN/EDIFACT equivalent is the DELJIT delivery just-in-time message.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related planning documents

All 7 planning documents

Need help with the EDI 862?

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

Request a Demo Contact us