GSA (General Services Administration)
/
Ship Notice/Manifest (GSA ADV)
  • Specification
  • EDI Inspector
Import guide into your account
GSA (General Services Administration) logo

X12 856 Ship Notice/Manifest (GSA ADV)

X12 Release 4010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI sample
  • Sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/gsa/ship-noticemanifest-gsa-adv/01HH10MK8XX5HAR8HHBF3JG1FN
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
detail
HL Loop Address Information
HL
010
Hierarchical Level
Max use 1
Required
N1 Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

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
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

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
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

SH
Ship Notice/Manifest (856)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BSN
020
Heading > BSN

Beginning Segment for Ship Notice

RequiredMax use 1

To transmit identifying numbers, dates, and other basic data relating to the transaction set

Example
BSN-01
353
Transaction Set Purpose Code
Required
Identifier (ID)

Code identifying purpose of transaction set

00
Original
CO
Corrected

Use only after receiving an acknowledgment of receipt for a previously transmitted Shipment Notice. When used, the entire Shipment Notice will be transmitted.

BSN-02
396
Shipment Identification
Required
String (AN)
Min 2Max 30

A unique control number assigned by the original shipper to identify a specific shipment

Usage notes
  1. Use, on other than Defense Logistics Management System Shipment Performance Notices, to cite the shipment number. If applicable, include the final shipment indicator (i.e., the letter Z) or if applicable, the replacement shipment indicator, e.g., A, B, etc., at the end of the shipment number.

  2. When used by Defense Contract Management Command as a Shipment Performance Notice or destination acceptance alert, use ZZ for this data element. Defense Logistics Management System does not use this data element, but it is mandatory in the X12 standards. The ZZ entry satisfies the X12 usage requirements; the receiving application software shall not process it.

  3. On Defense Logistics Management System Shipment Performance Notices, do not include the final shipment indicator (Z) on underrun deliveries when a final line item shipment is replaced. In that situation, use the 2/REF/150 segment.

BSN-03
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BSN03 is the date the shipment transaction set is created.
Usage notes
  1. Use to indicate the transaction set creation date.

  2. Express the originating activity's date in Universal Time Coordinate (UTC).

BSN-04
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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.
Usage notes
  1. Express the originating activity's time in Universal Time Coordinate (UTC).

  2. Express time in a four-position (Hour Hour Minute Minute) format

DTM
040
Heading > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

282
Previous Report
DTM-02
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes
  1. Use to indicate the transaction set creation date of the original Shipment Notice (e.g., the date carried in BSN03 of the original transmission).

  2. Express the date in Universal Time Coordinate.

DTM-03
337
Time
Optional
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

Usage notes
  1. Use to indicate the transaction set creation time of the original Shipment Notice (e.g., the time carried in BSN04 of the original transmission).

  2. Express the time in a four-position (Hour Hour Minute Minute) format.

Heading end

Detail

HL Loop Address Information
RequiredMax 200000
HL
010
Detail > HL Loop Address Information > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

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.
V
Address Information
N1 Loop
OptionalMax >1
N1
220
Detail > HL Loop Address Information > N1 Loop > N1

Name

RequiredMax use 1

To identify a party by type of organization, name, and code

Example
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
At least one of Name (N1-02) or Identification Code Qualifier (N1-03) is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)
Min 2Max 3

Code identifying an organizational entity, a physical location, property or an individual

N1-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N1-03
66
Identification Code Qualifier
Optional
Identifier (ID)
Min 1Max 2

Code designating the system/method of code structure used for Identification Code (67)

N1-04
67
Identification Code
Optional
String (AN)
Min 2Max 80

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.
N2
230
Detail > HL Loop Address Information > N1 Loop > N2

Additional Name Information

OptionalMax use 2

To specify additional names or those longer than 35 characters in length

Example
N2-01
93
Name
Required
String (AN)
Min 1Max 60

Free-form name

N2-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

N3
240
Detail > HL Loop Address Information > N1 Loop > N3

Address Information

OptionalMax use 2

