856 Ship Notice/Manifest

Size: px
Start display at page:

Download "856 Ship Notice/Manifest"

Transcription

1 856 Ship Notice/Manifest Functional Group ID=SH Introduction: KOSTAL 4010 Inbound 856 Trading Partner Specs Heading: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments Must Use 010 ST Transaction Set Header M 1 Must Use 020 BSN Beginning Segment for Ship Notice M 1 Must Use 040 DTM Date / Time Reference M 10 Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - HL Must Use 010 HL Hierarchical Level M 1 Must Use 100 MEA Measurements M 2 Must Use 110 TD1 Carrier Details (Quantity and Weight) M TD5 Carrier Details (Routing Sequence/Transit O 12 Time) 130 TD3 Carrier Details (Equipment) O 12 Must Use 150 REF Reference Identification O >1 Must Use 150 REF Reference Identification O >1 LOOP ID N N1 Name O LOOP ID HL Must Use 020 HL Hierarchical Level M LIN Item Identification O SN1 Item Detail (Shipment) O PRF Purchase Order Reference 070 PID Product/Item Description 150 REF Reference Identification LOOP ID CLD 170 CLD Load Detail Must Use 010 LOOP ID HL LIN Item Identification O SN1 Item Detail (Shipment) O REF Reference Numbers Summary: reserved

2 Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments 020 CTT Transaction Set Trailer O 1 Must Use 020 SE Transaction Set Trailer M 1 Transaction Set Comments 1. The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.

3 1. Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To indicate the start of a transaction set and to assign a control number Syntax Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). Comments: >> ST Transaction Set Identifier Code M ID 3/3 Value 856 >> ST Transaction Set Control Number M AN 4/9 Sequentially assigned by sender, starting at

4 Segment: BSN Beginning Segment for Ship Notice Position: 020 Loop: Level: Heading Usage: Mandatory Max Use: 1 Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set Syntax Notes: 1 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. >> BSN Transaction Set Purpose Code M ID 2/2 Valid values: 00 Original 01 Cancellation (deletion) 04 Change >> BSN Shipment Identification Packing Slip number M AN 2/30 >> BSN Date Dispatch Advice (ASN) Date M DT 8/8 >> BSN Time Dispatch Advice (ASN) Time M TM 4/8 Not used BSN Hierarchical Structure Code O ID 4/4 Not used BSN Transaction Type Code X ID 2/2 Not used BSN Status Reason Code O ID 3/3

5 Segment: DTM Date/Time Reference Position: 040 Loop: Level: Heading Max Use: 10 Purpose: To specify pertinent dates and times Syntax Notes: 1 At least one of DTM02 DTM03 or DTM05 is required. Comments: >> DTM Date/Time Qualifier M ID 3/3 Value 011 Shipped Value 017 Arrived DTM Date X DT 8/8 Dispatch Date DTM Time X TM 4/8 Dispatch Time Not used DTM Time Code O ID 2/2 Not used DTM Date Time Period Format Qualifier X ID 2/3 Not used DTM Date Time Period X AN 1/35

6 Segment: HL Hierarchical Level Position: 010 Loop: HL Mandatory Usage: Mandatory Max Use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data segments Syntax Notes: 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. The HL segment defines a top-down/left-right ordered structure. 2 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. 3 HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 4 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. 5 HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Notes: Hierarchy can be either Shipment or Item levels. One Shipment level, followed by one or more Item levels. This order may be repeated. >> HL Hierarchical ID Number M AN 1/12 Sequentially numbered, starting with 1 Not used HL Hierarchical Parent ID Number O AN 1/12 >> HL Hierarchical Level Code M ID 1/2 Value S Shipment Not used HL Hierarchical Child Code O ID 1/1

7 Segment: MEA Measurements Position: 100 Loop: - Shipment Usage: Mandatory Max Use: 2/HL Purpose: To specify physical measurements Syntax Notes: Comments: MEA segment is used to transmit the physical weight of the shipment. At least one occurrence of the MEA is required, to transmit the Gross Weight of the Shipment. MEA Measurement Reference ID Code M ID 2/2 PD Physical Dimensions MEA Measurement Qualifier M ID 1/3 G Gross weight N Net weight MEA Measurement Value M R 1/20 Weight MEA04 C001 Composite Unit of Measure M LB Pound KG - Kilograms Not used MEA Range Minimum X R 1/20 Not used MEA Range Maximum X R 1/20 Not used MEA Measurement Significance Code X ID 2/2 Not used MEA Measurement Attribute Code X ID 2/2 Not used MEA Surface / Layer / Position Code X ID 2/2 Not used MEA Measurement Method or Device X ID 2/4 reserved

8 Segment: TD1 Carrier Details ( Quantity and Weight) Position: 110 Loop: - Shipment Usage: Mandatory Max Use: 1/HL Purpose: To specify the transportation details relative to commodity, weight and quantity Syntax Notes: Comments: Used to indicate the total number of loose packages. For example: 12 boxes shrink wrapped to 5 pallets plus 2 bins would have a TD101 of CNT71 and a TD102 of 7. TD Packaging Code M AN 3/5 BOX25 Boxes TD Lading Quantity M N0 1/7 Total Number of loose packages TD Commodity Code Qualifier X ID 1/1 TD Commodity Code X AN 1/30 Not used TD Lading Description X AN 1/50 Not used TD Weight Qualifier X ID 1/2 Not used TD Weight X R 1/10 Not used TD Unit or Basis for Measurements Code X ID 2/2 Not used TD Volume X ID 1/8 Not used TD Unit or Basis for Measurements Code X ID 2/2 reserved

9 Segment: TD5 Carrier Details (Routing Sequence/Transit Time) Position: 120 Loop: HL Mandatory Max Use: 12 Purpose: To specify the carrier and sequence of routing and provide transit time information Syntax Notes: 1 At least one of TD502 TD504 TD505 TD506 or TD512 is required. 2 If TD502 is present, then TD503 is required. Comments: 1 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. Notes: Used only for Shipment level, HL03 = "S". TD Routing Sequence Code O ID 1/2 Value B Origin/Delivery Carrier TD Identification Code Qualifier X ID 1/2 Value 02 Standard Alpha Carrier Code (SCAC) TD Identification Code X AN 2/80 Standard Alpha Carrier Code (SCAC) TD Transportation Method/Type Code X ID 1/2 Value A Air Value M - Motor (Common Carrier) Value S - Sea / Ocean Not used TD Routing X AN 1/35 Not used TD Shipment/Order Status Code X ID 2/2 Not used TD Location Qualifier O ID 1/2 Not used TD Location Identifier X AN 1/30 Not used TD Transit Direction Code O ID 2/2 Not used TD Transit Time Direction Qualifier O ID 2/2 Not used TD Transit Time X R 1/4 Not used TD Service Level Code X ID 2/2 Not used TD Service Level Code X ID 2/2 Not used TD Service Level Code O ID 2/2 Not used TD Country Code O ID 2/3 reserved

