856 Ship Notice/Manifest - Suppliers

856 Ship Notice/ManifestFunctional Group ID=SHTransaction Layout:Heading:ARM Pos. Seg. Req. Loop Notes andReq. No. ID Name Des. Max.Use Repeat ExamplesRequired 010 ST Transaction Set Header M 1Required 020 BSN Beginning Segment for Ship Notice M 1Required 030 DTM Date/Time Reference O 10Detail:Pos. Seg. Req. Loop Notes andNo. ID Name Des. Max.Use Repeat ExamplesLOOP ID - HL 200000Required 010 HL Hierarchical Level M 1 c1Required 020 MEA Measurements O 40Required 030 TD1 Carrier Details (Quantity and Weight) O 20Required 040 TD5 Carrier Details (Routing Sequence/Transit O 12Time)Required 050 TD3 Carrier Details (Equipment) O 12Required 060 REF Reference Identification O >1LOOP ID - N1 200Required 070 N1 Name O 1LOOP ID - SAC >1140 SAC Service, Promotion, Allowance, or ChargeInformationO 1LOOP ID - HL 200000Required 160 HL Hierarchical Level M 1 c2Required 170 LIN Item Identification O 1Required 180 SN1 Item Detail (Shipment) O 1Required 200 PRF Purchase Order Reference O 1LOOP ID - CLD 200380 CLD Load Detail O 1Required 390 REF Reference Identification O 200Summary:Pos. Seg. Req. Loop Notes andNo. ID Name Des. Max.Use Repeat ExamplesRequired 010 CTT Transaction Totals O 1 n1Required 020 SE Transaction Set Trailer M 1ArvinMeritor Segment/Element Usage NotesMay 13, 2004ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, Inc1. For Segment requirements, refer to the column titled “ARM Req.” in the table above for those segments thatare required in the transaction.2. For Element requirements, refer to the column titled “ARM Req.” in the element tables for each segmentdetailed in the pages that follow. If the segment is used, then these elements are required.Segment: ST Transaction Set HeaderPosition: 010Loop:Level: HeadingUsage: MandatoryMax Use: 1Purpose: To indicate the start of a transaction set and to assign a control numberSemantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of theinterchange partners to select the appropriate transaction set definition (e.g., 810selects the Invoice Transaction Set).Examples:ST*856*12341~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired ST01 143 Transaction Set Identifier Code M ID 3/3Code uniquely identifying a Transaction SetRefer to 004010 Data Element Dictionary for acceptable code values.Required ST02 329 Transaction Set Control Number M AN 4/9Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setMay 13, 2004 2 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: BSN Beginning Segment for Ship NoticePosition: 020Loop:Level: HeadingUsage: MandatoryMax Use: 1Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction setSemantic Notes: 1 BSN03 is the date the shipment transaction set is created.2 BSN04 is the time the shipment transaction set is created.Examples:BSN*00*776655*20030301*1614~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired BSN01 353 Transaction Set Purpose Code M ID 2/2Code identifying purpose of transaction set00 Original01 CancellationRequired BSN02 396 Shipment Identification M AN 2/30A unique control number assigned by the original shipper to identify a specificshipmentUnique supplier assigned Shipment ID Number (SID) that is not repeatedwithin a one-year period. This number will be the key identifying number forreconciliation of payments.Required BSN03 373 DateDate expressed as CCYYMMDDM DT 8/8Local ASN creation date.Required BSN04 337 TimeTime expressed in 24-hour clock time as follows: HHMMM TM 4/8Local ASN creation time.May 13, 2004 3 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: DTM Date/Time ReferencePosition: 030Loop:Level: HeadingUsage: OptionalMax Use: 10Purpose: To specify pertinent dates and timesSyntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required.2 If DTM04 is present, then DTM03 is required.Examples:DTM*011*20030301*1614*ED~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired DTM01 374 Date/Time Qualifier M ID 3/3Code specifying type of date or time, or both date and time011 ShippedRequired DTM02 373 DateDate expressed as CCYYMMDDX DT 8/8The local shipment date.Required DTM03 337 TimeTime expressed in 24-hour clock time as follows: HHMMX TM 4/8The local shipment time.Required DTM04 623 Time CodeCDCentral Daylight TimeO ID 2/2CSCentral Standard TimeCTCentral TimeEDEastern Daylight TimeESEastern Standard TimeETEastern TimeGMGreenwich Mean TimeMDMountain Daylight TimeMSMountain Standard TimeMTMountain TimePDPacific Daylight TimePSPacific Standard TimePTPacific TimeMay 13, 2004 4 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: HL Hierarchical LevelPosition: 010Loop: HL MandatoryLevel: DetailUsage: MandatoryMax Use: 1Purpose: To identify dependencies among and the content of hierarchically related groups of datasegmentsSemantic Notes: 1 The HL segment is used to identify levels of detail information using a hierarchicalstructure, such as relating line-item data to shipment data, and packaging data to lineitemdata.The HL segment defines a top-down/left-right ordered structure.2 HL01 shall contain a unique alphanumeric number for each occurrence of the HLsegment in the transaction set. For example, HL01 could be used to indicate thenumber of occurrences of the HL segment, in which case the value of HL01 wouldbe "1" for the initial HL segment and would be incremented by one in eachsubsequent HL segment within the transaction.3 HL02 identifies the hierarchical ID number of the HL segment to which the currentHL segment is subordinate.4 HL03 indicates the context of the series of segments following the current HLsegment 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 logicalgrouping of data referring to shipment, order, or item-level information.Examples:HL*1**S~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired HL01 628 Hierarchical ID Number M AN 1/12A unique number assigned by the sender to identify a particular data segmentin a hierarchical structure"1" in the initial HL segment, incrementing by 1 each subsequent HL segmentwithin the transaction.HL02 734 Hierarchical Parent ID Number O AN 1/12Identification number of the next higher hierarchical data segment that the datasegment being described is subordinate toRequired except for Shipment levelRequired HL03 735 Hierarchical Level Code M ID 1/2Code defining the characteristic of a level in a hierarchical structureSShipmentMay 13, 2004 5 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: MEA MeasurementsPosition: 020Loop: HL MandatoryLevel: DetailUsage: OptionalMax Use: 40Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances,and weights (See Figures Appendix for example of use of C001)Semantic Notes: 1 MEA04 defines the unit of measure for MEA03.Examples:MEA*PD*G*15000*LB~MEA*PD*N*14000*LB~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired MEA01 737 Measurement Reference ID Code O ID 2/2Code identifying the broad category to which a measurement appliesPDPhysical DimensionsRequired MEA02 738 Measurement Qualifier O ID 1/3Code identifying a specific product or process characteristic to which ameasurement appliesGGross WeightNActual Net WeightRequired MEA03 739 Measurement ValueThe value of the measurementX R 1/20MEA04 C001 Composite Unit of Measure XTo identify a composite unit of measure (See Figures Appendix for examplesof use)Required C00101 355 Unit or Basis for Measurement Code M ID 2/2Code specifying the units in which a value is being expressed, or manner inwhich a measurement has been takenLBPoundMay 13, 2004 6 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: TD1 Carrier Details (Quantity and Weight)Position: 030Loop: HL MandatoryLevel: DetailUsage: OptionalMax Use: 20Purpose: To specify the transportation details relative to commodity, weight, and quantitySyntax Notes: 1 If TD101 is present, then TD102 is required.Examples:Notes:TD1*BOX25*12~TD1*PLT90*3~Required by ArvinMeritor at the Shipment level to indicate the total number of higherlevel packages (pallets, skids, etc.) on the shipment.Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired TD101 103 Packaging Code O AN 3/5Code identifying the type of packaging; Part 1: Packaging Form, Part 2:Packaging Material; if the Data Element is used, then Part 1 is always requiredBOX BoxCOL CoilCTN CartonMIX Mixed Container TypesMore than one type of container is included in ashipment (shipment could consist of 3 pieces thatinclude 1 box, 1 crate, and 1 basket)PLTPallet25 Corrugated or Solid52 Iron or Steel70 Multiple-wall Paper (3 or more walls)71 Not otherwise specified90 StandardRequired TD102 80 Lading QuantityNumber of units (pieces) of the lading commodityX N0 1/7May 13, 2004 7 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: TD5 Carrier Details (Routing Sequence/Transit Time)Position: 040Loop: HL MandatoryLevel: DetailUsage: OptionalMax Use: 12Purpose: To specify the carrier and sequence of routing and provide transit time informationSyntax Notes: 1 At least one of TD502 TD504 TD505 TD506 or TD512 is required.2 If TD502 is present, then TD503 is required.3 If TD507 is present, then TD508 is required.Examples:TD5*B*2*RDWY*M*Roadway~TD5*B*2*BAXN*AE*BAX Global**OR*DTW~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired TD501 133 Routing Sequence Code O ID 1/2Code describing the relationship of a carrier to a specific shipment movementBOrigin/Delivery Carrier (Any Mode)Required TD502 66 Identification Code Qualifier X ID 1/2Code designating the system/method of code structure used for IdentificationCode (67)2 Standard Carrier Alpha Code (SCAC)Required TD503 67 Identification CodeCode identifying a party or other codeX AN 2/80Valid, mutually agreed SCAC CodeRequired TD504 91 Transportation Method/Type Code X ID 1/2Code specifying the method or type of transportation for the shipmentAAirAEAir ExpressDParcel PostEExpedited TruckLTLess Than Trailer Load (LTL)MMotor (Common Carrier)OContainerized OceanRRailTD505 387 Routing X AN 1/35Free-form description of the routing or requested routing for shipment, or theoriginating carrier's identityCarrier Text NameTD507 309 Location Qualifier O ID 1/2Code identifying type of locationOROrigin (Shipping Point)PEPort of Entry (Port where customs is declared)PPPool PointTD508 310 Location Identifier X AN 1/30Code which identifies a specific locationIf TD507 = "PP" use pool point shown on Supplier Routing Instructions. IfTD507 = "OR" use originating airport code from airbill.May 13, 2004 8 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: TD3 Carrier Details (Equipment)Position: 050Loop: HL MandatoryLevel: DetailUsage: OptionalMax Use: 12Purpose: To specify transportation details relating to the equipment used by the carrierSyntax Notes: 1 If TD302 is present, then TD303 is required.Examples:TD3*TL**878787~TD3*RR**32483243598~TD3*AF**101~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired TD301 40 Equipment Description Code X ID 2/2Code identifying type of equipment used for shipmentUse any valid code from the ANSI X12 v4010 dictionary.TD302 206 Equipment Initial O AN 1/4Prefix or alphabetic part of an equipment unit's identifying numberUse alpha portion of the Equipment IDRequired TD303 207 Equipment Number X AN 1/10Sequencing or serial part of an equipment unit's identifying number (purenumeric form for equipment number is preferred)Trailer number, Flight number, or Railcar numberMay 13, 2004 9 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: REF Reference IdentificationPosition: 060Loop: HL MandatoryLevel: DetailUsage: OptionalMax Use: >1Purpose: To specify identifying informationSyntax Notes: 1 At least one of REF02 or REF03 is required.Examples:REF*CN*230985302432823~REF*BM*778899~REF*AW*23890EW-23482~Notes: At least one REF segment is required for the Bill of Lading. If the shipment is via Air,then a REF*AW is required. REF*DK is required if the dock code is included in the 830or 862 transaction.Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired REF01 128 Reference Identification Qualifier M ID 2/3Code qualifying the Reference IdentificationAWAir Waybill NumberBMBill of Lading NumberCNCarrier's Reference Number (PRO/Invoice)DKDock NumberFRFreight Bill NumberKBBeginning Kanban Serial NumberKEEnding Kanban Serial NumberMBMaster Bill of LadingSIShipper's Identifying Number for Shipment (SID)A unique number (to the shipper) assigned by theshipper to identify the shipmentRequired REF02 127 Reference Identification X AN 1/30Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierMay 13, 2004 10 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: N1 NamePosition: 070Loop: N1 OptionalLevel: DetailUsage: OptionalMax Use: 1Purpose: To identify a party by type of organization, name, and codeSyntax 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: 1 This segment, used alone, provides the most efficient method of providingorganizational identification. To obtain this efficiency the "ID Code" (N104) mustprovide a key to the table maintained by the transaction processing party.Examples:N1*SF*SCREWS-R-US*92*313131997~N1*ST*ARM-Tilbury*1*207558495~N1*SU*DANNY’S BOLTS*ZZ*V328328~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired N101 98 Entity Identifier Code M ID 2/3Code identifying an organizational entity, a physical location, property or anindividualSFShip FromSTShip ToSUSupplier/ManufacturerN102 93 Name X AN 1/60Free-form nameRequired N103 66 Identification Code Qualifier X ID 1/2Code designating the system/method of code structure used for IdentificationCode (67); use the code supplied in the 830 or 862 document.1 D-U-N-S Number, Dun & Bradstreet12 Telephone Number (Phone)92 Assigned by Buyer or Buyer's AgentZZMutually DefinedRequired N104 67 Identification Code X AN 2/80Code identifying a party or other code; see Appendix X. for a list of ARMShip-to codes.May 13, 2004 11 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: SAC Service, Promotion, Allowance, or Charge InformationPosition: 140Loop: SAC OptionalLevel: DetailUsage: OptionalMax Use: 1Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amountor percentage for the service, promotion, allowance, or chargeSyntax Notes: 1 At least one of SAC02 or SAC03 is required.2 If either SAC03 or SAC04 is present, then the other is required.Semantic Notes: 1 If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.2 SAC05 is the total amount for the service, promotion, allowance, or charge.If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.Examples:SAC*C*D240***10217*******06~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired SAC01 248 Allowance or Charge Indicator M ID 1/1Code which indicates an allowance or charge for the service specifiedAAllowanceCChargeQCharge RequestSServiceRequired SAC02 1300 Service, Promotion, Allowance, or Charge Code X ID 4/4Code identifying the service, promotion, allowance, or chargeD240 FreightH550 SurchargeI260Transportation Direct BillingI500Vendor FreightRequired SAC05 610 AmountMonetary amountO N2 1/15Required SAC12 331 Allowance or Charge Method of Handling Code O ID 2/2Code indicating method of handling for an allowance or charge05 Charge to be Paid by Vendor06 Charge to be Paid by CustomerZZMutually DefinedMay 13, 2004 12 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: HL Hierarchical LevelPosition: 160Loop: HL MandatoryLevel: DetailUsage: MandatoryMax Use: 1Purpose: To identify dependencies among and the content of hierarchically related groups of datasegmentsSemantic Notes: 1 The HL segment is used to identify levels of detail information using a hierarchicalstructure, such as relating line-item data to shipment data, and packaging data to lineitemdata.The HL segment defines a top-down/left-right ordered structure.2 HL01 shall contain a unique alphanumeric number for each occurrence of the HLsegment in the transaction set. For example, HL01 could be used to indicate thenumber of occurrences of the HL segment, in which case the value of HL01 wouldbe "1" for the initial HL segment and would be incremented by one in eachsubsequent HL segment within the transaction.3 HL02 identifies the hierarchical ID number of the HL segment to which the currentHL segment is subordinate.4 HL03 indicates the context of the series of segments following the current HLsegment 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 logicalgrouping of data referring to shipment, order, or item-level information.Examples:HL*2*1*I~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired HL01 628 Hierarchical ID Number M AN 1/12A unique number assigned by the sender to identify a particular data segmentin a hierarchical structure"2" in the initial HL segment, incrementing by 1 each subsequent HL segmentwithin the transaction.Required HL02 734 Hierarchical Parent ID Number O AN 1/12Identification number of the next higher hierarchical data segment that the datasegment being described is subordinate toRequired at Item levelRequired HL03 735 Hierarchical Level Code M ID 1/2Code defining the characteristic of a level in a hierarchical structureIItemMay 13, 2004 13 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: LIN Item IdentificationPosition: 170Loop: HL MandatoryLevel: DetailUsage: OptionalMax Use: 1Purpose: To specify basic item identification dataSyntax Notes: 1 If either LIN04 or LIN05 is present, then the other is required.2 If either LIN06 or LIN07 is present, then the other is required.Examples: LIN**BP*243823-AOP*EC*D~LIN**BP*773245AH*RC*1001001~Notes:LIN03 must contain the ArvinMeritor part number. Vendor part number, EngineeringChange Level, or Returnable Container Code, may occur in LIN04/05, LIN06/07, orLIN08/09.Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired LIN02 235 Product/Service ID Qualifier M ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)BPBuyer's Part NumberRequired LIN03 234 Product/Service IDIdentifying number for a product or serviceM AN 1/48ArvinMeritor part number.LIN04 235 Product/Service ID Qualifier X ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)ECEngineering Change LevelRCReturnable Container NumberVPVendor's (Seller's) Part NumberLIN05 234 Product/Service ID X AN 1/48Identifying number for a product or serviceIf LIN04 = "VP", then this is the Vendor part number. If LIN04 = "EC", thenthis is the engineering change level. If LIN04 = "RC", then this is theReturnable Container Code.LIN06 235 Product/Service ID Qualifier X ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)LIN07 234 Product/Service ID X AN 1/48Identifying number for a product or serviceIf LIN06 = "VP", then this is the Vendor part number. If LIN06 = "EC", thenthis is the engineering change level. If LIN06 = "RC", then this is theReturnable Container Code.LIN08 235 Product/Service ID Qualifier X ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)LIN09 234 Product/Service ID X AN 1/48Identifying number for a product or serviceIf LIN08 = "VP", then this is the Vendor part number. If LIN08 = "EC", thenthis is the engineering change level. If LIN08 = "RC", then this is theReturnable Container Code.May 13, 2004 14 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: SN1 Item Detail (Shipment)Position: 180Loop: HL MandatoryLevel: DetailUsage: OptionalMax Use: 1Purpose: To specify line-item detail relative to shipmentExamples:SN1**12*EA*5638~SN1**436*LB~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired SN102 382 Number of Units Shipped M R 1/10Numeric value of units shipped in manufacturer's shipping units for a line itemor transaction setNumber of parts (quantity shipped) for the Buyer's Part indicated in the LINsegment.Required SN103 355 Unit or Basis for Measurement Code M ID 2/2Code specifying the units in which a value is being expressed, or manner inwhich a measurement has been takenRefer to the part unit of measure on your ArvinMeritor Purchase Order.SN104 646 Quantity Shipped to Date O R 1/15Number of units shipped to dateYTD cumulative for current model year.May 13, 2004 15 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: PRF Purchase Order ReferencePosition: 200Loop: HL MandatoryLevel: DetailUsage: OptionalMax Use: 1Purpose: To provide reference to a specific purchase orderSemantic Notes: 1 PRF04 is the date assigned by the purchaser to purchase order.Examples:PRF*V919304***20020131~PRF*G4514-0988***20030131*009~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired PRF01 324 Purchase Order Number M AN 1/22Identifying number for Purchase Order assigned by the orderer/purchaserArvinMeritor PO number including amendments.PRF04 373 DateDate expressed as CCYYMMDDO DT 8/8ArvinMeritor PO Date.PRF05 350 Assigned Identification O AN 1/20Alphanumeric characters assigned for differentiation within a transaction setPO Line NumberMay 13, 2004 16 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: CLD Load DetailPosition: 380Loop: CLD OptionalLevel: DetailUsage: OptionalMax Use: 1Purpose: To specify the number of material loads shippedSyntax Notes: 1 If CLD05 is present, then CLD04 is required.Semantic Notes: 1 CLD05 is used to dimension the value given in CLD04.Examples:CLD*4*3*BOX25~CLD*8*100*BOX25*25*EA~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired CLD01 622 Number of Loads M N0 1/5Number of customer-defined loads shipped by the supplierNumber of ContainersRequired CLD02 382 Number of Units Shipped M R 1/10Numeric value of units shipped in manufacturer's shipping units for a line itemor transaction setTotal number of units in container.Required CLD03 103 Packaging Code O AN 3/5Code identifying the type of packaging; Part 1: Packaging Form, Part 2:Packaging Material; if the Data Element is used, then Part 1 is always requiredBOX BoxCOL CoilCRT CrateCTN CartonLSELoosePLTPalletSKD Skid25 Corrugated or Solid52 Iron or Steel71 Not Otherwise Specified90 StandardRequired CLD04 357 SizeSize of supplier units in packX R 1/8Subpack quantity.Required CLD05 355 Unit or Basis for Measurement Code O ID 2/2Code specifying the units in which a value is being expressed, or manner inwhich a measurement has been takenUOM for subpack quantity. Use the same unit of measure as the SN1.May 13, 2004 17 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: REF Reference IdentificationPosition: 390Loop: CLD OptionalLevel: DetailUsage: OptionalMax Use: 200Purpose: To specify identifying informationSyntax Notes: 1 At least one of REF02 or REF03 is required.2 If either C04003 or C04004 is present, then the other is required.3 If either C04005 or C04006 is present, then the other is required.Semantic Notes: 1 REF04 contains data relating to the value cited in REF02.Examples:Notes:REF*PK*161188~REF*DK*G17~REF*KB*1231234~REF*KE*1231248~At least one REF segment with a "PK" qualifier (Packing Slip Number) is required at thislevel.Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired REF01 128 Reference Identification Qualifier M ID 2/3Code qualifying the Reference IdentificationDKDock NumberHCHeat CodeKBBeginning Kanban Serial NumberKEEnding Kanban Serial NumberLAShipping Label Serial NumberLSBar-Coded Serial NumberLTLot NumberPKPacking List NumberSESerial NumberRequired REF02 127 Reference Identification X AN 1/30Reference information as defined for a particular Transaction Set or asspecified by the Reference Identification QualifierMay 13, 2004 18 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: CTT Transaction TotalsPosition: 010Loop:Level: SummaryUsage: OptionalMax Use: 1Purpose: To transmit a hash total for a specific element in the transaction setSemantic Notes: 1 This segment is intended to provide hash totals to validate transaction completenessand correctness.Examples:CTT*7*56238~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired CTT01 354 Number of Line Items M N0 1/6Total number of line items in the transaction setTotal number of HL loops in transaction.CTT02 347 Hash Total O R 1/10Total number of parts in ASNMay 13, 2004 19 ANSI X12 856 v004010Released Version

Supplier EDI SpecificationArvinMeritor, IncSegment: SE Transaction Set TrailerPosition: 020Loop:Level: SummaryUsage: MandatoryMax Use: 1Purpose: To indicate the end of the transaction set and provide the count of the transmittedsegments (including the beginning (ST) and ending (SE) segments)Examples:SE*123*12341~Data Element SummaryARM Ref. DataReq. Des. Element Name AttributesRequired SE01 96 Number of Included Segments M N0 1/10Total number of segments included in a transaction set including ST and SEsegmentsRequired SE02 329 Transaction Set Control Number M AN 4/9Identifying control number that must be unique within the transaction setfunctional group assigned by the originator for a transaction setMay 13, 2004 20 ANSI X12 856 v004010Released Version