• Have any questions?
  • info.zbook.org@gmail.com

856 Ship Notice/Manifest - V4030

10d ago
1 Views
0 Downloads
863.80 KB
35 Pages
Last View : 10d ago
Last Download : n/a
Upload by : Mia Martinelli
Share:
Transcription

Ship Notice/Manifest - 856856 Ship Notice/Manifest v4030X12/V4030/856Version: 1.8Author:Publication:Modified:PepBoys856 4030 v1 8OpenTextApril 1, 2008September 17, 2015Ver 1.8Page 1

Ship Notice/Manifest - 856Revision HistoryDateApril 1, 2008Version1.0October 20, 20081.1May 15, 20091.2December 8, 20111.4December 19, 20111.5RevisionInitial PublicationChanged description ofdata associated with UKqualifier (LIN)Changed MAN02 min/maxModified User notes on theREF, TD3, and LINsegmentsModified User notes on theApproved ByDiane PizzarelliDiane PizzarelliPaul HeidlerDiane PizzarelliDiane PizzarelliN104 and LIN segmentsModified User notes on theMarch 2, 2012March 19, 2012September 17, 2015PepBoys856 4030 v1 81.61.71.8Diane PizzarelliREF segmentCorrected examples,added Special Orderexample, clarified usernotes for the N1, and LINsegments.Changed LIN05 Min/MaxVer 1.8Diane PizzarelliDiane PizzarelliPage 2

Ship Notice/Manifest - 856856Ship Notice/ManifestFunctional Group SHThis Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/ManifestTransaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. Thetransaction set can be used to list the contents of a shipment of goods as well as additional information relating to theshipment, such as order information, product description, physical characteristics, type of packaging, marking, carrierinformation, and configuration of goods within the transportation equipment. The transaction set enables the senderto describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibilityto convey information.The sender of this transaction is the organization responsible for detailing and communicatingthe contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of thistransaction set can be any organization having an interest in the contents of a shipment or information about thecontents of a shipment.User Note:PLEASE NOTE THAT IN 4030 THE ISA11 NO LONGER CONTAINS THE INTERCHANGE CONTROLSTANDARDS IDENTIFIER. IT IS NOW USED TO IDENTIFY THE REPETITION SEPARATOR.Heading:PosSegment NameInterchange Control HeaderFunctional Group HeaderTransaction Set HeaderBeginning Segment for ShipNoticeReqMMMMSegment NameReqMax UseHierarchical LevelItem Detail (Shipment)Carrier Details (Quantity andWeight)Carrier Details (RoutingSequence/Transit Time)MOO1120O12Carrier Details (Equipment)Reference IdentificationDate/Time ReferenceOOO1 110NameO1LOOP ID - HL010HL050PRFHierarchical LevelPurchase Order ReferenceMM11LOOP ID - HL010HL190MANHierarchical LevelMarks and NumbersMO1 1LOOP ID - HL010HL020LINHierarchical LevelItem IdentificationMM11010020IdISAGSSTBSNMax UseRepeat1111NotesUsageMust useMust useMust useMust useDetail:PosIdLOOP ID - HL010HL030SN1110TD1120TD5LOOP ID - TD31300TD3150REF200DTMLOOP ID - N1220N1Repeat200000NotesC2/010LC2/010UsageMust useUsedMust useUsed12UsedMust useMust use200Must use200000200000200000PepBoys856 4030 v1 8Ver 1.8C2/010LC2/010C2/010LC2/010C2/010LCN2/010Must useMust useMust useMust useMust useMust usePage 3

Ship Notice/Manifest - 856030060070110SN1PO4PIDTD1Item Detail (Shipment)Item Physical DetailsProduct/Item DescriptionCarrier Details (Quantity andWeight)MOOO1120020Must useMust useMust useMust useSummary:Pos010020IdCTTSEGEIEASegment NameTransaction TotalsTransaction Set TrailerFunctional Group TrailerInterchange Control TrailerPepBoys856 4030 v1 8ReqOMMMMax UseRepeat1111Ver 1.8NotesUsageMust useMust useMust useMust usePage 4