10 Segment: TD3 Carrier Details (Equipment) Position: 130 Loop: HL Mandatory Max Use: 12 Purpose: To specify transportation details relating to the equipment used by the carrier Syntax Notes: Comments: Notes: Used only for Shipment level, HL03 = "S". TD Equipment Description Code X ID 2/2 Value CN Container Value AR - Airways Not used TD303 TD Equipment Number Equipment Initial X AN 1/10 O AN 1/4 Trailer ID / Airway Bill Number Not used TD Weight Qualifier O ID 1/2 Not used TD Weight X R 1/10 Not used TD Unit or Basis for Measurement Code X ID 2/2 Not used TD Ownership Code O ID 1/1 Not used TD Seal Status Code O ID 2/2 Not used TD Seal Number O AN 2/15 Not used TD Equipment Type X ID 4/4

11 Segment: REF Reference Identification Position: 150 Loop: HL Mandatory Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Comments: Notes: Used only at Shipment level, HL03 = "S". >> REF Reference Identification Qualifier M ID 2/3 Value BM Bill of Lading Number Value PK Packing slip Number REF Reference Identification X AN 1/30 Bill of Lading Number Packing Slip Not used Not used REF03 REF C040 Description Reference Identifier X AN 1/80 O Not used C Reference Identification Qualifier M ID 2/3 Not used C Reference Identification M AN 1/30 Not used C Reference Identification Qualifier X ID 2/3 Not used C Reference Identification X AN 1/30 Not used C Reference Identification Qualifier X ID 2/3 Not used C Reference Identification X AN 1/30

12 Segment: N1 Name Position: 220 Loop: N1 Optional Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 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 the transaction processing party. Notes: Used only for Shipment level, HL03 = "S". >> N Entity Identifier Code M ID 2/3 Value ST Plant Value SF Supplier/Manufacturer Not used N102 N Name Identification Code Qualifier X AN 1/60 X ID 1/2 Value 92 Assigned by Buyer N Identification Code X AN 2/80 Supplier Identification Code Not used Not used N105 N Entity Relationship Code Entity Identifier Code O ID 2/2 O ID 2/3

13 Segment: HL Hierarchical Level Position: 010 Loop: HL Mandatory Usage: Mandatory Max Use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data segments Syntax Notes: 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. The HL segment defines a top-down/left-right ordered structure. 2 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. 3 HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 4 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. 5 HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Notes: Hierarchy can be either Shipment or Item levels. One Shipment level, followed by one or more Item levels. This order may be repeated. >> HL Hierarchical ID Number M AN 1/12 Sequentially numbered, starting with 1 Not used HL Hierarchical Parent ID Number O AN 1/12 >> HL Hierarchical Level Code M ID 1/2 Value I Item Not used HL Hierarchical Child Code O ID 1/1

14 Segment: LIN Item Identification Position: 020 Loop: HL Mandatory Max Use: 1 Purpose: To specify basic item identification data Syntax Notes: 1 If either LIN04 or LIN05 is present, then the other is required. 6 If either LIN14 or LIN15 is present, then the other is required. 7 If either LIN16 or LIN17 is present, then the other is required. 1 LIN01 is the line item identification Comments: Notes: Used only for Item level, HL03 = "I". Not used LIN Assigned Identification O AN 1/20 LIN Product/Service ID Qualifier M ID 2/2 Value BP Buyer s Part Number LIN Product/Service ID Customer Material Number M AN 1/48 LIN Product/Service ID Qualifier X ID 2/2 Value B8 --- Batch Number LIN Product/Service ID X AN 1/48 Batch Number Not Used LIN Product/Service ID Qualifier M ID 2/2 Not Used LIN Product/Service ID M AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48

15 Segment: SN1 Item Detail (Shipment) Position: 030 Loop: HL Mandatory Max Use: 1 Purpose: To specify line-item detail relative to shipment Syntax Notes: 1 SN101 is the ship notice line-item identification. Comments: 1 SN103 defines the unit of measurement for both SN102 and SN104. Notes: Used only for Item level, HL03 = "I". Not used SN Assigned Identification O AN 1/20 >> SN Number of Units Shipped M R 1/10 Number of Units Shipped >> SN Unit or Basis for Measurement Code Value PC Pieces M ID 2/2 SN Quantity Shipped to Date O R 1/15 Not used SN Quantity Ordered X R 1/15 Not used SN Unit or Basis for Measurement Code X ID 2/2 Not used SN Returnable Container Load Make-Up Code O ID 1/2 Not used SN Line Item Status Code O ID 2/2

16 Segment: PRF Purchase Order Reference Position: 030 Loop: HL Mandatory Max Use: 1 Purpose: To provide reference to a specific purchase order Syntax Notes: Comments: Notes: PRF Purchase Order Number M AN 1/22 Identifying number for purchase order assigned by the purchaser Purchase Order + Item Category Not used PRF Release Number O AN 1/30 Number identifying a release against a purchase order Previously placed by the parties involved in the transaction Not used PRF Change Order Sequence Number O AN 1/8 Number assigned by the orderer identifying a specific change Or revision to a previously transmitted transaction set PRF Purchase Order Date O DT 8/8 Date assigned by the purchaser to Purchase Order Not used PRF Quantity Ordered X R 1/15 Not used SN Unit or Basis for Measurement Code X ID 2/2 Not used SN Returnable Container Load Make-Up Code O ID 1/2 Not used SN Line Item Status Code O ID 2/2

17 Segment: PID Product / Item Description Position: 030 Loop: HL Mandatory Max Use: 1 Purpose: To provide reference to a specific purchase order Syntax Notes: Comments: Notes: PID Item Description type M AN 1/1 F Free Form PID Product / Process Characteristic Code O AN 2/3 Number identifying for Usage. PID Agency Qualifier Code O AN 2/2 AS Assigned by Seller PID Product Description Code O AN/1/12 CFC Fixed Code PID Description X R 1/15 BOX25 Cartoon Boxes Returnable Container Number

18 REF Reference Identification Segment: Position: 150 Loop: HL Mandatory Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Comments: Notes: Used only at Shipment level, HL03 = "S". >> REF Reference Identification Qualifier M ID 2/3 Value SI KKS ASN Number or Delivery Note Value DK Dock Number REF Reference Identification X AN 1/30 Identification of the ASN Not used Not used REF03 REF C040 Description Reference Identifier X AN 1/80 O Not used C Reference Identification Qualifier M ID 2/3 Not used C Reference Identification M AN 1/30 Not used C Reference Identification Qualifier X ID 2/3 Not used C Reference Identification X AN 1/30 Not used C Reference Identification Qualifier X ID 2/3 Not used C Reference Identification X AN 1/30

19 CLD load Detail Position: 150 Loop: HL Mandatory Max Use: >1 Purpose: To specify identifying information Syntax Notes: Comments: Notes: Used only at Shipment level, HL03 = "I". >> CLD Numbers of Loads M ID 1/5 Number of Boxes CLD Number of Units Shipped X AN 1/10 Pieces per box CLD Packaging Code X AN 3/5 Not used Not used CLD04 CLD Size Unit or Basis for Measurement Code O R 1/3 O ID 2/2

