caterpillar: confidential green 856 ship notice/manifest

Caterpillar: Confidential Green

CAT8563020-20190531 (003020) 1 May 31, 2019 Caterpillar: Confidential Green

856 Ship Notice/Manifest

Functional Group ID=SH

Introduction:

This standard provides the standardized format and establishes the data contents of a ship notice/manifest transaction set. A ship notice/manifest lists the contents of a shipment of goods as well as additional information relating to the

shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the

sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information. The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The

receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.

Notes:

IMPORTANT NOTE: CATERPILLAR REQUIRES ALL SUPPLIERS TO USE BAR CODED SHIPPING

LABELS, PER CATERPILLAR STANDARD PRACTICE SP20 DOCUMENT, ON ALL MATERIAL SHIPPED

TO CATERPILLAR. ALL SUPPLIERS MUST PASS THE PKG ID NUMBER OF THE HIGHEST LEVEL

SHIPPING LABEL (HANDLING UNIT) USING THE REF*LS SEGMENT OF THE 856 ASN. (SEE

EXAMPLES BELOW)

GUIDELINE CHANGE CONTROL:

2019/05/31: Modified Guideline to explain qualifiers and elements required for

Exports and Imports. (DICE)

2019/05/23: Modified Guideline to explain how to send ASN's with Serialized Parts,

so that the Part Serial Number (REF*SE) corresponds to the appropriate Bar Code

Label (REF*LS) segment. (Inc.0922453)

2016/06/14: Made the following changes to support sending ASN's for Configurable

Product Order Process to support project AirDrop.

- Added qualifier "PO" to REF segment at Shipment HL level, to report Top Level

PO number for Configurable Product Process orders. (Project AirDrop)

- Added PID03 and PID04 elements to PID segment to report Componant Part Number

for Configurable Product Process orders. (Project AirDrop).

- Added qualifier "AN" to REF segment at Item HL Level, to report componant PO

number for Configurable Product Process orders. (Project AirDrop).

2015/08/14:

- Modified N101 at the Detail level to maike N101 Qualifier "MA" required by

Caterpillar. (Global Network Operations)

- Add qualifier 'IV' to REF01 at the Shipment Level and Modified Implementation

Note to describe passing the "Commercial Invoice Number" in REF02. (Global Network

Operations)

- Open up REF03 in the REF segment ad the Shipment Level to allow passing of the

"Total Value of the Commerical Invoice. (Global Network Operations)

2015/04/16:

- Clarified implementation notes on CTT01 element on the CTT segment. (ICC)

2014/11/04:

- Added verbiage to implementation notes on the REF*LS to clarify and align with

Package ID Number length limitations on the Standard Practice 20 label. (ICC, DART)

2014/08/18:



- Added Qualifier *PK","HC" and "LT" to REF01 at the Shipment HL level to correspond

with Implementation Note Verbiage explaining when to send a Reference Number at

the Shipment vs Item HL level. (ICC, AP-SS)

- Added Qualifier "CN" to REF01 at the Item HL Level to correspond with

Implementation Note Verbiage explaining when to send a Reference Number at the

Shipment vs Item HL Level. (ICC, AP-SS)

2014/04/01:

- Added Qualifier 'MA' to the N101 segment at the Shipment Level to indicate

ultimate destination when 856 is sent to Consolidator. (Mach1)

2013/12/02:

- Added qualifier 'IL' to REF segement at the detail level per Mach1. This was

included in Mach1 in 2011, but this change never got published. This change will

make the Guideline coincide with Translation Map.

2013/02/20:

- Corrected SN1 and CLD counts in example 3 and 6, and added missing CLD segment

in example 6.

2013/02/18:

- Reworked the diagrams in example 3 and 5, as well as Label Sample Diagram and

the Segment Data examples to add clarity and match verbiage to the SP20

documentation. (GP)

2013/01/22:

- Added 'CS' qualifier to N101 and clarify note verbiage on N103 and N104 for

'Consolidator' information. (M1-OTD)

- Clarified verbiage on REF segment to match SP20 Bar Code Label documentation:

Package ID Number = Pkg ID # = Bar Code Serial Number. (GP)

2012/11/13:

- Added PD and PW Qualifiers to LIN02.

- Added TN qualifier to REF01segment in the Shipment Level HL loop. (CGMM)

SAMPLE TRANSACTIONS:

ISA*00* *00* *ZZ*X0000X0 *09*005070479ff *

081001*1204*U*00200*890751204*0*P*\@

GS*SH*X0000X0*ff*081001*1123*852751201*X*003020@

ST*856*0001@

BSN*00*SHIP IDENT NO*081001*1023@

NTE*ZZZ*ANY NOTES PERTINENT TO THE SHIPMENT@ (SHIPMENT LEVEL)

NTE*ZZZ*ANY NOTES PERTINENT TO THE PACKING LIST ITEMS@ (ITEM LEVEL)

DTM*011*081001*1201@

DTM*017*081003*1155@

HL*1**S@

MEA*PD*G*1250*LB@

TD1*PLT71*1@

TD5*B*92*9800*P @

TD5*B*2*CETR*T @

TD3*CN*VEH#*1234567@

REF*CN*PRO/NUMBER00001@

REF*TN*SHIPMENT AUTHORIZATION NUMBER@

REF*IV*COMMERCIAL INVOICE NUMBER@

FOB*CC@

N1*SF**16*61604@

N1*SF**92*X0000X0@

N1*SF**91*120010@

N1*SU**91*BE@

N1*MA**92*FF00@



HL*2*1*I@

LIN*1*BP*1A-0001*EC*0001@

SN1**1000*PC@

SLN*1**A*955*PC*97.22@

SLN*1**A*100*PC*25@

PRF*DAN 51245*001***01@

PID*F****DRILL 6;00MM 502 W/HP TANG@

MEA*PD*N*1250*LB@

REF*PK*ABC123@

CLD*1*300*PLT71*5.0*PC@

REF*LS*123456@

CUR*SE*DEM@

ITA*C**C0090*06**59.7****77*PC**CUTTING CHG@

CTT*2*1100@

SE*36*0001@

GE*1*852751201@

IEA*1*128528701@

EXAMPLE NO. 1

The first example is a shipment which is from a U.S. supplier and contains three

different item numbers. All three items are being shipped on a common packing

list. One shipment authorization number applies to the entire shipment. Carrier

information is also being passed by the supplier. The packing list number is

repeated for each item in the shipment even though it does not change. The packing

list number could have been passed at the SHIPMENT level. There are 3 Handling

Units in this example.

SHIP IDENT NO (shipment)

|

|

|

|

+-----------------------+---------------------+

| | |

| | |

| | |

1A-0001 (item) 2B-0002 3C-0003