To specify the location of the named party

Example
N3-01
166
Address Information
Required
String (AN)
Min 1Max 55

Address information

N3-02
166
Address Information
Optional
String (AN)
Min 1Max 55

Address information

N4
250
Detail > HL Loop Address Information > N1 Loop > N4

Geographic Location

OptionalMax use 1

To specify the geographic place of the named party

Example
N4-01
19
City Name
Optional
String (AN)
Min 2Max 30

Free-form text for city name

  • A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
N4-02
156
State or Province Code
Optional
Identifier (ID)
Min 2Max 2

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.
N4-03
116
Postal Code
Optional
Identifier (ID)
Min 3Max 15

Code defining international postal zone code excluding punctuation and blanks (zip code for United States)

N4-04
26
Country Code
Optional
Identifier (ID)
Min 2Max 3

Code identifying the country

PER
270
Detail > HL Loop Address Information > N1 Loop > PER

Administrative Communications Contact

OptionalMax use 3

To identify a person or office to whom administrative communications should be directed

Example
If either Communication Number Qualifier (PER-03) or Communication Number (PER-04) is present, then the other is required
If either Communication Number Qualifier (PER-05) or Communication Number (PER-06) is present, then the other is required
If either Communication Number Qualifier (PER-07) or Communication Number (PER-08) is present, then the other is required
PER-01
366
Contact Function Code
Required
Identifier (ID)

Code identifying the major duty or responsibility of the person or group named

IC
Information Contact
PER-02
93
Name
Optional
String (AN)
Min 1Max 60

Free-form name

Usage notes

When PER01 cites codes CE or AS, use to indicate the name of the party making the certification or authorization.

PER-03
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

EM
Electronic Mail
FX
Facsimile
IT
International Telephone
TE
Telephone
PER-04
364
Communication Number
Optional
String (AN)
Min 1Max 80

Complete communications number including country or area code when applicable

PER-05
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

AU
Defense Switched Network Department of Defense telecommunications system and successor of the Automatic Voice Network (AUTOVON)
EM
Electronic Mail
EX
Telephone Extension

When used, there must be a previous communication number citing either a national or international telephone number.

FT
Federal Telecommunications System (FTS)
FX
Facsimile
IT
International Telephone
TE
Telephone
PER-06
364
Communication Number
Optional
String (AN)
Min 1Max 80

Complete communications number including country or area code when applicable

PER-07
365
Communication Number Qualifier
Optional
Identifier (ID)

Code identifying the type of communication number

AU
Defense Switched Network Department of Defense telecommunications system and successor of the Automatic Voice Network (AUTOVON)
EM
Electronic Mail
EX
Telephone Extension

When used, there must be a previous communication number citing either a national or international telephone number.

FT
Federal Telecommunications System (FTS)
FX
Facsimile
IT
International Telephone
TE
Telephone
PER-08
364
Communication Number
Optional
String (AN)
Min 1Max 80

Complete communications number including country or area code when applicable

PER-09
443
Contact Inquiry Reference
Optional
String (AN)

Additional reference number or description to clarify a contact number

Usage notes

When PER01 cites code CE (Certifier), use to indicate the title of the party making the certification.

9
Indicator Code

Use to indicate Fast Pay terms.

10
Transaction Status Indicator Code

Use to identify the status of supply and service shipment notices.

14
Contract Shipment Advice Code

Use as required to identify contract shipment advice information for supply and service shipment notices.

16
Cash Discount Stipulation Code

Use to indicate that a shipment involves discount payment terms.

83
Supply Condition Code

Use to identify the supply condition of bulk petroleum shipments.

84
Management Code
EP
United States Environmental Protection Agency (EPA)
FG
Federal Government
GS
General Services Administration (GSA)
ZZ
Mutually Defined

Use to indicate an agency that is not otherwise listed.

Use to indicate the acceptance site.

N1 Loop end
HL Loop Shipment
RequiredMax 200000
HL
010
Detail > HL Loop Address Information > HL Loop Shipment > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

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
PRF
050
Detail > HL Loop Address Information > HL Loop Shipment > PRF