20 Segment: N1 Name Position: 220 Loop: N1 Optional Max Use: 1 Purpose: To identify a party by type of organization, name, and code Syntax Notes: 1 At least one of N102 or N103 is required. 2 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 the transaction processing party. Notes: Used only for Shipment level, HL03 = "I". >> N Entity Identifier Code M ID 2/3 Value ST Plant Value SU Supplier/Manufacturer N Name X AN 1/60 ASN NUMBER GENERATED BY SYS N Identification Code Qualifier X ID 1/2 Value 92 Assigned by Buyer N Identification Code X AN 2/80 Supplier Identification Code Not used Not used N105 N Entity Relationship Code Entity Identifier Code O ID 2/2 O ID 2/3

21 Segment: HL Hierarchical Level Position: 010 Loop: HL Mandatory Usage: Mandatory Max Use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data segments Syntax Notes: 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. The HL segment defines a top-down/left-right ordered structure. 2 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. 3 HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate. 4 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. 5 HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. Notes: Hierarchy can be either Shipment or Item levels. One Shipment level, followed by one or more Item levels. This order may be repeated. >> HL Hierarchical ID Number M AN 1/12 Sequentially numbered Not used HL Hierarchical Parent ID Number O AN 1/12 >> HL Hierarchical Level Code M ID 1/2 Value I Item Not used HL Hierarchical Child Code O ID 1/1

22 Segment: LIN Item Identification Position: 020 Loop: HL Mandatory Max Use: 1 Purpose: To specify basic item identification data Syntax Notes: 1 If either LIN04 or LIN05 is present, then the other is required. 6 If either LIN14 or LIN15 is present, then the other is required. 7 If either LIN16 or LIN17 is present, then the other is required. 1 LIN01 is the line item identification Comments: Notes: Used only for Item level, HL03 = "I". Not used LIN Assigned Identification O AN 1/20 LIN Product/Service ID Qualifier M ID 2/2 Value RC Returnable Container Packaging Information LIN Product/Service ID M AN 1/48 Packaging Information Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48 Not used LIN Product/Service ID Qualifier X ID 2/2 Not used LIN Product/Service ID X AN 1/48

23 Segment: SN1 Item Detail (Shipment) Position: 030 Loop: HL Mandatory Max Use: 1 Purpose: To specify line-item detail relative to shipment Syntax Notes: 1 SN101 is the ship notice line-item identification. Comments: 1 SN103 defines the unit of measurement for both SN102 and SN104. Notes: Used only for Item level, HL03 = "I". Not used SN Assigned Identification O AN 1/20 SN Number of Units Shipped M R 1/10 Quantity of Pieces per Handling Unit SN Unit or Basis for Measurement Code M ID 2/2 Value PC Pieces Not used SN Quantity Shipped to Date O R 1/15 Not used SN Quantity Ordered X R 1/15 Not used SN Unit or Basis for Measurement Code X ID 2/2 Not used SN Returnable Container Load Make-Up Code O ID 1/2 Not used SN Line Item Status Code O ID 2/2

24 Segment: REF Reference Identification Position: 150 Loop: HL Mandatory Max Use: >1 Purpose: To specify identifying information Syntax Notes: 1 At least one of REF02 or REF03 is required. Comments: Notes: Used only at Shipment level, HL03 = "S". >> REF Reference Identification Qualifier M ID 2/3 Value LS Handling Unit Number REF Reference Identification X AN 1/30 Handling Unit number M Master Label + Handling Unit in SAP S - Single Label + Hnadling Unit in SAP G Mixed Label + Handling Unit in SAP A Auxiliar Material Packaging + Handling Unit in SAP Handling Unit in SAP is in the following way: Handling Unit KKS + Supplier no REF Description X AN 1/80 Value = N --- Repack the Box Not used REF04 C040 Reference Identifier O Not used C Reference Identification Qualifier M ID 2/3 Not used C Reference Identification M AN 1/30 Not used C Reference Identification Qualifier X ID 2/3 Not used C Reference Identification X AN 1/30 Not used C Reference Identification Qualifier X ID 2/3 Not used C Reference Identification X AN 1/30

25

26 Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary Max Use: 1 Syntax Notes: Comments: 1 This segment is intended to provide hash totals to validate transaction completeness and correctness. >> CTT Number of Line Items M N0 1/6 Count of all HL Segments in Transaction Set X CTT Hash Total O R 1/10 X CTT03 81 Weight X R 1/10 X CTT Unit or Basis for Measurement Code X ID 2/2 X CTT Volume X R 1/8 X CTT Unit or Basis for Measurement Code X ID 2/2 X CTT Description O AN 1/80

27 Segment: SE Transaction Set Trailer Position: 020 Loop: Level: Summary Usage: Mandatory Max Use: 1 Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) Syntax Notes: Comments: 1 SE is the last segment of each transaction set. >> SE01 96 Number of Included Segments M N0 1/10 Count of all Segments in Transaction Set, Including ST and SE >> SE Transaction Set Control Number M AN 4/9 Same as ST02

28 EXAMPLE ASN ISA*00* *00* *ZZ*MX85002 *ZZ*SISV SISV *1720*U*00400* *0*P*: GS*SH*ASN40*SISV002* *1720*2960*X* ST*856*0001 BSN*00*23* *1720 DTM*011* *1720 HL*1**S MEA*PD*G*970*LB MEA*PD*N*591*LB TD1*BOX25*48 TD5*B*02*SYS - FEDEX*E TD3*TL** REF*BM* REF*PK*19624 N1*ST**92*0003 N1*SF**92* HL*2*1*I LIN**BP* *B8*K SN1**120*PC*70360 PRF* *** PID*F*0S*AS*CFC* PKG*F*CB*AA*34* PKG*F*CB*AA*34* PKG*F*CB*AA*170* REF*SI* REF*DK*0071 CLD*34*40*CNT71 HL*3*2*I LIN**RC* SN1**1*PC REF*LS*A HL*4*2*I LIN**RC* SN1**1*PC REF*LS*M HL*5*2*I LIN**RC* SN1**40*PC REF*LS*S *N HL*6*2*I LIN**RC* SN1**40*PC REF*LS*S HL*7*2*I LIN**RC* SN1**40*PC REF*LS*S CTT*7 SE*187*0001 GE*1*2960 IEA*1* KKS Packing No. O Shipment No. Returnable Information just in case the material is packed on it Packaging Information KKS Qty Per box Serial Box Handling Unit Auxiliar Packing Information Packaging Information KKS Qty Per box Master Pallet Handling Unit Batch No. Or Lote No. Purchase Order No. Our SenderId in GE segment will change as following: ASN40 N -- Means that this box needs to be Repacked Box Handling Unit

