brownartcorp.combrownartcorp.com/gsdb3/Suppliersys/attachments/NLEM.… · Web viewRCD06 +/-200 Quantity in Question (Difference between SN102 and RCD02) C R 01/09. RCD07 PC Measurement

This manual is available at https://web.pslsupp.ford.com/

Ford Customer Service Division North America

PDC (Network Locations) EDI Manual

(Excluding Mazda & Nissan Unique)

This document is a sub-set with specific FCSD requirements, which may differ from the Ford Corporate Guidelines.

TABLE OF CONTENTS

3FCSD Releasing Schedule and Mailbox Availability

EDI Coordinators3

Ford Single Point of Contact (SPOC) Support Services4

Establishing an EDI Connection to the GEC Hub4

Connectivity Methods5

Ford Approved VAN's5

Network Locations ANSI X12 Required EDI Transactions6

Interchange Control Structure including Explanation and Attributes7

830 Material Release (Intermediate Consignee/Packager) Transaction Set Layout8

830 Material Release (Network Location/PDC/PRC) Transaction Set Layout9

830 Material Release Explanation and Attributes10

861 Receipt Advise Transaction Set Layout14

861 Receipt Advise Explanation and Attributes15

856 Advance Shipment Notice (Intermediate Consignee/Packager) Transaction Set Layout17

856 ASN (Intermediate Consignee/Packager) Explanation and Attributes18

856 ASN (Network Location/PDC/PRC) Transaction Set Layout23

856 ASN (Network Location/PDC/PRC) Explanation and Attributes24

856 ASN (Dealer Direct Emergency Order) Transaction Set Layout28

856 ASN (Dealer Direct Emergency Order) Explanation and Attributes29

997 Functional Acknowledgement Transaction Set Layout- ACCEPTED33

997 Functional Acknowledgement Explanation and Attributes - ACCEPTED34

997 Functional Acknowledgement Transaction Set Layout- REJECTED35

997 Functional Acknowledgement Explanation and Attributes - REJECTED36

997 Functional Acknowledgement Error Definitions38

TA1 Errors40

TA1 Error Note Code Definitions41

Mode of Transportation (MOT), Packaging Codes, & REF Qualifiers42

Glossary of Acronyms43

Glossary of Attributes44

EDI Manual Revisions45

FCSD Releasing Schedule and Mailbox Availability TC "FCSD Releasing Schedule and Mailbox Availability" \f C \l "1"

Cycle releasing will issue four (4) evenly balanced weekly releasing cycles throughout the month instead of releasing all parts at the beginning of the month. Each of the four (4) cycles will have a balance of lines and pieces for each supplier. All parts will be assigned to one (1) of the four (4) cycles.

Releases will be available to FCSD suppliers every Saturday Morning EST (Eastern Standard Time).

Emergency and Exception releases will be available daily, Monday through Thursday, at 8:00 PM EST.

Suppliers are required to access their SOLMIS Mailbox DAILY to receive the Replenishment, Exception, and Emergency releases.

Determination of Firm (Authorized) Requirements and Planning Quantities in an 830 Material Release

FCSD Releases requirements to suppliers utilizing twenty (20) forecasted schedules with the associated CUM quantities. The first ten (10) forecasted schedules (FST Segment) identifies the next ten (10) weekly requirements followed by ten (10) forecasted schedules identifying the ten (10) monthly requirements.

Firm and Planning CUM can be determined by the Authorization Date (ATH Segment) in the 830 Material Release. The date and CUM Quantity stated in the ATH Segment sets the line between the firm quantities and the planning quantities. Any DATES and CUM Quantities listed BEFORE the Authorization Date are firm requirements. All other CUM Quantities are for planning purposes only.

Due to occasional Intermediate Consignee (Packager) Changes, Ford REQUIRES that you DO NOT HARD CODE the Intermediate Consignee (Packager) Code in the N1*IC Segment or the address of the Intermediate Consignee (Packager) anywhere in your EDI System.

EDI Coordinators TC "EDI Coordinators" \f C \l "1" :

FCSD-NA:[email protected]

FoC (Ford Of Canada): [email protected]

Ford Single Point of Contact (SPOC) Support Services TC "Ford Single Point of Contact (SPOC) Support Services" \f C \l "1"

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.

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

The SPOC Help Desk phone number is: (888) 317- 4957 or (313) 317-4957.

When calling the GEC Hub Helpdesk about EDI issues, please ask for your ticket to be routed to the GEC Hub EDI Helpdesk for quicker response.

Establishing an EDI Connection to the GEC Hub TC "Establishing an EDI Connection to the GEC Hub" \f C \l "1"

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 first 4 characters of your Supplier GSDB Code; Click 'Submit'

5. Check the supplier code listed under "New GSDB Connection Request" or "Change existing Connection to the GEC Hub"; 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.

Connectivity Methods TC "Connectivity Methods" \f C \l "1"

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.

Ford Approved VAN's TC "Ford Approved VAN's" \f C \l "1" :

VAN Provider

Website

Toll Free

Direct

Covisint

www.covisint.com

(888) 222-1700

-

ELIT Services

http://www.business-exchange.canada.eds.com/ELIT/

(866) 214-0108

(248) 365-2248

GXS (GEIS)

www.gxs.com

(800) 560-4347

(301) 340-4000

IBM

www.gxs.com

(800) 560-4347

(301) 340-4000

iConnect

www.iconnect-corp.com

(877) 327-9334

(734) 930-4274

Inovis/GXS (Merged)

www.gxs.com/inovis/

(877) 446-6847

-

Kleinschmidt

www.kleinschmidt.com

-

(847) 945-1000

Sterling Commerce

www.sterlingcommerce.com

(800) 876-9772

(614) 793-7000

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

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 [email protected].

NETWORK LOCATIONS ANSI X12 REQUIRED EDI TRANSACTIONS TC "Network Locations ANSI X12 Required EDI Transactions" \f C \l "1"

Suppliers communicating via EDI with FCSD North American Supply Chain are Required to adhere to the following ANSI X12/Ford EDI requirements.

FCSD Ford/ANSI X12 Transaction Sets

830 (FCSD to Supplier)Material Release (ver 002001FORD) – Informs the supplier of shipment schedule.

861 (FCSD to Supplier)Receipt Advice (ver 002001) – An acknowledgement of receipt and payment to the supplier for the shipment.

856 (Supplier to FCSD)Advance Shipping Notice (ver 002002FORD) - Provides FCSD with Shipment Confirmation of 830 Material Releases. The 856 must mirror the information in the most recent 830 Material Release.

997 (FCSD to Supplier)Functional Acknowledgement (ver 002002) – When supplier sends 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.

Interchange Control Structure including Explanation and Attributes TC "Interchange Control Structure including Explanation and Attributes" \f C \l "1"

Sample Interchange Control Structure with explanation – HEADER/TRAILER INFORMATION

ISA*00* *00* *ZZ*SCODE *ZZ*F159B *060101*1241*U*00200*000016285*0*P*<

Attributes

ISA

INTERCHANGE CONTROL HEADER (Start)

ISA0100

Use "00" (zeroes)

MID02/02

ISA02SPACES

Use 10 (ten) spaces

MAN10/10

ISA0300

Use "00" (zeroes)

MID02/02

ISA04SPACES

Use 10 (ten) spaces

MAN10/10

ISA05ZZ

Interchange ID Qualifier (Use "ZZ")MID02/02

ISA06SCODE

Interchange Sender ID (Left Justified and filled with blanks)MID15/15

ISA07ZZ

Interchange ID Qualifier (Use "ZZ")MID01/02

ISA08F159B

Interchange Receiver ID (Left Justified and filled with blanks)MID15/15

ISA09060101

Date of Transmission (YYMMDD)

MDT06/06

ISA101241

Time of Transmission (HHMM, 24 Hour Clock)MTM04/04

ISA11U

Use "U" for USA

MID01/01

ISA1200200

Version ID Use "00200"

MID05/05

ISA13 000016285

Control Number (Must Match IEA02)MN009/09

ISA140

Use "0" (zero)

MID01/01

ISA15PTest Indicator (Always use "P")

MID01/01

