888	Item Maintenance	
	Functional Group=QG	

This Draft Standard for Trial Use provides the format and establishes the data contents of the Item Maintenance Transaction Set (888) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to enable a manufacturer, supplier, broker, or agent to provide detailed finished goods product information to a partner in a consumer goods market. This transaction set can be used to provide information about new products or changes in existing product specifications. Price changes will not be sent with this transaction set, but can be sent with the Price Change Transaction Set (879). 
Staffing Notes are identified in red text/yellow highlight.

Staffing Note:  The Small Arms Data Change transaction, DS 888A  was used as the basis for development of DS 888B, UIT Data Change transaction.  Throughout, reference to small arms was changed to UIT item to provide a more generic DS for use with all commodities--these changes are not highlighted.    However NEW qualifiers, data elements, etc, different from the Small Arms DS 888A are identified in blue text.  PAGES with changes from DS 888A are:  1, 5, 8, 11, 20, 23, and 24. 
Notes:
1/0200	One iteration of the N1 loop should be used to identify the buying party (BY) to establish the area or location for which the item maintenance applies. 
2/0200	The G62 segment is used to specify the effective date for the item maintenance action reflected in G5301. 
Federal Note:
1. Organizations use this transaction set to report data corrections and changes for unique item tracking (UIT) items, including UIT reject response corrections and changes, for data recorded in component registries (when applicable), DoD Small Arms registry and originator records.

2. Use one occurrence of this transaction set to transmit a single or multiple transactions.

3. DoD logistics users should refer to the Defense Logistics Management System (DLMS) Supplement to the Federal Implementation Convention (IC) available at URL: http://www.dla.mil/j-6/dlmso. The DLMS Supplement provides specific business rules, conditions, and authorized codes necessary for appropriate use of this IC within the DLMS.

DLMS Note:
1. Use a single occurrence of this transaction set to transmit data changes or corrections for UIT items to one or more organizations. 

2. DLSS functionality allows for Service or Agency data in various RP(s). Data conveyed therein will require Service or Agency identification to DLMSO and incorporation into the DLMS.

3. Users operating under the Defense Logistics Management system (DLMS) must reference the Unit of Issue and Purchase Unit Conversion Table, Transportation Mode of Shipment Conversion Table, and the Accounting Classification Appendix which can be found on the Defense Logistics Management Standards Office (DLMSO) web site at http://www.dla.mil/j-6/dlmso.

4. This DLMS Supplement contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system. DLMS procedures may not have been developed. Components must coordinate requirements and business rules with DLMSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be received or understood by the recipient's automated processing system. Components must coordinate implementation with DLMSO prior to use.

c. Defense Logistics Standard System (DLSS) data which must be retained in the DLMS for a transition period to support transaction conversion in a mixed DLSS/DLMS environment.  This data will be streamlined out once full DLMS implementation is reached.  Components may coordinate with DLMSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment.

d. Data elements which have an expanded files size above existing DLSS capability which may not be supported by the recipient's automated processing system. Components must coordinate implementation with DLMSO prior to use.

e. Data required to accommodate Component -unique transaction requirements (ex. C-series transactions). Data does not apply to DLSS transactions.

4. This revision to the DS incorporates Proposed DLMS Change (PDC) listed. PDCs are available from the DLMSO website:
http://www/dla.mil/j-6/dlmso/Changes.

- PDC 90, New DLMS Supplement (DS) and Federal Implementation Convention (IC) for Transaction Set 888B, Unique Item Tracking  Data Change

Heading:	
	Pos	Id	Segment Name	Req	Max Use	Repeat	Notes	Usage											
	0100	ST	Transaction Set Header	M	1			Must use											
	0150	BGN	Beginning Segment	O	1			Must use											
																			
 LOOP ID - 0100			>1													
	0200	N1	Name	M	1		N1/0200	Must use											
*	0300	N2	Additional Name Information	O	1			Not used											
*	0400	N3	Address Information	O	2			Not used											
*	0500	N4	Geographic Location	O	1			Not used											
*	0600	N9	Reference Identification	O	10			Not used											
	0700	G61	Contact	O	>1			Used											
*	0800	NTE	Note/Special Instruction	O	20			Not used											
*	0850	G93	Price Bracket Identification	O	50			Not used											
	0860	G62	Date/Time	M	1			Must use											
																			
 LOOP ID - 0200			>1													
