Transcription
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation Guidelines856 Ship Notice/ManifestSHFunctional Group ID Introduction:This 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,carrier information, and configuration of goods within the transportation equipment. The transaction set enables thesender to describe the contents and configuration of a shipment in various levels of detail and provides an orderedflexibility to convey information. The sender of this transaction is the organization responsible for detailing andcommunicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. Thereceiver of this transaction set can be any organization having an interest in the contents of a shipment orinformation about the contents of a shipment.Notes:Ariba Network allows Suppliers to send Ship Notices to Buyers in the form of the cXML ShipNoticeRequest. Thisis a fulfillment document to the cXML OrderRequest.As a service to Suppliers preferring to transact via EDI, Ariba Network accepts the ANSI X12 004010 856 ShipNotice / Manifest document.On receiving the 856 (documented here), Ariba Network validates the EDI content, returns a 997 to the Supplier,and converts it to the cXML ShipNoticeRequest. The final cXML document is internally posted to perform theactual fulfillment update.If an error arises at the application level, an email notification is sent to the Supplier, advising the failure and thereason. Ariba Network does not currently implement the 824 Application Advice.All separator characters within the ANSI X12 domain are allowed. You do not need to use the same separators thatyou receive on your 850. The recommended separators are:Segment Terminator:Element Separator:Sub-Element Separator: (tilde)* (asterisk) (greater than)* Note that different VANs have different separator char requirements. They are usually modified in transit. Thesethree chars are always written to all inbound interchanges to Ariba Network by Sterling Commerce. Needless to say,these three chars must not occur within your data itself.On the returning 997, the following points should be noted.Summary 997's are implemented, returning AK2/AK5 segments. Detailed 997's with AK3 and AK4 segments arenot supported at this time.Interchanges are not acknowledged. Do not expect a TA1 segment. ISA14 should be set to 0, but is ignored.AK5 acknowledgement codes:- Code "A" constitutes acceptance. A cXML ShipNoticeRequest was successfully prepared for submission to AribaNetwork.- Code "E" is an EDI Compliance error. If you receive this in an AK5, it means that the 856 was not converted anddid not make it past our EDI gateway.Copyright (c) 1996–2014 Ariba, Inc. All rights reserved.1Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation Guidelines- Code "R" represents total rejection. Ariba Network EDI does not currently implement this code.AK9 acknowledgement codes:- The above codes apply. Code "P" is possible if not all AK5's are code "A".Ariba Network Support is available to help resolve technical issues with EDI. Suppliers are requested to open casesif they need assistance.The ideal way to create a case is to complete the Network Support help form on supplier.ariba.com.Ariba Commerce Services Network: network support@ariba.comAriba Marketplace, Network Edition: marketned support@ariba.comMain Support Phone: 888-89ARIBA / 888-892-7422In reading this Implementation Guide, the following usage codes are used:StatusSegmentElement----------------------- ------------ ----------MandatoryMMMust UseMust UseMRecommendedRRDependantDDNot Recommended NRNRNot UsedXXMandatory means that X12 says it is mandatory, so the guideline is bound by that rule.Must Use means that X12 says it is optional, but Ariba Network requires it.Recommended means that X12 says it is optional, and Ariba Network considers it optional, but recommends that itbe used.Dependant means that X12 might have its usage dependant on other segments or elements, or by semantic notes, orthat Ariba Network describes semantics on which its dependency lies.Not Recommended is the opposite of Recommended. The information may be technically allowed, but is probablyignored.Not Used segments and elements are not even shown in the guideline. In cases there they made need to be shown forconsistency, they are marked with an on Set HeaderBaseGuideM55020BSNBeginning Segment for Ship NoticeM77040DTMDate/Time ReferenceOUserStatusMMax.Use1MLoopRepeatNotes andCommentsLoopRepeatNotes 0010HLHierarchical Level - ShipmentM11120TD5O113120TD5O1115140TD4Carrier Details (RoutingSequence/Transit Time)Carrier Details (TransportInformation)TD4 Carrier Details (CarrierO1NameLOOP ID - HLCopyright (c) 1996–2014 Ariba, Inc. All rights reserved.UserStatusMax.Use12M1Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation Guidelines16150REF18210FOBIdentifier)Reference IdentificationO4F.O.B Related Instructions (Terms ofDelivery)LOOP ID - N1O120021220N1NameO123230N2Additional Name InformationO224240N3Address InformationO225250N4Geographic LocationO128270PERAdministrative CommunicationsContactO3LOOP ID - N13031322202402501N1NameO1N3Address InformationO2N4Geographic LocationO1LOOP ID - HL20000035010HLHierarchical Level - OrderMM137050PRFPurchase Order ReferenceOMust Use138150REFReference IdentificationO139200DTMDate/Time ReferenceO10LOOP ID - N120041220N1NameO142230N2Additional Name InformationO243240N3Address InformationO244250N4Geographic LocationO145270PERAdministrative CommunicationsContactO3LOOP ID - HL20000046010HLHierarchical Level - Line ItemMM147030SN1Item Detail (Shipment)OMust Use148060PO4Item Physical DetailsO151150REFReference IdentificationO 153190MANMarks and NumbersO tion Totals56020SETransaction Set es andCommentsn11Transaction 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 SN1 segment.Transaction Set Comments1.The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has nomeaning.Copyright (c) 1996–2014 Ariba, Inc. All rights reserved.3Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation GuidelinesSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:ST Transaction Set Header010HeadingMandatory1To indicate the start of a transaction set and to assign a control number1The 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).Example:ST*856*0001 produces. ShipNoticeRequest Data Element meAttributesAttributesTransaction Set Identifier CodeM ID 3/3MCode uniquely identifying a Transaction Set856Ship Notice/ManifestTransaction Set Control NumberM AN 4/9MIdentifying control number that must be unique within the transaction set functional groupassigned by the originator for a transaction setCopyright (c) 1996–2014 Ariba, Inc. All rights reserved.4Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation GuidelinesSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:BSN Beginning Segment for Ship Notice020HeadingMandatory1To transmit identifying numbers, dates, and other basic data relating to the transaction set1 If BSN07 is present, then BSN06 is required.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.1 BSN06 and BSN07 differentiate the functionality of use for the transaction 004 produces. ShipNoticeRequest ShipNoticeHeader shipmentID "843-2187-5193" operation "new" noticeDate "200109-03T12:18:44-0000" . Data Element esTransaction Set Purpose CodeM ID 2/2Code identifying purpose of transaction setThe (optional) operational mode of ship notice document.UserAttributesMAn "update" ship notice (BSN01 '05') allows a supplier to correct an error in a ship noticeor to add additional information learned later. In either case, an "update" document mustbe complete: All data from the original should be discarded by the recipient.An "replace" ship notice must have the same Shipment Identifier (BSN02) as the previousversion of the notice. This provides an unambiguous and direct connection between allversions of the ship notice.* Note that the 856 supports Delete and Replace options here, to map into similar cXMLoperation values. However, the AN13s3 release does not yet support this. ShipNoticeHeader operation BSN01 operation (new update delete) "new"00#REQUIREDOriginal ShipNoticeHeader operation "new" 03BSN02396Delete ShipNoticeHeader operation "delete" * Reserved for future use - not supported by AN13s305Replace ShipNoticeHeader operation "update" * Reserved for future use - not supported by AN13s3Shipment IdentificationM AN 2/30MA unique control number assigned by the original shipper to identify a specific shipmentAn identifier for this particular shipment assigned by the supplier. This value does not varyas a particular ship notice is updated. That is, BSN01 "03" or BSN01 "05" documentsdescribing the same shipment must share a shipmentID with the original (BSN01 "00")Ship Notice. ShipNoticeHeader shipmentID BSN02 shipmentID %string; #REQUIREDCopyright (c) 1996–2014 Ariba, Inc. All rights reserved.5Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation GuidelinesBSN03373DateDate expressed as CCYYMMDDThe date this ship notice was created.MDT 8/8M ShipNoticeHeader noticeDate BSN03 BSN04 BSN04337TimeM TM 4/8MTime 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 (0059) and DD decimal seconds; decimal seconds are expressed as follows: D tenths (0-9)and DD hundredths (00-99)The time this ship notice was created. ShipNoticeHeader noticeDate BSN03 BSN04 BSN051005BSN06640Hierarchical Structure CodeO ID 4/4OCode indicating the hierarchical application structure of a transaction set that utilizes theHL segment to define the structure of the transaction set0004Shipment, Order, ItemTransaction Type CodeO ID 2/2OCode specifying the type of transactionThis element is used for defining the shipmentType. ShipNoticeHeader shipmentType ”actual” BSN0764109actualPLplannedStatus Reason CodeCode indicating the status reasonThis element is used for defining the fulfillmentType.OID 3/3O ShipNoticeHeader fulfillmentType ”partial” C20B44completepartialCopyright (c) 1996–2014 Ariba, Inc. All rights reserved.6Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation GuidelinesSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Usage Notes:Notes:DTM Date/Time Reference040HeadingOptional2To specify pertinent dates and times1 At least one of DTM02 DTM03 or DTM05 is required.2 If DTM04 is present, then DTM03 is required.3 If either DTM05 or DTM06 is present, then the other is 0*ED DTM*017*20010904*0900*20 produces. ShipNoticeHeader . shipmentDate "2001-09-03T08:30:00-0400"deliveryDate "2001-09-04T09:00:00-0500" * DTM04 "ED" represents Eastern Daylight Time, which is UTC-0400DTM04 "20" represents ISO M05, which is -05, hence UTC-0500Specify the Shipment Date and/or Estimated Delivery Date. Both are optional, but theShipment Date is recommended.Note that a complete date/time/zone is recommended. Timestamps in cXML arerepresented as a date with a time, and an offset to UTC. If you do not specify a time, itmay be taken as midnight on the date specified. If you do not specify the time code(zone), then it will be defaulted. ShipNoticeHeadershipmentDate %datetime.tz; #IMPLIED DTM02 DTM03 DTM04 where DTM01 "011"deliveryDate %datetime.tz; #IMPLIED DTM02 DTM03 DTM04 where DTM01 "017" Data Element DTM04623BaseUserNameAttributesAttributesDate/Time QualifierM ID 3/3MCode specifying type of date or time, or both date and time011Shipped017Estimated DeliveryDateX DT 8/8MDate expressed as CCYYMMDDTimeX TM 4/8RTM 4/6Time 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 (0059) and DD decimal seconds; decimal seconds are expressed as follows: D tenths (0-9)and DD hundredths (00-99)Time CodeO ID 2/2RCode identifying the time. In accordance with International Standards OrganizationCopyright (c) 1996–2014 Ariba, Inc. All rights reserved.7Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation Guidelinesstandard 8601, time can be specified by a or - and an indication in hours in relation toUniversal Time Coordinate (UTC) time; since is a restricted character, and - aresubstituted by P and M in the codes that followNote that the LT code is not available. This is because Ariba Network does not currentlyhave a way to make a context-sensitive assumption on the time zone.The ISO codes are favorable because you have direct control over the output, but they donot support half hour zones as in Newfoundland. (If you need Newfoundland time, NS &NT map to -0330, ND maps to -0230)01Equivalent to ISO P0102Equivalent to ISO P0203Equivalent to ISO P0304Equivalent to ISO P0405Equivalent to ISO P0506Equivalent to ISO P0607Equivalent to ISO P0708Equivalent to ISO P0809Equivalent to ISO P0910Equivalent to ISO P1011Equivalent to ISO P1112Equivalent to ISO P1213Equivalent to ISO M1214Equivalent to ISO M1115Equivalent to ISO M1016Equivalent to ISO M0917Equivalent to ISO M0818Equivalent to ISO M0719Equivalent to ISO M0620Equivalent to ISO M0521Equivalent to ISO M0422Equivalent to ISO M0323Equivalent to ISO M0224Equivalent to ISO M01ADAlaska Daylight TimeASAlaska Standard TimeATAlaska TimeCDCentral Daylight TimeCSCentral Standard TimeCTCentral TimeEDEastern Daylight TimeESEastern Standard TimeETEastern TimeGMGreenwich Mean TimeHDHawaii-Aleutian Daylight TimeHSHawaii-Aleutian Standard TimeHTHawaii-Aleutian TimeMDMountain Daylight TimeMSMountain Standard TimeMTMountain TimeNDNewfoundland Daylight TimeNSNewfoundland Standard TimeNTNewfoundland TimeCopyright (c) 1996–2014 Ariba, Inc. All rights reserved.8Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation GuidelinesPDPSPTTDTSTTUTPacific Daylight TimePacific Standard TimePacific TimeAtlantic Daylight TimeAtlantic Standard TimeAtlantic TimeUniversal Time Coordinate "Z" or "-00:00"This is Coordinated Universal Time, or UTC. The correct ISOzone extension for UTC is simply Z. However this release ofAriba Network does not support Z, so it renders as "-00:00", todistinguish it from GMT which uses " 00:00".Copyright (c) 1996–2014 Ariba, Inc. All rights reserved.9Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation GuidelinesSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Notes:HLHierarchical Level - Shipment010HLMandatoryDetailMandatory1To identify dependencies among and the content of hierarchically related groups of datasegments1The 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 lineitem data.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.5 HL04 indicates whether or not there are subordinate (or child) HL segments relatedto the current HL segment.Example: HL*1**S*1 At the Shipment level, we specify information concerning the shipment as a whole. Thisincludes carrier and route information.Data Element 4736BaseUserNameAttributesAttributesHierarchical ID NumberM AN 1/12MA unique number assigned by the sender to identify a particular data segment in ahierarchical structureHierarchical Parent ID NumberO AN 1/12NRIdentification number of the next higher hierarchical data segment that the data segmentbeing described is subordinate toSince Shipment is the root of the hierarchical tree, it has no parent id. The Shipment levelonly should leave this element as null. (Marked NR here for consistency only).Hierarchical Level CodeM ID 1/2MCode defining the characteristic of a level in a hierarchical structureSShipmentHierarchical Child CodeO ID 1/1OCode indicating if there are hierarchical child data segments subordinate to the level beingdescribed1Additional Subordinate HL Data Segment in This HierarchicalStructure.Copyright (c) 1996–2014 Ariba, Inc. All rights reserved.10Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation GuidelinesSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Usage Notes:Notes:TD5Carrier Details (Routing Sequence/Transit Time)120HLMandatoryDetailOptional1To specify the carrier and sequence of routing and provide transit time information1 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.4 If TD510 is present, then TD511 is required.5 If TD513 is present, then TD512 is required.6 If TD514 is present, then TD513 is required.7 If TD515 is present, then TD512 is required.1 TD515 is the country where the service is to be performed.1 When specifying a routing sequence to be used for the shipment movement in lieu ofspecifying each carrier within the movement, use TD502 to identify the partyresponsible for defining the routing sequence, and use TD503 to identify the actualrouting sequence, specified by the party identified in TD502.Used/OptionalExample:TD5**2*NSTY*J*Nasty Express**ZZ*DEA24597281772****ND produces. ShipNoticeRequest ShipNoticeHeader . ServiceLevel xml:lang "en" Next Day Air /ServiceLevel . /ShipNoticeHeader ShipControl CarrierIdentifier domain "SCAC" NSTY /CarrierIdentifier CarrierIdentifier domain "companyName" Nasty Express /CarrierIdentification ShipmentIdentifier DEA24597281772 /ShipmentIdentifier Route method "motor" / ShipControl .Carrier and routing information is summed in a single TD5 segment. In this release, onlyone carrier for the shipment is supported.If carrier information is being supplied here, Ariba Network requires identification of thecarrier. Both the coded identification (TD502-03) and the carrier name (TD505) arerequired. It is possible to merge complete carrier company contact information withN1*CA (1/220, this level) by matching TD502-03 with N103-04.Data Element butesAttributesIdentification Code QualifierX ID 1/2MCode designating the system/method of code structure used for Identification Code (67)Elements 2 and 3 are used to identify the carrier. Note the element id's: 66 & 67. They mustmatch N103 and N104 (also 66 & 67) for N101 'CA' to provide full carrier contactinformation. The Standard Carrier Alpha Code (SCAC) is recommended (TD502 '2'). ShipControl CarrierIdentifier domain TD502 TD503 /CarrierIdentifier Copyright (c) 1996–2014 Ariba, Inc. All rights reserved.11Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation GuidelinesTD50367TD504911D-U-N-S Number, Dun & Bradstreet2Standard Carrier Alpha Code (SCAC)4International Air Transport Association (IATA)Identification CodeX AN 2/80Code identifying a party or other codeTransportation Method/Type CodeX ID 1/2Code specifying the method or type of transportation for the shipment ShipControl Route method TD504 method (air motor rail ship)AJRSTD505387MO#REQUIREDAirmethod "air"Motormethod "motor"Railmethod "rail"Oceanmethod "ship"RoutingX AN 1/35MFree-form description of the routing or requested routing for shipment, or the originatingcarrier's identityCarrier's company name. Note that full carrierCorporate contact information can besupplied in an N1, in which N103 and N104 match TD502 and TD503. This level of detailis optional. If such an N1 is supplied, and N102 is provided, then N102 takes precedenceover TD505. The carrier company name is required, so if you're not providing full carriercontact information with N102, then TD505 is required. ShipControl CarrierIdentifier role "companyName" TD505 /CarrierIdentifier TD507309TD508310Location QualifierCode identifying type of locationOID 1/2ZZMutually DefinedLocation IdentifierX AN 1/30Code which identifies a specific locationCarrier assigned reference / tracking id for their part of the shipment.MMIdentifier that appears on this shipment and through which additional detail about theshipment may be retrieved. Defined by the carrier.Conceptually, this is a tracking number. Different carriers have different names forshipment identifiers. Some call it a way bill number, others call it a pro number, and stillothers call it a bill of lading. They all represent tracking numbers. ShipmentIdentification TD508 /ShipmentIdentification TD512284Service Level CodeX ID 2/2OCode indicating the level of transportation service or the billing service offered by thetransportation carrierAll ANSI X12 defined codes are allowed here. The description from the ANSI Standard ismapped into the ServiceLevel element.Refer to 004010 Data Element Dictionary for acceptable code values.Copyright (c) 1996–2014 Ariba, Inc. All rights reserved.12Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation GuidelinesSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Usage Notes:Notes:TD5Carrier Details (Transport Information)120HLMandatoryDetailOptional11To specify the carrier and sequence of routing and provide transit time information1 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.4 If TD510 is present, then TD511 is required.5 If TD513 is present, then TD512 is required.6 If TD514 is present, then TD513 is required.7 If TD515 is present, then TD512 is required.1 TD515 is the country where the service is to be performed.1 When specifying a routing sequence to be used for the shipment movement in lieu ofspecifying each carrier within the movement, use TD502 to identify the partyresponsible for defining the routing sequence, and use TD503 to identify the actualrouting sequence, specified by the party identified in structions produces. ShipNoticeRequest ShipControl TransportInformation Route method "motor" /Route ShippingContractNumber 12345 /ShippingContractNumber ShippingInstructions Description xml:lang "en" Instructions /Description /ShippingInstructions /TransportInformation ShipControl .The TD5 segment is also used for providing the transport information in theShipNoticeRequest. It is differentiated from carrier details by providing TD502 value ZZ.Data Element eUserNameAttributesAttributesIdentification Code QualifierX ID 1/2OCode designating the system/method of code structure used for Identification Code (67)ZZMutually DefinedIdentification CodeX AN 2/80OCode identifying a party or other codeThis element is used for shipping contract number.Transportation Method/Type CodeX ID 1/2OCode specifying the method or type of transportation for the shipment ShipControl TransportInformation Route method TD504 method (air motor rail ship)Copyright (c) 1996–2014 Ariba, Inc. All rights reserved.13Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation GuidelinesAJRSTD507309TD508310Airmethod "air"Motormethod "motor"Railmethod "rail"Oceanmethod "ship"Location QualifierO ID 1/2DCode identifying type of location. Required only if shipping instructions need to beprovided.ZZMutually DefinedLocation IdentifierX AN 1/30OCode which identifies a specific locationThis element is used to provide shipping instructions ShipControl TransportInformation ShippingInstructions Description xml:lang "en" Instructions /Description Copyright (c) 1996–2014 Ariba, Inc. All rights reserved.14Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation GuidelinesSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Usage Notes:Notes:TD4 Carrier Details (Carrier Identifier)140HLMandatoryDetailOptional1To specify transportation special handling requirements, or hazardous materialsinformation, or both.1 At least one of TD401, TD402 or TD404 is required.2 If TD402 is present, then TD403 is required.1 TD405 identifies if a Material Safety Data Sheet (MSDS) exists for this product. A"Y" indicates an MSDS exists for this product; an "N" indicates an MSDS does notexist for this YZ produces. ShipNoticeRequest ShipControl CarrierIdentifier domain "XYZ" UPS /CarrierIdentifier ShipControl .The TD4 segment is used for providing the carrier identifier information.Data Element NameAttributesAttributesSpecial Handling CodeX ID 2/3DCode specifying special transportation handling instructions. Required only if TD404 isused.ZZZMutually DefinedDescriptionX AN 1/80OA free-form description to specify the related data elements and their contentThis element is used for providing carrier identifier value alongwith the domain. Thedomain is prefixed by “@domain”The format for the value is CarrierIdentifier @domain Domain .e.g UPS@domainXYZ will be converted to CarrierIdentifier domain "XYZ" UPS /CarrierIdentifier Copyright (c) 1996–2014 Ariba, Inc. All rights reserved.15Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation GuidelinesSegment:Position:Loop:Level:Usage:Max Use:Purpose:Syntax Notes:Semantic Notes:Comments:Usage Notes:Notes:REFReference Identification150HLMandatoryDetailOptional4To specify identifying information1 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.1 REF04 contains data relating to the value cited in REF02.Used/OptionalExample:REF*AEC**US12345 Produces . IdReference domain "governmentNumber" identifier "US12345" /IdReference REF*D2**ASN001 Produces . IdReference domain "supplierReference" identifier "ASN001" /IdReference REF*DD**Partial Shipment Produces . IdReference domain "documentName" identifier "Partial Shipment" /IdReference REF*0L*FOB05*MyOwnTermsTransportTerms Produces . ShipNoticeRequest ShipNoticeHeader TermsOfDelivery TransportTerms value "Other" MyOwnTermsTransportTerms /TransportTerms This is an optional segment to specify IDReference information and custom transportterms.Data Element ibutesAttributesReference Identification QualifierM ID 2/3MCode qualifying the Reference Identification0LReferenced ByThis is used in conjunction with REF02 FOB05 to specify custom valuefor Transport terms.AECGovernment Registration Number IdReference domain "governmentNumber" identifier "US12345" Copyright (c) 1996–2014 Ariba, Inc. All rights reserved.16Revised 29 September 2014
Ariba, Inc. cXML 1.2: ANSI X12 004010 856 Ship Notice / Manifest Implementation Guidelines /IdReference Supplier Document Identification Number IdReference domain "supplierReference" identifier "TestSupplyRef" /IdReference DDDocument Identification Code IdReference domain "documentName" identifier "TestDocName" /IdReference Reference IdentificationX AN 1/30OReference information as defined for a particular transaction set or as specified by theReference Identification QualifierFOB5Used to specify custom value for Transport terms.DescriptionX AN 1/80OA free-form description
As a service to Suppliers preferring to transact via EDI, Ariba Network accepts the ANSI X12 004010 856 Ship Notice / Manifest document. On receiving the 856 (documented here), Ariba Network validates the EDI content, returns a 997 to the Supplier, . In reading this Implementation Guide, the following usage codes are used: Status Segment .