Ship Notice/Manifest - 856ISAInterchange Control HeaderPos:Max: 1Heading - MandatoryLoop: N/AElements: 16User Option (Usage): Must useTo start and identify an interchange of zero or more functional groups and interchange-related control segmentsElement I05ISA06I06ISA07I05ISA08I07Element NameReqTypeMin/MaxUsageAuthorization Information QualifierMID2/2Must useDescription: Code identifying the type ofinformation in the Authorization InformationCodeName00No Authorization Information Present (No Meaningful Information in I02)Authorization InformationMAN10/10Must useDescription: Information used for additionalidentification or authorization of theinterchange sender or the data in theinterchange; the type of information is set bythe Authorization Information Qualifier (I01)Security Information QualifierMID2/2Must useDescription: Code identifying the type ofinformation in the Security InformationCodeName00No Security Information Present (No Meaningful Information in I04)Security InformationMAN10/10Must useDescription: This is used for identifying thesecurity information about the interchangesender or the data in the interchange; thetype of information is set by the SecurityInformation Qualifier (I03)Interchange ID QualifierMID2/2Must useDescription: Code indicating thesystem/method of code structure used todesignate the sender or receiver ID elementbeing qualifiedAll valid standard codes are used.Interchange Sender IDMAN15/15Must useDescription: Identification code published bythe sender for other parties to use as thereceiver ID to route data to them; the senderalways codes this value in the sender IDelementInterchange ID QualifierMID2/2Must useDescription: Code indicating thesystem/method of code structure used todesignate the sender or receiver ID elementbeing qualifiedCodeName01Duns (Dun & Bradstreet)ZZMutually DefinedInterchange Receiver IDMAN15/15Must usePepBoys856 4030 v1 8Ver 1.8Page 5

Ship Notice/Manifest - 3ISA15I14ISA16I15Description: Identification code published bythe receiver of the data; When sending, it isused by the sender as their sending ID, thusother parties sending to them will use this asa receiving ID to route data to themUser Note: Inovis Test: CLPEPBOYSPep Boys Test: 007914401TProduction: 007914401Interchange DateMDT6/6Must useDescription: Date of the interchangeInterchange TimeMTM4/4Must useDescription: Time of the interchangeRepetition SeparatorM1/1Must useDescription: Type is not applicable; therepetition separator is a delimiter and not adata element; this field provides the delimiterused to separate repeated occurrences of asimple data element or a composite datastructure; this value must be different than thedata element separator, component elementseparator, and the segment terminatorInterchange Control Version NumberMID5/5Must useDescription: Code specifying the versionnumber of the interchange control segmentsCodeName00403Draft Standards for Trial Use Approved for Publication by ASC X12 ProceduresReview Board through October 1999Interchange Control NumberMN09/9Must useDescription: A control number assigned bythe interchange senderAcknowledgment RequestedMID1/1Must useDescription: Code indicating sender'srequest for an interchange acknowledgmentAll valid standard codes are used.Usage IndicatorMID1/1Must useDescription: Code indicating whether dataenclosed by this interchange envelope is test,production or informationCodeNamePProduction DataTTest DataComponent Element SeparatorM1/1Must useDescription: Type is not applicable; thecomponent element separator is a delimiter andnot a data element; this field provides thedelimiter used to separate component dataelements within a composite data structure; thisvalue must be different than the data elementseparator and the segment terminatorPepBoys856 4030 v1 8Ver 1.8Page 6

Ship Notice/Manifest - 856GSFunctional Group HeaderPos:Max: 1Heading - MandatoryLoop: N/AElements: 8User Option (Usage): Must useTo indicate the beginning of a functional group and to provide control informationSemantics:1. GS04 is the group date.2. GS05 is the group time.3. The data interchange control number GS06 in this header must be identical to the same data element inthe associated functional group trailer, GE02.Comments:1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collectionof similar transaction sets enclosed by a functional group header and a functional group trailer.Element 0628Element NameReqFunctional Identifier CodeMDescription: Code identifying a group ofapplication related transaction setsCodeNameSHShip Notice/Manifest (856)Application Sender's CodeMDescription: Code identifying party sendingtransmission; codes agreed to by tradingpartnersApplication Receiver's CodeMDescription: Code identifying party receivingtransmission; codes agreed to by tradingpartnersUser Note: Inovis Test: CLPEPBOYSPep Boys Test: 007914401TProduction: 007914401DateMDescription: Date expressed asCCYYMMDD where CC represents the firsttwo digits of the calendar yearTimeMDescription: Time expressed in 24-hourclock time as follows: HHMM, or HHMMSS, orHHMMSSD, or HHMMSSDD, where H hours (00-23), M minutes (00-59), S integer seconds (00-59) and DD decimalseconds; decimal seconds are expressed asfollows: D tenths (0-9) and DD hundredths (00-99)Group Control NumberMDescription: Assigned number originatedand maintained by the senderPepBoys856 4030 v1 8Ver 1.8TypeIDMin/Max2/2UsageMust useAN2/15Must useAN2/15Must useDT8/8Must useTM4/8Must useN01/9Must usePage 7