*	0900	LM	Code Source Information	O	1			Not used											
*	1000	LQ	Industry Code	M	100														
Detail:	
	Pos	Id	Segment Name	Req	Max Use	Repeat	Notes	Usage											
																			
 LOOP ID - 0300			>1													
	0100	G53	Maintenance Type	M	1			Must use											
	0200	G62	Date/Time	O	3		N2/0200	Used											
*	0300	NTE	Note/Special Instruction	O	20			Not used											
																			
 LOOP ID - 0310			>1													
	0350	LX	Assigned Number	M	1			Must use											
	0400	G39	Item Characteristics - Vendor's Selling Unit	O	1			Used											
*	0500	G69	Line Item Detail - Description	O	5			Not used											
*	0550	QTY	Quantity	O	>1			Not used											
*	0560	LIN	Item Identification	O	1			Not used											
*	0570	PID	Product/Item Description	O	200			Not used											
*	0580	PKG	Marking, Packaging, Loading	O	25			Not used											
*	0600	G23	Terms of Sale	O	10			Not used											
*	0700	G62	Date/Time	O	2			Not used											
*	0800	G36	Price List Reference	O	1			Not used											
*	0900	G26	Pricing Conditions	O	2			Not used											
*	1000	G43	Promotion/Price List Area	O	9999			Not used											
*	1100	G24	Promotion Reference	O	999			Not used											
*	1200	G40	Bracket Price	O	99			Not used											
*	1300	G93	Price Bracket Identification	O	50			Not used											
*	1350	G22	Pricing Information	O	5			Not used											
*	1400	G46	Promotion Allowance/Charge	O	99			Not used											
*	1450	H1	Hazardous Material	O	5			Not used											
*	1500	G54	Module Description	O	99			Not used											
	1510	N9	Reference Identification	O	10			Used											
*	1520	UIT	Unit Detail	O	10			Not used											
*	1530	MEA	Measurements	O	10			Not used											
*	1540	TD1	Carrier Details (Quantity and Weight)	O	1			Not used											
																			
 LOOP ID - 0311			>1													
	1560	N1	Name	O	1			Used											
*	1570	N2	Additional Name Information	O	2			Not used											
*	1580	N3	Address Information	O	2			Not used											
*	1590	N4	Geographic Location	O	1			Not used											
*	1600	PAL	Pallet Information	O	>1			Not used											
*	1610	G93	Price Bracket Identification	O	1			Not used											
*	1620	QTY	Quantity	O	1			Not used											
																			
 LOOP ID - 0312			>1													
	1650	G55	Item Characteristics - Consumer Unit	O	1			Used											
*	1700	G69	Line Item Detail - Description	O	5			Not used											
*	1750	QTY	Quantity	O	1			Not used											
*	1760	LIN	Item Identification	O	1			Not used											
*	1765	PID	Product/Item Description	O	200			Not used											
*	1770	H1	Hazardous Material	O	5			Not used											
*	1775	REF	Reference Identification	O	10			Not used											
*	1780	PKG	Marking, Packaging, Loading	O	25			Not used											
*	1785	MEA	Measurements	O	10			Not used											
*	1790	TD1	Carrier Details (Quantity and Weight)	O	1			Not used											
*	1795	SLN	Subline Item Detail	O	100			Not used											
																			
 LOOP ID - 0313			>1													
	1800	LM	Code Source Information	O	1			Used											
	1900	LQ	Industry Code	M	100			Must use											
	2000	SE	Transaction Set Trailer	M	1			Must use											

ST	Transaction Set Header	Pos: 0100	Max: 1
Heading - Mandatory
Loop: N/A	Elements: 3	

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

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	ST01	143	Transaction Set Identifier Code
Description: Code uniquely identifying a Transaction Set 
	Code 	Name                                                                                          _
 	888	Item Maintenance
	M	ID	3/3	Must use		
	ST02	329	Transaction Set Control Number
Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set 
Federal Note:   A unique number assigned by the originator of the transaction set, or the originator's application program.

	M	AN	4/9	Must use		
	ST03	1705	Implementation Convention Reference
Description: Reference assigned to identify Implementation Convention 
	O	AN	1/35	Used		
