856 EDI SPECIFICATIONS VERSION 4010 - Iconnect-corp

Transcription

856 EDI SPECIFICATIONSVERSION 401011/19/2007Page 1 of 23Revision 2

Transaction Set HeaderSegment:ST - Transaction Set HeaderLevel:HeadingMax. Use:1Requirement: MandatoryPurpose:To indicate the start of the 856 transaction set and assign a transactioncontrol number.Comments:The transaction set control number (data element ST02) in the headermust match the transaction set control number in the trailer (data elementSE02).Example:ST*856*0001ELEM ELE# NAMEIDFEATURES COMMENTSST01143Transaction Set M ID 3/3Identifier Code856ST02329Transaction Set M AN 4/9ControlNumberA unique number assigned to eachtransaction set within a functionalgroup, starting with 0001 andincremented by 1 for each subsequenttransaction set.11/19/2007Page 2 of 23Revision 2

Beginning Segment for Ship NoticeSegment:BSN - Beginning Segment for Ship NoticeLevel:HeadingMax. Use:1Requirement: MandatoryPurpose:To transmit identifying numbers, dates and other basic data relating to thetransaction set.Example:BSN*00*123456*19990502*0810ELEM ELE# NAMEIDBSN01 353FEATURES COMMENTSTransaction Set M ID 2/2Purpose Code00 Original05 ReplacementBSN02 396ShipmentIdentificationM AN 2/30ASN Number—Unique supplierassigned number that is not repeatedwithin a one year period. InforAutomotive recommends use of theshipment ID number (SID).BSN03 373DateM DT 8/8Date of ASN Creation Format isYYYYMMDDBSN04 337TimeM TM 4/4Time of ASN Creation Format isHHMM11/19/2007Page 3 of 23Revision 2

Date/Time ReferenceSegment:DTM - Date/Time ReferenceLevel:HeadingMax. Use:2Requirement: DTM*011 Segment is MandatoryDTM*017 Segment is OptionalPurpose:To specify pertinent dates and times.Example:DTM*011*880601*1115 or DTM*011*880601*1115*PTDTM*017*880607*0800 or DTM*017*880607*2300*PTELEMIDELE# NAMEFEATURES COMMENTSDTM01374M ID 3/3Date/TimeQualifier011 Date and Time ShipmentLeaves Supplier017 Estimated Date and Time ofArrivalDTM02373DateM DT 8/8If DTM01 is 011, this will be theshipment date.If DTM is 017, this will be thedelivery date.Format is YYYYMMDDDTM03337TimeC TM 4/4If DTM01 011, this will be theshipment time.If DTM 017, this will be thedelivery time.Format is HHMM.DTM04623Time CodeC AN 2/2Any valid time zone may be used(e.g., AT, ET, PT).This value can only be present if timevalue is present.11/19/2007Page 4 of 23Revision 2

Hierarchal LevelSegment:HL - Hierarchal LevelLevel:Detail - first segment in each HL loopMax. Use:1Requirement: MandatoryPurpose:To identify dependencies among and the content of hierarchically relatedgroups of data segments.Comments:The HL segment is used to identify levels of detail information usinghierarchical structure, such as relating line item data to shipment data.Infor Automotive will only use the shipment and item levels. CancellationASNs require only the shipment level.Example:HL*1**S (shipment level)ELEM ELE# NAMEIDFEATURES COMMENTSHL01628Hierarchical IDNumberM AN 1/121 for the first HL segment,incremented by 1 in each subsequentHL segment within the transactionset.HL02734HierarchicalParent IDNumberM AN 1/12Not UsedHL03735HierarchicalLevel CodeM ID 1/2S ShipmentHL04736HierarchicalChild CodeN11/19/2007Page 5 of 23Revision 2