29 EXAMPLE: PICKING ORDER MESSAGE ISA*00* *00* *ZZ*MX85002 *ZZ*SISV SISV *1720*U*00401* *0*P*: GS*SH*ASN90*SISV002* *1720*2960*X* ST*856*0001 BSN*00*23458* *1720 DTM*011* *1720 HL*1**S N1*ST**92*AP12A Customer Plant N1*SF**92*L8A1C Supplier Account at Customer HL*2*1*I LIN**BP* *B8*K SN1**120*PC*70360 PRF*KP34567*** REF*SI* CLD*34*40*BOX25 HL*3*2*I LIN**RC* SN1**40*PC REF*LS*S * HL*4*2*I LIN**RC* SN1**40*PC REF*LS*S * HL*5*2*I LIN**RC* SN1**40*PC REF*LS*S * HL*6*1*I LIN**BP* *B8*K SN1**80*PC*70360 PRF*GH89065*** REF*SI* CLD*34*40*BOX25 HL*7*2*I LIN**RC* SN1**40*PC REF*LS*S * HL*8*2*I LIN**RC* SN1**40*PC REF*LS*S * CTT*8 SE*40*0001 GE*1*2960 IEA*1* KOA Shipment No. Batch No. Or Lote No. KOA Delivery Note No. Packaging Information KOA Qty Per box Serial Box Handling Unit Delivery Note No. Batch No. Or Lote No. Packaging Information KOA Qty Per box Serial Box Handling Unit Our SenderId in GE segment will change as following: ASN90

30 EXAMPLE: HANDLING UNIT STRUCTURE AFTER PICKING CONFIRMATION KOA WILL SEND THIS EDI MESSAGE ISA*00* *00* *ZZ*MX85002 *ZZ*SISV SISV *1720*U*00401* *0*P*: GS*SH*ASN95*SISV002* *1720*2960*X* ST*856*0001 BSN*00*45678* *1720 DTM*011* *1720 HL*1**S N1*SU*SYS ASN NUMBER*92* HL*2*2*I LIN**RC* REF*LS*M *M HL*3*1*I LIN**RC* REF*LS*S *S HL*4*2*I LIN**RC* REF*LS*S *S HL*5*2*I LIN**RC* REF*LS*S *S CTT*5 SE*19*0001 GE*1*2960 IEA*1* KOA SHIPMNT NO. KOA HANDLING UNIT M SYS HANDLING UNIT M KOA HANDLING UNIT S KKS HANDLING UNIT S Our SenderId in GE segment will change as following: ASN95

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest Functional Group ID=SH Introduction: This standard provides the standardized format and establishes the data contents of a ship notice/manifest transaction set. A ship notice/manifest

More information

Modine Manufacturing Company. North America EDI Guidelines for Advance Ship Notices (856) v. 4010

Modine Manufacturing Company. North America EDI Guidelines for Advance Ship Notices (856) v. 4010 Modine Manufacturing Company North America EDI Guidelines for Advance Ship Notices (856) v. 4010 Date: December 20, 2002 856 Ship Notice/Manifest Functional Group ID=SH Introduction: This Draft Standard

More information

Pos. Seg. Req. Loop Notes and

Pos. Seg. Req. Loop Notes and 856 Ship Notice/Manifest - (003040) 09/16/09 Functional Group ID=SH Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction

More information

EDI Guidelines Modine Manufacturing Company

EDI Guidelines Modine Manufacturing Company 30-501 December 20, 2002 EDI Guidelines for Advance Ship Notices (856) v. 4010 Modine Manufacturing Company 1500 De Koven Ave. Racine, WI 53403-2552 856 Ship Notice/Manifest Functional Group ID=SH Introduction:

More information

AMTEX IMPLEMENTATION GUIDELINES FOR EDI CONVENTIONS

AMTEX IMPLEMENTATION GUIDELINES FOR EDI CONVENTIONS IMPLEMENTATION GUIDELINES FOR AIAG (ASC X12) EDI CONVENTIONS SHIP NOTICE/MANIFEST TRANSACTION SET (856) ASC X12 VERSION/RELEASE 003060 Amtex 1500 Kingsview Drive Lebanon, OH 45036 6/4/2009 Page 1 856 SHIP

More information

International Automotive Components Group, North America

International Automotive Components Group, North America International Automotive Components Group, North America IMPLEMENTATION GUIDELINES FOR AIAG (ASC X12) EDI CONVENTIONS SHIP NOTICE / MANIFEST TRANSACTION SET (856) IACNA 5300 Auto Club Drive Dearborn, MI

More information

Martinrea International s EDI Specifications. AIAG version 4010 ANSI X (ASN)

Martinrea International s EDI Specifications. AIAG version 4010 ANSI X (ASN) Martinrea International s EDI Specifications AIAG version 4010 ANSI X12 856 (ASN) Segment: ST Transaction Set Header Position: 010 Purpose: To indicate the start of a transaction set and to assign a control

More information

Shape Corp. IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS 856 TRANSACTION SET SHIP NOTICE / MANIFEST. Version

Shape Corp. IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS 856 TRANSACTION SET SHIP NOTICE / MANIFEST. Version Shape Corp. IMPLEMENTATION GUIDELINES FOR ANSI X12 EDI CONVENTIONS 856 TRANSACTION SET SHIP NOTICE / MANIFEST Version 004010 Revised December 27, 2016 2 P a g e Introduction: This document contains the

More information

Agilent Technologies Company Guideline For Electronic Data Interchange Transaction Set 856 Advance Ship Notice/Manifest - Inbound

Agilent Technologies Company Guideline For Electronic Data Interchange Transaction Set 856 Advance Ship Notice/Manifest - Inbound Agilent Technologies Company Guideline For Electronic Data Interchange Transaction Set 856 Advance Ship Notice/Manifest - Inbound Functional Group ID=SH Version 003 Release 020 March 2002 AGLi85632ANY.rtf

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest Functional Group ID=SH Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for

More information

DENSO North America Supplier Web IMPLEMENTATION GUIDELINES FOR ASC X12 EDI CONVENTIONS

DENSO North America Supplier Web IMPLEMENTATION GUIDELINES FOR ASC X12 EDI CONVENTIONS DENSO North America Supplier Web IMPLEMENTATION GUIDELINES FOR ASC X12 EDI CONVENTIONS SHIP NOTICE/MANIFEST TRANSACTION SET (856) VERSION/RELEASE 004010 Technical Contact: Wes Stringfield, North American

More information

JL French, Inc. Ship Notice (X ) Version 1.2. iconnect, Inc.

JL French, Inc. Ship Notice (X ) Version 1.2. iconnect, Inc. JL French, Inc. Ship Notice (X12 004010 856) Version 1.2 iconnect, Inc. Revision History Revision Date Description 1.0 2/18/2008 Created 1.1 3/20/2008 REF Lot number sub element updated Sample data updated

More information

Supplier EDI Specification 856 Advanced Notice Version

Supplier EDI Specification 856 Advanced Notice Version Supplier EDI Specification 856 Advanced Notice Version 003010 February 2017 SEGMENT ID MOTUS REQ MAX USE SEGMENT NAME BSN M 1 Beginning Segment for Ship Notice DTM M 1 Date/Time Reference HL M 1 Shipment

More information

RPS - EDI Specifications User Guide PART 10: 856 (SHIP NOTICE/MANIFEST) ANSI X.12 - RELEASE

RPS - EDI Specifications User Guide PART 10: 856 (SHIP NOTICE/MANIFEST) ANSI X.12 - RELEASE RPS - EDI Specifications User Guide PART 10: 856 (SHIP NOTICE/MANIFEST) ANSI X.12 - RELEASE 004010 RPS - EDI Specifications 856 (Ship Notice/Manifest) - Part 10 User Guide ANSI X.12 - Release 004010 This

