X12 856 Ship Notice/Manifest
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 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.
The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.
- ~ Segment
- * Element
- > Component
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
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)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
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)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
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
- >
- Component Element Separator
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related transaction sets
- SH
- Ship Notice/Manifest (856)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
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)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
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
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 856
- Ship Notice/Manifest
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Ship Notice
To transmit identifying numbers, dates, and other basic data relating to the transaction set
Sample EDI:
BSN0099999999200701011022*0002~
Code identifying purpose of transaction set
- 00
- Original
A unique control number assigned by the original shipper to identify a specific shipment
Date expressed as CCYYMMDD
- BSN03 is the date the shipment transaction set is created.
Creation/Transaction Date
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)
- BSN04 is the time the shipment transaction set is created.
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, Order, Packaging, Item
- 0002
- Shipment, Order, Item, Packaging
Estimated Delivery
To specify pertinent dates and times
Mandatory for For Warehouse Shipments
Sample EDI:
DTM01720051105~
Shipped
To specify pertinent dates and times
Sample EDI:
DTM01120051101~
Detail
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- S
- Shipment
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
The TD1 segment is Mandatory for all direct to warehouse shipments.
Scenario #1: Product is shipped to warehouse on Pallets.
*****One TD101 with PLTxx qualifier and TD102 with total number of pallets in the shipment.
*****One TD101 with CTNxx qualifier and TD102 with total number of cartons/cases in the shipment.
Scenario #2: Product is shipped to warehouse in cartons only (No Pallets but in a Master Carton).
*****One TD101 with PLTxx qualifier and TD102 with total number of Master Cartons in the shipment.
*****One TD101 with CTNxx qualifier and TD102 with total number of cartons/cases in the shipment.
**If the shipment is a Return that is shipped directly to the consumer/End-User, the TD1 segment is not required.
========================
Non-Warehouse Shipments:
This segment is not Mandatory for Non-Warehouse Shipments.
Sample EDI:
For TL, LTL, Small Parcel shipments (i.e. FedEx, DHL, UPS, etc.):
TD1PLT9410*G8000*LB~
TD1CTN25250***G7750*LB~
Code identifying the type of packaging; Part 1: Packaging Form, Part 2: Packaging Material; if the Data Element is used, then Part 1 is always required
Warehouse Shipments:
The TD101 is a composite element so the "PLT" and "94" will be sent as “PLT94”.
The TD101 is a composite element so the "CTN" and "25" will be sent as “CTN25”.
- CTN
- Carton
- PLT
- Pallet
- 25
- Corrugated or Solid
- 76
- Paper
- 79
- Plastic
- 91
- Stainless Steel
- 94
- Wood
Number of units (pieces) of the lading commodity
Numeric value of weight
You will send the total gross weight for the appropriate TD1 segment. There are two TD1 segments required if you are shipping on a pallet or in a Master Carton. The PLT will be all cartons on the pallets + the pallet/Master Carton weight.
The CTN iteration of the TD1 will contain the total gross weight for all cartons in the shipment (does not include the pallets).
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- LB
- Pound
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
This segment is not Mandatory for Non-Warehouse Shipments.
Sample EDI:
TD5B2XXXXM*Shipper Name~
Code describing the relationship of a carrier to a specific shipment movement
- B
- Origin/Delivery Carrier (Any Mode)
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
- 2
- Standard Carrier Alpha Code (SCAC)
Code identifying a party or other code
The SCAC must be a valid SCAC code for the Transportation industry.
Code specifying the method or type of transportation for the shipment
- M
- Motor (Common Carrier)
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier
Only one TD3 per EDI 856 transaction. Each TL (Truckload) or LTL (Less than Truckload) trailer must have an individual
**** The TD3 segment is Required for TL and LTL shipments. The TD3 is Optional for Small Parcel shipments.
Non-Warehouse Shipments:
This segment is not Mandatory for Non-Warehouse Shipments.
Sample EDI:
For TL or LTL shipments:
TD3TLXXX*1234567890~
Code identifying type of equipment used for shipment
- TL
- Trailer (not otherwise specified)
Prefix or alphabetic part of an equipment unit's identifying number
The AT&T Mobility 3 position Alpha Vendor Code will be provided to the Vendor by the Account Representative. The Vendor Code will be used to ensure a unique Truck Number is used in the Warehouse Management System.
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred)
This is the Truck Number that is used to uniquely identify the truck.
Buyer Identification
To specify identifying information
The REF*YD segment is Mandatory.
The YD qualifier is a reference field used for Wireless and Wireline Shipments.
Valid examples for the REFYD:
REFYDSERIALIZED~
REFYDNON-SERIALIZED~
REFYD*MIXED~
MIXED shipment should contain SERIALIZED and NON-SERIALIZED items at the Item level.
SERIALIZED items are items that require the HL*K loop, which communicates all serialized infromation, such as IMEI, Unlock Code, etc.
REFYDWIRELINE~
WIRELINE items require the HLK loop, which communicates all serialized infromation, such as Serial Number, MAC Address, etc.
Only one REF*YD segment is expected at the Shipment level.
Non-Warehouse Orders:
REFYDNON-WAREHOUSE~
Code qualifying the Reference Identification
- YD
- Buyer Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Supplier Number - Identifier for the supplier. Assigned by AT&T Mobility. Contact the AT&T Mobility Buyer or Account Representative to obtain the correct Supplier Number.
References
To specify identifying information
REFBM segment is Mandatory.
REFCN segment is Optional.
REF*ZA segment is Mandatory.
Non-Warehouse Shipments:
REFBM segment is Optional.
REFCN segment is Optional.
REF*ZA segment is Optional.
Sample EDI:
Warehouse Orders:
REFBM123456789~
REFCN1234567890~
REFZASUPPLIER NUMBER~
Code qualifying the Reference Identification
- BM
- Bill of Lading Number
- CN
- Carrier's Reference Number (PRO/Invoice)
- ZA
- Supplier
Supplier Number - Identifier for the supplier. Assigned by AT&T Mobility. Contact the AT&T Mobility Buyer or Account Representative to obtain the correct Supplier Number.
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Name
To identify a party by type of organization, name, and code
Warehouse Shipments:
N1STMEMPHIS DISTRIBUTION CENTER9210107048~
Non-Warehouse Shipments:
N1STNON-WAREHOUSE SHIPMENT9299999999~
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
Free-form name
- FORT WORTH DISTRIBUTION CENTER
for Warehouse Shipments
- MEMPHIS DISTRIBUTION CENTER
for Warehouse Shipments
- NON-WAREHOUSE SHIPMENT
for Non-Warehouse Shipments
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party.
- 10107048
- Memphis Distribution Center
for Warehouse Shipments
- 10110146
- Ft. Worth Distribution Center
for Warehouse Shipments
- 99999999
- Non-Warehouse Shipments
Address Information
To specify the location of the named party
Warehouse Shipments:
N3Address Line 1Address Line 2~
N3Address Line 3Address Line 4~
Non-Warehouse Shipments:
This segment is not Mandatory for Non-Warehouse Shipments.
Geographic Location
To specify the geographic place of the named party
Warehouse Shipments:
N4ANY CITYGA00000US~
Non-Warehouse Shipments:
This segment is not Mandatory for Non-Warehouse Shipments.
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- O
- Order
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
**** The data values for the PRF segment are available on the printed Purchase Order.
Non-Warehouse Shipments:
This segment is not Mandatory for Non-Warehouse Shipments. However, if you have this information, please include it in this segment.
Sample EDI:
Warehouse Shipments:
Stand-Alone Purchase Order
PRF7035632020051017~
Release Purchase Order (as part of a Blanket Purchase Order)
PRF7035632120051017~
Purchase Order Change applied to Stand-Alone
PRF70356320120051017~
Purchase Order Change applied to a Release Purchase Order
PRF70356321120051017~
**** The PRF02 and PRF03 are derived from the printed Purchase Order from AT&T Mobility. The values in the above examples may not be typical of your particular scenario.
Identifying number for Purchase Order assigned by the orderer/purchaser
This is the AT&T Mobility PO Number.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
If the Purchase Order was a Release Purchase Order for a Blanket PO from AT&T Mobility, include the Release Number; otherwise, please default this value to '0'.
Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set
If the Purchase Order was changed by the AT&T Mobility Buyer prior to shipment, the Purchase Order Change Order Sequence Number is Required.
Date expressed as CCYYMMDD
- PRF04 is the date assigned by the purchaser to purchase order.
Reference Identification
To specify identifying information
Mandatory for Warehouse Shipments
Warehouse Shipments:
REFVN987654321~
Non-Warehouse Shipments:
This segment is not Mandatory for Non-Warehouse Shipments. However, if you have this information, please include it in this segment.
Code qualifying the Reference Identification
- VN
- Vendor Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Sample EDI:
Warehouse and Non-Warehouse Orders:
For Serialized Items
HL54I1~
For Non-Serialized Items
HL54I0~
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- I
- Item
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
Warehouse Orders:
LIN0001CBXXX.12345MNMODEL NUMBERUIUPC CODESK*12345~
Non-Warehouse Orders:
LIN0001CBXXX.12345MN*MODEL NUMBER~
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
The LIN01 must be the Line Number from the Original Purchase Order created by AT&T Mobility. The LIN01 must be expressed in 4 numeric characters, with leading zeros.
examples:
Line Item 01 will be 0001.
Line Item 10 will be 0010.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- CB
- Buyer's Catalog Number
Identifying number for a product or service
The format of the SKU must match the value sent in the original Purchase Order. Typically, the Buyer's Catalog Number is formatted as XXX.12345 where 'XXX.' is the prefix to the numeric AT&T Mobility SKU.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MN
- Model Number
Identifying number for a product or service
Model: This is the model of the device (e.g. 'V70G', '5190', 'Treo 650')
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UI
- U.P.C. Consumer Package Code (1-5-5)
Identifying number for a product or service
UPC Code is not Mandatory. However, if you have this information, please include it in this element.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
The AT&T Mobility SKU is required on ALL Warehouse Orders, but not on Non-Warehouse Orders.
The AT&T Mobility SKU is sent in the Purchase Order. The value in the LIN09 element should be the numeric portion of the LIN03 Buyers Catalog Number; do not send the 'XXX.' prefix in the LIN09.
Item Detail (Shipment)
To specify line-item detail relative to shipment
Sample EDI:
Warehouse Orders:
SN100012000*EA~
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
Must match the Line Number from the LIN segment (LIN01) exactly
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Serialized: Total number of eaches in the carton/container. This quantity will be the number of Serialized eaches in the carton/container. The SN102 must match the number of HL Kit level SLN segment iterations.
Non-Serialized: Total number of eaches in the carton/container. This quantity will be the number of Non-Serialized eaches in the carton/container.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- SN103 defines the unit of measurement for both SN102 and SN104.
- EA
- Each
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
For SIM cards, the box inside the outer carton contains 4 packs of 250 each. The PO401 would be 1000 and the PO414 should be 1.
PO41000***********1~
For handsets, no Inner Pack is used. You should send just the PO401.
Handset Example:
PO410~
Non-Warehouse Orders:
This segment is not Mandatory for Non-Warehouse Orders.
Sample EDI:
PO41000***********1~ (SIM cards)
or
PO41~ (handsets)
Buyer Identification
To specify identifying information
The REF*YD segment is Mandatory. The YD qualifier references whether the line item is SERIALIZED or NON-SERIALIZED.
SERIALIZED items are items that require the HL*K loop, which communicates all serialized infromation, such as IMEI, Unlock Code, Serial Number, MAC Address, etc.
Only one REF*YD segment is expected at the Item level per Item.
Valid examples for the REFYD:
REFYDSERIALIZED~
REFYD*NON-SERIALIZED~
Code qualifying the Reference Identification
- YD
- Buyer Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- NON-SERIALIZED
- SERIALIZED
Shipment Number
To specify identifying information
The Trading Partner must send the ShipNum (Shipment Number) value from the original Purchase Order created by AT&T Mobility.
** Contact your AT&T Mobility Buyer if you do not receive the ShipNum on the paper/PDF Purchase Order.
Non-Warehouse Orders:
This segment is not Mandatory for Non-Warehouse Orders.
The REF02 (ZZ qualifier) must be expressed in 4 numeric characters, with leading zeros.
examples:
ShipNum 01 will be 0001.
ShipNum 10 will be 0010.
Sample EDI:
Warehouse Orders:
REFZZSHIPNUM~
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The HL Kit loop is Required if the product is Serialized.
The HL Kit loop is NOT Required if the product is Non-Serialized product (i.e. Accessories)
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- K
- Kit
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Subline Item Detail
To specify product subline detail item data
Sample EDI:
For WIRELESS Equipment:
with ICC-ID:
SLN00011I1EA********IC12345678901234567890IS356862003671263TW65225359*PJ20051101*ZZR47R~
without ICC-ID:
SLN00011I1EA***IS356862003671263*TW65225359*PJ20051101*ZZR47R~
without Unlock Code:
SLN00011I1EA***IS356862003671263*TWUNLOCK_NOT_SENT*PJ20051101*ZZR472R~
For WIRELINE Equipment:
with Serial Number & MAC Address:
SLN00011I1EASN123456789012*MA210987654321*PJ20051101ZZR472_G_08.18.40R~
without Serial Number:
SLN00011I1EA*****SNSERIAL_NOT_SENT**MA210987654321*PJ20051101ZZ*R472_G_08.18.40R~
without MAC Address:
SLN00011I1EA*SN123456789012**MAMAC_NOT_SENTPJ20051101ZZR472_G_08.18.40R~
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Must match the Line Number from the LIN segment (LIN01) exactly.
Alphanumeric characters assigned for differentiation within a transaction set
- SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.
Unique Counter for each SLN iteration.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
Numeric value of quantity
Usually a quantity of 1.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SN
- Serial Number
Identifying number for a product or service
The SLN11 and SLN12 are mandatory for all WIRELINE equipment.
** Serial Number is mandatory for all wireline equipment. There will only be one Serial Number per piece of wireline equipment. If Serial Number is not being sent in the SLN segment of the EDI 856 based on a prior legal agreement with AT&T, please include the following hardcoded text within the SLN12 element: SERIAL_NOT_SENT.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IC
- ICC-ID (SIM Serial Number)
Identifying number for a product or service
The SLN14 contains the ICC-ID (SIM Serial Number).
** ICC-ID (SIM Cards Serial Number) is mandatory for all WIRELESS equipment that is pre-packaged with SIM Cards. There will only be one ICC-ID per handset/data device.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IS
- International Standard Serial Number (ISSN)
IMEI Code
Identifying number for a product or service
The SLN16 contains the IMEI number. The SLN15 and SLN16 are mandatory for all WIRELESS equipment.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- TW
- Program Code
Subsidy Unlock Code
Identifying number for a product or service
The SLN17 and SLN18 are mandatory for all WIRELESS equipment.
** Subsidy Unlock Codes (SIMLOCK3 or SIMLOCK4) are mandatory for all wireless equipment. There will only be one Subsidy Unlock Code per handset/data device. If Subsidy Unlock Code is not being sent in the SLN segment of the EDI 856 based on a prior legal agreement with AT&T, please include the following hardcoded text within the SLN18 element: UNLOCK_NOT_SENT.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MA
- Media Access Control (MAC) Address
- OI
- OEM Identification Code
Identifying number for a product or service
The SLN19 and SLN20 are mandatory for all WIRELINE equipment.
** Media Access Control (MAC) Address is mandatory for all wireline equipment. There will only be one Media Access Control (MAC) Address per piece of wireline equipment. If Media Access Control (MAC) Address is not being sent in the SLN segment of the EDI 856 based on a prior legal agreement with AT&T, please include the following hardcoded text within the SLN20 element: MAC_NOT_SENT.
The SLN19 and SLN20 are mandatory for all FEMTOCELL equipment.
** OEM Identification Code is mandatory for all FemtoCell equipment. There will only be one OEM Identification Code per piece of FemtoCell equipment.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PJ
- Product Date Code (A code indicating the period during which a product was manufactured.)
Manufacture Date
Identifying number for a product or service
The SLN21 and SLN22 are mandatory for all WIRELESS equipment.
Format Date as CCYYMMDD. If the Manufacture Date is not formatted correctly, the EDI856 transaction will be rejected.
Manufacture Date - This is the date which the device was manufactured.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ZZ
- Software/Firmware Version
Identifying number for a product or service
The SLN23 and SLN24 are mandatory for all WIRELESS equipment.
Firmware Version - Build or version of firmware on the phone.
Vendor Firmware Version Number must be sent for all handset/data card devices.
AT&T Mobility is expecting the Operating System (OS) Software/Firmware version in SLN24.
For handsets/data devices that also utilize a Flex Version, please use the SLN25 and SLN26.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- RN
- Flex Version
Identifying number for a product or service
Flex Version - Depending on the device, a Flex Version will identify the build of the software. This field will contain the appropriate information of this build. This should be blank if it is not applicable to a device.
For handsets/data devices that also utilize a Flex Version, please use the SLN25 and SLN26.
The HL Pack iteration is Mandatory for all Warehouse shipments
Non-Warehouse Shipments:
This segment is not Mandatory for Non-Warehouse Shipments.
Sample EDI:
Warehouse Orders:
For LTL, TL, or Small Parcel Shipments where product is in a Carton
HL43P1~
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- P
- Pack
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
If the product has a UCC-128 barcode label applied, the MAN segment could contain the following:
MANGM00123456789123456789~
**** Only 1 MAN segment is required at the Pack level.
**** The Carton ID number is required in the MAN segment.
Sample EDI:
MANAny Qualifier123456789123456~
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
The MAN02 should contain a valid identification number for the Carton. The AT&T Mobility Routing Guide should be referenced.
Sample EDI:
Warehouse and Non-Warehouse Orders:
For Serialized Items
HL54I1~
For Non-Serialized Items
HL54I0~
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- I
- Item
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
Warehouse Orders:
LIN0001CBXXX.12345MNMODEL NUMBERUIUPC CODESK*12345~
Non-Warehouse Orders:
LIN0001CBXXX.12345MN*MODEL NUMBER~
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
The LIN01 must be the Line Number from the Original Purchase Order created by AT&T Mobility. The LIN01 must be expressed in 4 numeric characters, with leading zeros.
examples:
Line Item 01 will be 0001.
Line Item 10 will be 0010.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- CB
- Buyer's Catalog Number
Identifying number for a product or service
The format of the SKU must match the value sent in the original Purchase Order. Typically, the Buyer's Catalog Number is formatted as XXX.12345 where 'XXX.' is the prefix to the numeric AT&T Mobility SKU.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MN
- Model Number
Identifying number for a product or service
Model: This is the model of the device (e.g. 'V70G', '5190', 'Treo 650')
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UI
- U.P.C. Consumer Package Code (1-5-5)
Identifying number for a product or service
UPC Code is not Mandatory. However, if you have this information, please include it in this element.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
The AT&T Mobility SKU is required on ALL Warehouse Orders, but not on Non-Warehouse Orders.
The AT&T Mobility SKU is sent in the Purchase Order. The value in the LIN09 element should be the numeric portion of the LIN03 Buyers Catalog Number; do not send the 'XXX.' prefix in the LIN09.
Item Detail (Shipment)
To specify line-item detail relative to shipment
Sample EDI:
Warehouse Orders:
SN100012000*EA~
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
Must match the Line Number from the LIN segment (LIN01) exactly
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Serialized: Total number of eaches in the carton/container. This quantity will be the number of Serialized eaches in the carton/container. The SN102 must match the number of HL Kit level SLN segment iterations.
Non-Serialized: Total number of eaches in the carton/container. This quantity will be the number of Non-Serialized eaches in the carton/container.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- SN103 defines the unit of measurement for both SN102 and SN104.
- EA
- Each
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
For SIM cards, the box inside the outer carton contains 4 packs of 250 each. The PO401 would be 1000 and the PO414 should be 1.
PO41000***********1~
For handsets, no Inner Pack is used. You should send just the PO401.
Handset Example:
PO410~
Non-Warehouse Orders:
This segment is not Mandatory for Non-Warehouse Orders.
Sample EDI:
PO41000***********1~ (SIM cards)
or
PO41~ (handsets)
Buyer Identification
To specify identifying information
The REF*YD segment is Mandatory. The YD qualifier references whether the line item is SERIALIZED or NON-SERIALIZED.
SERIALIZED items are items that require the HL*K loop, which communicates all serialized infromation, such as IMEI, Unlock Code, Serial Number, MAC Address, etc.
Only one REF*YD segment is expected at the Item level per Item.
Valid examples for the REFYD:
REFYDSERIALIZED~
REFYD*NON-SERIALIZED~
Code qualifying the Reference Identification
- YD
- Buyer Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- NON-SERIALIZED
- SERIALIZED
Shipment Number
To specify identifying information
The Trading Partner must send the ShipNum (Shipment Number) value from the original Purchase Order created by AT&T Mobility.
** Contact your AT&T Mobility Buyer if you do not receive the ShipNum on the paper/PDF Purchase Order.
Non-Warehouse Orders:
This segment is not Mandatory for Non-Warehouse Orders.
The REF02 (ZZ qualifier) must be expressed in 4 numeric characters, with leading zeros.
examples:
ShipNum 01 will be 0001.
ShipNum 10 will be 0010.
Sample EDI:
Warehouse Orders:
REFZZSHIPNUM~
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The HL Kit loop is Required if the product is Serialized.
The HL Kit loop is NOT Required if the product is Non-Serialized product (i.e. Accessories)
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- K
- Kit
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Subline Item Detail
To specify product subline detail item data
Sample EDI:
For WIRELESS Equipment:
with ICC-ID:
SLN00011I1EA********IC12345678901234567890IS356862003671263TW65225359*PJ20051101*ZZR47R~
without ICC-ID:
SLN00011I1EA***IS356862003671263*TW65225359*PJ20051101*ZZR47R~
without Unlock Code:
SLN00011I1EA***IS356862003671263*TWUNLOCK_NOT_SENT*PJ20051101*ZZR472R~
For WIRELINE Equipment:
with Serial Number & MAC Address:
SLN00011I1EASN123456789012*MA210987654321*PJ20051101ZZR472_G_08.18.40R~
without Serial Number:
SLN00011I1EA*****SNSERIAL_NOT_SENT**MA210987654321*PJ20051101ZZ*R472_G_08.18.40R~
without MAC Address:
SLN00011I1EA*SN123456789012**MAMAC_NOT_SENTPJ20051101ZZR472_G_08.18.40R~
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Must match the Line Number from the LIN segment (LIN01) exactly.
Alphanumeric characters assigned for differentiation within a transaction set
- SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.
Unique Counter for each SLN iteration.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
Numeric value of quantity
Usually a quantity of 1.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SN
- Serial Number
Identifying number for a product or service
The SLN11 and SLN12 are mandatory for all WIRELINE equipment.
** Serial Number is mandatory for all wireline equipment. There will only be one Serial Number per piece of wireline equipment. If Serial Number is not being sent in the SLN segment of the EDI 856 based on a prior legal agreement with AT&T, please include the following hardcoded text within the SLN12 element: SERIAL_NOT_SENT.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IC
- ICC-ID (SIM Serial Number)
Identifying number for a product or service
The SLN14 contains the ICC-ID (SIM Serial Number).
** ICC-ID (SIM Cards Serial Number) is mandatory for all WIRELESS equipment that is pre-packaged with SIM Cards. There will only be one ICC-ID per handset/data device.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IS
- International Standard Serial Number (ISSN)
IMEI Code
Identifying number for a product or service
The SLN16 contains the IMEI number. The SLN15 and SLN16 are mandatory for all WIRELESS equipment.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- TW
- Program Code
Subsidy Unlock Code
Identifying number for a product or service
The SLN17 and SLN18 are mandatory for all WIRELESS equipment.
** Subsidy Unlock Codes (SIMLOCK3 or SIMLOCK4) are mandatory for all wireless equipment. There will only be one Subsidy Unlock Code per handset/data device. If Subsidy Unlock Code is not being sent in the SLN segment of the EDI 856 based on a prior legal agreement with AT&T, please include the following hardcoded text within the SLN18 element: UNLOCK_NOT_SENT.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MA
- Media Access Control (MAC) Address
- OI
- OEM Identification Code
Identifying number for a product or service
The SLN19 and SLN20 are mandatory for all WIRELINE equipment.
** Media Access Control (MAC) Address is mandatory for all wireline equipment. There will only be one Media Access Control (MAC) Address per piece of wireline equipment. If Media Access Control (MAC) Address is not being sent in the SLN segment of the EDI 856 based on a prior legal agreement with AT&T, please include the following hardcoded text within the SLN20 element: MAC_NOT_SENT.
The SLN19 and SLN20 are mandatory for all FEMTOCELL equipment.
** OEM Identification Code is mandatory for all FemtoCell equipment. There will only be one OEM Identification Code per piece of FemtoCell equipment.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PJ
- Product Date Code (A code indicating the period during which a product was manufactured.)
Manufacture Date
Identifying number for a product or service
The SLN21 and SLN22 are mandatory for all WIRELESS equipment.
Format Date as CCYYMMDD. If the Manufacture Date is not formatted correctly, the EDI856 transaction will be rejected.
Manufacture Date - This is the date which the device was manufactured.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ZZ
- Software/Firmware Version
Identifying number for a product or service
The SLN23 and SLN24 are mandatory for all WIRELESS equipment.
Firmware Version - Build or version of firmware on the phone.
Vendor Firmware Version Number must be sent for all handset/data card devices.
AT&T Mobility is expecting the Operating System (OS) Software/Firmware version in SLN24.
For handsets/data devices that also utilize a Flex Version, please use the SLN25 and SLN26.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- RN
- Flex Version
Identifying number for a product or service
Flex Version - Depending on the device, a Flex Version will identify the build of the software. This field will contain the appropriate information of this build. This should be blank if it is not applicable to a device.
For handsets/data devices that also utilize a Flex Version, please use the SLN25 and SLN26.
The HL Tare iteration is Mandatory for all Warehouse shipments
Non-Warehouse Shipments:
This segment is not Mandatory for Non-Warehouse Shipments.
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- T
- Shipping Tare
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
If the product has a UCC-128 barcode label applied, the MAN segment could contain the following:
MANGM00123456789123456789~
**** Only 1 MAN segment is required at the Tare level.
Sample EDI:
MANAny Qualifier123456789123456~
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
The MAN02 should contain a valid identification number for the Pallet. The AT&T Mobility Routing Guide should be referenced.
Sample EDI:
Warehouse and Non-Warehouse Orders:
For Serialized Items
HL54I1~
For Non-Serialized Items
HL54I0~
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- I
- Item
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
Warehouse Orders:
LIN0001CBXXX.12345MNMODEL NUMBERUIUPC CODESK*12345~
Non-Warehouse Orders:
LIN0001CBXXX.12345MN*MODEL NUMBER~
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
The LIN01 must be the Line Number from the Original Purchase Order created by AT&T Mobility. The LIN01 must be expressed in 4 numeric characters, with leading zeros.
examples:
Line Item 01 will be 0001.
Line Item 10 will be 0010.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- CB
- Buyer's Catalog Number
Identifying number for a product or service
The format of the SKU must match the value sent in the original Purchase Order. Typically, the Buyer's Catalog Number is formatted as XXX.12345 where 'XXX.' is the prefix to the numeric AT&T Mobility SKU.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MN
- Model Number
Identifying number for a product or service
Model: This is the model of the device (e.g. 'V70G', '5190', 'Treo 650')
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UI
- U.P.C. Consumer Package Code (1-5-5)
Identifying number for a product or service
UPC Code is not Mandatory. However, if you have this information, please include it in this element.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
The AT&T Mobility SKU is required on ALL Warehouse Orders, but not on Non-Warehouse Orders.
The AT&T Mobility SKU is sent in the Purchase Order. The value in the LIN09 element should be the numeric portion of the LIN03 Buyers Catalog Number; do not send the 'XXX.' prefix in the LIN09.
Item Detail (Shipment)
To specify line-item detail relative to shipment
Sample EDI:
Warehouse Orders:
SN100012000*EA~
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
Must match the Line Number from the LIN segment (LIN01) exactly
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Serialized: Total number of eaches in the carton/container. This quantity will be the number of Serialized eaches in the carton/container. The SN102 must match the number of HL Kit level SLN segment iterations.
Non-Serialized: Total number of eaches in the carton/container. This quantity will be the number of Non-Serialized eaches in the carton/container.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- SN103 defines the unit of measurement for both SN102 and SN104.
- EA
- Each
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
For SIM cards, the box inside the outer carton contains 4 packs of 250 each. The PO401 would be 1000 and the PO414 should be 1.
PO41000***********1~
For handsets, no Inner Pack is used. You should send just the PO401.
Handset Example:
PO410~
Non-Warehouse Orders:
This segment is not Mandatory for Non-Warehouse Orders.
Sample EDI:
PO41000***********1~ (SIM cards)
or
PO41~ (handsets)
Buyer Identification
To specify identifying information
The REF*YD segment is Mandatory. The YD qualifier references whether the line item is SERIALIZED or NON-SERIALIZED.
SERIALIZED items are items that require the HL*K loop, which communicates all serialized infromation, such as IMEI, Unlock Code, Serial Number, MAC Address, etc.
Only one REF*YD segment is expected at the Item level per Item.
Valid examples for the REFYD:
REFYDSERIALIZED~
REFYD*NON-SERIALIZED~
Code qualifying the Reference Identification
- YD
- Buyer Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- NON-SERIALIZED
- SERIALIZED
Shipment Number
To specify identifying information
The Trading Partner must send the ShipNum (Shipment Number) value from the original Purchase Order created by AT&T Mobility.
** Contact your AT&T Mobility Buyer if you do not receive the ShipNum on the paper/PDF Purchase Order.
Non-Warehouse Orders:
This segment is not Mandatory for Non-Warehouse Orders.
The REF02 (ZZ qualifier) must be expressed in 4 numeric characters, with leading zeros.
examples:
ShipNum 01 will be 0001.
ShipNum 10 will be 0010.
Sample EDI:
Warehouse Orders:
REFZZSHIPNUM~
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The HL Kit loop is Required if the product is Serialized.
The HL Kit loop is NOT Required if the product is Non-Serialized product (i.e. Accessories)
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- K
- Kit
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Subline Item Detail
To specify product subline detail item data
Sample EDI:
For WIRELESS Equipment:
with ICC-ID:
SLN00011I1EA********IC12345678901234567890IS356862003671263TW65225359*PJ20051101*ZZR47R~
without ICC-ID:
SLN00011I1EA***IS356862003671263*TW65225359*PJ20051101*ZZR47R~
without Unlock Code:
SLN00011I1EA***IS356862003671263*TWUNLOCK_NOT_SENT*PJ20051101*ZZR472R~
For WIRELINE Equipment:
with Serial Number & MAC Address:
SLN00011I1EASN123456789012*MA210987654321*PJ20051101ZZR472_G_08.18.40R~
without Serial Number:
SLN00011I1EA*****SNSERIAL_NOT_SENT**MA210987654321*PJ20051101ZZ*R472_G_08.18.40R~
without MAC Address:
SLN00011I1EA*SN123456789012**MAMAC_NOT_SENTPJ20051101ZZR472_G_08.18.40R~
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Must match the Line Number from the LIN segment (LIN01) exactly.
Alphanumeric characters assigned for differentiation within a transaction set
- SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.
Unique Counter for each SLN iteration.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
Numeric value of quantity
Usually a quantity of 1.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SN
- Serial Number
Identifying number for a product or service
The SLN11 and SLN12 are mandatory for all WIRELINE equipment.
** Serial Number is mandatory for all wireline equipment. There will only be one Serial Number per piece of wireline equipment. If Serial Number is not being sent in the SLN segment of the EDI 856 based on a prior legal agreement with AT&T, please include the following hardcoded text within the SLN12 element: SERIAL_NOT_SENT.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IC
- ICC-ID (SIM Serial Number)
Identifying number for a product or service
The SLN14 contains the ICC-ID (SIM Serial Number).
** ICC-ID (SIM Cards Serial Number) is mandatory for all WIRELESS equipment that is pre-packaged with SIM Cards. There will only be one ICC-ID per handset/data device.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IS
- International Standard Serial Number (ISSN)
IMEI Code
Identifying number for a product or service
The SLN16 contains the IMEI number. The SLN15 and SLN16 are mandatory for all WIRELESS equipment.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- TW
- Program Code
Subsidy Unlock Code
Identifying number for a product or service
The SLN17 and SLN18 are mandatory for all WIRELESS equipment.
** Subsidy Unlock Codes (SIMLOCK3 or SIMLOCK4) are mandatory for all wireless equipment. There will only be one Subsidy Unlock Code per handset/data device. If Subsidy Unlock Code is not being sent in the SLN segment of the EDI 856 based on a prior legal agreement with AT&T, please include the following hardcoded text within the SLN18 element: UNLOCK_NOT_SENT.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MA
- Media Access Control (MAC) Address
- OI
- OEM Identification Code
Identifying number for a product or service
The SLN19 and SLN20 are mandatory for all WIRELINE equipment.
** Media Access Control (MAC) Address is mandatory for all wireline equipment. There will only be one Media Access Control (MAC) Address per piece of wireline equipment. If Media Access Control (MAC) Address is not being sent in the SLN segment of the EDI 856 based on a prior legal agreement with AT&T, please include the following hardcoded text within the SLN20 element: MAC_NOT_SENT.
The SLN19 and SLN20 are mandatory for all FEMTOCELL equipment.
** OEM Identification Code is mandatory for all FemtoCell equipment. There will only be one OEM Identification Code per piece of FemtoCell equipment.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PJ
- Product Date Code (A code indicating the period during which a product was manufactured.)
Manufacture Date
Identifying number for a product or service
The SLN21 and SLN22 are mandatory for all WIRELESS equipment.
Format Date as CCYYMMDD. If the Manufacture Date is not formatted correctly, the EDI856 transaction will be rejected.
Manufacture Date - This is the date which the device was manufactured.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ZZ
- Software/Firmware Version
Identifying number for a product or service
The SLN23 and SLN24 are mandatory for all WIRELESS equipment.
Firmware Version - Build or version of firmware on the phone.
Vendor Firmware Version Number must be sent for all handset/data card devices.
AT&T Mobility is expecting the Operating System (OS) Software/Firmware version in SLN24.
For handsets/data devices that also utilize a Flex Version, please use the SLN25 and SLN26.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- RN
- Flex Version
Identifying number for a product or service
Flex Version - Depending on the device, a Flex Version will identify the build of the software. This field will contain the appropriate information of this build. This should be blank if it is not applicable to a device.
For handsets/data devices that also utilize a Flex Version, please use the SLN25 and SLN26.
The HL Pack iteration is Mandatory for all Warehouse shipments
Non-Warehouse Shipments:
This segment is not Mandatory for Non-Warehouse Shipments.
Sample EDI:
Warehouse Orders:
For LTL, TL, or Small Parcel Shipments where product is in a Carton
HL43P1~
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- P
- Pack
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Marks and Numbers
To indicate identifying marks and numbers for shipping containers
If the product has a UCC-128 barcode label applied, the MAN segment could contain the following:
MANGM00123456789123456789~
**** Only 1 MAN segment is required at the Pack level.
**** The Carton ID number is required in the MAN segment.
Sample EDI:
MANAny Qualifier123456789123456~
Code specifying the application or source of Marks and Numbers (87)
- MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the same physical container.
- When MAN01 contains code "UC" (U.P.C. Shipping Container Code) and MAN05/MAN06 contain a range of ID numbers, MAN03 is not used. The reason for this is that the U.P.C. Shipping Container code is the same on every carton that is represented in the range in MAN05/MAN06.
Marks and numbers used to identify a shipment or parts of a shipment
- When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is the ending number of that range.
The MAN02 should contain a valid identification number for the Carton. The AT&T Mobility Routing Guide should be referenced.
Sample EDI:
Warehouse and Non-Warehouse Orders:
For Serialized Items
HL54I1~
For Non-Serialized Items
HL54I0~
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- I
- Item
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Item Identification
To specify basic item identification data
Warehouse Orders:
LIN0001CBXXX.12345MNMODEL NUMBERUIUPC CODESK*12345~
Non-Warehouse Orders:
LIN0001CBXXX.12345MN*MODEL NUMBER~
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
The LIN01 must be the Line Number from the Original Purchase Order created by AT&T Mobility. The LIN01 must be expressed in 4 numeric characters, with leading zeros.
examples:
Line Item 01 will be 0001.
Line Item 10 will be 0010.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- CB
- Buyer's Catalog Number
Identifying number for a product or service
The format of the SKU must match the value sent in the original Purchase Order. Typically, the Buyer's Catalog Number is formatted as XXX.12345 where 'XXX.' is the prefix to the numeric AT&T Mobility SKU.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MN
- Model Number
Identifying number for a product or service
Model: This is the model of the device (e.g. 'V70G', '5190', 'Treo 650')
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- UI
- U.P.C. Consumer Package Code (1-5-5)
Identifying number for a product or service
UPC Code is not Mandatory. However, if you have this information, please include it in this element.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SK
- Stock Keeping Unit (SKU)
Identifying number for a product or service
The AT&T Mobility SKU is required on ALL Warehouse Orders, but not on Non-Warehouse Orders.
The AT&T Mobility SKU is sent in the Purchase Order. The value in the LIN09 element should be the numeric portion of the LIN03 Buyers Catalog Number; do not send the 'XXX.' prefix in the LIN09.
Item Detail (Shipment)
To specify line-item detail relative to shipment
Sample EDI:
Warehouse Orders:
SN100012000*EA~
Alphanumeric characters assigned for differentiation within a transaction set
- SN101 is the ship notice line-item identification.
Must match the Line Number from the LIN segment (LIN01) exactly
Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set
Serialized: Total number of eaches in the carton/container. This quantity will be the number of Serialized eaches in the carton/container. The SN102 must match the number of HL Kit level SLN segment iterations.
Non-Serialized: Total number of eaches in the carton/container. This quantity will be the number of Non-Serialized eaches in the carton/container.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- SN103 defines the unit of measurement for both SN102 and SN104.
- EA
- Each
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
For SIM cards, the box inside the outer carton contains 4 packs of 250 each. The PO401 would be 1000 and the PO414 should be 1.
PO41000***********1~
For handsets, no Inner Pack is used. You should send just the PO401.
Handset Example:
PO410~
Non-Warehouse Orders:
This segment is not Mandatory for Non-Warehouse Orders.
Sample EDI:
PO41000***********1~ (SIM cards)
or
PO41~ (handsets)
Buyer Identification
To specify identifying information
The REF*YD segment is Mandatory. The YD qualifier references whether the line item is SERIALIZED or NON-SERIALIZED.
SERIALIZED items are items that require the HL*K loop, which communicates all serialized infromation, such as IMEI, Unlock Code, Serial Number, MAC Address, etc.
Only one REF*YD segment is expected at the Item level per Item.
Valid examples for the REFYD:
REFYDSERIALIZED~
REFYD*NON-SERIALIZED~
Code qualifying the Reference Identification
- YD
- Buyer Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- NON-SERIALIZED
- SERIALIZED
Shipment Number
To specify identifying information
The Trading Partner must send the ShipNum (Shipment Number) value from the original Purchase Order created by AT&T Mobility.
** Contact your AT&T Mobility Buyer if you do not receive the ShipNum on the paper/PDF Purchase Order.
Non-Warehouse Orders:
This segment is not Mandatory for Non-Warehouse Orders.
The REF02 (ZZ qualifier) must be expressed in 4 numeric characters, with leading zeros.
examples:
ShipNum 01 will be 0001.
ShipNum 10 will be 0010.
Sample EDI:
Warehouse Orders:
REFZZSHIPNUM~
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The HL Kit loop is Required if the product is Serialized.
The HL Kit loop is NOT Required if the product is Non-Serialized product (i.e. Accessories)
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
- The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Code defining the characteristic of a level in a hierarchical structure
- 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.
- K
- Kit
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Subline Item Detail
To specify product subline detail item data
Sample EDI:
For WIRELESS Equipment:
with ICC-ID:
SLN00011I1EA********IC12345678901234567890IS356862003671263TW65225359*PJ20051101*ZZR47R~
without ICC-ID:
SLN00011I1EA***IS356862003671263*TW65225359*PJ20051101*ZZR47R~
without Unlock Code:
SLN00011I1EA***IS356862003671263*TWUNLOCK_NOT_SENT*PJ20051101*ZZR472R~
For WIRELINE Equipment:
with Serial Number & MAC Address:
SLN00011I1EASN123456789012*MA210987654321*PJ20051101ZZR472_G_08.18.40R~
without Serial Number:
SLN00011I1EA*****SNSERIAL_NOT_SENT**MA210987654321*PJ20051101ZZ*R472_G_08.18.40R~
without MAC Address:
SLN00011I1EA*SN123456789012**MAMAC_NOT_SENTPJ20051101ZZR472_G_08.18.40R~
Alphanumeric characters assigned for differentiation within a transaction set
- SLN01 is the identifying number for the subline item.
- SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
Must match the Line Number from the LIN segment (LIN01) exactly.
Alphanumeric characters assigned for differentiation within a transaction set
- SLN02 is the identifying number for the subline level. The subline level is analogous to the level code used in a bill of materials.
Unique Counter for each SLN iteration.
Code indicating the relationship between entities
- SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
- I
- Included
Numeric value of quantity
Usually a quantity of 1.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- SN
- Serial Number
Identifying number for a product or service
The SLN11 and SLN12 are mandatory for all WIRELINE equipment.
** Serial Number is mandatory for all wireline equipment. There will only be one Serial Number per piece of wireline equipment. If Serial Number is not being sent in the SLN segment of the EDI 856 based on a prior legal agreement with AT&T, please include the following hardcoded text within the SLN12 element: SERIAL_NOT_SENT.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IC
- ICC-ID (SIM Serial Number)
Identifying number for a product or service
The SLN14 contains the ICC-ID (SIM Serial Number).
** ICC-ID (SIM Cards Serial Number) is mandatory for all WIRELESS equipment that is pre-packaged with SIM Cards. There will only be one ICC-ID per handset/data device.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IS
- International Standard Serial Number (ISSN)
IMEI Code
Identifying number for a product or service
The SLN16 contains the IMEI number. The SLN15 and SLN16 are mandatory for all WIRELESS equipment.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- TW
- Program Code
Subsidy Unlock Code
Identifying number for a product or service
The SLN17 and SLN18 are mandatory for all WIRELESS equipment.
** Subsidy Unlock Codes (SIMLOCK3 or SIMLOCK4) are mandatory for all wireless equipment. There will only be one Subsidy Unlock Code per handset/data device. If Subsidy Unlock Code is not being sent in the SLN segment of the EDI 856 based on a prior legal agreement with AT&T, please include the following hardcoded text within the SLN18 element: UNLOCK_NOT_SENT.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- MA
- Media Access Control (MAC) Address
- OI
- OEM Identification Code
Identifying number for a product or service
The SLN19 and SLN20 are mandatory for all WIRELINE equipment.
** Media Access Control (MAC) Address is mandatory for all wireline equipment. There will only be one Media Access Control (MAC) Address per piece of wireline equipment. If Media Access Control (MAC) Address is not being sent in the SLN segment of the EDI 856 based on a prior legal agreement with AT&T, please include the following hardcoded text within the SLN20 element: MAC_NOT_SENT.
The SLN19 and SLN20 are mandatory for all FEMTOCELL equipment.
** OEM Identification Code is mandatory for all FemtoCell equipment. There will only be one OEM Identification Code per piece of FemtoCell equipment.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PJ
- Product Date Code (A code indicating the period during which a product was manufactured.)
Manufacture Date
Identifying number for a product or service
The SLN21 and SLN22 are mandatory for all WIRELESS equipment.
Format Date as CCYYMMDD. If the Manufacture Date is not formatted correctly, the EDI856 transaction will be rejected.
Manufacture Date - This is the date which the device was manufactured.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ZZ
- Software/Firmware Version
Identifying number for a product or service
The SLN23 and SLN24 are mandatory for all WIRELESS equipment.
Firmware Version - Build or version of firmware on the phone.
Vendor Firmware Version Number must be sent for all handset/data card devices.
AT&T Mobility is expecting the Operating System (OS) Software/Firmware version in SLN24.
For handsets/data devices that also utilize a Flex Version, please use the SLN25 and SLN26.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- RN
- Flex Version
Identifying number for a product or service
Flex Version - Depending on the device, a Flex Version will identify the build of the software. This field will contain the appropriate information of this build. This should be blank if it is not applicable to a device.
For handsets/data devices that also utilize a Flex Version, please use the SLN25 and SLN26.
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- Number of line items (CTT01) is the accumulation of the number of HL segments.
If used, hash total (CTT02) is the sum of the value of units shipped (SN102) for each SN1 segment.
Sample EDI:
CTT0120002005~
Total number of line items in the transaction set
The CTT01 contains the total number of Eaches in the shipment. If the product is serialized (such as handsets), the CTT01 should contain the total number of SLN segments in the HL Kit level loop. If the product is not serialized (such as accessories), the CTT01 should contain the total number of eaches in the shipment (sum of the SN102 from the item level).
Example:
If there are two HL Item level loops in the 856, the sum of the SN102 elements must be provided in the CTT01.
HL Item Loop # 1
LIN Item 2
SN10001500EA~
...
HL Item Loop # 2
LIN Item 2
SN100021000EA~
...
CTT0115001503~
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
The CTT02 must contain the Total Count of all HL segments
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.