MeasurementSegment:MEA - MeasurementsLevel:Detail (Shipment Level)Max. Use:2Requirement: Mandatory (Both MEA Segments)Purpose:To specify physical measurements, including dimensions, tolerances,weights and counts.Comments:At shipment hierarchical level: - gross weight of shipment- tare weight LEMIDELE# NAMEFEATURES COMMENTSMEA01737Measurement Reference IDCodeM ID 2/2PD for physicaldimensionsMEA02738Measurement QualifierM ID 1/3G Gross WeightT Tare WeightMEA03739Measurement ValueM R 1/10WeightMEA04355Unit of Measure CodeM ID 2/2Unit of MeasureMEA05740Range MinimumNMEA06741Range MaximumNMEA07935Measurement SignificanceCodeNMEA08936Measurement Attribute CodeNMEA09752Surface/Layer/Position Code11/19/2007Page 6 of 23Revision 2

Carrier Details (Quantity and Weight)Segment:TD1 - Carrier Details (Qty/Weight)Level:Detail (Shipment Hierarchical Level Only)Max. Use:1Requirement: MandatoryPurpose:To specify the transportation details relative to commodity, weight andquantity.Example:TD1*PLT71*2ELEMIDELE# NAMETD101103Packaging Code M ID 5/5Any defined code is acceptable, i.e.,PLT71 for pallet; BOX34 forcardboard box; SKD90 for skid.TD102080Lading Quantity M N0 1/7Number of packages of the typespecified in TD101.TD103023CommodityCode 08355Unit of Measure NCode11/19/2007FEATURES COMMENTSPage 7 of 23Revision 2

Carrier Details (Routing / Transit)Segment:TD5 - Carrier Detail (Routing Sequence / Transit Time)Level:Detail (Shipment Hierarchical Level Only)Max. Use:1Requirement: MandatoryPurpose:To specify the carrier, routing sequence, and provide transit timeinformation.Comments:One TD5 is required for each shipment. Do not use more than one ELEMIDELE# NAMETD501133Routing Sequence Code M ID 1/2B Carrier is Origin/DeliveryCarrierTD502066Identification CodeQualifierM ID 1/22 SCAC Code92 Assigned by BuyerTD503067Identification CodeM AN 2/17Carrier's SCAC codeTD504091TransportationMethod/Type CodeM ID 1/2M Motor,A Air, etc.Valid Codes are listed belowONLY Use Codes Included inthe Table BelowTD505387RoutingNTD506368Ship/Order Status Code NTD507309Location QualifierCOR for Origin required ifTD504 A or AETD508310Location IdentifierCAirport Code (e.g., GRR)TD509731Transit Direction CodeNTD510732Transit Time DirectionQualifierNTD511733Transit TimeN11/19/2007FEATURES COMMENTSPage 8 of 23Revision 2

Transportation Method ModeThe following are valid codes for segment TD5, element TD504: TransportationMethod Mode: A - AIRAE - AIR EXPRESSC - CONSOLIDATIONLT - LTL TRUCKLOADM - MOTOR (COMMON CARRIER)Please note these are the only valid codes accepted by our ERP system.Using any other code will cause the data upload to fail.11/19/2007Page 9 of 23Revision 2

Carrier Details (Equipment)Segment:TD3 - Carrier Details (Equipment)Level:Detail (Shipment Hierarchal Level Only)Max. Use:1Requirement: MandatoryPurpose:To specify transportation details relating to the equipment used by thecarrier.Comments:Only one TD3 segment is used per shipment to identify the conveyancenumber.Example:TD3*TL**5ELEMIDELE# NAMEFEATURES COMMENTSTD301040M ID 2/2EquipmentDescription CodeTL TrailerAF Air FreightTD302206Equipment InitialNTD303207EquipmentNumberM AN 1/10TD304187Weight QualifierNTD305081WeightNTD306355Unit of MeasureCodeNTD307102Ownership CodeN11/19/2007Page 10 of 23Conveyance Number (i.e., trailernumber or air bill number)Revision 2