More information

856 Gerdau Ship Notice/Manifest

856 Gerdau Ship Notice/Manifest 856 Gerdau Ship Notice/Manifest Functional Group ID=SH Introduction: Gerdau's Strategy for sending the 856 Outbound Advance Shipping Notification is to provide the most amount of mapped fields available

More information

Toyoda Gosei Ship Notice (X ) iconnect, Inc.

Toyoda Gosei Ship Notice (X ) iconnect, Inc. Toyoda Gosei Ship Notice (X12 004010 856) iconnect, Inc. Revision History Revision Date Description 1.0 12/9/2007 Created 1.1 1/25/2008 Added REF segment under the LIN for KANBAN numbers Header Section:

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest X12/V4010/856: 856 Ship Notice/Manifest Version: 1.0 Final Notes: Table of Contents 856 Ship Notice/Manifest...1 ISA Interchange Control Header...3 GS Functional Group Header...5

More information

EDI SPECIFICATIONS. ANSI X Advance Shipping Notice. Contact: The APEX Group Phone

EDI SPECIFICATIONS. ANSI X Advance Shipping Notice. Contact: The APEX Group Phone EDI SPECIFICATIONS ANSI X12 856 Advance Shipping Notice Contact: The APEX Group edihelpdesk@mpc-inc.com Phone 262-275-5791 Last Modified Jan 26, 2015 Advanced Shipping Notice (856) INTRODUCTION This convention

More information

Verizon Business Purchasing, LLC 856 Guide 856 Ship Notice/Manifest

Verizon Business Purchasing, LLC 856 Guide 856 Ship Notice/Manifest 856 Ship Notice/Manifest Introduction: Functional Group ID=SH This Standard for Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within

More information

MGM Brakes 856 Ship Notice / Manifest

MGM Brakes 856 Ship Notice / Manifest MGM Brakes 856 Ship Notice / Manifest VERSION: ANSI ASC X12 4010 FINAL Created: June 24, 2004 856Specs.rtf 1 856 Ship Notice/Manifest Functional Group=SH This Draft Standard for Trial Use contains the

More information

856 Ship Notice/Manifest - v4030

856 Ship Notice/Manifest - v4030 Ship Notice/Manifest 856 856 Ship Notice/Manifest - v4030 X12/V4030/856 Version: 1.3 Author: OpenText Publication: April 1, 2008 Modified: September 16, 2015 PepBoys856_4030_v1_3 Ver 1.3 Page 1 Ship Notice/Manifest

More information

9/2/2015 Ship Notice/Manifest Table of Contents

9/2/2015 Ship Notice/Manifest Table of Contents Table of Contents 856 Ship Notice/Manifest.. ST Transaction Set Header... BSN Beginning Segment for Ship Notice DTM Date/Time Reference.. HL Loop Hierarchical Level.. HL Hierarchical

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest X12/V4010/856 : 856 Ship Notice/Manifest Version: 1.1 Final Author: Advance Auto Parts Company: Advance Auto Parts Publication: 9/23/2013 Notes: Table of Contents 856 Ship Notice/Manifest...

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest Functional Group ID=SH Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for

More information

LVS/ET Division ASN Advance Ship Notice

LVS/ET Division ASN Advance Ship Notice LVS/ET Division 856 - ASN Advance Ship Notice ANSI X12 Version 004010 lvsedi@arvinmeritor.com 856v4010 Revised 5/24/2007 Page 1 of 28 856 Advance Ship Notice Transaction Layout: Segments: Arm Req Pos No

More information

EDI X Implementation Guide. Advanced Ship Notice

EDI X Implementation Guide. Advanced Ship Notice EDI X12 004010 856 Implementation Guide Advanced Ship Notice Issued by: AM General Date: July 15, 2009 The information disclosed herein is proprietary to AM GENERAL and is not to be used or disclosed to

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest Functional Group ID=SH Introduction: This Standard contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context

More information

L & W Engineering Inbound 856 EDI Specifications

L & W Engineering Inbound 856 EDI Specifications SEGMENT: ISA - Interchange Control Header Purpose: Starts and identifies an interchange of one or more functional groups and interchange-related control segments. ISA01 I01 Authorization Info. Qualifier

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest X12/V4030/856: 856 Ship Notice/Manifest Version: 1.0 Author: Abbott Nutrition ebusiness Company: Abbott Nutrition Created: 11/29/2012 Current: 11/29/2012 Table of Contents 856

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest X12/V4060/856: 856 Ship Notice/Manifest Modified: 01/17/2005 856_4060_BEAR.ecs 1 For internal use only 856 Ship Notice/Manifest Functional Group=SH This X12 Transaction Set contains

More information

856 Ship Notice/Manifest Functional Group=SH

856 Ship Notice/Manifest Functional Group=SH 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

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest Functional Group ID=SH Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for

More information

Functional information for outbound Advance Ship Notice (ASN) EDIFACT - DESADV ANSI X12-856

Functional information for outbound Advance Ship Notice (ASN) EDIFACT - DESADV ANSI X12-856 Functional information for outbound Advance Ship Notice (ASN) EDIFACT - DESADV ANSI X12-856 Micron has created a standard electronic Advance Ship Notice (ASN) document format. This standard format includes

More information

BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 856 VERSION 4010 FROM SUPPLIER. Document version 1.1

BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 856 VERSION 4010 FROM SUPPLIER. Document version 1.1 ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 856 VERSION 4010 FROM SUPPLIER Document version 1.1 The following guide is intended to facilitate the user in implementing Electronic Data Interchange

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest Functional Group ID=SH Introduction: This X12 Transaction Set contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within

More information

BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 856 VERSION 4010 FROM SUPPLIER. Document version 1.1

BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 856 VERSION 4010 FROM SUPPLIER. Document version 1.1 BRP Inc. ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE 856 VERSION 4010 FROM SUPPLIER Document version 1.1 The following guide is intended to facilitate the user in implementing Electronic Data

More information

856 Ship Notice/Manifest. X12/V4010/856 : 856 Ship Notice/Manifest Version: 1.0 Draft

856 Ship Notice/Manifest. X12/V4010/856 : 856 Ship Notice/Manifest Version: 1.0 Draft 856 Ship Notice/Manifest X12/V4010/856 : 856 Ship Notice/Manifest Version: 1.0 Draft Author: Pauline Flanigan Publication: 5/31/2018 Created: 5/31/2018 Modified: 5/31/2018 Table of Contents 856 Ship Notice/Manifest................................................................................................

More information

Rite Aid Corporation 856 DSD Ship Notice/Manifest Direct Store Delivery (DSD)

Rite Aid Corporation 856 DSD Ship Notice/Manifest Direct Store Delivery (DSD) Rite Aid Corporation 856 DSD Ship Notice/Manifest Direct Store Delivery (DSD) Functional Group ID=SH Introduction: This X12 Transaction Set contains the format and establishes the data contents of the

More information

Implementation Guide Ship Notice