Semantics:
1.	The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). 
2.	The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate implementation convention to match the transaction set definition. 

BGN	Beginning Segment	Pos: 0150	Max: 1
Heading - Optional
Loop: N/A	Elements: 5	

To indicate the beginning of a transaction set 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	BGN01	353	Transaction Set Purpose Code
Description: Code identifying purpose of transaction set 
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.

	Code 	Name                                                                                          _
 	00	Original
 	77	Simulation Exercise
DLMS Note:   Use to identify a simulated mobilization exercise transaction set. Activities initiating simulated mobilization exercises must ensure complete coordination with all activities involved.  All transaction set recipients must use extreme caution to ensure that individual transactions do not process as action documents which affect accountable records.

	M	ID	2/2	Must use		
	BGN02	127	Reference Identification
Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 
Federal Note:   Use code "Z" for this data element to satisfy mandatory X12 syntax requirements.

	M	AN	1/50	Must use		
	BGN03	373	Date
Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year 
Federal Note:   This date corresponds to the Universal Time Coordinate (UTC).

DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.

	M	DT	8/8	Must use		
	BGN07	640	Transaction Type Code
Description: Code specifying the type of transaction 
	Code 	Name                                                                                          _
 	W1	Weapons Data Change
DLMS Note:   Use to indicate the transaction set that contains changes or corrections to small arms and other UIT program data.  An ANSI Data Maintenance Action has been prepared to obtain a unique qualifier for "UIT Item Data Change" and will be available in a future release.   

	O	ID	2/2	Must use		
	BGN08	306	Action Code
Description: Code indicating type of action 
Federal Note:   Following is a list of preferred codes.

DLMS Note:   For DLMS use, only the following codes are authorized.

	Code 	Name                                                                                          _
 	U	Reject
DLMS Note:   Use with BGN07 code W1 to indicate that a UIT item data correction was rejected.  

 	A6	Modified
DLMS Note:   Use with BGN07 code W1 to indicate that this is the re-submission of a previously rejected transaction.

	O	ID	1/2	Used		

Syntax:
1.  BGN05 C0504 -- If BGN05 is present, then BGN04 is required

Semantics:
1.	BGN02 is the transaction set reference number. 
2.	BGN03 is the transaction set date. 
3.	BGN04 is the transaction set time. 
4.	BGN05 is the transaction set time qualifier. 
5.	BGN06 is the transaction set reference number of a previously sent transaction affected by the current transaction. 

N1	Name	Pos: 0200	Max: 1
Heading - Mandatory
Loop: 0100	Elements: 4	

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

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	N101	98	Entity Identifier Code
Description: Code identifying an organizational entity, a physical location, property or an individual 
Federal Note:   Following is a list of preferred codes.

DLMS Note:   1.  Use only one of codes KK or RL.

2.  For DLMS use, only the following code is authorized.

	Code 	Name                                                                                          _
 	KK	Registering Party
DLMS Note:   Use only in UIT item data change reject to identify the registry issuing the reject.

 	RL	Reporting Location
DLMS Note:   Use to identify the reporting activity submitting the UIT item Data Change transaction.

	M	ID	2/3	Must use		
	N103	66	Identification Code Qualifier
Description: Code designating the system/method of code structure used for Identification Code (67) 
	Code 	Name                                                                                          _
 	1	D-U-N-S Number, Dun & Bradstreet
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.

 	9	D-U-N-S+4, D-U-N-S Number with Four Character Suffix
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.

 	10	Department of Defense Activity Address Code (DODAAC)
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.

 	33	Commercial and Government Entity (CAGE)
DLMS Note:   Use when the contractor is not assigned a DoDAAC.

 	M4	Department of Defense Routing Identifier Code (RIC)
DLMS Note:   1. The RIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS environment. Continued support of the RIC in a full DLMS environment will be assessed at a future date. Typically under the DLMS, the RIC will be replaced with a DoDAAC or a commercial identifier.

2. Future Streamlined data; see introductory DLMS note 4c.

 	UR	Uniform Resource Locator (URL)
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.
STAFFING NOTE:  DLA is including URL, along with RIC and DoDAAC, in DoD UIT-Phase 1 as possible address codes for transactional interface.

	X	ID	1/2	Must use		
	N104	67	Identification Code
Description: Code identifying a party or other code 
	X	AN	2/80	Must use		
	N106	98	Entity Identifier Code
