EDI Specifications Guide. 856 Supplier Advance Ship Notice Last updated February 2017

Transcription

1 856 Supplier Advance Ship Notice Last updated February 2017

2 856 Ship Notice/Manifest - Functional Group=SH VER FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific Supplier Ship Notice/Manifest 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: Pos Id Segment Name Req Max Use Repeat Notes 010 ST Transaction Set Header M BSN Beginning Segment for Ship Notice M 1 Detail: Pos Id Segment Name Req Max Use Repeat LOOP ID - HLS HL Hierarchical Level - Shipment M 1 Carrier Details (Routing 120 TD5 Sequence/TransitTime) O REF Reference Identification O REF Reference Identification O DTM Date/Time Reference M 1 LOOP-ID N1 200 N1 Name LOOP ID - HLO HL Hierarchical Level - Order M PRF Purchase Order Reference M REF Reference Identification M 1 LOOP-ID -HLT or HLP HL Hierarchical Level Tare or Pack M MAN Marks and Numbers C >1 LOOP-ID - HLI HL Hierarchical Level Item M LIN Item Identification M SN1 Item Detail (Shipment) M SLN Sub-line Item detail C DTM Date/Time Reference C 1 Summary: Pos Id Segment Name Req Max Use Repeat 010 CTT Transaction Totals O SE Transaction Set Trailer M 1 *997 Will be sent back for all 856 s

3 ST Transaction Set Header Pos: 010 Max: 1 Heading - Mandatory Loop: N/A Elements: 2 To indicate the start of a transaction set and to assign a control number ST Transaction Set Identifier Code M ID 3/3 856 Ship Notice/Manifest ST Transaction Set Control Number M AN 4/9 Semantics: 1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects th Invoice Transaction Set).

4 BSN Beginning Segment for Ship Notice Pos: 020 Max: 1 Heading - Mandatory Loop: N/A Elements: 5 To transmit identifying numbers, dates, and other basic data relating to the transaction set BSN Transaction Set Purpose Code M ID 2/2 00 Original BSN Shipment Identification M AN 2/30 BSN Date M DT 8/8 BSN Time M TM 4/8 BSN Hierarchical Structure Code O ID 4/ Shipment,Packaging, Item Semantics: 1. BSN03 is the date the shipment transaction set is created. 2. BSN04 is the time the shipment transaction set is created.

5 HL Hierarchical Level - Shipment Pos: 010 Max: 1 Detail - Mandatory Loop: HL Elements: 4 To identify dependencies among and the content of hierarchically related groups of data segments HL Hierarchical ID Number M AN 1/12 HL Hierarchical Parent ID Number O AN 1/12 HL Hierarchical Level Code M ID 1/2 S Shipment HL Hierarchical Child Code O ID 1/1 Comments: 1. 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. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent 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 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 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Notes: *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ Sample HL (Shipment Level) Segment HL*1**S ************************

6 TD5 Carrier Details (Routing Sequence/Transit Time) Pos: 120 Max: 12 Heading - Mandatory Loop: HL - Shipment Elements: 5 To specify the carrier and sequence of routing and provide transit time information TD Routing Sequence Code M ID 1/2 B Origin/Delivery Carrier TD Identification Code Qualifier M ID 1/2 Comments: When specifying a routing sequence to be used for the shipment movement in lieu of Specifying each carrier 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. Syntax Rules: 1. R At least one of the TD502, TD504, TD505, TD506 or TD512 is required. 2. C0203 If TD502 is present, then TD503 is required. Notes: TD502 - The Standard Carrier Alpha Code (SCAC) is a unique two-to-four-letter code used to identify a carrier. Carrier SCAC codes are assigned and maintained by the MFTA (National Motor Freight Association). To obtain a SCAC code or the list of all carrier SCAC codes contact the NMFTA.. Correct information is necessary for matching to the corresponding EDI 214 Carrier Shipment Status Message. Sample TD5 Segment TD5*B*2*SOCS*C*Consolidator Name (consolidator example) TD5*B*2*RDWY*M (truckload or LTL carrier example) TD5*B*2*RPSI*U*RPS (private parcel example) If TD504='C', TD505=name of consolidator 2 Standard Carrier Alpha Code (SCAC) TD Identification Code M AN 4/4 TD Transportation Method/Type Code C ID 1/2 A Air C Consolidation M Motor (Common Carrier) U Private Parcel Service AE Air Express CE Customer Pickup L Contract Carrier P Private Carrier TD Routing M AN 1/80 If TD504='U', TD505='UPS' or 'RPS'