Implementation Guide Ship Notice Implementation Guide Ship Notice TABLE OF CONTENTS I. IDENTIFICATION... 2 COMPANY... 2 CONTACTS... 2 II. TECHNICAL PARAMETERS... 3 VALUE ADDED NETWORKS (VAN)... 3 III. SET UP PROCEDURE... 4 SETUP BY THE

More information

856 EDI SPECIFICATIONS VERSION 4010

856 EDI SPECIFICATIONS VERSION 4010 856 EDI SPECIFICATIOS VERSIO 4010 11/19/2007 Page 1 of 23 Revision 2 Transaction Set Header Segment: ST - Transaction Set Header Level: Heading Max. Use: 1 To indicate the start of the 856 transaction

More information

This transaction set allows 3M to send shipment notification to your company electronically via EDI.

This transaction set allows 3M to send shipment notification to your company electronically via EDI. Introduction This guideline provides a description and technical lay-out of the data segments sent in 3M s EDI ship notices (ASC X12 transaction set 856). 3M can send many valid ASC X12 data segments and

More information

861 Receiving Advice/Acceptance Certificate

861 Receiving Advice/Acceptance Certificate 861 Receiving Advice/Acceptance Certificate Transaction Layout: Heading: Functional Group ID=RC ARM Pos. Seg. Req. Loop Notes and Req. No. ID Name Des. Max.Use Repeat Examples Required 010 ST Transaction

More information

MAGNA. ANSI X12 - Version AIAG. Advanced Shipping Notice / Manifest [856] IMPLEMENTATION GUIDE

MAGNA. ANSI X12 - Version AIAG. Advanced Shipping Notice / Manifest [856] IMPLEMENTATION GUIDE MAGNA ANSI X12 - Version 003060 AIAG Advanced Shipping Notice / Manifest [856] IMPLEMENTATION GUIDE This guide has been produced by Magna International Inc. This Guideline is developed to be compliant

More information

Target Canada. Domestic 856 Ship Notice/Manifest - Pre-Distro

Target Canada. Domestic 856 Ship Notice/Manifest - Pre-Distro Target Canada Domestic 856 Ship Notice/Manifest - Pre-Distro EDI Guideline Version: 5010 Draft Author: GXS Company: Target Canada Publication: 2/1/2012 Trading Partner: ANY Rev Date Author Purpose for

More information

856 Ship Notice/Manifest X12/V4010/856: 856 Ship Notice/Manifest Version: 1.1

856 Ship Notice/Manifest X12/V4010/856: 856 Ship Notice/Manifest Version: 1.1 856 Ship Notice/Manifest X12/V4010/856: 856 Ship Notice/Manifest Version: 1.1 X12V4010 1 CHANGE LOG Chg# Date Noted Description of Change Change By Version Num. 1 Original 1.0 2 9/1/2017 NEW Loop ID HL

More information

Super Shoes EDI Guideline

Super Shoes EDI Guideline Super Shoes EDI Guideline ANSI X12-004010 856 Advance Ship Notice Version: 1.0 Draft Author: SPS Commerce Publication: Trading Partner: Created: 01/21/2010 Modified: 02/01/2010 Current: 03/23/2010 Notes:

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest Functional Group ID=SH Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for

More information

EDI Implementation Guide for SAP ASN

EDI Implementation Guide for SAP ASN EDI Implementation Guide for SAP ASN March 2015 TRANSACTION SET 856 Advanced Ship Notice ANSI X.12 Table of Contents 856 Advanced Ship Notice Usage Convention...1 ANSI X.12 Version...2 H-D EDI Qualifier

More information

Belk Stores 856 Ship Notice/Manifest

Belk Stores 856 Ship Notice/Manifest Belk Stores 856 Ship Notice/Manifest X12/V4030/856 : 856 Ship Notice/Manifest Version: 4.1 856 Ship Notice/Manifest Functional Group= SH Purpose: This Draft Standard for Trial Use contains the format and

More information

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

EDI Specifications Guide. 856 Supplier Advance Ship Notice Last updated February 2017 856 Supplier Advance Ship Notice Last updated February 2017 856 Ship Notice/Manifest - Functional Group=SH VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents

More information

Message Implementation Guideline for JIS suppliers MBUSI_003050_856. based on. 856 Ship Notice/Manifest X

Message Implementation Guideline for JIS suppliers MBUSI_003050_856. based on. 856 Ship Notice/Manifest X Message Guideline for JIS suppliers MBUSI_003050_856 based on 856 Ship Notice/Manifest X12 003050 Version 1.0: 16-Feb-2016 Note This document is an EDI specification guideline for JIS suppliers to implement

More information

EDI Implementation Guide

EDI Implementation Guide EDI Implementation Guide TRANSACTION SET 856 UCC128 ASN (RETAIL/TRADE) PLEASE TAKE NOTE THAT ALL SEGMENTS MARKED OPTIONAL OFFICE DEPOT DOES WANT YOU TO MAP AND UTILIZE AS OUR SPECIFICATIONS ARE CREATED

More information

Ship Notice/Manifest DSD. Walgreens Advance Ship Notice (DSD) 856 X

Ship Notice/Manifest DSD. Walgreens Advance Ship Notice (DSD) 856 X Walgreens Advance Ship Notice (DSD) 856 X12-4010 1 August 2, 2001 856 Advance Ship Notice/Manifest The 856 Transaction Set is d to help expedite the receipt of supplier goods at both Walgreens distribution

More information

EDI SPECIFICATIONS. LIN Product/Service ID M AN 1/48 Will be the identifying number for a product or service. CN = Commodity Name

EDI SPECIFICATIONS. LIN Product/Service ID M AN 1/48 Will be the identifying number for a product or service. CN = Commodity Name 862 (Shipping Schedule) EDI SPECIFICATIONS This BRAIN North America, Inc. standard provides the format and establishes the data contents of the 862 (Shipping Schedule Transaction Set). The transaction

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest X12/V4010/856 : 856 Ship Notice/Manifest Status: Final Publication: 6/16/2016 Table of Contents 856 Ship Notice/Manifest................................................................................................

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest Functional Group ID=SH Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for

More information

Target Canada. Domestic 856 Ship Notice Manifest Distribution/Fulfillment Centers

Target Canada. Domestic 856 Ship Notice Manifest Distribution/Fulfillment Centers Target Canada Domestic 856 Ship Notice Manifest Distribution/Fulfillment Centers EDI Guideline Version: 5010 Draft Author: GXS Company: Target Canada Publication: 1/27/2012 Trading Partner: Distribution/Fulfillment

More information

ANSI X12 version Ship Notice/Manifest

ANSI X12 version Ship Notice/Manifest ANSI X12 version 4010 856 Ship Notice/Manifest VERSION: 01.00.00 Author: EDI Administration Team Publication Date: 10/15/2007 Trading Partner: All Contact Information: O. C. Tanner Company EDI Administration

More information

856 Advance Ship Notice Segment Descriptions Transmission Data File Specifications Ansi X12 Version 4010

856 Advance Ship Notice Segment Descriptions Transmission Data File Specifications Ansi X12 Version 4010 O Reilly / Ozark Automotive Inc. 856 ASN Implementation Guide To: Trading Partners From: Jim Edwards Date: 08/10/01 856 Advance Ship Notice Segment Descriptions Transmission Data File Specifications Ansi

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest Functional Group ID=SH Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for