Description: Code identifying an organizational entity, a physical location, property or an individual 
	Code 	Name                                                                                          _
 	FR	Message From
Federal Note:   Must use to indicate that the organization cited in N104 is originating the transaction set. 

	O	ID	2/3	Must use		

Syntax:
1.  N102 R0203 -- At least one of N102 or N103 is required.
2.  N103 P0304 -- If either N103 or N104 are present, then the others are required.

Comments:
1.	This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 
2.	N105 and N106 further define the type of entity in N101. 

Federal Note:
Must use this 1/N1/020 loop to identify the organization originating the transaction set.

G61	Contact	Pos: 0700	Max: >1
Heading - Optional
Loop: N/A	Elements: 5	

To identify a person or office to whom communications should be directed 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	G6101	366	Contact Function Code
Description: Code identifying the major duty or responsibility of the person or group named 
	Code 	Name                                                                                          _
 	IC	Information Contact
Federal Note:   Must use to identify the primary point of contact (POC) and their primary communication number.

DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.

	M	ID	2/2	Must use		
	G6102	93	Name
Description: Free-form name 
Federal Note:   Provide the last name, first name, middle initial, and rate/rank/title, as required, of the individual named POC.  Include blank spaces between name components and periods after initials.  Do not include NMN or NMI when a middle initial is not available.  

	M	AN	1/60	Must use		
	G6103	365	Communication Number Qualifier
Description: Code identifying the type of communication number 
Federal Note:   1.  Use to identify the preferred method of communication in the first repetition.  Use additional repetitions when identifying alternate communication methods. 

2.  Do not include blanks spaces, dashes or parentheses between numbers.  

	Code 	Name                                                                                          _
 	AU	Defense Switched Network
DLMS Note:   1.  Use to identify the DSN telephone number.  

2.  DLMS enhancement; see introductory DLMS note 4a.  

 	EM	Electronic Mail
 	EX	Telephone Extension
Federal Note:   Use immediately following AU, IT, or TE to identify the telephone extension.

 	FT	Federal Telecommunications System (FTS)
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a. 

 	FX	Facsimile
DLMS Note:   Use to identify the facsimile (FAX) telephone number.

 	IT	International Telephone
Federal Note:   Include country and city code.

DLMS Note:   DLMS enhancement; see introductory DLMS note 4a. 

 	TE	Telephone
Federal Note:   Use to identify the commercial telephone number.  Include the area code and number.  

DLMS Note:   DLMS enhancement; see introductory DLMS note 4a. 

 	TL	Telex
 	TX	TWX
	X	ID	2/2	Used		
	G6104	364	Communication Number
Description: Complete communications number including country or area code when applicable 
	X	AN	1/256	Used		
	G6105	443	Contact Inquiry Reference
Description: Additional reference number or description to clarify a contact number 
Federal Note:   Use to indicate the office symbol or activity code, for the party identified.

DLMS Note:   DLMS enhancement; see introductory DLMS note 4a. 

	O	AN	1/20	Used		

Syntax:
1.  G6103 P0304 -- If either G6103 or G6104 are present, then the others are required.

Comments:
1.	G6103 qualifies G6104. 

Federal Note:
1.  Use only under exceptional circumstances when requiring direct communication with the party originating the transaction set.

2.  Use multiple repetitions, as needed, to identify multiple communication numbers.  When using multiple repetitions to identify different communication numbers, repeat the name cited in G6102.  

 

G62	Date/Time	Pos: 0860	Max: 1
Heading - Mandatory
Loop: N/A	Elements: 2	

To specify pertinent dates and times 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	G6203	176	Time Qualifier
Description: Code specifying the reported time 
	Code 	Name                                                                                          _
 	W	Effective Time
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a. 

	X	ID	1/2	Used		
	G6204	337	Time
Description: Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) 
Federal Note:   1. Use to identify the time of transaction set preparation in UTC.

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

STAFFING NOTE:  DLA proposal recommends using 8-position Time format with comment:  “DLA would like to establish application standards to  uniformly identify time elements to decimal seconds (i.e., HHMMSSDD).”    Standard DLMS transactions use HHMM format expressing time in hours and minutes.  Please comment on use of HHMMSSDD vs HHMM.
ADC 81 DLMSO COMMENT:  No comments on use of HHMMSSDD vs HHMM were received during staffing pf PDC 90.  Recommend DLA pursue this requirement as a proposal to all affected DSs, with more detailed documentation/justification for the requirement.	X	TM	4/8	Must use		

