Skip to content
EDI John Deere John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773) 862
X12 EDI

John Deere X12 862 Shipping Schedule

X12 862 (Shipping Schedule) is the EDI transaction exchanged between John Deere (John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
16
Loops
4
X12 862
All partners ↗
Book a demo ← All John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773) transactions

Transaction context

Where 862 Shipping Schedule fits on John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773)

John Deere channels
10 of 10

10 of John Deere's 10 channels carry 862

Trading partners
3

partners across the Stacksync network trade 862

Channels
12

channels network-wide carry 862

Most common alongside 862

On Saicits, 862 runs on 1 channel.

The 862 carries a buyer's firm, near-term shipping requirements: exact quantities, ship or delivery dates, and ship-to locations, down to time-of-day via the JIT segment. It supplements a previously issued 830 planning schedule, superseding the forecast's shipping and delivery detail without replacing the 830 itself. It exists to support just-in-time manufacturing, where releases are issued daily or more often and can be triggered by inventory falling below a restock level. Sent by the buyer, typically a manufacturing plant running just-in-time replenishment, to its supplier; the 830 forecast and 862 releases operate as a pair.

When it fires: Inventory of a component at the buyer's plant drops below its restock threshold, or the plant firms its short-term build plan, and the scheduling system releases an 862 to the supplier.

Common 862 rejection causes
  • Supplier continues building to the earlier 830 forecast after an 862 has superseded its shipping detail, causing over- or under-shipment.
  • Multiple same-day 862 revisions for the same item applied out of sequence, so the supplier ships against a stale release.
  • Wrong ship-to plant or dock identifiers when individual locations issue schedules independently of the consolidated planning schedule.
  • Treating the 862 as authorization to commit labor or materials, which the specification explicitly states it does not provide.

Specification summary

X12 862 Shipping Schedule at the element level

The X12 862 specification defines 22 segments carrying 74 data elements, 50 of which are mandatory.

Segments
22
Data elements
74
Mandatory elements
50
Segments with mandatory elements
Segment Elements Mandatory
BSS 8 7
N1 3 1
LIN 4 2
REF 2 1
PER 4 1
FST 6 4
JIT 2 2
TD3 2 1
CTT 2 1
Key identifiers in 862
  • Transaction Set Purpose Code
  • Reference Number
  • Date
  • Forecast Type Qualifier
  • Forecast Quantity Qualifier
  • Entity Identifier Code
  • Product/Service ID Qualifier
  • Product/Service ID
Full segment guideline — 16 segments 4 loops · X12 862 Shipping Schedule
ISA Interchange Control Header 16 elements

To start and identify an interchange of zero or more functional groups and interchange-related control segments

GS Functional Group Header 8 elements

To indicate the beginning of a functional group and to provide control information

ST Transaction Set Header 2 elements

To indicate the start of a transaction set and to assign a control number

BSS Beginning Segment for Shipping Schedule/Production Sequence 9 elements

To transmit identifying numbers, dates, and other basic data relating to the transaction set

N1 Loop Repeat: 200
N1 Name 4 elements

To identify a party by type of organization, name, and code

N2 Additional Name Information 1 element

To specify additional names or those longer than 35 characters in length

N3 Address Information 2 elements

To specify the location of the named party

N4 Geographic Location 6 elements

To specify the geographic place of the named party

LIN Loop Repeat: 10,000
LIN Item Identification 11 elements

To specify basic item identification data

UIT Unit Detail 1 element

To specify item unit data

PKG Marking, Packaging, Loading 3 elements

To describe marking, packaging, loading, and unloading requirements

REF Reference Identification 2 elements

To specify identifying information

FST Loop Repeat: 100
CTT Transaction Totals 2 elements

To transmit a hash total for a specific element in the transaction set

SE Transaction Set Trailer 2 elements

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

FST Forecast Schedule 8 elements

To specify the forecasted dates and quantities

SHP Loop Repeat: 10
SHP Shipped/Received Information 4 elements

To specify shipment and/or receipt information

Trading partners

9+ trading partners.
And every channel covered.

We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.

Browse the full directory

Trading partners

7+ trading partners.
And every channel covered.

We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.

Browse the full directory

John Deere John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773) EDI 862 FAQ

Common questions about 862 Shipping Schedule on the John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773) channel.

What is X12 862 Shipping Schedule?
X12 862 (Shipping Schedule) is the EDI transaction set used to exchange shipping schedule data. John Deere's John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773) channel requires it from trading partners.
Does John Deere John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773) require 862 for trading partners?
Yes, John Deere (John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773)) supports X12 862 Shipping Schedule. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate John Deere 862 with Stacksync?
Most companies go live with John Deere 862 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which other John Deere channels accept 862?
X12 862 runs on 10 of John Deere's 10 channels. Besides John Deere (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773), it is accepted on John Deere (Thibodaux -T8) (ISA ID: 008473506), John Deere (AG) (ISA ID: 149825353), John Deere (SP) (ISA ID: 557074379SP), John Deere (Engines) (ISA ID: 021688858), John Deere (ISA ID: 249619198), John Deere (Kernersville) (ISA ID: 557074379), John Deere (M3) (ISA ID: 812912349), John Deere (Dubuque and Davenport) (ISA ID: 833123370), John Deere (Reman- SE) (ISA ID: 010678766). Each channel carries its own implementation guideline; Stacksync validates outbound documents against the correct guideline automatically.

Ready to automate your John Deere EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.

Book a John Deere EDI demo Tour the platform on your own