More information

VOLVO Dealer Programs 856 Ship Notice/Manifest EDI Guidelines

VOLVO Dealer Programs 856 Ship Notice/Manifest EDI Guidelines VOLVO (ASN) General This document describes Volvo's application of the ANSI X12 transaction set 856 Ship Notice/Manifest. In the following description the general notation ASN (Advanced Shipping Notice)

More information

Message Implementation Guideline CCUSA_003050_856. based on. 856 Ship Notice/Manifest X

Message Implementation Guideline CCUSA_003050_856. based on. 856 Ship Notice/Manifest X Message Guideline CCUSA_003050_856 based on 856 Ship Notice/Manifest X12 003050 Version 1.0: June 25, 2018 Change History Date Chapter Description 1.0 Apr/20/2018 All Document created 1.1 Jun/25/2018 2.2

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest X12/V4010/856: 856 Ship Notice/Manifest Version: 5.0 4010 Draft Company: itradenetwork -dc Publication: 6/19/2015 Trading Partner: itn Supplier Version Notes: Universal 856 Draft

More information

FILE LAYOUT FOR 856 EDI TRANSACTION (OUTBOUND)

FILE LAYOUT FOR 856 EDI TRANSACTION (OUTBOUND) FILE LAYOUT FOR 856 EDI TRANSACTION (OUTBOUND) SHIPMENT BASED VERSION 4010 Page 1 of 40 OVERVIEW PURPOSE OF TRANSACTION Outbound (Hubbell to Trading Partner) Shipment Based Advance Ship Notice VERSION

More information

856 Ship Notice/Manifest Functional Group=SH

856 Ship Notice/Manifest Functional Group=SH 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

More information

856 Ship Notice/Manifest

856 Ship Notice/Manifest 856 Ship Notice/Manifest X12/V4010/856: 856 Ship Notice/Manifest Version: Author: Abbott Nutrition ebusiness Company: Abbott Nutrition Created: 03/22/2012 Current: 03/22/2012 Table of Contents 856 Ship

More information

KOHLER COMPANY VENDOR SHIP NOTICE LAYOUT (856) Kohler Description Number M = Mandatory O = Optional C = Conditional

KOHLER COMPANY VENDOR SHIP NOTICE LAYOUT (856) Kohler Description Number M = Mandatory O = Optional C = Conditional ISA Field ISA Field Description M = Mandatory O = Optional C = Conditional M = Mandatory O = Optional C = Conditional ISA - Interchange Control Header ISA01 101 Authorization Info. Qualifier M ID 2/2 M

More information

Message Implementation Guideline CCUSA_003050_856. based on. 856 Ship Notice/Manifest X

Message Implementation Guideline CCUSA_003050_856. based on. 856 Ship Notice/Manifest X Message Guideline CCUSA_003050_856 based on 856 Ship Notice/Manifest X12 003050 Version 1.2: Sep 26th, Change History Date Chapter Description 1.0 Apr/20/ All Document created 1.1 Jun/25/ 3.2 GS Application

More information

EDI Specifications Guide. 856 Supplier Advance Ship Notice

EDI Specifications Guide. 856 Supplier Advance Ship Notice 856 Supplier Advance Ship Notice 856 Ship Notice/Manifest - Functional Group=SH VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific

More information

Message Implementation Guideline MBUSI_003050_856. based on. 856 Ship Notice/Manifest X

Message Implementation Guideline MBUSI_003050_856. based on. 856 Ship Notice/Manifest X Message Guideline MBUSI_003050_856 based on 856 Ship Notice/Manifest X12 003050 Version 1.13: July the 24 th 2017 Change History Date Chapter Description 1.10 Feb/06/2017 2.9.1 LIN Added: Quantities per

More information

856 FM Ship Notice/Manifest

856 FM Ship Notice/Manifest 856 FM Ship Notice/Manifest Functional Group=SH Applies to: Heading: Pos Id Segment Name Req Max Use Repeat Notes Usage 0200 BSN Beginning Segment for Ship M 1 Must use Notice Detail: Pos Id Segment Name

More information

BIG ROCK SPORTS ADVANCE SHIP NOTICE

BIG ROCK SPORTS ADVANCE SHIP NOTICE ALL SPORTS SUPPLY AWR SPORTS CSI SPORTS HENRY S TACKLE MT SPORTS BIG ROCK SPORTS 856 ADVANCE SHIP NOTICE IMPLEMENTATION GUIDE Updated September 26, 2006 Page 1 of 31 09/26/2006 Revision History Revisions

More information

The Shipment and Billing Notice - 857

The Shipment and Billing Notice - 857 The Shipment and Billing Notice - 857 The Shipment and Billing Notice (857) is to be used in those cases where a supplier and distributor agree that adequate controls and accuracy in picking and shipping

More information

EDI Implementation Guide

EDI Implementation Guide EDI Implementation Guide BUSINESS SERVICES DIVISION TRANSACTION SET 856 Shipping Notice 856 Shipping Notice DATA SEGMENT SEQUENCE FUNCTIONAL GROUP ID=SH Header Seg. Name Req. Des. Loop Repeat ID ST Transaction

More information

Advance Shipment Notice Specification EDI 856

Advance Shipment Notice Specification EDI 856 Advance Shipment Notice Specification EDI 856 This document is solely for the use of Logicbroker, Inc. personnel and its intended client. No part of it may be circulated, Quoted, or reproduced for distribution

More information

Introduction: Notes: Heading: Detail: Functional Group ID=SH

Introduction: Notes: Heading: Detail: Functional Group ID=SH 856 Ship Notice/Manifest Functional Group ID=SH Introduction: This X12 Transaction Set contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within

More information

Ship Notice/Manifest. Regular. Rev X pg. 1. (Non Steel) Revision Date: June 8, 2017

Ship Notice/Manifest. Regular. Rev X pg. 1. (Non Steel) Revision Date: June 8, 2017 EDI IMPLEMENTATION GUIDE 856 ANSI X2 V400 Ship Notice/Manifest Regular (Non Steel) Rev 8.2. X2 00400 pg. Functional Group ID= SH Introduction: This Draft Standard for Trial Use contains the format and

More information

856 Ship Notice/Manifest. X12/V4010/856 : 856 Ship Notice/Manifest Version: 2.0 Final

856 Ship Notice/Manifest. X12/V4010/856 : 856 Ship Notice/Manifest Version: 2.0 Final 856 Ship Notice/Manifest X12/V4010/856 : 856 Ship Notice/Manifest Version: 2.0 Final Author: EDI Department Company: D&H Distributing Publication: 01/29/2016 Trading Partner: Created: 01/27/2016 Modified:

More information

Advanced Ship Notice Message 856 X12/V3040/856: 856 Advanced Ship notice

Advanced Ship Notice Message 856 X12/V3040/856: 856 Advanced Ship notice Advanced Ship Notice Message 856 X12/V3040/856: 856 Advanced Ship notice Author: Publication: Trading Partner: Notes: Seagate B2B Outbound from Seagate to trading partner Cust856 1 2012 Seagate Technology

