ANSI X12 Version / Release 3020 856 Ship Notice / Manifest
ANSI X12 Version /Release 3020856 Ship Notice / ManifestEDI Implementation GuidelinesANSI X.12 856 V 3020Page 1 of 49
856 Ship Notice/ManifestSHFunctional Group ID Introduction:This standard provides the standardized format and establishes the data contents of a shipnotice/manifest transaction set. A ship notice/manifest lists the contents of a shipment ofgoods 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 enablesthe sender to describe the contents and configuration of a shipment in various levels of detailand provides an ordered flexibility to convey information. The sender of this transaction is theorganization responsible for detailing and communicating the contents of a shipment, orshipments, to one or more receivers of the transaction set. The receiver of this transaction setcan be any organization having an interest in the contents of a shipment or information aboutthe contents of a shipment.Heading:Pos. Seg.No. IDNameReq.LoopNotes andDes. Max.Use Repeat Comments010020STBSNTransaction Set HeaderBeginning Segment for Ship NoticeMM11Not Used 030040NTEDTMNote/Special InstructionDate/Time/PeriodFO10010Pos. Seg.No. IDNameReq.LoopNotes andDes. Max.Use Repeat Comments010020030040Hierarchical LevelItem IdentificationItem Detail (Shipment)Subline Item DetailMMDetail:LOOP ID - HLMNot UsedNot UsedNot UsedHLLINSN1SLNNot Used 050 PRFPurchase Order ReferenceNot Used 060 PO4Item Physical DetailsEDI Implementation GuidelinesANSI X.12 856 V 3020200000MOOO111100OO11c1Page 2 of 49
Not Used 070M080Not Used 090PIDMEAPWKProduct/Item DescriptionMeasurementsPaperworkOMO2004025Not Used 100M110M120PKGTD1TD5Marking, Packaging, LoadingCarrier Details (Quantity and Weight)Carrier Details (Routing Sequence /TransitOMM252012130TD3Carrier Details (Equipment)M12140TD4Carrier Details (Special Handling,Hazardous Materials, or Both)O5150MM150Not Used 160REFREFPERReference NumbersReference NumbersAdministrative Communications ContactMMO2002003Not Used 170CLDLOOP ID - CLDLoad DetailO1Not UsedNot UsedNot UsedNot UsedREFMANDTMFOBReference NumbersMarks and NumbersDate/Time/PeriodF.O.B. Related InstructionsOOOO20010101M180190200210or200LOOP ID - N1200M220230Not Used 240Not Used 250N1N2N3N4NameAdditional Name InformationAddress InformationGeographic LocationMOOO1221Not Used 260REFReference NumbersO12Not UsedNot UsedNot UsedNot UsedNot UsedNot UsedPERFOBSDQETDCURITAAdministrative Communications ContactF.O.B. Related InstructionsDestination QuantityExcess Transportation DetailCurrencyAllowance, Charge or ServiceLOOP ID - INHierarchical LevelItem IdentificationOM11MNot UsedMNot Used030040050060SN1SLNPRFPO4Item Detail (Shipment)Subline Item DetailPurchase Order ReferenceItem Physical DetailsMOMO110011Not Used 070Not Used 080PIDMEAProduct/Item DescriptionMeasurementsOO20040Not Used 090Not Used 100PWKPKGPaperworkMarking, Packaging, LoadingOO25EDI Implementation GuidelinesANSI X.12 856 V 3020c225Page 3 of 49
Not Used 110TD1O20OO1212TD4Carrier Details (Quantity and Weight)Carrier Details (Routing Sequence/TransitTime)Carrier Details (Equipment)Carrier Details (Special Handling, orHazardous Materials, or Both)Not Used 120Not Used 130TD5TD3Not Used 140O5Not Used 150REFReference NumbersO200Not Used 160PERAdministrative Communications ContactO3170Not Used 180Not Used 190CLDREFMANLoad DetailReference NumbersMarks and NumbersOOO120010Not Used 200DTMDate/Time/PeriodO10Not Used 210FOBO1Not Used 220Not Used 230N1N2F.O.B. Related InstructionsLOOP ID - N1NameAdditional Name InformationOO12Not UsedNot UsedNot UsedNot UsedNot UsedNot UsedNot UsedNot UsedN3N4REFPERFOBSDQETDCURAddress InformationGeographic LocationReference NumbersAdministrative Communications ContactF.O.B. Related InstructionsDestination QuantityExcess Transportation DetailCurrencyOOOOOOOO2112315011ITAO10MMM111LOOP ID - CLD240250260270280290300310Not Used 320200200MMM010020030HLLINSN1Allowance, Charge or ServiceLOOP ID - HLHierarchical LevelItem IdentificationItem Detail (Shipment)Not UsedMNot UsedNot Used040050060070SLNPRFPO4PIDSubline Item DetailPurchase Order ReferenceItem Physical DetailsProduct/Item DescriptionOMOO10011200080Not Used 090Not Used 100Not Used 110MEAPWKPKGTD1OOOO40252520Not Used 120TD5MeasurementsPaperworkMarking, Packaging, LoadingCarrier Details (Quantity and Weight)Carrier Details (Routing Sequence/TransitTime)O12Not Used 130TD3Carrier Details (Equipment)O12EDI Implementation GuidelinesANSI X.12 856 V 3020200000c3Page 4 of 49
Not Used 140TD4Carrier Details (Special Handling,Hazardous Materials, or Both)150150REFREFNot Used 160PER170180CLDREFNot Used 190Not Used 200Not Used 210MANDTMFOBNot Used 220Not UsedNot UsedNot UsedNot UsedNot UsedNot UsedNot UsedNot UsedNot UsedorO5Reference NumbersReference NumbersOO200200Administrative Communications ContactLOOP ID - CLDLoad DetailReference NumbersO3OO1200OOO10101N1Marks and NumbersDate/Time/PeriodF.O.B. Related InstructionsLOOP ID - N1NameO1230240250260N2N3N4REFAdditional Name InformationAddress InformationGeographic LocationReference nistrative Communications ContactF.O.B. Related InstructionsDestination QuantityExcess Transportation DetailCurrencyOOOOO315011ITAAllowance, Charge or ServiceO10Not Used 320200200Summary:Pos. Seg.MMReq.LoopNotes andNo.IDNameDes. Max.Use Repeat Comments1020CTTSETransaction TotalsTransaction Set TrailerMMEDI Implementation GuidelinesANSI X.12 856 V 302011n1Page 5 of 49
Transaction Set Notes1. 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 SN1segment.Transaction Set Comments1. The HL segment is the only mandatory segment within the HL loop, and by itself, the HLsegment has no meaning.2. The HL segment is the only mandatory segment within the HL loop, and by itself, the HLsegment has no meaning.3. The HL segment is the only mandatory segment within the HL loop, and by itself, the HLsegment has no meaning.EDI Implementation GuidelinesANSI X.12 856 V 3020Page 6 of 49
STSegment:Transaction Set yMax Use:Purpose:Syntax Notes:1To indicate the start of a transaction set and to assign a control numberSemantic Notes:Comments:1The transaction set identifier (ST01) is intended for use by the translationroutines of the interchange partners to select the appropriate transaction setdefinition (e.g., 810 selects the invoice transaction set).Data Element SummaryRef.DataDes.M ST01Element143M ST02329NameTransaction Set Identifier CodeCode uniquely identifying a Transaction Set856 X12.10 Ship Notice/ManifestTransaction Set Control NumberIdentifying control number assigned by the originator for a transaction set.EDI Implementation GuidelinesANSI X.12 856 V 3020AttributesM ID 3/3M AN 4/9Page 7 of 49
BSNBeginning Segment for Ship NoticeSegment:Position:Loop:Level:Usage:Max Use:Purpose:020HeadingMandatory1To transmit identifying numbers, dates, and other basic data relating to thetransaction setSyntax 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.Data Element SummaryRef.DataDes.Element NameAttributesM BSN01353Transaction Set Purpose CodeCode identifying purpose of transaction setOriginal00M ID 2/2M BSN02396Shipment IdentificationA unique control number assigned by the original shipper to identify a specificshipmentASN number. Unique supplier assigned number that is not repeated within one year.Adient recomends using the packing slip number.M AN 2/30M BSN03373DateM DT 6/6Date (YYMMDD)Date ASN was created. YYMMDDM BSN04337TimeM TM 4/6Time expressed in 24-hour clock time (HHMMSS) (Time range: 000000through 235959)Time ASN was created. HHMMXBSN051005Hierarchical Structure CodeO ID 4/4Code indicating the hierarchical application structure of a transaction setthat utilizes the HL segment to define the structure of the transaction setRefer to 003020 Data Element Dictionary for acceptable code valuesEDI Implementation GuidelinesANSI X.12 856 V 3020Page 8 of 49
DTMSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic 0To specify pertinent dates and times1 At least one of DTM02 or DTM03 is required.Data Element SummaryRef.DataDes.Element NameM DTM01374AttributesDate/Time QualifierM ID 3/3Code specifying type of date or time, or both date and timeDTM02373011Shipped017Estimated DeliveryDateXDT 6/6XTM 4/6Date (YYMMDD)YYMMDDDTM03337TimeTime expressed in 24-hour clock time (HHMMSS) (Time range: 000000through 235959)HHMMXDTM04623Time CodeO ID 2/2Code identifying the time. In accordance with International StandardsOrganization standard 8601, time can be specified by a or - and anindication in hours in relation to Universal Time Coordinate (UTC) time;since is a restricted character, and - are substituted by P and M in thecodes that followRefer to 003020 Data Element Dictionary for acceptable code values.XDTM05624CenturyO N0 2/2The first two characters in the designation of the year (CCYY)EDI Implementation GuidelinesANSI X.12 856 V 3020Page 9 of 49
HLHierarchical LevelSegment:Position:Loop:Level:Usage:Max Use:Purpose:010HLMandatoryDetailMandatory1To identify dependencies among and the content of hierarchicallyrelated groups of data segmentsSyntax Notes:Semantic Notes:Comments:12The HL segment defines a top-down/left-right ordered structure.HL01 shall contain a unique alphanumeric number for each occurrence ofthe HL segment in the transaction set. For example, HL01 could be used toindicate the number of occurrences of the HL segment, in which case thevalue of HL01 would be “1” for the initial HL segment and would beincremented by one in each subsequent HL segment within the transaction.3 HL02 identifies the hierarchical ID number of the HL segment to which thecurrent HL 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. Forexample, HL 03 is used to indicate the subsequent segments in the HL loopform a logical grouping of data referring to shipment, order, or item-levelinformation.5 HL04 indicates whether or not there are subordinate (or child) HL segmentsrelated to the current HL segment.Notes:Shipment LevelData Element SummaryMRef.DataDes.Element NameHL01628AttributesHierarchical ID NumberM AN 1/12A unique number assigned by the sender to identify a particular datasegment in a hierarchical structureHL02734Hierarchical Parent ID NumberO AN 1/12Identification number of the next higher hierarchical data segment that thedata segment being described is subordinate toMHL03735Hierarchical Level CodeM ID 1/2Code defining the characteristic of a level in a hierarchical structureSEDI Implementation GuidelinesANSI X.12 856 V 3020ShipmentPage 10 of 49
HL04736Hierarchical Child CodeO ID 1/1Code indicating whether if there are hierarchical child data segmentssubordinate to the level being described.Refer to 003020 Data Element Dictionary for acceptable code values.EDI Implementation GuidelinesANSI X.12 856 V 3020Page 11 of 49
ax Use:Purpose:Syntax Notes:123456080HLDetailMandatory40To specify physical measurements, including dimension tolerances, weights andcounts.At least one of MEA03 MEA05 MEA06 or MEA08 is required.If MEA03 is present, then MEA04 is requiredIf MEA05 is present, then MEA04 is required.If MEA06 is present, then MEA04 is required.If MEA07 is present, then at least one of MEA03 MEA05 or MEA06 is required.Only one of MEA08 or MEA03 may be present.Semantic Notes:Comments:1When citing dimensional tolerances, any measurement requiring a sign ( or -),or any measurement where a positive ( ) value cannot be assumed, use MEA05as the negative (-) value and MEA06 as the positive ( )valueData Element SummaryRef.DataDes.Element NameMEA01737AttributesMeasurement Reference ID CodeO ID 2/2Code specifying the application of physical measurement cited.PDMEA02738Physical DimensionsMeasurement QualifierO ID 1/3Code identifying the type of measurement.MEA03739GGross WeightNActual Net WeightMeasurement ValueX R 1/10The value of the measurementMEA04355Unit or Basis for Measurement CodeX ID 2/2Code identifying the basic unit of measurement.LBMEA05740Pound, KGKilogram,Range MinimumX R 1/10The value specifying the minimum of the measurement rangeEDI Implementation GuidelinesANSI X.12 856 V 3020Page 12 of 49
MEA06741MEA07935Range MaximumX R 1/10The value specifying the maximum of the measurement rangeMeasurement Significance CodeO ID 2/2Code used to benchmark, qualify or further define a measurement valueRefer to 003020 Data Element Dictionary for acceptable code values.MEA08936Measurement Attribute CodeX ID 2/2Code used to express an attribute response when a numeric measurementvalue cannot be determinedRefer to 003020 Data Element Dictionary for acceptable code valuesMEA09752Surface/Layer/Position CodeO ID 2/2Code indicating the product surface, layer or position that is beingdescribedRefer to 003020 Data Element Dictionary for acceptable code valuesEDI Implementation GuidelinesANSI X.12 856 V 3020Page 13 of 49
TD1Carrier Details (Quantity and Weight)Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:110MandatoryDetailMandatory20To specify the transportation details relative to commodity, weight, andquantity1 If TD101 is present, then TD102 is required2 If TD103 is present, then TD104 is required.3 If TD106 is present, then TD107 is required.Semantic Notes:Comments:Data Element SummaryRef.DataDes.Element NameTD101103Packaging CodeAttributesO AN 5/5Code identifying the type of packaging; Part 1: Packaging Form, Part 2:Packaging MaterialRefer to 003020 Data Element Dictionary for acceptable code values.TD10280Lading QuantityX N0 1/7Number of units (pieces) of the lading commodityXTD10323Commodity Code QualifierO ID 1/1Code identifying the commodity coding system used for Commodity CodeRefer to 003020 Data Element Dictionary for acceptable code values.XTD10422Commodity CodeXTD10579Lading DescriptionXTD106187Weight QualifierX AN 1/16Code describing a commodity or group of commoditiesO AN 1/50Description of an item as required for rating and billing purposesO ID 1/2Code defining the type of weightRefer to 003020 Data Element Dictionary for acceptable code values.XTD10781WeightX R 1/8Numeric value of weightEDI Implementation GuidelinesANSI X.12 856 V 3020Page 14 of 49
XTD108355Unit or Basis for Measurement CodeO ID 2/2Code identifying the basic unit of measurement.Refer to 003020 Data Element Dictionary for acceptable code valuesEDI Implementation GuidelinesANSI X.12 856 V 3020Page 15 of 49
TD5Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:1234Carrier Details (Routing Sequence/Transit Time)120HLDetailMandatory12To specify the carrier and sequence of routing and provide transit time informationAt least one of TD502 TD504 or TD505 is required.If TD502 is present, then TD503 is requiredIf TD507 is present, then TD508 is required.If TD510 is present, then TD511 is required.Semantic Notes:Comments:1 When specifying a routing sequence to be used for the shipment movement inlieu of specifying each carrier within the movement, use TD502 to identify theparty responsible for defining the routing sequence, and use TD503 to identifythe actual routing sequence, specified by the party identified in TD502Data Element SummaryRef.DataDes.Element NameTD501133AttributesRouting Sequence CodeO ID 1/2Code describing the relationship of a carrier to a specific shipmentmovementBTD50266Origin/Delivery Carrier (Any Mode)Identification Code QualifierX ID 1/2Code designating the system/method of code structure used forIdentification Code (67)2Standard Carrier Alpha Code (SCAC)TD50367Identification CodeTD50491Transportation Method/Type CodeX AN 2/17Code identifying a party.X ID 1/2Code specifying the method or type of transportation for the shipmentAAirCConsolidationMMotor (Common Carrier)RRailEDI Implementation GuidelinesANSI X.12 856 V 3020Page 16 of 49
TD505387RoutingX AN 1/35Free-form description of the routing or requested routing for shipment, orthe originating carrier's identityTD506368Shipment/Order Status CodeO ID 2/2Code indicating the status of an order or shipment or the disposition ofany difference between the quantity ordered and the quantity shipped for aline item or transaction Refer to 003020 Data Element Dictionary for acceptable code valuesXTD507309Location QualifierO ID 1/2Code identifying type of locationRefer to 003020 Data Element Dictionary for acceptable code values.XTD508310Location IdentifierX AN 1/25Code which identifies a specific locationTD509731Transit Direction CodeO ID 2/2The point of origin and point of directionRefer to 003020 Data Element Dictionary for acceptable code values.TD510732Transit Time Direction QualifierO ID 2/2Code specifying the value of time used to measure the transit timeRefer to 003020 Data Element Dictionary for acceptable code values.TD511733Transit TimeX R 1/4The numeric amount of transit timeEDI Implementation GuidelinesANSI X.12 856 V 3020Page 17 of 49
TD3Segment:Carrier Details lUsage:Max Use:Mandatory12Purpose:Syntax Notes:To specify transportation details relating to the equipment used by the carrier1 If TD302 is present, then TD303 is required.2 If TD304 is present, then both TD305 and TD306 are requiredSemantic Notes:Comments:Data Element SummaryMRef.DataDes.Element NameTD30140AttributesEquipment Description CodeM ID 2/2Code identifying type of equipment used for shipmentTLXTrailer (not otherwise specified)TD302206Equipment InitialTD303207Equipment NumberO AN 1/4Prefix or alphabetic part of an equipment unit's identifying numberX AN 1/10Sequencing or serial part of an equipment unit's identifying number (purenumeric form for equipment number is preferred)TD304187Weight QualifierO ID 1/2Code defining the type of weightRefer to 003020 Data Element Dictionary for acceptable code values.TD30581WeightTD306355Unit or Basis for Measurement CodeX R 1/8Numeric value of weightX ID 2/2Code identifying the basic unit of measurement.Refer to 003020 Data Element Dictionary for acceptable code valuesTD307102Ownership CodeO ID 1/1Code indicating the relationship of equipment to carrier.Refer to 003020 Data Element Dictionary for acceptable code valuesEDI Implementation GuidelinesANSI X.12 856 V 3020Page 18 of 49
TD4Carrier Details (Special Handling, or Hazardous Materials, or Both)Segment:Position:Loop:Level:Usage:Max Use:140HLMandatoryDetailOptional5To specify transportation special handling requirements, or hazardous materialsinformation, or bothPurpose:Syntax Notes:1 At least one of TD401 TD402 or TD404 is required.2 If TD402 is present, then TD403 is requiredSemantic Notes:Comments:Data Element SummaryRef.DataDes.Element NameTD401152Special Handling CodeAttributesX ID 2/3Code specifying special transportation handling instructionsRefer to 003020 Data Element Dictionary for acceptable code values.TD402208Hazardous Material Code QualifierX ID 1/1Code which qualifies the Hazardous Material Class Code (209)Refer to 003020 Data Element Dictionary for acceptable code values.TD403209Hazardous Material Class CodeX AN 2/4Code specifying the kind of hazard for a materialTD404352DescriptionX AN 1/80A free-form description to clarify the related data elements and theircontentEDI Implementation GuidelinesANSI X.12 856 V 3020Page 19 of 49
REFReference etailUsage:Max Use:Mandatory200Purpose:To specify identifying numbers.Syntax Notes:1 At least one of REF02 or REF03 is required.Semantic Notes:Comments:Data Element SummaryMRef.DataDes.Element NameREF01128AttributesReference Number QualifierM ID 2/2Code qualifying the Reference Number.REF02127BMBill of Lading NumberPKPacking List NumberReference NumberXAN 1/30XAN 1/80Reference number or identification number as defined for a particularTransaction Set, or as specified by the Reference Number Qualifier.REF03352DescriptionA free-form description to clarify the related data elements and their contentEDI Implementation GuidelinesANSI X.12 856 V 3020Page 20 of 49
N1Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Name220N1MandatoryDetailMandatory1To identify a party by type of organization, name, and code1 At least one of N102 or N103 is required.2 If either N103 or N104 is present, then the other is requiredSemantic Notes:Comments:1 This segment, used alone, provides the most efficient method of providingorganizational identification. To obtain this efficiency the "ID Code" (N104)must provide a key to the table maintained by the transaction processing party.Data Element SummaryMRef.DataDes.Element NameN10198AttributesEntity Identifier CodeM ID 2/2Code identifying an organizational entity or a physical location.XN10293N10366SFShip FromSTShip ToNameXAN 1/35XID 1/2XAN 2/17Free-form nameIdentification Code QualifierCode designating the system/method of code structure used forIdentification Code (67)1N10467Dun and Bradstreet (Credit Reporting) (DUNS)Identification CodeCode identifying a party.DUNS NumberEDI Implementation GuidelinesANSI X.12 856 V 3020Page 21 of 49
N2Additional Name InformationSegment:Position:Loop:Level:Usage:Max Use:Purpose:230N1DetailOptional2To specify additional names or those longer than 35 characters in lengthSyntax Notes:Semantic Notes:Comments:Data Element SummaryMRef.DataDes.Element NameN20193NameAttributesM AN 1/35Free-form nameN20293NameO AN 1/35Free-form nameEDI Implementation GuidelinesANSI X.12 856 V 3020Page 22 of 49
HLHierarchical LevelSegment:Position:Loop:Level:Usage:Max Use:Purpose:010HLOptionalDetailOptional1To identify dependencies among and the content of hierarchically related groupsof data segmentsSyntax Notes:Semantic Notes:Comments:Notes:1 The HL segment defines a top-down/left-right ordered structure.2 HL01 shall contain a unique alphanumeric number for each occurrence of theHL segment in the transaction set. For example, HL01 could be used to indicatethe number of occurrences of the HL segment, in which case the value ofHL01 would be "1" for the initial HL segment and would be incremented by onein each subsequent HL segment within the transaction3 HL02 identifies the hierarchical ID number of the HL segment to which thecurrent HL 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. Forexample, HL03 is used to indicate that subsequent segments in the HL loopform a logical grouping of data referring to shipment, order, or item-levelinformation.5 HL04 indicates whether or not there are subordinate (or child) HL segmentsrelated to the current HL segment.Order Level - Primary Metals ONLYData Element SummaryMRef.DataDes.Element NameHL01628AttributesHierarchical ID NumberM AN 1/12A unique number assigned by the sender to identify a particular datasegment in a hierarchical structureHL02734Hierarchical Parent ID NumberO AN 1/12Identification number of the next higher hierarchical data segment that thedata segment being described is subordinate toMHL03735Hierarchical Level CodeM ID 1/2Code defining the characteristic of a level in a hierarchical structureOOrderEDI Implementation GuidelinesANSI X.12 856 V 3020Page 23 of 49
HL04736Hierarchical Child CodeO ID 1/1Code indicating whether if there are hierarchical child data segmentssubordinate to the level being described.Refer to 003020 Data Element Dictionary for acceptable code valuesEDI Implementation GuidelinesANSI X.12 856 V 3020Page 24 of 49
LINSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Item ilMandatory1To specify basic item identification dataIf LIN04 is present, then LIN05 is required.If LIN06 is present, then LIN07 is required.If LIN08 is present, then LIN09 is required.If LIN10 is present, then LIN11 is required.If LIN12 is present, then LIN13 is required.If LIN14 is present, then LIN15 is required.If LIN16 is present, then LIN17 is required.If LIN18 is present, then LIN19 is required.If LIN20 is present, then LIN21 is required.If LIN22 is present, then LIN23 is required.If LIN24 is present, then LIN25 is required.If LIN26 is present, then LIN27 is required.If LIN28 is present, then LIN29 is required.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 identification3 LIN02 through LIN31 provide for fifteen (15) different product/service ID'sfor each item. For Example: Case, Color, Drawing No., UPC No., ISBN No.,Model No., SKU.Data Element SummaryRef.DataDes.Element NameXLIN01350MLIN02235AttributesAssigned IdentificationO AN 1/11Alphanumeric characters assigned for differentiation within a transaction setProduct/Service ID QualifierM ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)BPEDI Implementation GuidelinesANSI X.12 856 V 3020Buyer's Part NumberPage 25 of 49
MLIN03234Product/Service IDLIN04235Product/Service ID QualifierM AN 1/20Identifying number for a product or serviceO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN05234Product/Service IDX AN 1/30Identifying number for a product or serviceLIN06235Product/Service ID QualifierO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN07234Product/Service IDX AN 1/30Identifying number for a product or serviceLIN08235Product/Service ID QualifierO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN09234Product/Service IDX AN 1/30Identifying number for a product or serviceLIN10235Product/Service ID QualifierO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN11234Product/Service IDLIN12235Product/Service ID QualifierX AN 1/30Identifying number for a product or serviceO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN13234Product/Service IDLIN14235Product/Service ID QualifierX AN 1/30Identifying number for a product or serviceO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN15234Product/Service IDX AN 1/30Identifying number for a product or serviceEDI Implementation GuidelinesANSI X.12 856 V 3020Page 26 of 49
LIN16235Product/Service ID QualifierO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN17234Product/Service IDLIN18235Product/Service ID QualifierX AN 1/30Identifying number for a product or serviceO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN19234Product/Service IDX AN 1/30Identifying number for a product or serviceLIN20235Product/Service ID QualifierO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN21234Product/Service IDX AN 1/30Identifying number for a product or serviceLIN22235Product/Service ID QualifierO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN23234Product/Service IDLIN24235Product/Service ID QualifierX AN 1/30Identifying number for a product or serviceO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN25234Product/Service IDLIN26235Product/Service ID QualifierX AN 1/30Identifying number for a product or serviceO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN27234Product/Service IDLIN28235Product/Service ID QualifierX AN 1/30Identifying number for a product or serviceO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.EDI Implementation GuidelinesANSI X.12 856 V 3020Page 27 of 49
LIN29234Product/Service IDLIN30235Product/Service ID QualifierX AN 1/30Identifying number for a product or serviceO ID 2/2Code identifying the type/source of the descriptive number used inProduct/Service ID (234)Refer to 003020 Data Element Dictionary for acceptable code values.LIN31234Product/Service IDX AN 1/30Identifying number for a product or serviceEDI Implementation GuidelinesANSI X.12 856 V 3020Page 28 of 49
SN1Segment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Item Detail (Shipment)030HLOptionalDetailMandatory1To specify line-item detail relative to shipment1 If SN10
EDI Implementation Guidelines ANSI X.12 856 V 3020 Page 6 of 49 Transaction Set Notes 1. Number of line items
STANDARDS EVOLVE · Working papers · Three times a year · Draft standards · ANSI standards · Version & release 001000 ANSI - 1983 002000 ANSI - 1986 002040 Draft X12 May 89 003000 ANSI - 1992 003020 Draft X12 Oct 91 003021 Draft X12 Feb 92 004000 ANSI - 1997 004010 Draft X12 Oct 97 CHANGES · Simplify data. · Eliminate transactions.
VOLVO Application of ANSI X12 1 P a g e Application of ANSI X12 General ANSI X12 or ASC X12 (Accredited Standards Committee) develops and maintains EDI standards. X12 was the sequential designator assigned by
- Digit digit test X3 X3 X3 X3 - Digit symbol test X3 X3 X3 X3 - Controlled Oral Word Association (COWA) X12 X12 X12 - Telephone Interview for Cognitive Status (TICS) X14 X14 X14 Contact information X X XX X X X X X X X X X X X X X X X X X X X X X X X12 X12 X12 Demographics - age X - educatio
Slit Lamp with chinrest 20.0Kg, 75 x 54 x 45cm W x D x H Table top with PSU & Acc drawer 5.2Kg, 51 x 42 x 15cm W x D x H system components Part number Slit Lamp 40H, Standard Set complete with Table Top Slit Lamp PSU 3020-P-2000 3020-P-5032 3020-P-5040 Slit Lamp 40H, Refraction Unit Set Slit Lamp Power Supply and Socket Kit 3020-P-2003 3020-P-5032
ANSI X12—this overview provides need-to-know information on the ANSI X12 standards for electronic data interchange (EDI), including transaction sets, data elements and functional acknowledgements. Welcome This tutorial is an overview of the ANSI ASC X12
Code Sources—ANSI ASC X12 allows industry-specific codes. These codes are not main-tained by the ANSI ASC X12 committee, but by industry organizations. A list of where to obtain these industry codes can be found in the ASC X12 Standards manual. Interactive Control Structure—These are syntax rules at the application level that have been
ANSI X12 V3050 997 Functional Acknowledgment INFORMATIVE GUIDE. February 9, 2000 . Insurance Information & Enforcement System (IIES) New Directions in Enforcing Compulsory Insurance Laws. . Draft Standard for Trial Use Approved by ASC X12 Through May 1989 . 00300 . Standard Issued as ANSI X12.5-1992 . 00301 .
06/09/10 Purchase Order - 850 CLP_X12_ANSI8504010_060910.ecs 1 For internal use only . Inbound ANSI X12 850 Version 04010. For CLP License Ordering. Version: ANSI X12 850 4010 . Author: Adobe EDI Modified: 06/09/2010
