Skip to content
X12 EDI

Ford Motor Company X12 862 Shipping Schedule

Plan X12 862 Shipping Schedule for Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS). Connect document identifiers to your business records, test exception handling and track each exchange to completion.

Segments
16
Loops
5
X12 862
Partner references ↗

Implementation guide

Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS): 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.

This document is listed for Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS). Confirm the version, required fields and responses that apply to your account.

Map records and test the business result
Document or decisionRecord and matching IDsWhat to test
Match the business record shipping schedule

schedule reference, item and delivery time bucket

  • Define which combination of schedule reference, item and delivery time bucket identifies one business record, its lines and any later revision.
Update the receiving system Processing the shipping schedule

ID assigned by the receiving system and processing result

  • Distinguish detailed shipping instructions from a longer-range forecast.
  • Apply a revised delivery bucket without retaining superseded demand as extra demand.
Check the processing result Processing status for the shipping schedule

Original document reference and matching response

  • Reconcile the shipping schedule with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

The document reference includes 16 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.

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.

Implementation steps

  1. 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.

  2. 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 Ford Motor Company guide. Preserve the source reference alongside any new destination identifier.

  3. 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.

  4. 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.

Transaction context

Where 862 Shipping Schedule fits on Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS)

Ford Motor Company channels
1 of 1

1 of Ford Motor Company's 1 channel list 862

Trading partners
3

partner references list 862

Channels
12

channel entries list 862

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
Segments with elements marked mandatory in this reference
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
Segment reference — 16 segments 5 loops · X12 862 Shipping Schedule
ISA Interchange Control Header 16 elements

To start and identify an interchange of one 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 8 elements

To indicate the beginning of a shipping schedule.

N1 Loop Repeat: 200
N1 Name 3 elements

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

LIN Loop Repeat: 10,000
LIN Item Identification Detail 4 elements

To specify basic item identification data.

UNT Unit Detail 1 element

To specify item unit data.

REF Reference Numbers 2 elements

To transmit identifying numbers.

PER Administrative Communications Contact 4 elements

To identify a person or office to whom administrative communications should be directed

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 6 elements

To specify the forecasted dates and quantities

JIT Loop Repeat: 24
JIT Just-In-Time Schedule 2 elements

To identify the specific shipping/delivery time in terms of a 24-hour clock and the associated quantity.

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

To specify shipment and/or receipt information

TD1 Carrier Details (Quantity and Weight) 5 elements

To specify the transportation details relative to commodity, weight and quantity.

TD3 Carrier Details (Equipment) 2 elements

To specify transportation details relating to the equipment used by the carrier.

Related references

Other transactions in Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS)

Other EDI documents listed on this channel.

Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS) EDI 862 questions

Common questions about 862 Shipping Schedule on the Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS) channel.

What is X12 862 Shipping Schedule used for?

862 is used when specific shipment timing or quantities are scheduled. It carries information for the shipping schedule. Match it to your business system using schedule reference, item and delivery time bucket.

Is 862 required for Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS)?

862 is listed for Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS). Confirm the required version and direction for your business unit and account with the partner.

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.

How does 862 relate to other EDI messages?

X12 856 Ship Notice Manifest is a related document also listed on Ford Motor Company (Customer Service Division) (North America) (Supplier Direct Ship - SDS). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.

Connect Ford Motor Company 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.