Reference NumberSegment:REF - Reference NumbersLevel:Detail (Shipment Level)Max. Use:3Requirement: Mandatory(REF*SI Iteration Mandatory)(REF*SI Iteration Mandatory when Sending Serial Numbers.)(Mandatory CLD and REF*SE Segments Required in Item Loop sinceSerial Numbers are Sent.)(If sending MULTIPLE Shipper Numbers per Master Bill of Lading theREF*SI segment MUST be included in EACH Item Loop (HL***I - ItemLevel) preceding the first CLD segment and NOT in the Shipping Loop(HL***S). REF*BM Mandatory in the Shipping Loop)Purpose:To specify identifying numbers.Comments:Used in the shipment level for: Air bill number - required if air shipment,Bill of Lading number - required if ground shipment.Example:REF*SI*234567 - required if air shipmentREF*BM*123456 - required if ground shipmentREF*DK*DK1ELEMIDELE# NAMEFEATURESCOMMENTSREF01128M ID 2/2BM Bill of LadingReference IdentificationQualifierSI Shipper Number*DK Dock CodeREF02127Reference IdentificationM AN 1/10REF03352DescriptionN11/19/2007Page 11 of 23Revision 2

NameSegment:N1 - NameLevel:Detail (Shipment Hierarchical Level)Max. Use:2Requirement: Mandatory (Both ST and SF Segments)Purpose:To identify a party by type of organization, name and code.Comments:The SF Ship From and ST Ship To ELEMIDELE# NAMEFEATURES COMMENTSN101098M ID 2/2Entity IdentifierCodeST Ship ToSF Ship FromFor Ship From (SF) Qualifier 92and 5 Digit Vendor Code PreferredM102093NameNN103066Identification Code M ID 1/2Qualifier01 DUNS NumberZZ User-assigned92 Buyer-assigned NumberN10406711/19/2007Identification Code M AN 2/17Page 12 of 23Identifying Number from N103Revision 2

Hierarchal LevelSegment:HL - Hierarchal LevelLevel:Detail - first segment in each HL loop (Item Level)Max. Use:1Requirement: MandatoryPurpose:To identify dependencies among and the content of hierarchically relatedgroups of data segments.Comments:The HL segment is used to identify levels of detail information usinghierarchical structure, such as relating line item data to shipment data.Infor Automotive will only use the shipment and item levels. CancellationASNs require only the shipment level.Example:HL*2*1*I (item level)ELEM ELE# NAMEIDFEATURES COMMENTSHL01628Hierarchical IDNumberM AN 1/121 for the first HL segment,incremented by 1 in each subsequentHL segment within the transactionset.HL02734HierarchicalParent IDNumberM AN 1/12The ID number of the parent HLsegment. Required for all HLsegments at the item level.HL03735HierarchicalLevel CodeM ID 1/2I ItemHL04736HierarchicalChild CodeN11/19/2007Page 13 of 23Revision 2

Item IdentificationSegment:LIN - Item IdentificationLevel:Detail (Item Hierarchical Level)Max. Use:1Requirement: MandatoryPurpose:To specify basic item identification 89ELEMIDELE# NAMEFEATURES duct/Service IDQualifierM ID 2/2BP Buyer's Part NumberLIN03234Product/Service IDM AN 1/20Part numbers are up to 20characters in length only11/19/2007Page 14 of 23Revision 2

Item Detail (Shipment)Segment:SN1 - Item Detail (shipment)Level:Detail (Item Hierarchal Level)Max. Use:1Requirement: MandatoryPurpose:To specify line item detail relative to shipment.Comments:Used to show the quantity being shipped, the unit of measure, andcumulative year to date shipments.Example:SN1**123*EA*1055ELEMIDELE# NAMEFEATURES ber of UnitsShippedM R 1/10SN103355Unit of Measure Code M ID 2/2Must use the unit of measurereceived on the material release830.SN104646Quantity Shipped toDateO R 1/9Cumulative quantity shipped forthis model year, including thisASN.SN105330Quantity OrderedNSN016355Unit of Measure Code NSN107728Returnable ContainerLoad Make-Up CodeSN108668Line Item Status Code N11/19/2007NPage 15 of 23Revision 2