Ship Notice/Manifest - 856GS07455GS08480Responsible Agency CodeMID1/2Must useDescription: Code identifying the issuer ofthe standard; this code is used in conjunctionwith Data Element 480CodeNameXAccredited Standards Committee X12Version / Release / Industry Identifier CodeMAN1/12Must useDescription: Code indicating the version,release, subrelease, and industry identifier ofthe EDI standard being used, including theGS and GE segments; if code in DE455 inGS segment is X, then in DE 480 positions 13 are the version number; positions 4-6 arethe release and subrelease, level of theversion; and positions 7-12 are the industry ortrade association identifiers (optionallyassigned by user); if code in DE455 in GSsegment is T, then other formats are allowedCodeName004030Draft Standards Approved for Publication by ASC X12 Procedures ReviewBoard through October 1999PepBoys856 4030 v1 8Ver 1.8Page 8

Ship Notice/Manifest - 856STPos: 010Max: 1Heading - MandatoryLoop: N/AElements: 2Transaction Set HeaderUser Option (Usage): Must useTo indicate the start of a transaction set and to assign a control numberSemantics:1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to selectthe appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).Example:ST*856*0001 Element Summary:RefST01Id143ST02329Element NameTransaction Set Identifier CodeDescription: Code uniquely identifying aTransaction SetCodeName856Ship Notice/ManifestTransaction Set Control NumberDescription: Identifying control number thatmust be unique within the transaction setfunctional group assigned by the originatorfor a transaction setPepBoys856 4030 v1 8Ver 1.8ReqMTypeIDMin/Max3/3UsageMust useMAN4/9Must usePage 9

Ship Notice/Manifest - 856BSN Beginning Segment forPos: 020Max: 1Heading - MandatoryLoop: N/AElements: 5Ship NoticeUser Option (Usage): Must useTo transmit identifying numbers, dates, and other basic data relating to the transaction setSyntax Rules:1. C0706 - If BSN07 is present, then BSN06 is required.Semantics:1. BSN03 is the date the shipment transaction set is created.2. BSN04 is the time the shipment transaction set is created.3. BSN06 is limited to shipment related codes.Comments:1. BSN06 and BSN07 differentiate the functionality of use for the transaction set.Example:BSN*00*1828458823*20080201*1454*0001 Element 1005Element NameReqTransaction Set Purpose CodeMDescription: Code identifying purpose oftransaction setCodeName00OriginalShipment IdentificationMDescription: A unique control numberassigned by the original shipper to identify aspecific shipmentDateMDescription: Date expressed asCCYYMMDDTimeMDescription: Time expressed in 24-hourclock time as follows: HHMM, or HHMMSS, orHHMMSSD, or HHMMSSDD, where H hours (00-23), M minutes (00-59), S integer seconds (00-59) and DD decimalseconds; decimal seconds are expressed asfollows: D tenths (0-9) and DD hundredths (00-99)Hierarchical Structure CodeMDescription: Code indicating the hierarchicalapplication structure of a transaction set thatutilizes the HL segment to define the structureof the transaction setCodeName0001Shipment, Order, Packaging, ItemPepBoys856 4030 v1 8Ver 1.8TypeIDMin/Max2/2UsageMust useAN2/30Must useDT8/8Must useTM4/4Must useID4/4Must usePage 10

