EDI Specification - InterTrade

BNY EDI ASN 856 specification Version 403010/27/2014EDI Specification856 - ASNAdvance Shipping NoticeVersion: ANSI X12 00403010/27/2014V 1.01 of 51

BNY EDI ASN 856 specification Version 403010/27/2014Table of ContentIntroduction: 856 Ship Notice/ Manifest . 3Envelope details. 6ISA Interchange Control Header . 6GS Functional Control Header. 9ST Transaction Set Header . 10ASN Header . 10BSN Beginning Segment for Ship Notice . 10Shipment Level . 11HL Reference Identification (Shipment) . 11TD1 Carrier Details (Quantity and Weight) . 12TD5 Carrier Details (Routing Sequence/Transit Time) . 13TD4 Carrier Details (Special Handling) . 14REF Reference Identification . 15PER Administrative Communications Contact . 18DTM Date/Time Reference . 19N1 Address Name . 20N3 Address Information . 21N4 Geographic Location . 22Order Level. 23HL Reference Identification (Order Level) . 23PRF Purchase Order Reference . 24TD1 Carrier Details (Quantity and Weight) . 25TD5 Carrier Details (Routing Sequence/Transit Time) . 26N1 Address Name . 27N3 Address Information . 28N4 Geographic Location . 29Carton Level . 30HL Reference Identification (Pack: Carton Level) . 30PO4 Item Physical details . 31MAN Marks and Numbers. 32Item Level . 33HL Reference Identification (Item Level) . 33LIN Item Identification . 34SN1 Item Detail (Shipment) . 35PID Product Item Description .36Summary detail . 37CTT Transaction Totals . 37Enveloping summary detail . 38SE Transaction Set Trailer . 38GE Functional Group Trailer . 39IEA Interchange Control Trailer . 41Samples of pick and pack 856 . 43Changes Summary . 452 of 51

BNY EDI ASN 856 specification Version 4030Introduction: 856 Ship10/27/2014Notice/ ManifestSHFunctional Group This specification 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 Interchange (EDI) environment. The transaction set can be usedto list the contents of a shipment of goods as well as additional information relating to the shipment, such as orderinformation, product description, physical characteristics, type of packaging, marking, carrier information, andconfiguration of goods within the transportation equipment. The transaction set enables the sender to describe thecontents and configuration of a shipment in various levels of detail and provides an ordered flexibility to conveyInformation.IMPORTANT: ALL ADVANCE SHIPMENT NOTICE/MANIFEST DOCUMENTS NEED TO MATCHEXACTLY WHAT WILL BE RECEIVED ON THE PHYSICAL SHIPMENT.All vendors are required to use Pick and Pack structure (BSN05 0001). This is the only acceptable EDI ASNformat.Small Package Carrier (SPC) ASN Requirements includedFor shipments sent via UPS, Fedex, etc., Barneys New York requires:More than one Small Package: Small Package Master ID included on Shipment Level using “BM”MAN(04) and Man(05) with “CP” qualifier contain Small Package Carrier Tracking Number.One Small Package: Small Package Tracking Number included on Shipment Level using “BM”MAN(04) and Man(05) with “CP” qualifier contain Small Package Carrier Tracking Number.Pick and Pack structure (BSN05 “0001”):This is the preferred method for Barneys New York. The transaction hierarchy is: Shipment Order Pack Item3 of 51

BNY EDI ASN 856 specification Version 403010/27/2014Heading:STTransaction Set HeaderM1BSNBeginning Segment for Ship NoticeM1Detail:LOOP ID – HL (SHIPMENT LEVEL)HL-SHLHierarchical Level – Shipment LevelM1TD1Carrier Details (Quantity and Weight)M1TD5Carrier Details (Routing Sequence)M1TD4Carrier Details (Special Handling)O1REFReference IdentificationM 1PERAdministrative Communications ContactO1DTMDate/Time ReferenceM 1LOOP ID – HL/N1HL-S-N1N1NameMN3Address InformationO12N4Geographic LocationO1LOOP ID – HL (ORDER LEVEL)HL-OHLHierarchical Level – Order LevelM1PRFPurchase Order ReferenceM1TD1Carrier Details (Quantity and Weight)O1TD5O1REFCarrier Details (Routing Sequence/TransitTime)Reference IdentificationM 1DTMDate/Time/PeriodO 1LOOP ID – HL-O– N1HL-O-N1N1Address NameM1N3Address InformationO2N4Geographic LocationO1M1PO4Hierarchical Level – Transportation PackLevelItem Physical detailsM20PKGMarking, Packaging, LoadingOMANMarks and NumbersMLOOP ID – HL (TRANS. Pack LEVEL)HLHL-P 14 of 51

BNY EDI ASN 856 specification Version 403010/27/2014HLLINSN1LOOP ID – HL (ITEM LEVEL)Hierarchical Level – Item LevelItem IdentificationItem Detail (Shipment)MMM111HL-IPIDProduct/Item DescriptionM 1Summary:CTTTransaction TotalsM1SETransaction Set TrailerM15 of 51