Purchase Order Reference

RequiredMax use 1

To provide reference to a specific purchase order

Example
PRF-01
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

Enter the purchase order number, contract number (including Federal Supply Schedules, General Services Administration Schedules and all other basic contracts), Blanket Purchase Agreement number, Grant, Lease or Agreement number. This is always the Procurement Instrument Identification Number for the Department of Defense or the equivalent expression for Civilian Agencies. This is never the number of a delivery order, call or release against a basic award instrument. That number is carried in PRF02. This number shall be transmitted without dashes. Contract number.

PRF-02
328
Release Number
Optional
String (AN)
Min 1Max 30

Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction

Usage notes

Enter the number of a release, call or delivery order against a basic award instrument. This is always the Supplemental Procurement Instrument Identification Number for the Department of Defense or the equivalent expression for Civilian Agencies. This number shall be transmitted without dashes. When preparing a Shipment Performance Notice or destination acceptance alert for Defense Contract Management Command do not include the contract modification number. Required Purchase order number.

PRF-03
327
Change Order Sequence Number
Optional
String (AN)
Min 1Max 8

Number assigned by the orderer identifying a specific change or revision to a previously transmitted transaction set

Usage notes
  1. Use to indicate, as applicable, the modification number of the contract or purchase order. When a call or delivery order is cited, use to indicate the modification number of the call or order, as applicable. When both the contract and call or order have been modified, cite the modification number of the call or order and do not transmit the modification number of the contract.

  2. Except when shipping instructions are furnished by telephone or message and the confirming contract modification (SF 30) has not been received, do not use PRF03 to enter supplementary numbers used in conjunction with basic Procurement Instrument Identification Numbers to identify -- Modifications to contracts and agreements; Modifications to calls/orders; or Document numbers representing contracts written between contractors.

PRF-04
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • PRF04 is the date assigned by the purchaser to purchase order.
PRF-05
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

Usage notes

This Reference Number should be what goes out on the Purchase Order (REF with FI qualifier). Required data.

PRF-06
367
Contract Number
Optional
String (AN)
Min 1Max 30

Contract number

Usage notes

Use to identify the Small Business Administration (SBA) contract number for an 8a set-aside. The SBA office issuing this contract is cited in 2/N1/220 segment by use of code C9 in N101.

HL Loop Item
RequiredMax 200000
HL
010
Detail > HL Loop Address Information > HL Loop Shipment > HL Loop Item > HL

Hierarchical Level

RequiredMax use 1

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.
Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

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
LIN
020
Detail > HL Loop Address Information > HL Loop Shipment > HL Loop Item > LIN

Item Identification

OptionalMax use 1

To specify basic item identification data

Example
If either Product/Service ID Qualifier (LIN-04) or Product/Service ID (LIN-05) is present, then the other is required
If either Product/Service ID Qualifier (LIN-06) or Product/Service ID (LIN-07) is present, then the other is required
If either Product/Service ID Qualifier (LIN-08) or Product/Service ID (LIN-09) is present, then the other is required
If either Product/Service ID Qualifier (LIN-10) or Product/Service ID (LIN-11) is present, then the other is required
If either Product/Service ID Qualifier (LIN-12) or Product/Service ID (LIN-13) is present, then the other is required
If either Product/Service ID Qualifier (LIN-14) or Product/Service ID (LIN-15) is present, then the other is required
If either Product/Service ID Qualifier (LIN-16) or Product/Service ID (LIN-17) is present, then the other is required
If either Product/Service ID Qualifier (LIN-18) or Product/Service ID (LIN-19) is present, then the other is required
If either Product/Service ID Qualifier (LIN-20) or Product/Service ID (LIN-21) is present, then the other is required
If either Product/Service ID Qualifier (LIN-22) or Product/Service ID (LIN-23) is present, then the other is required
If either Product/Service ID Qualifier (LIN-24) or Product/Service ID (LIN-25) is present, then the other is required
If either Product/Service ID Qualifier (LIN-30) or Product/Service ID (LIN-31) is present, then the other is required
If either Product/Service ID Qualifier (LIN-28) or Product/Service ID (LIN-29) is present, then the other is required
If either Product/Service ID Qualifier (LIN-26) or Product/Service ID (LIN-27) is present, then the other is required
LIN-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • LIN01 is the line item identification
Usage notes
  1. Use to identify in accordance with the format prescribed in the Defense Federal Acquisition Regulation Supplement Uniform Line Item Numbering Policy, the Line Item, if applicable, e.g., Contract Line Item Number, Sub Line Item Number, Exhibit Line Item Number, etc., in accordance with the Uniform Contract Line Item Numbering System.

  2. This data element is required when preparing a Shipment Performance Notice or destination acceptance alert for Defense Contract Management Command use.