Ship Notice/Manifest - 856HLPos: 010Max: 1Detail - MandatoryLoop: HLElements: 2Hierarchical LevelUser Option (Usage): Must useTo identify dependencies among and the content of hierarchically related groups of data segmentsComments:1. The HL segment is used to identify levels of detail information using a hierarchical structure, such asrelating line-item data to shipment data, and packaging data to line-item data.2. The HL segment defines a top-down/left-right ordered structure.3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transactionset. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which casethe value of HL01 would be "1" for the initial HL segment and would be incremented by one in eachsubsequent HL segment within the transaction.4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.5. HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence ofan HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loopform a logical grouping of data referring to shipment, order, or item-level information.6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.Example:HL*1**S Element Summary:RefHL01Id628HL03735Element NameHierarchical ID NumberDescription: A unique number assigned bythe sender to identify a particular datasegment in a hierarchical structureHierarchical Level CodeDescription: Code defining the characteristicof a level in a hierarchical structureCodeNameSShipmentPepBoys856 4030 v1 8Ver 1.8ReqMTypeANMIDMin/Max1/121/2UsageMust useMust usePage 11

Ship Notice/Manifest - 856SN1Item Detail (Shipment)Pos: 030Max: 1Detail - OptionalLoop: HLElements: 2User Option (Usage): UsedTo specify line-item detail relative to shipmentSyntax Rules:1. P0506 - If either SN105 or SN106 is present, then the other is required.Semantics:1. SN101 is the ship notice line-item identification.Comments:1. SN103 defines the unit of measurement for both SN102 and SN104.Example:SN1**9*EA Element Summary:RefSN102Id382SN103355Element NameNumber of Units ShippedDescription: Numeric value of units shippedin manufacturer's shipping units for a line itemor transaction setUser Note: Must equal the sum of all SN102sat Item Level.Unit or Basis for Measurement CodeDescription: Code specifying the units inwhich a value is being expressed, or mannerin which a measurement has been takenCodeNameEAEachPepBoys856 4030 v1 8Ver 1.8ReqMTypeRMIDMin/Max1/102/2UsageMust useMust usePage 12

Ship Notice/Manifest - 856TD1Carrier Details (Quantityand Weight)Pos: 110Max: 20Detail - OptionalLoop: HLElements: 4User Option (Usage): Must useTo specify the transportation details relative to commodity, weight, and quantitySyntax Rules:1.2.3.4.5.C0102 - If TD101 is present, then TD102 is required.C0304 - If TD103 is present, then TD104 is required.C0607 - If TD106 is present, then TD107 is required.P0708 - If either TD107 or TD108 is present, then the other is required.P0910 - If either TD109 or TD110 is present, then the other is required.Example:TD1**1****G*30*LB Element Summary:RefTD102Id80TD106187TD10781TD108355Element NameLading QuantityDescription: Number of units (pieces) of thelading commodityUser Note: Must equal total number of MANsegments at the Pack LevelWeight QualifierDescription: Code defining the type ofweightCodeNameGGross WeightWeightDescription: Numeric value of weightUnit or Basis for Measurement CodeDescription: Code specifying the units inwhich a value is being expressed, or mannerin which a measurement has been takenCodeNameLBPoundPepBoys856 4030 v1 8Ver 1.8ReqXTypeN0Min/Max1/7UsageMust useOID1/2Must useXR1/10Must useXID2/2Must usePage 13

Ship Notice/Manifest - 856TD5Carrier Details (RoutingSequence/Transit Time)Pos: 120Max: 12Detail - MandatoryLoop: HLElements: 2User Option (Usage): UsedTo specify the carrier and sequence of routing and provide transit time informationSyntax Rules:1.2.3.4.5.6.7.R0204050612 - At least one of TD502, TD504, TD505, TD506 or TD512 is required.C0203 - If TD502 is present, then TD503 is required.C0708 - If TD507 is present, then TD508 is required.C1011 - If TD510 is present, then TD511 is required.C1312 - If TD513 is present, then TD512 is required.C1413 - If TD514 is present, then TD513 is required.C1512 - If TD515 is present, then TD512 is required.Semantics:1. TD515 is the country where the service is to be performed.Comments:1. When specifying a routing sequence to be used for the shipment movement in lieu of specifying eachcarrier within the movement, use TD502 to identify the party responsible for defining the routing sequence,and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.Example:TD5**2*WATK Element Summary:RefTD502Id66TD50367Element NameReqIdentification Code QualifierMDescription: Code designating thesystem/method of code structure used forIdentification Code (67)CodeName2Standard Carrier Alpha Code (SCAC)Identification CodeXDescription: Code identifying a party or othercodePepBoys856 4030 v1 8Ver 1.8TypeIDANMin/Max1/22/10UsageMust useMust usePage 14