(PKG ID #01) (PKG ID #02) (PKG ID #03)

ISA*00* *00* *ZZ*SUPPLCD *09*005070479ff *

081001*1204*U*00200*000000001*0*P*\@

GS*SH*SUPPLCD*ff*081001*1123*853121201*X*003020@

ST*856*0001@


DTM*011*081001@

DTM*017*081003@

HL*1**S@

MEA*PD*G*250*LB@

TD1*CTN71*3@

TD5*B*2*PRES*T@

TD3*CN*VEH#*1234567@

REF*CN*CARRIER PRO NUM@

FOB*PP@



N1*SF**16*92634@

N1*SF**92*X0000X0@

N1*SU**91*BE@

HL*2*1*I@

LIN*1*SI*ASN*BP*1A-0001@

SN1**1000*PC@

PRF*DAN 51245@

REF*PK*PACK LIST #1@

REF*TN*AUTHORIZTN@

CLD*1*1000*CTN71@

REF*LS*PKG ID #01@

HL*3*1*I@

LIN*2*SI*ASN*BP*2B-0002*EC*0001@

SN1**100*PC@

PRF*DAN 51244@


REF*TN*AUTHORIZTN@

CLD*1*100*CTN71@

REF*LS*PKG ID #02@

HL*4*1*I@

LIN*3*SI*ASN*BP*3C-0003@

SN1**200*PC@

PRF*DAN 76234@


REF*TN*AUTHORIZTN@

CLD*1*200*CTN71@

REF*LS*PKG ID #03@

CTT*4*1300@

SE*40*0001@

GE*1*853121201@

IEA*1*000000001@

EXAMPLE NO. 2

This example is identical to example #1 with the exception that all three items

are combined on a mixed load pallet. Because of the mixed label, the serial number

from the mixed load label is passed with all three items in the shipment. This

example has only one Handling Unit.


|

|

+-------------- MIXED LB1 -----------|

| (PKG ID #4) |

| | |

1A-0001 (item) 2B-0002 3C-0003

(PKG ID #01) (PKG ID #02) (PKG ID #03)

ISA*00* *00* *ZZ*SUPPLCD *09*005070479ff *

081001*1204*U*00200*000000001*0**\*@

GS*SH*SUPPLCD*ff*081001*1123*853121202*X*003020@

ST*856*0001@


DTM*011*081001@

DTM*017*081003*1300@

HL*1**S@

MEA*PD*G*250*LB@

TD1*PLT71*1@

TD5*B*2*AUFF*T@

TD3*CN*VEH#*1234567@




FOB*PP@

N1*SF**16*61604@

N1*SF**92*X0000X0@

N1*SU**91*BE@

HL*2*1*I@

LIN*1*SI*ASN*BP*1A-0001@

SN1**1000*PC@

PRF*AAB 98345@


REF*TN*AUTHORIZTN@

CLD*1*1000*CTN71@

REF*LS*PKG ID #4@

HL*3*1*I@

LIN*2*SI*ASN*BP*2B-0002@

SN1**100*PC@

PRF*AAB 88734@


REF*TN*AUTHORIZTN@

CLD*1*100*CTN71@

REF*LS*PKG ID #4@

HL*4*1*I@

LIN*3*SI*ASN*BP*3C-0003*@

SN1**200*PC@

PRF*AAB 99823@


REF*TN*AUTHORIZTN@

CLD*1*200*CTN71@

REF*LS*PKG ID #4@

CTT*4*1300@

SE*40*0001@

GE*1*853121202@

IEA*1*000000001@

EXAMPLE NO. 3

A shipment with multiple packing lists, each containing multiple items, is shown

here. There are no special reference numbers. Carrier information is not being

sent by the supplier. The material is being shipped on two mixed load pallets,

(two handling units) each containing two different part numbers. Note that the

Pkg ID number from the mixed load label is used. Net weights are shown at the

packing list (part number) level because this material is paid for by weight.

ASN SHIP ID #81001

ASN TOTAL QTY = 4300

ASN TOTAL WT = 1950

+-----------------------------------+ +-----------------------------------+

| PACKING LIST #2 | | PACKING LIST #3 |

| | | |

| MIXED LOAD PKG ID#9 | | MIXED LOAD PKG ID#10 |

| | | |

| REF*PK*#2 REF*PK*#2 | | REF*PK*#3 REF*PK*#3 |

| +--------------+ +--------------+ | | +--------------+ +--------------+ |

| | Part# 4D-0004| | Part# 5E-0005| | | | Part# 6F-0006| | Part# 7G-0007| |

| | | | | | | | | | | |

| | +-------+ | | +-------+ | | | | +-------+ | | +-------+ | |

| | | BOX | | | | BOX | | | | | | BOX | | | | BOX | | |

| | +-------+ | | +-------+ | | | | +-------+ | | +-------+ | |

| |REF*LS*PKG ID4| |REF*LS*PKG ID6| | | |REF*LS*PKG ID7| |REF*LS*PKG ID8| |

| | QTY=1000 PCS | | QTY=2000 PCS | | | | QTY=100 PCS | | QTY=200 PCS | |

| | WT=200 LB | | WT=250 LB | | | | WT=1000 LB | | WT=300 LB | |



| | | +--------------+ | | +--------------+ +--------------+ |

| | +-------+ | | | |

| | | BOX | | | | |

| | +-------+ | | | |

| |REF*LS*PKG ID5| | | |

| | QTY=1000 PCS | | | |

| | WT=200 LB | | | |

| +--------------+ | | |

+===================================+ +===================================+

ISA*00* *00* *ZZ*SUPPLCD *09*005070479ff *

081001*1204*U*00200*000000001*0*P*\@

GS*SH*SUPPLCD*ff*081001*1123*128512301*X*003020@

ST*856*0002@


DTM*011*081001@

DTM*017*081003@

HL*1**S*1@

MEA*PD*G*1880*LB@

TD1*PLT71*2@

TD5*B*2*AUFF*t@


FOB*PP@

N1*SF**16*54283@

N1*SF**92*X0000X0@

N1*SU**91*BE@

HL*2*1*I*0@

LIN**SI*ASN*BP*4D-0004@

SN1**2000*PC@

PRF*EAV 88734@


CLD*1*2000*CTN71@

REF*LS*PKG ID #9@

HL*3*1*I*0@

LIN**SI*ASN*BP*5E-0005*EC*0002@

SN1**2000*PC@

PRF*EAV 87389@

MEA*PD*N*250*LB@


CLD*1*2000*CTN71@

REF*LS*PKG ID #9@

HL*4*1*I*0@

LIN**SI*ASN*BP*6F-0006*EC*0001@

SN1**100*PC@

PRF*EAV 88324@

MEA*PD*N*1000*LB@


CLD*1*100*CTN71@

REF*LS*PKG ID #10@

HL*5*1*I*0@

LIN**SI*ASN*BP*7G-0007*EC*0001@

SN1**200*PC@

PRF*EAV 23997@

MEA*PD*N*300*LB@


CLD*1*200*CTN71@

REF*LS*PKG ID #10@

CTT*5*3300@

SE*46*0002@

GE*1*128512301@

IEA*1*000000001@



EXAMPLE NO. 4

This is an example of a shipment of material that is not controlled by Caterpillar

identification codes (part numbers). Instead, the receipt is controlled by the

item number of the purchase order. In this shipment, two sales manuals are being

sent on a mixed pallet from the supplier. The pallet contains two cases of the

first manual and four cases of the other manual. This examples only has one

handling unit (Mixed Load Label 4)

SHIP IDENT NO (SHIPMENT)

|

|

+------------------ MIXED LB4 ------------------+

| (PKG ID #15) |

| |

| |

| |

| |

01-223-2234-A (item) 01-882-7762-P

(PKG ID #09) (PKG ID #11)

(PKG ID #10) (PKG ID #12)

(PKG ID #13)

(PKG ID #14)

ISA*00* *00* *ZZ*SUPPLCD *09*005070479ff *

081001*1204*U*00200*000000001*0*P*\@

GS*SH*SUPPLCD*ff*081001*1123*128512300*X*003020@

ST*856*0004@


DTM*011*081001@

DTM*017*081003@

HL*1**S*1@

MEA*PD*G*150*LB@

TD1*PLT71*1@

TD5*B*2*AUFF*t@


FOB*PP@

N1*SF**16*61639@

N1*SF**92*X0000X0@

N1*SU**91*BE@

HL*2*1*I*1@

LIN*1*SI*ASN*BP*01-223-2234-A@

SN1**80*PC@

PRF*JEAC54329***860602*05@


CLD*1*80@

REF*LS*PKG ID #15@

HL*3*1*I*1@

LIN*1*SI*ASN*BP*01-882-7762-P@

SN1**300*PC@

PRF*JEAC54329***860602*12@


CLD*1*300@

REF*LS*PKG ID #15@

CTT*3*380@

SE*29*0004@

GE*1*128512300@



IEA*1*000000001@

EXAMPLE NO. 5

This is an example of a shipment containing three different items. Two of the

items (8H-0008 and 9I-0009) are being shipped on a "mixed load" pallet controlled

by a common packing list. The other item (0J-0010) is being shipped both as a

loose pack and on two multiple common item packs. Each of the multiple common

item packs for 0J-0010 contains two sub packs. 0J-0010 is controlled by its own

packing list. Carrier related data is being communicated by the supplier. This

example points out the way the Pkg ID numbers from the CAT bar coded label should

be passed. That is:

1) All label information is passed at the ITEM level.

2) When shipping mixed loads, Pkg ID numbers from the mixed load label is to be

used for all associated items.

3) When shipping with multiple, common item packs, only the Pkg ID number from

the master label is sent. The sub packs Pkg ID numbers are not to be sent.

4) The Pkg ID number of the label of all packs not combined to form a multiple

pack (either mixed item or common item) are to be sent.

Shipping/Part Identification Label Pkg ID numbers are displayed in this example

for master labels 1 & 2, even though they are not passed with the ASN data.


|

|

|

+---------------------+------------+------------+

| | | |

| | | |

| | | |

| | | |

| | | |

+--- MIXED LB5 ---+ | MST-LABEL1 MST-LABEL2

| (Pkg ID #5) | | (Pkg ID #1) (Pkg ID #2)

| | | | |

| | | | |

8H-0008 (item) 9I-0009 0J-0010 0J-0010 0J-0010

| | | | |

| | | | |

| | | | |

Pkg ID #15 Pkg ID #16 Pkg ID #18 Pkg ID #19 Pkg ID #21

Pkg ID #17 Pkg ID #20 Pkg ID #22

ISA*00* *00* *ZZ*SUPPLCD *09*005070479ff *

081001*1204*U*00200*000000001*0*P*\@

GS*SH*SUPPLCD*ff*081001*1123*128512300*X*003020@

ST*856*0008@


DTM*011*081001@

DTM*017*081003@

HL*1**S@

MEA*PD*G*2550*LB@

TD1*PLT71*3@

TD1*CTN71*1@



TD5*B*2*9800*t@

TD5*1*2*CETR*t@

TD3*CN*VEH#*1234567@


FOB*PP@

N1*SF**16*52239@

N1*SF**92*X0000X0@

N1*SU**91*BE@

HL*2*1*I@

LIN*1*SI*ASN*BP*8H-0008*EC*0004@

SN1**1000*PC@


REF*TN*AUTHOR NO@

CLD*1*1000*BOX71@

REF*LS*PKG ID #5@

HL*3*1*I

LIN*2*SI*ASN*BP*9I-0009*EC*0001@

SN1**200*PC@

PRF*DAN 76245@


REF*TN*AUTHOR NO@

CLD*1*200*BOX71@

REF*LS*PKG ID #5@

HL*4*1*I@

LIN*3*SI*ASN*BP*0J-0010*EC*0001@

SN1**1000*PC@

PRF*DAN 25147@


REF*TN*AUTHOR NO@

CLD*2*400*PLT71@

REF*LS*PKG ID #1@

REF*LS*PKG ID #2@

CLD*1*200*BOX71@

REF*LS*SERIAL #18@

CTT*4*2200@

SE*44*0008@

GE*1*128512300@

IEA*1*000000001@

EXAMPLE NO. 6

This example shows a shipment with one item (1K-0011) being shipped in two different

types of containers (tub and basket).


|

|

|

1K-0011 (item)

(Pkg ID #23 - tub)

(Pkg ID #24 - basket)

ISA*00* *00* *ZZ*SUPPLCD *09*005070479ff *

081001*1204*U*00200*000000001*0*P*\@

GS*SH*SUPPLCD*ff*081001*1123*128512300*X*003020@

ST*856*0006@


DTM*011*081001@

DTM*017*081003@

HL*1**S@



MEA*PD*G*1520*LB@

TD1*BSK71*1@

TD5*B*2*AUFF*T@


FOB*PP@

N1*SF**16*44529@

N1*SF**92*X0000X0@

N1*SU**91*BE@

HL*2*1*I@

LIN**SI*ASN*BP*1K-0011*EC*0001@

SN1**90*PC@

PRF*AAB 88723@


CLD*1*50*TUB71@

REF*LS*PKG ID #23@

CLD*1*40*BSK71@

REF*LS*PKG ID #24@

CTT*2*90@

SE*24*0006@

GE*1*128512300@

IEA*1*000000001@

EXAMPLE NO. 7

This is an example of a shipment of one item being shipped in Caterpillar returnable

tubs. Three of the tubs have the same quantity of items, the other two Containers

both contain unique quantities.


|

|

2L-0012 (item)

(PKG ID #25)

(PKG ID #26)

(PKG ID #27)

(PKG ID #28)

(PKG ID #29)

ISA*00* *00* *ZZ*SUPPLCD *09*005070479ff *

081001*1204*U*00200*000000001*0*P*\@

GS*SH*SUPPLCD*ff*081001*1123*128512300*X*003020@

ST*856*0005@


DTM*011*081001@

DTM*017*081003@

HL*1**S@

MEA*PD*G*3350*LB@

TD1*TUB52*5@

TD5*B*2*AUFF*T@


FOB*CC@

N1*SF**16*92438@

N1*SF**92*X0000X0@

N1*SU**91*BE@

HL*2*1*I@

LIN*1*SI*ASN*BP*2L-0012@

SN1**4071*PC@



PRF*AAB 75564@


CLD*3*1000*TUB52@

REF*LS*PKG ID #25@

REF*LS*PKG ID #26@

REF*LS*PKG ID #27@

CLD*1*800*TUB52@

REF*LS*PKG ID #28@

CLD*1*271*TUB52@

REF*LS*PKG ID #29@

CTT*2*4071@

SE*28*0005@

GE*1*128512300@

IEA*1*000000001@

EXAMPLE NO. 8 - ARRANGEMENTS FOR FORGER

ISA*00* *00* *ZZ*SUPPLCD *09*005070479ff *

081001*1204*U*00200*000000001*0*P*\@

GS*SH*SUPPLCD*ff*081001*1123*128512300*X*003020@

ST*856*0005@


DTM*011*081001@

DTM*017*081003@

HL*1**S@

MEA*PD*G*3350*LB@

TD1*TUB52*5@

TD5*B*2*AUFF*T@


FOB*CC@

N1*SF**16*92438@

N1*SF**92*X0000X0@

N1*SU**91*BE@

HL*2*1*I@

LIN*1*SI*ASN*BP*2L-0012*EC*12*GC*1E456@

SN1**2271*PC@

PRF*AAB 75564@


REF*LT*VWE@

REF*HC*HEATA@

CLD*2*1000*TUB52@

REF*LS*PKG ID #25@

REF*LS*PKG ID #26@

CLD*1*271*TUB52@

REF*LS*PKG ID #29@

HL*3*1*I@

LIN*1*SI*ASN*BP*2L-0012*EC*12*GC*1E234@

SN1**200*PC@

PRF*AAB 75564@


REF*LT*VWE@



REF*HC*HEATB@

CLD*2*100*TUB52@

REF*LS*PKG ID #35@

REF*LS*PKG ID #36@

CTT*3*2471@

SE*37*0005@

GE*1*128512300@

IEA*1*000000001@

EXAMPLE NO. 9 - ASN WITH PRICE DATA

ISA*00* *00* *ZZ*SUPPLCD *09*005070479ff *

081001*1204*U*00200*000000001*0*P/*@

GS*SH*SUPPLCD*ff*081001*1123*128512300*X*003020@

ST*856*0005@


DTM*011*081001@

DTM*017*081003@

HL*1**S@

MEA*PD*G*3350*LB@

TD1*TUB52*5@

TD5*B*2*AUFF*T@


FOB*CC@

N1*SF**16*92438@

N1*SF**92*X0000X0@

N1*SU**91*BE@

HL*2*1*I@

LIN*1*SI*ASN*BP*1A-0001*VP*041855*EC*0002*GC*1E456@

SN1**2271*PC@

SLN*1**A*2271*PC*12.50@

PRF*AAB 75564@

PID*F****PUMP@


CLD*2*1000*TUB52@

REF*LS*PKG ID #25@

REF*LS*PKG ID #26@

CLD*1*271*TUB52@

REF*LS*PKG ID #29@

CUR*SE*DEM@

ITA*C**C0090*06**59.7****77*pc**CUTTING CHG@

ITA*C**D0020*06**10****1*DR**DEPOSIT@

CTT*2*2271@

SE*30*0005@

GE*1*128512300@

IEA*1*000000001@

EXAMPLE 10: ASN WITH SERIALIZED PARTS

ISA*00* *00* *ZZ*SUPPLCD *09*005070479ff

*190318*1510*U*00200*000017888*0*P*\_

GS*SH*SUPPLCD*ff*190318*1510*17561*X*003020_

ST*856*0085_

BSN*00*0080748467B*190318*151049_

DTM*011*190318_

DTM*017*190320_

HL*1**S_

MEA*PD*G*38843*LB_

TD1*CNT71*17_

TD3*CN*GLDU*9994549_



REF*CN*0080748467_

FOB*PP_

N1*SF**92*B5327D0_

N1*SF**16*78155_

N1*SU**91*FR_

HL*2*1*I_

LIN*1*BP*5586636*CH*US_

SN1**1*PC_

PRF*FIFF33207_

PID*F****CAPTIVE: 5586636-C9.3-TT538_

REF*PG*AR-A-3514_

REF*SE*SYE31172_

REF*PK*2JCSJ_

CLD*1*1_

REF*LS*1002516008_

HL*3*1*I_

LIN*2*BP*5586636*CH*US_

SN1**1*PC_

PRF*FIFF33207_

PID*F****CAPTIVE: 5586636-C9.3-TT538_

REF*PG*AR-A-3514_

REF*SE*SYE31240_

REF*PK*2JCSJ_

CLD*1*1_

REF*LS*1002516009_

HL*4*1*I_

LIN*3*BP*5586636*CH*US_

SN1**1*PC_

PRF*FIFF33207_

PID*F****CAPTIVE: 5586636-C9.3-TT538_

REF*PG*AR-A-3514_

REF*SE*SYE31241_

REF*PK*2JCSJ_

CLD*1*1_

REF*LS*1002516010_

HL*5*1*I_

LIN*4*BP*5586636*CH*US_

SN1**1*PC_

PRF*FIFF33207_

PID*F****CAPTIVE: 5586636-C9.3-TT538_

REF*PG*AR-A-3514_

REF*SE*SYE31242_

REF*PK*2JCSJ_

CLD*1*1_

REF*LS*1002516011_

HL*6*1*I_

LIN*5*BP*5586636*CH*US_

SN1**1*PC_

PRF*FIFF33207_

PID*F****CAPTIVE: 5586636-C9.3-TT538_

REF*PG*AR-A-3514_

REF*SE*SYE31243_

REF*PK*2JCSJ_

CLD*1*1_

REF*LS*1002516012_

HL*7*1*I_

LIN*6*BP*5586636*CH*US_

SN1**1*PC_

PRF*FIFF33207_

PID*F****CAPTIVE: 5586636-C9.3-TT538_

REF*PG*AR-A-3514_



REF*SE*SYE31244_

REF*PK*2JCSJ_

CLD*1*1_

REF*LS*1002516013_

HL*8*1*I_

LIN*7*BP*5586636*CH*US_

SN1**1*PC_

PRF*FIFF33207_

PID*F****CAPTIVE: 5586636-C9.3-TT538_

REF*PG*AR-A-3514_

REF*SE*SYE31249_

REF*PK*2JCSJ_

CLD*1*1_

REF*LS*1002516014_

CTT*8*8_

SE*85*0085_

GE*1*17561_

IEA*1*000017888_ REQUIRED CHANGES TO YOUR PROCEDURES

An ASN is a logical description of a shipment. It contains both freight and packing list data. It is intended to speed the receipt of material by eliminating manual data entry of receipt information. If Caterpillar requests an ASN with prices, four additional segments can be used to communicate data relative to prices. They are: 1) SLN

Sub line Item Detail segment for pricing quantity, unit of measure, and item price; 2) PID Item Description segment for item description when there is no part number on the purchase order; 3) CUR currency segment to communicate currency other than US dollars; and 4) the ITA Additional Charge Price segment.

To effectively use the ASN data, the receiving clerk must know that ASN data exists. The clerk must also be able

to tie the logical ASN data with the physical shipment. The PKG ID number from the bar coded label provides the ability to mechanically tie the shipment with the ASN. In some cases, the two must be "tied" together before the labels can be scanned.

TO ALLOW PROPER IDENTIFICATION OF THE SHIPMENT WHEN IT ARRIVES AT CATERPILLAR, THE ASN CONTROL NUMBER (SUPPLIER CODE AND SHIPMENT IDENTIFICATION NUMBER-SID) MUST

BE CLEARLY IDENTIFIED WHEN THE SHIPPING DOCUMENTS ARRIVE. TO DO THIS, THE ATTACHED SHEET MUST BE COMPLETED AND SENT WITH THE SHIPMENT DOCUMENTATION.

ATTENTION CARRIER/DRIVER: ----------------------------

THIS SHEET MUST ACCOMPANY THE SHIPMENT (FREIGHT BILL) DELIVERED TO CATERPILLAR. ASN CONTROL NUMBER

____________________ _________________________________________

SUPPLIER CODE SHIPMENT IDENTIFICATION NUMBER (SID)

ASN SYSTEM TERMS AND DEFINITIONS See examples of pallets and cartons on the next page.

(A) SHIPPING PACK. A container used for shipping items from one point to another. (B) MIXED ITEM PACK. A pack containing items with different part/item numbers.

(C) MULTIPLE PACK. A pack containing smaller packages (sub packs) of items. (D) SUBPACK One of the smaller packs within a larger multiple pack.

(E) SHIPPING/PART IDENTIFICATION LABEL. A label used to identify the contents of a shipping pack. This label is bar coded per Caterpillar Standard Practice 20 (Finished Material) or 21 (Primary Metals). These Caterpillar practices are based on the AIAG bar code standards AIAG-B-3 and AIAG-B-5, respectively. The label

has a unique number which provides pack traceability. The label identifies the supplier, purchase order number, ident number and quantity.



(F) MASTER LABEL. A label used to identify and summarize the total contents of a multiple pack. This label is bar coded per Caterpillar Standard Practice 20 which is based on AIAG bar code standard AIAG-B-3. The label

has a unique number which provides ack traceability. The label identifies the supplier, purchase order number, ident number contained in the common item sub packs, and the total quantity of that ident number in the multiple pack.

(G) MIXED LOAD LABEL. A label used to designate mixed item shipping packs. This label is bar coded per Caterpillar Standard Practice 20 which is based on AIAG bar code standard AIAG-B-3. The label has a unique

number which provides pack traceability. The label identifies the supplier. | | 7H8872 |

| |(3S) 26341 | SHIPPING/PART IDENTIFICATION LABEL | +-----------+ | (E)

+---------------+

+-----------+-------+-----------+------+-----------+-------+-----------+ | 1A0001 | | 1A0001 | | 1A0001 | | 1A0001 | |(3S) 28931 | |(3S) 28932 | |(3S) 28933 | |(3S) 28934 |

+-----------+ +-----------+ +-----------+ +-----------+ | (E) | | (D) |

| +-------------------+ | | | MASTER LABEL| (F) | |

| | 1A0001 | | | | (4S) 678234 | | | +-------------------+ |

| | +-----------+ +-----------+ +-----------+ +-----------+ | 1A0001 | | 1A0001 | | 1A0001 | | 1A0001 |

|(3S) 28935 | |(3S) 28936 | |(3S) 28937 | |(3S) 28938 | +-----------+-------+-----------+------+-----------+-------+-----------+

========================================================================== +-----------+-------+-----------+------+-----------+-------+-----------+

| 1A0002 | | 1A0002 | | 3P3492 | | 3P3492 | |(3S) 28781 | |(3S) 28782 | |(3S) 28883 | |(3S) 28884 | +-----------+ +-----------+ +-----------+ +-----------+

| (E) | | |

| (D) | | +-------------------+ | | | MIXED LOAD (G) | |

| | 1A0001 | | | | (5S) 993454 | | | +-------------------+ |

| | | |

+-----------+ +-----------+ +-----------+ +-----------+ | 8M1948 | | 8M1948 | | 7Z0023 | | 3P3492 | |(3S) 28964 | |(3S) 28963 | |(3S) 28882 | |(3S) 28794 |

+-----------+-------+-----------+------+-----------+-------+-----------+ ==========================================================================

BAR CODE SERIAL NOS. AND RELATED QTYS

In order for Caterpillar to efficiently receive material, the ASN shipment data must be "tied" to the physical material. This is done through the use of Caterpillar bar coded shipping labels. By passing the unique PKG ID

number from the bar code label with the ASN part number data, the Caterpillar receiving system can find the corresponding ASN data when that label is physically scanned. The receiving system is designed to only scan the



"high level" shipping labels. That means when an item is shipped on a container with a mixed or master label, the PKG ID numbers from the sub packs should not be sent.

Caterpillar also needs to know the quantity of items associated with the bar code label PKG ID number. This information is passed in the ASN by using a CLD segment. The PKG ID number is then passed in the REF

segment in the CLD loop (after the CLD segment). The following rules are used to determine when a CLD segment is required.

1. A "CLD" customer load detail segment is required for each load that varies by quantity. This means a shipment containing two pallets of the same item, one pallet containing three cartons for a total quantity on the pallet

of 150 pieces and the other pallet containing two cartons with a total quantity of 100 pieces, requires two "CLD" segments even though they are both pallets. (See example #3 on the next page.)

2. If a shipment contains multiple shipping containers of the same item with the same total Quantity, the "CLD" data can be combined in a single "CLD" segment. (See example #2 )

3. The "CLD" segment is always passed at the ITEM level.

4. The accumulated "CLD" quantity for an item (QUANTITY PER LOAD times NUMBER OF LOADS) must equal the accumulated "SN1" QUANTITY SHIPPED.

The following examples show the LIN, SN1, CLD, and REF segments that would be used to describe the shipment. In these examples, each box contains 50 pieces.

SEGMENT DATA

EXAMPLE #1 +-----+ +-----+ +-----+

| 1A1 | | 1A1 | | 1A1 | LIN**BP*1A0001*EC*02@ +-----+ +-----+ +-----+ SN1**300*PC@ +-----+ +-----+ +-----+ CLD*1*300@

| 1A1 | | 1A1 | | 1A1 | REF*LS*MSTR PKG ID #1@ +-----+ +-----+ +-----+

=======================

EXAMPLE #2 +-----+ +-----+ +-----+ +-----+ LIN**BP*1A0001*EC*02@

| 1A1 | | 1A1 | | 1A1 | | 1A1 | SN1**200*PC@ +-----+ +-----+ +-----+ +-----+ CLD*2*100@

=============== =============== REF*LS*MSTR PKG ID #2@ REF*LS*MSTR PKG ID #3@

EXAMPLE #3

+-----+ +-----+ +-----+ +-----+ +-----+ LIN**BP*1A0001*EC*02@ | 1A1 | | 1A1 | | 1A1 | | 1A1 | | 1A1 | SN1**250*PC@ +-----+ +-----+ +-----+ +-----+ +-----+ CLD*1*150@

======================= =============== REF*LS*MSTR PKG ID #4@ CLD*1*100@

REF*LS*MSTR PKG ID #5@



EXAMPLE #4 LIN**BP*1A0001*EC*02@

+-----+ +-----+ +-----+ SN1**150*PC@ | 2A1 | | 2A1 | | 3A1 | CLD*1*150@ +-----+ +-----+ +-----+ REF*LS*MIXED PKG ID #1@

+-----+ +-----+ +-----+ LIN**BP*2A0001*EC*02@ | 1A1 | | 1A1 | | 1A1 | SN1**100*PC@

+-----+ +-----+ +-----+ CLD*1*100@ ======================= REF*LS*MIXED PKG ID #1@ LIN**BP*3A0001*EC*02@

SN1**50*PC@ CLD*1*50@ REF*LS*MIXED PKG ID #1@

EXAMPLE #5 LIN**BP*1A0001*EC*02@ +-----+ +-----+ +-----+ +-----+ +-----+ SN1**250*PC@

| 1A1 | | 1A1 | | 1A1 | | 1A1 | | 1A1 | CLD*1*150@ +-----+ +-----+ +-----+ +-----+ +-----+ REF*LS*MSTR PKG ID #1@ ======================= ======= ======= CLD*2*50@

REF*LS*PKG ID #2@ REF*LS*PKG ID #3@

Heading: Page Pos. Seg. Req. Loop Notes and

No. No. ID Name Des. Max.Use Repeat Comments 19 003 ISA Interchange Control Header O 1 21 005 GS Functional Group Header O 1 23 010 ST Transaction Set Header M 1 24 020 BSN Beginning Segment for Ship Notice M 1 25 030 NTE Note/Special Instruction F 100 26 040 DTM Date/Time/Period O 10

Detail: Page Pos. Seg. Req. Loop Notes and

No. No. ID Name Des. Max.Use Repeat Comments

LOOP ID - HL 1 27 005 HL Hierarchical Level = Shipment Level M 1 28 080 MEA Measurements O 40 29 110 TD1 Carrier Details (Quantity and Weight) O 20 30 120 TD5 Carrier Details (Routing Sequence/Transit

Time) O 12

31 130 TD3 Carrier Details (Equipment) O 12 32 150 REF Reference Numbers O 200 34 210 FOB F.O.B. Related Instructions O 1

LOOP ID - N1 200 35 220 N1 Name O 1

LOOP ID - HL 200000 37 010 HL Hierarchical Level = Item Level M 1 c1 38 020 LIN Item Identification O 1 40 030 SN1 Item Detail (Shipment) O 1 41 040 SLN Subline Item Detail O 100



43 050 PRF Purchase Order Reference O 1 44 070 PID Product/Item Description O 200 45 080 MEA Measurements O 40 46 150 REF Reference Numbers O 200

LOOP ID - CLD 200 48 170 CLD Load Detail M 1 49 180 REF Reference Numbers M 200

50 310 CUR Currency O 1 52 320 ITA Allowance, Charge or Service O 10

Summary: Page Pos. Seg. Req. Loop Notes and

No. No. ID Name Des. Max.Use Repeat Comments 54 010 CTT Transaction Totals M 1 n1 55 020 SE Transaction Set Trailer M 1 56 030 GE Functional Group Trailer O 1 57 040 IEA Interchange Control Trailer O 1

Transaction Set Notes 1. Number of line items (CTT01) is the accumulation of the number of HL segments. If used, hash total

(CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.

Transaction Set Comments 1. The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no

meaning.



Segment: ISA Interchange Control Header

Position: 003 Loop: Level: Heading

Usage: Optional Max Use: 1

Purpose: To start and identify an interchange of one or more functional groups and interchange-related control segments

Syntax Notes:

Semantic Notes: Comments:

Notes: ISA*00* *00* *ZZ*X0000X0 *09*005070479ff *

081001*1204*U*00200*890751204*0*P*\@

Note: ISA Is Required by Caterpillar.

Data Element Summary Ref. Data Des. Element Name Attributes

ISA01 I01 Authorization Information Qualifier M ID 2/2

Code to identify the type of information in the Authorization Information.

00 No Authorization Information Present (No Meaningful

Information in I02) ISA02 I02 Authorization Information M AN 10/10

Information used for additional identification or authorization of the sender or

the data in the interchange. The type of information is set by the Authorization Information Qualifier.

ISA03 I03 Security Information Qualifier M ID 2/2

Code to identify the type of information in the Security Information.

00 No Security Information Present (No Meaningful Information in I04)

ISA04 I04 Security Information M AN 10/10

This is used for identifying the security information about the sender or the data in the interchange. The type of information is set by the Security

Information Qualifier. ISA05 I05 Interchange ID Qualifier M ID 2/2

Qualifier to designate the system/method of code structure used to designate

the sender or receiver ID element being qualified. ZZ Mutually Defined

ISA06 I06 Interchange Sender ID M AN 15/15

Identification code published by the sender for other parties to use as the

receiver ID to route data to them. The sender always codes this number in the sender ID element

CATERPILLAR ASSIGNED SUPPLIER CODE

ISA07 I05 Interchange ID Qualifier M ID 2/2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified.

09 X.121 (CCITT)

ISA08 I07 Interchange Receiver ID M AN 15/15

Identification code published by the receiver of the data. When sending, it is used by the sender as their sending ID, thus other parties sending to them will

use this as a receiving ID to route data to them. 005070479 = CATERPILLAR DUNS CODE + FF = CATERPILLAR

FACILITY CODE

(see APPENDICES)



ISA09 I08 Interchange Date M DT 6/6

Date of the interchange.

ISA10 I09 Interchange Time M TM 4/4

Time of the interchange.

ISA11 I10 Interchange Control Standards Identifier M ID 1/1

Code to identify the agency responsible for the control standard used by the

message that is enclosed by the interchange header and trailer. U = U.S. EDI Community of ASCX12, TDCC, and UCS

ISA12 I11 Interchange Control Version Number M ID 5/5

This version number covers the interchange control segments.

00200 Standard Issued as ANSI X12.5-1987

ISA13 I12 Interchange Control Number M N0 9/9

This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the

interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.

ISA14 I13 Acknowledgment Requested M ID 1/1

Code sent by the sender to request an interchange acknowledgment.

0 No Acknowledgment Requested

ISA15 I14 Test Indicator M ID 1/1

Code to indicate whether data enclosed by this interchange envelope is test or production.

P Production Data

T Test Data

ISA16 I15 Subelement Separator M AN 1/1

This is a field reserved for future expansion in separating data element

subgroups. (In the interest of a migration to international standards, this must be different from the data element separator).



Segment: GS Functional Group Header



Purpose: To indicate the beginning of a functional group and to provide control information Syntax Notes: Semantic Notes: 1 The data interchange control number GS06 in this header must be identical to the

same data element in the associated Functional Group Trailer GE02. Comments: 1 A functional group of related transaction sets, within the scope of X12 standards,

consists of a collection of similar transaction sets enclosed by a functional group

header and a functional group trailer. 2 GS04 is the Group Date.

3 GS05 is the Group Time. Notes: GS*SH*X0000X0*ff*081001*1123*852751201*X*003020@

Note: GS is required by Caterpillar.

Data Element Summary Ref. Data

Des. Element Name Attributes

GS01 479 Functional Identifier Code M ID 2/2

Code identifying a group of application related transaction sets

SH Ship Notice/Manifest (856)

GS02 142 Application Sender's Code M AN 2/15

Code identifying party sending transmission; codes agreed to by trading partners

CATERPILLAR ASSIGNED SUPPLIER CODE

Note: Sender ID sent here in GS element 02 must match

the sender ID sent in ISA element 06.

GS03 124 Application Receiver's Code M AN 2/15

Code identifying party receiving transmission; codes agreed to by trading partners

FACILITY CODE FOR RECEIVING CATERPILLAR FACILITY

Note: Do not pass the full DUNS number here - Only pass

the characters immediately after the 9 digit Cat DUNS

number, which indicates the Caterpillar Facility Code.

GS04 373 Date M DT 6/6

Date (YYMMDD)

Note: At version 003020, the date format is YYMMDD.

Do not pass an 8 digit date.

GS05 337 Time M TM 4/6

Time expressed in 24-hour clock time (HHMMSS) (Time range: 000000

through 235959) TRANSMISSION TIME IN HHMM FORMAT

Note: 2400 is NOT a valid time. Valid values are 0000

thru 2359 or 000000 thru 235959.

GS06 28 Group Control Number M N0 1/9

Assigned number originated and maintained by the sender

GS07 455 Responsible Agency Code M ID 1/2

Code used in conjunction with Data Element 480 to identify the issuer of the

standard X Accredited Standards Committee X12



GS08 480 Version / Release / Industry Identifier Code M AN 1/12

Code indicating the version, release, subrelease and industry identifier of the

EDI standard being used, including the GS and GE segments. Positions 1-3, version number, positions 4-6, release and subrelease level of version; positions 7-12, industry or trade association identifier (optionally assigned by

user). 003020 Draft Standards Approved By ASC X12 Through June

1991.



Segment: ST Transaction Set Header


Usage: Mandatory Max Use: 1

Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: Semantic Notes:

Comments: 1 The transaction set identifier (ST01) is intended for use by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the invoice transaction set).

Notes: ST*856*0001@

Data Element Summary

Ref. Data Des. Element Name Attributes

ST01 143 Transaction Set Identifier Code M ID 3/3

Code uniquely identifying a Transaction Set

856 X12.10 Ship Notice/Manifest

ST02 329 Transaction Set Control Number M AN 4/9

Identifying control number assigned by the originator for a transaction set.



Segment: BSN Beginning Segment for Ship Notice



Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set Syntax Notes: Semantic Notes:

Comments: 1 BSN03 is the date the shipment transaction set is created. 2 BSN04 is the time the shipment transaction set is created.

Notes: BSN*00*SHIP IDENT NO*081001*1023@


Ref. Data


BSN01 353 Transaction Set Purpose Code M ID 2/2

Code identifying purpose of transaction set

00 Original

01 Cancellation

02 Add

03 Delete

04 Change

05 Replace

BSN02 396 Shipment Identification M AN 2/30

A unique control number assigned by the original shipper to identify a specific

shipment EACH SHIPMENT IDENTIFICATION NUMBER (SID) MUST BE UNIQUE

FOR ONE YEAR.

BSN03 373 Date M DT 6/6

Date (YYMMDD)

ASN CREATION DATE

BSN04 337 Time M TM 4/6

Time expressed in 24-hour clock time (HHMMSS) (Time range: 000000

through 235959) ASN CREATION TIME IN HHMM FORMAT



Segment: NTE Note/Special Instruction


Usage: Floating Max Use: 100

Purpose: To transmit information in a free-form format, if necessary, for comment or special instruction

Syntax Notes:

Semantic Notes: Comments: 1 The NTE segment permits free-form information/data which, under ANSI X12

standard implementations, is not machine processable. The use of the NTE segment

should therefore be avoided, if at all possible, in an automated environment. Notes: NTE*ZZZ*ANY NOTES PERTINENT TO THE SHIPMENT@ (SHIPMENT

LEVEL)

NTE*ZZZ*ANY NOTES PERTINENT TO THE PACKING LIST ITEMS@ (ITEM

LEVEL)

NOTE: THE NTE SEGMENT IS USED TO PASS DATA THAT IS INTENDED TO

BE READ BY HUMANS. IN A MECHANIZED ENVIRONMENT, SUCH AS

CATERPILLAR'S ASN, THIS DATA MAY NEVER BE SEEN. ITS USE SHOULD

BE AVOIDED IF AT ALL POSSIBLE.



NTE01 363 Note Reference Code O ID 3/3

Code identifying the functional area or purpose for which the note applies

ZZZ Mutually Defined

NTE02 3 Free Form Message M AN 1/60

Free-form text



Segment: DTM Date/Time/Period



Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 or DTM03 is required. Semantic Notes:

Comments: Notes: DTM*011*081001*1201@

DTM*017*081003*1155@

Note: DTM is required by Caterpillar (See below).



DTM01 374 Date/Time Qualifier M ID 3/3

Code specifying type of date or time, or both date and time

SHIPPED DATE AND ESTIMATED DELIVERY DATE ARE BOTH

REQUIRED BY CATERPILLAR.

011 Shipped

017 Estimated Delivery

DTM02 373 Date X DT 6/6

Date (YYMMDD)

NOTE: IF THE ACTUAL ARRIVAL DATE IS NOT KNOWN, THE

ARRIVAL DATE MUST BE ESTIMATED.

Note: At version 003020, the date format is YYMMDD.

Do not pass an 8 digit date.

DTM03 337 Time X TM 4/6

Time expressed in 24-hour clock time (HHMMSS) (Time range: 000000 through 235959)

TIME FORMAT IS HHMM

Note: 2400 is not a valid time. Valid values are 0000

thru 2359 or 000000 thru 235959.



Segment: HL Hierarchical Level = Shipment Level

Position: 005 Loop: HL Mandatory Level: Detail


Purpose: To identify dependencies among and the content of hierarchically related groups of data segments

Syntax Notes:

Semantic Notes: Comments: 1 The HL segment defines a top-down/left-right ordered structure. 2 HL01 shall contain a unique alphanumeric number for each occurrence of the HL

segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would

be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

3 HL02 identifies the hierarchical ID number of the HL segment to which the current

HL segment is subordinate. 4 HL03 indicates the context of the series of segments following the current HL

segment up to the next occurrence of an HL segment in the transaction. For example,

HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

5 HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Notes: HL*1**S@

Note: Shipment Level HL loop required by Caterpillar.



HL01 628 Hierarchical ID Number M AN 1/12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

HL03 735 Hierarchical Level Code M ID 1/2

Code defining the characteristic of a level in a hierarchical structure

S Shipment



Segment: MEA Measurements



Purpose: To specify physical measurements, including dimension tolerances, weights and counts. Syntax Notes: 1 At least one of MEA03 MEA05 MEA06 or MEA08 is required. 2 If MEA03 is present, then MEA04 is required.

3 If MEA05 is present, then MEA04 is required. 4 If MEA06 is present, then MEA04 is required. 5 If MEA07 is present, then at least one of MEA03 MEA05 or MEA06 is required.

6 Only one of MEA08 or MEA03 may be present. Semantic Notes:

Comments: 1 When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a positive (+) value cannot be assumed, use MEA05 as the negative (-) value and MEA06 as the positive (+) value.

Notes: MEA*PD*G*1250*LB@

IDENTIFIES THE "GROSS" WEIGHT OF THE ENTIRE SHIPMENT.


MEA01 737 Measurement Reference ID Code O ID 2/2

Code specifying the application of physical measurement cited.

PD Physical Dimensions

MEA02 738 Measurement Qualifier O ID 1/3

Code identifying the type of measurement.

G Gross Weight

MEA03 739 Measurement Value X R 1/10

The value of the measurement

Note: Do not pass Decimals; Whole Numbers only.

MEA04 355 Unit or Basis for Measurement Code X ID 2/2

Code identifying the basic unit of measurement.

(SEE APPENDIX)



Segment: TD1 Carrier Details (Quantity and Weight)



Purpose: To specify the transportation details relative to commodity, weight, and quantity Syntax Notes: 1 If TD101 is present, then TD102 is required. 2 If TD103 is present, then TD104 is required.

3 If TD106 is present, then TD107 is required. Semantic Notes: Comments:

Notes: TD1*PLT71*1@

Note: TD1 Required by Caterpillar.

THIS SEGMENT IS USED TO DESCRIBE THE CONTAINERS USED IN A

SHIPMENT. THIS DATA WILL BE USED TO DETERMINE THE NUMBER OF

SHIPPING CONTAINERS (CARTONS, TUBS, PALLETS, RACKS, etc.).

SEE THE SECTION ON THE RULES USED TO DETERMINE HOW TO PASS

CONTAINER DESCRIPTION DATA TO DETERMINE HOW MANY "TD1" SEGMENTS

THERE WILL BE.


Ref. Data


TD101 103 Packaging Code O AN 5/5

Code identifying the type of packaging; Part 1: Packaging Form, Part 2:

Packaging Material (SEE APPENDIX)

Note: Field length of 5. Do not truncate.

TD102 80 Lading Quantity X N0 1/7

Number of units (pieces) of the lading commodity



Segment: TD5 Carrier Details (Routing Sequence/Transit Time)



Purpose: To specify the carrier and sequence of routing and provide transit time information Syntax Notes: 1 At least one of TD502 TD504 or TD505 is required. 2 If TD502 is present, then TD503 is required.

3 If TD507 is present, then TD508 is required. 4 If TD510 is present, then TD511 is required. Semantic Notes:

Comments: 1 When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party

responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.

Notes: TD5*B*92*9800*P@ TD5*B*2*CETR*T@

NOTE: TD5 SEGMENT IS REQUIRED BY CATERPILLAR.



TD501 133 Routing Sequence Code M ID 1/2

Code describing the relationship of a carrier to a specific shipment movement

1 1st Carrier after Origin Carrier

2 2nd Carrier after Origin Carrier

B Origin/Delivery Carrier (Any Mode)

TD502 66 Identification Code Qualifier M ID 1/2

Code designating the system/method of code structure used for Identification Code (67)

2 Standard Carrier Alpha Code (SCAC)

92 Assigned by Buyer or Buyer's Agent

TD503 67 Identification Code M AN 2/17

Code identifying a party.

IF TD502 = 2 STANDARD CARRIER ALPHA CODE FOR CARRIER

IF TD502 = 92 CATERPILLAR ASSIGNED CARRIER CODE FOR

CARRIER

Note: Standard Carrier Alpha Code (SCAC) is required

for MACH1 facilities. Please contact your carrier for

their correct SCAC code.

TD504 91 Transportation Method/Type Code M ID 1/2

Code specifying the method or type of transportation for the shipment

SEE APPENDIX



Segment: TD3 Carrier Details (Equipment)



Purpose: To specify transportation details relating to the equipment used by the carrier Syntax Notes: 1 If TD302 is present, then TD303 is required. 2 If TD304 is present, then both TD305 and TD306 are required.


Notes: TD3*CN*VEH#*1234567@

NOTE: THE VEHICLE NUMBER IS REQUIRED FOR FULL TRUCK LOAD

SHIPMENTS. WHEN THE VEHICLE NUMBER IS LESS THAN EIGHT

CHARACTERS LONG, PASS THE SCAC CODE (SEE TD503) IN TD302 AND

VEHICLE NUMBER IN TD303.



TD301 40 Equipment Description Code M ID 2/2

Code identifying type of equipment used for shipment

CN Container

TD302 206 Equipment Initial X AN 1/4

Prefix or alphabetic part of an equipment unit's identifying number

TD303 207 Equipment Number X AN 1/10

Sequencing or serial part of an equipment unit's identifying number (pure

numeric form for equipment number is preferred) Note: "UNKNOWN" is not an acceptable value and should

not be passed.



Segment: REF Reference Numbers



Purpose: To specify identifying numbers. Syntax Notes: 1 At least one of REF02 or REF03 is required. Semantic Notes:

Comments: Notes: REF*CN*PRO/NUMBER00001@

REF*TN*SHIPORDNUM123@

REF*IV*COMMERCIAL INVOICE@

NOTE: PACKING LIST NUMBER (REF01=PK), CARRIER INVOICE NUMBER

(REF01=CN), HEAT CODE (REF01=HC), AND/OR SUPPLIER'S LOT NUMBER

(REF01=LT) MAY BE PASSED AT EITHER THE SHIPMENT LEVEL OR THE

ITEM LEVEL. IF THE DATA APPLIES TO ALL ITEMS IN THE SHIPMENT

(AND THE SHIPMENT CONTAINS MULTIPLE ITEMS), THIS DATA SHOULD

BE PASSED IN A "REF" SEGMENT AT THE SHIPMENT LEVEL. OTHERWISE,

IT SHOULD BE PASSED AT THE ITEM LEVEL.



REF01 128 Reference Number Qualifier M ID 2/2

Code qualifying the Reference Number.

CN = CARRIER'S PRO NO.

Note: Carrier's PRO Number is mandatory for

Caterpillar. Please contact your carrier for the

correct number.

CN Carrier's Reference Number (PRO/Invoice)

HC Heat Code

IV Seller's Invoice Number

Commercial Invoice Number

LT Lot Number

PK Packing List Number

PO Purchase Order Number

High Level PO Number for Configurable

Product Orders.

TN Transaction Reference Number

TN = SHIPMENT ORDER NUMBER (obtained

from Caterpillar Global Material

Managment)

REF02 127 Reference Number X AN 1/30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

IF REF01 = CN, then CARRIER'S PRO NO

IF REF01 = TN, then SHIPMENT ORDER NUMBER

Note: Do not pass "UNKNOWN" in this segment! Please

contact your carrier for their correct PRO Number.

NOTE: ALTHOUGH CARRIER PRO NUMBER IS PREFERABLE, IF

CARRIER PRO NUMBER CANNOT BE DETERMINED, CATERPILLAR

WILL ALSO ACCEPT CARRIER TRACKING NUMBER, CONTAINER



NUMBER, INVOICE NUMBER, BILL OF LAIDING NUMBER OR PACKING

LIST NUMBER.



Segment: FOB F.O.B. Related Instructions



Purpose: To specify transportation instructions relating to shipment Syntax Notes: 1 If FOB03 is present, then FOB02 is required. 2 If FOB04 is present, then FOB05 is required.

3 If FOB07 is present, then FOB06 is required. 4 If FOB08 is present, then FOB09 is required. Semantic Notes:

Comments: 1 FOB01 indicates which party will pay the carrier. 2 FOB02 is the code specifying transportation responsibility location.

3 FOB06 is the code specifying title passage location. 4 FOB08 is the code specifying the point at which the risk of loss transfers. This may

be different than the location specified in FOB02/FOB03 and FOB06/FOB07.

Notes: FOB*CC@

Note: FOB segment is only allowed at the HL Shipment

Hierarchical Level (HL03='S'). FOB should not be sent at the

detail level.

REQUIRED BY CATERPILLAR.



FOB01 146 Shipment Method of Payment M ID 2/2

Code identifying payment terms for transportation charges

IF PO = FREE ASTRAY

CC Collect

DF Defined by Buyer and Seller

PO Prepaid Only

PP Prepaid (by Seller)



Segment: N1 Name

Position: 220 Loop: N1 Optional Level: Detail


Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 If either N103 or N104 is present, then the other is required.

Semantic Notes: Comments: 1 This segment, used alone, provides the most efficient method of providing

organizational identification. To obtain this efficiency the "ID Code" (N104) must

provide a key to the table maintained by the transaction processing party. Notes: N1*SF**16*61604@

N1*SF**92*X0000X0@

N1*SF**91*120010@

N1*SU**91*BE@

N1*MA*92*FF00@



N101 98 Entity Identifier Code M ID 2/2

Code identifying an organizational entity or a physical location.

CS Consolidator

MA Party for whom Item is Ultimately Intended

MA is used to inform Consolidator the

ultimate destination. (Obtained from

EDI 830 "Deliver To" code. Required for

all imports/exports for the Container

Cross Docks.

SF Ship From

SU Supplier/Manufacturer

N103 66 Identification Code Qualifier X ID 1/2

Code designating the system/method of code structure used for Identification Code (67)

IF N101 = SF

16 = POSTAL ZIP CODE

92 = CATERPILLAR DEFINED SUPPLIER CODE

91 = CATERPILLAR SHIP POINT

IF N101 = SU

91 = COUNTRY CODE

16 ZIP Code

91 Assigned by Seller or Seller's Agent

92 Assigned by Buyer or Buyer's Agent

N104 67 Identification Code X AN 2/17

Code identifying a party.

IF N103 or N104 is present, the other is required.

IF N101= SF AND N103 = 16, THEN POSTAL ZIP CODE OF SHIP

FROM ORIGIN LOCATION

IF N101= SF AND N103 = 92, THEN CATERPILLAR DEFINED

SUPPLIER CODE

IF N101= SF AND N103 = 91, THEN CATERPILLAR SUPPLIED SHIP



POINT CODE (Only needed if no postal zip code can be

provided.)

IF N101= SU AND N103 = 91, THEN ISO COUNTRY CODE

IF N101= MA AND N103 = 92, THEN CATERPILLAR DEFINED

FACILITY and DOCK CODE



Segment: HL Hierarchical Level = Item Level



Purpose: To identify dependencies among and the content of hierarchically related groups of data segments

Syntax Notes:

Semantic Notes: Comments: 1 The HL segment defines a top-down/left-right ordered structure. 2 HL01 shall contain a unique alphanumeric number for each occurrence of the HL

segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would

be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.

3 HL02 identifies the hierarchical ID number of the HL segment to which the current

HL segment is subordinate. 4 HL03 indicates the context of the series of segments following the current HL

segment up to the next occurrence of an HL segment in the transaction. For example,

HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

5 HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

Notes: HL*2*1*I@

NOTE: When shipping "Serialized Parts", please start a new

"Item Level HL" loop for each serialized part. (See "Shipping

Serialized Parts" section at the begnning of this Guideline).



HL01 628 Hierarchical ID Number M AN 1/12

A unique number assigned by the sender to identify a particular data segment in a hierarchical structure

HL02 734 Hierarchical Parent ID Number O AN 1/12

Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to

HL03 735 Hierarchical Level Code M ID 1/2

Code defining the characteristic of a level in a hierarchical structure

I Item



Segment: LIN Item Identification



Purpose: To specify basic item identification data Syntax Notes: 1 If LIN04 is present, then LIN05 is required. 2 If LIN06 is present, then LIN07 is required.

3 If LIN08 is present, then LIN09 is required. 4 If LIN10 is present, then LIN11 is required. 5 If LIN12 is present, then LIN13 is required.

6 If LIN14 is present, then LIN15 is required. 7 If LIN16 is present, then LIN17 is required.



14 If LIN30 is present, then LIN31 is required. Semantic Notes:

Comments: 1 See the Data Dictionary for a complete list of ID's. 2 LIN01 is the line item identification 3 LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each

item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.

Notes: LIN*1*BP*1A-0001*EC*0001@

Note: Country of Origin Code (LIN02=CH) is REQUIRED for

Caterpillar.

Note: Engineering Change Number (LIN02=EC) must match what was

sent from Caterpillar on the corresponding 850, 860 or 830. If

the Engineering Change Number was not passed, then it should

not be passed on the 856.

NOTE: THE LIN02 AND LIN03 CAN OCCUR 15 TIMES IN ANY ONE LIN

SEGMENT IN ANY OF THE OCCURRENCES, HOWEVER, IF THE PURCHASE

ORDER IS SENT TO THE SUPPLIER WITHOUT A BUYER IDENTIFICATION

NUMBER, ENGINEERING CHANGE NUMBER OR 1E SPEC NUMBER, AND THE

SUPPLIER DOES NOT HAVE A VENDOR IDENTIFICATION NUMBER, THE LIN

SEGMENT SHOULD BE SENT TO CATERPILLAR WITH "SI" IN LIN02 AND

"ASN" IN LIN03. THIS IS A MANDATORY SEGMENT.



LIN01 350 Assigned Identification O AN 1/11

Alphanumeric characters assigned for differentiation within a transaction set

LIN02 235 Product/Service ID Qualifier M ID 2/2

Code identifying the type/source of the descriptive number used in

Product/Service ID (234) NOTE: BP - BUYER'S PART NUMBER IS REQUIRED BY

CATERPILLAR AND THE FORMAT MUST MATCH EXACTLY AS SENT BY

CATERPILLAR.

NOTE: GC = 1E SPEC



BP Buyer's Part Number

CH Country of Origin Code

DR Drawing Revision Number

EC Engineering Change Level

GC Grade Code

PD Part Number Description

PW Part Drawing

SI Standard Industrial Classification Code

VC Vendor's (Seller's) Catalog Number

VP Vendor's (Seller's) Part Number

LIN03 234 Product/Service ID M AN 1/30

Identifying number for a product or service

AS PER VALUE IN PREV ELEMENT IF LIN02 = 'SI', LIN03 SHOULD

= 'ASN'.

LIN04 235 Product/Service ID Qualifier O ID 2/2


Product/Service ID (234) LIN05 234 Product/Service ID X AN 1/30



Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN07 234 Product/Service ID X AN 1/30







Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN11 234 Product/Service ID X AN 1/30








Segment: SN1 Item Detail (Shipment)



Purpose: To specify line-item detail relative to shipment Syntax Notes: 1 If SN105 is present, then SN106 is required. Semantic Notes:

Comments: 1 SN101 is the ship notice line item identification. 2 SN103 defines the unit of measurement for both SN102 and SN104.

Notes: SN1**1000*PC@

NOTE: TO DELETE A PACKING LIST ITEM THAT WAS EITHER SENT IN ERROR

BY A PREVIOUS TRANSMISSION OR WHICH IS NO LONGER VALID, SEND

THE IDENT NUMBER (LIN SEGMENT), THE P.O. NUMBER (PRF SEG), AND

THE PACKING LIST NUMBER (REF SEGMENT) ALONG WITH AN SN1 SEGMENT

WITH A NUMBER OF UNITS SHIPPED (SN102) EQUAL TO ZERO. THE

TRANSACTION SET PURPOSE (BSN02) MUST BE A VALUE OF 04 (CHANGE)

TO DELETE THE PACKING LIST ITEM.

EFFECTIVE WITH VERSION 3020, IT IS POSSIBLE TO TRANSMIT CHANGES

TO PREVIOUSLY SENT 856 TRANSACTIONS. SEE BSN SEGMENT FOR VALID

CODES. THE ONLY TIME A SHIPMENT NOTICE NUMBER (S.I.D.) SHOULD

BE USED TWICE IN ONE YEAR IS WHEN YOU ARE CHANGING A PREVIOUSLY

SENT S.I.D. NUMBER.



SN102 382 Number of Units Shipped M R 1/10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

SN103 355 Unit or Basis for Measurement Code M ID 2/2


UOM FOR THE QUANTITY SHIPPED

(SEE APPENDIX)

NOTE: UOM MUST MATCH VALUE SENT BY CATERPILLAR..



Segment: SLN Subline Item Detail



Purpose: To specify product subline detail item data Syntax Notes: 1 If SLN07 is present, then SLN06 is required. 2 If SLN08 is present, then SLN06 is required.

3 If SLN09 is present, then SLN10 is required. 4 If SLN11 is present, then SLN12 is required. 5 If SLN13 is present, then SLN14 is required.

6 If SLN15 is present, then SLN16 is required. 7 If SLN17 is present, then SLN18 is required.

8 If SLN19 is present, then SLN20 is required. 9 If SLN21 is present, then SLN22 is required. 10 If SLN23 is present, then SLN24 is required.

11 If SLN25 is present, then SLN26 is required. 12 If SLN27 is present, then SLN28 is required. Semantic Notes:

Comments: 1 See the Data Dictionary for a complete list of ID's. 2 SLN01 is the identifying number for the subline item. It is related to (but not

necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.

3 SLN02 is the identifying number for the subline level. The subline level is analogous

to the level code used in a bill of materials. 4 SLN09 through SLN28 provide for ten (10) different product/service ID's for each

item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No.,

SKU. Notes: USED ONLY FOR PAY-ON-RECEIPT PROGRAM, OTHERWISE NOT USED.

SLN*1**A*955*PC*97.22@

SLN*1**A*100*PC*25@

NOTE: If the ASN is resent, we overlay the old price data with

new. Therefore, when resending an ASN be sure the data on the

SLN, CUR, and ITA is what you want to be sent to Caterpillar.



SLN01 350 Assigned Identification M AN 1/11


ALWAYS USE '1'.

SLN03 661 Configuration Code M ID 1/1

Code indicating the relationship of the subline item to the baseline item.

A Added

SLN04 380 Quantity M R 1/15

Numeric value of quantity

FORMAT = 9(8).9999

* THE DECIMAL POINT SHOULD BE TRANSMITTED IF PRICE OR

QUANTITY IS LESS THAN A WHOLE NUMBER.

SLN05 355 Unit or Basis for Measurement Code M ID 2/2


(SEE APPENDIX)

Refer to 003020 Data Element Dictionary for acceptable code values.



SLN06 212 Unit Price X R 1/14

Price per unit of product, service, commodity, etc.

FORMAT = 9(7).99999

* THE DECIMAL POINT SHOULD BE TRANSMITTED IF PRICE OR

QUANTITY IS LESS THAN A WHOLE NUMBER.



Segment: PRF Purchase Order Reference



Purpose: To provide reference to a specific purchase order Syntax Notes: Semantic Notes:

Comments: Notes: PRF*DAN 51245*001***01@

NOTE: RELEASE NUMBERS ARE ONLY USED WITH "OPEN END" TYPE

PURCHASE ORDERS.

ONE "PRF" SEGMENT PER PACKING LIST/P.O./IDENT NUMBER

Note: PRF Segment Required by Caterpillar.


PRF01 324 Purchase Order Number M AN 1/22

Identifying number for Purchase Order assigned by the orderer/purchaser

PRF02 328 Release Number O AN 1/30

Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction

PRF05 350 Assigned Identification O AN 1/11


PURCHASE ORDER LINE NUMBER IS REQUIRED AND MUST MATCH THE

EXACT PURCHASE ORDER LINE NUMBER AND FORMAT SENT BY

CATERPILLAR FOR THIS PART.



Segment: PID Product/Item Description



Purpose: To describe a product or process in coded or free-form format Syntax Notes: 1 If PID04 is present, then PID03 is required. 2 At least one of PID04 or PID05 is required.

Semantic Notes: Comments: 1 If PID01 = ``F'', then PID05 is used. If PID01 = ``S'', then PID04 is used. If PID01 =

``X'', then both PID04 and PID05 are used.

2 Use PID03 to indicate the organization that publishes the code list being referred to. 3 PID04 should be used for industry-specific product description codes.

4 Use PID06 when necessary to refer to the product surface or layer being described in the segment.

Notes: PID*F****DRILL 6;00MM 502 W/HP TANG@

NOTE: IF THE PURCHASE ORDER WAS SENT TO THE SUPPLIER WITHOUT

A BUYER IDENTIFICATION NUMBER, THE PID SEGMENT CAN BE USED AS

DESCRIPTION TO DEFINE THE ITEM ON THE ASN.



PID01 349 Item Description Type M ID 1/1

Code indicating the format of a description

F Free-form

PID03 559 Agency Qualifier Code X ID 2/2

Code identifying the agency assigning the code values

AB Assigned by Buyer

PID04 751 Product Description Code X AN 1/12

A code from an industry code list which provides specific data about a product

characteristic For Configurable Product Orders, Report "Componant Part

Number" here.

PID05 352 Description X AN 1/80

A free-form description to clarify the related data elements and their content



Segment: MEA Measurements



Purpose: To specify physical measurements, including dimension tolerances, weights and counts. Syntax Notes: 1 At least one of MEA03 MEA05 MEA06 or MEA08 is required. 2 If MEA03 is present, then MEA04 is required.

3 If MEA05 is present, then MEA04 is required. 4 If MEA06 is present, then MEA04 is required. 5 If MEA07 is present, then at least one of MEA03 MEA05 or MEA06 is required.

6 Only one of MEA08 or MEA03 may be present. Semantic Notes:

Comments: 1 When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a positive (+) value cannot be assumed, use MEA05 as the negative (-) value and MEA06 as the positive (+) value.

Notes: MEA*PD*N*1250*LB@

THE "NET" WEIGHT FOR EACH PACKING LIST. (MULTIPLE "MEA"

SEGMENTS PER SHIPMENT)

NOTE: NET WEIGHT IS ONLY USED WHEN MATERIAL IS PAID FOR BY

WEIGHT. THIS NORMALLY IS ONLY USED FOR UNFORMED STEEL CODES.



MEA01 737 Measurement Reference ID Code O ID 2/2

Code specifying the application of physical measurement cited.

CH Chemistry

PD Physical Dimensions

MEA02 738 Measurement Qualifier O ID 1/3

Code identifying the type of measurement.

LN Length

N Actual Net Weight

TH Thickness

WD Width

WT Weight

MEA03 739 Measurement Value X R 1/10

The value of the measurement

Note: Do not pass Decimals; Whole Numbers only.

MEA04 355 Unit or Basis for Measurement Code X ID 2/2


(SEE APPENDIX)







Comments: Notes: REF*PK*ABC123@

REF*TN*AUTHORIZTN@ (KANBAN/TRIGGER/JIT NUMBER)

NOTE: PACKING LIST NUMBER (REF01=PK), HEAT CODE (REF01=HC),

AND/OR SUPPLIER'S LOT NUMBER (REF01=LT) MAY BE PASSED AT EITHER

THE SHIPMENT LEVEL OR THE ITEM LEVEL. IF THE DATA APPLIES TO

ALL ITEMS IN THE SHIPMENT (AND THE SHIPMENT CONTAINS MULTIPLE

ITEMS), THIS DATA SHOULD BE PASSED IN A "REF" SEGMENT AT THE

SHIPMENT LEVEL. OTHERWISE, IT SHOULD BE PASSED AT THE ITEM

LEVEL.

PLEASE CREATE SEPERATE ITEM LOOPS FOR MULTIPLE CUSTOMER ORDER

NUMBERS PER ITEM.

TN = AUTH NO ( KANBAN / TRIGGER / JIT NUMBER) FOR "JUST IN TIME"

MATERIAL.

Note: PK = Packing List Number (required by Caterpillar)





LT = FORGER CODE

TN = AUTHORIZATION NO ( KANBAN / TRIGGER / JIT NUMBER)

AN Associated Purchase Orders

For Configurable Product orders, this is

the Componant PO Number.

BT Batch Number

CN Carrier's Reference Number (PRO/Invoice)

CO Customer Order Number

MSO Number

HC Heat Code

IL Internal Order Number

Sales Document Number

LT Lot Number

PK Packing List Number

SE Serial Number

TN Transaction Reference Number



PER VALUE IN REF01

Note: For Packing List Number, do not pass special



characters and do not pass leading zeros.



Segment: CLD Load Detail

Position: 170 Loop: CLD Mandatory Level: Detail


Purpose: To specify the number of material loads shipped Syntax Notes: Semantic Notes:

Comments: 1 The CLD data segment may be used to provide information to aid in the preparation of move tags and/or bar coded labels.

2 CLD05, "Unit of Measure Code," is used to dimension the value given in CLD04,

"Size." Notes: CLD*1*300*PLT71*5.0*PC@

IDENTIFIES THE CUSTOMER'S (CATERPILLAR'S) STORAGE LOAD

INFORMATION REQUIRED TO TAG AND STORE THE PART. THIS INCLUDES

THE CONTAINER TYPE AND QUANTITY, QUANTITY PER CONTAINER, AND

QUANTITY PER PACK WITHIN THE CONTAINER.

(MULTIPLE "CLD" SEGMENTS PER PACKING LIST/P.O./IDENT NUMBER)



CLD01 622 Number of Loads M N0 1/5

Number of customer-defined loads shipped by the supplier

NUMBER OF STORAGE LOADS SENT CONTAINING THE SAME

QUANTITY.

CLD02 382 Number of Units Shipped M R 1/10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

QUANTITY OF ITEMS CONTAINED IN THIS STORAGE LOAD.

CLD03 103 Packaging Code O AN 5/5

Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material

(SEE APPENDIX.)

CLD04 357 Size O R 1/8

Size of supplier units in pack

SUBPACK QUANTITY FORMAT 9(5).99

CLD05 355 Unit or Basis for Measurement Code O ID 2/2


UOM FOR THE SUBPACK QUANTITY.

(SEE APPENDIX.)




Position: 180 Loop: CLD Mandatory Level: Detail



Comments: Notes: REF*LS*123456@

NOTE: PKG ID # (BAR CODE SERIAL NUMBER) IS REQUIRED BY

CATERPILLAR AND MUST MATCH THE PKG ID NUMBER PRINTED ON THE

HANDLING UNIT BAR CODE SHIPPINIG LABEL, PER CATERPILLAR

STANDARD PRACTICE 20.





LS Bar-Coded Serial Number

PKG ID # = Package ID Number = Bar-Coded

Serial Number



REF02 must be the Pkg ID Number printed on the Bar Code

Shipping Label of the High Level Label or Handling Unit.

Please note the following field length restrictions for

the Bar Coded Serial Number (Pkg ID #) value as

specificied in Caterpillar Standard Practice 20

documentation: The legnth of the package ID number

must NOT exceed seventeen (17) alphanumeric characters.

DO NOT PASS A BAR-CODED SERIAL NUMBER VALUE GREATER THAN

17 CHARACTERS!!



Segment: CUR Currency



Purpose: To specify the currency (dollars, pounds, francs, etc.) used in a transaction Syntax Notes: 1 If CUR08 is present, then CUR07 is required. 2 If CUR09 is present, then CUR07 is required.

3 If CUR11 is present, then CUR10 is required. 4 If CUR12 is present, then CUR10 is required. 5 If CUR14 is present, then CUR13 is required.

6 If CUR15 is present, then CUR13 is required. 7 If CUR17 is present, then CUR16 is required.

8 If CUR18 is present, then CUR16 is required. 9 If CUR20 is present, then CUR19 is required. 10 If CUR21 is present, then CUR19 is required.

Semantic Notes: Comments: 1 Monetary values are assumed to be expressed in the currency of the country of the

transaction originator unless the optional CUR segment is used to specify a different

currency. The CUR segment also permits the transaction originator to indicate a specific exchange rate, foreign exchange location and date/time as the basis for a

currency conversion. Example 1. Assuming the currency of the transaction originator is U.S. dollars, the following CUR segment, when used in the heading area of a transaction, would indicate that all monetary values appearing in the transaction

are expressed in Canadian Dollars (CAD). (In this example the exchange rate is at the discretion of the receiver). CUR*BY*CAD* N/L Example 2. Assuming the currency of the transaction originator is U.S. dollars, the following CUR segment,

when used in the detail area of a transaction, describes a currency conversion for that particular item from U.S. dollars to Canadian dollars. It also indicates that a specific

exchange rate, at a specified foreign exchange location on a given date/time be used as the basis for the currency conversion. Notes below the diagram describe the meaning of the element values.

CUR*BY*USD*1.20*SE*CAD*NY*007*840821*1400 N/L 1 2 3 4 1. Identifies the buyer's (BY) currency as U.S. dollars (USD). 2. The multiplier (1.20) is the exchange rate factor for the conversion. 3. Identifies the seller's (SE)

currency as Canadian dollars (CAD). 4. Indicates the basis for the exchange rate as the New York Foreign Exchange (NY) and the effective date/time (007) as August

21, 1984 (840821) at 2:00 P.M. (1400). The value for this item is to be converted to Canadian dollars (CAD) at the exchange rate of 1.20, based on the New York Foreign Exchange (NY) at 2:00 P.M. (1400) on August 21, 1984. The actual unit

price conversion for the item would be: The unit price value 7.50 (U.S. dollars) multiplied by the exchange rate (1.20) equals 9.00 Canadian dollars (7.50 X 1.20 = 9.00) CUR07 through CUR21 provide for five (5) dates/times relating to the

currency conversion, i.e., effective date, expiration date, etc. Notes: USED ONLY FOR PAY-ON-RECEIPT PROGRAM, OTHERWISE NOT USED.

CUR*SE*DEM@

SPECIFIES THE CURENCY, OTHER THAN U. S. DOLLARS, IN WHICH THE

INVOICE IS TO BE PAID. THIS SEGMENT SHOULD NOT BE USED WHEN

INVOICE AMOUNT IS IN U.S. DOLLARS.

NOTE: If the ASN is resent, we overlay old price data with new.

Be sure the data on the SLN, CUR, and ITA is what you want sent

to Caterpillar because we delete the old data and load the new.


Ref. Data




CUR01 98 Entity Identifier Code M ID 2/2

Code identifying an organizational entity or a physical location.

SE Selling Party

CUR02 100 Currency Code M ID 3/3

Code (Standard ISO) for country in whose currency the charges are specified

NON-US CURRENCY INVOICES ONLY. (SEE APPENDIX)



Segment: ITA Allowance, Charge or Service



Purpose: To specify allowances, charges, or services Syntax Notes: 1 If ITA02 is present, then at least one of ITA03 ITA13 or ITA14 is required. 2 If ITA08 is present, then ITA09 is required.

3 If ITA10 is present, then ITA11 is required. Semantic Notes: Comments: 1 If ITA01 = A-Allowance or C-Charge, then at least one of ITA06, ITA07, or ITA08

must be present. 2 ITA02 identifies the source of the code value in ITA03 or ITA15.

3 If ITA07 is present with either ITA06 or ITA08, then ITA07 takes precedence. 4 ITA12 is the quantity of free goods. 5 ITA13 is used to clarify the allowance, charge, or service.

Notes: USED ONLY FOR PAY-ON-RECEIPT PROGRAM, OTHERWISE NOT USED.

ITA*C**C0090*06**59.7****77*PC**CUTTING CHG@

NOTE: MAXIMUM ADDITIONAL CHARGES PER ITEM ON PURCHASE ORDER

IS TEN.

If the ASN is resent, we overlay old price data with new. Be

sure the data on the SLN, CUR, and ITA is what you want sent

to Caterpillar because we delete the old data and load the new.


ITA01 248 Allowance or Charge Indicator M ID 1/1

Code which indicates an allowance or charge for the service specified

A Allowance

C Charge

ITA02 559 Agency Qualifier Code O ID 2/2

Code identifying the agency assigning the code values

AX ANSI Accredited Standards Committee, X12

ITA03 560 Special Services Code X ID 2/10

Code identifying the special service

IDENTIFIES ADDITIONAL ALLOWANCE OR CHARGE.

SEE APPENDIX

ITA04 331 Allowance or Charge Method of Handling Code M ID 2/2

Code indicating method of handling for an allowance or charge

06 Charge to be Paid by Customer

ITA06 359 Allowance or Charge Rate O R 1/9

Allowance or Charge Rate per Unit

FORMAT = 9(7).99999

THE DECIMAL POINT SHOULD BE TRANSMITTED IF LESS THAN A

WHOLE NUMBER.

ITA10 339 Allowance or Charge Quantity O R 1/10

Quantity basis when allowance or charge quantity is different from the purchase order or invoice quantity

FORMAT = 9 (8).9999



THE DECIMAL POINT SHOULD BE TRANSMITTED IF THE QUANTITY

OR PRICE IS LESS THAN A WHOLE NUMBER.

ITA11 355 Unit or Basis for Measurement Code X ID 2/2


(SEE APPENDIX)

ITA13 352 Description X AN 1/80

A free-form description to clarify the related data elements and their content



Segment: CTT Transaction Totals

Position: 010 Loop: Level: Summary


Purpose: To transmit a hash total for a specific element in the transaction set Syntax Notes: 1 If CTT03 is present, then CTT04 is required. 2 If CTT05 is present, then CTT06 is required.

Semantic Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction completeness

and correctness.

Notes: CTT*2*1100@



CTT01 354 Number of Line Items M N0 1/6

Total number of line items in the transaction set

Number of line items (CTT01) is the accumulation of the

number HL segments in the transaction.

CTT02 347 Hash Total O R 1/10

Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the

maximum size of the hash total of the data element. Example:

-.0018 First occurrence of value being hashed. .18 Second occurrence of value

being hashed. 1.8 Third occurrence of value being hashed. 18.01 Fourth occurrence of value being hashed. ------- 1855 Hash total prior to truncation. 855 Hash total after truncation to three-digit field.



Segment: SE Transaction Set Trailer



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

Syntax Notes:

Semantic Notes: Comments: 1 SE is the last segment of each transaction set.

Notes: SE*78*0001@


Ref. Data


SE01 96 Number of Included Segments M N0 1/6

Total number of segments included in a transaction set including ST and SE

segments SE02 329 Transaction Set Control Number M AN 4/9

Identifying control number assigned by the originator for a transaction set.



Segment: GE Functional Group Trailer



Purpose: To indicate the end of a functional group and to provide control information Syntax Notes: Semantic Notes: 1 The data interchange control number GE02 in this trailer must be identical to the

same data element in the associated Functional Group Header GS06. Comments: 1 The use of identical data interchange control numbers in the associated functional

group header and trailer is designed to maximize functional group integrity. The

control number is the same as that used in the corresponding header. Notes: GE*1*852751201@



GE01 97 Number of Transaction Sets Included M N0 1/6

Total number of transaction sets included in the functional group or

interchange (transmission) group terminated by the trailer containing this data element

GE02 28 Group Control Number M N0 1/9

Assigned number originated and maintained by the sender



Segment: IEA Interchange Control Trailer



Purpose: To define the end of an interchange of one or more functional groups and interchange-related control segments

Syntax Notes:


Notes: IEA*1*128528701@


Ref. Data


IEA01 I16 Number of Included Functional Groups M N0 1/5

A count of the number of functional groups included in a transmission.

IEA02 I12 Interchange Control Number M N0 9/9

This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the

interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.

caterpillar: confidential green 856 ship notice/manifest

Documents