Syntax:
1.  G6201 R0103 -- At least one of G6201 or G6203 is required.
2.  G6201 P0102 -- If either G6201 or G6202 are present, then the others are required.
3.  G6203 P0304 -- If either G6203 or G6204 are present, then the others are required.

Federal Note:
Must use to identify the time of transaction set preparation.

G53	Maintenance Type	Pos: 0100	Max: 1
Detail - Mandatory
Loop: 0300	Elements: 1	

To identify the specific type of item maintenance 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	G5301	875	Maintenance Type Code
Description: Code identifying the specific type of item maintenance 
	Code 	Name                                                                                          _
 	001	Change
DLMS Note:   Use to identify UIT item data changes or corrections.

	M	ID	3/3	Must use		
DLMS Note:
Use in 2/G53/010 loop to identify the purpose of the transaction, the UIT item data requiring change or correction, and the changed or corrected data.  

G62	Date/Time	Pos: 0200	Max: 3
Detail - Optional
Loop: 0300	Elements: 2	

To specify pertinent dates and times 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	G6201	432	Date Qualifier
Description: Code specifying type of date 
	Code 	Name                                                                                          _
 	07	Effective Date
DLMS Note:   Use to identify the effective date of changes or corrections. 

 	BB	Transaction Control Date
DLMS Note:   Use to identify the date the transaction was entered on the component registry.

	X	ID	2/2	Must use		
	G6202	373	Date
Description: Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year 
	X	DT	8/8	Must use		

Syntax:
1.  G6201 R0103 -- At least one of G6201 or G6203 is required.
2.  G6201 P0102 -- If either G6201 or G6202 are present, then the others are required.
3.  G6203 P0304 -- If either G6203 or G6204 are present, then the others are required.

Federal Note:
Use this segment to identify dates associated with the transaction.
 
DLMS Note:
DLMS enhancement; see introductory DLMS note 4a. 

LX	Assigned Number	Pos: 0350	Max: 1
Detail - Mandatory
Loop: 0310	Elements: 1	

To reference a line number in a transaction set 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	LX01	554	Assigned Number
Description: Number assigned for differentiation within a transaction set 
Federal Note:    the first 2/LX/350 loop iteration, cite numeric 1.  In each subsequent loop iteration, increase incrementally by 1.

	M	N0	1/6	Must use		
Federal Note:
 as a counter to identify the number of 2/LX/350 loop iterations in the transaction set.

G39	Item Characteristics - Vendor's Selling Unit	
Pos: 0400	Max: 1
Detail - Optional
Loop: 0310	Elements: 4	

To identify a vendor's selling unit or to provide physical characteristics relative to a vendor's selling unit 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	G3902	235	Product/Service ID Qualifier
Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) 
Federal Note:   Following is a list of preferred codes.

DLMS Note:   1.  Use only one of codes A3, AN, FS, or MG to identify the item requiring changes or corrections.

2. For DLMS use, only the following codes are authorized.

	Code 	Name                                                                                          _
 	A3	Locally Assigned Control Number
DLMS Note:   Use to identify the local control number (LCN).

 	AN	Asset Number
DLMS Note:   Use to identify the management control number (MCN).

 	FS	National Stock Number
DLMS Note:   Must use the NSN when known.

 	MG	Manufacturer's Part Number
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.

	X	ID	2/2	Used		
	G3903	234	Product/Service ID
Description: Identifying number for a product or service 
	X	AN	1/48	Used		
	G3923	235	Product/Service ID Qualifier
Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) 
Federal Note:   Following is a list of preferred codes.

DLMS Note:   For DLMS use, only the following code(s) are authorized.

	Code 	Name                                                                                          _
 	ZB	Commercial and Government Entity (CAGE) Code
DLMS Note:   1.  Use with G3902 code MG touniquely identify a manufacturer's part number.

2.  DLMS enhancement; see introductory DLMS note 4a.

	X	ID	2/2	Used		
	G3924	234	Product/Service ID
Description: Identifying number for a product or service 
	X	AN	1/48	Used		