Ship Notice/Manifest - 856TD3Carrier Details (Equipment)Pos: 1300Max: 1Detail - MandatoryLoop: TD3Elements: 2User Option (Usage): UsedTo specify transportation details relating to the equipment used by the carrierSyntax Rules:1.2.3.4.E0110 - Only one of TD301 or TD310 may be present.C0203 - If TD302 is present, then TD303 is required.C0405 - If TD304 is present, then TD305 is required.P0506 - If either TD305 or TD306 is present, then the other is required.Example:TD3*TL**12345678 User Note:This segment is not required for Special Order shipments.Element Summary:RefTD301Id40TD303207Element NameEquipment Description CodeDescription: Code identifying type ofequipment used for shipmentCodeNameTLTrailer (not otherwise specified)Equipment NumberDescription: Sequencing or serial part of anequipment unit's identifying number(pure numeric form for equipmentnumber is preferred)PepBoys856 4030 v1 8Ver 1.8ReqXTypeIDXANMin/Max2/21/10UsageMust useMust usePage 15

Ship Notice/Manifest - 856REFReference IdentificationPos: 150Max: 1Detail - OptionalLoop: HLElements: 2User Option (Usage): Must useTo specify identifying informationSyntax Rules:1. R0203 - At least one of REF02 or REF03 is required.Semantics:1. REF04 contains data relating to the value cited in REF02.Example:REF*BM*1234567890 REF*CN*12345ABCDE6789ZZZUser Note:Bill of Lading Number (BM) is required.Carrier's Ref Number (CN) is required for special orders only. It is the tracking # provided by the carrier.Packing List Number (PK) is optional.Element Summary:RefREF01Id128REF02127Element NameReqTypeReference Identification QualifierMIDDescription: Code qualifying the ReferenceIdentificationCodeNameBMBill of Lading NumberCNCarrier's Reference Number (PRO/Invoice)PKPacking List NumberReference IdentificationXANDescription: Reference information asdefined for a particular Transaction Set oras specified by the Reference IdentificationQualifierPepBoys856 4030 v1 8Ver 1.8Min/Max2/31/30UsageMust useMust usePage 16

Ship Notice/Manifest - 856Pos: 200Max: 10Detail - OptionalLoop: HLElements: 2DTM Date/Time ReferenceUser Option (Usage): Must useTo specify pertinent dates and timesSyntax Rules:1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.2. C0403 - If DTM04 is present, then DTM03 is required.3. P0506 - If either DTM05 or DTM06 is present, then the other is required.Example:DTM*011*20080215 DTM*371*20080220 User Note:Shipped Date (011) is required.Current Schedule Delivery Date (067) is optional.Estimated Arrival Date (371) is required.Element Summary:RefDTM01Id374DTM02373Element NameDate/Time QualifierDescription: Code specifying type of date ortime, or both date and timeCodeName011Shipped067Current Schedule Delivery371Estimated Arrival DateDateDescription: Date expressed asCCYYMMDDPepBoys856 4030 v1 8Ver 1.8ReqMTypeIDMin/Max3/3UsageMust useXDT8/8Must usePage 17

Ship Notice/Manifest - 856N1Pos: 220Max: 1Detail - OptionalLoop: N1Elements: 3NameUser Option (Usage): Must useTo identify a party by type of organization, name, and codeSyntax Rules:1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.Comments:1. This segment, used alone, provides the most efficient method of providing organizational identification.To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by thetransaction processing party.2. N105 and N106 further define the type of entity in N101.Example:N1*ST**92*14026 0rN1*ST**92*0766 User Note:For Regular Order ASNs, this will be the 5-digit Distribution Center location code sent on the Purchase Order.For Special Order ASNs, this will be the 4-digit store number location code sent on the Purchase Order.Element Summary:RefN101Id98N10366N10467Element NameReqEntity Identifier CodeMDescription: Code identifying anorganizational entity, a physical location,property or an individualCodeNameSTShip ToIdentification Code QualifierXDescription: Code designating thesystem/method of code structure used forIdentification Code (67)CodeName92Assigned by Buyer or Buyer's AgentIdentification CodeXDescription: Code identifying a party or othercodePepBoys856 4030 v1 8Ver 1.8TypeIDMin/Max2/3UsageMust uID1/2Must useAN4/5Must usePage 18