7 REF Reference Identification Pos: 150 Max: 1 Detail - Optional Loop: HL - Shipment Elements: 2 To specify identifying information REF Reference Identification Qualifier M ID 2/2 BM - Bill of Lading Number REF Reference Identification M AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Notes: 1. REF02 - Bill of Lading (BOL) reference number is required for truckload and less than truckload (LTL) shipments. BOL reference number is the unique number assigned by the shipper in creating the Bill of Lading. This is a number that identifies a unique shipment. ******************************** Samples of REF Segment REF*BM*30582 ********************************

8 REF Reference Identification Pos: 150 Max: 1 Detail - Optional Loop: HL - Shipment Elements: 2 To specify identifying information REF Reference Identification Qualifier M ID 2/2 CN Carrier s Reference Number PRO/Invoice) REF Reference Identification M AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Notes: 1. CN is used to qualify the following values: carrier PRO Number for LTL and TL Carriers carrier tracking number for small parcel carriers ******************************** Samples of REF Segment Pro Number REF*CN* Tracking Number REF*CN*1ZE1628E *********************************

9 DTM Date/Time Reference Pos: 200 Max: 10 Heading - Mandatory Loop: HL - Shipment Elements: 4 To specify pertinent dates and times DTM Date/Time Qualifier M ID 3/3 011 Shipped DTM Date C DT 8/8 DTM Time C TM 4/8 DTM Time Code O ID 2/2 ES Eastern Standard Time Syntax: 1. 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 are present, then the others are required. Notes: ************************** Sample DTM Segment DTM*011* **************************

10 N1 Name EDI Specifications Guide Pos: 310 Max: 1 Heading - Optional Loop: HL - Shipment / N1 Elements: 4 To identify a party by type of organization, name, and code Notes N Entity Identifier Code M AN 2/3 N/98 BT Bill To Party ST Ship To SF Ship From VN Vendor N Name C AN 1/60 N Identification Code Qualifier 92 Assigned by Buyer or Buyer's Agent C AN 1/2 N Identification Code C AN 2/80 Syntax: 1. R At least one of N102 or N103 is required. 2. P If either N103 or N104 are present, then the others are 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 the transaction processing party. Notes: N/98 Please refer to EDI Services Guide for additional requirements. Important: The N1, N3 and N4 for the Ship From and Ship To are required.

11 N2 Additional Name Information Pos: 320 Max: 2 Heading - Optional Loop: HL Shipment / N1 Elements: 2 To specify additional names or those longer than 35 characters in length N Name M AN 1/25 N Name O AN 1/25

12 N3 Address Information Pos: 330 Max: 2 Heading - Optional Loop: HL Shipment / N1 Elements: 2 To specify the location of the named party N Address Information M AN 1/25 N Address Information O AN 1/25

13 N4 Geographic Location EDI Specifications Guide Pos: 340 Max: >1 Heading - Optional Loop: HL Shipment / N1 Elements: 3 To specify the geographic place of the named party N City Name M AN 2/30 N State or Province Code M AN 2/2 N Postal Code M AN 3/15 Syntax: 1. C If N406 is present, than N405 is required Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location. 2. N402 is required only if city name (N401) is in the U.S. or Canada.

14 HL Hierarchical Level - Order EDI Specifications Guide Pos: 010 Max: 1 Detail - Mandatory Loop: HL Elements: 4 To identify dependencies among and the content of hierarchically related groups of data segments HL Hierarchical ID Number M AN 1/12 HL Hierarchical Parent ID Number M AN 1/12 HL Hierarchical Level Code M ID 1/2 O Order HL Hierarchical Child Code O ID 1/1 Comments: 7. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating lineitem data to shipment data, and packaging data to line-item data. 8. The HL segment defines a top-down/left-right ordered structure. 9. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction. 10. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 11. 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. 12. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Notes: *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ Sample HL (Order Level) Segment HL*2*1*O An HL at Order Level must be sent for every Mark for Location. ************************

15 PRF Purchase Order Reference Pos: 050 Max: 1 Heading - Optional Loop: HL - Order Elements: 1 To provide reference to a specific purchase order PRF Purchase Order Number M AN 1/22 Identifying number for Purchase Order assigned by the Buyer/Purchaser Identifying number sent on 850 Purchase Order in the BEG03 segment. Notes: *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ Sample PRF Segment PRF*PR PRF*DR ************************

16 REF Reference Identification Pos: 150 Max: 1 Detail - Mandatory Loop: HL - Order Elements: 2 To specify identifying information REF Reference Identification Qualifier M ID 2/2 PO End Customer s Purchase Order Number REF Reference Identification C AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Notes: 1. If REF01 is present REF02 is required MANDATORY ONLY if the Purchase Order is a Drop Ship; we do not send a customer order number on the 850 for warehouse orders.

17 REF Reference Identification Pos: 150 Max: 1 Detail - Optional Loop: HL - Order Elements: 2 To specify identifying information REF Reference Identification Qualifier O ID 2/2 VN Vendor Number REF Reference Identification O AN 1/30 Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