BNY EDI ASN 856 specification Version 403010/27/2014Envelope detailsSegment:ISA Interchange Control HeaderLevel:Loop:Usage:Max use:Purpose:N/AMandatory1To start and identify an interchange of zero or more functional groups and interchange-related control segments.Data Element SummaryRefISA01IdElement NameReqTypeMin/MaxI01Authorization Information QualifierMID2/2Description: Code identifying the type of information in the Authorization InformationCodeName00No Authorization Information Present (No Meaningful Information in I02)ISA02I02Authorization InformationMAN10/10Description: Information used for additional identification or authorization of the interchange sender or the data in theInterchange; the type of information is set by the Authorization Information Qualifier (I01)Set to 10 empty spacesISA03I03Security Information QualifierMIDDescription: Code identifying the type of information in the Security InformationCodeName00No Security Information Present (No Meaningful Information in I04)ISA04I04Security InformationMAN10/10Description: This is used for identifying the security information about the interchange sender or the data in theinterchange; the type of information is set by the Security Information Qualifier (I03)Set to 10 empty spacesISA05I05Interchange ID QualifierMID2/2Description: Code indicating the system/method of code structure used to designate the sender ID element beingqualifiedISA06I06Interchange Sender IDMAN15/15Description: Identification code published by the sender for other parties to use as the Sender ID to route data to them.ISA07I05Interchange ID QualifierMID2/22/2Barneys New York Note:This information is provided during the EDI certification and testing processISA08I07Interchange Receiver IDMAN15/15Barneys New York Note:This information is provided during the EDI certification and testing processISA09I08Interchange Date (sender)Description: Date of the interchangeMDT6/6ISA10I09Interchange Time (sender)Description: Time of the interchangeMTM4/4ISA11I65Repetition SeparatorM1/1Description: Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides thedelimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must bedifferent than the data element separator, component element separator, and the segment terminator6 of 51

BNY EDI ASN 856 specification Version 403010/27/2014‘ ’RefISA12IdElement NameReqTypeMin/MaxI11Interchange Control Version NumberMID5/5Description: Code specifying the version number of the interchange control segmentsCodeName00403Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board throughOctober 1999ISA13I12Interchange Control NumberMDescription: A control number assigned by the interchange senderISA14I13Acknowledgment RequestedMIDDescription: Code indicating sender's request for an interchange acknowledgmentCodeName0No Acknowledgment RequestedISA15I14Usage IndicatorMID1/1Description: Code indicating whether data enclosed by this interchange envelope is test, production or informationCodeNamePProduction DataTTest DataISA16I15Component Element SeparatorM1/1Description: Type is not applicable; the component element separator is a delimiter and not a data element; this fieldprovides the delimiter used to separate component data elements within a composite data structure; this value must bedifferent than the data element separator and the segment terminator‘ ’N09/91/17 of 51

BNY EDI ASN 856 specification Version 4030Segment:GS Functional Control HeaderLevel:Loop:Usage:Max use:Purpose:N/A10/27/2014Mandatory1To indicate the beginning of a functional group and to provide control information.Data Element Summary:RefGS01IdElement NameReqType479Functional Identifier CodeMIDDescription: Code identifying a group of application related transaction setsCodeNameSHShip Notice/Manifest (856)Min/Max2/2GS02142Application Sender's CodeMAN2/15Description: Code identifying party sending transmission; codes agreed to by trading partnersGS03124Application Receiver's CodeMAN2/15Description: Code identifying party receiving transmission; codes agreed to by trading partnersBarneys New York Note:This information is provided during the EDI certification and testing processGS04373DateMDT8/8Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar yearGS05337TimeMTM4/8Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD,where H hours (00-23), M minutes (00-59), S integer seconds (00-59) and DD decimal seconds; decimal secondsare expressed as follows: D tenths (0-9) and DD hundredths (00-99)Barneys New York Note:The format used is HHMMSSDDGS0628Group Control NumberMN0Description: Assigned number originated and maintained by the sender1/9GS07455Responsible Agency CodeMID1/2Description: Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480CodeNameXAccredited Standards Committee X12GS08480Version / Release / Industry Identifier Code MAN1/12Description: Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used,including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the versionnumber; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or tradeassociation identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowedCodeName004030 Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 19998 of 51

BNY EDI ASN 856 specification Version 4030Segment:ST Transaction Set HeaderLevel:Loop:Usage:Max use:Purpose:Header10/27/2014Mandatory1To indicate the start of a transaction set and to assign a control number.Data Element SummaryRefST01IdElement NameReq143Transaction Set Identifier CodeMDescription: Code uniquely identifying a Transaction SetCodeName856Ship Notice/ManifestTypeIDMin/Max3/3RefST02IdElement NameReqTypeMin/Max329Transaction Set Control NumberMAN4/9Description: Identifying control number that must be unique within the transaction set functional group assigned by theoriginator for a transaction setExample:ST*856*00019 of 51

BNY EDI ASN 856 specification Version 403010/27/2014ASN HeaderSegment:BSN Beginning Segment for Ship NoticeLevel:Loop:Usage:Max use:Purpose:HeaderMandatory1To transmit identifying numbers, dates, and other basic data relating to the transaction setData

BNY EDI ASN 856 specification Version 4030 10/27/2014 1 of 51. EDI Specification. 856 - ASN. Adva