Ship Notice/Manifest - 856HLPos: 010Max: 1Detail - MandatoryLoop: HLElements: 3Hierarchical LevelUser Option (Usage): Must useTo identify dependencies among and the content of hierarchically related groups of data segmentsExample:HL*2*1*O Element Summary:RefHL01Id628HL02734HL03735Element NameHierarchical ID NumberDescription: A unique number assigned bythe sender to identify a particular datasegment in a hierarchical structureHierarchical Parent ID NumberDescription: Identification number of the nexthigher hierarchical data segment that the datasegment being described is subordinate toHierarchical Level CodeDescription: Code defining the characteristicof a level in a hierarchical structureCodeNameOOrderPepBoys856 4030 v1 8Ver 1.8ReqMTypeANMin/Max1/12UsageMust useMAN1/12Must useMID1/2Must usePage 19

Ship Notice/Manifest - 856PRFPurchase Order ReferencePos: 050Max: 1Detail - MandatoryLoop: HLElements: 1User Option (Usage): Must useTo provide reference to a specific purchase orderSemantics:1. PRF04 is the date assigned by the purchaser to purchase order.Example:PRF*S3482451 Element Summary:RefPRF01Id324Element NamePurchase Order NumberDescription: Identifying number for PurchaseOrder assigned by the orderer/purchaserPepBoys856 4030 v1 8Ver 1.8ReqMTypeANMin/Max1/22UsageMust usePage 20

Ship Notice/Manifest - 856HLPos: 010Max: 1Detail - MandatoryLoop: HLElements: 3Hierarchical LevelUser Option (Usage): Must useTo identify dependencies among and the content of hierarchically related groups of data segmentsExample:HL*3*2*P Element Summary:RefHL01Id628HL02734HL03735Element NameHierarchical ID NumberDescription: A unique number assigned bythe sender to identify a particular datasegment in a hierarchical structureHierarchical Parent ID NumberDescription: Identification number of the nexthigher hierarchical data segment that the datasegment being described is subordinate toHierarchical Level CodeDescription: Code defining the characteristicof a level in a hierarchical structureCodeNamePPackPepBoys856 4030 v1 8Ver 1.8ReqMTypeANMin/Max1/12UsageMust useOAN1/12Must useMID1/2Must usePage 21

Ship Notice/Manifest - 856Pos: 190Max: 1Detail - OptionalLoop: HLElements: 2MAN Marks and NumbersUser Option (Usage): Must useTo indicate identifying marks and numbers for shipping containersSyntax Rules:1. C0605 - If MAN06 is present, then MAN05 is required.2. P0405 - If either MAN04 or MAN05 is present, then the other is required.Semantics:1. MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned tothe same physical container.2. When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03is the ending number of that range.3. When both MAN05 and MAN06 are used, MAN05 is the starting number of a sequential range, and MAN06is the ending number of that range.Example:MAN*GM*00000079405300190343 OrMAN*AA*000079405300190343 Element Summary:RefMAN01Id88MAN0287Element NameReqMarks and Numbers QualifierMDescription: Code specifying the applicationor source of Marks and Numbers (87)CodeNameAASSCC-18GMSSCC-18 and Application IdentifierMarks and NumbersMDescription: Marks and numbers used toidentify a shipment or parts of a shipment22PepBoys856 4030 v1 8TypeIDANMin/Max1/2UsageMust use18/20Must useVer 1.7Ver 1.8Page 22