LIN-02
235
Product/Service ID Qualifier
Required
Identifier (ID)

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.
Usage notes
  1. For Navy and Defense Logistics Agency contracts, LIN02 must be used at least once and cited either of codes FS, MG, or SW to identify material. Use code SV to identify a service performance notice.

  2. Use code PD when the line item cannot be identified by using one of the other listed codes. When used, describe the item in the associated Product/Service ID, DE 234.

  3. For other than Navy and Defense Logistics Agency contracts use any applicable code(s).

  4. For bulk fuels, only use code FS.

CN
Commodity Name
FS
National Stock Number

Must use for Navy and Defense Logistics Agency contracts, when the National Stock Number is known. Transmit the number without the dashes. Submit only the basic 13 position National Stock Number.
Use to indicate the Government assigned management/material control code if provided.

MF
Manufacturer
MG
Manufacturer's Part Number

Use as needed to identify the manufacturer's part number. When applicable use an additional occurrence of a 235/234 pair citing code ZB to identify the manufacturer's Contractor and Government Entity code. Required data.

VP
Vendor's (Seller's) Part Number

Use to indicate a part number assigned by a contractor other than a manufacturer.

LIN-03
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

Use code "Z" to indicate "See Contract" when the item cannot be described by one of the other codes, or by using the 2/PID/070 segment.

LIN-04
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

CN
Commodity Name
FS
National Stock Number
MG
Manufacturer's Part Number
VP
Vendor's (Seller's) Part Number
LIN-05
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-06
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-08
235
Product/Service ID Qualifier
Optional
Identifier (ID)

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

CN
Commodity Name
FS
National Stock Number
MF
Manufacturer
MG
Manufacturer's Part Number
VP
Vendor's (Seller's) Part Number
LIN-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-10
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-12
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN-13
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-14
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN-15
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-16
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN-17
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-18
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN-19
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-20
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN-21
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-22
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN-23
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-24
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN-25
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-26
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN-27
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-28
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN-29
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

LIN-30
235
Product/Service ID Qualifier
Optional
Identifier (ID)
Min 2Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

LIN-31
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

SN1
030
Detail > HL Loop Address Information > HL Loop Shipment > HL Loop Item > SN1

Item Detail (Shipment)

OptionalMax use 1

To specify line-item detail relative to shipment

Example
If either Quantity Ordered (SN1-05) or Unit or Basis for Measurement Code (SN1-06) is present, then the other is required
SN1-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • SN101 is the ship notice line-item identification.
Usage notes

Use only to indicate that the quantity of units shipped, as cited in SN102 is an estimated quantity. When used, cite the letter E to specify when the quantity is an estimate.

SN1-02
382
Number of Units Shipped
Required
Decimal number (R)
Min 1Max 10

Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set

Usage notes
  1. When BSN05 is not present and HL03 is code S (shipment loop), use to identify the quantity shipped.

  2. Use as necessary in the 2/HL/010 container loop to indicate the quantity of returnable containers or the total quantity of containers shipped. Use 2/REF/150 code RS to indicate serial numbers of returnable containers.

  3. When BSN05 is code 0001 and HL03 is code O (Order loop), use to identify the number of items shipped in an order.

  4. When BSN05 is code 0001 and HL03 is code P (Pack loop), use to identify the number of items shipped in a pack.

  5. Use the number "0" (zero) to indicate no quantity was either shipped or reported, such as in an interim Shipment Performance Notice.