Syntax:
1.  G3901 R0102 -- At least one of G3901 or G3902 is required.
2.  G3902 P0203 -- If either G3902 or G3903 are present, then the others are required.
3.  G3905 P050607 -- If either G3905, G3906 or G3907 are present, then the others are required.
4.  G3906 P0607 -- If either G3906 or G3907 are present, then the others are required.
5.  G3908 P0809 -- If either G3908 or G3909 are present, then the others are required.
6.  G3910 P1011 -- If either G3910 or G3911 are present, then the others are required.
7.  G3912 P1213 -- If either G3912 or G3913 are present, then the others are required.
8.  G3914 P1415 -- If either G3914 or G3915 are present, then the others are required.
9.  G3918 P1819 -- If either G3918 or G3919 are present, then the others are required.
10.  G3923 P2324 -- If either G3923 or G3924 are present, then the others are required.
11.  G3925 P2526 -- If either G3925 or G3926 are present, then the others are required.

DLMS Note:
Use the 2/G39/040 loop to identify the item being changed or corrected.

N9	Reference Identification	Pos: 1510	Max: 10
Detail - Optional
Loop: 0310	Elements: 3	

To transmit identifying information as specified by the Reference Identification Qualifier 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	N901	128	Reference Identification Qualifier
Description: Code qualifying the Reference Identification 
Federal Note:   Following is a list preferred codes.

DLMS Note:   1.  Use only one of codes A3, MF, NS, TN, or X9 to identify the correct item identifying number

2. For DLMS use, only the following codes are authorized.

	Code 	Name                                                                                          _
 	A3	Assignment Number
DLMS Note:   Use to identify the new or corrected LCN.

 	MF	Manufacturers Part Number
DLMS Note:   1.  Use to identify the new or corrected manufacturer's part number.

2.  DLMS enhancement; see introductory DLMS note 4a.

 	NS	National Stock Number
DLMS Note:   Use to identify the new or corrected NSN.

 	TN	Transaction Reference Number
DLMS Note:   1.  Must use to identify the transaction number for each transaction.

2.  DLMS enhancement; see introductory DLMS note 4a.

 	X9	Internal Control Number
DLMS Note:   Use to identify the new or corrected MCN.

	M	ID	2/3	Must use		
	N902	127	Reference Identification
Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 
	X	AN	1/50	Used		
	N907	C040	Reference Identifier
Description: To identify one or more reference numbers or identification numbers as specified by the Reference Qualifier 
	O	Comp		Used		
		128	Reference Identification Qualifier
Description: Code qualifying the Reference Identification 
	Code 	Name                                                                                          _
 	W7	Commercial and Government Entity (CAGE) Code
DLMS Note:   1.  Use only with N901 code MF to uniquely identify a manufacturer's part number.

2.  DLMS enhancement; see introductory DLMS note 4a.

	M	ID	2/3	Must use		
		127	Reference Identification
Description: Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier 
	M	AN	1/50	Must use		

Syntax:
1.  N902 R0203 -- At least one of N902 or N903 is required.
2.  N906 C0605 -- If N906 is present, then N905 is required

Semantics:
1.	N906 reflects the time zone which the time reflects. 
2.	N907 contains data relating to the value cited in N902. 

Federal Note:
Must use multiple repititions to identify the correct item data and the transaction number.

N1	Name	Pos: 1560	Max: 1
Detail - Optional
Loop: 0311	Elements: 4	

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

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	N101	98	Entity Identifier Code
Description: Code identifying an organizational entity, a physical location, property or an individual 
Federal Note:   Following is a list of preferred codes.

DLMS Note:   1.  Use only one od codes KK or RL.

2.  For DLMS use, only the following codes are authorized.

	Code 	Name                                                                                          _
 	KK	Registering Party
DLMS Note:   Use to identify the registry, if applicable, to receive the UIT Data Change transaction.

 	QD	Responsible Party
DLMS Note:   1.  Use when changing or correcting the accountable organization.

2.  DLMS enhancement; see introductory DLMS note 4a.

 	RL	Reporting Location
DLMS Note:   Use only in UIT item data change reject to identify the reporting activity to receive the transaction.

 	ZA	Corrected Address
DLMS Note:   Use when changing or correcting the accountable organization.

	M	ID	2/3	Must use		
	N103	66	Identification Code Qualifier