Ship Notice/Manifest - 856HLPos: 010Max: 1Detail - MandatoryLoop: HLElements: 3Hierarchical LevelUser Option (Usage): Must useTo identify dependencies among and the content of hierarchically related groups of data segmentsElement Summary:RefHL01Id628HL02734HL03735Element NameHierarchical ID NumberDescription: A unique number assigned bythe sender to identify a particular datasegment in a hierarchical structureHierarchical Parent ID NumberDescription: Identification number of the nexthigher hierarchical data segment that the datasegment being described is subordinate toHierarchical Level CodeDescription: Code defining the characteristicof a level in a hierarchical structureCodeNameIItemPepBoys856 4030 v1 8Ver 1.8ReqMTypeANMin/Max1/12UsageMust useOAN1/12Must useMID1/2Must usePage 23

Ship Notice/Manifest - 856LINPos: 020Max: 1Detail - MandatoryLoop: HLElements: 6Item IdentificationUser Option (Usage): Must useTo specify basic item identification dataSyntax Rules:1. P0405 - If either LIN04 or LIN05 is present, then the other is required.2. P0607 - If either LIN06 or LIN07 is present, then the other is *MF*33968209 User Note:The UPC and Buyers Item Number are not required for Special Order shipmentsThe Manufacturer’s Number is required for Special Order shipments. (This will be the item number sent on thespecial order 850 with a ‘VP’ qualifier.)Element 235LIN07234Element NameReq TypeMin/MaxUsageProduct/Service ID QualifierMID2/2UsedDescription: Code identifying thetype/source of the descriptive number used inProduct/Service ID (234)CodeNameUK14-digit UPC/EAN CodeDescription: Pep Boys expects 12-digit UPC with 2 leading zeroes.User Note: Not required for SpecialOrder shipments.Product/Service IDMAN14/14UsedDescription: Identifying number for a productor serviceProduct/Service ID QualifierDescription: Code identifying thetype/source of the descriptive number used inProduct/Service ID (234)CodeNameINBuyer's Item NumberUser Note: Not required for Special Ordershipments.Product/Service IDDescription: Identifying number for a productor serviceProduct/Service ID QualifierDescription: Code identifying thetype/source of the descriptive number used inProduct/Service ID (234)CodeNameMFManufacturerUser Note: Manufacturers number requiredfor Special Order shipments.Product/Service IDDescription: Identifying number for a productor servicePepBoys856 4030 v1 8Ver 1.8XID2/2UsedXAN1/48UsedXID2/2UsedXAN1/15UsedPage 24

Ship Notice/Manifest - 856SN1Pos: 030Max: 1Detail - MandatoryLoop: HLElements: 2Item Detail (Shipment)User Option (Usage): Must useTo specify line-item detail relative to shipmentSyntax Rules:1. P0506 - If either SN105 or SN106 is present, then the other is required.Semantics:1. SN101 is the ship notice line-item identification.Example:SN1**9*EA Element Summary:RefSN102Id382SN103355Element NameNumber of Units ShippedDescription: Numeric value of units shippedin manufacturer's shipping units for a line itemor transaction setUnit or Basis for Measurement CodeDescription: Code specifying the units inwhich a value is being expressed, or mannerin which a measurement has been takenCodeNameEAEachPepBoys856 4030 v1 8Ver 1.8ReqMTypeRMIDMin/Max1/102/2UsageMust useMust usePage 25

Ship Notice/Manifest - 856PO4Pos: 060Max: 1Detail - OptionalLoop: HLElements: 1Item Physical DetailsUser Option (Usage): Must useTo specify the physical qualities, packaging, weights, and dimensions relating to the itemSyntax Rules:1.2.3.4.5.6.7.8.9.10.C0506 - If PO405 is present, then PO406 is required.C1013 - If PO410 is present, then PO413 is required.C1113 - If PO411 is present, then PO413 is required.C1213 - If PO412 is present, then PO413 is required.C1716 - If PO417 is present, then PO416 is required.C1804 - If PO418 is present, then PO404 is required.L13101112 - If PO413 is present, then at least one of PO410, PO411 or PO412 is required.P0203 - If either PO402 or PO403 is present, then the other is required.P0607 - If either PO406 or PO407 is present, then the other is required.P0809 - If either PO408 or PO409 is present, then the other is required.Semantics:1. PO415 is used to indicate the relative layer of this package or range of packages within the layersof packaging. Relative Position 1 (value R1) is the innermost

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