SN1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)
Min 2Max 2

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.
Usage notes
  1. Use any code, other than code ZZ, to identify as necessary, the purchase unit for the quantity shipped or service performed. DLMS users see the Unit of Issue and Purchase Unit Conversion Table for available codes. Use code UL when no purchase unit applies.

  2. Use as necessary to indicate the applicable unit when in the shipment or container level loops.

SN1-05
330
Quantity Ordered
Optional
Decimal number (R)
Min 1Max 15

Quantity ordered

Usage notes

Use to indicate another quantity against an alternate unit of issue. When used, include that other unit of issue in the SN106 data element.

SN1-06
355
Unit or Basis for Measurement Code
Optional
Identifier (ID)
Min 2Max 2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

Usage notes

Use any code, other than code ZZ, to indicate the alternate unit of measure. DLMS users see the Unit of Issue and Purchase Unit Conversion Table for available codes.

REF
150
Detail > HL Loop Address Information > HL Loop Shipment > HL Loop Item > REF

Reference Identification

OptionalMax use >1

To specify identifying information

Example
At least one of Reference Identification (REF-02) or Description (REF-03) is required
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

2I
Tracking Number
FI
File Identifier
IL
Internal Order Number
RQ
Purchase Requisition Number
TG
Transportation Control Number
TN
Transaction Number
VR
Vendor ID Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

REF-03
352
Description
Optional
String (AN)
Min 1Max 80

A free-form description to clarify the related data elements and their content

DTM
200
Detail > HL Loop Address Information > HL Loop Shipment > HL Loop Item > DTM

Date/Time Reference

OptionalMax use 10

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

Usage notes

Use only one code except for bulk petroleum shipments which may cite codes 011 and 375 together, if applicable.

009
Process

Use to indicate the item is currently being processed.

011
Shipped

Use to indicate that a supply activity has shipped (i.e., the date a shipment was released to a carrier). Also use to indicate the date of a prior shipment when the current shipment consists of items which were short shipped on the prior shipment.

139
Estimated

Use to indicate the estimated date when a supply will be shipped, (i.e., the estimated date a shipment will be released to a carrier).

177
Cancelled

Use to indicate the cancellation of an item.

514
Transferred

Use to indicate the item has been shipped to GSA Depot, Burlington

727
On-hold

Use to indicate the item is backordered.

928
Reissue

Use to indicate the item has been reshipped.

EXP
Export

Use to indicate the item has been shipped to Tracy, CA

RTO
Referred To

Use to indicate the item has been shipped to GSA Depot, Sharpe

STN
Transition

Use to indicate the item has been shipped to New Cumberland, PA

DTM-02
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

HL Loop Item end
HL Loop Shipment end
HL Loop Address Information end
Detail end

Summary

SE
020
Summary > SE

Transaction Set Trailer

RequiredMax use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

EDI Samples

Sample

ISA*00* *00* *01*000111119 *ZZ*GSAADV *130605*0715*U*00300*000021606*0*P*:
GS*SH*000111119*GSAADV*20130605*0715*14640192*X*004010
ST*856*0001
BSN*00*13371098Z*20130604*233305
HL*1**V
N1*SE*ABC TECHNOLOGIES*1*000111119
PER*IC**EM*SC0133@ABCTECH.COM
HL*2*1*S
PRF*GS00F0000Z*MGAKXS9999M**20230812*19048888-78000999
HL*3*2*I
LIN*1*MG*20-114-X-XXXX*CN*RAGS & WIPING CLOTHS*VP*XXXXXX000002*MF*ANCHOR INC
SN1**5*CA
REF*IL*0071098
REF*VR*007900129
REF*2I*13371098*PC
DTM*011*20130531
SE*15*0001
GE*1*14640192
IEA*1*000021606

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.