X12 transaction code
EDI 862 Shipping Schedule (X12 862)
EDI 862 is the X12 Shipping Schedule transaction set, used when specific shipment timing or quantities are scheduled. The buyer, typically a manufacturing plant running just-in-time replenishment, sends the 862 to its supplier. The 830 forecast and 862 releases operate as a pair.
- Standard
- X12
- Code
- 862
- Partner references
- 3
At a glance
EDI 862 at a glance
What the 862 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 862 Shipping Schedule |
|---|---|
| Business record | Shipping schedule |
| Who sends it to whom | The buyer, typically a manufacturing plant running just-in-time replenishment, sends the 862 to its supplier. The 830 forecast and 862 releases operate as a pair. |
| When it is sent | 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. |
| Match on | Schedule reference, item and delivery time bucket |
| Partner references | 3 trading partners in this directory |
| Related documents | X12 830 Planning Schedule with Release Capability, X12 856 Ship Notice/Manifest |
Key segments in an EDI 862
The business segments that appear in at least half of the 12 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.
| Segment | Name | Purpose | Partner references |
|---|---|---|---|
| BSS | Beginning Segment for Shipping Schedule | To indicate the beginning of a shipping schedule. | 12 of 12 |
| N1 | Name | To identify a party by type of organization, name and code. | 12 of 12 |
| LIN | Item Identification Detail | To specify basic item identification data. | 12 of 12 |
| REF | Reference Numbers | To transmit identifying numbers. | 12 of 12 |
| CTT | Transaction Totals | To transmit a hash total for a specific element in the transaction set. | 12 of 12 |
| FST | Forecast Schedule | To specify the forecasted dates and quantities. | 12 of 12 |
| SHP | Shipped/Received Information | To specify shipment and/or receipt information. | 12 of 12 |
| N2 | Additional Name Information | To specify additional names or those longer than 35 characters in length. | 11 of 12 |
| N3 | Address Information | To specify the location of the named party. | 11 of 12 |
| N4 | Geographic Location | To specify the geographic place of the named party. | 11 of 12 |
Stacksync connects EDI documents such as the X12 862 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.
Implementation guide
X12 862 mapping and validation
X12 862 Shipping Schedule is used when specific shipment timing or quantities are scheduled. Preserve schedule reference, item and delivery time bucket so the shipping schedule in your business system stays connected to the original document.
Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | shipping schedule schedule reference, item and delivery time bucket |
|
| Update the receiving system | Processing the shipping schedule ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the shipping schedule Original document reference and matching response |
|
How the related documents differ
Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.
- X12 830 Planning Schedule with Release Capability
demand and release schedule: forecast or release planning is updated.
- X12 856 Ship Notice/Manifest
shipment notice (ASN): an order ships, before the goods arrive.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when specific shipment timing or quantities are scheduled. Name the operational owner of the shipping schedule and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map schedule reference, item and delivery time bucket. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
-
Test failures before launch
Run the failure cases in the mapping table against realistic shipping schedule data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
-
Track every document to completion
Record transport delivery and document validation separately from successful shipping schedule processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 862 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic shipping schedule data.
- Each submitted document can be traced through delivery, validation and processing in the receiving system.
- Your team knows how to investigate and recover a rejected or timed-out shipping schedule without processing it twice.
Document structure
X12 862 Shipping Schedule at the element level
The X12 862 reference contains 22 segment entries and 74 data elements; 50 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 22
- Data elements
- 74
- Mandatory elements
- 50
| 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 |
- Transaction Set Purpose Code
- Reference Number
- Date
- Forecast Type Qualifier
- Forecast Quantity Qualifier
- Entity Identifier Code
- Product/Service ID Qualifier
- Product/Service ID
Find your trading partner for X12 862
3 partners, 12 channels. Choose a channel to inspect its listed document reference and implementation context.
- Ford Motor Company
- John Deere 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 (via Saicits) (1B - Worldwide Logistics) (ISA ID: 156471773)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)
- John Deere Mexico
Catalog breakdown
Where X12 862 Shipping Schedule appears in this catalog
The largest groups of classified 862 catalog entries are in agriculture, manufacturing & industrial and automotive.
By industry
- agriculture 10 channels
- manufacturing & industrial 1 channel
- automotive 1 channel
By network
- Saicits 1 channel
FAQ
EDI 862 questions
What is an EDI 862?
EDI 862 is the X12 Shipping Schedule transaction set. Trading partners use it when specific shipment timing or quantities are scheduled. It carries the data for the shipping schedule, and your system matches it on schedule reference, item and delivery time bucket.
Who sends an EDI 862 and who receives it?
The buyer, typically a manufacturing plant running just-in-time replenishment, sends the 862 to its supplier. The 830 forecast and 862 releases operate as a pair. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 862 sent?
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. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 862?
Across 12 partner document references listed here, the business segments that appear most often include BSS (Beginning Segment for Shipping Schedule), N1 (Name), LIN (Item Identification Detail), REF (Reference Numbers), CTT (Transaction Totals), FST (Forecast Schedule). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 862 and EDI 830?
The 862 carries the shipping schedule and is used when specific shipment timing or quantities are scheduled. The 830 carries the demand and release schedule and is used when forecast or release planning is updated.
What should I map for X12 862?
Start with schedule reference, item and delivery time bucket and the target shipping schedule. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.
How should I test 862 error handling?
Distinguish detailed shipping instructions from a longer-range forecast. Apply a revised delivery bucket without retaining superseded demand as extra demand. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 862?
The directory on this page links 3 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
Connect EDI to your business systems
See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.