18 HL Hierarchical Level Pack or Tare Pos: 010 Max: 1 Detail - Mandatory Loop: HL Elements: 4 To identify dependencies among and the content of hierarchically related groups of data segments HL Hierarchical ID Number M AN 1/12 HL Hierarchical Parent ID Number M AN 1/12 HL Hierarchical Level Code M ID 1/2 P Pack T Shipping Tare HL Hierarchical Child Code O ID 1/1 Comments: 13. 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. 14. The HL segment defines a top-down/left-right ordered structure. 15. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction. 16. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 17. 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. 18. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Notes: *Pallet Level is Preferred *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ Sample HL (Pack or Tare Level) Segment HL*4*3*P or HL*4*3*T ************************

19 MAN Marks and Numbers Pos: 190 Max: >1 Detail - Optional Loop: HL Pack or Tare Elements: 2 To indicate identifying marks and numbers for shipping containers Notes MAN01 88 Marks and Numbers Qualifier M ID 1/2 N/88 CP Carrier-Assigned Package ID Number GM SSCC-18 and Application Identifier (Pallet ID) SM Shipper Assigned (Tracking Number) MAN02 87 Marks and Numbers M AN 1/48 Semantics: 1. MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container. 2. When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range. Comments: 1. When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 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 MAN05/MAN06. Notes: N/88 Please refer to EDI Services Guide for additional requirements.

20 HL Hierarchical Level - Item Pos: 010 Max: 1 Detail - Mandatory Loop: HL Elements: 4 To identify dependencies among and the content of hierarchically related groups of data segments HL Hierarchical ID Number M AN 1/12 HL Hierarchical Parent ID Number O AN 1/12 HL Hierarchical Level Code M ID 1/2 I Item HL Hierarchical Child Code O ID 1/1 Comments: 19. 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. 20. The HL segment defines a top-down/left-right ordered structure. 21. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction. 22. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 23. 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. 24. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Notes: *Warning: Segment includes critical data elements. Please ensure accuracy to avoid document suspension and/or loss of data. ************************ Sample HL (Item Level) Segment HL*5*4*I ************************

21

22 LIN Item Identification EDI Specifications Guide Pos: 020 Max: 1 Detail - Mandatory Loop: HL - Item Elements: 3 To specify basic item identification data LIN Assigned Identification O AN 1/20 LIN Product/Service ID Qualifier M ID 2/2 CB Buyer's Catalog Number LIN Product/Service ID M AN 1/48 LIN Product/Service ID Qualifier M ID 2/2 VC Vendor s (Seller s) Catalog Number LIN Product/Service ID M AN 1/48 Semantics: 1. LIN01 is the line item identification Comments: 1. See the Data Dictionary for a complete list of IDs. 2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

23 SN1 Item Detail (Shipment) Pos: 030 Max: 1 Detail - Optional Loop: HL - Item Elements: 3 To specify line-item detail relative to shipment SN Assigned Identification O AN 1/20 SN Number of Units Shipped M N3 1/10 SN Unit or Basis for Measurement Code M ID 2/2 BX Box CA Case EA Each PH Package PR Pair Semantics: 1. SN101 is the ship notice line-item identification. Comments: 1. SN103 defines the unit of measurement for both SN102 and SN SN103 - UOM must match what was sent on the 850 in the PO103.

24 SLN Subline Item Detail Pos: 040 Max: 100 Detail - Optional Loop: HL - Item Elements: 5 To specify product subline detail item data Notes SLN Assigned Identification M AN 1/20 N/350 SLN Assigned Identification O AN 1/20 SLN Relationship Code M ID 1/1 I Included SLN Product/Service ID Qualifier M ID 2/2 LT Lot Number SLN Product/Service ID M AN 1/48 Syntax: 1. SLN09 -- If either SLN09 or SLN10 are present, then the others are required. Semantics: 1. SLN01 is the identifying number for the subline item. 2. SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials. 3. SLN03 is the configuration code indicating the relationship of the subline item to the baseline item. Comments: 1. See the Data Element Dictionary for a complete list of IDs. 2. SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number SLN09 through SLN28 provide for ten different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU. 4. If Supplier items are Lot controlled, the SLN segment will be required for them. Notes: **************************** Sample SLN Segment SLN*1**I******LT* ****************************

25 PID Product/Item Description EDI Specifications Guide Pos: 050 Max: 1 Detail - Optional Loop: HL Item / PID Elements: 4 To describe a product or process in coded or free-form format PID Item Description Type M ID 1/1 F Free-form PID Product/Process Characteristic Code O ID 2/3 08 Product PID Agency Qualifier Code C ID 2/2 ZZ Mutually Defined PID Description C AN 1/80 Semantics: 1. Use PID03 to indicate the organization that publishes the code list being referred to Comments: 1. If PID01 equals F, then PID05 is used. If PID01 equals S, then PID04 is used. If PID01 equals X, then both PID04 and PID05 are used.

