EDI Specifications Advance Ship Notice (Supplier v4010)

Transcription

1 (Supplier v400) December 200

2 856 Ship Notice/anifest- Functional Group=SH VER. 400 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific Customer Ship Notice/anifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. Please refer to the EDI Services Guide for additional information. All information contained herein is subject to change at the discretion of Fisher Scientific Company, L.L.C. Heading: PS ax Use 00 ST Transaction Set Header 020 BSN Beginning Segment for Ship Notice 040 DT Date/Time erence 0 ax Use Repeat Repeat Detail: PS LP - HL HL Hierarchical Level 020 LIN Item Identification 030 SN Item Detail (Shipment) 040 SLN Subline Item Detail PRF Purchase rder erence 90 arks and Numbers > C2/00 Summary: PS ax Use 00 CTT Transaction Totals 030 SE Transaction Set Trailer Repeat N/00 Comments: 2/00 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning. : /00 Number of line items (CTT0) is the accumulation of the number of HL segments. If used, hash total (CTT02) is the sum of the value of units shipped (SN02) for each SN segment. Page 2

3 ST PS: 00 ax: Heading - andatory Loop: N/A Elements: 2 Transaction Set Header To indicate the start of a transaction set and to assign a control number. in/ax ST0 43 Transaction Set Identifier Code 856 Ship Notice/anifest 3/3 ST Transaction Set Control Number 4/9 Semantics: The transaction set identifier (ST0) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 80 selects the Invoice Transaction Set). Page 3

4 BSN Beginning Segment for Ship Notice PS: 020 ax: Heading - andatory Loop: N/A Elements: 5 To transmit identifying numbers, dates, and other basic data relating to the transaction set. in/ax BSN0 353 Transaction Set Purpose Code 00 riginal 2/2 BSN Shipment Identification 2/30 B Date DT 8/8 BSN Time T 4/8 BSN Hierarchical Structure Code 000 Shipment, Packaging, Item Semantics: BSN03 is the date the shipment transaction set is created. 2. BSN04 is the time the shipment transaction set is created. Page 4

5 DT Date/Time erence PS: 040 ax: 0 Heading - ptional Loop: N/A Elements: 4 To specify pertinent dates and times. in/ax DT0 374 Date/Time Qualifier 0 Shipped 3/3 DT Date C DT 8/8 DT Time C T 4/8 DT Time Code ES Eastern Standard Time 2/2 Syntax: R At least one of DT02, DT03 or DT05 is required. 2. C If DT04 is present, than DT03 is required 3. P If either DT05 or DT06 are present, then the others are required. Page 5

6 HL Hierarchical Level PS: 00 ax: Detail - andatory Loop: HL Elements: 4 To identify dependencies among and the content of hierarchically related groups of data segments. in/ax HL0 628 Hierarchical Number /2 HL Hierarchical Parent Number /2 HL Hierarchical Level Code I Item rder P Pack S Shipment T Shipping Tar /2 HL Hierarchical Child Code 0 No Subordinate HL Segment in this Hierarchical Structure Additional Subordinate HL Data Segment in this Hierarchical Structure / Comments: The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating 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. HL0 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL0 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL0 would be for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction. 4. HL02 identifies the hierarchical 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 of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information. 6. HL04 indicated whether or not there are subordinate (or child) HL segments related to the current HL segment. Page 6

7 LIN Item Identification PS: 020 ax: Detail - ptional Loop: HL Elements: 3 To specify basic item identification data. in/ax LIN0 350 Assigned Identification /20 LIN Product/Service Qualifier VP Vendor s (Seller s) Part Number CB Buyer s Catalog Number 2/2 LIN Product/Service /48 Semantics LIN0 is the line item identification. Comments: See the data Dictionary for a complete list of s. 2. LIN02 through LIN3 provide for fifteen different product/service s for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., odel No., or SKU. Page 7