ISA16<Sub Element Separator (Use '<' ASCII Hex Value) MAN01/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 with the GEC Hub only, for Production it will be F159B.

IEA*1*000016285

IEA

INTERCHANGE CONTROL TRAILER (End)

IEA011Number of GS/GE Pairs (Between ISA & IEA)MN001/15

IEA02000016285Control Number (Must Match ISA13)MN009/09

830 Material Release (Intermediate Consignee/Packager) Transaction Set Layout TC "830 Material Release (Intermediate Consignee/Packager) Transaction Set Layout" \f C \l "1"

Sample 830 Transaction Set Layout from FCSD to Supplier for Shipment to an Intermediate Consignee (Packager)

ISA………HEADER INFORMATION

GS*PO*AF52M*SCODE*060107*1924*000000001*X*002001FORD\ ( Receiving Code, Sender Code, Version

ST*830*0001\ ( Transaction Set Header

BFR*05**613-1A*SH*C*050801*070103*060107\ ( Beginning Segment for Planning Schedule

N1*ST**92*AF52M\

( Ship To (Receiving Code)

N1*SF**92*SCODE\

( Ship From (Supplier Code)

N1*BT*92*B82AA\

( Bill To Code (Ford Field Accounting Code)

N1*IC*92*PCODE\

( Intermediate Consignee (Packager Code)

LIN**BP*D8TZ 9840704 A*PO*SC 01364*EC*E0TB 9843121 AB*FI*00315809\ ( Part #'s, PO #

UNT*PC\

( Unit of Measure

PER*EX* CONTACT NAME*TE*CONTACT PHONE\

( Contact Name, Contact Phone

SDP*Y*Y\

( Ship Delivery Pattern

NTE*LIN*PKG. SPEC. DATE 2006-03-19\

( Special Instructions, Free Form Message

NTE*LIN*PKG. EFFEC. DATE 2006-06-19\

( Special Instructions, Free Form Message

FST*302*D*W*060105\

( Total CUM Required by week of 1/05/06 (Planning, Weekly)

FST*414*D*W*060112\

FST*414*D*W*060119\

FST*517*D*W*060126\

FST*517*D*W*060202\

FST*517*D*W*060209\

FST*517*D*W*060216\

FST*517*D*W*060223\

FST*517*D*W*060302\

FST*517*D*W*060309\

FST*517*D*F*050801*060329\

( Flexible Planning from "Begin Date" to "End Date"

FST*623*D*F*050801*060503\

FST*623*D*F*050801*060531\

FST*704*D*F*050801*060628\

FST*786*D*F*050801*060802\

FST*786*D*F*050801*060830\

FST*851*D*F*050801*061004\

FST*851*D*F*050801*061101\

FST*851*D*F*050801*061129\

FST*851*D*F*050801*070103\

ATH*FI*060206*517**050801\

( Finished Goods CUM Quantity authorized to ship through 2/06/06

ATH*MT*060405*623**050801\

( Raw Material CUM Quantity authorized to procure through 4/05/06

SHP*01*126*011*050912\

( Discrete Quantity, Shipped or Beginning Inventory Date

REF*SI*217535\( Shipment Identification on last ASN

SHP*02*302*011*050801**050912\( CUM Quantity, Date, Date of last shipment

CTT*1*12192\

( Total Number of LIN segments, Sum of FST01's

SE*39*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

830 Material Release (Network Location/PDC/PRC) Transaction Set Layout TC "830 Material Release (Network Location/PDC/PRC) Transaction Set Layout" \f C \l "1"

Sample 830 Transaction Set Layout from FCSD to Supplier for Shipment to A Network Location (PDC/PRC)


GS*PO*AF52M*SCODE*060107*1924*000000001*X*002001FORD\ ( Receiving Code, Sender Code, Version

ST*830*0001\ ( Transaction Set Header

BFR*05**613-1A*SH*C*050801*070103*060107\ ( Beginning Segment for Planning Schedule

N1*ST**92*AF30A\( Ship To (Network Location Receiving Code)

N1*SF**92*SCODE\( Ship From (Supplier Code)

N1*BT*92*B82AA\( Bill To Code (Ford Field Accounting Code)

LIN**BP*D8TZ 9840704 A*PO*SC 01364*EC*E0TB 9843121 AB*FI*00315809\ ( Service, PO, Engineering #'s

UNT*PC\( Unit of Measure

PER*EX* CONTACT NAME*TE*CONTACT PHONE\( Contact Name, Contact Phone

SDP*Y*Y\( Ship Delivery Pattern

NTE*LIN*PKG. SPEC. DATE 2006-03-19\ ( Special Instructions, Free Form Message

NTE*LIN*PKG. EFFEC. DATE 2006-06-19\( Special Instructions, Free Form Message

FST*302*D*W*060105\ ( Total CUM Required by week of 1/05/06 (Planning, Weekly)

FST*414*D*W*060112\

FST*414*D*W*060119\

FST*517*D*W*060126\

FST*517*D*W*060202\

FST*517*D*W*060209\

FST*517*D*W*060216\

FST*517*D*W*060223\

FST*517*D*W*060302\

FST*517*D*W*060309\

FST*517*D*F*050801*060329\( Flexible Planning from "Begin Date" to "End Date"

FST*623*D*F*050801*060503\

FST*623*D*F*050801*060531\

FST*704*D*F*050801*060628\

FST*786*D*F*050801*060802\

FST*786*D*F*050801*060830\

FST*851*D*F*050801*061004\

FST*851*D*F*050801*061101\

FST*851*D*F*050801*061129\

FST*851*D*F*050801*070103\

ATH*FI*060206*517**050801\ ( Finished Goods CUM Quantity authorized to ship through 2/06/06

ATH*MT*060405*623**050801\ ( Raw Material CUM Quantity authorized to procure through 4/05/06

SHP*01*126*011*050912\ ( Discrete Quantity, Shipped or Beginning Inventory Date

REF*SI*217535\

( Shipment Identification on last ASN

SHP*02*302*011*050801**050912\

( CUM Quantity, Date of last shipment

CTT*1*12192\ ( Total Number of LIN segments, Sum of FST01's

SE*39*0001\

( Total Segment Count (Including ST/SE)

GE*1*000000001\ ( Total Number of ST/SE pairs between GS & GE, Control Number (Must match GS06)


830 Material Release Explanation and Attributes TC "830 Material Release Explanation and Attributes" \f C \l "1"


GS*PO*AF52M*SCODE*060107*1924*000000001*X*002001FORD

Attributes

GS

FUNCTIONAL GROUP HEADER (Start)

GS01PO

Functional Group Qualifier

MID02/02

GS02AF52M

Ford Assigned Sender Code

MID02/12

GS03SCODE

Ford Assigned Receiver Code (Supplier GSDB Code)MID02/12

GS04060107

Date (YYMMDD)

MDT06/06

GS051924

Time (HHMM, 24 Hour Clock)

MTM04/04

GS06000000001

Control Number (Must Match GE02)MN001/09

GS07X

Responsible Agency Code (Use "X")MAN01/02

GS08002001FORD

ANSI X12 Version

MID01/12

ST*830*0001

ST

TRANSACTION SET HEADER

ST01830Transaction Set ID (Planning Schedule)MID03/03

ST020001

Control Number (Must Match SE02)MAN04/09

BFR*05**613-1A*SH*C*050801*070103*060107

BFR

BEGINNING SEGMENT (Forecast/Material Release)

BFR0105

Replace (First release after annual CUM reset - 00)MID02/02

BFR03613-1A

Release Number (Ford Program Number)CAN01/30

BFR04SH

Schedule Type Qualifier

MID02/02

BFR05C

Schedule Quantity Qualifier ("C" = Cumulative Quantities)MID01/01

BFR06050801

Accumulations Begin Date (YYMMDD) MDT06/06

BFR07070103

Horizon End Date (YYMMDD)

MDT06/06

BFR08060107

Release Issue Date (YYMMDD)

MDT06/06

N1*ST**92*AF52M

N1

NAME

N101ST

Ship To

MID02/02

N10392

Assigned by Ford Buyer (Will Contain 92)MID01/02

N104AF52M

Ford Assigned Mailbox Code

MAN05/05

· Suppliers will only see AF52M in the N1*ST Segment if they are shipping to a IC (Packager). Otherwise, they will see their release to location (AF30A, AF31A, AF30E, AF1JA., etc…

N1*SF**92*SCODE

N1

NAME

N101SF

Ship From

MID02/02

N10392


N104SCODE

Ford Assigned Code (Supplier GSDB Code)MAN05/05

N1*BT*92*B82AA\

N1

NAME

N101BT

Bill To

MID02/02

N10392


N104B82AABill To Code (Ford Field Accounting Code)MAN05/05

N1*IC*92*PCODE\

N1

NAME

N101IC

Intermediate Consignee

MID02/02

N10392


N104PCODEPackager Code

MAN05/05

· Suppliers will only see the N1*IC Segment if they are shipping their requirements to an IC (Packager).

LIN**BP*D8TZ 9840704 A*PO*SC 01364*EC*E0TB 9843121 AB*FI*00315809

LIN

ITEM IDENTIFICATION DETAIL

LIN02BP

Buyer's Part Number

MID02/02

LIN03D8TZ 9840704 AFord Service Part Number (In form of Prefix, Base, Suffix)MAN01/30

LIN04PO

Purchase order Number

OID02/02

LIN05SC 01364

Ford Purchase Order Number

CAN01/30

LIN06EC

Engineering Part Number

CID02/02

LIN07E0TB 9843121 ABFord Engineering Number (In form of Prefix, Base, Suffix)CID02/02

LIN08FI

Finis Part Number

CAN01/30

LIN0900315809

European Part Number

CAN01/30

PRS*3

PRS

PART RELEASE STATUS

PRS013

Balance out part (7 - Final Release for this cancelled part) MID01/02

· PRS (Part Release Status) - Is used only when the part is to be coded 'Balance Out' or 'Final Release'.

UNT*PC

UNT

UNIT DETAIL

UNT01PC

Measurement Code

MID02/02

PER*EX* CONTACT NAME*TE*CONTACT PHONE

PER

ADMINISTRATIVE COMMUNICATIONS CONTACT

PER01EX

Qualifier for Information Contact

MID02/02

EX - Expeditor RD - Receiving Dock

PER02CONTACT NAMEExpeditor Contact Name

OAN01/35

PER03TE

Qualifier for Telephone

OID02/02

PER04CONTACT PHONEContact Telephone Number

OAN07/21

SDP*Y*Y

SDP

SHIP/DELIVERY PATTERN

SDP01Y

Ship/Delivery or Calendar Pattern Code (Y=None)MID01/02

SDP02Y

Ship/Delivery Pattern Time Code (Y=None)MID01/01

NTE*LIN*PKG. SPEC. DATE 1998-03-19

NTE

NOTE

NTE01LIN

Line Item (Detail Level) or GEN (Heading Level)OID03/03

NTE02PKG.SPEC.DATE Free Form Message

MAN01/60

998-03-19

FST*302*D*W*060105

FST

FORECAST SCHEDULE

FST01302

Quantity

MR01/10

FST02D

Planning

MID01/01

FST03W

Weekly Bucket (Monday through Sunday)MID01/01

FST04060105

Weekly Starting Date (YYMMDD)MDT06/06

FST*517*D*F*050801*060329

FST

FORECAST SCHEDULE

FST01

517

Quantity

MR01/10

FST02

D

Planning

MID01/01

FST03

F

Flexible Interval (From Date "X" through Date "Y")MID01/01

FST04

050801

Flexible CUM Quantity Start Date (YYMMDD)MDT06/06

FST05

060329

Flexible Period ending date (YYMMDD)ODT06/06

ATH*FI*060206*517**050801

ATH

RESOURCE AUTHORIZATION

ATH01FI

Finished (Labor, Material, and Overhead/Burden)MID02/02

ATH02060206

Last day of the week (YYMMDD)

MDT06/06

ATH03517

CUM QTY authorized through date in ATH02MR01/10

ATH05050801

CUM Qty Start Date (YYMMDD)

MDT06/06

· The date and CUM Quantity stated in the ATH Segments sets the line between the Firm and Planning Quantities. ANY DATES AND CUM QUANITIES LISTED BEFORE THE AUTHORIZATION DATE ARE FIRM REQUIREMENTS.

ATH*MT*060405*623**050801

ATH

RESOURCE AUTHORIZATION

ATH01MT

Material

MID02/02

ATH02060405

Last Day of the Week (YYMMDD)

MDT06/06

ATH03623

CUM QTY authorized through date in ATH02MR01/10

ATH05050801

CUM Quantity Start Date (Beginning inventory date)MDT06/06

· There will always be at most one ATH*FI and one ATH*MT for each LIN.

SHP*01*126*011*050912

SHP

SHIPPED/RECEIVED INFORMATION

SHP0101

Discrete Quantity Qualifier

OID02/02

SHP02126

Quantity

CR01/10

SHP03011

Shipped

CID03/03

SHP04050912

Shipped Date or Beginning Inventory Date (YYMMDD)CDT06/06

REF*SI*217535

REF

REFERENCE NUMBER

REF01SI

SID (Shipper's Identifying Number for Shipment)MID02/02

REF02217535

Reference Number (ASN Number of Last Shipment)MAN01/30

SHP*02*302*011*050801**050912

SHP

SHIPPED/RECEIVED INFORMATION

SHP0102

Cumulative Quantity Qualifier

OID02/02

SHP02302

Quantity

CR01/10

SHP03011

Shipped

CID03/03

SHP04050801

Shipped date or Beginning Inventory Date (YYMMDD)CDT06/06

SHP06050912

Date of last Shipment (YYMMDD)

CDT06/06

CTT*1*12192

CTT

TRANSACTION TOTALS

CTT011

Total Number of LIN segments

MN001/06

CTT0212192

Hash Totals (Sum of FST01's)

MR01/10

SE*39*0001

SE

TRANSACTION SET TRAILER

SE0139

Total Segment Count (Including ST/SE)MN001/06

SE020001

Control Number (Must Match ST02)MAN04/09

GE*1*000000001

GE

FUNCTIONAL GROUP TRAILER (End)

GE011

Total Number of ST/SE pairs between GS and GEMN001/06

GE02000000001

Control Number (Must Match GS06)MN001/09


861 Receipt Advice Transaction Set Layout TC "861 Receipt Advise Transaction Set Layout" \f C \l "1"

Sample 861 Transaction Set Layout From FCSD To Supplier


GS*SH*AF52M*SCODE*060309*0108*000171386*X*002001\( Sender Code, Receiving Code, Version

ST*861*0001\

( Transaction Set Header

BRA*2006-03-09-06.06.21.8217340001*060309*00\

( Beginning of Receiving Advice

REF*PK*M8004550\

( Packing Slip Number

REF*SI*M8004550\

( Shipper's Identifying Number for Shipment (SID)

DTM*050*060308\

( Material Received on Date

N1*ST**92*AF1TA\

( Ship To Network Location Code

N1*SF**92*SCODE\

( Ship From Supplier GSDB Code

RCD**+3*PC\

( Receiving Conditions

SN1**+3*PC\

( Shipment Detail

LIN**BP*F75Z 1007 EB\

( Line Item Detail

CTT*1*3\

( Total Number of RCD Segments

SE*12*0001\


GE*1*000171386\

( Total Number of ST/SE pairs between GS & GE, Control Number


861 Receipt Advice Explanation and Attributes TC "861 Receipt Advise Explanation and Attributes" \f C \l "1"


GS*SH*AF52M*SCODE*060309*0108*000171386*X*002001

Attributes

GS


GS01SH

Functional Group Qualifier

MID02/02

GS02AF52M


MID02/12

GS03SCODE


GS04060309

Date (YYMMDD)

MDT06/06

GS050108


MTM04/04

GS06000171386


GS07X


GS08002001

ANSI X12 Version

MID01/12

ST*861*0001

ST


ST01861Transaction Set ID (Receiving Advice)MID03/03

ST020001


BRA*2006-03-09-06.06.21.8217340001*060309*00

BRA

BEGINNING SEGMENT (RECEIVING ADVICE)

BRA012006-03-09-06.

06.21.8217340001Transaction Set ID (Assigned by Ford)MAN01/30

BRA02060309Transaction Creation Date (YYMMDD)MDT06/06

BRA0300Original Transmission (Normal)

MID02/02

REF*PK*M8004550

REF

REFERENCE NUMBERS

REF01PKPacking List Number (Qualifier)

MID02/02

REF02M8004550Reference Number (BSN02 of the 856)CAN01/30

REF*SI*M8004550

REF

REFERENCE NUMBERS

REF01SIShipper's Identifying Number (Qualifier)MID02/02

REF02M8004550Reference Number (BSN02 of the 856)CAN01/30

DTM*050*060308

DTM

DATE/TIME REFERENCE

DTM01050Material Received on Date QualifierMID03/03

DTM02060308Date (YYMMDD)

CDT06/06

N1*ST**92*AF1TA

N1

NAME

N101STShip To (Entity Identifier Code)

MID02/02

N10392

Assigned by Buyer (Will Contain 92)C ID01/02

N104AF1TALocation Code

CAN02/17

N1*SF**92*SCODE

N1

NAME

N101SFShip From (Entity Identifier Code)

MID02/02

N10392

Assigned by Buyer (Will Contain 92)CID01/02

N104SCODESupplier GSDB Code

CAN02/17

RCD**+3*PC or RCD**+3*PC***+/-200*PC*13 (Example)

RCD

RECEIVING CONDITIONS

RCD02+3Quantity Received or Accepted (Actual Received Quantity)CR01/09

RCD03PC

Measurement Code (Same as 830)CID02/02

RCD04*

Quantity Units Returned (Not used in this example)CR01/09

(Used by Assembly Division to indicate return quantity)

RCD05*Measurement Code (Same as 830) (Not used in this example)CID02/02

RCD06+/-200Quantity in Question (Difference between SN102 and RCD02)CR01/09

RCD07PC


RCD0813

Receiving Condition Code

CID02/02

08 - Rejected 12 - Return Overshipment 13 - Quantity Discrepancy

RCD09

Quantity in Question (Will contain CUM adjustment Quantity) CR01/09

RCD10


RCD1111

Receiving Condition Code (11 - CUM Adjustment Quantity)CID02/02

· Ford will use the RCD09-RCD11 discrepancy set to show CUM adjustment Quantity only.

SN1**+3*PC

SN1

ITEM DETAIL

S102+3Number of Units Shipped (ASN Quantity)MR01/10

S103PCUnit of Measure

CID02/02

LIN**BP*F75Z 1007 EB

LIN

ITEM IDENTIFICATION DETAIL

LIN02BPBuyers Part Number (Qualifier)

MID02/02

LIN03F75Z 1007 EBFord Service Part Number

MAN01/30

CTT*1*3

CTT

TRANSACTION TOTALS

CTT011

Number of Line Items (Total Number of RCD Segments)MN001/06

CTT023

Hash Total (Sum of RCD02's)

MR01/10

SE*12*0001

SE


SE0112

Total Segment Count (Including ST/SE)MN001/06

SE020001

Control Number (Must Match ST02)MAN04/09

GE*1*000171386

GE


GE011


GE02000171386



856 Advance Shipment Notice (Intermediate Consignee/Packager) Transaction Set Layout TC "856 Advance Shipment Notice (Intermediate Consignee/Packager) Transaction Set Layout" \f C \l "1"

Sample 856 Transaction Set Layout From Supplier To FCSD For Shipment To An Intermediate Consignee (PKGR)


GS*SH*SCODE*AF52M*060204*1227*000006167*X*002002FORD\

( Sender Code, Receiver Code

ST*856*1001\

( Transaction Set Header, Control Number

BSN*00*920620*060204*1227\

( Purpose Code, ASN number, Date, Time

DTM*011*060204*1226\

( Date, Time

HL*1**S\

( Hierarchical Level (Shipment)

MEA*PD*G*97*LB\

( Measurements, Physical Dimensions (Gross Weight)

MEA*PD*N*56*LB\

( Measurements, Physical Dimensions (Net Weight)

TD1*CTN90*1\

( Number of containers (Pallets, Boxes, Cartons, etc…)

TD5*B*02*FDEG*LT\

( Carrier SCAC Code, Transportation Type

TD3*TL**4638156\

( Carrier details, equipment type, trailer number

REF*BM*DA12345\

( SLI # or carrier PRO # (REQUIRED at Shipment Level)

REF*CN*DA12345\ ( SLI # or Carrier PRO # (Required in either BM or CN, not both)

REF*PK*920620\

( Packing Slip (REQUIRED at Shipment or Item Level)

N1*ST**92*AF52M\

( Ship To Receiving Location (In Care Of The Intermediate Consignee)

N1*SF**92*SCODE\

( Ship From (Supplier GSDB Code)

N1*IC**92*PCODE\

( Intermediate Consignee (Packager GSDB Code)

CUR*SE*USD

( Used for International Shipments ONLY

ITA*C*AX*HC*06***1260


HL*2*1*I\

( Hierarchical Level (Item)

LIN**BP*F6DZ 5868175D90 C\

( Service Part Number

SN1**357*PC*5712\

( Shipment Quantity and Total CUM Shipped

PRF*SC 00656\

( Purchase order Reference

CLD*1*357*CTN90\

( Load Detail, Number of Containers, and Number of pieces

FOB*PP****FOB*OR


CTT*2*357\

( Transaction Totals

SE*23*1001\


GE*1*000006167\

( Group End, Number of ST/SE Segments, Control Number


· Due to occasional Intermediate Consignee/Packager Changes, Ford REQUIRES that you DO NOT HARD CODE the Intermediate Consignee/Packager Code in the N1*IC Segment.

· Your 856 ASN MUST Mirror your 830 Material Release.

856 ASN (Intermediate Consignee/Packager) Explanation and Attributes TC "856 ASN (Intermediate Consignee/Packager) Explanation and Attributes" \f C \l "1"


GS*SH*SCODE*AF52M*060204*1227*000006167*X*002002FORD

Attributes

GS


GS01SH

Functional Group

MID02/02

GS02SCODE

Ford Assigned Sender Code (Supplier GSDB Code)MID02/12

GS03AF52M

Ford Assigned Receiver Code

MID02/12

GS04060204

Date (YYMMDD)

MDT06/06

GS051227


MTM04/04

GS06000006167


GS07X


GS08002002FORD

ANSI X12 Version

MID01/12

ST*856*1001

ST


ST01856

Transaction Set ID (Ship Notice)

MID03/03

ST021001


BSN*00*920620*060204*1227

BSN

BEGINNING SEGMENT ADVANCE SHIP NOTICE

BSN0100

Transaction Set Purpose Code

MID02/02

00 - Original 05 - Replacement 01 - Cancellation

BSN02920620

ASN Number (Cannot be repeated within One-Year Period)MAN02/11

BSN03060204

Date (YYMMDD)

MDT06/06

BSN041227


MTM04/04

DTM*011*060204*1226

DTM

DATE/TIME REFERENCE

DTM01011

Shipped (Date & time Stock leaves the dock)MID03/03

DTM02060204

Date (YYMMDD)

MDT06/06

DTM031226


MTM04/04

HL*1**S

HL

HIERARCHICAL LEVEL

HL011

Hierarchical ID (Incremented by 1 in each subsequent HL)MAN01/06

HL03S

Hierarchical Level (Shipment)

MID01/02

MEA*PD*G*97*LB/

MEA

MEASUREMENTS

MEA01

PDPhysical Dimensions (Measurement Reference ID)MID02/02

MEA02

GGross Weight (Measurement Qualifier)MID01/03

MEA03

97Measurement Value (Value referred to by MEA02)MR01/10

MEA04LBUnit Of Measurement (LB - Pound KG - Kilogram)MID02/02

MEA*PD*N*56*LB

MEA

MEASURMENTS

MEA01

PDPhysical Dimensions (Measurement Reference ID)MID02/02

MEA02

NActual Net Weight (Measurement Qualifier)MID01/03

MEA03

97Measurement Value (Value referred to by MEA02)MR01/10


TD1*CTN90*1

TD1

CARRIER DETAILS (Quantity & Weight)

TD101

CTN90Packaging Code (Refer to Packaging Codes)MID05/05

TD102

1Lading Quantity/Number of Packages (Specified in TD101)MN001/07

· Most commonly used Packaging Codes can be found on Page 42.

TD5*B*02*FDEG*LT or TD5*B*02*FDE1*A***OR*BUF or TD5*B*02*CFXC*C***PP*PC07A

TD5

CARRIER DETAIL (Routing)

TD501

BRouting Sequence Code (Use 'B')M ID 01/02

TD502

02Identification Code Qualifier (Use '02')M ID 02/02

TD503

CFXCCarrier's SCAC Code

M ID 02/04

TD504

LT Transportation Method/Type Code (Refer to MOT)M ID 01/02

TD507

PP or ORLocation Qualifier

C ID 02/02

PP - Pool Point OR - Origin/Shipping Point (Air Only)

TD508

PC07A or BUFLocation Identifier (Identifies a Pool Point or Airport Code)C AN 01/05

· If Rail, Ocean, or Piggyback is used, in TD504 the use of TD302 is Mandatory; otherwise, not used.

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

· If PP (Pool Point) is used in TD507 - Use Ford Assigned code for Pool Point in TD508. TD507 AND TD508 are REQUIRED when shipping AIR or to a POOL POINT; otherwise not used.

TD3*TL**4638156 or TD3*RR*CSX*143607 (Example)

TD3

CARRIER DETAILS (Equipment)

TD301

TL (RR)Conveyance/Trailer # Qualifier (Refer to MOT)MID02/02

TD302

(CSX)Equipment Initial/Owners Code/Container CodeCAN01/04

TD3034638156 (143607)Equipment Number/Container NumberMAN01/07

· If TD504 Indicates Rail, Piggyback, or Ocean shipment - The use of TD302 is REQUIRED; otherwise not used. 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 42.

REF*BM*DA12345

REF

REFERENCE NUMBERS

REF01

BMQualifier for "Bill of Material/Lading" (Refer to REF Qualifiers)MID02/02

REF02

DA12345SLI Number or Carrier PRO Number (required)MAN01/30

· The use of at least one REF Segment with a qualifier of "BM" or "AW" is required at the SHIPMENT LEVEL.

· You are required to enter the SLI # or Carrier PRO # the REF*BM OR the REF*CN of the ASN. The SLI # MUST BE:

· Left Justified

· NO Leading Spaces or Zeros

· String no other data

· No more than 7 Characters in length (SLI# consists of 2 Alpha & 5 Numeric)

REF*CN*DA12345 (Only required if SLI # is NOT placed in the REF*BM)

REF

REFERENCE NUMBERS

REF01

CNQualifier for "Carton Number" (Refer to REF Qualifiers)MID02/02

REF02



· Left Justified




REF*PK*920620

REF

REFERENCE NUMBERS

REF01

PKQualifier for "Packing List" (Refer to REF Qualifiers)MD02/02

REF02

920620Reference Number

MAN01/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.

· Ford will accept up to 16 characters for Air and Freight Bill numbers; 17 characters for Dealer Direct data, and up to 12 characters for Vessel name. For all other entries in REF02, Ford will accept up to 11 characters.

· Most commonly used REF Qualifiers can be found on page 42.

N1*ST**92*AF52M

N1

NAME


MID02/02

N10392

Assigned by Buyer (Will Contain 92)MID01/02

N104AF52MShip To Receiving Location (Must match N1*ST of the 830)MID05/05

N1*SF**92*SCODE

N1

NAME


MID02/02

N10392


N104SCODEShip From Location (Supplier GSDB Code)MID05/05

N1*IC**92*PCODE

N1

NAME

N101ICIntermediate Consignee/PackagerMID02/02

N10392


N104PCODEIntermediate Consignee/Packager Code (From N1*IC of 830)MID05/05

· Due to occasional Intermediate Consignee/Packager Changes, Ford REQUIRES that you DO NOT HARD CODE the Intermediate Consignee/Packager Code in the N1*IC Segment.

CUR*SE*USD(INTERNATIONAL SHIPMENTS ONLY to specify the currency used in the transaction.)

CUR

CURRENCY

CUR01SESelling Party (Identifying physical location) MID02/02

CUR02USDCurrency Code

MID03/03

ITA*C*AX*HC*06***1260 (INTERNATIONAL SHIPMENTS ONLY to specify allowances, charges, or services.)

ITA

ALLOWANCE, CHARGE, OR SERVICE

ITA01CAllowance or Charge Indicator (C - Charge)MID01/01

ITA02AXAgency Qualifier Code (AX - ANSI X12)OID02/02

ITA03HCSpecial Services Code (HC - Handling Service)CID02/10

ITA0406Method of Handling (06 - Charge to be Paid by Customer)MID02/02

ITA071260Total dollar amount for the allowance or chargeCN201/09

HL*2*1*I

HL

HIERARCHICAL LEVEL

HL012


HL021

Hierarchical Parent ID (Required at Item Level)OAN01/06

HL03I

Hierarchical Level (Item)

MID01/02

LIN**BP*F6DZ 5868175D90 C

LIN

LINE ITEM DETAIL

LIN02BP

Product/Service ID Qualifier

MID02/02

BP - Buyers Part RC - Returnable Container

LIN03F6DZ 5868175D90 CFord Service Part Number (Prefix, Base, Suffix)MAN01/30

SN1**357*PC*5712

SN1

ITEM DETAIL SHIPMENT

SN102357

Quantity in this Shipment

R01/07

SN103PC

Unit Of Measure (From 830)

MID02/02

SN1045712

Quantity Shipped to Date (Total CUM including this ASN)CR01/09

· Enter the total CUM Quantity shipped since CUM rollback including this ASN in SN104. Not used for returnable containers.

PRF*SC 00656

PRF

PURCHASE ORDER REFERENCE

PRF01SC 00656

Ford Purchase Order Number (LIN05 of the 830)MAN01/10

CLD*1*357*CTN90

CLD

CUSTOMER'S LOAD DETAIL

CLD011Number of Containers (Skids, Pallets, boxes, etc.)MNO01/05

CLD02357Quantity Per Container

MR01/07

CLD03CTN90Packaging Code/Container Type (Refer to Packaging Codes)MID05/05


FOB*PP****FOB*OR (INTERNATIONAL SHIPMENTS ONLY for customs purposes.)

FOB

F.O.B. RELATED INSTRUCTIONS

FOB01CC or PPPayment terms for transportation charges (Collect or Prepaid)MID02/02

FOB05FOBTransportation Terms Code (Any ANSI Defined Code)MID03/06

FOB06DE or OR Location Qualifier (DE - Destination OR - Origin ) MID01/02

CTT*2*357

CTT

TRANSACTION TOTALS

CTT012Total Number of HL Segments

MN001/06

CTT02357Hash Total (Total of Quantities from SN102's)MR01/10

SE*23*1001

SE


SE0123Total Segment Count (Including ST/SE)MN001/06

SE021001Transaction Set Control Number (Must Match ST02)MAN04/09

GE*1*000006167

GE


GE011


GE02000006167



856 ASN (Network Location/PDC/PRC) Transaction Set Layout TC "856 ASN (Network Location/PDC/PRC) Transaction Set Layout" \f C \l "1"

Sample 856 Transaction Set Layout From Supplier To FCSD For Shipment To A Network Location (PDC/PRC)


GS*SH*SCODE*AF52M*060204*1227*000006167*X*002002FORD\( Sender Code, Receiving Code

ST*856*1001\


BSN*00*920620*060204*1227\


DTM*011*060204*1226\

( Date, Time

HL*1**S\


MEA*PD*G*97*LB\


MEA*PD*N*56*LB\


TD1*CTN90*1\


TD5*B*02*CWCE*LT\

( Carrier details, transportation type

TD3*TL**4638156\


REF*BM*DA12345\



REF*PK*920620\


N1*ST**92*AF30A\

( Ship To Receiving Location (FCSD Network Location)

N1*SF**92*SCODE\


CUR*SE*USD


ITA*C*AX*HC*06***1260


HL*2*1*I\


LIN**BP*F6DZ 5868175D90 C\


SN1**357*PC*5712\


PRF*SC 00656\


CLD*1*357*CTN90\


FOB*PP****FOB*OR


CTT*2*357\


SE*21*1001\


GE*1*000006167\



· Your 856 ASN MUST Mirror your 830 Material Release.

856 ASN (Network Location/PDC/PRC) Explanation and Attributes TC "856 ASN (Network Location/PDC/PRC) Explanation and Attributes" \f C \l "1"



Attributes

GS


GS01SHFunctional Group

MID02/02

GS02SCODEFord Assigned Sender Code (Supplier GSDB Code)MID02/12

GS03AF52MFord Assigned Receiver Code

MID02/12

GS04060204Date (YYMMDD)

MDT06/06

GS051227Time (HHMM, 24 Hour Clock)

MTM04/04

GS06000006167 Control Number (Must Match GE02)MN001/09

GS07XResponsible Agency Code (Use "X")MAN01/02

GS08002002FORDANSI X12 Version

MID01/12

ST*856*1001

ST


ST01856Transaction Set ID (Ship Notice)

MID03/03

ST021001Control Number (Must Match SE02)MAN04/09

BSN*00*920620*060204*1227

BSN

BEGINNING SEGEMTN ADVANCE SHIP NOTICE

BSN0100Transaction Set Purpose Code

MID02/02

00 - Original 05 - Replacement 01 - Cancellation

BSN02920620ASN Number (Cannot be repeated within One-Year Period)MAN02/11

BSN03060204Date (YYMMDD)

MDT06/06

BSN041227Time (HHMM, 24 Hour Clock)

MTM04/04

DTM*011*060204*1226

DTM

DATE/TIME REFERENCE

DTM01011Shipped (Date & Time Stock leaves the Dock)MID03/03

DTM02060204Date (YYMMDD)

MDT06/06

DTM031226Time (HHMM, 24 Hour Clock)

MTM04/04

HL*1**S

HL

HIERACHICAL LEVEL

HL011Hierarchical ID (Incremented by 1 in each subsequent HL)MN001/06

HL03SHierarchical Level (Shipment)

MID01/02

MEA*PD*G*97*LB/

MEA

MEASUREMENTS

MEA01PDPhysical Dimensions (Measurement Reference ID)MID02/02

MEA02GGross Weight (Measurement Qualifier)MID01/03

MEA0397Measurement Value (Value referred to by MEA02)MR01/10


MEA*PD*N*56*LB

MEA

MEASUREMENTS


MEA02NActual Net Weight (Measurement Qualifier)MID01/03



TD1*CTN90*1

TD1


TD101CTN90Packaging Code (Refer to Packaging Codes)MID05/05

TD1021Lading Quantity/Number of Packages (Specified in TD101)MN001/07


TD5*B*02*FDEG*LT or TD5*B*02*FDE1*A***OR*BUF or TD5*B*02*CFXC*C***PP*PC07A

TD5


TD501


TD502


TD503

CFXCCarrier's SCAC Code

M ID 02/04

TD504

LT Transportation Method/Type Code (Refer to MOT) M ID 01/02

TD507


C ID 02/02


TD508


· If Rail, Ocean, or Piggyback is used, in TD504 the use of TD302 is Mandatory.

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

· If PP (Pool Point) is used in TD507 - Use Ford Assigned code for Pool Point in TD508. TD507 AND TD508 are REQUIRED when shipping AIR or to a POOL POINT; otherwise not used.


TD3


TD301


TD302

(CSX)Equipment Initial/Owners Code/Container CodeCAN01/04

TD3034638156 (143607)Equipment Number/Container NumberMAN01/07



REF*BM*DA12345

REF

REFERENCE NUMBERS

REF01


REF02




· Left Justified





REF

REFERENCE NUMBERS

REF01


REF02



· Left Justified




REF*PK*920620

REF

REFERENCE NUMBERS

REF01


REF02


MAN01/30




N1*ST**92*AF30A

N1

NAME


MID02/02

N10392Assigned by Buyer (Will Contain 92)MID01/02

N104AF30AShip To Receiving Location (Must match N1*ST of the 830)MID05/05

N1*SF**92*SCODE

N1

NAME


MID02/02

N10392Assigned by Buyer (Will Contain 92)MID01/02


CUR*SE*USD(INTERNATIONAL SHIPMENTS ONLY to specify the currency used in the transaction.)

CUR

CURRENCY

CUR01SESelling Party (Identifying physical location) MID02/02

CUR02USDCurrency Code

MID03/03

ITA*C*AX*HC*06***1260 (INTERNATIONAL SHIPMENTS ONLY to specify allowances, charges, or services.)

ITA

ALLOWANCE, CHARGE, OR SERVICE

ITA01CAllowance or Charge Indicator (C - Charge)MID01/01

ITA02AXAgency Qualifier Code (AX - ANSI X12)OID02/02

ITA03HCSpecial Services Code (HC - Handling Service)CID02/10

ITA0406Method of Handling (06 - Charge to be Paid by Customer)MID02/02

ITA071260Total dollar amount for the allowance or chargeCN201/09

HL*2*1*I

HL

HIERARCHICAL LEVEL

HL012


HL021


HL03I


MID01/02


LIN

LINE ITEM DETAIL

LIN02BP

Product/Service ID Qualifier (RC - Returnable Container No.)MID02/02

LIN03F6DZ 5868175D90 CFord Part Number (In form of Prefix, Base, Suffix)MAN01/30

SN1**357*PC*5712

SN1


SN102357

Number of Units Shipped

MR01/07

SN103PC

Measurement Code (From the 830)MID02/02

SN1045712

Quantity Shipped to Date (Total CUM including this ASN)CR01/09

· Enter the total CUM Quantity shipped since CUM rollback including this ASN in SN104. Not used for returnable containers.

PRF*SC 00656

PRF


PRF01SC 00656

Ford Purchase Order Number (LIN05 of the 830)MAN01/10

CLD*1*357*CTN90

CLD


CLD011Number of Containers (Skids, Pallets, etc.)MNO01/05

CLD02357Number of Units Per Container

MR01/07

CLD03CTN90Packaging Code (Refer to Packaging Codes)MID05/05


FOB*PP****FOB*OR(INTERNATIONAL SHIPMENTS ONLY for customs purposes.)

FOB

F.O.B. RELATED INSTRUCTIONS

FOB01CC or PPPayment terms for transportation charges (Collect or Prepaid)MID02/02

FOB05FOBTransportation Terms Code (Any ANSI Defined Code)MID03/06

FOB06ORLocation Qualifier (DE - Destination OR - Origin )MID01/02

CTT*2*357

CTT

TRANSACTION TOTALS


MN001/06

CTT02357Hash Total (Total Quantities from SN102's)MR01/10

SE*23*1001

SE




GE*1*000006167

GE


GE011


GE02000006167 Control Number (Must Match GS06)MN001/09


856 ASN (Dealer Direct Emergency Order) Transaction Set Layout TC "856 ASN (Dealer Direct Emergency Order) Transaction Set Layout" \f C \l "1"

Sample 856 Transaction Set Layout From Supplier To FCSD For Dealer Direct Emergency Order Shipments


GS*SH*SCODE*AF52M*060204*1227*000006167*X*002002FORD\ ( Sender Code, Receiving Code

ST*856*1001\


BSN*00*920620*060204*1227\


DTM*011*060204*1226\

( Date, Time

HL*1**S\


MEA*PD*G*7*LB\


MEA*PD*N*6*LB\


TD1*CTN90*1\


TD5*B*02*UPSS*M\

( Carrier details, transportation type

TD3*TL*UPSS*977141\


REF*BM*DA12345\



REF*PK*316894\


N1*ST**92*AF52M\

( Ship To Receiving Location (Mirror N1*ST from 830)

N1*SF**92*SCODE\


HL*2*1*I\


LIN**BP*F6DZ 5868175D90 C\


SN1**1*PC*5712\


PRF*SC 00656\


REF*CO*DLR04812DOR17291

( Dealer Code and DOR (Dealer Order Number) (REQUIRED)

CLD*1*1*CTN90\


CTT*2*1\


SE*22*1001\


GE*1*000006167\



856 ASN (Dealer Direct Emergency Order) Explanation and Attributes TC "856 ASN (Dealer Direct Emergency Order) Explanation and Attributes" \f C \l "1"



Attributes

GS


GS01SH

Functional Group

MID02/02

GS02SCODE

Ford Assigned Sender Code (Supplier GSDB Code)MID02/12

GS03AF52M

Ford Assigned Receiver Code

MID02/12

GS04060204

Date (YYMMDD)

MDT06/06

GS051227


MTM04/04

GS06000006167


GS07X


GS08002002FORD

ANSI X12 Version

MID01/12

· GS03 will be AF52M for Material Suppliers. Total Suppliers can use AF52M or their releasing location (i.e. AF31A, AF1JA, AF30A, etc…)

ST*856*1001

ST


ST01856

Transaction Set ID (Ship Notice)

MID03/03

ST021001


BSN*00*920620*060204*1227

BSN

BEGINNING SEGMENT ADVANCE SHIP NOTICE

BSN0100

Transaction Set Purpose Code

MID02/02

00 - Original 01 - Cancellation

BSN02920620

ASN Number (Cannot be repeated within One-Year Period)MAN02/11

BSN03060204

Date (YYMMDD)

MDT06/06

BSN041227


MTM04/04

· DO NOT send an ' 05 ' purpose code for a Replacement ASN for Dealer Direct orders. Cancel the ASN with a ' 01 ' and resend as a Original ' 00 '.

DTM*011*060204*1226

DTM

DATE/TIME REFERENCE

DTM01011

Shipped (Date & Time Stock leaves the dock)MID03/03

DTM02060204

Date (YYMMDD)

MDT06/06

DTM031226


MTM04/04

HL*1**S

HL

HIERARCHICAL LEVEL

HL011


HL03S

Hierarchical Level (Shipment)

MID01/02

MEA*PD*N*6*LB

MEA

MEASUREMENTS


MEA02NActual Net Weight (Measurement Qualifier)MID01/03



TD1*CTN90*1

TD1


TD101CTN90Packaging Code (Refer to Packaging Codes)MID05/05

TD1021Lading Quantity/Number of Packages (Specified in TD101)MN001/07


TD5*B*02*FDEG*LT or TD5*B*02*FDE1*A***OR*BUF or TD5*B*02*FDEG*C***PP*PC07A

TD5


TD501


TD502


TD503

FDEGCarrier's SCAC Code

M ID 02/04

TD504

LT Transportation Method/Type Code (Refer to MOT) M ID 01/02

TD507


C ID 02/02


TD508


· If Rail, Ocean, or Piggyback is used in TD504 the use of TD302 is MANDATORY.

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

· If PP (Pool Point) is used in TD507 - Use Ford Assigned code for Pool Point in TD508. TD507 and TD508 are REQUIRED when shipping AIR or to a POOL POINT; otherwise not used.


TD3


TD301


TD302

(CSX)Equipment Initial/Owners Code

CAN01/04

TD3034638156 (143607)Equipment Number

MAN01/07



REF*BM*DA12345

REF

REFERENCE NUMBERS

REF01


REF02




· Left Justified





REF

REFERENCE NUMBERS

REF01


REF02



· Left Justified




REF*PK*920620

REF

REFERENCE NUMBERS

REF01


REF02


MAN01/30




N1*ST**92*AF52M

N1

NAME


MID02/02

N10392


N104AF52MShip To Receiving Location (Mirror 830 ST)MID05/05

· N1*ST will be AF52M for Material Suppliers (N1*IC will be blank). Total Suppliers will use their releasing location (i.e. AF31A, AF1JA, AF30A, etc…) that is normally sent in the N1*ST of their 830.

N1*SF**92*SCODE

N1

NAME


MID02/02

N10392



HL*2*1*I

HL

HIERACHICAL LEVEL

HL012


HL021


HL03I


MID01/02


LIN

LINE ITEM DETAIL

LIN02BP

Product/Service ID Qualifier

MID02/02

LIN03F6DZ 5868175D90 CFord Part Number (In form of Prefix, Base, Suffix)MAN01/30

SN1**1*PC*5712

SN1


SN1021

Number of Units Shipped

MR01/07

SN103PC

Measurement Code (From the 830)MID02/02

SN1045712

Quantity Shipped to Date

CR01/09

· Enter the total CUM Quantity shipped since CUM rollback including this ASN in SN104. Not used for returnable containers

PRF*SC 00656

PRF


PRF01SC 00656Purchase Order Number

MAN01/10

REF*CO*DLR04812DOR17291

REF

REFERENCE NUMBERS

REF01COQualifier for "Customer Order Number"MID02/02

REF02DLR04812DOR17291Text "DLR" followed by the customer/dealer codeMAN01/17

(Dealer Code & DOR # can be found on the ROLA or TGLA Screen in DDL)

Text "DOR" followed by the Dealer Order Number

· The use of the REF*CO Segment is MANDATORY for Dealer Direct Emergency Orders.

CLD*1*1*CTN90

CLD


CLD011Number of Containers (Skids, Pallets, etc.)MN001/05

CLD021Number of Units Per Container

MR01/07

CLD03CTN90Packaging Code (Refer to Packaging Codes)MID05/05


CTT*2*1

CTT

TRANSACTION TOTALS


MN001/06

CTT021Hash Total (Total of Quantities from SN102's)MR01/10

SE*22*1001

SE




GE*1*000006167

GE


GE011

Total Number of ST/SE pairs between GS and GEM N0 01/06

GE02000006167

Control Number (Must Match GS06)M N0 01/09


997 Functional Acknowledgement Transaction Set Layout- ACCEPTED TC "997 Functional Acknowledgement Transaction Set Layout- ACCEPTED" \f C \l "1"


GS*FA*AF52M*SCODE*060204*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*4\

( Acknowledge of Acceptance

AK9*A*1*1*1\

( Accepted, # of included transactions sets, received sets, accepted sets

SE*6*0001\


GE*1*000000876\



997 Functional Acknowledgement Explanation and Attributes - ACCEPTED

TC "997 Functional Acknowledgement Explanation and Attributes - ACCEPTED" \f C \l "1"


GS*FA*AF52M*SCODE*060204*0835*000000876*X*002002

Attributes

GS


GS01FA

Functional Acknowledgement

MID02/02

GS02AF52M


MID02/12

GS03SCODE


GS04060204

Date (YYMMDD)

MDT06/06

GS051227


MTM04/04

GS06000000876


GS07X


GS08002002

ANSI X12 Version

MID01/12

ST*997*1001

ST


ST01

997

Transaction Set ID

MID03/03


AK1*SH*000006167

AK1

FUNCTIONAL GROUP RESPONSE HEADER

AK101SHValue in GS01 of transaction being acknowledgedMID02/02

AK102000006167Control number (GS06 of the message being acknowledged)MN001/09

AK2*856*0983

AK2

TRANSACTION SET RESPONSE HEADER

AK201856Type of transaction being acknowledged (ST01)MID03/03

AK2020983Value in (ST02) of the transaction being acknowledgedMAN04/09

AK5*A

AK5

TRANSACTION SET RESPONSE TRAILER

AK501A

Transaction Set is Accepted (Refer to Chart 3 on page 38)M ID 01/01

AK9*A*1*1*1

AK9

FUNCTIONAL GROUP RESPONSE TRAILER

AK901A

Transaction Set is Accepted (Refer to Chart 5 on page 39) MID01/01

AK9021

Number of transaction sets includedMN001/06

AK9031

Number of Received Transaction SetsMN001/06

AK9041

Number of Accepted Transaction SetsMN001/06

SE*6*0001

SE




GE*1*000000876

GE

FUNCTIONAL GROUP TRALIER (End)

GE011




997 Functional Acknowledgement Transaction Set Layout- REJECTED TC "997 Functional Acknowledgement Transaction Set Layout- REJECTED" \f C \l "1"


GS*FA*AF52M*SCODE*060204*0835*000030876*X*002002\ ( Group Start, Sender Code, Receiving Code

ST*997*001\


AK1*SH*2616\

( Functional Group Response Header

AK2*856*0983\

( Transaction being acknowledged

AK3*TD1*7**5\

( 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\


GE*1*000030876\



997 Functional Acknowledgement Explanation and Attributes - REJECTED TC "997 Functional Acknowledgement Explanation and Attributes - REJECTED" \f C \l "1"


GS*FA*AF52M*SCODE*060204*0835*000030876*X*002002

Attributes

GS


GS01FA

Functional Acknowledgement

MID02/02

GS02AF52M


MID02/12

GS03SCODE


GS04060204

Date (YYMMDD)

MDT06/06

GS051227


MTM04/04

GS06000030876


GS07X


GS08002002ANSI X12 Version

MID01/12

ST*997*1001

ST


ST01

997

Transaction Set ID

MID03/03


AK1*SH*2616

AK1

FUNCTIONAL GROUP RESPONSE HEADER

AK101SHValue in GS01 of transaction being acknowledgedMID02/02

AK1022616Control number (GS06 of the message being acknowledged)MN001/09

AK2*856*0983

AK2

TRANSACTION SET RESPONSE HEADER

AK201856Type of transaction being acknowledged (ST01)MID03/03

AK2020983

Value in (ST02) of the transaction being acknowledgedMAN04/09

AK3*TD1*7**5

AK3

DATA SEGMENT NOTE

AK301TD1Segment in Error

M ID 02/03

AK3027Segment position in transaction set has errorMN001/06

AK3045Segment Note Code (Refer to Chart 1 on page 38)OID01/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

AK4012Element Number in Error (Segment AK301)MN001/02

AK4031Code Indicating the Error found (Refer to Chart 2 on page 38) MID01/03

AK404XXXXCopy of Bad Data Element

OAN01/99

AK5*R*5

AK5

TRANSACTION SET RESPONSE TRAILER

AK501RTransaction Set is Rejected (Refer to Chart 3 on page 38)M ID 01/01

AK5025Code indicating the error found (Refer to Chart 4 on page 38)O ID 01/03

AK9*R*1*1*0

AK9

FUNCTIONAL GROUP RESPONSE TRAILER

AK901RTransaction Set is Rejected (Refer to Chart 5 on page 39)MID01/01

AK9021Number of transaction Sets IncludedMN001/06

AK9031Number of Received Transaction SetsMN001/06

AK9040Number of Accepted Transaction SetsMN001/06

AK9055Functional Group Note Code (Refer to Chart 6 on page 39)OID01/03

SE*6*0001

SE




GE*1*000030876

GE


GE011




997 Functional Acknowledgement Error Definitions TC "997 Functional Acknowledgement Error Definitions" \f C \l "1"

CHART 1: Click to return to: (AK304 Rejected)

CodeDefinition

1Unrecognized segment ID

2Unexpected segment

3Mandatory segment missing

4Loop occurs over maximum times

5Segment within loop exceeds maximum use


CodeDefinition

1Mandatory data element missing.

2Conditional required data element missing.

3Too many data elements.

4Data element too short.

5Data element too long.

6Invalid character in data element.

7Invalid code value.

8Invalid date.

9Invalid time.

CHART 3: Click to return to: (AK501 Accepted) (AK501 Rejected)

CodeDefinition

AThe transmitted transaction set is Accepted.

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


Code

Definition

1

This transaction set type is not supported.

2

The transaction set trailer is missing.

3The 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: Click to return to: (AK901 Accepted) (AK901 Rejected)

Code

Definition

AThe transmitted functional group is Accepted. An acceptance of a functional group is an acceptance of all transaction sets in that functional group.

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

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


Code

Definition

1This functional group type is not supported.

2This version of the functional group is not supported.

3The functional group trailer is missing.

4The data interchange control number in the header and trailer do not match. The value from the header is used in the acknowledgement.

5The number of included sets does not match the actual count.

TA1 Errors TC "TA1 Errors" \f C \l "1"

Supplier will receive a TA1 Error if there are errors in the Envelope Structure (ISA/IEA) of transactions sent to Ford

TA1*265162219*060204*1527*R*021

Attributes

TA1

INTERCHANGE ACKNOWLEDGMENT

TA101265162219Interchange Control Number

MN009/09

(ISA13 of the group being acknowledged)

TA102060204Interchange Date (YYMMDD)

MDT06/06

TA1031527Interchange Time (HHMM)

MTM04/04

TA104RInterchange Acknowledgement CodeMID01/01

A - Accepted E - Accepted With Errors R - Rejected

TA10521Interchange Note Code (Refer to Chart 7 On page 41) MID03/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.

TA1 Error Note Code Definitions TC "TA1 Error Note Code Definitions" \f C \l "1"

CHART 7: Click to return to: (TA105)

CodeDefinition

000No Error.

001The 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.

003This Version of the Controls is not Supported.

004The Segment Terminator is Invalid.

005Bad Interchange ID Qualifier for sender.

006Bad Interchange Sender ID.

007Bad Interchange ID Qualifier for Receiver.

008Bad Interchange Receiver ID.

009Network provider could not deliver message because of unknown Receiver ID as qualified.

010Bad Authorization Information Qualifier Value.

011Bad Authorization Information Value.

012Bad Security Information Qualifier Value.

013Bad Security Information Value.

014Bad Interchange Date Value.

015Bad Interchange Time Value.

016Bad Interchange Standards Identifier Value.

017Bad Interchange Version ID Value.

018Bad Interchange Control Number Value.

019Invalid Acknowledgement Requested Value – Must be "0" (Zero).

020Bad Test Indicator Value – Must be "P".

021Bad Number of Included Groups Value.

022Invalid Control Structure.

023Improper (premature) end-of-file (transmission).

024Invalid Interchange Content (e.g. bad GS Segment).

025Duplicate Interchange Control Number.

026Invalid 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.

Mode of Transportation (MOT), Packaging Codes, & REF Qualifiers TC "Mode of Transportation (MOT), Packaging Codes, & REF Qualifiers" \f C \l "1"

Most Commonly Used MOT Codes Click to return to: (Page 19) (Page 25) (Page 30)

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

TL

Truck Load

U

Private Parcel Service

W

Inland Waterway

ZZ

On hand at pool

Most Commonly Used Packaging Codes Click to return to: (Page 19) (Page 21) (Page 25) (Page 27) (Page 30)

(Page 32)

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 Click to return to: (Page 20) (Page 26) (Page 31)

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

Glossary of Acronyms TC "Glossary of Acronyms" \f C \l "1"

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 GEC Hub to process their EDI transactions.

GEC Hub (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

DSO:

Domestic Special order

DOR/COR:

Dealer/Customer Order Number

PDC/PRC:

Parts Distribution Center/Parts Redistribution Center

IC (Intermediate Consignee):

Ford Contract Packager

SPOC (Single Point Of Contact):

Support Services/Helpdesk

DDL (Direct Data Link):

Communication link between supplier and FCSD

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

Glossary of Attributes TC "Glossary of Attributes" \f C \l "1"

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.

EDI Manual Revisions TC "EDI Manual Revisions" \f C \l "1"

Date

Section

Page(s)

09/28/2006

TD507/TD508 When Shipping Air Added

19, 24, 29

10/06/2006

Note About NOT Hard Coding N1*IC

3, 17, 20

02/06/2007

New Ford Approved VANS Added

5

11/14/2007

AK304 Explanation and Chart Added for 997 Reject

35

11/21/2007

Entire Manual Reformatted

1 - 43

12/05/2007

Minor Formatting Adjustments

1 - 43

12/10/2007

EDI Coordinator Email Added

3

02/20/2008

Added DDL to Acronyms

41

01/20/2010

Removed use of the REF*CN for SLI # & replaced with the use of the REF*BM for SLI #

17, 20, 22, 25, 27, 29

02/01/2010

Network Locations ANSI X12 Required EDI Transactions added to TOC

2

06/29/2010

Updated the

Documents

brownartcorp.combrownartcorp.com/gsdb3/Suppliersys/attachments/NLEM.… · Web viewRCD06 +/-200 Quantity in Question (Difference between SN102 and RCD02) C R 01/09. RCD07 PC Measurement