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 Introduction: 856 Ship Notice/ Manifest... 4 Envelope details... 7 ISA Interchange Control Header... 7 GS Functional Control Header... 9 ST Transaction Set Header... 10 ASN Header... 11 BSN Beginning Segment for Ship Notice... 11 Shipment Level... 12 HL Reference Identification (Shipment)... 12 TD1 Carrier Details (Quantity and Weight)... 13 TD5 Carrier Details (Routing Sequence/Transit Time)... 14 TD4 Carrier Details (Special Handling)... 15 REF Reference Identification... 16 PER Administrative Communications Contact... 17 DTM Date/Time Reference... 18 N1 Address Name... 19 N3 Address Information... 20 N4 Geographic Location... 21 Equipment Level... 22 HL Reference Identification (Equipment)... 22 TD1 Carrier Details (Quantity and Weight)... 23 TD3 Carrier Details (Equipment)... 24 Order Level... 25 HL Reference Identification (Order Level)... 25 PRF Purchase Order Reference... 26 TD1 Carrier Details (Quantity and Weight)... 27 TD5 Carrier Details (Routing Sequence/Transit Time)... 28 REF Reference Identification... 29 DTM Date/Time Reference... 30 N1 Address Name... 31 N3 Address Information... 32 N4 Geographic Location... 33 Carton Level... 34 HL Reference Identification (Pack: Carton Level)... 34 PO4 Item Physical details... 35 PKG Marking, Packaging, Loading... 36 TSD Trailer Shipment Details... 37 MAN Marks and Numbers... 38 Item Level... 39 HL Reference Identification (Item Level)... 39 LIN Item Identification... 40 SN1 Item Detail (Shipment)... 41 SLN Subline Item Details... 42 From Domestic Vendors to CSI 2 of 51
Summary detail... 45 CTT Transaction Totals... 45 Enveloping summary detail... 46 SE Transaction Set Trailer... 46 GE Functional Group Trailer... 47 IEA Interchange Control Trailer... 48 Sample of pick and pack 856... 49 Changes Summary... 51 From Domestic Vendors to CSI 3 of 51
Introduction: 856 Ship Notice/ Manifest Functional Group=SH This specification contains the format and establishes the data contents of the ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey Information. IMPORTANT: ALL ADVANCE SHIPMENT NOTICE/MANIFEST DOCUMENTS NEED TO MATCH EXACTLY WHAT WILL BE RECEIVED ON THE PHYSICAL SHIPMENT. All vendors are required to use Pick and Pack structure (BSN05 = 0001). This is the only acceptable EDI ASN format. Pick and Pack structure (BSN05 = 0001 ): This is the preferred method for Charming Shoppes. The transaction hierarchy is: Shipment Equipment Order Pack Item From Domestic Vendors to CSI 4 of 51
Heading: ST Transaction Set Header M 1 BSN Beginning Segment for Ship Notice M 1 Detail: LOOP ID HL (SHIPMENT LEVEL) HL Hierarchical Level Shipment Level M 1 TD1 Carrier Details (Quantity and Weight) O 1 TD5 Carrier Details (Routing Sequence) M 1 TD4 Carrier Details (Special Handling) O 1 REF Reference Identification M >1 PER Administrative Communications Contact O 1 DTM Date/Time Reference M >1 LOOP ID HL/N1 N1 Name M 1 N3 Address Information O 2 N4 Geographic Location O 1 HL-S HL-S-N1 LOOP ID HL (TRANS. EQUIPMENT LEVEL) HL Hierarchical Level Transportation Equipment Level M 1 TD1 Carrier Details (Quantity and Weight) M 1 TD3 Carrier Details (Equipment) M 1 HL-E LOOP ID HL (ORDER LEVEL) HL Hierarchical Level Order Level M 1 PRF Purchase Order Reference M 1 TD1 Carrier Details (Quantity and Weight) O 1 TD5 Carrier Details (Routing Sequence/Transit O 1 REF Time) Reference Identification M >1 DTM Date/Time/Period O >1 LOOP ID HL-O N1 N1 Address Name M 1 N3 Address Information O 2 N4 Geographic Location O 1 HL-O HL-O-N1 LOOP ID HL (TRANS. Pack LEVEL) HL Hierarchical Level Transportation Pack Level M 1 PO4 Item Physical details M 20 PKG Marking, Packaging, Loading O TSD Trailer Shipment Details O 1 MAN Marks and Numbers M >1 HL-P From Domestic Vendors to CSI 5 of 51
LOOP ID HL (ITEM LEVEL) HL Hierarchical Level Item Level M 1 LIN Item Identification M 1 SN1 Item Detail (Shipment) M 1 SLN Sub Line Item Detail M >1 HL-I Summary: CTT Transaction Totals M 1 SE Transaction Set Trailer M 1 From Domestic Vendors to CSI 6 of 51
Envelope details ISA Interchange Control Header Level: N/A Loop: Max use: 1 Purpose: To start and identify an interchange of zero or more functional groups and interchange-related control segments. Data Element Summary ISA01 I01 Authorization Information Qualifier M ID 2/2 Description: Code identifying the type of information in the Authorization Information 00 No Authorization Information Present (No Meaningful Information in I02) ISA02 I02 Authorization Information M AN 10/10 Description: Information used for additional identification or authorization of the interchange sender or the data in the Interchange; the type of information is set by the Authorization Information Qualifier (I01) Set to 10 empty spaces ISA03 I03 Security Information Qualifier M ID 2/2 Description: Code identifying the type of information in the Security Information 00 No Security Information Present (No Meaningful Information in I04) ISA04 I04 Security Information M AN 10/10 Description: This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03) Set to 10 empty spaces ISA05 I05 Interchange ID Qualifier M ID 2/2 Description: Code indicating the system/method of code structure used to designate the sender ID element being qualified ISA06 I06 Interchange Sender ID M AN 15/15 Description: Identification code published by the sender for other parties to use as the Sender ID to route data to them. ISA07 I05 Interchange ID Qualifier M ID 2/2 This information is provided during the EDI certification and testing process ISA08 I07 Interchange Receiver ID M AN 15/15 This information is provided during the EDI certification and testing process ISA09 I08 Interchange Date (sender) M DT 6/6 Description: Date of the interchange ISA10 I09 Interchange Time (sender) M TM 4/4 Description: Time of the interchange ISA11 I65 Repetition Separator M 1/1 Description: Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator From Domestic Vendors to CSI 7 of 51
^ ISA12 I11 Interchange Control Version Number M ID 5/5 Description: Code specifying the version number of the interchange control segments 00403 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1999 ISA13 I12 Interchange Control Number M N0 9/9 Description: A control number assigned by the interchange sender ISA14 I13 Acknowledgment Requested M ID 1/1 Description: Code indicating sender's request for an interchange acknowledgment 0 No Acknowledgment Requested ISA15 I14 Usage Indicator M ID 1/1 Description: Code indicating whether data enclosed by this interchange envelope is test, production or information P Production Data T Test Data ISA16 I15 Component Element Separator M 1/1 Description: Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator > From Domestic Vendors to CSI 8 of 51
GS Functional Control Header Level: N/A Loop: Max use: 1 Purpose: To indicate the beginning of a functional group and to provide control information. Data Element Summary: GS01 479 Functional Identifier Code M ID 2/2 Description: Code identifying a group of application related transaction sets SH Ship Notice/Manifest (856) GS02 142 Application Sender's Code M AN 2/15 Description: Code identifying party sending transmission; codes agreed to by trading partners GS03 124 Application Receiver's Code M AN 2/15 Description: Code identifying party receiving transmission; codes agreed to by trading partners This information is provided during the EDI certification and testing process GS04 373 Date M DT 8/8 Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year GS05 337 Time M TM 4/8 Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD =decimal seconds; decimal seconds are expressed as follows: D =tenths (0-9) and DD = hundredths (00-99) The format used is HHMMSSDD GS06 28 Group Control Number M N0 1/9 Description: Assigned number originated and maintained by the sender GS07 455 Responsible Agency Code M ID 1/2 Description: Code identifying the issuer of the standard; this code is used in conjunction with Data Element 480 X Accredited Standards Committee X12 GS08 480 Version / Release / Industry Identifier Code M AN 1/12 Description: Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed 004030 Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1999 From Domestic Vendors to CSI 9 of 51
ST Transaction Set Header Level: Header Loop: Max use: 1 Purpose: To indicate the start of a transaction set and to assign a control number. Data Element Summary ST01 143 Transaction Set Identifier Code M ID 3/3 Description: Code uniquely identifying a Transaction Set 856 Ship Notice/Manifest ST02 329 Transaction Set Control Number M AN 4/9 Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Example: ST*856*0001 From Domestic Vendors to CSI 10 of 51
ASN Header BSN Beginning Segment for Ship Notice Level: Header Loop: Max use: 1 Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set Data Element Summary: BSN01 353 Transaction Set Purpose Code M ID 2/2 Description: Code identifying purpose of transaction set 00 Original 03 Delete 05 Replace All revised ASN s must have 05 otherwise the data will be rejected BSN02 396 Shipment Identification M AN 2/30 Description: A unique control number assigned by the original shipper to identify a specific shipment This value should be unique value across all ASN s sent by your company BSN03 373 Date M DT 8/8 Description: Date expressed as CCYYMMDD ASN created date BSN04 337 Time M TM 4/8 Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) ASN created Time BSN05 1005 Hierarchical Structure Code M ID 4/4 Description: Code indicating the hierarchical application structure of a transaction set that utilizes the HL segment to define the structure of the transaction set 0001 Shipment, Equipment, Order, Packaging, Item Pick and Pack Structure Example: BSN*00*13000667108HK*20100801*0257*0001 From Domestic Vendors to CSI 11 of 51
Shipment Level HL Reference Identification (Shipment) Level: Shipment - Detail Loop: HL-S Usage Mandatory Max use 200000 Loop: Max use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data segments 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 Comments: 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. 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. Charming Shoppes Notes: Only one Shipment level should be present in the ASN transmission (ST to SE) Data Element Summary HL01 628 Hierarchical ID Number M AN 1/12 Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure The value at this level should be 1 HL02 734 Hierarchical Parent ID Number M AN 1/12 Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to. (Note: The HL02 is not required within the first occurrence of the HL segment.) This position is not used at the shipment level HL03 735 Hierarchical Level Code M ID 1/2 Description: Code defining the characteristic of a level in a hierarchical structure S Shipment Examples: HL*1**S From Domestic Vendors to CSI 12 of 51
TD1 Carrier Details (Quantity and Weight) Level: Shipment- Detail Loop: HL-S Usage: Optional Max use: 20 Purpose: To specify the transportation details relative to commodity, weight, and quantity CSI Note: Only one TD1 segment must be sent at the shipment level This segment is preferred to send at the shipment level Data Element Summary TD101 103 Packaging Code M AN 3/5 Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure CTN Carton TD102 80 Lading Quantity M N0 1/7 Description: The number of units in the shipment as described in TD101 TD102 equal to the total number of cartons for the whole shipment TD106 187 Weight Qualifier M ID 1/2 Description: Code defining the type of weight G Gross Weight TD107 81 Weight M R 1/10 Description: Numeric value of weight This is the weight of the shipment TD108 355 Unit or Basis for Measurement Code M ID 2/2 Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. LB Pound TD109 183 Volume M R 1/8 Description: Gross Volume This is the volume of the whole shipment TD110 355 Unit or Basis for Measurement Code M ID 2/2 Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. CF Cubic Feet Example: TD1*CTN*20****G*6.55*LB*20*CF From Domestic Vendors to CSI 13 of 51
TD5 Carrier Details (Routing Sequence/Transit Time) Level: Shipment- Detail Loop: HL-S Max use: 12 Purpose: To specify the carrier and sequence of routing and provide transit time CSI Note: Only one TD5 segment must be sent at the shipment level For vendor shipment going to CSI domestic 3PL, the carrier details must match the shipment going from the vendor location to 3PL location. Data Element Summary TD502 66 Identification code Qualifier M ID 1/2 Description: Code designing the system/method of code structure used for identification code (67) 2 Standard Carrier Alpha Code (SCAC) 91 Assigned by Seller or Seller s Agent 91 code should be used only if the carrier does not have a SCAC code. TD503 will include the carrier name instead of the SCAC code in this case. TD503 67 Identification Code M AN 2/80 Description: Code identifying a party or other code TD504 91 Transportation Method/Type Code M ID 1/2 Description: Free-form description of the routing or requested routing for shipment, or the originating carrier's identity A Air D Parcel Post M Motor S Ocean U Private Parcel X Intermodel TD505 387 Routing O AN 1/35 Description: Free-form description of the routing or requested routing for shipment, or the originating carrier's identity Example: TD5**2*MOLU*M From Domestic Vendors to CSI 14 of 51
TD4 Carrier Details (Special Handling) Level: Shipment- Detail Loop: HL-S Usage: Optional Max use: 5 Purpose: To specify the transportation special handling requirements CSI Note: Only one TD4 segment can be sent at the shipment level Data Element Summary TD401 152 Special Handling Code Qualifier M ID 2/3 Description: Code specifying special transportation handling instructions CC Container, Consolidator Load Full Container Example: TD4*LT CF LN LR TC TF LT Container, Factory Load Full container, not to be opened for consolidation Less Than Container, Consolidator Load Less Than Container, Factory Load Trailer, Consolidator Load Full trailer Trailer, Factory Load Full trailer, not to be opened for consolidation Less than Trailer load (LTL) From Domestic Vendors to CSI 15 of 51
REF Reference Identification Level: Shipment- Detail Loop: HL-S Level: Header Max use: >1 Purpose: To specify identifying information CSI Note: At least two REF segments must be sent for each shipment: One segment with REF01 = 8X. Accuracy is critical to the processing of the shipment and must be sent as expected. A second segment with BM qualifier with Bill of lading number Data Element Summary REF01 128 Reference Identification Qualifier M ID 2/3 Description: Code qualifying the Reference Identification BM Bill of Lading number CN Carrier reference number (Pro Number) AO Appointment Number 8X Transaction type REF02 127 Reference Identification M AN 1/50 Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Possible values for REF02 where REF01 = 8X Code Description ASN for vendors shipping directly to CSI Distribution center PREASN For vendor shipping to 3PL location Examples: REF*BM*123456789 REF*8X*ASN REF*8X*PREASN From Domestic Vendors to CSI 16 of 51
PER Administrative Communications Contact Level: Shipment- Detail Loop: HL-S Level: Header Usage: Optional Max use: 3 Purpose: To identify a person or office to whom administrative communications should be directed Data Element Summary PER01 366 Contact Function Code M ID 2/2 Description: Code identifying the major duty or responsibility of the person or group named DI Delivery Instructions Contract PER02 93 Name O ID 1/60 Description: Free-form name PER03 366 Communication Number Qualifier O ID 2/2 Description: Code identifying the type of communication number EM Electronic Mail PER04 364 Communication Number O AN 1/256 Description: Complete communications number Email address can be communicated in this field Examples: PER*DI*John Smith*EM*John.Smith@aa.com From Domestic Vendors to CSI 17 of 51
DTM Date/Time Reference Level: Shipment-Detail Loop: HL-S Max use: 10 Purpose: To specify pertinent dates and times. Data Element Summary: DTM01 374 Date/Time Qualifier M ID 3/3 Description: Code specifying type of date or time, or both date and time 011 Shipped Date (from vendor location) 017 Estimated Delivery Date (to 3PL location or CSI distribution center) Both dates are required DTM02 373 Date M DT 8/8 Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year Examples: DTM*011*20100412 From Domestic Vendors to CSI 18 of 51
N1 Address Name Level: Shipment- Detail Loop: HL-S-N1 Usage Mandatory Max use 200 Max use: 1 Purpose: To identify a party by type of organization, name, and code Syntax: N103 is required if N104 is present Ship from with SF qualifier and full vendor ship from address is required. Ship to final destination with ST qualifier is required. This is expected to match what was sent in the PO 850. Consolidation point with CS qualifier is required for vendor shipping to 3PL location only. Vendor shipping directly to CSI distribution center are not required to send this address. Data Element Summary: N101 98 Entity Identifier Code M ID 2/3 Description: Code identifying an organizational entity, a physical location, property or an individual SF Ship from address CS 3PL location ST Ship to location final destination Charming Shoppes Location N102 93 Name M AN 1/60 Description: Free-form name N103 66 Identification Code Qualifier O ID 1/2 Description: Code designating the system/method of code structure used for Identification Code (67) 1 D-U-N-S Number, Dun & Bradstreet 9 D-U-N-S+2, D-U-N-S Number with Two Character Suffix 91 Assigned by Seller or Seller s Agent 92 Assigned by Buyer or Buyer s Agent N104 67 Identification Code C AN 2/80 Description: Code identifying a party or other code This is the Consolidator s ID as defined by Charming Shoppes for N101 with CS qualifier Code Value 09956 GALE TRIANGLE 12816 SHOEMAKER AVE, SANTA FE SPRINGS, CA, 90670 09951 SUMMIT TRANSPORTATION 7373 WEST SIDE AVE. NORTH BERGEN, NJ, 07047 09953 ARGIX DIRECT 100 Middlesex Center Blvd, Jamesburg, NJ, 8831 Example: N1*ST*F B DISTRO INC*92*3098 N1*CS*SUMMIT TRANSPORTATION*53*09951 From Domestic Vendors to CSI 19 of 51
N3 Address Information Level: Shipment - detail Loop: HL-S-N1 Usage: Optional Max use: 2 Purpose: To specify the location of the named party Data Element Summary N301 166 Address Information M AN 1/55 Description: Address information N302 166 Address Information O AN 1/55 Description: Address information Example: N3*5304 WEST 74 TH STREET, BLDG 89 N3*MERCHANDISE ACCOUNTS PAYABLE*P.O. BOX 1067 From Domestic Vendors to CSI 20 of 51
N4 Geographic Location Level: Shipment - detail Loop: HL-S-N1 Usage: Optional Max use: >1 Purpose: To specify the geographic place of the named party Data Element Summary N401 19 City Name M AN 2/30 Description: Free-form text for city name N402 156 State or Province Code O ID 2/2 Description: Code (Standard State/Province) as defined by appropriate government agency State field is optional for international addresses that do not have a state only. N403 116 Postal Code O ID 3/15 Description: Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N404 26 Country Code M ID 2/3 Description: Code identifying the country Example: N4*INDIANAPOLIS*IN*46268*US From Domestic Vendors to CSI 21 of 51
Equipment Level HL Reference Identification (Equipment) Level: Equipment -Detail Loop: HL-E Usage Mandatory Max use 200000 Loop: Max use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data segments 4. 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. 5. 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 Comments: 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. 6. 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. Charming Shoppes Notes: At least one equipment level should be present. Trailer information needs to be included at this level For Vendors shipping through Private Parcel, this level is considered as logical grouping of cartons shipped at the same time. Data Element Summary HL01 628 Hierarchical ID Number M AN 1/12 Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure HL02 734 Hierarchical Parent ID Number M AN 1/12 Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to. (Note: The HL02 is not required within the first occurrence of the HL segment.) HL03 735 Hierarchical Level Code M ID 1/2 Description: Code defining the characteristic of a level in a hierarchical structure E Equipment Examples: HL*5*1*E From Domestic Vendors to CSI 22 of 51
TD1 Carrier Details (Quantity and Weight) Level: Equipment- Detail Loop: HL-E Max use: 20 Purpose: To specify the transportation details relative to commodity, weight, and quantity CSI Note: Only one TD1 segment must be sent at the equipment level Data Element Summary TD101 103 Packaging Code M AN 3/5 Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure CTN Carton TD102 80 Lading Quantity M N0 1/7 Description: The number of units in the shipment as described in TD101 TD102 equal to the total number of cartons for the whole equipment. If there is only one equipment level, this value is expected to match the total number of cartons for the whole shipment TD106 187 Weight Qualifier M ID 1/2 Description: Code defining the type of weight G Gross Weight TD107 81 Weight M R 1/10 Description: Numeric value of weight This is the weight of the shipment TD108 355 Unit or Basis for Measurement Code M ID 2/2 Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. LB Pound TD109 183 Volume M R 1/8 Description: Gross Volume This is the volume of the whole shipment TD110 355 Unit or Basis for Measurement Code M ID 2/2 Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. CF Cubic Feet Example: TD1*CTN*20****G*6.55*LB*20*CF From Domestic Vendors to CSI 23 of 51
TD3 Carrier Details (Equipment) Level: Equipment -Detail Loop: HL-E Max use: 1 Purpose: To specify transportation details relating to the equipment used by the carrier. Syntax: If TD302 is present, then TD303 is required. If you do not know the below details when sending the ASN, you can send TD303 = UNKNOWN Data Element Summary TD302 206 Equipment Initial O AN 1/4 Description: Prefix or alphabetic part of an equipment unit s identifying number. TD303 207 Equipment Number C ID 1/10 Description: Sequencing or serial part of an equipment unit s identifying number (pure numeric form for equipment number is preferred). TD309 255 Seal Number O AN 2/15 Description: Unique number on seal used to close a shipment. TD310 24 Equipment Type O ID 4/4 Description: Code identifying type of equipment used for shipment. Code Name 22GP 20 Standard Dry 42GP 40 Standard Dry 45GP 40 High Cube Dry L5GP 45 High Cube Dry 22HR 20 Non Operating Reefer 42HR 40 Non Operating Reefer L5HR 40 High Cube Non Operating Reefer 20CZ 20 Refrigerated container 40CZ 40 Refrigerated container 53TL 53 trailer, dry van 48TL 48 trailer, dry van 28TL 28 trailer (pup) 1323 Box trucks -13 to 23 1853 Reefers 18 to 53 0000 Unspecified Example: TD3**MOFU*0426043******Y567937*42GP From Domestic Vendors to CSI 24 of 51
Order Level HL Reference Identification (Order Level) Level: Order-Detail Loop: HL-O Usage Mandatory Max use 200000 Loop: Max use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data segments 7. 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. 8. 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 Comments: 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. 9. 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. Charming Shoppes Notes: At least one order level is required for each equipment level. Data Element Summary HL01 628 Hierarchical ID Number M AN 1/12 Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure HL02 734 Hierarchical Parent ID Number M AN 1/12 Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to. (Note: The HL02 is not required within the first occurrence of the HL segment.) HL03 735 Hierarchical Level Code M ID 1/2 Description: Code defining the characteristic of a level in a hierarchical structure O Order Examples: HL*3*2*O From Domestic Vendors to CSI 25 of 51
PRF Purchase Order Reference Level: Order-Detail Loop: HL-O Max use: 1 Purpose: To provide reference to a specific purchase order Data Element Summary PRF01 324 Purchase Order Number M AN 6/22 Description: Identifying number for Purchase Order assigned by the purchaser. The value in this field should be exactly the same as the BEG03 field in the EDI PO 850 document Examples: PRF*3022440 From Domestic Vendors to CSI 26 of 51
TD1 Carrier Details (Quantity and Weight) Level: Order-Detail Loop: HL-O Usage: Optional Max use: 20 Purpose: To specify the transportation details relative to commodity, weight, and quantity Data Element Summary TD101 103 Packaging Code M AN 3/5 Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure CTN Carton TD102 80 Lading Quantity M N0 1/7 Description: The number of units in the shipment as described in TD101 TD102 equal to the total number of cartons for the specified purchase order in the PRF segment. TD106 187 Weight Qualifier M ID 1/2 Description: Code defining the type of weight G Gross Weight TD107 81 Weight M R 1/10 Description: Numeric value of weight This is the weight of the shipment TD108 355 Unit or Basis for Measurement Code M ID 2/2 Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. LB Pound TD109 183 Volume M R 1/8 Description: Gross Volume This is the volume of the whole shipment TD110 355 Unit or Basis for Measurement Code M ID 2/2 Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. CF Cubic Feet Example: TD1*CTN*20****G*6.55*LB*20*CF From Domestic Vendors to CSI 27 of 51
TD5 Carrier Details (Routing Sequence/Transit Time) Level: Order-Detail Loop: HL-O Max use: 1 Purpose: To specify the carrier and sequence of routing and provide transit time Data Element Summary TD506 368 Order Status Code M ID 2/2 Description: Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction Code CC CM PR SS Name Shipment Complete (on date) Shipment Complete with Additional Quantity Partial Shipment Split Shipment Example: TD5******CC From Domestic Vendors to CSI 28 of 51
REF Reference Identification Level: Order-Detail Loop: HL-O Max use: >1 Purpose: To specify identifying information Data Element Summary REF01 128 Reference Identification Qualifier M ID 2/3 Description: Code qualifying the Reference Identification 19 Chain Code RV Receiving number BN Booking Number Charming Shoppes Notes: REF segment with 19 qualifier must be sent in all ASN s. Chain code should be the same value as the REF02 with REF01 = 19 in the EDI PO 850 document REF segment with RV or BN qualifiers are not required for vendor shipping directly to CSI distribution centers. REF02 127 Reference Identification M AN 1/50 Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier Examples: REF*19*01 From Domestic Vendors to CSI 29 of 51
DTM Date/Time Reference Level: Order-Detail Loop: HL-O Usage: Optional Max use: 10 Purpose: To specify pertinent dates and times. Charming Shoppes Notes: DTM segment with 922 qualifier is required for vendor shipping to 3PL only. Vendor shipping directly to CSI distribution centers are not required to send this segment. Data Element Summary: DTM01 374 Date/Time Qualifier M D 3/3 Description: Code specifying type of date or time, or both date and time 922 Receipt date at 3PL location DTM02 373 Date M DT 8/8 Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year Examples: DTM*922*20100412 From Domestic Vendors to CSI 30 of 51
N1 Address Name Level: Order-Detail Level: Header Loop: HL-O-N1 Usage Optional Max use 200 Max use: 1 Purpose: To identify a party by type of organization, name, and code Syntax: If N104 is present, N103 is required CSI Note: Corresponding N3 and N4 segments are optional Data Element Summary: N101 98 Entity Identifier Code M ID 2/3 Description: Code identifying an organizational entity, a physical location, property or an individual BY Buying Party (Chain address) N102 93 Name M AN 1/60 Description: Free-form name N103 66 Identification Code Qualifier O ID 1/2 Description: Code designating the system/method of code structure used for Identification Code (67) 92 Assigned by Buyer or Buyer s Agent N104 67 Identification Code C AN 2/80 Description: Code identifying a party or other code Example: N1*BY*LANE BRYANT PURCHASING CORP.*92*07 From Domestic Vendors to CSI 31 of 51
N3 Address Information Level: Order-Detail Loop: HL-O-N1 Usage: Optional Max use: 2 Purpose: To specify the location of the named party Data Element Summary N301 166 Address Information M AN 1/55 Description: Address information N302 166 Address Information O AN 1/55 Description: Address information Example: N3*5304 WEST 74 TH STREET, BLDG 89 N3*MERCHANDISE ACCOUNTS PAYABLE*P.O. BOX 1067 From Domestic Vendors to CSI 32 of 51
N4 Geographic Location Level: Order-Detail Loop: HL-O-N1 Usage: Optional Max use: >1 Purpose: To specify the geographic place of the named party Data Element Summary N401 19 City Name O AN 2/30 Description: Free-form text for city name N402 156 State or Province Code O ID 2/2 Description: Code (Standard State/Province) as defined by appropriate government agency State field is optional for international addresses that do not have a state only. N403 116 Postal Code O ID 3/15 Description: Code defining international postal zone code excluding punctuation and blanks (zip code for United States) N404 26 Country Code M ID 2/3 Description: Code identifying the country Example: N4*INDIANAPOLIS*IN*46268*US From Domestic Vendors to CSI 33 of 51
Carton Level HL Reference Identification (Pack: Carton Level) Level: Pack-detail Loop: HL-P Usage Mandatory Max use 200000 Loop: Max use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data segments 10. 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. 11. 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 Comments: 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. 12. 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. Data Element Summary HL01 628 Hierarchical ID Number M AN 1/12 Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure HL02 734 Hierarchical Parent ID Number M AN 1/12 Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to. (Note: The HL02 is not required within the first occurrence of the HL segment.) HL03 735 Hierarchical Level Code M ID 1/2 Description: Code defining the characteristic of a level in a hierarchical structure P Pack Examples: HL*5*2*P From Domestic Vendors to CSI 34 of 51
PO4 Item Physical details Level: Pack-detail Loop: HL-P Max use: 1 Purpose: To specify the physical qualities, packaging, weights, and dimensions relating to the item Data Element Summary PO406 384 Gross Weight per Pack M R 1/9 Description: Numerical value of gross weight per pack This is the weight of the carton PO407 355 Unit or Basis for Measurement Code M ID 2/2 Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. LB Pound PO408 385 Gross Volume per Pack M R 1/8 Description: Gross Volume PO409 355 Unit or Basis for Measurement Code M ID 2/2 Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. CF Cubic Feet PO410 82 Length M R 1/8 Description: Largest horizontal dimension of an object measured when the object is in the upright position PO411 189 Width M R 1/8 Description: Shorter measure of the two horizontal dimensions measured when the object is in the upright position PO412 65 Height M R 1/8 Description: Vertical dimension of an object measured when the object is in the upright position PO413 355 Unit or Basis for Measurement Code M ID 2/2 Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. E8 Inches Examples: PO4******100*LB*10*CF*50*20*10*E8 From Domestic Vendors to CSI 35 of 51
PKG Marking, Packaging, Loading Level: Pack-detail Loop: HL-P Usage: Optional Max use: 1 Purpose: To describe marking, packaging, loading, unloading requirements CSI Note: This segment is required for ODD cartons. ODD Carton processing is managed through an intensive manual process. All vendors are required NOT to send ODD cartons unless approved in writing by CSI Supply Chain Department Data Element Summary: PKG01 349 Item Description Type M ID 1/1 Description: S Structured PKG02 753 Packaging Characteristic Code M ID 1/5 Description: Code Name PN SMK OPI Promotional Marking Special Marking Optional Procedure Indicator Charming Shoppes Notes: SMK qualifier is used to flag a carton as ODD OPI qualifier is used to flag a carton as inspected PKG03 559 Agency Qualifier Code M ID 2/2 Description: VI Voluntary Inter-Industry Commerce Standard (VICS) EDI PKG04 754 Packaging Description Code M AN 1/7 Description: Free Form description Examples: PKG*S*SMK*VI*Odd From Domestic Vendors to CSI 36 of 51
TSD Trailer Shipment Details Level: Pack-detail Loop: HL-P Usage: Optional Max use: 1 Purpose: To specify details of shipments on a trailer Data Element Summary: TSD01 350 Assigned Identification O AN 1/20 Description: Alphanumeric characters assigned for differentiation within a transaction set. Indicates the loading sequence TSD02 219 Position O AN 1/3 Description: Relative position of shipment in car, trailer, or container (mutually defined) 1 First quarter of the trailer/container 2 Second quarter of the trailer/container 3 Third quarter of the trailer/container 4 Fourth quarter of the trailer/container Examples: TSD**4 From Domestic Vendors to CSI 37 of 51
MAN Marks and Numbers Level: Pack-detail Loop: HL-P Max use: >1 Purpose: To specify basic item identification data Data Element Summary: MAN01 88 Marks and Numbers Qualifier M ID 1/2 Description: Code specifying the application or source of Marks and Numbers CP Carrier-Assigned Package ID Number GM SSCC-18 and Application identifier This is a twenty-character UCC/EAN-128 Serial Container Code (SSCC-18) that includes the two digit application identifier. The symbology code and the modulo 103 check digit are not included. MAN02 87 Marks and Numbers M AN 1/48 Description: Marks and Numbers used to identify a shipment or part of a shipment Charming Shoppes Notes: One MAN with GM qualifier is always required. A second MAN with CP qualifier can be sent with the Carrier-Assigned Package ID Number (Tracking#) Examples: MAN*GM*00000112230000111000 MAN*CP*0123456789 From Domestic Vendors to CSI 38 of 51
Item Level HL Reference Identification (Item Level) Level: Item-Detail Loop: HL-I Usage Mandatory Max use 200000 Loop: Max use: 1 Purpose: To identify dependencies among and the content of hierarchically related groups of data segments 13. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment data, and packaging data to line-item data. The HL segment defines a top-down/left-right ordered structure. 14. 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 Comments: 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. 15. 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. This level is required for all shipment. Data Element Summary HL01 628 Hierarchical ID Number M AN 1/12 Description: A unique number assigned by the sender to identify a particular data segment in a hierarchical structure HL02 734 Hierarchical Parent ID Number M AN 1/12 Description: Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to. (Note: The HL02 is not required within the first occurrence of the HL segment.) HL03 735 Hierarchical Level Code M ID 1/3 Description: Code defining the characteristic of a level in a hierarchical structure I Item Examples: HL*5*2*I From Domestic Vendors to CSI 39 of 51
LIN Item Identification Level: Item-Detail Loop: HL-I Max use: >1 Purpose: To specify basic item identification data Data Element Summary: LIN02 235 Product / Service ID Qualifier M ID 2/2 IN Buyer s item number (MSN#) LIN03 234 Product / Service ID M AN 1/48 MSN# (Charming Shoppes Merchandise Serial Number) Charming Shoppes Notes: The value should be the same as PO107 in the EDI PO 850 document Example: LIN**IN*200744458 From Domestic Vendors to CSI 40 of 51
SN1 Item Detail (Shipment) Level: Item-Detail Loop HL-I Max use: >1 Purpose: To specify line-item detail relative to shipment Data Element Summary: SN102 382 Number of Units Shipped M R 1/10 Description: SN102 is the number of MSN s per carton. SN103 355 Unit or Basis for Measurement Code M ID 2/2 Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. AS for assortment Examples: SN1**50*AS From Domestic Vendors to CSI 41 of 51
SLN Subline Item Details Level: Item-Detail Loop: HL-I Max use: >1 Purpose: To specify product sub-line detail item data Syntax: If SLN28 is present, SLN27 is required Data Element Summary: SLN01 350 Assign Identification M AN 1/11 Description: SLN01 is a unique line identifier sent in the SLN01of the EDI PO 850 document SLN03 662 Configuration Code M ID 1/1 Description: Code Name A Add D Delete I Included D and A flags is sent for ODD cartons only where the assortment sub-items changed from what was originally sent in the EDI PO 850 document. SLN04 380 Quantity M R 1/15 Description: SLN04 is the number of pieces per assortment. This is expected to match the SLN04 value sent in the EDI PO 850 document SLN05 355 Unit or Basis for Measurement Code M ID 2/2 Description: Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken. EA Each This is expected to match the SLN05 value sent in the EDI PO 850 document SLN09 235 Product/Service ID Qualifier M ID 2/2 IN Buyer s Item Number UP UPC# This is expected to match the SLN09 value sent in the EDI PO 850 document SLN10 234 Product/Service ID M AN 1/48 This is expected to match the SLN10 value sent in the EDI PO 850 document SLN11 235 Product/Service ID Qualifier M ID 2/2 IT Buyers Style Number This is expected to match the SLN11 value sent in the EDI PO 850 document From Domestic Vendors to CSI 42 of 51
SLN12 234 Product/Service ID M AN 1/48 Buyers Style Number This is expected to match the SLN12 value sent in the EDI PO 850 document SLN13 235 Product/Service ID Qualifier M ID 2/2 BO Buyers Color This is expected to match the SLN13 value sent in the EDI PO 850 document SLN14 234 Product/Service ID M AN 1/48 Buyers Color This is expected to match the SLN14 value sent in the EDI PO 850 document SLN15 235 Product/Service ID Qualifier M ID 2/2 IZ Buyers Size Code This is expected to match the SLN15 value sent in the EDI PO 850 document SLN16 234 Product/Service ID M AN 1/48 Buyers Size Code This is expected to match the SLN16 value sent in the EDI PO 850 document SLN17 235 Product/Service ID Qualifier M ID 2/2 SK Stock Keeping Unit at Style / Color level This is expected to match the SLN19 value sent in the EDI PO 850 document SLN18 234 Product/Service ID M AN 1/48 Stock Keeping Unit This is expected to match the SLN20 value sent in the EDI PO 850 document SLN19 235 Product/Service ID Qualifier M ID 2/2 PL Purchase order line# This is expected to match the SLN17 value sent in the EDI PO 850 document SLN20 234 Product/Service ID M AN 1/48 Purchase order line# This is expected to match the SLN18 value sent in the EDI PO 850 document SLN21 235 Product/Service ID Qualifier M ID 2/2 DV Department This is expected to match the SLN21 value sent in the EDI PO 850 document SLN22 234 Product/Service ID M AN 1/48 Department This is expected to match the SLN12 value sent in the EDI PO 850 document From Domestic Vendors to CSI 43 of 51
SLN23 235 Product/Service ID Qualifier O ID 2/2 GE Size description SLN24 234 Product/Service ID C AN 1/48 This is expected to match PID05 sent in the EDI PO 850 for the PID segment under the SLN loop where PID02 = 91 SLN25 235 Product/Service ID Qualifier O ID 2/2 MF Manufacturer (1) SLN26 234 Product/Service ID C AN 1/48 Manufacturer s ID Number (MID) This is expected to match N406 sent in the EDI PO 850 header where N101 = SU SLN27 235 Product/Service ID Qualifier O ID 2/2 MF Manufacturer (2)) SLN27 and SLN28 fields are sent only when there is more one manufacturer for the specified item SLN28 234 Product/Service ID C AN 1/48 Manufacturer s ID Number (MID) Example: SLN*0100380**I*6*EA****IN*000094900035*IT*600000*BO*DV*IZ*0380*SK*2270759*PL*010*DV*942*GE*14/16*MF*MID12345 From Domestic Vendors to CSI 44 of 51
Summary detail CTT Transaction Totals Level: Summary Loop: Max use: 1 Purpose: To transmit a hash total for a specific element in the transaction set Data Element Summary CTT01 354 Number of Line Items M N0 1/6 Description: Total number of line items in the transaction set Total number of HL segments in the transaction set Example: CTT*4 From Domestic Vendors to CSI 45 of 51
Enveloping summary detail SE Transaction Set Trailer Level: Header Loop: 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) Data Element Summary: SE01 96 Number of Included Segments M N0 1/10 Description: Total number of segments included in a transaction set including ST and SE segments SE02 329 Transaction Set Control Number M AN 4/9 Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Examples: SE*149*000000001 From Domestic Vendors to CSI 46 of 51
GE Functional Group Trailer Level: Header Loop: Max use: 1 Purpose: To indicate the end of a functional group and to provide control information Semantics: The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06 Data Element Summary: GE01 97 Number of Transaction Sets Included M N0 1/6 Description: Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element GE02 28 Group Control Number M N0 1/9 Description: Assigned number originated and maintained by the sender Example: GE*1*90902339 From Domestic Vendors to CSI 47 of 51