8 SN Item Detail (Shipment) PS: 030 ax: Detail - ptional Loop: HL Elements: 3 To specify line-item detail relative to shipment. in/ax SN0 350 Assigned Identification /20 SN Number of Units Shipped R /0 SN Unit or Basis for easurement Code CA Case EA Each GR Gram PC Piece PK Package 2/2 Semantics SN0 is the ship notice line-item identification. Comments: SN03 defines the unit of measurement for both SN02 and SN04. Page 8

9 SLN PS: 040 ax: 000 Detail - ptional Loop: HL Elements: 5 Subline Item Detail To specify the location of the named party. in/ax SLN0 350 Assigned Identification /20 SLN Assigned Identification /20 SLN Relationship Code Included / SLN Product/Service Qualifier LT Lot Number C 2/2 SLN0 234 Product/Service C /48 N/350 Syntax: SLN09 If either SLN09 or SLN0 are present, then the others are required. Semantics SLN0 is the identifying number for the subline item. 2. SLN02 is the identifying number for the subline item. The subline level is analogous to the level code used in a bill of material. 3. SLN03 is the configuration code indicating the relationship of the subline item to the baseline item. Comments: See the Data Element Dictionary for a complete list of S. 2. SLN0 is related to (but non necessarily equivalent to) the baseline item number. Example: or A might be used as a subline number to relate to baseline number 3. SLN09 through SLN28 provide for ten different product/service s for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., odel No., or SKU. : N/350 Please refer to EDI Services Guide for additional requirements. Page 9

10 PRF Purchase rder erence PS: 050 ax: Detail - ptional Loop: HL Elements: 3 To provide reference to a specific purchase order. PRF0 324 in/ax /22 N/324 Purchase rder Number N/324 Please refer to the EDI Services Guide for additional requirements. Page 0

11 arks and Numbers PS: 90 ax: > Detail - ptional Loop: HL Elements: 3 To indicate identifying marks and numbers for shipping containers. in/ax 0 88 arks and Numbers Qualifier G SSCC-8 and Application Identifier S Shipper Assigned / arks and Numbers /48 N/88 Semantics: 0/02 and 04/05 may be used to identify two different marks and numbers assigned to the same physical container. 2. When both 02 and 03 are used, 02 is the starting number of a sequential range and 03 is the ending number of that range. Comments; When 0 contains code "UC" (U.P.C. Shipping Container Code) and 05/06 contain a range of numbers, 03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in 05/06. N/88 Please refer to the EDI Services Guide for additional requirements. Page

12 CTT PS: 00 ax: Summary - ptional Loop: N/A Elements: 2 Transaction Totals To transmit a hash total for a specific element in the transaction set. in/ax CTT0 354 Number o Line Items N0 /6 CTT Hash Total R /0 Comments: This segment is intended to provide hash totals to validate transaction completeness and correctness. Page 2

13 SE PS: 020 ax: Summary - andatory Loop: N/A Elements: 2 Transaction Set Trailer To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) in/ax SE0 96 Number of Included Segments N0 /0 SE Transaction Set Control Number 4/9 Comments: SE is the last segment of each transaction set. Page 3

14 Sample 856: Below is a complete example of an 856 transmission: Shipment Level ISA*00* *00* *ZZ* *4* IBP *070920*0849*U*0040* *0*P*> GS*SH* * * *0849*2467*X*00400 ST*856*259 BSN*00*222253* *5902*000 HL***S DT*0* HL*2** PRF*DR HL*3*2*P *S*Z54242X HL*4*3*I LIN*00*CB*2590 SN*00*2*EA CTT*4 SE*3*259 GE**2467 IEA** Pallet Level ISA*00* *00* *ZZ* *4* IBP *070920*0849*U*0040* *0*P*> GS*SH* * * *0849*2467*X*00400 ST*856*259 BSN*00*222253* *5902*000 HL***S DT*0* HL*2*** PRF*DR HL*3*2*T* *S*Z54242X HL*4*3*I* LIN*00*CB*2590 SN*00*2*EA CTT*4 SE*3*259 GE**2467 IEA** Page 4