More information

Message Implementation Guideline CCUSA_003050_856. based on. 856 Ship Notice/Manifest for JIS deliveries X

Message Implementation Guideline CCUSA_003050_856. based on. 856 Ship Notice/Manifest for JIS deliveries X Message Guideline CCUSA_003050_856 based on 856 Ship Notice/Manifest for JIS deliveries X12 003050 Version 1.0: June 25, 2018 Change History Date Chapter Description 1.0 Apr/20/2018 All Document created

More information

X12 Implementation. Guidelines. For. Inbound Standard. Advance Ship Notice. (856i- Standard)

X12 Implementation. Guidelines. For. Inbound Standard. Advance Ship Notice. (856i- Standard) X2 Implementation Guidelines For Inbound Standard Advance Ship Notice (856i- Standard) 856.pdf 856 Ship Notice/anifest Functional Group ID=SH Introduction: This standard provides the standardized format

More information

EDI Implementation Guide 856 Advance Ship Notice Version 4010

EDI Implementation Guide 856 Advance Ship Notice Version 4010 EDI Implementation Guide 856 Advance Ship Notice Version 4010 Stores, Inc. and Subsidiaries and Affiliates 8000 Bent Branch Dr. Irving, TX 75063 (972) 409-1300 856 Ship Notice/Manifest 4010 Functional

More information

Message Implementation Guideline MBUSI_003050_856. based on. 856 Ship Notice/Manifest X

Message Implementation Guideline MBUSI_003050_856. based on. 856 Ship Notice/Manifest X Message Guideline MBUSI_003050_856 based on 856 Ship Notice/Manifest X12 003050 Version 1.11: 16-Feb-2017 Change History Date Chapter Description 1.1 25-Sep-2015 All Document created 1.2 29-Oct-2015 3.9.1

More information

856 Ship Notice/Manifest Functional Group=SH Heading: Pos Id Segment Name Req Max Use Repeat Notes 0200 BSN Beginning Segment for Ship Notice M 1

856 Ship Notice/Manifest Functional Group=SH Heading: Pos Id Segment Name Req Max Use Repeat Notes 0200 BSN Beginning Segment for Ship Notice M 1 856 Ship Notice/Manifest Functional Group=SH Heading: Pos Id Segment Req Max Use Repeat Notes 0200 BSN Beginning Segment for Ship Notice M 1 Detail: Pos Id Segment Req Max Use Repeat Notes LOOP ID - HL

More information

DoD Transportation Electronic Business (DTEB) Convention

DoD Transportation Electronic Business (DTEB) Convention DEPARTMENT OF DEFENSE TRANSPORTATION EDI CONVENTION ADVANCE SHIP NOTICE FEDERAL AND DOD 856.F.004010 Department of Defense DoD Transportation Electronic Business (DTEB) Convention ASC X12 Transaction Set

More information

Transaction 856. Benteler Automotive Electronic Data Interchange Specifications. Version 2.2 November 30, 2009

Transaction 856. Benteler Automotive Electronic Data Interchange Specifications. Version 2.2 November 30, 2009 Benteler Automotive Electronic Data Interchange Specifications Transaction 856 Version 2.2 November 30, 2009 NAO_LO-023 Benteler Automotive 1 November 30,2009 856 Version 4010 Version 2.2 Changes from

More information

Grand & Toy EDI Guidelines October 18, 2000, Revised March 30, Segment Usage. Segment Segment Required Max ID Name Use Occurrence

Grand & Toy EDI Guidelines October 18, 2000, Revised March 30, Segment Usage. Segment Segment Required Max ID Name Use Occurrence Segment Usage Segment Segment Required Max ID Name Use Occurrence HEADER SEGMENTS ST Transaction Set Header M 1 BSN Beginning Segment for Ship Notice M 1 SHIPMENT LEVEL HL Hierarchical Level M 1 PO4 Item

More information

ANSI X12 ASN 856 Version

ANSI X12 ASN 856 Version ADVANCE SHIP NOTICE MESSAGE ANSI X12 ASN 856 Version 002040 V01 12/11/04 Page 1/36 Property of VALEO Duplication Prohibited Table of Contents 1 THE ADVANCE SHIP NOTICE MESSAGE... 4 1.1 Introduction...

More information

ACE HARDWARE 856 ADVANCED SHIP NOTICE ANSI X

ACE HARDWARE 856 ADVANCED SHIP NOTICE ANSI X ACE HARDWARE 856 ADVANCED SHIP NOTICE ANSI X12 4010 *NOTES: PLEASE REFERENCE 1 PO PER 856 TRANSACTION SET (ST-SE ENVELOPE). THE 856 SHOULD BE SENT THE SAME DAY THE ORDER IS SHIPPED. MAKE SURE ALL SHIP

More information

856 Ship Notice/Manifest Purchase Order Carton Consolidation Shipment Pick/Pack Structure

856 Ship Notice/Manifest Purchase Order Carton Consolidation Shipment Pick/Pack Structure 856 Ship Notice/Manifest Purchase Order Carton Consolidation Shipment Pick/Pack Structure Macy s VICS Version 4010 VICS Document Mapping Updated 10/8/10 NOTE: The POs that are Stand Alone must appear first

More information

870 Order Status Report (Version 4010) Target Corporation Common

870 Order Status Report (Version 4010) Target Corporation Common 870 Order Status Report (Version 4010) Target Corporation Common Revised: August 26, 2003 Introduction: Functional Group ID=RS This Draft Standard for Trial Use contains the format and establishes the

More information

10/04/2017 NORDSTROM CANADA Ship Notice/Manifest Ship Notice/Manifest

10/04/2017 NORDSTROM CANADA Ship Notice/Manifest Ship Notice/Manifest 856 NORDSTROM CANADA Ship Notice/Manifest Functional Group=SH Purpose: This Standard contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within

More information

JCPenney 856 Ship Notice/Manifest Version 4030

JCPenney 856 Ship Notice/Manifest Version 4030 TABLE OF CONTENTS JCPenney Mapping Differences between Versions 3060 and 4030... 1.2 Transaction Set Purpose... 1.3 Pick Pack Shipment Segment Hierarchy... 1.3 Standard Pack Shipment Segment Hierarchy...

More information

Implementation Guidelines for AIAG (ANSI X12) EDI Conventions Ship Notice/Manifest Transaction Set (856) (2040 format)

Implementation Guidelines for AIAG (ANSI X12) EDI Conventions Ship Notice/Manifest Transaction Set (856) (2040 format) Page 1 of 32 Implementation Guidelines for AIAG (ANSI X12) EDI Conventions Ship Notice/Manifest Transaction Set (856) (2040 format) 01/2012 Version 3.0 revised for multiple Magna divisions: Monterrey,

More information

857 Shipment and Billing Notice

857 Shipment and Billing Notice 857 Shipment and Billing Notice X12/V3050/857: 857 Shipment and Billing Notice Version: 2 Author: Global Exchange Services Publication: August 2007 STEELi85735ANY_IG_v2.ecs 1 Table of Contents Shipment

More information