Description: Code designating the system/method of code structure used for Identification Code (67) 
	Code 	Name                                                                                          _
 	1	D-U-N-S Number, Dun & Bradstreet
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.

 	9	D-U-N-S+4, D-U-N-S Number with Four Character Suffix
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.

 	10	Department of Defense Activity Address Code (DODAAC)
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.

 	33	Commercial and Government Entity (CAGE)
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.

 	M4	Department of Defense Routing Identifier Code (RIC)
DLMS Note:   1. The RIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS environment. Continued support of the RIC in a full DLMS environment will be assessed at a future date. Typically under the DLMS, the RIC will be replaced with a DoDAAC or a commercial identifier.

2. Future Streamlined data; see introductory DLMS note 4c.

 	UR	Uniform Resource Locator (URL)
DLMS Note:   DLMS enhancement; see introductory DLMS note 4a.
STAFFING NOTE:  DLA is including URL, along with RIC and DoDAAC, in DoD UIT-Phase 1 as possible address codes for transactional interface.

	X	ID	1/2	Used		
	N104	67	Identification Code
Description: Code identifying a party or other code 
	X	AN	2/80	Used		
	N106	98	Entity Identifier Code
Description: Code identifying an organizational entity, a physical location, property or an individual 
	Code 	Name                                                                                          _
 	TO	Message To
DLMS Note:   Must use with the 2/N101/156 code KK or RL to indicate the organization cited in N104 is receiving the transaction.

	O	ID	2/3	Used		

Syntax:
1.  N102 R0203 -- At least one of N102 or N103 is required.
2.  N103 P0304 -- If either N103 or N104 are present, then the others are required.

Comments:
1.	This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID Code" (N104) must provide a key to the table maintained by the transaction processing party. 
2.	N105 and N106 further define the type of entity in N101. 

Federal Note:
1.  Must usethe 2/N1/156 loop to identify the organization to receive the transaction.

2.  Use additional iterations to identify original and new or corrected accountable organizations.

G55	Item Characteristics - Consumer Unit	
Pos: 1650	Max: 1
Detail - Optional
Loop: 0312	Elements: 4	

To provide physical characteristics relative to a consumer unit 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	G5501	235	Product/Service ID Qualifier
Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) 
	Code 	Name                                                                                          _
 	SN	Serial Number
DLMS Note:   Use when changing or correcting UII data to identify the old UII.

	M	ID	2/2	Must use		
	G5502	234	Product/Service ID
Description: Identifying number for a product or service 
	M	AN	1/48	Must use		
	G5503	235	Product/Service ID Qualifier
Description: Code identifying the type/source of the descriptive number used in Product/Service ID (234) 
	Code 	Name                                                                                          _
 	RR	Replacement Product Number
DLMS Note:   Use when changing or correcting UII data to identify the new UII.

	X	ID	2/2	Used		
	G5504	234	Product/Service ID
Description: Identifying number for a product or service 
	X	AN	1/48	Used		

Syntax:
1.  G5503 P0304 -- If either G5503 or G5504 are present, then the others are required.
2.  G5505 P0506 -- If either G5505 or G5506 are present, then the others are required.
3.  G5507 P0708 -- If either G5507 or G5508 are present, then the others are required.
4.  G5509 P0910 -- If either G5509 or G5510 are present, then the others are required.
5.  G5511 P1112 -- If either G5511 or G5512 are present, then the others are required.
6.  G5514 P1415 -- If either G5514 or G5515 are present, then the others are required.
7.  G5523 P232425 -- If either G5523, G5524 or G5525 are present, then the others are required.
8.  G5526 P262728 -- If either G5526, G5527 or G5528 are present, then the others are required.
9.  G5529 P2930 -- If either G5529 or G5530 are present, then the others are required.

Semantics:
1.	G5521 indicates if the product is prepriced. Code "Y" indicates the product is prepriced. Code "N" indicates the product is not prepriced. 

Comments:
1.	G5516 is limited to 16 characters. 

DLMS Note:
Use to identify unique item identifier (UII) data changes.  Use multiple iterations to change multiple UIIs.

LM	Code Source Information	Pos: 1800	Max: 1
Detail - Optional
Loop: 0313	Elements: 1	