Purchase Order ReferenceSegment:PRF - Purchase Order ReferenceLevel:Detail (Item Hierarchical Level)Max. Use:1Requirement: MandatoryPurpose:To provide reference to a specific purchase order.Example:PRF*PO123***19990501ELEMIDELE# NAMEFEATURES COMMENTSPRF01324Purchase Order NumberM AN 1/22PRF02328Release NumberNPRF03327Change Order SequenceNumberNPRF04323Purchase Order DateO DT 8/8PRF05350Assigned IdentificationNPRF06367Contract NumberN11/19/2007Page 16 of 23Format isYYYYMMDDRevision 2

Load DetailSegment:CLD - Load DetailLevel:Detail (Item Hierarchical Level)Max. Use:200Requirement: MandatoryPurpose:To specify the number of material loads shipped.Comments:A CLD segment is required. Serial Numbers are to be sent.Example:CLD*123*12***EAELEMIDELE# NAMEFEATURES COMMENTSCLD01622Number ofContainersM NO 1/5Number of Containers ShippedCLD02382Number of UnitsShippedM R 1/10Quantity Shipped per ContainerCLD03103Packaging CodeNCLD04357SizeNCLD05355Unit ofMeasurement CodeO ID 2/211/19/2007Page 17 of 23Must be the unit of measure codereceived on the 830.Revision 2

Reference NumbersSegment:REF - Reference NumbersLevel:Detail (Item Hierarchical Level)Max. Use:200Requirement: MandatoryPurpose:To specify identifying numbers.Comments:The REF segments are required. Serial Numbers are to be sent.Example:REF*SE*12345678ELEMIDELE# NAMEREF01128Reference Identification M ID 2/2QualifierREF02127Reference Identification M AN 1/9REF03352Description11/19/2007FEATURES COMMENTSSE Serial or Lot NumberIdentifier LS Not AcceptedNPage 18 of 23Revision 2

Transaction TotalsSegment:CTT - Transaction TotalsLevel:SummaryRequirement: MandatoryMax. Use:1Purpose:To transmit a hash total for a specific element in the transaction set.Comments:This segment is intended to provide hash totals to validate transactioncompleteness and correctness.Example:CTT*2*100ELEMIDELE# NAMECTT01354Number of Line M N0 1/6ItemsTotal Number of HL SegmentsCTT02347Hash TotalM R 1/10Required hash total of quantityshipped from all SN102 segments.CTT03081WeightNCTT04355Unit of Measure NCodeCTT05183VolumeCTT06355Unit of Measure NCodeCTT07352Description11/19/2007FEATURES COMMENTSNNPage 19 of 23Revision 2

Transaction Set TrailerSegment:SE - Transaction Set TrailerLevel:SummaryRequirement: MandatoryMax. Use:1Purpose:To indicate the end of the transaction set and provide the count of thetransmitted segments (including the beginning (ST) and ending (SE)segments).Comments:SE*25*00001Example:ELEM ID ELE# NAMEFEATURES COMMENTSSE01096Number of Included SegmentsM N0 1/6SE02329Transaction Set Control Number M AN 4/9CharacterMatches ST02Represented AsData Segment Terminating Character(Preference 7E)Tilde ( )Data Element Separating Character(Preference 2A)Asterisk ( * )Data Sub-Element Separating Character (Preference 3C)Less Than ( )The actual characters will be defined in the ISA segment. These characters are being usedfor display purposes only.Any valid ANSI X.12 defined control char will be used for the data segmentterminator (i.e., hex 1C).Do Not Use (Hex 2E (Period .)) as a Data or Hex Character.This will cause adverse effects on the processing of your ASN.Any valid ANSI X.12 defined control char , special char , or other special char will be used for the data element and subelement separator (i.e., * and \).11/19/2007Page 20 of 23Revision 2