26 DTM Date/Time Reference Pos: 200 Max: 10 Detail - Optional Loop: HL - Item Elements: 2 To specify pertinent dates and times DTM Date/Time Qualifier M ID 3/3 036 Lot Expiration Date Expiration date required based on Distribution Center Shipments, which are based on Thermo Fisher item setup designation as expiration date controlled product. DTM Date Date expressed as CCYYMMDD C DT 8/8 If lot number does not have an expiration date, please use in the DTM02 as a default. Syntax: 1. At least one of DTM02, DTM03 or DTM05 is required. 2. If DTM04 is present, than DTM03 is required 3. If either DTM05 or DTM06 are present, then the others are required. Notes: ************************ Sample DTM Segment DTM*036* ***********************

27

28 CTT Transaction Totals Pos: 010 Max: 1 Summary - Optional Loop: N/A Elements: 2 To transmit a hash total for a specific element in the transaction set CTT Number of Line Items M N0 1/6 CTT Hash Total O R 1/10 Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness Notes: The number of HL segments present in the transaction set.

29 SE Transaction Set Header Pos: 030 Max: 1 Summary - Mandatory Loop: N/A Elements: 2 To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) SE01 96 Number of Included Segments M N0 1/10 SE Transaction Set Control Number M AN 4/9 Comments: 1. SE is the last segment of each transaction set.

30 Below is a complete example of a Shipment/Pallet Level 856 transmission: Pallet Level Preferred Method ISA*00* *00* *99* *14* IBMP *141212*0150*U*00400* *0*P*> GS*SH* * * *0150*999999*X* ST*856* BSN*00* * *0145*0001 HL*1*0*S TD5*B*2*UPSN*M*UPS REF*BM* REF*CN*1Z DTM*011* N1*SF*NAME N3*99 SOMEWHERE PLACE N4*CITY*ST*99999 N1*ST*XYZ COMPANY*92* EMD N3*123 EASY STREET N4*CITY*ST*15275 HL*2*1*O PRF*PR HL*3*2*T MAN*GM* HL*4*3*I LIN*1*VC* SN1**8*PK SLN*1**I******LT* PID*F****LEVINE EMB AGAR 20/PK DTM*036* HL*5*3*I LIN*2*VC* SN1**2*PK SLN*2**I******LT* PID*F****COOKED MEAT W/GLUCOSE 10/PK DTM*036* HL*6*3*I LIN*3*VC* SN1**3*PK SLN*3**I******LT* PID*F****THIOGY MED W/O INDICATR 10/PK DTM*036* CTT*6 SE*35* GE*1* IEA*1*

31 Shipment/Parcel Level One tracking number per ASN ISA*00* *00* *99* *14* IBMP *141211*2308*U*00401* *0*P*> GS*SH* * * *2308*9999*X* ST*856*9999 BSN*00* * *1707*0001 HL*1**S TD5*B*2*UPSN*M*UPS REF*CN*1Z DTM*011* N1*SF*VENDOR NAME N3*987 BRADY STREET N4*SOMETOWN*PA*16061 N1*ST*XYZ COMPANY*92* EMD N3*123 EASY STREET N4*ANYTOWN*PA*15275 HL*2*1*O PRF*DR REF*PO* HL*4*3*I LIN*001*VC* SN1**2*EA PID*F****SCALE 6KG X 0.2G CTT*4 SE*22*9999 GE*1*9999 IEA*1*

32 Shipment/Parcel Level - Multiple tracking numbers ISA*00* *00* *99* *14* IBMP *141211*2308*U*00401* *0*P*> GS*SH* * * *2308*9999*X* ST*856*9999 BSN*00* * *1707*0001 HL*1**S TD5*B*2*UPSN*M*UPS DTM*011* N1*SF*VENDOR NAME N3*987 BRADY STREET N4*SOMETOWN*PA*16061 N1*ST*XYZ COMPANY*92* EMD N3*123 EASY STREET N4*ANYTOWN*PA*15275 HL*2*1*O PRF*DR REF*PO* HL*3*2*P MAN*SM*1Z HL*4*3*I LIN*001*VC* SN1**2*EA PID*F****SCALE 6KG X 0.2G HL*5*2*P MAN*SM*1Z HL*6*3*I LIN*001*VC* SN1**2*EA PID*F****SCALE 6KG X 0.2G CTT*4 SE*29*9999 GE*1*9999 IEA*1* Example of 997 to be sent back to Supplier Functional Acknowledgement ISA*00* *00* *ZZ* *09* VNDP *151117*0010*U*00401* *0*P*> GS*FA* * IBMP* *001001*17232*X* ST*997*00001 AK2*850* AK5*A AK9*A*1*1*1 SE*5*00001 GE*1*17232 IEA*1*