Caterpillar Inc. 856 - Advance Ship Notice (ASN)
Caterpillar Inc.856 - Advance Ship Notice (ASN)
PREFACE .4REQUIRED CHANGES TO YOUR PROCEDURES .5ASN SYSTEM TERMS AND DEFINITIONS.6BAR CODE SERIAL NOS. AND RELATED QTYS .8USE OF INDUSTRY IDENTIFICATION VALUES . 10GENERAL COMMUNICATION FORMAT . 11SEGMENT FUNCTIONS AND ARRANGEMENTS . 13EXPLANATION OF ANSI LEVELS . 15TRANSACTION SEQUENCE WITHIN THE LEVEL. 17CONTROLS REQUIRED BY ANSI. 19EXPLANATION ON DATA SEGMENT LAYOUTS . 20BSN-BEGINNING SEGMENT (HEADER DATA) . 22CLD-CUSTOMER LOAD DETAIL (ITEM LEVEL) . 23CTT-TRANSACTION TOTALS SEGMENT . 24CUR-CURRENCY SEGMENT . 25DTM-DATE/TIME REFERENCE SEGMENT . 26FOB-F.O.B.RELATED INSTRUCTIONS SEGMENT . 27GE - FUNCTIONAL GROUP TRAILER SEGMENT . 28GS -FUNCTIONAL GROUP HEADER SEGMENT . 29HL -HIERARCHICAL LEVEL IDENTIFIER SEGMENt . 30IEA-INTERCHANGE CONTROL TRAILER SEGMENT . 31ISA-INTERCHANGE CONTROL HEADER SEGMENT . 32ITA ADDITIONAL CHARGES SEGMENT . 34LIN-LINE ITEM DETAIL SEGMENT (ITEM LVL) . 352
MEA-MEASUREMENTS SEGMENT (SHIP/ITEM LVL) . 36NTE-NOTES SEGMENT (SHIP AND/OR ITEM LVL) . 37N1 -NAME SEGMENT (SHIPMENT LEVEL) . 38PID-ITEM DESCRIPTION SEGMENT . 39PRF-PURCHASE ORDER REFERENCE SEGMENT . 40REF-REFERENCE NUMBERS SEGMENT . 41SE -TRANSACTION SET TRAILER SEGMENT . 42SLN-SUBLINE ITEM DETAIL SEGMENT (PRICES) . 43SN1-ITEM DETAIL (SHIPMENT) SEG (ITEM LVL) . 44ST -TRANSACTION SET HEADER SEGMENT . 45TD1-CARRIER DETAILS (QTY AND WEIGHTS) . 46TD3-CARRIER DETAIL (EQUIP) SEG (SHIP LVL) . 47TD5-CARRIER DETAIL (ROUTING) SEG (SHIP) . 48INTRODUCTION . 493
PREFACEThis writing is intended to give details on how to construct anelectronic Advance Ship Notice (ASN) transaction set 856 to satisfyCaterpillar's requirements.A ZWIP-specific document is available for suppliers sending advanceship notices under the ZWIP program. You can obtain the ZWIP EDI &Bar Code Specification from your Indirect Purchasing contact.Caterpillar is committed to supporting and using the AutomotiveIndustry Action Group/American National Standards Institute (AIAG/ANSI)X12 national standards. However, the standards are broad in scope andflexible in methods of implementing. These are the Caterpillarspecific requirements for the ASN.Any questions or concerns regarding the Caterpillar ASN system and/orCaterpillar's Electronic Data Interchange (EDI) communication networkmay be directed to:Caterpillar Inc.EDI Support Services - AD3321600 W. Washington StreetEast Peoria, IL 61630(800) 435-7334 Ext. 3(309) 675-0834For specific questions regarding Caterpillar's Bar Code labels, contact:D.L.(Joe) Burgess(309) 675-2360or800-435-7334, Ext. 44
REQUIRED CHANGES TO YOUR PROCEDURESAn ASN is a logical description of a shipment. It contains bothfreight and packing list data. It is intended to speed the receipt ofmaterial by eliminating manual data entry of receipt information.If Caterpillar requests an ASN with prices, four additional segmentscan be used to communicate data relative to prices. They are: 1) SLNSubline Item Detail segment for pricing quantity, unit of measure, anditem price; 2) PID Item Description segment for item description whenthere is no part number on the purchase order; 3) CUR currency segmentto communicate currency other than US dollars; and 4) the ITAAdditional Charge Price segment.To effectivly use the ASN data, the receiving clerk mustknow that ASN data exists. The clerk must also be able to tie thelogical ASN data with the physical shipment. The serial number fromthe bar coded label provides the ability to mechanically tie theshipment with the ASN. In some cases, the two must be "tied" togetherbefore the labels can be scanned.TO ALLOW PROPER IDENTIFICATION OF THE SHIPMENT WHENIT ARRIVES AT CATERPILLAR, THE ASN CONTROL NUMBER(SUPPLIER CODE AND SHIPMENT IDENTIFICATION NUMBER-SID)MUST BE CLEARLY IDENTIFIED WHEN THE SHIPPING DOCUMENTSARRIVE. TO DO THIS, THE ATTACHED SHEET MUST BECOMPLETED AND SENT WITH THE SHIPMENT DOCUMENTATION.ATTENTION CARRIER/DRIVER:---------------------------THIS SHEET MUST ACCOMPANY THE SHIPMENT(FREIGHT BILL) DELIVERED TO CATERPILLAR.ASN CONTROL NUMBERSUPPLIER CODESHIPMENT IDENTIFICATION NUMBER (SID)5
ASN SYSTEM TERMS AND DEFINITIONSSee examples of pallets and cartons on the next page.(A) SHIPPING PACK. A container used for shipping items from onepoint to another.(B) MIXED ITEM PACK. A pack containing items with different part/itemnumbers.(C) MULTIPLE PACK. A pack containing smaller packages (subpacks) ofitems.(D) SUBPACKOne of the smaller packs within a larger multiple pack.(E)(F)(G)SHIPPING/PART IDENTIFICATION LABEL. A label used to identify thecontents of a shipping pack. This label is bar coded perCaterpillar Standard Practice 20 (Finished Material) or 21(Primary Metals). These Caterpillar practices are based on theAIAG bar code standards AIAG-B-3 and AIAG-B-5, respectively. Thelabel has a unique number which provides pack traceability. Thelabel identifies the supplier, purchase order number, ident numberand quantity.MASTER LABEL. A label used to identify and summarize the totalcontents of a multiple pack. This label is bar coded perCaterpillar Standard Practice 20 which is based on AIAG bar codestandard AIAG-B-3. The label has a unique number which providespack traceability. The label identifies the supplier, purchaseorder number, ident number contained in the common item subpacks,and the total quantity of that ident number in the multiple pack.MIXED LOAD LABEL. A label used to designate mixed item shippingpacks. This label is bar coded per Caterpillar Standard Practice20 which is based on AIAG bar code standard AIAG-B-3. The labelhas a unique number which provides pack traceability. The labelidentifies the suplier. 7h8872 S26341 (E) SHIPPING/PART IDENTIFICATION LABEL 1A0001 1A0001 1A0001 1A0001 S28931 S28932 S28933 S28934 (E) (D) MASTER LABEL (F) 1A0001 --------------- -------- 4S678234 --------- --------------- 1A0001 1A0001 1A0001 S28935 S28936 S28937 S28938 6
1A0002 1A0002 3P3492 3P3492 S28781 S28782 S28883 S28884 (E) (D) (G) MIXED LOAD --------------- --------- 5S993454 ---------- --------------- 8M1948 8 7Z0023 3P3492 S28964 S28963 S28882 S28794 7
BAR CODE SERIAL NOS. AND RELATED QTYSIn order for Caterpillar to efficiently receive material, the ASNshipment data must be "tied" to the physical material. This is donethrough the use of Caterpillar bar coded shipping labels. By passingthe unique serial number from the bar code label with the ASN partnumber data, the Caterpillar receiving system can find thecorresponding ASN data when that label is physically scanned.The receiving system is designed to only scan the "high level" shippinglabels. That means when an item is shipped on a container with a mixedor master label, the serial numbers from the subpacks should not besent.Caterpillar also needs to know the quantity of items associated withthe bar code label serial number. This information is passed in theASN by using a CLD segment. The serial number is then passed in theREF segment in the CLD loop (after the CLD segment). The followingrules are used to determine when a CLD segment is required.1. A "CLD" customer load detail segment is required for each load thatvaries by quantity. This means a shipment containing two palletsof the same item, one pallet containing three cartons for a totalquantity on the pallet of 150 pieces and the other palletcontaining 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 sameitem with the same total quantity, the "CLD" data can becombined 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 timesNUMBER OF LOADS) must equal the accumulated "SN1" QUANTITY SHIPPED.The following examples show the LIN, SN1, CLD, and REF segments thatwould be used to describe the shipment. In these examples, each boxcontains 50 pieces.SEGMENT DATA 1A1 1A1 1A1 1A1 1A1 1A1 1A1 1A1 MSTR-1@EXAMPLE #1EXAMPLE #2 1A1 1A1 1A1 1A1 1A1 MSTR-2@REF*LS*MSTR-3@EXAMPLE #3 1A1 1A1 *MSTR-4@CLD*1*100@REF*LS*MSTR-5@
2A1 2A1 3A1 1A1 1A1 1A1 1A1 1A1 1A1 1*50@REF*LS*MIXED1@EXAMPLE #4EXAMPLE #5 1A1 1A1 *MSTR-6@CLD*2*50@REF*LS*SERL-1@REF*LS*SERL-2@
USE OF INDUSTRY IDENTIFICATION VALUESIn an attempt to standardize as much as possible with the automotiveindustry, Caterpillar will use industry standard identificationconventions, whenever possible. This includes use of ZIP codes toidentify "ship from" locations, and use of the SCAC code (StandardCarrier Alphabetic Code) for identifying the carrier. A list ofcommonly used carriers is included in APPENDIX. Other carrier codesmay be obtained from Caterpillar.DUNS numbers must be used in the ISA record to identify the receiver.With the DUNS number, all hyphens must be eliminated The two digitCaterpillar facility code must also be included as a suffix to the DUNSnumber to identify the receiving facility, again with no hyphens.10
GENERAL COMMUNICATION FORMATA COMMUNICATION SESSION is the uninterrupted flow of data transferredbetween two independent computer systems. Transaction data that istransferred during a communication session is contained in disciplineddata segments as defined by the ANSI standard. Each segment has aspecific function. Some provide controls in the form of header andtrailer records while others pass the actual data.There are three levels of control used in electronic transmissions asdefined by ANSI. They are:1. INTERCHANGE CONTROL. These segments define the electronicenvelope. They identify the sender and the receiver of thedata. For outgoing transmissions, there is one set ofinterchange control records ('ISA' and 'IEA') for eachCaterpillar facility to which you are sending data. Forincoming data, there will be one set of interchange controlrecords for each transmission sent to you. MultipleINTERCHANGE CONTROL records may exist in the same transmissionif you are communicating to more than one Caterpillar facilityor if data has been sent to your mailbox more than once.2. FUNCTIONAL GROUPS. These separate documents in the envelope byfunction. You might think of a functional group as asubgrouping within the envelope. All purchase order documentsare in one group (purchase orders, releases, acknowledgments,etc.), invoice data is in another group, and ship notice datain still another group. There are plans to send variousdocuments to you and receive data from you via the EDI network.The different types of documents can be grouped within the sameelectronic envelope by using multiple functional groups.Normally, however, there will be only one functional group('GS' and 'GE') per envelope.TRANSACTION SETS. These define the electronic document, beingcommunicated. There is a transaction set header and trailersegment ('ST' and 'SE') for each document controlled by aunique control number. There may be multiple transaction setswithin the same functional group.The following examples show how these levels of control are appliedin a normal communication session.A communication session sending data to TWO facilities is picturedbelow. In this session TWO documents are being transferred to thefirst facility and ONE document to the second.-------- INTERCHANGE CONTROL HEADER (ISA) --------- FUNCTIONAL GROUP HEADER (GS)F A --------- TRANSACTION SET HEADER (ST)C TRANS.I SETDOCUMENT DATA (.)L I INTERCHANGE FUNCTIONAL--------- TRANSACTION SET TRAILER (SE)T ENVELOPE GROUPY --------- TRANSACTION SET HEADER (ST) TRANS. SETDOCUMENT DATA (.)11
ONEFACILITYTWO --------- TRANSACTION SET TRAILER (SE) --------- FUNCTIONAL GROUP TRAILER (GE) -------- INTERCHANGE CONTROL TRAILER (IEA)-------- INTERCHANGE CONTROL HEADER (ISA) --------- FUNCTIONAL GROUP HEADER (GS) --------- TRANSACTION SET HEADER (ST) INTERCHANGE FUNCTIONAL TRANS. ENVELOPE GROUP SETDOCUMENT DATA (.) --------- TRANSACTION SET TRAILER (SE) --------- FUNCTIONAL GROUP TRAILER (GE) -------- INTERCHANGE CONTROL TRAILER (IEA)12
SEGMENT FUNCTIONS AND ARRANGEMENTSVarious records are used to communicate ship notices. Following areexplanations of these records in the order they are sent in acommunication session.The INTERCHANGE CONTROL HEADER consists of one segment labeled withthe identifier 'ISA'. This is the first record in the electronicenvelope. The purpose of this segment is to identify and start aninterchange of one or more types of information. When we encounterthis segment, it is like opening an envelope. The envelopeidentifies the sender and receiver of the data as well as informationneeded in order to mechanically interrogate the data being sent (dataelement separators and segment terminators). If you are sending datato more than one Caterpillar facility, you must create an interchangecontrol header for each facility to which you are sending ship noticeinformation.The FUNCTIONAL GROUP HEADER consists of one segment labeled withidentifier 'GS'. The purpose of this segment is to subdivide thecontents of the interchange (envelope) into related groups (types ofdocuments). It allows the sender and receiver to be further defined,as these may vary within the sending and receiving locations by thedifferent types of documents. In addition, it defines the documentsthat are grouped together. Each type of document being communicated,such as ship notices or invoices, has its own functional group headersegment. In most cases you only send one type of document andtherefore only use one 'GS' per envelope.The TRANSACTION SET HEADER consists of one segment labeled with theidentifier 'ST'. The purpose of this segment is to identify the startof a document contained in a functional group. In this case thatdocument is a ship notice. You must send a transaction set headerwith each document being communicated. For example, if you arecommunicating information about three different shipments to the sameCaterpillar facility, all would be in the same envelope but eachwould have its own 'ST'.The DOCUMENT DATA consists of several different segments labeled withvarious identifiers. These segments contain specific information aboutthe document being communicated, the ship notice. Examples ofinformation included in these segments are the supplier code, shipmentidentification number (SID), part number, ship date, arrival date,shipment quantities, and summary counts. Each of these segments isdescribed in detail in the "Segment Layout/Data Element Definition"section of this document.The TRANSACTION SET TRAILER consists of one segment labeled with theidentifier 'SE'. You must provide one of these segments for eachcorresponding transaction set header segment 'ST'. The trailersegment contains control information pertaining to the transaction set.It also indicates the end of the transaction set (ship notice document)for which information is being transmitted. We will use data in thissegment to verify that no data pertaining to a document was droppedduring a transmission. See "Controls Required by ANSI" in thisdocument to determine how the controls work.The FUNCTIONAL GROUP TRAILER consists of one segment labeled with theidentifier 'GE'. You must provide one of these segments for eachcorresponding functional group header segment 'GS'. The trailersegment contains control information pertaining to the functional groupas well as indicating the end of a group of documents. Data in this13
segment is used by us to verify that we received all documents youtransmitted. See "Controls Required by ANSI" in this document todetermine how the controls work.The INTERCHANGE CONTROL TRAILER consists of one segment labeled withthe identifier 'IEA'. There is one for each interchange control headersegment 'ISA'. This segment contains control information about theinterchange as well as indicating the end (bottom) of the envelope. Weuse data in this segment to verify that all functional groups werereceived. See "Controls required by ANSI" in this document todetermine how the controls work.Within the ship notice transaction set are several segments whichcontain the ship notice data. These segments were earlier referred toas DOCUMENT DATA. When looking at a shipment of material, data mayapply to the entire shipment (such as the shipment arrival date), or asingle packing list entry (such as the quantity of a given item beingsent). Sometimes the same type of data applies differently todifferent shipments. For example, a purchase order number may apply toan entire shipment or to only one item within the packing list.14
EXPLANATION OF ANSI LEVELSIn order to keep track of where ship notice data applies, ANSIdeveloped a hierarchical level concept for passing data. Thehierarchical levels that have been defined by ANSI are as follows:SHIPMENTThis includes data that applies to the total shipment,such as the shipment identification number (SID), number ofshipping containers, and supplier code. There is only oneshipment level per transaction set ('ST'-'SE').EQUIPMENTThis includes data that is unique to the deliveryequipment. It is not used by Caterpillar.ORDERTAREKITITEMThis includes data that applies to all shipments for aparticular order.- OR This level is used to describe the physical configurationof the shipment. The TARE level includes data unique to amultiple pack such as the master label number and containerdescription. Caterpillar does not require configurationdata and therefore does not recommend using the TARE level.This includes data that is unique to a kit where the itemswithin the kit are identified. The kit level is not usedby Caterpillar.This includes data that is unique to the item such as itemidentification (part number), quantity shipped, andpurchase order number. There is an item level for each itemcontained in the shipment.Multiple item levels for the same part may be required if:- the part is being shipped against multiple purchaseorders (An item level is required for each P/O)- an item is being shipped on multiple packing lists andthe unique packing list number is identified on theinvoice sent to Caterpillar (This may be required forinvoice matching)PACKSUBPACKThis includes data that is unique to the pack (carton).The PACK level, like the TARE level, is used to conveyconfiguration data. Caterpillar does not requireconfiguration data and therefore does not recommend usinga PACK level.This includes data that is unique to the subpack. Asubpack is a grouping within the pack. (For example, apack of cigarettes is a subpack of a carton of cigarettes.)An example of this type of data is package quantity if itvaries by subpack. Caterpillar has not identified a needfor the subpack level.All of the levels have a definite hierarchical sequence. This sequenceis: SHIPMENT, EQUIPMENT, ORDER, TARE, KIT, ITEM, PACK, SUBPACK.Not all these levels apply to Caterpillar shipments. The levelsrecommended for use by Caterpillar are: SHIPMENT and ITEM.There are other rules regarding the arrangement of the various levels.They are: there must be only one shipment level; it must be the15
highest level; and an item level is required for each packing listentry. (A packing list entry represents a unique part number/purchaseorder/packing list number combination.)The following sequence of levels applies to Caterpillar shipments:SHIPMENT. Always the first segment.ITEM. An item level must be passed for every packing list lineitem, even if there is only one item in the shipment.16
TRANSACTION SEQUENCE WITHIN THE LEVELThe transaction set has been broken down into three different areas:header data, detail data, and summary data. The header data identifiesthe transaction set being passed and gives the shipment control number.The detail data identifies data related to the shipment by level. Thesummary data provides control information to insure all data wassuccessfully received.As stated earlier, the detail data is made up of several hierarchicallevels of data related to a specific aspect of the shipment. In thecase of Caterpillar these levels will normally be: SHIPMENT and ITEMWithin each level of detail data there is also a sequence of segments.In order to make the ship notice standard meet everyone's needs, ANSIincluded some segments not used by everyone. In this document we areonly concerned with the segments required by Caterpillar. The sequenceof the segments within each level appear on the next page. Not allsegments apply to each level.-------------------------HEADER DATA --------------------------ST TRANSACTION SET HEADERBSN BEGINNING SEGMENT (SHIP NOTICE)DTM DATE/TIME REFERENCE------------------- LEVEL DATA (DETAIL DATA) ------------------HL HIERARCHICAL LEVEL SPECIFICATIONLIN LINE ITEM DETAILSN1 ITEM SHIPMENT DETAILSLN SUBLINE ITEM DETAIL (PRICES)PID ITEM DESCRIPTIONPRF PURCHASE ORDER REFERENCEMEA MEASUREMENTSREF REFERENCE NUMBERS (PACKING LIST NUMBER)TD1 CARRIER DETAILSTD5 CARRIER DETAIL (ROUTING -------------- LOOP ------- TD3 CARRIER DETAIL (EQUIPMENT) -------------------------REF REFERENCE NUMBERSCLD CUSTOMER'S LOAD DETAIL ---------------- LOOP ------- REF REFERENCE NUMBERS ----------------------------------FOB FOB RELATED INSTRUCTIONSN1 NAMECUR CURRENCYITA ADDITIONAL CHARGES------------------- SUMMARY DATA ------------------------------------CTT TRANSACTION TOTALSSE TRANSACTION SET TRAILERFollowing are the segments used by Caterpillar and the levels wherethese segments normally apply. Some data, such as packing list dataand some reference data, may apply at other levels even though it isshown here under the item level.LEVELHEADERTYPESTDATA CONTAINED IN THE SEGMENTCONTROL DATA17
BSNASN CONTROL NUMBER AND DOCUMENT CREATION DATE/TIMEDTMSHIP AND ARRIVAL DATES AND ------------------------SHIPMENTHLLEVEL INDICATION DATAMEATRAFFIC WEIGHTSTD1SHIPPING CONTAINER DESCRIPTIONS AND QUANTITIES CARRIER DETAILS LOOP TD5CARRIER CODE, SEQUENCE AND METHOD OF SHIPMENT TD3CARRIER VEHICLE NUMBERREFCARRIER'S PRO NUMBER, AUTHORIZATION, INVOICE NUMBERS,FOBMETHOD OF PAYING FOR SHIPMENTN1CATERPILLAR ASSIGNED SUPPLIER CODEN1SUPPLIER COUNTRY CODEN1ASN FACILITYN1SHIPPING POINTS POSTAL ZIP CODEITEMHLLEVEL INDICATION DATALINIDENTIFICATION CODES (PART NO., ENGRG CHG NO.,VENDER'S CATALOG NO. ETC.)SN1UNITS SHIPPEDSLNPRICE PER UNITPRFPURCHASE ORDER DATAPIDITEM DESCRIPTIONREFPACKING LIST NUMBER, FORGER CODE, HEAT CODE CATERPILLAR'S STORAGE LOAD INFORMATION LOOP CLDNUMBER OF STORAGE LOADS AND QUANTITY PER LOAD TYPE OF CONTAINER AND SUBPACK QUANTITY REFPRODUCT SERIAL NUMBER OR SHIPPING LABEL NUMBER AND/OR NEXT LOAD'S FORGER AND/OR NEXT LOAD'S HEAT CODECURCURRENCY FOR PAYMENT OF ITEMITAADDITIONAL CHARGES RELATING TO ------------------------CONTROLCTTTRANSACTION HASH TOTALS AND ITEM COUNTSSETRANSACTION SET TRAILER18
CONTROLS REQUIRED BY ANSISEGMENT SEQUENCE REQUIREMENTS1. 'ISA' must be the first record or preceded by 'IEA'.2. 'IEA' must be the last record for each facility receiving data.3. 'GS' must be preceded by 'ISA' or 'GE'.4. 'ST' must be preceded by 'GS' or 'SE'.5. 'GE' must be preceded by 'SE'.6. 'IEA' must be preceded by 'GE'.7. The interchange control number in 'IEA' (field IEA02) must be thesame as the previous 'ISA' (field ISA13).8. The data interchange control number in 'GE' (field GE02) must be thesame as the previous 'GS' (field GS06).9. The transaction set control number in 'SE' (field SE02) must be thesame as the previous 'ST' (field ST02).REQUIRED CONTROL COUNTS1. The 'number of included functional groups' in 'IEA' (field IEA01)must equal the number of 'GS' records since the previous 'ISA'.2. The 'number of included transaction sets' in 'GE' (field GE01)must equal the number of 'ST' records since the previous 'GS'.3. The 'number of included segments' in 'SE' (field SE01) must equalthe number of records read since the previous 'ST'. The 'ST' and'SE' records are included in this count.4. The 'quantity hash total' in 'CTT' (field CTT02) must equal thesum of the 'number of units shipped' field in the 'SN1' records(field SN102). Only 'SN1' records since the previous 'ST' are tobe included in the summarization.19
EXPLANATION ON DATA SEGMENT LAYOUTSThe following pages give a layout of all the ANSI records Caterpillaruses in transferring ship notice data. They are in alphabetic sequenceby transaction type.The '@' at the end of each record represents the segment terminator.This segment terminator is defined in the 'ISA' record. EDI*EXPRESSrequires the terminator to be a hexadecimal '0D'.The '*' between each field represents the field separator. The fieldseparator is defined in the 'ISA' record. As with the segmentterminator, any character may be used as a separator unless it is alsocontained in the data being sent.The next page shows an explanation of the data segment layoutscontaining ship notice data to be sent to Caterpillar.(1)(2)NOTES SEGMENT (SHIPMENT AND/OR ITEM LEVELS)(3)(4)NTE*ZZZ*ANY NOTES PERTINENT TO THE PACKING LIST ITEMS@ (ITEM LEVEL)ABC IDENTIFIES 'NOTE' TYPE DATA PERTAINING TO THE PURCHASE (5) ORDER. THERE ARE SEVERAL TYPES OF DATA CAN BE CONVEYED BY THIS TRANSACTION WHICH IS IDENTIFIED BY THE REFERENCE CODE. ANSIFIELD REFERENCECHARACTERISTICSDESCRIPTION A. NTE(AN-3)REQUIREDDATA SEGMENT IDENTIFIER (6)(7)(8)(9)(10) B. NTE01 363(ID-3)REQUIRENOTE REFERENCE CODE ZZZ MUTUALLY DEFINED (11) C. NTE02 3(AN-60) REQUIREDFREE FORM NOTES NOTE: THE NTE SEGMENT IS USED TO PASS DATA THAT IS INTENDED TO BE READ BY HUMANS. IN A MECHANIZED ENVIRONMENT, SUCH AS (12) CATERPILLAR'S ASN, THIS DATA MAY NEVER BE SEEN. ITS USE SHOULD BE AVOIDED IF AT ALL POSSIBLE. DESCRIPTION OF NOTES(1) ANSI segment name(2) Levels to which this segment can apply(3) Layout of the segment fields(
electronic Advance Ship Notice (ASN) transaction set 856 to satisfy Caterpillar's requirements. A ZWIP-specific document is available for suppliers sending advance ship notices under the ZWIP program. You can obtain the ZWIP
Jun 03, 2020 · 856 advance ship notice ansi x12 4010 this document has many updates, please review all segments and elements *notes: please reference 1 po per 856 transaction set (st-se envelope). the 856 should be sent the same day the order is shipped. make sure all ship quantities on the 856 are in the
EDI 856 Implementation Guide, version 4010 Document Status Document Number KB toys 856 4010 IG 2_4 Version 2.4 File Name Advance Ship Notice 856 – EDI Implementation Guide Issue Date May 21, 2003 Owner Cathy Covell Description An EDI Implementation Guide for KB toys Advance Ship Notice. Document Revision History
EDI 856 Advance Ship Notice Best Practices and Common Errors 1 October/2020 856 Advance Ship Notice Best Practices and Common Errors The 856 ASN tells us: when the order will be shipped, which items are being shipped, how much of each item
13- WHEEL LOADERS: 2- 2014 Caterpillar 966K 2- 2014 Caterpillar 950K 2013 Caterpillar 950K 2- Caterpillar 950G John Deere 544C Kawasaki 50ZV Komatsu WA900-3LC Komatsu WA500-3L 2011 Komatsu WA430-6 Samsung SL150. CRAWLER LOADERS: Caterpillar 973 2008 Caterpillar 939C.
20- CRAWLER TRACTORS: 2- Case 850K 2- Caterpillar D10R Cat - erpillar D8N Caterpillar D6R 2013 Caterpillar D6N LGP 2015 & 2014 Caterpillar D6K2 LGP Caterpillar D6K2 LGP 2012 Caterpillar D5K2 XL Caterpillar D5H Caterpillar D5G 2014 John Deere 650K
Apr 01, 2008 · Ship Notice/Manifest - 856 856 Ship Notice/Manifest Functional Group SH This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Int
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)
Basic competences for humanistic counselling with young people: skills that are fundamental to humanistic counselling. 4. Specific competences for humanistic counselling with young people: skills that are practised in some, but not necessarily all, cases, depending on how and what the young person presents in therapy. 5.