Sample 856 With Serial *0933*U*00401*000011514*0*P* 10 ST*856*2020001 BSN*00*976174*20070321*0933 DTM*011*20070321*0930 DTM*017*20070321*0930 HL*1**S MEA*PD*G*8120*LB MEA*PD*T*4494*LB TD1*PLT90*7 TD5*B*2*MISC*M TD3*TL**730035 REF*SI*976174 N1*ST**01*809149292 N1*SF**01*YYYYY HL*2*1*I LIN**BP*1BM91PR4AC SN1**160*EA*6797 PRF*R000084***20060920 CLD*4*40***EA REF*SE*1078514 REF*SE*1078577 REF*SE*1078580 REF*SE*1078593 HL*3*1*I LIN**BP*1BM91DX8AC SN1**120*EA*14200 PRF*R000084***20060920 CLD*3*40***EA REF*SE*1074681 REF*SE*1078046 REF*SE*1078132 CTT*3*280 SE*32*2020001 GE*1*202 IEA*1*000011514 11/19/2007Page 21 of 23Revision 2

Sample 856Master Bill of LadingIndividual Shipment Numbers with Serial *0933*U*00401*000011514*0*P* 10 ST*856*2020001 BSN*00*976174*20070321*0933 DTM*011*20070321*0930 DTM*017*20070321*0930 HL*1**S MEA*PD*G*8120*LB MEA*PD*T*4494*LB TD1*PLT90*7 TD5*B*2*MISC*M TD3*TL**730035 REF*BM*976174 N1*ST**01*809149292 N1*SF**01*YYYYY HL*2*1*I LIN**BP*1BM91PR4AC SN1**160*EA*6797 PRF*R000084***20060920 REF*SI*976174 CLD*4*40***EA REF*SE*1078514 REF*SE*1078577 REF*SE*1078580 REF*SE*1078593 HL*3*1*I LIN**BP*1BM91DX8AC SN1**120*EA*14200 PRF*R000084***20060920 REF*SI*976175 CLD*3*40***EA REF*SE*1074681 REF*SE*1078046 REF*SE*1078132 CTT*3*280 SE*34*2020001 GE*1*202 IEA*1*000011514 11/19/2007Page 22 of 23Revision 2

Sample 856Master Bill of LadingIndividual Shipment Numbers with Serial NumbersDifferent Pack 321*0933*U*00401*000011514*0*P* 10 ST*856*2020001 BSN*00*976174*20070321*0933 DTM*011*20070321*0930 DTM*017*20070321*0930 HL*1**S MEA*PD*G*8120*LB MEA*PD*T*4494*LB TD1*PLT90*7 TD5*B*2*MISC*M TD3*TL**730035 REF*BM*976174 N1*ST**01*809149292 N1*SF**01*YYYYY HL*2*1*I LIN**BP*1BM91PR4AC SN1**160*EA*6797 PRF*R000084***20060920 REF*SI*976174 CLD*2*40***EA REF*SE*1078514 REF*SE*1078577 CLD*2*20***EA REF*SE*1078580 REF*SE*1078593 HL*3*1*I LIN**BP*1BM91DX8AC SN1**120*EA*14200 PRF*R000084***20060920 REF*SI*976175 CLD*2*40***EA REF*SE*1074681 REF*SE*1078046 CLD*1*20***EA REF*SE*1078132 CTT*3*280 SE*36*2020001 GE*1*202 IEA*1*000011514 11/19/2007Page 23 of 23Revision 2

856 EDI SPECIFICATIONS VERSION 4010 . 11/19/2007 Page 2 of 23 Revision 2 Transaction Set Header Segment: ST - Transaction Set Header Level: Heading Max. Use: 1 Requirement: Purpose: Mandatory To indicate the start of the 856 transaction set and assign a transaction .