JCPenney 856 Ship Notice/Manifest Version 4030
|
|
- Kenneth Terry
- 6 years ago
- Views:
Transcription
1 TABLE OF CONTENTS JCPenney Mapping Differences between Versions 3060 and Transaction Set Purpose Pick Pack Shipment Segment Hierarchy Standard Pack Shipment Segment Hierarchy HL Levels and Segment Hierarchy Supplementary 856 Catalog Division Documentation ISA -Envelope Segment GS -Functional Group Segment ST -Start of Ship Notice/Manifest Transaction Set BSN -Ship Notice Number, Date and Time and HL Code HL -Start of Shipment Level and HL Dependencies TD1 -Transportation Packaging, Weight, and Cartons TD5 -Carrier and Sequence of Routing, Port of Discharge REF -Bill of Lading Number REF -Carrier Reference Number (Pro Number) REF -JCP Load ID PER -Vendor Contact DTM -Supplier's Ship Date and Time DTM -Supplier's Estimated Shipment Arrival Date N1 -Initial Ship-To Location Code N1 -Ship From Location or Port of Origin N4 -Ship From City/State/Zipcode HL -Start of Order Level and HL Dependencies PRF -Purchase Order Number and Date, International Import Contract Number PID -Fair Labor Standards Act Compliance TD5 -Shipment Order Status Code REF -JCPenney's Internal Supplier Number REF -Subdivision Number REF -Supplier's Order Number REF -Supplier's Invoice Number REF -Inspection Report Number N1 -Mark-For Location Code N3 -Mark-For Street Address N4 -Mark-For City/State/Zipcode N1 -Bill To Location Code HL -Start of Tare Level and HL Dependencies MAN -Ocean Shipping Container Number HL -Start of Pack Level and HL Dependencies SLN -Individual Component SKUs in a Standard Pack Set PKG -Retail Procedures Compliance Indicator or Catalog Color Coordinate Number MAN -UCC 128 Shipping Container Code Number HL -Start of Item Level and HL Dependencies LIN -SKU Numbers On Ship Notice SN1 -SKU Quantity Shipped and Original Order Quantity SLN -SKUs Within An Assortment TD5 -Shipment Item Status Code CTT -Count of HL Segments SE -End of Ship Notice/Manifest Transaction Set GE -Functional Group Segment IEA -Envelope Segment Pick Pack Shipments Pick Pack Shipment Example Standard Pack Shipments Standard Pack Shipment Example Business Examples June 2003 Page 1.1 Section 20 d:\my_docs\4030\ POM F5 June 03 Page
2 Page(s) JCPENNEY MAPPING DIFFERENCES BETWEEN VERSIONS 3060 and 4030 Differences NOTE: Beginning with version 4010 of the Standards, all DATE data elements (373) have changed to a min/max of 8/8. The format is CCYYMMDD. Also, note that the maximum use of a segment may have changed due to the explicit declaration of the loop maximum on the Segment Hierarchy page (1.3). 2.1 D/E I10 in ISA11 has been replaced with D/E I65. D/E I14 in ISA15 has been renamed. 2.2 D/E 1005 in BSN05 has a JCP attribute change. 2.3 Segment TD1 usage count has changed. D/E 67 in TD503 has an X12 and JCP attribute change. D/E 127 in the first REF02 has an X12 and JCP attribute change. D/E 127 in REF02 has an X12 attribute change. 2.4 Segment PER has been added. D/E 337 in DTM03 has been added for time D/E 98 in N101 has an X12 attribute change. D/E 93 in N102 has an X12 attribute change. D/E 67 in N104 has an X12 attribute change. 2.5 D/E 367 in PRF06 has a JCP attribute change. D/E 67 in TD503 has an X12 attribute change. 2.6 Segment PID and TD5 have been added. D/E 127 in REF02 has an X12 attribute change. 2.7 D/E 127 in REF02 has an X12 and JCP attribute change. Segment REF has been added for inspection report number. Segment N1, N3 N4 has been added to identify the mark for party. 2.8 D/E 98 in N101 has an X12 attribute change and a new code value. D/E 93 in N102 has an X12 attribute change. D/E 67 in N104 has an X12 attribute change. 2.9 D/E 88 in MAN01 has a new code value D/E 350 in SLN01 has a change to the comment field. D/E 380 in SLN04 has an X12 and JCP attribute change. Composite 0001 in SLN05 has an X12 attribute change. D/E 235 in SLN09 has a new code value. D/E 234 in SLN10, SLN12 and SLN14 has an X12 attribute change Segment PKG has been added D/E 235 in LIN02 has a new code value. D/E 234 in LIN03, LIN05 and LIN07 has an X12 attribute change. D/E 382 in SN102 has a JCP attribute change. D/E 646 in SN104 has an X12 attribute change. D/E 330 in SN105 has an X12 and JCP attribute change D/E 350 in SLN01 has a change to the comment field. D/E 380 in SLN04 has an X12 and JCP attribute change. Composite 0001 in SLN05 has an X12 attribute change. D/E 639 in SLN07 has a new code value. D/E 235 in SLN09 has a new code value. D/E 234 in SLN10, SLN12 and SLN14 has an X12 attribute change. D/E 67 in TD503 has an X12 attribute change. NOTE - Highlighted (shaded) areas of the document reflect changes from the previous version. June 2003 Page 1.2
3 SEGMENT HIERARCHY Purpose: The 856 is used by a supplier to notify a retailer that merchandise for a specific purchase order has been shipped. Transaction contains information relating to the supplier's shipment, retailer's original order, and also identifies any differences in order quantities requested and actual quantities shipped. ISA -INTERCHANGE CONTROL HEADER GS -FUNCTIONAL GROUP HEADER Ship Notice/Manifest Segment Hierarchy (Pick Pack) HEADER Loop Max ST -Start of Purchase Order Transaction Set BSN -Ship Notice Number, Date and Time, and Hierarchical Structure Code DETAIL Shipment HL -Start of Shipment Level and HL Dependencies 200,000 TD1 -Transportation Packaging, Weight, and Cartons TD5 -Carrier and Sequence of Routing, Port of Discharge REF -Bill of Lading Number REF -Carrier Reference Number (Pro Number) REF -JCP Load ID PER -Vendor Contact DTM -Supplier's Ship Date and Time DTM -Supplier's Estimated Shipment Arrival Date N1 -Initial Ship-To Location Code 1 N1 -Ship From Location or Port of Origin 1 N4-Ship From City/State/Zipcode Order HL -Start of Order Level and HL Dependencies 200,000 PRF -Purchase Order Number and Date PID -Fair Labor Standards Act Compliance TD5 -Shipment Order Status Code REF -JCPenney's Internal Supplier Number REF -Subdivision Number REF -Supplier's Order Number REF -Supplier's Invoice Number REF -Inspection Report Number N1 -Mark For Location Code 1 N3-Mark For Street Address N4-Mark For City/State/Zipcode N1 -Bill To Location Code 1 Tare HL -Start of Tare Level and HL Dependencies 200,000 MAN-Ocean Shipping Container Number Pack HL -Start of Pack Level and HL Dependencies 200,000 PKG -Retail Procedures Compliance Indicator or Catalog Color Coordinate Number MAN-UCC 128 Shipping Container Code Number Item HL -Start of Item Level and HL Dependencies 200,000 LIN -SKU Numbers On Ship Notice SN1 -SKU Quantity Shipped and Original Order Quantity SLN -SKUs Within An Assortment TD5 -Shipment Item Status Code TRAILER CTT -Count of HL Segments SE -End of Ship Notice/Manifest Transaction Set GE -FUNCTIONAL GROUP TRAILER IEA -INTERCHANGE CONTROL TRAILER June 2003 Page 1.3
4 SEGMENT HIERARCHY ISA -INTERCHANGE CONTROL HEADER GS -FUNCTIONAL GROUP HEADER Ship Notice/Manifest Segment Hierarchy (Standard Pack) HEADER Loop Max ST -Start of Purchase Order Transaction Set BSN -Ship Notice Number, Date and Time, and Hierarchical Structure Code DETAIL Shipment HL -Start of Shipment Level and HL Dependencies 200,000 TD1 -Transportation Packaging, Weight, and Cartons TD5 -Carrier and Sequence of Routing, Port of Discharge REF -Bill of Lading Number REF -Carrier Reference Number (Pro Number) REF -JCP Load ID PER -Vendor Contact DTM -Supplier's Ship Date and Time DTM -Supplier's Estimated Shipment Arrival Date N1 -Initial Ship-To Location Code 1 N1 -Ship From Location or Port of Origin 1 N4-Ship From City/State/Zipcode Order HL -Start of Order Level and HL Dependencies 200,000 PRF -Purchase Order Number and Date PID -Fair Labor Standards Act Compliance TD5 -Shipment Order Status Code REF -JCPenney's Internal Supplier Number REF -Subdivision Number REF -Supplier's Order Number REF -Supplier's Invoice Number REF -Inspection Report Number N1 -Mark For Location Code 1 N3-Mark For Street Address N4-Mark For City/State/Zipcode N1 -Bill To Location Code 1 Tare HL -Start of Tare Level and HL Dependencies 200,000 MAN-Ocean Shipping Container Number Item HL -Start of Item Level and HL Dependencies 200,000 LIN -SKU Numbers On Ship Notice SN1 -SKU Quantity Shipped and Original Order Quantity SLN -SKUs Within An Assortment TD5 -Shipment Item Status Code Pack HL -Start of Pack Level and HL Dependencies 200,000 SLN -Individual Component SKUs in a Standard Pack Set PKG -Retail Procedures Compliance Indicator or Catalog Color Coordinate Number MAN-UCC 128 Shipping Container Code Number TRAILER CTT -Count of HL Segments SE -End of Ship Notice/Manifest Transaction Set GE -FUNCTIONAL GROUP TRAILER IEA -INTERCHANGE CONTROL TRAILER June 2003 Page 1.4
5 HL Levels and Segment Hierarchy PROCEDURES AND REQUIREMENTS The sequence in which the various segments are generated will vary depending on whether the shipment is "Pick Pack" or "Standard Pack" structure. Within an 856 shipment (ST to SE) the structure must be the same, either pick pack or standard pack. A specific 856 transaction set can contain data relating to multiple purchase orders, multiple cartons shipped for each purchase order, and multiple SKUs within each carton. An HL (hierarchical) segment is used to identify the different levels of data (e.g., shipment, order, carton, item level). BSN05 identifies whether the shipment is pick pack or standard pack structure. Supplementary 856 Catalog Division Documentation Examples of how the ship notice/manifest (856), order status inquiry (869), and order status report (870) are used in relationship to JCPenney Catalog purchase orders are explained in a separate document called "Catalog Purchase Order Follow Up (POF) Supplier Procedures". If you have any questions, call JCPenney EDI Support ( ). June 2003 Page 1.5
6 Segment: ISA - INTERCHANGE CONTROL HEADER Level: ENVELOPE Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To start and identify an interchange of one or more functional groups and interchange related control. ISA01 I01 Authorization Information Qualifier M ID 2/2 "00" (No Authorization Information) ISA02 I02 Authorization Information M AN 10/10 Ten blank positions. ISA03 I03 Security Information Qualifier M ID 2/2 "00" (No Security Information) ISA04 I04 Security Information M AN 10/10 Ten blank positions. ISA05 I05 Interchange ID Qualifier M ID 2/2 Advise DUNS, Comm ID or SCAC number. ISA06 I06 Interchange Sender ID M AN 15/15 ISA07 I05 Interchange ID Qualifier M ID 2/2 "08" (Communication ID) ISA08 I07 Interchange Receiver ID M AN 15/15 See note. ISA09 I08 Interchange Date M DT 6/6 ISA10 I09 Interchange Time M TM 4/4 ISA11 I65 Repetition Separator M ID 1/1 ISA12 I11 Interchange Version ID M ID 5/5 ISA13 I12 Interchange Control Number M N0 9/9 ISA14 I13 Acknowledgment Requested M ID 1/1 0 (No Acknowledgment Requested) ISA15 I14 Usage Indicator M ID 1/1 ISA16 I15 Component Element Separator M AN 1/1 ISA08 - JCPenney will use the following Receiver-IDs: (Retail), (Catalog), (Indirect Imports), (DFW). Segment: GS - FUNCTIONAL GROUP HEADER Level: GROUP Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To start and identify a functional group of related transaction sets and provide control and application identification information. GS Functional ID M ID 2/2 "SH" (Ship Notice/Manifest) GS Application Sender's Code M AN 2/15 M AN 2/10 Same ID as ISA06. GS Application Receiver's Code M AN 2/15 M AN 10/10 Same ID as ISA08. GS Date M DT 8/8 GS Time M TM 4/8 GS06 28 Group Control Number M N0 1/9 GS Responsible Agency Code M ID 1/2 GS Version M AN 1/12 Segment: ST - TRANSACTION SET HEADER Level: HEADER Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To indicate the start of a Ship Notice/Manifest transaction set and to assign a control number. ST Transaction Set ID M ID 3/3 "856" ST Transaction Set Control Number M AN 4/9 June 2003 Page 2.1
7 Segment: BSN - BEGINNING SEGMENT Level: HEADER Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To identify ship notice number, date, time, and hierarchical structure code. BSN Transaction Set Purpose Code M ID 2/2 "00" (Original) BSN Shipment Identification M AN 2/30 Ship notice number BSN Date M DT 8/8 Ship Notice Date BSN Time M TM 4/8 Ship Notice Time BSN Hierarchical Structure Code O ID 4/4 M ID 4/4 "0001" (Shipment, Order, Packaging, Item) "0002" (Shipment, Order, Item, Packaging) BSN05 - Code '0001' is used for Pick and Pack Structure; code '0002' for Standard Carton Pack Structure. Segment: HL - HIERARCHICAL LEVEL Loop: HL Max Use: 1 Usage: MANDATORY PURPOSE: To identify the start of the shipment level and hierarchical level dependencies. HL Hierarchical ID Number M AN 1/12 Shipment level is "1". HL Hierarchical Parent ID Number O AN 1/12 Not used by VICS. HL Hierarchical Level Code M ID 1/2 "S" (Shipment) NOTE - HL02 is not used for the first HL segment of the transaction set, since it has no parent relationship. It is used in the other HL levels of the transaction. Segment: TD1 - CARRIER DETAILS Loop: HL Max Use: 20 Usage: REQUIRED PURPOSE: To specify transportation packaging, weight, and number of cartons shipped. TD Packaging Code O AN 3/5 M AN 3/5 TD Lading Quantity C N0 1/7 M N0 1/7 TD Commodity Code Qualifier O ID 1/1 Not used by VICS. TD Commodity Code C AN 1/30 Not used by VICS. TD Lading Description O AN 1/50 Not used by VICS. TD Weight Qualifier O ID 1/2 M ID 1/1 "G" (Gross Weight) TD Weight C R 1/10 M R2 1/8 TD Unit of Measure Code C ID 2/2 M ID 2/2 "LB" (Pounds) June 2003 Page 2.2
8 Segment: TD5 - CARRIER DETAILS PURPOSE: To specify the carrier, sequence of routing and port of discharge. TD Routing Sequence Code O ID 1/2 TD Identification Code Qualifier C ID 1/2 M ID 1/2 "2" (Standard Carrier Alpha Code) "91" (Assigned by Seller) See note. TD Identification Code C AN 2/80 M AN 2/80 SCAC code. See note. TD Transportation Method/Type Code C ID 1/2 See note. TD Routing C AN 1/35 M AN 1/35 Original carrier. TD Shipment/Order Status Code C ID 2/2 Not used by JCP. TD Location Qualifier O ID 1/2 O ID 2/2 "PE" Port of Entry TD Location Identifier C AN 1/30 Port of discharge TD502 - Code "91" is only used for Indirect Imports, and is limited to identifying ocean vessel carriers. TD503 - To obtain the SCAC code list for all carriers contact: National Motor Freight Trucking Association 2200 Mill Road Alexandria, VA TD504 - If utilizing a parcel service (UPS, FedEx, etc.), use code "U" (Private Parcel Service). For ocean vessel shipments to JCP Wholesale Distribution Centers, use code "S" (Ocean). TD507&8 - Used only for Indirect Imports, and is limited to ocean vessel shipments referencing port of discharge. Segment: REF - REFERENCE IDENTIFICATION PURPOSE: To specify bill of lading number. REF Reference Identification Qualifier M ID 2/3 "BM" (Bill of Lading Number) REF Reference Identification C AN 1/50 M AN 1/17 Bill of lading number. REF02 - Bill of lading number is "0" if TD504 is code "U" (Private Parcel Service). Segment: REF - REFERENCE IDENTIFICATION Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To specify carrier reference number (PRO number). REF Reference Identification Qualifier M ID 2/3 "CN" (Carrier's Reference Number) REF Reference Identification C AN 1/50 M AN 1/10 Carrier reference number. Segment: REF - REFERENCE IDENTIFICATION Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To specify the JCP load identification or Authorization number. REF Reference Identification Qualifier M ID 2/3 PUA (Pick Up Appointment Number); REF Reference Identification C AN 1/50 JCP load ID or Authorization number. June 2003 Page 2.3
9 Segment: PER - ADMINISTRATIVE COMMUNICATION CONTACT Loop: Max Use: 1 Usage: REQUIRED PURPOSE: To specify the Supplier contact information. PER Contact Function Code M ID 2/2 "IC" (Information Contact) PER02 93 Name O AN 1/60 PER Communication Number Qualifier C ID 2/2 M ID 2/2 "EM" (Electronic Mail) PER Communication Number C AN 1/256 M AN 1/80 Segment: DTM - DATE/TIME REFERENCE PURPOSE: To specify supplier's ship date. DTM Date/Time Qualifier M ID 3/3 "011" (Shipped) DTM Date C DT 8/8 M DT 8/8 Date shipped. DTM Time C TM 4/8 M TM 4/4 Time shipped (HHMM). Segment: DTM - DATE/TIME REFERENCE Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To specify supplier's estimated shipment arrival date. DTM Date/Time Qualifier M ID 3/3 "067" (Current Schedule Delivery) DTM Date C DT 8/8 M DT 8/8 Estimated shipment arrival date. Segment: N1 - NAME Loop: HL/N1 Max Use: 1 Usage: REQUIRED PURPOSE: To specify initial ship to (ST) location code for the shipment. N Entity Identifier Code M ID 2/3 "ST" (Ship To) N Name C AN 1/60 Not used by JCP. N Identification Code Qualifier C ID 1/2 M ID 2/2 "92" (Assigned By Buyer) N Identification Code C AN 2/80 M AN 5/6 Ship to location. See note. N104 - The ship to location code specified at this shipment level should contain the same ship to location code as specified at the order level if the shipment is sent directly to the ship to location as specified on the purchase order. If the shipment is not sent directly to the ship to location code on the purchase order, then this location code should identify the initial shipping location code (PEPS center, consolidator, etc.). June 2003 Page 2.4
10 Segment: N1 - NAME Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To identify supplier ship point location, or.the actual port of origin for the shipment N Entity Identifier Code M ID 2/3 "SF" (Ship From) N Name C AN 1/60 N Identification Code Qualifier C ID 1/2 M ID 2/2 "92" (Assigned By Buyer) N Identification Code C AN 2/80 M AN 2/17 Port of origin. N103&04 Fields are only used for Indirect Imports to specify the originating location of the ocean shipment, e.g. actual port of origin. Segment: N4 - GEOGRAPHIC LOCATION Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To identify the supplier geographic ship point. N City Name O AN 2/30 M AN 2/19 N State/Province Code O ID 2/2 M ID 2/2 N Postal Code O ID 3/15 M ID 5/9 N Country Code O ID 2/3 O ID 2/2 Segment: HL - HIERARCHICAL LEVEL Loop: HL Max Use: 1 Usage: MANDATORY PURPOSE: To identify the start of the order level and hierarchical level dependencies. HL Hierarchical ID Number M AN 1/12 See note. HL Hierarchical Parent ID Number O AN 1/12 M AN 1/12 See note. HL Hierarchical Level Code M ID 1/2 "O" (Order) HL01 - The value assigned to the first HL segment (Shipment level) will be "1", and is incremented by one for each subsequent HL segment within the transaction set. HL02 - Identifies the hierarchical ID number of the HL segment which the current HL segment is subordinate to (child of). Segment: PRF - PURCHASE ORDER REFERENCE PURPOSE: To identify purchase order number and date, and specify international import contract number. PRF Purchase Order Number M AN 1/22 M AN 8/12 See note. PRF Release Number O AN 1/30 Not used by JCP. PRF Change Order Sequence Number O AN 1/8 Not used by VICS. PRF Date O DT 8/8 Date is optional. PRF Assigned Identification O AN 1/20 Not used by JCP. PRF Contract Number O AN 1/30 O AN 12/12 See note. PRF01 For core furniture orders only, add the string 0500 to the end of the PO number. PRF06 - International orders may not have a purchase order number, only an import contract number. In this event, place a "0" in PRF01 and the appropriate import contract number in PRF06. June 2003 Page 2.5
11 Segment: PID - PRODUCT/ITEM DESCRIPTION Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To specify Fair Labor Standards compliance for all products in order. PIDO1 349 Item Description Type M ID 1/1 "S" (Structured (From Industry Code List)) PIDO2 750 Product Characteristic Code O ID 2/3 Not used by VICS. PIDO3 559 Agency Qualifier Code C ID 2/2 M ID 2/2 "VI" (VICS) PIDO4 751 Product Description Code C AN 1/12 M AN 2/2 FL (Compliant with Fair Labor Standards Act) Segment: TD5 - CARRIER DETAILS Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To specify shipment order status for a purchase order. TD Routing Sequence Code O ID 1/2 Not used by VICS. TD Identification Code Qualifier C ID 1/2 Not used by VICS. TD Identification Code C AN 2/80 Not used by VICS. TD Transportation Method/Type Code C ID 1/2 Not used by VICS. TD Routing C AN 1/35 Not used by VICS. TD Shipment/Order Status Code C ID 2/2 M ID 2/2 "BP" (Shipment partial, back order to follow) "CC" (Shipment complete) "CP" (Partial shipment, considered no back order) "CS" (Shipment complete with substitution) "DE" (Deleted Order) LS (Last Shipment) "SS" (Split Shipment) Segment: REF - REFERENCE IDENTIFICATION PURPOSE: To identify JCPenney's internal supplier number. REF Reference Identification Qualifier M ID 2/3 "IA" (Internal Vendor Number) REF Reference Identification C AN 1/50 M N0 6/6 JCP six digit supplier number. Segment: REF - REFERENCE IDENTIFICATION PURPOSE: To identify subdivision number. REF Reference Identification Qualifier M ID 2/3 "DP" (Department Number) REF Reference Identification C AN 1/50 M N0 3/3 Subdivision number. June 2003 Page 2.6
12 Segment: REF - REFERENCE IDENTIFICATION PURPOSE: To identify suppliers order number. REF Reference Identification Qualifier M ID 2/3 "VN" (Vendor Order Number) REF Reference Identification C AN 1/50 M N0 1/50 Suppliers order number. See note. REF02 - If the order number you send is more than 15 positions, we will return the right most 15 positions to you in an Order Status Inquiry transaction (869). For example, if your order number is we will send NOTE - For retail orders this segment is optional. Segment: REF - REFERENCE IDENTIFICATION Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To identify suppliers invoice number. REF Reference Identification Qualifier M ID 2/3 "IV" (Seller's Invoice Number) REF Reference Identification C AN 1/50 M N0 1/50 Suppliers invoice number. Segment: REF - REFERENCE IDENTIFICATION Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To identify the QC inspection report number for indirect imports. REF Reference Identification Qualifier M ID 2/3 "IP" (Inspection Report Number) REF Reference Identification C AN 1/50 NOTE This segment is used for indirect import orders only. Segment: N1 - NAME Loop: HL/N1 Max Use: 1 Usage: REQUIRED PURPOSE: To identify the mark for party. N Entity Identifier Code M ID 2/3 "Z7" (Mark-for Party) N Name C AN 1/60 Not used by JCP. N Identification Code Qualifier C ID 1/2 M ID 2/2 "92" (Assigned By Buyer) N Identification Code C AN 2/80 M N0 5/6 Store number. NOTE - This segment is optional for Indirect Imports to JCP Wholesale Distribution Centers. Segment: N3 - ADDRESS INFORMATION Loop: N1 Max Use: 2 Usage: OPTIONAL PURPOSE: To specify the mark for party address. N Address Information M AN 1/55 N Address Information O AN 1/55 June 2003 Page 2.7
13 Segment: N4 - GEOGRAPHIC LOCATION Loop: N1 Max Use: 1 Usage: OPTIONAL PURPOSE: To specify the mark for party geographic location. N City Name O AN 2/30 M AN 2/19 N State/Province Code O ID 2/2 M ID 2/2 N Postal Code O ID 3/15 M ID 5/9 N Country Code O ID 2/3 O ID 2/2 Segment: N1 - NAME Loop: HL/N1 Max Use: 1 Usage: REQUIRED PURPOSE: To identify the Bill-To party for the purchase order. N Entity Identifier Code M ID 2/3 "BT" (Bill-to-Party) N Name C AN 1/60 Not used by JCP. N Identification Code Qualifier C ID 1/2 M ID 2/2 "92" (Assigned By Buyer) N Identification Code C AN 2/80 M N0 5/6 Store number. See note. N104 - For Factory Ship or DFW Furniture, data element will contain the store number of where the order originated; i.e., June 2003 Page 2.8
14 NOTE The TARE LEVEL is only used and required for Indirect Import Ocean Shipments. Segment: HL - HIERARCHICAL LEVEL Level: TARE Loop: HL Max Use: 1 Usage: MANDATORY PURPOSE: To identify the start of the tare level and hierarchical level dependencies. HL Hierarchical ID Number M AN 1/12 See note. HL Hierarchical Parent ID Number O AN 1/12 M AN 1/12 See note. HL Hierarchical Level Code M ID 1/2 "T" (Shipping Tare) HL01 - The value assigned to the first HL segment (Shipment level) will be "1", and is incremented by one for each subsequent HL segment within the transaction set. HL02 - Identifies the hierarchical ID number of the HL segment which the current HL segment is subordinate to (child of). Segment: MAN - MARKS AND NUMBERS Level: TARE PURPOSE: To identify the Indirect Import Ocean Shipping Container number. MAN01 88 Marks and Numbers Qualifier M ID 1/2 M ID 2/2 "SM" (Shipper Assigned) MAN02 87 Marks and Numbers M AN 1/48 M AN 1/30 Unique number for each Ocean Shipping Container. June 2003 Page 2.9
15 IMPORTANT NOTE The segment specification pages have been listed in the sequence required for pick pack shipments. If the shipment is standard pack, the pack level segments "HL" and "MAN" are sent after the item level segments. Segment: HL - HIERARCHICAL LEVEL Level: PACK Loop: HL Max Use: 1 Usage: MANDATORY PURPOSE: To identify the start of the pack level and hierarchical level dependencies. HL Hierarchical ID Number M AN 1/12 See note. HL Hierarchical Parent ID Number O AN 1/12 M AN 1/12 See note. HL Hierarchical Level Code M ID 1/2 "P" (Pack) HL01 - The value assigned to the first HL segment (Shipment level) will be "1", and is incremented by one for each subsequent HL segment within the transaction set. HL02 - Identifies the hierarchical ID number of the HL segment which the current HL segment is subordinate to (child of). Segment: SLN - SUBLINE ITEM DETAIL Level: PACK Loop: HL Max Use: 100 Usage: OPTIONAL PURPOSE: To specify the individual component of the item identified in the LIN segment in the previous item level. This segment is only used in a Standard Pack Structure for sets of items packed in different cartons (lamp and shade). SLN Assigned ID M AN 1/20 Increment by one starting with one (1). SLN Assigned ID O AN 1/20 Not used by VICS. SLN Relationship Code M ID 1/1 "I" (Included) SLN Quantity C R 1/15 M N0 1/10 SLN05 C001 Composite Unit of Measure C C Composite Unit/Basis for Measurement Code M ID 2/2 "ST" (Set) SLN Unit Price C R 1/17 Not used by VICS. SLN Basis of Unit Price Code O ID 2/2 Not used by VICS. SLN Relationship Code O ID 1/1 Not used by VICS. SLN Product/Service ID Qualifier C ID 2/2 M ID 2/2 "IN" (Buyers Item Number) SLN Product/Service ID C AN 1/48 M AN 9/13 Retail. See note. SLN Product/Service ID Qualifier C ID 2/2 "UP" (U.P.C. Consumer Package Code) SLN Product/Service ID C AN 1/48 C AN 12/12 U.P.C. number assigned to SKU in SLN10. SLN Product/Service ID Qualifier C ID 2/2 "EN" (European Article Number) SLN Product/Service ID C AN 1/48 C AN 13/13 EAN number assigned to SKU in SLN10. SLN10 - If SLN is being sent to denote an individual component, send the lot/line/size description in the following format: AAAABBBBCCCCC where AAAA = lot number, BBBB = line number, CCCCC = size desc. NOTE - This segment, when used in a Standard Carton Pack Structure at the Pack Level, may only be used to specify an individual component of the item identified in the LIN segment in the previous item level. The quantity specified in SN102, at the Item Level, represents the number of sets, and SN103 will contain code ST, to identify it as a set. Each subsequent MAN Segment, within this PACK Level, identifies the carton ID for each component identified in the SLN Segment. Additional Pack Level SLN segments and MAN segments are used to represent each different component of the SKU. June 2003 Page 2.10
16 Segment: PKG MARKING, PACKAGING, LOADING Level: PACK Loop: HL Max Use: 1 Usage: OPTIONAL PURPOSE: To identify Catalog s Color Coordinate number or Retail s floor ready procedures compliance. PKG Item Description Type C ID 1/1 M ID 1/1 F (Free-Form) PKG Packaging Characteristic Code O ID 1/5 OPI (Optional Procedure Indicator) PKG Agency Qualifier Code C ID 2/2 Not used by JCP. PKG Packaging Description Code C AN 1/7 Not used by JCP. PKG Description C AN 1/80 M N0 1/2 Retail - Y Catalog - 45 or 50 or 55 NOTE Retail shipments will use PKG01, PKG02 and PKG05. Catalog shipments for Color Coordinate program will use PKG01 and PKG05. Segment: MAN - MARKS AND NUMBERS Level: PACK PURPOSE: To identify the UCC 128 serial shipping container code number. MAN01 88 Marks and Numbers Qualifier M ID 1/2 "GM" (UCC 128 Serial Shipping Container Code Format) MAN02 87 Marks and Numbers M AN 1/48 M AN 20/20 Unique number for each 128 label. See note. MAN02 - The format of the UCC 128 shipping container number is 'AABCCCCCCCDDDDDDDDDE', where AA = UCC 128 serial shipping container code qualifier, B = extension digit, CCCCCCC = UCC manufacturing ID number (including number system character preceded by zero), DDDDDDDDD = shipping container serial number, E = mod 10 check digit character. NOTE - For Retail shipments, we will not accept an 856 if you do not have the ability to identify each carton with a scannable UCC 128 shipping container serial number. For a detail write-up on scannable UCC 128 shipping container code number specifications, contact the Uniform Code Council ( ). Segment: HL - HIERARCHICAL LEVEL Level: ITEM Loop: HL Max Use: 1 Usage: MANDATORY PURPOSE: To identify the start of the item level and hierarchical level dependencies. HL Hierarchical ID Number M AN 1/12 See note. HL Hierarchical Parent ID Number O AN 1/12 M AN 1/12 See note. HL Hierarchical Level Code M ID 1/2 "I" (Item) HL01 - The value assigned to the first HL segment (Shipment level) will be "1", and is incremented by one for each subsequent HL segment within the transaction set. HL02 - Identifies the hierarchical ID number of the HL segment which the current HL segment is subordinate to (child of). June 2003 Page 2.11
17 Segment: LIN - ITEM IDENTIFICATION Level: ITEM PURPOSE: To specify SKU number, and U.P.C. or EAN numbers. There is one LIN segment for each SKU. LIN Assigned ID O AN 1/20 Not used by JCP. LIN Product/Service ID Qualifier M ID 2/2 "IN" (Buyers Item Number) LIN Product/Service ID M AN 1/48 M AN 9/13 Retail. See note. M AN 11/11 Catalog. LIN Product/Service ID Qualifier C ID 2/2 "UP" (U.P.C. Consumer Package Code) Note LIN Product/Service ID C AN 1/48 C AN 12/12 U.P.C. number. LIN Product/Service ID Qualifier C ID 2/2 "EN" (European Article Number). See note. LIN Product/Service ID C AN 1/48 C AN 13/13 EAN number. LIN03 - If purchase order is for Retail merchandise, send the lot/line/size description in the following format: AAAABBBBCCCCC where AAAA = lot number, BBBB = line number, CCCCC = size description. For Catalog merchandise, we will send lot/sku in the following format: AAAAAAABBBB where AAAAAAA = lot number, BBBB = SKU number. LIN04 - U.P.C. numbers are used on a selective basis. U.P.C. numbers will only be sent for Retail orders and correspond to the SKU in LIN03. LIN06 - EAN numbers are used on a selective basis. EAN numbers will only be sent for Retail orders and correspond to the SKU in LIN03. Do not send both EAN and U.P.C. numbers, only one or the other. Segment: SN1 - ITEM DETAIL (SHIPMENT) Level: ITEM PURPOSE: To specify SKU quantity shipped and original purchase order quantity. SN Assigned ID O AN 1/20 Not used by VICS. SN Number of Units Shipped M R 1/10 M N0 1/10 Number of sellable units. SN Unit Of Measure Code M ID 2/2 "AS" (Assortment); "BX" (Box); "CA" (Case); "EA" (Each); "FT" (Feet); "PK" (Package); "PC" (Piece); "PR" (Pair); "RL" (Roll); "ST" (Set); "YD" (Yard) SN Quantity Shipped to Date O R 1/15 Not used by JCP. SN Quantity Ordered C R 1/15 O N0 1/10 Original quantity ordered less cancellations. SN Unit Of Measure Code C ID 2/2 O ID 2/2 "AS" (Assortment); "BX" (Box); "CA" (Case); "EA" (Each); "FT" (Feet); "PK" (Package); "PC" (Piece); "PR" (Pair); "RL" (Roll); "ST" (Set); "YD" (Yard) SN105 -The quantity ordered comes from the original quantity on the purchase order, less any cancellations the supplier makes to the original quantity. This D/E and SN106 are required for Catalog. June 2003 Page 2.12
18 Segment: SLN - SUBLINE ITEM DETAIL Level: ITEM Loop: HL Max Use: 100 Usage: OPTIONAL PURPOSE: To specify the component SKUs within an assortment. There is one SLN segment for each SKU within an assortment. The component number is specified in the preceding LIN segment. SLN Assigned ID M AN 1/20 Increment by one starting with one (1). SLN Assigned ID O AN 1/20 Not used by VICS. SLN Relationship Code M ID 1/1 "I" (Included) SLN Quantity C R 1/15 M N0 1/10 See note. SLN05 C001 Composite Unit of Measure C C Composite Unit or Basis for Measurement Code M ID 2/2 "AS" (Assortment); "BX" (Box); "CA" (Case); "EA" (Each); "FT" (Feet); "PK" (Package); "PC" (Piece); "PR" (Pair); "RL" (Roll); "ST" (Set); "YD" (Yard) SLN Unit Price C R 1/17 C R2 1/17 SLN Basis of Unit Price Code O ID 2/2 WH (Wholesale) SLN Relationship Code O ID 1/1 Not used by VICS. SLN Product/Service ID Qualifier C ID 2/2 M ID 2/2 "IN" (Buyers Item Number) SLN Product/Service ID C AN 1/48 M AN 9/13 Retail. See note. SLN Product/Service ID Qualifier C ID 2/2 "UP" (U.P.C. Consumer Package Code) Note SLN Product/Service ID C AN 1/48 C AN 12/12 U.P.C. number assigned to SKU in SLN10. SLN Product/Service ID Qualifier C ID 2/2 "EN" (European Article Number). See note. SLN Product/Service ID C AN 1/48 C AN 13/13 EAN number assigned to SKU in SLN10. SLN04 - The quantity should reflect the number of sellable units and not the physical count of items. SLN10 - If SLN is being sent to denote a component, send component's lot/line/size description in the following format: AAAABBBBCCCCC where AAAA = lot number, BBBB = line number, CCCCC = size desc. NOTE - Segment is only sent for Retail merchandise. Segment: TD5 - CARRIER DETAILS Level: ITEM PURPOSE: To specify ship/order status code for SKUs that have not been shipped per the original purchase order. TD Routing Sequence Code O ID 1/2 Not used by VICS. TD Identification Code Qualifier C ID 1/2 Not used by VICS. TD Identification Code C AN 2/80 Not used by VICS. TD Transportation Method/Type Code C ID 1/2 Not used by VICS. TD Routing C AN 1/35 Not used by VICS. TD Shipment/Order Status Code C ID 2/2 M ID 2/2 "BP" (Shipment partial, back order to follow) "CC" (Shipment complete) "CP" (Partial shipment, considered no back order) "CS" (Shipment complete with substitution) IC (Item canceled) June 2003 Page 2.13
19 Segment: CTT - TRANSACTION TOTALS Level: TRAILER Loop: Max Use: 1 Usage: REQUIRED PURPOSE: Count of HL segments in ship notice/manifest transaction set. CTT Number Of Line Items M N0 1/6 Number of HL segments in the transaction. Segment: SE - TRANSACTION SET TRAILER Level: TRAILER Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To indicate the end of a Ship Notice/Manifest transaction set and provide a count of the transmitted segments, including the beginning (ST) and ending (SE) segments. SE01 96 Number Of Included Segments M N0 1/10 Count of all segments including ST and SE. SE Transaction Set Control Number M AN 4/9 Same number as in ST02. Segment: GE - FUNCTIONAL GROUP TRAILER Level: GROUP Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To define the end of a functional group of related transaction sets. GE01 97 No. of Included Transaction Sets M N0 1/6 GE02 28 Group Control Number M N0 1/9 Same number as in GS06. Segment: IEA - INTERCHANGE CONTROL TRAILER Level: ENVELOPE Loop: Max Use: 1 Usage: MANDATORY PURPOSE: To define the end of an interchange of one or more functional groups and interchange related control. IEA01 I16 Number Of Included Groups M N0 1/5 IEA02 I12 Interchange Control Number M N0 9/9 Same number as in ISA13. June 2003 Page 2.14
20 MERCHANDISE SHIPMENT PACKAGING STRUCTURES Pick Pack Shipments This type of shipment is most prevalent in the soft goods area. The pick pack environment is where different items are picked to fill a carton. An example would be a carton containing multiple colors and sizes of a specific style women's dress, with variable quantities for each color and size. Pick Pack Shipment Example The illustration below shows the sequence in which various HL segments should be generated for a pick pack type shipment. The illustration assumes that the shipment was for 2 purchase orders. The first purchase order has 2 cartons with 3 unique SKUs in the first carton and 2 unique SKUs in the second carton. The second purchase order has 3 cartons with 3 unique SKUs in the first 2 cartons and 1 SKU in the last carton. Each box represents one hierarchical level (one HL segment followed by data elements). The number in the top left corner is the hierarchical sequence number (the number in HL01). The number in the top right corner is the parent ID (the number in HL02). 01 Shipment Order 1 Order Carton 1 Carton 2 Carton 3 Carton 4 Carton 5 04 SKU A SKU D SKU P SKU S SKU V SKU B SKU E SKU Q SKU T SKU C SKU R SKU U June 2003 Page 3.1
21 Standard Pack Shipments This type of shipment is most prevalent in the hard goods area. The standard pack environment is where a carton has been pre-packed and usually contains one or more pieces of a specific item. An example would be a carton containing 10 bowls of a specific style. If a shipment was for 70 bowls, there would be 7 standard pack cartons required for the shipment. Standard Pack Shipment Example The illustration below shows the sequence in which various HL segments should be generated for a standard pack type shipment. The illustration assumes that the shipment was for 2 purchase orders. The first purchase order contained 5 cartons (cartons 1 to 5), the second purchase order contained 7 cartons (cartons 6 to 12). The contents of cartons 1, 2 and 3 were identical, each of these cartons contained identical quantities of SKU A. Cartons 4 and 5, contain identical quantities of SKU B. Cartons 6, 7, and 8, contain identical quantities of SKU C. Cartons 9, 10, and 11, contain identical quantities of SKU D, and carton 12 contains SKU E. Each box represents one hierarchical level (one HL segment followed by data elements). The number in each box (top left corner) is the hierarchical sequence number (the number in HL01). The number in the top right corner is the parent ID (the number in HL02). 01 Shipment Order 1 Order SKU A SKU B SKU C SKU D SKU E Carton 1 Carton 4 Carton 6 Carton 9 Carton Carton 2 Carton 5 Carton 7 Carton Carton 3 Carton 8 Carton 11 June 2003 Page 3.2
22 HL RELATIONSHIPS IN THE 856 Business examples for the HL segments used in a Pick Pack structure NOTE - The data element separator is represented by a, the segment terminator is. 1 - ABC supplier has received one purchase order from a single store for 24 pants, all of the same size and color, which are inventoried under 1 SKU number. He picks the 24 pants and can get them in two cartons. His ship notice to the retailer reflects 6 HL segments. HL 1 S Shipment level with hierarchical ID number of 1 (one). HL02 is not used, there is no parent. HL 2 1 O Order level with hierarchical ID number of 2 and HL parent ID number of 1. HL 3 2 P Pack level with hierarchical ID number of 3 and HL parent ID number of 2. HL 4 3 I Item level with hierarchical ID number of 4 and HL parent ID number of 3. HL 5 2 P Pack level with hierarchical ID number of 5 and HL parent ID number of 2. HL 6 5 I Item level with hierarchical ID number of 6 and HL parent ID number of ABC supplier has received one purchase order from a single store for 12 pants, all of different sizes and colors, which are inventoried under 12 SKU numbers. He picks the 12 pants and can get all of them in one carton. His ship notice to the retailer reflects 15 HL segments. HL 1 S Shipment level with hierarchical ID number of 1 (one). HL02 is not used, there is no parent. HL 2 1 O Order level with hierarchical ID number of 2 and HL parent ID number of 1. HL 3 2 P Pack level with hierarchical ID number of 3 and HL parent ID number of 2. HL 4 3 I Item level (SKU 1) with hierarchical ID number of 4 and HL parent ID number of 3. HL 5 3 I Item level (SKU 2) with hierarchical ID number of 5 and HL parent ID number of 3. HL 6 3 I Item level (SKU 3) with hierarchical ID number of 6 and HL parent ID number of 3. HL 7 3 I Item level (SKU 4) with hierarchical ID number of 7 and HL parent ID number of 3. HL 8 3 I Item level (SKU 5) with hierarchical ID number of 8 and HL parent ID number of 3. HL 9 3 I Item level (SKU 6) with hierarchical ID number of 9 and HL parent ID number of 3. HL 10 3 I Item level (SKU 7) with hierarchical ID number of 10 and HL parent ID number of 3. HL 11 3 I Item level (SKU 8) with hierarchical ID number of 11 and HL parent ID number of 3. HL 12 3 I Item level (SKU 9) with hierarchical ID number of 12 and HL parent ID number of 3. HL 13 3 I Item level (SKU 10) with hierarchical ID number of 13 and HL parent ID number of 3. HL 14 3 I Item level (SKU 11) with hierarchical ID number of 14 and HL parent ID number of 3. HL 15 3 I Item level (SKU 12) with hierarchical ID number of 15 and HL parent ID number of 3. June 2003 Page 3.3
23 Business examples for the HL segments used in a Pick Pack structure (continued) 3 - ABC supplier has received three purchase orders from the same store for 144 shirts. The first order is 24 white shirts and 24 blue shirts. The second order is for 6 red shirts, 6 orange shirts, 6 yellow shirts, 6 purple shirts, 6 brown shirts, and 6 green shirts. The third order is for 60 black shirts. The orders represent 9 SKU numbers in his inventory. He fills all three orders and can put 12 shirts in a carton. He packs 4 cartons for the first order (12 white, 12 white, 12 blue, 12 blue), 3 cartons for the second order (6 red + 6 orange, 6 yellow + 6 purple, 6 brown + 6 green), and 5 cartons (12 black, 12 black, 12 black, 12 black, 12 black) for the third order. His ship notice to the retailer will reflect 31 HL segments. HL 1 S Shipment level with hierarchical ID number of 1. HL02 is not used, there is no parent. HL 2 1 O Order level (1st order) with hierarchical ID number of 2 and HL parent ID number of 1. HL 3 2 P Pack level (1st order 1st carton) with hierarchical ID number of 3 and HL parent ID number of 2. HL 4 3 I Item level (1st order 1st carton 12 white) with hierarchical ID number of 4 and HL parent ID number of 3. HL 5 2 P Pack level (1st order 2nd carton) with hierarchical ID number of 5 and HL parent ID number of 2. HL 6 5 I Item level (1st order 2nd carton 12 white) with hierarchical ID number of 6 and HL parent ID number of 5. HL 7 2 P Pack level (1st order 3rd carton) with hierarchical ID number of 7 and HL parent ID number of 2. HL 8 7 I Item level (1st order 3rd carton 12 blue) with hierarchical ID number of 8 and HL parent ID number of 7. HL 9 2 P Pack level (1st order 4th carton) with hierarchical ID number of 9 and HL parent ID number of 2. HL 10 9 I Item level (1st order 4th carton 12 blue) with hierarchical ID number of 10 and HL parent ID number of 9. HL 11 1 O Order level (2nd order) with hierarchical ID number of 11 and HL parent ID number of 1. HL P Pack level (2nd order 1st carton) with hierarchical ID number of 12 and HL parent ID number of 11. HL I Item level (2nd order 1st carton 6 red) with hierarchical ID number of 13 and HL parent ID number of 12. HL I Item level (2nd order 1st carton 6 orange) with hierarchical ID number of 14 and HL parent ID number of 12. HL P Pack level (2nd order 2nd carton) with hierarchical ID number of 15 and HL parent ID number of 11. HL I Item level (2nd order 2nd carton 6 yellow) with hierarchical ID number of 16 and HL parent ID number of 15. HL I Item level (2nd order 2nd carton 6 purple) with hierarchical ID number of 17 and HL parent ID number of 15. HL P Pack level (2nd order 3rd carton) with hierarchical ID number of 18 and HL parent ID number of 11. HL I Item level (2nd order 3rd carton 6 brown) with hierarchical ID number of 19 and HL parent ID number of 18. HL I Item level (2nd order 3rd carton 6 green) with hierarchical ID number of 20 and HL parent ID number of 18. HL 21 1 O Order level (3rd order) with hierarchical ID number of 21 and HL parent ID number of 1. HL P Pack level (3rd order 1st carton) with hierarchical ID number of 22 and HL parent ID number of 21. HL I Item level (3rd order 1st carton 12 black) with hierarchical ID number of 23 and HL parent ID number of 22. HL P Pack level (3rd order 2nd carton) with hierarchical ID number of 24 and HL parent ID number of 21. HL I Item level (3rd order 2nd carton 12 black) with hierarchical ID number of 25 and HL parent ID number of 24. HL P Pack level (3rd order 3rd carton) with hierarchical ID number of 26 and HL parent ID number of 21. HL I Item level (3rd order 3rd carton 12 black) with hierarchical ID number of 27 and HL parent ID number of 26. HL P Pack level (3rd order 4th carton) with hierarchical ID number of 28 and HL parent ID number of 21. HL I Item level (3rd order 4th carton 12 black) with hierarchical ID number of 29 and HL parent ID number of 28. HL P Pack level (3rd order 5th carton) with hierarchical ID number of 30 and HL parent ID number of 21. HL I Item level (3rd order 5th carton 12 black) with hierarchical ID number of 31 and HL parent ID number of 30. June 2003 Page 3.4
856 Ship Notice/Manifest Pick/Pack Structure DIRECT TO STORE
856 Ship Notice/Manifest Pick/Pack Structure DIRECT TO STORE Macy s VICS Version 4050 VICS Document Mapping Effective 06/01/07 PICK and PACK STRUCTURE Shipment/Order/Pack/Item The following is an outline
More informationPICK and PACK STRUCTURE. Shipment/Order/Pack/Item. The following is an outline of what is required when receiving VICS 856 Ship Notice from a vendor.
856 Ship Notice/Manifest Pick/Pack Structure WITH VENDOR DIRECT TO CONSUMER (V2C) ORDERS Macy s VICS Version 4010 VICS Document Mapping Effective 1/30/2015 PICK and PACK STRUCTURE Shipment/Order/Pack/Item
More information856 Ship Notice/Manifest Standard Carton Pack Structure
856 Ship Notice/Manifest Standard Carton Pack Structure Macy s VICS Version 4010 VICS Document Mapping Effective 02/14/09 The following is an outline of what is expected when receiving VICS 856 Ship Notice
More information855 Purchase Order Acknowledgment
855 Purchase Order Acknowledgment VICS EDI/V4030/855: 855 Purchase Order Acknowledgment Modified: 10/11/2006 Notes: Table of Contents Purchase Order Acknowledgment. 1 +++++ ISA - Interchange Control Header..
More information856 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 information856 Ship Notice/Manifest Standard Carton Pack Structure
856 Ship Notice/Manifest Standard Carton Pack Structure Macy s VICS Version 5010 VICS Document Mapping Effective 06/12/09 The following is an outline of what is expected when receiving VICS 856 Ship Notice
More information856 Ship Notice/Manifest Pick/Pack Structure
856 Ship Notice/Manifest Pick/Pack Structure Macy s GS1 Version 4010 GS1 Document Mapping Effective 09/22/2017 PICK and PACK STRUCTURE Shipment/Order/Pack/Item The following is an outline of what is required
More information856 Ship Notice/Manifest Pick/Pack Structure
856 Ship Notice/Manifest Pick/Pack Structure Macy s GS1 Version 5010 GS1 Document Mapping Effective 09/22/2017 PICK and PACK STRUCTURE Shipment/Order/Pack/Item The following is an outline of what is required
More information856 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 informationIf you have questions or need assistance with this document, call
Reverse 856 Outbound Ship Notice/Manifest Pick/Pack Structure Macy s Version 4010 Document Mapping Effective 06/01/07 PICK and PACK STRUCTURE Shipment/Order/Pack/Item The following is an outline of what
More information856 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 information856 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 information856 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 information856 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 information856 - Ship Notice/Manifest
General Information All Ship Notice/Manifest documents must contain UCC 128 carton label information. Shipments must comply with Von Maur, Inc. routing instructions, available through the traffic department.
More informationBelk 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 informationBon Ton 810 Mapping 4010 VICS Effective
Bon Ton 810 Mapping 4010 VICS Effective 4-18-13 ISA Interchange Control Header ISA01 2 '00' ISA02 10 Must be BLANK ISA03 2 '00' ISA04 10 Must be BLANK ISA05 2 Interchange ID Qualifier ISA06 9/15 Interchange
More informationACE 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 information856 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 informationSuper 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 information856 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 informationEDI 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 informationBIG 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 information856 Advance Ship Notice VICS / GTIN
SEGMENT: ST Transaction Set Header ST01 143 Transaction Set Identifier Code 856 - Advanced Ship Notice M 3/3 ST02 329 Transaction Set Control Number Assigned by sender M 4/9 SEGMENT: BSN Beginning Segment
More information856 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 informationFILE 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 information856 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 information856 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 information856 Ship Notice/Manifest
856 Ship Notice/Manifest X12/V4010/856 : 856 Ship Notice/Manifest Version: 3.0 Author: Spice Technology Group Company: Town Shoes Ltd Publication: 2/11/2015 Trading Partner: Notes Prepared By: SPICE Technology
More informationThis 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 information856 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 informationTarget 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 informationAdvance 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 informationMMG 856 Ship Notice Manifest SUPPLIER
acy s erchandising Group G 856 Ship Notice anifest PICK AND PACK STRUCTURE Shipment/Order/Pack/Item The following is an outline of what is expected when transmitting ANSI 856 Pick And Pack Structure Ship
More information856 Ship Notice/Manifest v4010
INTRODUCTION This document specifies Sears requirements for transmission of the 856 Ship Notice/Manifest transaction set. The document includes the data requirements for reporting all shipments made directly
More information856 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 informationEDI 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 information856 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 informationIMPLEMENTING EDI Version 4010 ADVANCE SHIP NOTICES
IMPLEMENTING EDI Technical Requirements Section 02 May 13, 1998 Document Version 4010.1 Revised Jan, 2004 - Registered Trade Mark of the C:\WORD\DATA\VENREF\hbc856.doc(3/16/2011) TABLE OF CONTENTS TRANSACTION
More informationMessage 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 information856 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 informationANSI 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 information9/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 informationPos. 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 informationTSC 856 Store & DC. Message Implementation Guideline. based on. 856 Ship Notice/Manifest X
Message Guideline TSC 856 Store & DC based on 856 Ship Notice/Manifest X12 004010 Version: 1.7 Variant: 1.0 Issue date: 10/19/2015 Updated: 4/8/2016 Author: TSC 1 Message Structure... 3 3 Segments... 4
More informationEDI 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 informationShip 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 informationVerizon 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 informationRite 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 informationToyoda 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 information856 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 informationGrand & 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 informationOperating Division Production S/R ID Test S/R ID. Neiman Marcus Group (NMG) 08 / INBOUND / OUTBOUND, VERSION *M = MANDATORY
5010 Maps Last modified: 06/14/18 Mapping Standards Non Standard Data The Neiman Marcus Group strictly adheres to the X12 standards as specified in the Retail Industry Conventions and Implementation Guidelines
More informationTarget 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 information856 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 informationEDI 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 information856 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 information1830 Route 130 North Burlington, NJ Phone: (609) Fax: (609)
1830 Route 130 North Burlington, NJ 08016 Phone: (609) 387-7800 Fax: (609) 387-2764 February 23, 2009 Table of Content Introduction... 1 ST Transaction Set Header... 8 BSN Beginning Segment for Ship Notice...
More information810 Invoice X12/V4010/810: 810 Invoice Version: 1.1 Draft
810 Invoice X12/V4010/810: 810 Invoice Version: 1.1 Draft X12V4010 1 Exim CHANGE LOG Chg# Date Noted Description of Change Change By Version Num. 1 Original 1.0 2 9/1/2017 Updated Segment and Element requirement
More informationRite Aid Corporation
Segment Rite Aid Corporation 856 Advance Shipment Notice (ASN) Segment Attributes Location EDI Control Segments ISA Interchange Control Header M Control GS Functional Group Header M Control ST Transaction
More informationFunctional 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 information856 Ship Notice/Manifest
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
More information10/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 informationKOHL S INVOICE PROGRAMMER'S REFERENCE GUIDE VERSION 4010VICS. Revised: July 10, 2015
PROGRAMMER'S REFERENCE GUIDE VERSION 4010VICS Revised: July 10, 2015 Within the retail industry, there exists two uses of the retail invoice document: Detail Invoicing and Consolidated Invoicing. Kohl
More information856 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 informationEDI 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 informationTable of Contents 7 <PH> <PH> 13 <PH> 16 <PH> 17 <PH> 19 <PH> 20 <PH>
Table of Contents 810 Invoice.................................................................................................................................... ISA Interchange Control Header......................................................................................................
More information856 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 informationMMG 856 Inbound Ship Notice/Manifest Macy s Merchandising Group ANSI X.12 Version 4010 ANSI X.12 Document Mapping Effective 03/15/2016
MMG 856 Inbound Ship Notice/Manifest Macy s Merchandising Group ANSI X.12 Version 4010 ANSI X.12 Document Mapping Effective 03/15/2016 STANDARD CARTON PACK STRUCTURE SHIPMENT/ORDER/ITEM/PACK The following
More informationImplementation 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 informationCSI EDI ASN 856 specification Version /21/ ASN Advance Shipping Notice. Version: ANSI X /21/2012 V 1.
Charming Technology Services EDI Specification 856 - ASN Advance Shipping Notice Version: ANSI X12 004030 07/21/2012 V 1.2 From domestic vendor to CSI From Domestic Vendors to CSI 1 of 51 Table of Content
More information856 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 informationIntroduction: 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 informationJL 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 information850 Purchase Order. Functional Group ID= PO
850 Purchase Order Functional Group ID= PO Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Transaction Set (850) for use within
More informationMGM 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 informationOrchard Supply Company Ship Notice / Manifest
Orchard Supply Company Ship Notice / Manifest Ship Notice / Manifest X12 4010 Author: Trading Partner: Created: Modified: Notes: Orchard Supply Company ISA/GS Qualifier, Receiver ID TEST PRODUCTION ZZ,
More informationAgilent 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 information856 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 informationKOHL'S 810 INVOICE PROGRAMMER'S REFERENCE GUIDE VERSION 4010VICS
KOHL'S 810 INVOICE PROGRAMMER'S REFERENCE GUIDE VERSION 4010VICS Revised: January 31, 2007 1 810 INVOICE Definition Within the retail industry, there exists two uses of the retail invoice document: Detail
More informationJCPenney 754 Routing Instructions Version 4030
TABLE OF CONTENTS Page JCPenney Mapping Differences Between Versions 3060 and 4030... 1.2 Transaction Set Purpose... 1.3 Routing Instructions Segment Hierarchy... 1.3 +++++++++++++++++++++++++++++++++++++++
More informationDo it Best Corp. Advance Ship Notice (ASN) Guidelines
Do it Best Corp. Advance Ship Notice (ASN) Guidelines Introduction The purpose of this document is to present and explain Advance Shipment Notices (ASN s) as they pertain to shipments into a Retail Service
More information856 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 informationAdvanced 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 information856 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 informationMessage 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 information850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0
850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 X12V4010 1 Exim 850 Purchase Order Functional Group=PO This Draft Standard for Trial Use contains the format and establishes the data contents
More informationLOWE'S EDI. 856 Advance Ship Notice. Version:
LOWE'S EDI 856 Advance Ship Notice Version: 004010 Author: Lowes Companies, Inc. Modified: 4/3/2009 Notes: This 856 Implementation Guide is the same for all vendors submitting the ASN. Lowe's Companies,
More informationMessage 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 informationDENSO 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 information810 - Invoice. Version: X12
810 - Invoice Version: 004010 X12 Company: DOT FOODS, INC. Publication: 12/23/2010 810 Invoice Functional Group= IN Purpose: This Draft Standard for Trial Use contains the format and establishes the data
More information404 Rail Carrier Shipment Information
404 Rail Carrier Shipment Information X12/V4010/404 : 404 Rail Carrier Shipment Information Company: General Mills Modified: 1/11/2018 Notes: Table of Contents 404 Rail Carrier Shipment Information.....................................................................................................
More information855 Inbound Purchase Order Acknowledgment
855 Inbound Purchase Order Acknowledgment Macy s VICS Version 4050 VICS Document Mapping Effective 06/01/07 The following is an outline of what is required when receiving VICS 855 Purchase Order Acknowledgments
More informationMessage 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 informationL & 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 information856 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 information12/19/2017 Ship Notice/Manifest - 856
856 Ship Notice/Manifest Functional Group= SH Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use
More information810 Invoice. Version: 2.0 Draft
810 Invoice Version: 2.0 Draft Author: vendors@finishline.com Company: The Finish Line, Inc. Publication: 8/1/2016 Trading Partner: FINISHLINE/ZZ Created: 7/28/2016 Modified: 1/30/2017 Notes: Table of
More informationAMTEX 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 informationEDI 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