SDS _Supplier Direct Ship_ EDI Manua SDS12 Supplierdirectshipedimanual
User Manual: SDS12
Open the PDF directly: View PDF 
.
Page Count: 52
North American Supply Chain Management Page 1 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
This manual is available at https://web.pslsupp.ford.com/
Ford Customer Service Division
SDS (Supplier Direct Ship) EDI Manual
North American Supply Chain Management Page 2 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
Table of Contents
FCSD SDS Purchase Order Schedule and Mailbox Availability .......................................................................... 3
Valid SCAC Codes for Track & Trace ..................................................................................................................... 3
Ford Single Point of Contact (SPOC) Support Services....................................................................................... 4
EDI Coordinators ...................................................................................................................................................... 4
Connectivity Methods .............................................................................................................................................. 5
SDS ANSI X12 Required EDI Transactions ............................................................................................................ 6
SDS EDI Testing Process ........................................................................................................................................ 7
Interchange Control Structure including Explanation and Attributes ................................................................ 8
850 Purchase Order Transaction Set Layout......................................................................................................... 9
850 Purchase Order Explanation and Attributes................................................................................................. 10
824 Purchase Order Cancellation Transaction Set Layout ................................................................................ 15
824 Purchase Order Cancellation Explanation and Attributes .......................................................................... 16
865 Purchase Order Change Transaction Set Layout ........................................................................................ 18
865 Purchase Order Change Explanation and Attributes .................................................................................. 19
865 Important Points .............................................................................................................................................. 21
860 PO Change Acknowledgement Transaction Set Layout ............................................................................. 22
860 PO Change Acknowledgement Explanation and Attributes ....................................................................... 23
870 Order Status (Promise Date) Transaction Set Layout ................................................................................. 25
870 Order Status (Promise Date) Explanation and Attributes ........................................................................... 26
856 Advance Ship Notice (ASN) Transaction Set Layout................................................................................... 28
856 Advance Ship Notice (ASN) Explanation and Attributes............................................................................. 29
824 Application Advice Transaction Set Layout ................................................................................................. 33
824 Application Advice Explanation and Attributes ........................................................................................... 34
TED Segment Error Messages Explanation......................................................................................................... 37
861 Receipt Advise Transaction Set Layout........................................................................................................ 38
861 Receipt Advise Explanation and Attributes.................................................................................................. 39
997 Functional Acknowledgement Transaction Set Layout- ACCEPTED ........................................................ 41
997 Functional Acknowledgement Explanation & Attributes- ACCEPTED ...................................................... 42
997 Functional Acknowledgement Transaction Set Layout- REJECTED......................................................... 43
997 Functional Acknowledgement Explanation & Attributes- REJECTED....................................................... 44
997 Functional Acknowledgement Error Definitions .......................................................................................... 46
TA1 Errors ............................................................................................................................................................... 47
TA1 Error Note Code Definitions .......................................................................................................................... 48
Mode of Transportation (MOT), Packaging Codes, & REF Qualifiers ............................................................... 49
Glossary of Acronyms ........................................................................................................................................... 50
Glossary of Attributes ............................................................................................................................................ 51
EDI Manual Revisions ............................................................................................................................................ 52
......................................................................................................................................................................................
If a Segment and/or Element is listed in this manual, it is a required field for FCSD SDS EDI even if it has an
Optional or Conditional Attribute according to ANSI X12, unless otherwise noted.
North American Supply Chain Management Page 3 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
FCSD SDS Purchase Order Schedule and Mailbox Availability
FCSD will place customer Purchase Orders in the Suppliers GEC Hub Mailbox 15 times daily Monday through
Friday.
Load Times are as follows:
6:20 AM
8:20 AM
9:20 AM
10:20 AM
11:20 AM
12:20 PM
1:20 PM
2:20 PM
3:20 PM
4:20 PM
5:20 PM
6:20 PM
7:20 PM
8:20 PM
9:20 PM
All Emergency Orders with an activity code of (xx1 or xx2) received on or before 4:00PM EST must be
shipped same day.
Suppliers are required to check their GEC Hub mailbox after each order load time to assure ample
time to meet the FCSD Ship Standards.
Valid SCAC Codes for Track & Trace
SMALL PACK:
FDEG - FedEx Ground
FDE1 - FedEx Express (Air) Emergency
FDE2 - FedEx Express 2
nd
Day (Economy Service) Emergency Shipments to Alaska and Hawaii
LTL:
CTII - Central
PJXI - PJAX
YFSY - Yellow
AACT - AAA Cooper
VGDG - Vanguard
North American Supply Chain Management Page 4 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
Ford Single Point of Contact (SPOC) Support Services
The Ford Single Point Of Contact (SPOC) Help Desk, is staffed 24/7. SPOC will create and route tickets to
the various EDI support teams within the Global Electronic Communications (GEC) Hub Service organization for
EDI issues. SPOC is prepared to answer questions about systems and network availability after hours, holidays,
and on weekends. Questions regarding specific EDI transactions and their content should be handled during
working hours Monday - Friday 7:00 am to 4:30 pm EST when GEC Hub Services is available.
The GEC Hub services team will be able to assist you in the following areas:
1. The availability of the GEC Hub mailbox system.
2. End-to-End communication line and connectivity problems between the supplier and the
GEC Hub mailbox system.
3. Provide a reference point between suppliers and Ford Plants.
4. Provide interpretation of the Ford EDI guidelines.
5. Provide a copy of the Ford Corporate EDI guidelines through their website, https://web.gsec.ford.com/
(Click "Specs" tab. This document is a sub-set with specific FCSD SDS requirements, which may
differ from the Ford Corporate guidelines).
6. Provide Transaction Log tool through website (above) to help track data transmissions.
7. Assist new suppliers in the initial phases of sending and receiving data from Ford. (Connectivity and
Syntax testing).
This document is a sub-set with specific FCSD requirements, which may differ from the Ford Corporate Guidelines.
The SPOC Help Desk phone number is: (888) 317- 4957 or (313) 317-4957.
Establishing an EDI Connection to the GEC Hub
1. Go to the GSEC Website located @ https://web.gsec.ford.com
2. Click on "Connection Requests"
3. Click on the "EDI Connection Request Form" link
4. Enter Supplier GSDB; Click 'Submit'
5. Check the supplier code listed under "New GSDB Connection Request"; Click 'Submit'
6. Complete Form; click 'Submit'
Please allow 1-8 business days to be contacted by a member of the Migration Team. This can vary depending on the
number of requests in their queue. You will be contacted via phone or email. At that time, you will be assigned to one of
our EDI Analysts, who will provide you with testing procedures.
EDI Coordinators:
FCSD-NA: FCSDEDI@Ford.com
FOC (Ford Of Canada): FOCEDI@Butcherent.com
North American Supply Chain Management Page 5 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
Connectivity Methods
VAN (Value Added Network) Connectivity Method
The method of connecting to the Ford GEC Hub requires the use of a VAN connection for EDI data transfers.
The VAN provides services that are similar to that of an ANX Service Provider and MUST BE APPROVED by
Ford Motor Company. The list of approved VAN's are as follows:
VAN Provider Website
Covisint www.covisint.com
EDS*Elit www.business-
exchange.canada.eds.com/EDS_ELIT
GXS (GEIS) www.gxs.com
IBM www.gxs.com
iConnect www.iconnect-corp.com
Inovis www.inovis.com
Kleinschmidt www.kleinschmidt.com
Sterling Commerce www.sterlingcommerce.com
ANX (Advanced Network Exchange) Connectivity Method
The services are as follows:
1. ANX Service Provider (required)
2. IPSEC Security Service Provider (optional)
3. ANX Overseer Group (required)
The ANX Service Provider is responsible for providing the ANX circuit and router. Estimate approximately 60
days to get an ANX circuit installed once the circuit is ordered. Add an additional week for some of the post circuit
installation implementation steps. This will include filling out and returning to Ford representatives some required
documents for establishing a secure tunnel. There are several ANX Certified Service Providers (CSP). These
providers typically charge a one-time installation service fee and a monthly ANX service fee w/access. Fees vary
by provider. Please check with the CSP for pricing information.
The IPSEC Security Service Provider is responsible for providing additional hardware (if required), software and
services for firewall and IPSEC security management. This service is only required if you chose to out-source this
operation. The service provider typically charges a one-time IPSEC product installation fee and a monthly IPSEC
service fee. Please check with your ANX Service Provider for details.
The ANX Overseer Group is responsible for enforcing the Service Level Agreement (SLA) and uptime
requirements (99.965% network availability) of the ANX network. As a result, trading partners must pay a onetime
fee along with an annual fee. Please reference the http://www.anx.com/ website for pricing details.
WAM (Web Access Module) Connectivity Method
Is the use of a public Internet connection for EDI data exchange. The WAM user utilizes a local ISP (Internet
Service Provider) to access the GEC Hub through the Trading Partners.
The Trading Partner must select an Internet Service Provider. It does not matter what ISP is selected as Ford
Motor Company has no guidelines or requirements for Internet Service Providers. Suppliers that are setup for the
WAM access it via the Ford Supplier Network portal using a standard web browser (Internet Explorer 5.5 or
Netscape 4.7). The WAM allows a user to download their data one transaction at a time and upload their data
one file at a time. The GEC Hub business team recommends the WAM be used for suppliers that send no more
than 10 ASN's or documents daily and supply less than 20 parts. For those sending documents other than ASN's,
document size should be limited to that WAM is NOT considered a fully integrated EDI solution for those suppliers
that need to meet their Q1 ratings.
For more information on connectivity, reference the GSEC website https://web.gsec.ford.com/ or for connectivity
questions, please email econnect@ford.com.
North American Supply Chain Management Page 6 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
SDS ANSI X12 Required EDI Transactions
Direct Ship Suppliers communicating via EDI with FCSD North American Supply Chain are Required to
adhere to the following ANSI X12/Ford EDI requirements.
FCSD Supplier Direct Ship Ford/ANSI X12 Transaction Sets
850
(FCSD to Supplier)
Purchase Order (ver 002001) – Informs the supplier of new orders to be
Direct Shipped to FCSD customers.
824
(Supplier to FCSD)
FCSD Order Cancellation (ver 003010) - Advises FCSD of order
rejects that do not fit into the 865 transaction set. e.g.: Customers' not
participating in a particular marketing program, customer order does not
meet supplier minimum ship quantities, or a customer requested
cancellation. Transmitting an 824 cancels the entire order.
865
(Supplier to FCSD)
Purchase Order Amendment (ver 002001) - Notifies FCSD of line item
cancellations, shipment of replacing parts, or quantity changes.
860
(FCSD to Supplier)
Purchase Order Amendment Acknowledgement (ver 002001) -
Acknowledges changes submitted from the supplier on an 865, PO
Change Acknowledgement. A "06" code sent back on the 860 indicates
the 865 was accepted; a "10" code indicates the 865 was rejected and
requires immediate corrective action by the supplier.
870
(Supplier to FCSD)
Order status (Promise Date) (ver 003010) - Provides FCSD's
customers with accurate ship date information for each part not
shipped on time.
856
(Supplier to FCSD)
Advance Shipping Notice (ver 002002FORD) - Provides FCSD with
Shipment Confirmation of 850 Purchase Orders. (ASN's should be sent
within 15 minutes of the shipment leaving the dock.)
824
(FCSD to Supplier)
Application Advice (ver 003010) - Advises supplier of rejects for
previously submitted (856) ASN's. 824 error messages are triggered
when the 856 data content does not match up to a specific 850 order.
Error types are: Mismatch, Overship, Duplicate, Rejected Shipment
(ASN with 01 purpose code), Part Source Error.
997
(FCSD to Supplier &
Functional Acknowledgement (ver 002002) – When supplier sends
Supplier to FCSD)
a message to Ford, a syntax check is performed. A Functional
Acknowledgement (997) will be sent immediately advising if the message
was "accepted" or "rejected". Each 997 must be reconciled against each
data message. If the 997 indicates that a message was "rejected", the
supplier must investigate, and take corrective action. 997's do NOT
check for correct data content against a specific order!
861
(FCSD to Supplier)
Receipt Advise (ver 002001) – An acknowledgement of receipt and
payment to the supplier for TDS or Association shipments for Direct
Ship. (L9V0C, R3MSA, H0TDC) FCSD expects suppliers to reconcile
each 861 received against every Advance Ship Notice in a timely basis.
The 861 Transaction is NOT required at this time, but may be implemented in the future.
North American Supply Chain Management Page 7 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
SDS EDI Testing Process
Start-Up (For New Launch Suppliers or Suppliers that have changed their Connection/VAN)
1) Supplier must complete and EDI "Connection Request" form on the Global Electronic Supplier
Communication (GSEC) Website to have a supplier mailbox established.
If supplier already has an established mailbox, EDI Coordinator will complete "Mailbox Profile Change Request" to include
the EDI transactions, versions, AND verify mailbox profile established for both Production and Education (Test
Environment).
2) Supplier must complete EDI connectivity testing with Ford ANX Migration Team of the GEC Hub. The
migration team will send test instructions for connectivity once your on-line request form is processed.
3) Once connectivity testing is complete, supplier to notify EDI Coordinator of readiness to start data content
testing.
4) Supplier to email EDI Coordinator 2 FCSD part numbers to use during data content tests. If supplier is
shipping Motorcraft parts, also submit 1 Motorcraft part number.
Test Order Process (New Launch, Connection/VAN changes, Software/Hardware Upgrades)
A. EDI Coordinator will load a total of 10 test purchase orders (850's) into the Education Mailbox
(F159E) of the Supply On-line Information System – SOLMIS and push to supplier GEC Hub Mailbox.
B. The 6 test purchase orders, comprised of 3 single line orders and 3 multiple line orders, will be pulled
by supplier from GEC Hub mailbox and processed.
C. Supplier must send back 6 (3 single line/3 multi line) successful test ASN's (856) utilizing the 850's.
856's must comply with the 5 match point criteria as established in the EDI Guidelines.
D. Supplier must send back 3 (824's). Each one should indicate a different reason code (Min order
QTY, Part Sourced in Error, Entire Order Cancellation) using the 850's.
E. Supplier must send 3 (865's). Each should indicate a different reason code (QTY Change, Part
Number Change, Line Item Cancellation) using the 850's.
F. Supplier must send back 1 (870) to update a Promise Date.
G. EDI Coordinator will load 1 (860) to indicate the Change issued in the 865 was Accepted or Rejected.
Supplier to pull into system and email Coordinator a Screenshot that the system has been able to
process the notice.
H.
EDI Coordinator will load 1 (824) Reject. Supplier to pull into system and email Coordinator
Screenshot that the system has been able to process the notice.
For each transaction transmitted, a copy of the RAW X12 Data, including the Envelope Structure (ISA/IEA), must be e-
mailed to the EDI Coordinator to review.
Hints for troubleshooting:
If the ISA15 is anything other than 'P', Ford will reject it. Only the ISA receiver ID
(ISA08)
changes to
F159E when the supplier is sending in documents to our test server at IP address
ftpqa.gechub.ford.com.
Check transaction version if data sent back from supplier does not reach mailbox.
Check Functional Acknowledgement (997) for rejected segment(s).
Check with your VAN to see if they have a transmission log file sent from VAN provider to Ford. If VAN
shows data transmitted successfully – Contact Ford EDI helpdesk @ (888) 317-4957 for assistance.
North American Supply Chain Management Page 8 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
Interchange Control Structure including Explanation and Attributes
Sample Interchange Control Structure with explanation – HEADER/TRAILER INFORMATION
ISA*00* *00* *ZZ*SCODE *ZZ*F159B *060531*1241*U*00200*000016285*0*P*<
Attributes
ISA INTERCHANGE CONTROL HEADER
(Start)
ISA01 00 Use "00"
(zeroes)
M ID 02/02
ISA02 SPACES Use 10
(ten)
spaces M AN 10/10
ISA03 00 Use "00"
(zeroes)
M ID 02/02
ISA04 SPACES Use 10
(ten)
spaces M AN 10/10
ISA05 ZZ Use "ZZ" M ID 02/02
ISA06 SCODE Sender ID (
Left Justified and filled with blanks)
M ID 15/15
ISA07 ZZ Use "ZZ" M ID 01/02
ISA08 F159B Receiver ID
(Left Justified and filled with blanks)
M ID 15/15
ISA09 060531 Date of Transmission
(YYMMDD)
M DT 06/06
ISA10 1241 Time of Transmission
(HHMM, 24 Hour Clock)
M TM 04/04
ISA11 U Use "U" for USA M ID 01/01
ISA12 00200 Version ID Use "00200" M ID 05/05
ISA13 000016285 Control Number
(Must Match IEA02)
M N0 09/09
ISA14 0 Use "0"
(zero)
M ID 01/01
ISA15 P Test Indicator
(Always use "P")
M ID 01/01
ISA16 < Sub Element Separator
(Use '<' ASCII Hex Value)
M AN 01/01
Ford does not utilize the 'T' for testing in the ISA15, MUST always be 'P'.
ISA08 will point to F159E (for the Education System) when testing SDS transactions only, for Production it will be F159B.
IEA*1*000016285
IEA INTERCHANGE CONTROL TRAILER
(End)
IEA01 1 Number of GS/GE Pairs
(Between ISA & IEA)
M N0 01/15
IEA02 000016285 Control Number
(Must Match ISA13)
M N0 09/09
North American Supply Chain Management Page 9 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
850 Purchase Order Transaction Set Layout
ISA………HEADER INFORMATION
GS*PO*AF1CC*SCODE*060531*0613*000185878*X*002001\
Receiving Code, Sender Code, Version
ST*850*0001\
Transaction Set Header
BEG*00*"SA" or "DS"*YA1234***060531\
Beginning Segment, SA–Stand Alone, DS-Drop Ship, Y-Release #
NTE*INV*NONE\
Note, Special Instructions
NTE*PMT*NONE\
Note, Special Instructions
REF*IT*08709*FCSD INTERNAL CUSTOMER NUMBER\
Dealer P&A Code
REF*CR*19278*CUSTOMER ORDER NUMBER\
Customer/Dealer Order Reference (COR/DOR) Number
REF*PO*SC07678*PURCHASE ORDER NUMBER\
FCSD Purchase Order Number
REF*DC*0219278*DEALER PURCHASE ORDER NUMBER\
Dealer Purchase Order Number
REF*ZZ*OT/725*ACTIVITY CODE\
FCSD Order Type
PER*IC*JOE WELTY FORD INC*TE*PHONE\
Requester (Dealer) Name, Phone
PER*IC*FCSD CONTACT NAME*TE*PHONE\
FCSD Contact Name, Phone
PER*EX*FCSD CONTACT NAME*TE*PHONE\
FCSD Expeditor Contact Name, Phone
N1*BY*FORD CUSTOMER SERVICE DIVISION*92*AF1CC\
Buying Party
N3*P.O. BOX 3333\
Buying Party Street Address
N4*LIVONIA*MI*92\
Buying Party City, State
N1*SU*SUPPLIER NAME*92*SCODE\
Supplier Name, Supplier GSDB Code
N3*NE 58
TH
AVE*P.O. BOX\
Supplier Street Address
N4*CARROLLTON*TX*75006*US\
Supplier City, State, Zip
N1*ST*JOE WELTY FORD INC*92*AF1CC\
Ship To Customer Name
(Different from Requestor if Drop Ship)
N3*SURVEYOR BLVD\
Ship To Customer Street Address
N4*CUSTOMER CITY*ST*ZIP CODE*92\
Ship To Customer City, State, Zip
PER*IC*JOE WELTY FORD INC*TE*PHONE NUMBER\
Customer Contact Name, Phone
DTM*007*060531\
Effective Date
DTM*036*061009\
Expiration Date
SHH*DD*069*060531\
Deliver On Date
(Requested Ship Date)
PO1*00001*4*EA*40.1800**BP*F81Z 16A550 JA\
Quantity, Unit of Measure, Price, Part Number
CUR*BY*USD\
Currency
PID*F****NONE\
Product/Item Description
(Freeform)
CTT*1*4\
Total Number of PO1 segments, Total Quantity in PO102's
SE*30*0001\
Total segment Count
(Including ST/SE)
GE*1*000185878\
Total Number of ST/SE pairs between GS & GE, Control Number
(Must match GS06)
IEA………TRAILER INFORMATION
North American Supply Chain Management Page 10 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
850 Purchase Order Explanation and Attributes
ISA………HEADER INFORMATION
GS*PO*AF1CC*SCODE*060531*0613*000185878*X*002001 Attributes
GS FUNCTIONAL GROUP HEADER
(Start)
GS01 PO Purchase Order M ID 02/02
GS02 AF1CC Direct Ship Sender Code M ID 02/12
GS03 SCODE Receiver Code
(Supplier GSDB Code)
M ID 02/12
GS04 060531 Transmission Date
(YYMMDD)
M DT 06/06
GS05 0613 Time
(HHMM, 24 Hour Clock)
M TM 04/04
GS06 000185878 Control Number
(Must Match GE02)
M N0 01/09
GS07 X Responsible Agency Code
(Use "X")
M AN 01/02
GS08 002001 ANSI X12 Version M ID 01/12
ST*850*0001
ST TRANSACTION SET HEADER
ST01 850 Transaction Set ID (Purchase Order) M ID 03/03
ST02 0001 Control Number (Must Match SE02) M AN 04/09
BEG*00*SA*YA1234 ***060531
BEG BEGINNING SEGMENT (Purchase Order)
BEG01 00 Original M ID 02/02
BEG02 SA PO Type M ID 02/02
SA - Stand Alone DS - Drop Ship
BEG03 YA1234 Y-Release Number
(Release number for a SDS 850 PO)
M AN 01/18
BEG06 060531 Purchase Order Date/Requested Ship Date
(YYMMDD)
M DT 06/06
Cut-Off is 2:00 PM EST for Stock & 4:00 PM EST for Emergency. After Cut-Off this field will have the next business date
as the Requested Ship Date.
NTE*INV*NONE
NTE NOTE/SPECIAL INSTRUCTION
NTE01 INV Invoice Instructions for entire transaction set follows O ID 03/03
GEN - Entire Transaction Set LIN - Line Item (Detail Only)
NTE02 NONE Freeform Message
(Invoice Instructions)
M AN 01/60
NTE*PMT*NONE
NTE NOTE/SPECIAL INSTRUCTION
NTE01 PMT Payment information for entire transaction set follows O ID 03/03
GEN - Entire Transaction Set LIN - Line Item (Detail Only)
NTE02 NONE Freeform Message
(Payment Instructions)
M AN 01/60
REF*IT*08709*FCSD INTERNAL CUSTOMER NUMBER
REF REFERENCE NUMBERS
REF01 IT Internal Customer Code Qualifier M ID 02/02
REF02 08709 Dealer P&A Code
(Dealer Code/Customer Code)
C AN 01/17
REF03 FCSD ICN Description C AN 01/80
North American Supply Chain Management Page 11 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
REF*CR*19278*CUSTOMER ORDER NUMBER
REF REFERENCE NUMBERS
REF01 CR Customer Reference Number Qualifier M ID 02/02
REF02 19278 Customer/Dealer Order Number
(COR/DOR#)
C AN 01/17
REF03
CUSTOMER ORDER #
Description C AN 01/80
REF*PO*SC035951*PURCHASE ORDER NUMBER
REF REFERENCE NUMBERS
REF01 PO Purchase Order Qualifier M ID 02/02
REF02 SC035951 FCSD Purchase Order Number C AN 01/17
REF03 PO NUMBER Description C AN 01/80
REF*DC*0219278*DEALER PURCHASE ORDER NUMBER
REF REFERENCE NUMBERS
REF01 DC Dealer Purchase Order Number Qualifier M ID 02/02
REF02 034567 Purchase order number C AN 01/17
REF03 DEALER PO # Description C AN 01/80
If no Customer PO is input at time of order, system default of 'no PO' will be transmitted in this field.
REF*ZZ*0T/725*ACTIVITY CODE
REF REFERENCE NUMBERS
REF01 ZZ Mutually Assigned Qualifier M ID 02/02
REF02 OT/725 OT
(Order Type)
/
(Delimiter)
725
(Stock Order)
C AN 01/17
REF03 ACTIVITY CODE Description C AN
01/80
PER*IC*YANKEE FORD SALES*TE*PHONE
PER ADMINISTRATIVE COMMUNICATIONS CONTACT
PER01 IC Information Contact Qualifier M ID 02/02
PER02
JOE WELTY FORD INC
Requester Contact
(Dealer)
Name O AN 01/30
PER03 TE Telephone Qualifier O ID 02/02
PER04 PHONE Requester Contact
(Dealer)
Phone Number C AN 07/20
PER*IC*CONTACT NAME*TE*PHONE
PER ADMINISTRATIVE COMMUNICATIONS CONTACT
PER01 IC Information Contact Qualifier M ID 02/02
PER02
CONTACT NAME
FCSD Contact Name O AN 01/30
PER03 TE Telephone Qualifier O ID 02/02
PER04 PHONE FCSD Contact Phone Number C AN 07/20
PER*EX*EXPEDITOR CONTACT*TE*PHONE
PER ADMINISTRATIVE COMMUNICATIONS CONTACT
PER01 EX Expeditor Contact Qualifier M ID 02/02
PER02 EXPEDITOR FCSD Expeditor Contact name O AN 01/30
PER03 TE Telephone Qualifier O ID 02/02
PER04 PHONE FCSD Expeditor Contact phone number C AN 07/20
North American Supply Chain Management Page 12 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
N1 *BY*FORD CUSTOMER SERVICE DIVISION*92*AF1CC
N1 NAME
N101 BY Buying Party Qualifier M ID 02/02
N102 FCSD FCSD
(Ford Customer Service Division)
M AN 01/30
N103 92 Assigned by Ford Buyer
(Will Contain 92)
M ID 01/02
N104 AF1CC FCSD Direct Ship Sender Code M ID 05/05
N3*P.O. BOX 3333\
N3 ADDRESS INFORMATION
N301 P.O. BOX 3333 Buying Party Street Address M AN 01/35
N4*LIVONIA*MI*48151*92
N4 GEOGRAPHIC LOCATION
N401 LIVONIA Buying Party City Name M AN 02/15
N402 MI Buying Party State/Providence M ID 02/02
N403 48151 Buying Party Postal Code M ID 05/09
N404 92 Country Code O ID 02/02
N1*SU*SUPPLIER NAME*92*SCODE
N1 NAME
N101 SU Supplier Qualifier M ID 02/02
N102 SUPPLIER NAME Supplier Name M AN 01/30
N103 92 Assigned by Ford Buyer
(Will Contain 92)
M ID 01/02
N104 SCODE Supplier GSDB Code M ID 05/05
N3*NE 58
TH
AVE*P.O. BOX
N3 ADDRESS INFORMATION
N301 NE 58
TH
AVE Supplier Street Address M AN 01/35
N302 P.O. BOX Supplier Street Address 2
(If Applicable)
O AN 01/35
N4*CARROLLTON*TX*75006*US
N4 GEOGRAPHIC LOCATION
N401 CARROLLTON Supplier City M AN 02/15
N402 TX Supplier State M ID 02/02
N403 75006 Supplier Postal Code M ID 05/09
N404 US Country Code O ID 01/02
N1*ST*JOE WELTY FORD INC*92*AF1CC
N1 NAME
N101 ST Ship To Qualifier M ID 02/02
N102
JOE WELTY FORD INC
Ship To Customer Name M AN 01/30
N103 92 Assigned by Ford Buyer
(Will Contain 92)
M ID 01/02
N104 AF1CC FCSD Supplier Direct Ship Code M ID 05/05
This name will be different from the Requester Name if there is a DS (Drop Ship) Indicator in the BEG02 segment.
N3*SURVEYOR BLVD
N3 ADDRESS INFORMATION
N301 SURVEYOR BLVD Customer
(Dealer)
Ship To Address
(Address of N102)
M AN 01/35
North American Supply Chain Management Page 13 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
N4*SHIP TO CITY*ST*ZIP CODE*92
N4 GEOGRAPHIC LOCATION
N401 SHIP TO CITY Customer
(Dealer)
City Name M AN 02/15
N402 ST Customer
(Dealer)
State M ID 02/02
N403 ZIP CODE Customer
(Dealer)
Postal Code M ID 05/09
N404 92 Country Code O ID 02/02
Will be the City, State, and Zip of the Ship To Customer in the N102 segment.
DTM*007*060531
DTM DATE/TIME REFERENCE
DTM01 007 Effective Date M ID 03/03
DTM02 060531 Date
(YYMMDD)
M DT 06/06
DTM*036*060531
DTM DATE/TIME REFERENCE
DTM01 036 Expiration Date M ID 03/03
DTM02 060531 Date
(YYMMDD)
M DT 06/06
SHH*DD*069*060531
SHH GENERAL SCHEDULE
SHH01 DD Deliver on Date M ID 02/02
SHH02 069 Promised for Delivery Qualifier M ID 03/03
SHH03 060531 Date Promised for Delivery
(YYMMDD)
C DT 06/06
PO1*00001*4*EA*40.1800**BP*F81Z 16A550 JA
PO1 PURCHASE ORDER BASELINE ITEM DATA
PO101 00001 PO Line Number M AN 01/06
PO102 4 Quantity Ordered M R 01/09
PO103 EA Unit of Measurement Code M ID 02/02
PO104 40.1800 Unit Price C R 01/14
PO106 BP Buyers Part O ID 02/02
PO107 F81Z 16A550 JA Ford Service Part/Motorcraft Number C AN 01/30
PO101 Increments by one (1) for each PO1 within a transaction Set.
If PO104 is '0' (zero) then PO105 is 'NC' (No Charge), otherwise PO105 is not used.
CUR*BY*USD
CUR CURRENCY
CUR01 BY Buying Identifier Party
(Purchaser)
M ID 02/02
CUR02 USD U.S. Dollars M ID 03/03
PID*F****NONE
PID PRODUCT/ITEM DESCRIPTION
PID01 F "Freeform" type followed by part description M ID 01/01
PID05 NONE Description M AN 01/80
CTT*1*4
CTT TRANSACTION TOTALS
CTT01 1 Total Number of LIN segments M N0 01/06
CTT02 4 Total Quantity ordered from PO102 M R 01/10
North American Supply Chain Management Page 14 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
SE*30*0001
SE TRANSACTION SET TRAILER
SE01 30 Number of Included Segments
(Including ST/SE)
M N0 01/06
SE02 0001 Control Number
(Must Match ST02)
M AN 04/09
GE*1*000185878
GE FUNCTIONAL GROUP TRAILER
(End)
GE01 1 Total Number of ST/SE pairs between GS and GE M N0 01/06
GE02 000185878 Control Number
(Must Match GS06)
M N0 01/09
IEA………TRAILER INFORMATION
North American Supply Chain Management Page 15 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
824 Purchase Order Cancellation Transaction Set Layout
ISA………HEADER INFORMATION
GS*AG*SCODE*AF1CC*060531*1430*000000001*X*003010\
Receiving Code, Sender Code, Version
ST*824*0001\
Transaction Set Header
BGN*00*0002011430*060531*1430\
Reference Number, Date, Time
OTI*IR*PO*YA1234*******850\
Rejected Code IR, Y-Release
REF*IT*05460\
Dealer P&A Code (From 850)
REF*CR*06249\
DOR/COR # (From 850)
TED*ZZZ*E03 Customer not participating in program Order Cancelled\
Error Code, Freeform Message
TED*ZZZ*E05 Order below minimum, Order Cancelled\
Error Code, Freeform Message
TED*ZZZ*E11 Order Cancelled\
Error Code, Freeform Message
SE*9*0001\
Total Segment Count
(Including ST/SE)
GE*1*00000001\
Total number of ST/SE pairs between GS & GE, Control Number (Must match GS06)
IEA………TRAILER INFORMATION
Only 1 TED*ZZZ error code will be used in each message. This example is showing all 3 for reference only.
North American Supply Chain Management Page 16 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
824 Purchase Order Cancellation Explanation and Attributes
ISA……… HEADER INFORMATION
GS*AG*SCODE*AF1CC*060531*1430*000000001*X*003010 Attributes
GS FUNCTIONAL GROUP HEADER
(Start)
GS01 AG Application Advice M ID 02/02
GS02 SCODE Supplier GSDB Sender Code M ID 02/12
GS03 AF1CC SDS GSDB Receiver Code M ID 02/12
GS04 060531 Transmission Date
(YYMMDD)
M DT 06/06
GS05 1430 Transmission Time
(HHMM, 24 Hour Clock)
M TM 04/04
GS06 000000001 Control Number
(Must Match GE02)
M N0 01/09
GS07 X Responsible Agency Code
(Use "X")
M AN 01/02
GS08 003010 ANSI X12 Version M ID 01/12
ST*824*0001
ST TRANSACTION SET HEADER
ST01 824 Transaction Set ID
(PO Cancellation)
M ID 03/03
ST02 0001 Control Number
(Must Match SE02)
M AN 04/09
BGN*00*0605311430*060531*1430
BGN BEGINNING SEGMENT
BGN01 00 Original M ID 02/02
BGN02 0605311430 Reference Number; Date & Time Stamp M AN 01/30
BGN03 060531 Transaction Creation Date
(YYMMDD)
M DT 06/06
BGN04 1430 Transaction Creation Time
(HHMM, 24 Hour Clock)
M TM 04/04
OTI*IR*PO*YA1234*******850
OTI ORIGINAL TRANSACTION ID SEGMENT
OTI01 IR Transaction Set is Rejected M ID 02/02
OTI02 PO Purchase Order M ID 02/02
OTI03 YA1234 Original Purchase Order Number from 850 M ID 06/06
OTI10 850 Original Transaction Set M ID 03/03
REF*IT*05460
REF REFERENCE NUMBERS
REF01 IT Internal Customer Code Qualifier M ID 02/02
REF02 05460 Customer/Dealer P&A Code M AN 01/30
REF*CR*06249
REF REFERENCE NUMBERS
REF01 CR Customer Reference Qualifier M ID 02/02
REF02 06249 Customer/Dealer Order Reference Number
(DOR/COR #)
M AN 01/30
TED*ZZZ*E03CUSTOMER NOT PARTICIPATING IN PROGRAM, ORDER CANCELLED
TED TECHNICAL ERROR DESCRIPTION SEGMENT
TED01 ZZZ Mutually Defined Qualifier M ID 01/03
TED02 E03 + Error msg. Error Code, Followed by an Error Freeform Message M AN 01/60
E03 - Customer Not Participating in Program, Order Cancelled
North American Supply Chain Management Page 17 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
TED*ZZZ*E05ORDER BELOW MINIMUM, ORDER CANCELLED
TED TECHNICAL ERROR DESCRIPTION SEGMENT
TED01 ZZZ Mutually Defined Qualifier M ID 01/03
TED02 E05 + Error msg. Error Code, Followed by an Error Freeform Message M AN 01/60
E05 - Order Below Minimum
(Order Not Meeting Minimum Order QTY)
TED*ZZZ*E11ORDER CANCELLED
TED TECHNICAL ERROR DESCRIPTION SEGMENT
TED01 ZZZ Mutually Defined Qualifier M ID 01/03
TED02 E11 + Error msg. Error Code, Followed by an Error Freeform Message M AN 01/60
E11 - Order Cancelled
Only one of the above Error Codes will be used per transaction. They will NOT be used at the same time.
SE*9*0001
SE TRANSACTION SET TRAILER
SE01 9 Total Segment Count
(Including ST/SE)
M N0 01/06
SE02 0001 Control Number
(Must Match ST02)
M AN 04/09
GE*1*000000001
GE FUNCTIONAL GROUP TRAILER
(End)
GE01 1 Total Number of ST/SE Pairs Between GS & GE M N0 01/06
GE02 000000001 Control Number
(Must Match GS06)
M N0 01/09
IEA………TRAILER INFORMATION
Data Match Criteria to support a successful transmission of an 824 from supplier:
Y-Release Number
GSDB Codes (Supplier Code, FCSD Direct Ship code of AF1CC)
Customer Code
Purchase Order Status must be Open "OP"
North American Supply Chain Management Page 18 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
865 Purchase Order Change Transaction Set Layout
ISA………HEADER INFORMATION
GS*CA*SCODE*AF1CC*060531*1430*00000001*X*002001\
Receiving Code, Sender Code, Version
ST*865*0001\
Transaction Set Header
BCA*13*AC*YA1234***060531*****060530\
Request, PO, PO Date, Creation Date
N1*SU*Supplier Name*92*SCODE\
Supplier Name, Supplier GSDB Code
N1*BY*FCSD SDS*92*AF1CC\
FCSD GSDB Mailbox Code
POC*00001*PQ*1*1*EA*34.000**BP*F8TZ 6006 A*RP*F9TZ 6006 A\
PQ - Replacing Part Change
POC*00002*PQ*3*5*EA*34.000**BP*F8TZ 6006 A\
PQ - Part Quantity Change
POC*00003*DI*1*0*EA*34.000**BP*F8TZ 6006 A\
DI - Delete Line Item Change
CTT*3*3\
Total Number of POC Segments
SE*9*0001\
Total Segment Count
(Including ST/SE)
GE*1*00000001\
Total Number of ST/SE pairs between GS & GE, Control Number
(Must Match GS06)
IEA………TRAILER INFORMATION
Not all of the POC segments will be used at the same time. This example is showing all 3 for reference only.
North American Supply Chain Management Page 19 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
865 Purchase Order Change Explanation and Attributes
ISA………HEADER INFORMATION
GS *CA*SCODE*AF1CC*060531*1430*00000001*X*002001 Attributes
GS FUNCTIONAL GROUP HEADER (
Start)
GS01 CA Purchase Order Change M ID 02/02
GS02 SCODE Supplier GSDB Sender Code M ID 02/12
GS03 AF1CC SDS GSDB Receiver Code M ID 02/12
GS04 060531 Transmission Date
(YYMMDD)
M DT 06/06
GS05 1430 Transmission Time
(HHMM, 24 Hour Clock)
M TM 04/04
GS06 000000001 Control Number
(Must Match GE02)
M N0 01/09
GS07 X Responsible Agency Code
(Use "X")
M AN 01/02
GS08 002001 ANSI X12 Version M ID 01/12
ST*865*0001
ST TRANSACTION SET HEADER
ST01 865 Transaction Set ID
(PO Change)
M ID 03/03
ST02 0001 Control Number
(Must Match SE02)
M AN 04/09
BCA*13*AC*YA1234***060530*****060531
BCA BEGINNING SEGMENT FOR PO CHANGE
BCA01 13 Request M ID 02/02
BCA02 AC Acknowledgement with Detail and Change M ID 02/02
BCA03 YA1234 Purchase Order Number
(Same as 850)
M AN 01/18
BCA06 060530 Original Order Date
(YYMMDD)
M DT 06/06
BCA11 060531 Creation Date of the 865
(YYMMDD)
M DT 06/06
N1 *SU**92*SCODE
N1 NAME
N101 SU Supplier Name Qualifier M ID 02/02
N102 Supplier Name Supplier Name C AN 01/35
N103 92 Assigned by FCSD Buyer C ID 01/02
N104 SCODE Supplier GSDB Code M ID 05/05
N1*BY*FCSD SDS*92*AF1CC
N1 NAME
N101 BY Buying Party Qualifier M ID 02/02
N102 FCSD SDS Buying Party's Name C AN 01/35
N103 92 Assigned by Buyer C ID 01/02
N104 AF1CC FCSD GSDB Code M ID 05/05
POC*00002*PQ*1*3*EA*34.0000**BP*F8TZ 6006 A
(Quantity Change)
POC LINE ITEM CHANGE
POC01 00002 Line Item Number O AN 01/06
POC02 PQ Price/Qty Change M ID 02/02
POC03 1 Quantity Ordered O R 01/09
POC04 3 Quantity Left to Ship C R 01/09
POC05 EA Unit Of Measure C ID 02/02
POC06 34.0000 Price C R 01/14
POC08 BP Product Service Qualifier O ID 02/02
POC09 F8TZ 6006 A Original Part on 850 PO C AN 01/30
North American Supply Chain Management Page 20 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
POC*00001*PQ*1*1*EA*34.0000**BP*F8TZ 6006 A*RP*F9TZ 6006 A
(Replacing part)
POC LINE ITEM CHANGE
POC01 00001 Line Item Number O AN 01/06
POC02 PQ Price/Qty Change M ID 02/02
POC03 1 Quantity Ordered O R 01/09
POC04 1 Quantity Left to Ship C R 01/09
POC05 EA Unit Of Measure C ID 02/02
POC06 34.0000 Price C R 01/14
POC08 BP Product Service Qualifier O ID 02/02
POC09 F8TZ 6006 A Original Part on 850 PO C AN 01/30
POC10 RP Product Service Qualifier M ID 02/02
POC11 F9TZ 6006 A Replacing Part Number C AN 01/30
POC*00003*DI*1*0*EA*34.0000**BP*F8TZ 6006 A
(Delete Line Item, line cancelled)
POC LINE ITEM CHANGE
POC01 00003 Line Item Number O AN 01/06
POC02 DI Price/Qty Change M ID 02/02
POC03 1 Quantity Ordered O R 01/09
POC04 0 Quantity Left to Ship C R 01/09
POC05 EA Unit Of Measure C ID 02/02
POC06 34.0000 Price C R 01/14
POC08 BP Product Service Qualifier O ID 02/02
POC09 F8TZ 6006 A Original Part on 850 PO C AN 01/30
Not all of the POC segments will be used at the same time. This example is showing all 3 for reference only.
CTT*3*3
CTT TRANSACTION TOTAL
CTT01 3 Total number of POC Segments within BEG M NO 01/06
CTT02 3 Total Quantity Ordered from POC03 M R 01/10
SE*9*0001
SE TRANSACTION SET TRAILER
SE01 9 Total Segment Count
(Including ST/SE)
M N0 01/06
SE02 0001 Control Number
(Must Match ST02)
M AN 04/09
GE*1*000000001
GE FUNCTIONAL GROUP TRAILER
(End)
GE01 1 Total Number of ST/SE Pairs Between GS & GE M N0 01/06
GE02 000000001 Control Number
(Must Match GS06)
M N0 01/09
IEA………TRAILER INFORMATION
Data Match Criteria to support a successful transmission of an 865 from supplier:
Y-Release Number
GSDB Codes (Supplier Code, FCSD Direct Ship Code of AF1CC)
Purchase Order Date
Part Number
Sourcing
Purchase Order Status must be Open "OP
"
North American Supply Chain Management Page 21 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
865 Important Points
Important Points to remember when sending an 865:
1. When sending an 865, it MUST be sent prior to sending an 856 (ASN).
2. 865 with a DI (delete item) qualifier must contain the original 850 Purchase order quantity.
3. 865 with a PQ (part/quantity) qualifier with a 0 quantity will cancel the line item and Close "CL" the order if
it is not a multi-line order.
4. An 865 with a PQ (part/quantity) qualifier is required for EACH active part level change.
Example: If original 850 order was for part AA and current part is now AD. Supplier must send three (3)
different 865's increasing the level with each message.
1. 865 to change from AA level to AB
2. 865 to change from AB to AC
3. 865 to change from AC to AD
4. Then supplier can ship the order and send an Advanced Ship Notice (856) for the AD level
If the part number is sourced incorrectly, an 865 will reject with an "RC" code and post on the SDS website. Please
contact your SDS Analyst immediately if your experience this issue for resolution.
North American Supply Chain Management Page 22 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
860 PO Change Acknowledgement Transaction Set Layout
ISA……...HEADER INFORMATION
GS*PC*AF1CC*SCODE*000201*1430*000000001*X*002001\
Sender Code, Receiving Code, Version
ST*860*0001\
Transaction Set Header
BCH*06*CP*YA1234***000201****000204*000203\
Beginning Segment
NTE*GEN*NOTE OR SPECIAL INSTRUCTIONS\
Note/Special Instructions
POC*000001*NC*1*0*EA*34.0000*BP*F8TZ 6006 A\
Line Item Change
CTT*1*1\
Total Number of POC Segments & Total Quantity in POC03
SE*6*0001\
Total Segment Count
(Including ST/SE)
GE*1*000000001\
Total Number of ST/SE pairs between GS & GE, Control Number
(Must Match GS06)
IEA………TRAILER INFORMATION
North American Supply Chain Management Page 23 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
860 PO Change Acknowledgement Explanation and Attributes
ISA……...HEADER INFORMATION
GS*PC*AF1CC*SCODE*060531*1430*000000001*X*002001 Attributes
GS FUNCTIONAL GROUP HEADER
(Start)
GS01 PC Acknowledge a PO Change M ID 02/02
GS02 AF1CC SDS GSDB Receiver Code M ID 02/12
GS03 SCODE Supplier GSDB Code M ID 02/12
GS04 060531 Date
(YYMMDD)
M DT 06/06
GS05 1430 Time
(HHMM, 24 Hour Clock)
M TM 04/04
GS06 000000001 Control Number
(Must Match GE02)
M N0 01/09
GS07 X Responsible Agency Code
(Use "X")
M AN 01/02
GS08 002001 ANSI X12 Version M ID 01/12
ST*860*0001
ST TRANSACTION SET HEADER
ST01 860 Transaction Set ID
(PO Change Acknowledgement)
M ID 03/03
ST02 0001 Control Number
(Must Match SE02)
M AN 04/09
BCH*06*CP*YA1234***060530****060531*060531
BCH BEGINNING SEGMENT FOR PO CHANGE REQUEST
BCH01 06 Transaction Set Purpose Code M ID 02/02
06 - Confirmation/Acceptance 10 - Not Found/Rejected
BCH02 CP Change to Purchase Order M ID 02/02
BCH03 YA1234 Purchase Order Number
(Same as 850)
M AN 01/18
BCH06 060530 Original Order Date
(YYMMDD)
M DT 06/06
BCH10 060531 Acknowledgement Date
(YYMMDD)
O DT 06/06
BCH11 060531 PO Change Request Date
(YYMMDD)
O DT 06/06
NTE*GEN*FREE FORM NOTE
NTE NOTE/SPECIAL INSTRUCTION
NTE01 GEN Entire Transaction Set O ID 03/03
NTE02 FREE FORM NOTE Free-Form Note/Special Instruction M AN 01/60
POC*000001*NC*1*0*EA*34.0000**BP*F8TZ 6006 A
POC LINE ITEM CHANGE
POC01 000001 Line Item Number O AN 01/05
POC02 NC No Change
(Concurrence)
M ID 02/02
POC03 1 Quantity Ordered O R 01/09
POC04 0 Quantity Left to Ship C R 01/09
POC05 EA Unit of Measure C ID 02/02
POC06 34.0000 Price
(Info Only)
O R 01/14
POC08 BP Buyer's Part O ID 02/02
POC09 F8TZ 6006 A Original Part on Order, Delete Line C AN 01/30
CTT*1*1
CTT TRANSACTION TOTAL
CTT01 1 Total Number of POC Segments within BEG M NO 01/06
CTT02 1 Total Quantity Ordered from POC03 O R 01/10
North American Supply Chain Management Page 24 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
SE*6*0001
SE TRANSACTION SET TRAILER
SE01 6 Total Segment Count
(Including ST/SE)
M NO 1/06
SE02 0001 Control Number
(Must Match ST02)
M AN 04/09
GE*1*000000001
GE FUNCTIONAL GROUP TRAILER
(End)
GE01 1 Total Number of ST/SE Pairs Between GS & GE M N0 01/06
GE02 000000001 Control Number
(Must Match GS06)
M N0 01/09
IEA………TRAILER INFORMATION
North American Supply Chain Management Page 25 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
870 Order Status (Promise Date) Transaction Set Layout
ISA……...HEADER INFORMATION
GS*RS*SCODE*AF1CC*000201*1430*000000001*X*003010\
Receiving Code, Sender Code, Version
ST*870*0001\
Transaction Set Header
BSR*2*PO*00020011430*000202\
Beginning Segment Report
N1*BY**92*AFICC\
Buying Party FCSD GSDB Mailbox Code
N1*SE**92*SCODE\
Selling Party Supplier GSDB Code
HL*1**O\
Hierarchical Level
PRF*YA1234***000201\
Y-Release Number/Date
REF*IT*05454\
Dealer P&A Code
REF*CR*08014\
DOR/COR #
PO1*1*200*PC***BP*F8TZ 6006 A\
Part Number & Quantity
ISR*ED*000205\
Expected to Ship By Date
QTY*01*200*PC\
Quantity
CTT*1*200\
Total Count of HL Segments
SE*13*0001\
Total Segment Count
(Including ST/SE)
GE*1*000000001\
Total Number of ST/SE pairs between GS & GE, Control Number
(Must Match GS06)
IEA………TRAILER INFORMATION
North American Supply Chain Management Page 26 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
870 Order Status (Promise Date) Explanation and Attributes
ISA………HEADER INFORMATION
GS*RS*SCODE*AF1CC*060531*1430*000000001*X*003010 Attributes
GS FUNCTIONAL GROUP HEADER
(Start)
GS01 RS Order Status Information M ID 02/02
GS02 AF1CC SDS GSDB Receiver Code M ID 02/12
GS03 SCODE Supplier GSDB Code M ID 02/12
GS04 060531 Date
(YYMMDD)
M DT 06/06
GS05 1430 Time
(HHMM, 24 Hour Clock)
M TM 04/04
GS06 000000001 Control Number
(Must Match GE02)
M N0 01/09
GS07 X Responsible Agency Code
(Use "X")
M AN 01/02
GS08 003010 ANSI X12 Version M ID 01/12
ST*870*0001
ST TRANSACTION SET HEADER
ST01 870 Transaction Set ID
(Order Status)
M ID 03/03
ST02 0001 Control Number
(Must Match SE02)
M AN 04/09
BSR*2*PO*0605301430*060531
BSR BEGINNING SEGMENT REPORT
BSR01 2 Prearranged Schedule or Agreement M ID 01/02
BSR02 PO Selected Orders - Unshipped Items M ID 01/02
BSR03 0605301430 Order Status Date/Time M AN 01/30
BSR04 060531 Date Status Report is Created
(YYMMDD)
M DT 06/06
N1*BY**92*AF1CC
N1 NAME
N101 BY Buying Party Qualifier M ID 02/02
N103 92 Assigned by FCSD Buyer C ID 01/02
N104 AF1CC FCSD GSDB Code C ID 02/17
N1*SE**92*SCODE
N1 NAME
N101 SE Selling Party Qualifier M ID 02/02
N103 92 Assigned by FCSD Buyer C ID 01/02
N104 SCODE Supplier GSDB Code C ID 02/17
HL*1**O
HL HIERARCHICAL LEVEL
HL01 1 Number of Loops within the BSR M AN 01/12
HL03 O Order M ID 01/02
PRF*YA1234***060530
PRF PURCHASE ORDER REFERENCE
PRF01 YA1234 Purchase Order Number
(Same as 850)
M AN 01/22
PRF04 060530 Original Release Date
(YYMMDD)
O DT 06/06
North American Supply Chain Management Page 27 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
REF*IT*05454
REF REFERENCE NUMBERS
REF01 IT Internal Customer Code Qualifier M ID 02/02
REF02 05454 FCSD Customer Number
(Dealer P&A Code)
C AN 01/30
REF*CR*08014
REF REFERENCE NUMBERS
REF01 CR Customer Reference Number Qualifier M ID 02/02
REF02 08014 Customer/Dealer Order Number
(COR/DOR #)
C AN 01/30
PO1*1*200*PC***BP*F8TZ 6006 A
PO1 PURCHASE ORDER BASELINE DETAIL
PO101 1 Number of Occurrences of PO1 within PRF O AN 01/06
PO102 200 Quantity Ordered M R 01/09
PO103 PC Unit Of Measure
(Pieces)
M ID 02/02
PO106 BP Buyer's Part Number Qualifier O ID 02/02
PO107 F8TZ 6006 A FCSD Service Part Number C AN 01/30
ISR*ED*060601
ISR ITEM STATUS REPORT
ISR01 ED Expected to Ship by
(Date)
M ID 02/02
ISR02 060601 Expected Ship Date 06/01/06
(YYMMDD)
O DT 06/06
QTY*01*200*PC
QTY QUANTITY
QTY01 01 Discrete
(Net)
Quantity Identifier M ID 02/02
QTY02 200 Expected Ship Quantity M R 01/10
QTY03 PC Unit Of Measure
(Pieces)
O ID 02/02
CTT*1*200
CTT TRANSACTION TOTALS
CTT01 1 Total Count of HL Segments M N0 01/06
CTT02 200 Total Quantity in PO102 O R 01/10
SE*13*0001
SE TRANSACTION SET TRAILER
SE01 13 Total Segment Count
(Including ST/SE)
M NO 01/06
SE02 0001 Control Number
(Must Match ST02)
M AN 04/09
GE*1*000000001
GE FUNCTIONAL GROUP TRAILER (End)
GE01 1 Total Number of ST/SE Pairs Between GS & GE M N0 01/06
GE02 000000001 Control Number
(Must Match GS06)
M N0 01/09
IEA………TRAILER INFORMATION
Data Match Criteria to support a successful transmission of an 870 from supplier:
Y-Release Number
GSDB Codes (Supplier Code & AF1CC)
Customer Code
Purchase Order Create Date
Part Number
Purchase Order Status must be Open (OP)
Quantity
North American Supply Chain Management Page 28 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
856 Advance Ship Notice (ASN) Transaction Set Layout
ISA………HEADER INFORMATION
GS*SH*SCODE*AF1CC*060531*1000*000000001*X*002002F0RD\
Sender Code, Receiving Code, Version
ST*856*0001\
Transaction Set Header
BSN*00*623884*060531*1130\
Purpose Code
(00,01,05)
, Date, Time
DTM*011*060531*1100\
Date/Time Stamp
HL*1**S\
Shipment Level
MEA*PD*G*2000*LB\
Measurements
TD1*CTN90*1\
Carrier Details
(Quantity & Weight)
TD5*B*02*CWCE*M\
Carrier Details
(Routing)
TD3*TL**12345\
Carrier Details
(Equipment)
REF*BM*802366678\
Tracking Number for LTL, otherwise, Bill of Lading
REF*PK*623884\
Packing Slip Number
(Same as ASN Number)
N1*ST**92*AF1CC\
Ship To
(SDS GSDB Code)
N1*SF**92*SCODE\
Ship from
(Supplier GSDB Code)
ITA*C*AX*HC*06***10.00\
Used for International Shipments
ONLY
for Customs Purposes
HL*2*1*I\
Item Level
LIN**BP*F8TZ 6006 A\
Buyer's Part Number
SN1**6*PC*6\
Item Detail Shipment
REF*CO*DLR05454DORA1234\
Dealer P&A Code, Y-Release Number
(Drop the 'Y')
CLD*1*6*CTN90\
Customer's Load Detail
REF*LS*20001\
Label Serial Number
CTT*2*6\
Total Number of HL Segments, Total Quantities from SN102's
SE*21*0001\
Total Segment Count
(Including ST/SE)
GE*01*000000001\
Total Number of ST/SE pairs between GS & GE, Control Number
(Must Match GS06)
IEA………TRAILER INFORMATION
North American Supply Chain Management Page 29 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
856 Advance Ship Notice (ASN) Explanation and Attributes
ISA………HEADER INFORMATION
GS*SH*SCODE*AF1CC*060531*1000*000000001*X*002002FORD Attributes
GS FUNCTIONAL GROUP HEADER
(Start)
GS01 SH Order Status Information M ID 02/02
GS02 SCODE Supplier GSDB Code M ID 02/12
GS03 AF1CC SDS GSDB Receiver Code M ID 02/12
GS04 060531 Date
(YYMMDD)
M DT 06/06
GS05 1000 Time
(HHMM, 24 Hour Clock)
M TM 04/04
GS06 000000001 Control Number
(Must Match GE02)
M N0 01/09
GS07 X Responsible Agency Code
(Use "X")
M AN 01/02
GS08 002002FORD ANSI X12 Version M ID 01/12
ST*856*0001
ST TRANSACTION SET HEADER
ST01 856 Transaction Set ID
(Advance Ship Notice - ASN)
M ID 03/03
ST02 0001 Control Number
(Must Match SE02)
M AN 04/09
BSN*00*623884*060531*1130
BSN BEGINNING SEGMENT ADVANCE SHIP NOTICE
BSN01 00 Transaction Set Purpose Code M ID 02/02
00 - Original 05 - Replacement
BSN02 623884 ASN Number
(Cannot be repeated within One-Year Period)
M AN 02/11
BSN03 060531 Date ASN was Created
(YYMMDD)
M DT 06/06
BSN04 1130 Time ASN was Created
(HHMM, 24 Hour Clock)
M TM 04/04
Direct Ship Suppliers CANNOT send a Cancellation ASN with a '01' Purpose Code (BSN01).
When sending a '05' Purpose Code for a Replacement ASN, add a character (A, B, C…) to the end of the ASN number
(BSN02) to make it a Unique ASN number so it won't reject in the SDS System.
DTM*011*060531*1100
DTM DATE/TIME REFERENCE
DTM01 011 Shipped
(Date & time Stock leaves the dock)
M ID 03/03
DTM02 060531 Date Shipped
(YYMMDD)
M DT 06/06
DTM03 1100 Time Shipped
(HHMM, 24 Hour Clock)
M TM 04/04
HL*1**S
HL HIERARCHICAL LEVEL (SHIPMENT LEVEL)
HL01 1 Hierarchical ID
(Incremented by 1 in each subsequent HL)
M N0 01/06
HL03 S Hierarchical Level
(Shipment)
M ID 01/02
MEA*PD*G*200*LB
MEA MEASURMENTS
MEA01 PD Physical Dimensions
(Measurement Reference ID)
M ID 02/02
MEA02 G Actual Net Weight
(Measurement Qualifier)
M ID 01/03
MEA03 200 Measurement Value
(Value referred to by MEA02)
M R 01/10
MEA04 LB Unit Of Measurement
(LB - Pound KG - Kilogram)
M ID 02/02
North American Supply Chain Management Page 30 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
TD1*CTN90*1
TD1 CARRIER DETAILS (QUANTITY & WEIGHT)
TD101 CTN90 Packaging Code M ID 05/05
TD102 1 Lading Quantity/Number of Packages
(Specified in TD101)
M N0 01/07
Most commonly used Packaging Codes can be found on Page 49.
TD5*B*02*FDEG*M or TD5*B*02*FDE1*A***OR*BUF
TD5 CARRIER DETAIL (ROUTING)
TD501 B Routing Sequence Code
(Use 'B')
M ID 01/02
TD502 02 Identification Code Qualifier
(Use '02')
M ID 02/02
TD503 FDEG Carrier's SCAC Code M ID 02/04
TD504 LT Transportation Method/Type Code
(Refer to MOT on page 39)
M ID 01/02
TD507 OR Location Qualifier C ID 02/02
OR - Origin/Shipping Point (Air Only)
TD508 BUF Location Identifier
(Identifies a Airport Code)
C AN 01/05
If OR (Air Shipment) is used in TD507 – Use Ship From or Ship To Airport Code (ex. "BUF"). If the Airport Code is
unknown, you can use the first 3-5 characters of the 'Ship From' or 'Ship To' city in TD508.
TD507 AND TD508 are REQUIRED when shipping AIR; otherwise not used.
TD3*TL**12345 or TD3*AE**12345
TD3 CARRIER DETAILS (EQUIPMENT)
TD301 TL or AE Conveyance/Trailer # Qualifier
(Refer to MOT on page 39)
M ID 02/02
TD303 12345 Equipment/Trailer Number M AN 01/07
If 'A' is used in TD504 for Air Shipments, use 'AE' for Air Express in TD301.
Most commonly used MOT (Mode Of Transportation) Codes can be found on Page 49.
REF*BM*802366678
REF REFERENCE NUMBERS
REF01 BM Qualifier for "Bill of Material/Lading" M ID 02/02
REF02 802366678 Carrier PRO number for LTL Track & Trace M AN 01/30
The use of at least one REF Segment with a qualifier of "BM" or "AW" is required at the shipment level.
REF*PK*623884
REF REFERENCE NUMBERS
REF01 PK Qualifier for "Packing List" M ID 02/02
REF02 623884 Packing Slip Number
(Identical to the ASN Number)
M AN 01/30
The use of one REF Segment with a qualifier of "PK" to provide packing slip number is required at either the shipment or
item level.
Most commonly used REF Qualifiers can be found on page 49.
N1*ST**92*AF1CC
N1 NAME
N101 ST Ship To
(Entity Identifier Code)
M ID 02/02
N103 92 Assigned by FCSD Buyer
(Will Contain 92)
M ID 02/02
N104 AF1CC Ship To Receiving Location
(Must match N1*ST of the 850)
M AN 05/05
North American Supply Chain Management Page 31 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
N1*SF**92*SCODE
N1 NAME
N101 SF Ship From
(Entity Identifier Code)
M ID 02/02
N103 92 Assigned by FCSD Buyer
(Will Contain 92)
M ID 02/02
N104 SCODE Ship From Location
(Supplier GSDB Code)
M AN 05/05
ITA*C*AX*HC*06***10.00
ITA ALLOWANCE, CHARGE, OR SERVICE
ITA01 C Allowance/Charge Code
(Use 'C')
M ID 01/01
ITA02 AX Agency Qualifier Code (Use 'AX') O ID 02/02
ITA03 HC Special Service Code
(Use 'HC')
C ID 02/10
ITA04 06 Method of Handling Code
(06 - charge to be paid by Customer)
M ID 02/02
ITA07 10.00 Allowance or Charge Total Amount C N2 01/09
This segment is used for INTERNATIONAL SHIPMENTS ONLY to specify the excess handling charge for Customs
purposes.
HL*2*1*I
HL HIERARCHICAL LEVEL
HL01 2 Hierarchical ID
(Incremented by 1 in each subsequent HL)
M AN 01/06
HL02 1 Hierarchical Parent ID
(Required at Item Level)
O AN 01/06
HL03 I Hierarchical Level (Item) M ID 01/02
LIN**BP*F8TZ 6006A
LIN LINE ITEM DETAIL
LIN02 BP Buyer's Part Number Qualifier M ID 02/02
LIN03 F8TZ 6006 A Ford Service Part Number (
Prefix, Base, Suffix)
M AN 01/30
SN1**6*PC*6
SN1 ITEM DETAIL SHIPMENT
SN102 6 Quantity in this Shipment M R 01/07
SN103 PC Unit of Measure
(From 850)
M ID 02/02
SN104 6 Quantity Shipped to Date
(Quantity in SN102)
C R 01/09
CUMS are not utilized in the Direct Ship system. The actual shipment quantity of this shipment (SN102) needs to be
included in the SN104 field.
REF*CO*DLR05454DORA1234
REF REFERENCE NUMBERS
REF01 CO Dealer Direct Qualifier
(Customer Order Number)
M ID 02/02
REF02 DLR05454DORA1234 Text "DLR" followed by the Dealer P&A Code. M AN 01/30
Text "DOR" followed by the last 5 Characters of the
Y-Release Number.
The Dealer P&A Code should ALWAYS be 5 Characters in Length. After the Text 'DOR' ALWAYS drop/minus the 'Y' off
the Y-Release number.
CLD*1*6*CTN90
CLD CUSTOMER'S LOAD DETAIL
CLD01 1 Number of Containers
(Skids, Pallets, boxes, etc.)
M N0 01/05
CLD02 6 Quantity per Container M R 01/07
CLD03 CTN90 Packaging Code/Container Type
(Refer to PG 44 for Codes)
M ID 05/05
North American Supply Chain Management Page 32 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
REF*LS*20001
REF REFERENCE NUMBERS
REF01 LS Bar Code Label Serial Number Qualifier M ID 02/02
REF02 20001 Bar Code Label Serial Number on Carton M AN 01/30
CTT*2*6
CTT TRANSACTION TOTALS
CTT01 2 Total Number of HL Segments M N0 01/06
CTT02 6 Hash Total
(Total of Quantities from SN102's)
M R 01/10
SE*21*0001
SE TRANSACTION SET TRAILER
SE01 13 Total Segment Count
(Including ST/SE)
M NO 01/06
SE02 0001 Control Number
(Must Match ST02)
M AN 04/09
GE*1*000000001
GE FUNCTIONAL GROUP TRAILER
(End)
GE01 1 Total Number of ST/SE Pairs Between GS & GE M N0 01/06
GE02 000000001 Control Number
(Must Match GS06)
M N0 01/09
IEA………TRAILER INFORMATION
Data Match Criteria to support a successful transmission of an 856 from supplier:
Y-Release Number
GSDB Codes (Supplier Code, FCSD Direct Ship Code of AF1CC)
Dealer P&A Code
Part Number
Purchase Order Status must be Open (OP)
Quantity
North American Supply Chain Management Page 33 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
824 Application Advice Transaction Set Layout
ISA………HEADER INFORMATION
GS*AG*AF1CC*SCODE*060531*1430*000000001*X*003010\
Sender Code, Receiving Code, Version
ST*824*0001\
Transaction Set Header
BGN*00*000000000000000000000000000001*060531*1430\
Purpose Code, Reference Number, Date,
Time
OTI*IR*PK*623884*******856\
Accepted/Rejected Code, Original GS Control Number of 856
REF*IT*05454\
Dealer P&A Code from 856
REF*RE*YA1234\
Y-Release Number from 856
TED*011*MISMATCH*****YA1234/SCODE/05456/F8TZ6006AB /623884/0000002\
Error Message
SE*7*0001\
Total Segment Count
(Including ST/SE)
GE*1*000000001\ Total Number of ST/SE pairs between GS & GE, Control Number
(Must Match GS06)
IEA………TRAILER INFORMATION
North American Supply Chain Management Page 34 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
824 Application Advice Explanation and Attributes
ISA………HEADER INFORMATION
GS*AG*AF1CC*SCODE*060531*1430*00000001*X*003010 Attributes
GS FUNCTIONAL GROUP HEADER
(Start)
GS01 AG Order Status Information M ID 02/02
GS02 AF1CC SDS GSDB Sender Code M ID 02/12
GS03 SCODE Supplier GSDB Receiver Code M ID 02/12
GS04 060531 Date
(YYMMDD)
M DT 06/06
GS05 1430 Time
(HHMM, 24 Hour Clock)
M TM 04/04
GS06 000000001 Control Number
(Must Match GE02)
M N0 01/09
GS07 X Responsible Agency Code
(Use "X")
M AN 01/02
GS08 003010 ANSI X12 Version M ID 01/12
ST*824*0001
ST TRANSACTION SET HEADER
ST01 824 Application Advice M ID 03/03
ST02 0001 Control Number (Must Match SE02) M AN 04/09
BGN*00*00000000000000000000000000001*060531*1430
BGN BEGINNING SEGMENT
BGN01 00 Original M ID 02/02
BGN02 0's+1 Control Number
(29 Zeroes and a 1, 30 Characters Total)
M AN 01/30
BGN03 060531 Date
(YYMMDD)
M DT 06/06
BGN04 1430 Time
(HHMM, 24 Hour Clock)
M TM 04/04
OTI*IR*PK*623884*******856
OTI ORIGINAL TRANSACTION ID SEGMENT
OTI01 IR Transaction Set is Rejected M ID 01/02
OTI02 PK Packing Slip Qualifier M ID 02/02
OTI03 623884 Original ASN/Packing Slip Number M AN 01/30
OTI10 856 Original Transaction Set O ID 03/03
REF*IT*05454
REF REFERENCE NUMBERS
REF01 IT Internal Customer Code Qualifier M ID 02/02
REF02 05454 Customer/Dealer P&A Code C AN 01/30
REF*RE*YA1234
REF REFERENCE NUMBERS
REF01 RE Release Number Qualifier M ID 02/02
REF02 YA1234 Original Y-Release Number C AN 01/30
North American Supply Chain Management Page 35 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
TED*006*DUPLICATE*****YA1234/SCODE/05454/F8TZ6006A /623884/0000002
TED TECHNICAL ERROR DESCRIPTION SEGMENT
TED01 006 Duplicate Error Message Qualifier M ID 01/03
TED02 DUPLICATE Free-Form Message O AN 01/60
TED07 YA1234/ Y-Release Number Transmitted on Rejected ASN O AN 01/99
SCODE/ Supplier GSDB Code
05454/ Customer/Dealer P&A Code transmitted on Rejected ASN
F8TZ 6006 A / Part # Transmitted on Rejected ASN
623884/ ASN # Transmitted on Rejected ASN
0000002 Control Number Transmitted on Rejected ASN
TED*008*OVERSHIP******YA1234/SCODE/05454/F8TZ6006A /623884/0000002
TED TECHNICAL ERROR DESCRIPTION SEGMENT
TED01 008 Overship Error Message Qualifier M ID 01/03
TED02 OVERSHIP Free-Form Message O AN 01/60
TED07 YA1234/ Y-Release Number Transmitted on Rejected ASN O AN 01/99
SCODE/ Supplier GSDB Code
05454/ Customer/Dealer P&A Code transmitted on Rejected ASN
F8TZ 6006 A / Part # Transmitted on Rejected ASN
623884/ ASN # Transmitted on Rejected ASN
0000002 Control Number Transmitted on Rejected ASN
TED*011*MISMATCH*****YA1234/SCODE/05454/F8TZ6006A /623884/0000002
TED TECHNICAL ERROR DESCRIPTION SEGMENT
TED01 011 Mismatch Error Message Qualifier M ID 01/03
TED02 MISMATCH Free-Form Message O AN 01/60
TED07 YA1234/ Y-Release Number Transmitted on Rejected ASN O AN 01/99
SCODE/ Supplier GSDB Code
05454/ Customer/Dealer P&A Code transmitted on Rejected ASN
F8TZ 6006 A / Part # Transmitted on Rejected ASN
623884/ ASN # Transmitted on Rejected ASN
0000002 Control Number Transmitted on Rejected ASN
TED*004*INVALID ASN TYPE*****YA1234/SCODE/05454/F8TZ6006A /623884/0000002
TED TECHNICAL ERROR DESCRIPTION SEGMENT
TED01 004 Mismatch Error Message Qualifier M ID 01/03
TED02 INVALID ASN TYPE Free-Form Message O AN 01/60
TED07 YA1234/ Y-Release Number Transmitted on Rejected ASN O AN 01/99
SCODE/ Supplier GSDB Code
05454/ Customer/Dealer P&A Code transmitted on Rejected ASN
F8TZ 6006 A / Part # Transmitted on Rejected ASN
623884/ ASN # Transmitted on Rejected ASN
0000002 Control Number Transmitted on Rejected ASN
TED*005*PART SOURCE ERROR*****YA1234/SCODE/05454/F8TZ6006A /623884/0000002
TED TECHNICAL ERROR DESCRIPTION SEGMENT
TED01 005 Mismatch Error Message Qualifier M ID 01/03
TED02 PART SOURCE ERROR Free-Form Message O AN 01/60
TED07 YA1234/ Y-Release Number Transmitted on Rejected ASN O AN 01/99
SCODE/ Supplier GSDB Code
05454/ Customer/Dealer P&A Code transmitted on Rejected ASN
F8TZ 6006 A / Part # Transmitted on Rejected ASN
623884/ ASN # Transmitted on Rejected ASN
0000002 Control Number Transmitted on Rejected ASN
The TED07 Segments have been broken down for easier explanation.
North American Supply Chain Management Page 36 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
SE*7*0001
SE TRANSACTION SET TRAILER
SE01 7 Total Segment Count
(Including ST/SE)
M NO 01/06
SE02 0001 Control Number
(Must Match ST02)
M AN 04/09
GE*1*000000001
GE FUNCTIONAL GROUP TRAILER
(End)
GE01 1 Total Number of ST/SE Pairs Between GS & GE M N0 01/06
GE02 000000001 Control Number
(Must Match GS06)
M N0 01/09
IEA………TRAILER INFORMATION
North American Supply Chain Management Page 37 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
TED Segment Error Messages Explanation
A '006' Duplicate condition occurs when an ASN has been sent twice with the same ASN number, resulting
in the Direct Ship system's inability to decipher which ASN to accept.
This type of rejection can be caused by an incorrect Replacement ASN. Replacement ASN must be
resent with a "05" Replacement ASN code PLUS adding an alpha or numeric character/digit to the
end of the original ASN number to make it a unique ASN number. Example: 887766 will now be
887766A
The other condition in which a Duplicate Error message is generated is when the supplier
experiences data transmission issues. In response, the supplier sends data a second time when the
GecHub has actually received the first ASN but maybe delayed in sending 997's or pushing data to
FSN (Ford Supplier Network).
An '008' Overship condition occurs when the quantity on the ASN is greater than twice the original order
quantity on the 850 Purchase Order. In this situation the ASN must be resent for the exact quantity on the 850
Purchase Order. Any remaining quantities shipped above and beyond the ordered quantity will require the
supplier to submit a payment dispute along with proof of shipment to the Direct Ship Accounting Department.
A '011' Mismatch condition occurs when either the contents of the ASN do not match up to the 850 Purchase
order based on 5 key match points, or a previous ASN has been sent and the subsequent ASN doesn't have
an open order/line to match to.
The 5 key match points are:
Part Number
Quantity
"Y" Release Number
Customer Code
GSDB Code - Supplier GSDB and AF1CC
An '004' Invalid ASN Type condition occurs when an ASN is sent using the "01" Purpose Code in the BSN01
Element indicating the ASN has not processed. SDS Suppliers cannot submit a cancellation ASN
transaction. This will also occur if a ZERO (0) Quantity is entered on the ASN.
A '005' Part Source Error condition occurs when an ASN tries to process against a part that was incorrectly
sourced or sourcing was changed. Suppliers will not be able to send a valid ASN against the current order
shipped. If you receive this type of rejection, please contact the EDI Coordinator at FCSDEDI@Ford.com for
the following procedure:
Obtain and Complete the "Manual Payment Layout Record Spreadsheet" and return to the EDI
Coordinator.
The EDI Coordinator will forward to the SDS Accounting Department for processing of Manual
Customer Billing/Supplier Payment.
Once the Billing/Payment has been processed, the order will be manually closed in the SDS System.
Supplier will need to Dispute ASN Accuracy occurrences and possible Not-On-Time (NOT) Points on
SDPR scorecard.
North American Supply Chain Management Page 38 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
861 Receipt Advise Transaction Set Layout
ISA………HEADER INFORMATION
GS*SH*AF52M*SCODE*060512*0122*000177915*X*002001\
NOTE SENDER CODE
ST*861*0001\
Transaction Set Header
BRA*2006-05-12-05.09.39.2449640001*060512*00\
Unique Number Assigned by Ford, Create Date
REF*PK*YA1234\
Y-Release number from 856
REF*SI*095019109\
ASN Number from 856
DTM*050*060511\
Material Receive on Date
N1*ST**92*H0TDC\
Ship To TDS Location Code
N1*SF**92*SCODE\
Ship From Supplier Code
RCD**+1*PC\
Received Quantity
SN1**+1*PC\
Quantity Shipped
(ASN Quantity)
LIN**BP*XL5Z 5E212 FA\
Ford Service Part Number
CTT*1*1\
Total Number of RCD Segments
SE*12*0001\
Total Segment Count
(Including ST/SE)
GE*1*000177915\
Total Number of ST/SE pairs between GS & GE, Control Number
(Must Match GS06)
IEA………TRAILER INFORMATION
An 861 will ONLY be transmitted against TDS (Total Distribution System), IDO (International Distribution Operations), or
Association (Mazda/Nissan) orders.
North American Supply Chain Management Page 39 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
861 Receipt Advise Explanation and Attributes
ISA………HEADER INFORMATION
GS*SH*AF52M*SCODE*060512*0122*000177915*X*002001 Attributes
GS FUNCTIONAL GROUP HEADER
(Start)
GS01 SH Order Status Information M ID 02/02
GS02 AF52M Sender GSDB Code M ID 02/12
GS03 SCODE Supplier GSDB Receiver Code M ID 02/12
GS04 060512 Date
(YYMMDD)
M DT 06/06
GS05 0122 Time
(HHMM, 24 Hour Clock)
M TM 04/04
GS06 000177915 Control Number
(Must Match GE02)
M N0 01/09
GS07 X Responsible Agency Code
(Use "X")
M AN 01/02
GS08 002001 ANSI X12 Version M ID 01/12
ST*861*0001
ST TRANSACTION SET HEADER
ST01 861 Transaction Set ID
(Receiving Advice)
M ID 03/03
ST02 0001 Control Number
(Must Match SE02)
M AN 04/09
BRA*2006-05-12-05.09.39.2449640001*060512*00
BRA BEGINNING SEGMENT (RECEIVEING ADVICE)
BRA01 2006-05-12-05.09.39.
449640001 Transaction Set ID
(Assigned by Ford)
M AN 01/30
BRA02 060512 Transaction Create Date
(YYMMDD)
M DT 06/06
BRA03 00 Original Transmission
(Normal)
M ID 02/02
REF*PK*YA1234
REF REFERENCE NUMBERS
REF01 PK Packing Slip Qualifier M ID 02/02
REF02 YA1234 Y-Release Number
(REF*CO Segment on ASN)
C AN 01/11
REF*SI*095019109
REF REFERENCE NUMBERS
REF01 SI Shipper's Identifying Number
(Qualifier)
M ID 02/02
REF02 095019109 Reference Number
(BSN02 of the 856)
C AN 01/11
DTM*050*060511
DTM DATE/TIME REFERENCE
DTM01 050 Material Received on Date Qualifier M ID 03/03
DTM02 060511 Date Material Received
(YYMMDD)
C DT 06/06
N1*ST**92*H0TDC
N1 NAME
N101 ST Ship To
(Entity Identifier Code)
M ID 02/02
N103 92 Assigned by Buyer
(Will Contain 92)
M ID 02/02
N104 H0TDC Ford Bailed Stock Facility
(H0TDC, L9V0C, R3MSA)
M AN 05/05
North American Supply Chain Management Page 40 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
N1*SF**92*SCODE
N1 NAME
N101 SF Ship From
(Entity Identifier Code)
M ID 02/02
N103 92 Assigned by Buyer
(Will Contain 92)
M ID 02/02
N104 SCODE Supplier GSDB Code M AN 05/05
RCD**+1*PC
RCD RECEIVING CONDITIONS
RCD02 +1 Actual Receipt Quantity C R 01/09
RCD03 PC Unit of Measure C ID 02/02
SN1**+1*PC
SN1 ITEM DETAIL
SN102 +1 Number of Units Shipped
(ASN Quantity)
M R 01/09
SN103 PC Unit of Measure C ID 02/02
LIN**BP*XL5Z 5E212 FA
LIN ITEM IDENTIFICATION DETAIL
LIN02 BP Buyers Part Number
(Qualifier)
M ID 02/02
LIN03 X65Z 5E212 FA Ford Service Part Number M AN 01/30
CTT*1*1
CTT TRANSACTION TOTALS
CTT01 1 Number of Line Items
(Total Number of RCD Segments)
M N0 01/06
CTT02 1 Hash Total
(Sum of RCD02's)
M R 01/10
SE*12*0001
SE TRANSACTION SET TRAILER
SE01 12 Total Segment Count
(Including ST/SE)
M NO 01/06
SE02 0001 Control Number
(Must Match ST02)
M AN 04/09
GE*1*000177915
GE FUNCTIONAL GROUP TRAILER
(End)
GE01 1 Total Number of ST/SE Pairs Between GS & GE M N0 01/06
GE02 000177915 Control Number
(Must Match GS06)
M N0 01/09
IEA………TRAILER INFORMATION
The BEG02 Segment in the 850 will have a 'DS' (Drop Ship) Indicator. The N1*ST segment of the 850 will indicate that
the 'Ship To' is "Ford I.D.O./T.D.S."
Export Orders Customer Codes
• 50000-59999
Ford of Mexico Customer Code
• 68084
Ford of Canada Customer Code
• 68097
Ford of Canada FAD Customer Codes
• 68108-68113
Association Orders (Mazda/Nissan) Customer
Codes
• 69000-69100
North American Supply Chain Management Page 41 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
997 Functional Acknowledgement Transaction Set Layout- ACCEPTED
ISA………HEADER INFORMATION
GS*FA*AF1CC*SCODE*060531*0835*000000876*X*002002\
Group Start, Sender Code, Receiving Code
ST*997*0001\
Transaction Set Header, Control Number
AK1*SH*000006167\
Functional Group Response Header
AK2*856*0983\
Transaction being acknowledged
AK5*A\
Acknowledge of Acceptance
AK9*A*1*1*1\
Accepted, # of included transactions sets, received sets, accepted sets
SE*6*0001\
Transaction Set Trailer, Total Number of Segments between ST/SE
GE*1*000000876\
Group End, Number of ST/SE Segments, Control Number
IEA………TRAILER INFORMATION
North American Supply Chain Management Page 42 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
997 Functional Acknowledgement Explanation & Attributes- ACCEPTED
ISA………HEADER INFORMATION
GS*FA*AF1CC*SCODE*060531*0835*000000876*X*002002 Attributes
GS FUNCTIONAL GROUP HEADER
(Start)
GS01 FA Functional Acknowledgement M ID 02/02
GS02 AF1CC Ford Assigned Sender Code M ID 02/12
GS03 SCODE Ford Assigned Receiver Code
(Supplier GSDB Code)
M ID 02/12
GS04 060531 Date
(YYMMDD)
M DT 06/06
GS05 1227 Time
(HHMM, 24 Hour Clock)
M TM 04/04
GS06 000000876 Control Number
(Must Match GE02)
M N0 01/09
GS07 X Responsible Agency Code
(Use "X")
M AN 01/02
GS08 002002 ANSI X12 Version M ID 01/12
ST*997*1001
ST TRANSACTION SET HEADER
ST01 997 Transaction Set ID M ID 03/03
ST02 1001 Control Number
(Must Match SE02)
M AN 04/09
AK1*SH*000006167
AK1 FUNCTIONAL GROUP RESPONSE HEADER
AK101 SH Value in GS01 of transaction being acknowledged M ID 02/02
AK102 000006167 Control number
(GS06 of the message being acknowledged)
M N0 01/09
AK2*856*0983
AK2 TRANSACTION SET RESPONSE HEADER
AK201 856 Type of transaction being acknowledged
(ST01)
M ID 03/03
AK202 0983 Value in
(ST02)
of the transaction being acknowledged M AN 04/09
AK5*A
AK5 TRANSACTION SET RESPONSE TRAILER
AK501 A Transaction Set is Accepted
(Refer to Chart 3 on page 46)
M ID 01/01
AK9*A*1*1*1
AK9 FUNCTIONAL GROUP RESPONSE TRAILER
AK901 A Transaction Set is Accepted
(Refer to Chart 5 on page 46)
M ID 01/01
AK902 1 Number of transaction sets included M N0 01/06
AK903 1 Number of Received Transaction Sets M N0 01/06
AK904 1 Number of Accepted Transaction Sets M N0 01/06
SE*6*0001
SE TRANSACTION SET TRAILER
SE01 6 Number of Included Segments
(Including ST/SE)
M N0 01/06
SE02 0001 Transaction Set Control Number
(Must Match ST02)
M AN 04/09
GE*1*000000876
GE FUNCTIONAL GROUP TRALIER
(End)
GE01 1 Total Number of ST/SE pairs between GS and GE M N0 01/06
GE02 000000876 Control Number (Must Match GS06) M N0 01/09
IEA………TRAILER INFORMATION
North American Supply Chain Management Page 43 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
997 Functional Acknowledgement Transaction Set Layout- REJECTED
ISA………HEADER INFORMATION
GS*FA*AF1CC*SCODE*060531*0835*000030876*X*002002\
Group Start, Sender Code, Receiving Code
ST*997*001\
Transaction Set Header, Control Number
AK1*SH*2616\
Functional Group Response Header
AK2*856*0983\
Transaction being acknowledged
AK3*TD1*7**3\
Segment ID of error, position in transaction set
AK4*2**1*XXXX\
To report errors in data element and identify the location
AK5*R*5\
Acknowledge of Rejection
AK9*R*1*1*0\
Rejected, # of included transactions sets, received sets, accepted sets
SE*6*0001\
Transaction Set Trailer, Total Number of Segments between ST/SE
GE*1*000030876\
Group End, Number of ST/SE Segments, Control Number
IEA………TRAILER INFORMATION
North American Supply Chain Management Page 44 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
997 Functional Acknowledgement Explanation & Attributes- REJECTED
ISA………HEADER INFORMATION
GS*FA*AF1CC*SUPPL*060531*0835*000030876*X*002002 Attributes
GS FUNCTIONAL GROUP HEADER
(Start)
GS01 FA Functional Acknowledgement M ID 02/02
GS02 AF1CC Ford Assigned Sender Code M ID 02/12
GS03 SCODE Ford Assigned Receiver Code
(Supplier GSDB Code)
M ID 02/12
GS04 060531 Date
(YYMMDD)
M DT 06/06
GS05 1227 Time
(HHMM, 24 Hour Clock)
M TM 04/04
GS06 000030876 Control Number
(Must Match GE02)
M N0 01/09
GS07 X Responsible Agency Code
(Use "X")
M AN 01/02
GS08 002002 ANSI X12 Version M ID 01/12
ST*997*001
ST
TRANSACTION SET HEADER
ST01 997 Transaction Set ID M ID 03/03
ST02 1001 Control Number
(Must Match SE02)
M AN 04/09
AK1*SH*2616
AK1 FUNCTIONAL GROUP RESPONSE HEADER
AK101 SH Value in GS01 of transaction being acknowledged M ID 02/02
AK102 2616 Control number
(GS06 of the message being acknowledged)
M N0 01/09
AK2*856*0983
AK2 TRANSACTION SET RESPONSE HEADER
AK201 856 Type of transaction being acknowledged
(ST01)
M ID 03/03
AK202 0983 Value in
(ST02)
of the transaction being acknowledged M AN 04/09
AK3*TD1*7**3
AK3 DATA SEGMENT NOTE
AK301 TD1 Segment in Error M ID 02/03
AK302 7 Segment position in transaction set has error M N0 01/06
AK304 3 Segment Note Code
(Refer to Chart 1 on page 46)
O ID 01/03
AK302 is the numerical count position of this data segment from the start of the transaction set. The transaction set
header (ST Segment) is count position 1.
AK4*2**1*XXXX
AK4 DATA ELEMENT NOTE
AK401 2 Element Number in Error
(Segment AK301)
M N0 01/02
AK403 1 Code Indicating the Error found
(Refer to Chart 2 on page 46)
M ID 01/03
AK404 XXXX Copy of Bad Data Element O AN 01/99
AK5*R*5
AK5 TRANSACTION SET RESPONSE TRAILER
AK501 R Transaction Set is Rejected
(Refer to Chart 3 on page 46)
M ID 01/01
AK502 5 Code indicating the error found
(Refer to Chart 4 on page 46)
O ID 01/03
North American Supply Chain Management Page 45 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
AK9*R*1*1*0
AK9 FUNCTIONAL GROUP RESPONSE TRAILER
AK901 R Transaction Set is Rejected
(Refer to Chart 5 on page 46)
M ID 01/01
AK902 1 Number of transaction Sets Included M N0 01/06
AK903 1 Number of Received Transaction Sets M N0 01/06
AK904 0 Number of Accepted Transaction Sets M N0 01/06
SE*6*0001
SE TRANSACTION SET TRAILER
SE01 6 Number of Included Segments
(Including ST/SE)
M N0 01/06
SE02 0001 Transaction Set Control Number
(Must Match ST02)
M AN 04/09
GE*1*000030876
GE FUNCTIONAL GROUP TRAILER
(End)
GE01 1 Total Number of ST/SE pairs between GS and GE M N0 01/06
GE02 000030876 Control Number
(Must Match GS06)
M N0 01/09
IEA………TRAILER INFORMATION
North American Supply Chain Management Page 46 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
997 Functional Acknowledgement Error Definitions
Chart 1:
Code Definition
1 Unrecognized segment ID
2 Unexpected segment
3 Mandatory segment missing
4 Loop occurs over maximum times
5 Segment within loop exceeds maximum use
Chart 2:
Code Definition
1 Mandatory data element missing.
2 Conditional required data element missing.
3 Too many data elements.
4 Data element too short.
5 Data element too long.
6 Invalid character in data element.
7 Invalid code value.
8 Invalid date.
9 Invalid time.
Chart 3:
Code Definition
A The transmitted transaction set is Accepted.
E The transmitted transaction set is accepted, but errors are noted.
This means that the sender must NOT resend this data.
R The transmitted transaction set is Rejected.
Depending on the error reason, the sender may resend this data.
Chart 4:
Code Definition
1 This transaction set type is not supported.
2 The transaction set trailer is missing.
3 The transaction set control number in the header and trailer do not match
(the value from the header is
used in the acknowledgment).
4 The number of included segments does not match the actual count.
5 One or more segments are in error.
Chart 5:
Code Definition
A The transmitted functional group is Accepted. An acceptance of a functional group is an acceptance
of all transaction sets in that functional group.
E The transmitted functional group is accepted, but errors are noted. This means that the sender must
NOT resend this data.
P Part of the transmitted functional group is accepted by transaction set.
R The transmitted functional group is Rejected.
A rejection of a functional group is a rejection of all transaction sets in that functional group.
Depending on the error reason, the sender may resend this data.
North American Supply Chain Management Page 47 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
TA1 Errors
TA1*265162219*060204*1527*R*021 Attributes
TA1 INTERCHANGE ACKNOWLEDGMENT
TA101 265162219 Interchange Control Number M N0 09/09
(ISA13 of the group being acknowledged)
TA102 060204 Interchange Date
(YYMMDD)
M DT 06/06
TA103 1527 Interchange Time
(HHMM)
M TM 04/04
TA104 R Interchange Acknowledgement Code M ID 01/01
A - Accepted E - Accepted With Errors R - Rejected
TA105 21 Interchange Note Code
(Refer to Chart 6 On page 48)
M ID 03/03
A TA1 will not be accepted by Ford systems in response to documents outbound from Ford. Ford will send the TA1 in
response to documents inbound to Ford without a properly formatted ISA or GS envelope.
North American Supply Chain Management Page 48 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
TA1 Error Note Code Definitions
Chart 6:
Code Definition
000 No Error.
001 The Interchange Control Number in the Header and Trailer do not match.
(The value from
the header is used in the acknowledgement).
002* This Standard as noted in the Control Standards Identifier is not Supported.
003 This Version of the Controls is not Supported.
004 The Segment Terminator is Invalid.
005 Bad Interchange ID Qualifier for sender.
006 Bad Interchange Sender ID.
007 Bad Interchange ID Qualifier for Receiver.
008 Bad Interchange Receiver ID.
009 Network provider could not deliver message because of unknown Receiver ID as qualified.
010 Bad Authorization Information Qualifier Value.
011 Bad Authorization Information Value.
012 Bad Security Information Qualifier Value.
013 Bad Security Information Value.
014 Bad Interchange Date Value.
015 Bad Interchange Time Value.
016 Bad Interchange Standards Identifier Value.
017 Bad Interchange Version ID Value.
018 Bad Interchange Control Number Value.
019 Invalid Acknowledgement Requested Value – Must be "0" (Zero).
020 Bad Test Indicator Value – Must be "P".
021 Bad Number of Included Groups Value.
022 Invalid Control Structure.
023 Improper (premature) end-of-file (transmission).
024 Invalid Interchange Content (e.g. bad GS Segment).
025 Duplicate Interchange Control Number.
026 Invalid Data Element Separator.
Code 002 is used as a default code by the Mailbox System when there is a problem with the data that cannot be
determined.
North American Supply Chain Management Page 49 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
Mode of Transportation (MOT), Packaging Codes, & REF Qualifiers
Most Commonly Used MOT Codes
Code Description
A Air
AE Air Express
C Consolidation
E Expedited Truck
G Piggyback
H Customer Pickup
JT Just in time
LT Less Than Trailer Load (LTL)
M Motor (Common Carrier)
O Containerized Ocean
PA Pooled Air
PC Private Carrier
PG Pooled Piggyback
PP Pool to pool*
PR Pooled Rail*
PT Pooled Truck
R Rail
RR Roadrailer
S Ocean
U Private Parcel Service
W Inland Waterway
ZZ On hand at pool
Most Commonly Used Packaging Codes
Code Description
PLT90 Pallet
BOX90 Box
LSE90 Loose
CTN90 Carton
SKD90 Skid
COL52 Steel Coil
LIF52 Metal Lift
BIN90 Bin
RCK90 Rack
Most Commonly Used REF Qualifiers
Code Description
AW Air Bill Number
BM Bill of Material/lading
CN Carton Number
PK Packing Slip
LS Label Serial Number
CO Dealer Direct
FR Freight Bill Number
VM Vessel Name
North American Supply Chain Management Page 50 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
Glossary of Acronyms
GSDB (Global Supplier Data Base):
Unique ID Code Ford Assigns Each Trading Partner.
GSEC (Global Supplier Electronic Communications):
Primary point of contact between Ford and its suppliers in matters relating to the transfer of electronic data.
EDI (Electronic Data Interchange):
The Exchange of structured data between computer applications using agreed rules. Ford uses X12 as its
standard rules.
ANSI ASC X12 (American National Standards Institute Accredited Standards Committee X12):
Created in 1984, X12 North American Format Language is an EDI Communication standard, which includes
directories and guidelines for data transmission between trading partners through out the supply chain.
OEM (Original Equipment Manufacturer):
Final point of assembly prior to sale of goods.
VAN (Value Added Network):
Third party company suppliers can contract to connect to the GECHub to process their EDI transactions.
GECHub (Global Electronic Commerce Hub):
A server that supports all trading partners' connectivity, providing the communication interface, and security
for access to Ford systems.
ANX (Advance Network Exchange):
A dedicated, high-performance data network, that enables subscribed buyers and sellers located all over the
world to communicate, collaborate, and transact business quickly, reliably, and securely.
The ANX Network is private (isolated from the public internet).
Covisint:
Provides a communication link between a company and the supply chain that it relies upon to manufacture its
products.
SDS:
Supplier Direct Ship
PDC/PRC:
Parts Distribution Center/Parts Redistribution Center
SPOC (Single Point Of Contact):
Support Services/Helpdesk
FCSD:
Ford Customer Service Division
SOLMIS (Supply On-Line Management Information Systems):
Ford Motor Company's communication network.
ASCII (ask-key) (American Standard Code for Information Interchange):
Computers can only understand numbers, so an ASCII code is the numerical representation of a character
such as 'a' or '@'.
Example:
If someone says they want your document in ASCII format, they want 'plain' text with no formatting such as
tabs, bold, or underscoring - the raw format that any computer can understand. This is usually so they can
easily import the file into their own applications without issues. Notepad.exe creates ASCII text or in MS Word
you can save a file as 'text only' by choosing 'plain text' as the "save as type".
North American Supply Chain Management Page 51 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
Glossary of Attributes
M (Mandatory):
If the segment is Mandatory for ANSI, it remains mandatory for Ford. If the segment is Optional for ANSI, but
Mandatory for Ford, it is designated by the letter "M".
O (Optional):
If the segment is optional for ANSI, but its requirements vary between Ford Applications, it is designated by
the letter "O". You must read the Ford "Optional" segments in detail to determine what Ford applications
require them.
C (Conditional):
A data element requirement designator that indicates that the presence of a specified data element is
dependent on the value or presence of other data elements in the segment/segments.
N (Not Used):
If the segment is not currently used by Ford, it is designated by the letter "N". This does not preclude future
implementation.
ID (Code Value/Identification):
If ANSI ASC X12 maintains the list of ID codes, the code values follow the data element definition
in the data element dictionary.
AN (String/Alphanumeric):
String data element types contain alphanumeric characters, including imbedded spaces.
DT (Date):
The date in the format: YYMMDD.
TM (Time):
The time in the format: HHMM (24-hour clock).
N0 (Numeric):
Numeric data element types contain only numeric characters and a minus sign if they are
negative. The digit after “N” defines the number of implied decimal positions. Therefore, N0
indicates a numeric value with no decimal position (a whole number).
N2 (Numeric):
Numeric data element types contain only numeric characters and a minus sign if they are
negative. The digit after “N” defines the number of implied decimal positions. Therefore, N2 indicates numeric
value with implied two decimal positions.
R (Decimal):
Decimal data element types contain only numeric characters, a decimal point (if needed), and
a minus sign if negative.
Field Lengths:
The field lengths are shown as 01/02, and so forth, are explained as 01 being the minimum character length
and 02 being the maximum character length for that particular element.
North American Supply Chain Management Page 52 of 52 Date Issued: 06/20/2006
Supplier Development Date Revised: 12/10/2007
EDI Manual Revisions
Date Section Page(s)
12/05/2007
Entire Manual Reformatted 1 - 52
12/10/2007
EDI Coordinator Contact Email Added
4