To transmit standard code list identification information 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	LM01	559	Agency Qualifier Code
Description: Code identifying the agency assigning the code values 
	Code 	Name                                                                                          _
 	DF	Department of Defense (DoD)
	M	ID	2/2	Must use		
Comments:
1.	LM02 identifies the applicable industry code list source information. 

Federal Note:
Must use this 2/LM/180 loop to identify coded information maintained in department or agency documentation.

LQ	Industry Code	Pos: 1900	Max: 100
Detail - Mandatory
Loop: 0313	Elements: 2	

Code to transmit standard industry codes 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	LQ01	1270	Code List Qualifier Code
Description: Code identifying a specific industry code list 
Federal Note:   Following is a list of preferred codes.

DLMS Note:   For DLMS use, only the following codes are authorized.

	Code 	Name                                                                                          _
 	0	Document Identification Code
DLMS Note:   1.  The DLSS DI Code is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS environment.  Continued support of the DI Code in a full DLMS environment will be assessed at a future date.

2.  Future streamlined data; see introductory DLMS note 4c.

 	A9	Supplemental Data
DLMS Note:   1. Use to identify supplemental address/data.

2. During the DLSS/DLMS transition, this field will
be used to perpetuate/populate the DLSS
Supplemented Address (SUPAAD) field. During this time, field size is restricted to 6 positions; see introductory DLMS note 4d.

3. Expanded use of this field for supplemental data
with out size restriction is a DLMS enhancement; see introductory DLMS note 4a.

4. Under full DLMS, the requirement to pass activity address information within the supplement data field will be streamlined. Activity address data previously contained in the SUPAAD will bereflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 4c.

 	AJ	Utilization Code
DLMS Note:   1. Under DLSS, this is the first position of the document serial number.

2. DLMS enhancement; see introductory DLMS note 4a.

 	AL	Special Requirements Code
Federal Note:   Use to identify the precedence, special handling, and processing requirements.

DLMS Note:   1. Under DLSS, this is carried in the required delivery date field.

2. DLMS enhancement; see introductory DLMS note 4a.

 	ABR	Assigned by Receiver
DLMS Note:   Use for UIT Error Transaction Reject Codes.  An ANSI Data Maintenance Action has been prepared to obtain a unique qualifier for UIT Error Transaction Reject Codes and will be available in a future release.
STAFFING NOTE:  DLMSO will release a PDC for UIT Error Transaction Reject Codes.   DLA Comment:  UIT-specific error conditions are still to be identified by UIT trading partners.  Many existing MILSTRAP small arms error codes are not currently being used; therefore, DLA believes perpetuating existing MILSTRAP codes would confuse users.

 	ABS	Assigned by Sender
DLMS Note:   Use for UIT Transaction Codes.  An ANSI Data Maintenance Action has been prepared to obtain a unique qualifier for UIT Transaction Codes and will be available in a future release.
STAFFING NOTE:  DLMSO will release a PDC for UIT Transaction Codes.

 	COG	Cognizance Symbol
DLMS Note:   Use to identify the material cognizance symbol (COG) of the end item.  Indicate NSL for non-stock numbered listed items.  This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.

 	IMC	Item Management Code
DLMS Note:   Use to identify the Item Management Code (IMC) for integrated material management.  This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.

 	MCC	Material Control Code
DLMS Note:   Use to identify the Material Control Code (MCC) for special inventory reporting. This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.

 	SMI	Special Material Identification Code
DLMS Note:   Use to identify the Special Material Identification Code (SMIC) for an end item.  This is a Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.

	O	ID	1/3	Used		
	LQ02	1271	Industry Code
Description: Code indicating a code from a specific industry code list 
	X	AN	1/30	Used		

Syntax:
1.  LQ01 C0102 -- If LQ01 is present, then LQ02 is required

Federal Note:
Use to identify codes, as appropriate, consistent with management information requirements.

SE	Transaction Set Trailer	Pos: 2000	Max: 1
Detail - Mandatory
Loop: N/A	Elements: 2	

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

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	SE01	96	Number of Included Segments
Description: Total number of segments included in a transaction set including ST and SE segments 
	M	N0	1/10	Must use		
	SE02	329	Transaction Set Control Number
Description: Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set 
Federal Note:   Cite the same number as the one cited in ST02.

	M	AN	4/9	Must use		
Comments:
1.	SE is the last segment of each transaction set.