140	Product Registration	
	Functional Group=WA	

This Draft Standard for Trial Use contains the format and establishes the data contents of the Product Registration Transaction Set (140) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to specify the manufacturer, seller, secondary warranter, and purchaser or lessee of the product. It can specify the date the product was sold, delivered, and placed in service as well as identify the product model and serial numbers. It can specify the class of service expected from this individual sale, for example: industrial, commercial, or household. This registration information can be used to divide sales commissions among sales associates or attribute license fees to the proper manufacturer. It can be used to submit many product registrations at one time to one receiving organization. 
Staffing Notes are identified in red text/yellow highlight.

STAFFING NOTE:  The Small Arms Reporting transaction, DS 140A was used as the basis for development of DS 140B, UIT Reporting.  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 140A are identified in blue text on pages:  1, 4, 7, 8, 10, 17, 20, 23, and 29.
Notes:
1/0200 BGN02 is used as the initial reference identifier for this transaction. BGN03 defines the date of this registration
            transaction. Normally BGN04 and BGN05 would not be used in this transaction. BGN01 is normally set to 00 to indicate
            that this is an original registration. Product registration is normally a by-product of a sale.
1/0300 The N9 segment can provide a reference to a previous registration transaction. For example, this could be a replacement of
            a previous registration transaction.
1/0400 The N1 loop defines the party submitting the product registration, usually the seller of the product rather than the
            customer, and the party who maintains the registration database, usually the manufacturer of the product. The N1 loop
            also can be used to specify the product's distributor.
2/0100 Each iteration of the LX loop is used to group one or more products that are being registered to one individual or
            organization.
2/0150 The REF segment is used to identify the individual registration number. It can include the data element 128, code value
            Q8, "Registration Number."
2/0200 The N1 loop is used to identify the individual or organization responsible for the registration. This could be the purchaser,
             the lessee, the operator, etc. This is the party registered to be notified if a product recall is required. Successive iterations
            could identify other individuals and organizations who are involved in some manner. It also could be used to specify if the
            product is to be installed or housed at a location that is different than that listed for the registration. An additional use of
            the N1 loop has been requested to be able to include the salesperson who sold the product or service contract and the
           service manager who would be responsible for servicing the product.
2/0600 The PER segment is used to provide an individual's or department's name for a particular support function and, if desired,
            their communication number for a phone, electronic mail, etc.
2/0800 The REF segment could be used to identify the item into or onto which this product being warranted will be residing. For
            example, when a controller is attached to a numerically controlled machine tool, part of the registration could include
            information about the machine tool. The machine tool could be identified with multiple occurrences of the REF segment.
            A similar situation would be if an engine were being replaced in a heavy duty truck. The REF segment could then be used
            to specify the vehicle.
2/0900 There is a separate LIN segment for each product included in this sale represented by the single iteration of the LX loop.
            The LIN segment will contain the product's model number and serial number in data element 234-235 combinations. The
            other pairs can be used to provide other information about the product.
2/1000 The PID segment can be used to provide additional information regarding the product. However, it seldom will be
            required. When it is used, PID06, data element 752, is not required.
2/1100 The QTY segment is used to reflect the quantity of items that do not have a serial number. QTY01 will have a discrete
            quantity qualifier of 01. For all items with a serial number, the value to be used is either explicitly or implicitly set to one.
2/1200 The DTM segment in the LIN loop can be used to specify the dates that are significant to the registration such as delivery,
            installation, placed in service, failed, brought in for service, etc.
2/1300 The REF segment can identify information about the product that was not able to be coded in the preceding segments. For
             example, it can be used to specify the warranty coverage code and the warranty registration number.
2/1400 The N1 loop within the LIN loop provides the same capabilities for the single product as the N1 loop above in the LX
            loop provides for the entire sale.
2/1800 The PER segment is used to provide an individual's or department's name or functional area and, if desired, their communication                    
            number for a phone, electronic mail, etc.
2/1900 The PSC loop in the LIN loop refers to the warranty or service contract for the entire product described by the LIN
            segment. If special operating conditions that could affect the registration are to be noted, such as a household product
            being used commercially, this would be placed in the PSC segment. Unless noted to the contrary, it will be assumed that
            the product will be used in its most normal capacity. For example, a kitchen appliance, unless specifically stated to the
            contrary, will be assumed to be used within a household. The PSC loop also may be used when a for fee registration is
            being specified, such as an extended warranty or service contract. The PSC segment also may be used without the other
            segments in the loop to describe conditions of a standard, free warranty registration. The PSC segment is used to specify
            the period for the warranty or service contract. There may be other measures of service life of a product such as operation
            counter, an odometer to measure mileage of a vehicle, or a clock that measures operational hours.
2/2000 The SSS special service segment is used in conjunction with the PSC segment to add any extra services to be specified
            within the service contract. For example, there may be a clause for 24 hour service or a guaranteed service response of no
            more than so many hours.
2/2100 The repeated use of the AMT segment within the PSC loop allows the total amount of the contract to be specified as well
            as any special conditions on the amount.
2/2200 The CUR segment is only required when the service contract is to be paid across national boundaries.
2/2300 The ITA segment would be used in those special cases where the normal service contract cost does not apply. For
            example, in fleet sales, the product and its service contract may be bought from a local dealer, but because one purchaser
            buys many of them from several dealers spread across a geographic area, they get a discount or extra service on the
            purchase.
2/2400 The TXI, Tax Information segment, can be used to list the sales tax paid on a service contract. Also it identifies the taxing
            authority.
2/2500 The ITD segment is to be used in the case where the service contract is to be paid at regular intervals over the life of the
            contract. For example, the payments might be monthly or quarterly.
2/2600 The N9 segment within the PSC loop can contain a unique code identifying the terms of the service contract. For example,
            repair order number or contract number as preassigned by the product's manufacturer. It also can be used to record the
            customer's method of payment for a service contract. It then would be used to contain the check number or charge card
            number. The expiration date on the charge card does not need to be recorded as the computer program entering the
            transaction only has to check that the card has not expired. N903 will be able to contain the name of the issuer of the card.
2/2700 The SLN loop is used to describe subassemblies or parts within an assembly that may be covered by separate warranty
            conditions. A pair of data elements 234 and 235 in the SLN segment will be used to contain the serial number, lot
            number, model number, etc. of the subassembly being registered. All the loops and segments within the SLN loop
            perform the same functions for the subassemblies as their counterparts above did for the product.
2/3200 The N1 loop within the SLN loop provides the same capabilities for the single product as the N1 loop above in the LX
            loop provides for the entire sale. However, the assembly whose information is in the N1 loop is part of the product
            specified in the SLN loop.
2/3600 The PER segment is used to provide an individual's or department's name or functional area and, if desired, their
            communication number for a phone, electronic mail, etc.
Federal Note:
1. Organizations use this transaction set to report events regarding the custody or status of unique items tracking (UIT) items, inquire into the custody or status of (UIT) items, reconcile (UIT) items reconciliation reports, follow up on unacknowledged rejections, and respond to rejections of (UIT) items reconciliation reports.

2. Use one occurrence of this transaction set to transmit single or multiple transactions of the same type.

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 (UIT) information to one or more organizations.

2. 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.

3. 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 140B, Unique Item Tracking (UIT) Reporting 

Heading:	
	Pos	Id	Segment Name	Req	Max Use	Repeat	Notes	Usage											
	0100	ST	Transaction Set Header	M	1			Must use											
	0200	BGN	Beginning Segment	M	1		N1/0200	Must use											
*	0300	N9	Reference Identification	O	>1		N1/0300	Not used											
																			
 LOOP ID - N1			3													
	0400	N1	Name	M	1		N1/0400	Must use											
*	0500	N2	Additional Name Information	O	2			Not used											
*	0600	N3	Address Information	O	3			Not used											
*	0700	N4	Geographic Location	O	1			Not used											
*	0800	REF	Reference Identification	O	2			Not used											
	0900	PER	Administrative Communications Contact	O	2			Used											
Detail:	
	Pos	Id	Segment Name	Req	Max Use	Repeat	Notes	Usage											
																			
 LOOP ID - LX			>1													
	0100	LX	Assigned Number	M	1		N2/0100	Must use											
	0150	REF	Reference Identification	O	>1		N2/0150	Used											
																			
 LOOP ID - N1			>1													
	0200	N1	Name	M	1		N2/0200	Must use											
*	0300	N2	Additional Name Information	O	2			Not used											
*	0400	N3	Address Information	O	3			Not used											
*	0500	N4	Geographic Location	O	1			Not used											
*	0600	PER	Administrative Communications Contact	O	>1		N2/0600	Not used											
*	0700	DTM	Date/Time Reference	O	1			Not used											
*	0800	REF	Reference Identification	O	>1		N2/0800	Not used											
																			
 LOOP ID - LM			>1													
	0860	LM	Code Source Information	O	1			Used											
	0870	LQ	Industry Code	M	100			Must use											
																			
 LOOP ID - LIN			>1													
	0900	LIN	Item Identification	M	1		N2/0900	Must use											
*	1000	PID	Product/Item Description	O	>1		N2/1000	Not used											
	1100	QTY	Quantity	O	1		N2/1100	Used											
	1200	DTM	Date/Time Reference	O	>1		N2/1200	Used											
	1300	REF	Reference Identification	O	>1		N2/1300	Used											
																			
 LOOP ID - N1			>1													
	1400	N1	Name	O	1		N2/1400	Used											
*	1500	N2	Additional Name Information	O	2			Not used											
*	1600	N3	Address Information	O	3			Not used											
*	1700	N4	Geographic Location	O	1			Not used											
*	1800	PER	Administrative Communications Contact	O	>1		N2/1800	Not used											
																			
 LOOP ID - PSC			>1													
*	1900	PSC	Product Service Contract	O	1		N2/1900	Not used											
*	2000	SSS	Special Services	O	>1		N2/2000	Not used											
*	2100	AMT	Monetary Amount	O	>1		N2/2100	Not used											
*	2200	CUR	Currency	O	1		N2/2200	Not used											
*	2300	ITA	Allowance, Charge or Service	O	1		N2/2300	Not used											
*	2400	TXI	Tax Information	O	1		N2/2400	Not used											
*	2500	ITD	Terms of Sale/Deferred Terms of Sale	O	1		N2/2500	Not used											
*	2600	N9	Reference Identification	O	>1		N2/2600	Not used											
																			
 LOOP ID - SLN			>1													
*	2700	SLN	Subline Item Detail	O	1		N2/2700	Not used											
*	2800	PID	Product/Item Description	O	>1			Not used											
*	2900	QTY	Quantity	O	1			Not used											
*	3000	DTM	Date/Time Reference	O	>1			Not used											
*	3100	REF	Reference Identification	O	>1			Not used											
																			
 LOOP ID - N1			>1													
*	3200	N1	Name	O	1		N2/3200	Not used											
*	3300	N2	Additional Name Information	O	2			Not used											
*	3400	N3	Address Information	O	3			Not used											
*	3500	N4	Geographic Location	O	1			Not used											
*	3600	PER	Administrative Communications Contact	O	>1		N2/3600	Not used											
																			
 LOOP ID - PSC			>1													
*	3700	PSC	Product Service Contract	O	1			Not used											
*	3800	SSS	Special Services	O	>1			Not used											
*	3900	AMT	Monetary Amount	O	>1			Not used											
*	4000	CUR	Currency	O	1			Not used											
*	4100	ITA	Allowance, Charge or Service	O	1			Not used											
*	4200	TXI	Tax Information	O	1			Not used											
*	4300	ITD	Terms of Sale/Deferred Terms of Sale	O	1			Not used											
*	4400	N9	Reference Identification	O	>1			Not used											
																			
 LOOP ID - LM			>1													
	4500	LM	Code Source Information	O	1			Used											
	4600	LQ	Industry Code	M	100			Must use											
	4700	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 
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. 

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                                                                                          _
 	140	Product Registration
	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		

BGN	Beginning Segment	Pos: 0200	Max: 1
Heading - Mandatory
Loop: N/A	Elements: 6	

To indicate the beginning of a transaction set 

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. 

Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	BGN01	353	Transaction Set Purpose Code
Description: Code identifying purpose of transaction set 
	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 transaction 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).

	M	DT	8/8	Must use		
	BGN04	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. Express the originating activity's time in UTC.

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

	X	TM	4/8	Must use		
	BGN07	640	Transaction Type Code
Description: Code specifying the type of transaction 
Federal Note:   Following is a list of preferred codes.

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

	Code 	Name                                                                                          _
 	G3	Confirmation Response
DLMS Note:   Use when the transaction set contains a UIT shipment report.  Use with BGN08, code T, when the transaction set contains a UIT item report inquiry.  
STAFFING NOTE:  DLA plans to implement use of DS 945A to report shipment of UIT items; however, there may still be instances in which a stand alone visibility shipment may be used (e.g., DLSS interface; customer input control screen (CICS) to CICS, etc.)

 	RP	Reporting
DLMS Note:   Use when the transaction set contains a UIT receipt report.  For interim use, DS 140B identify informational receipt report for UIT items until such time as Distribution Standard System (DSS) implements the full suite of DLMS transaction to include DS 527R accountable receipt transaction.  Use with BGN08, code T, when the transaction set contains a UIT item report inquiry.   
STAFING NOTE:  DSS UIT implementation Phase 1 contains a limited number of DLMS transactions and excludes accountable (balance affecting ) transactions.

 	RQ	Request
DLMS Note:   Use to request Sight Verification of a UIT program item.  Use with BGN08, code T, when the transaction set contains a UIT item report inquiry.  An ANSI Data Maintenance Action has been prepared to obtain a unique qualifier for Sight Verification Request and will be available in a future release.  Sight Verification functionality is scheduled for DSS UIT Phase 2.  

 	W4	Weapons Control Report
DLMS Note:   Use when the transaction set contains a UIT item report. Use with BGN08, code T, when the transaction set contains a UIT item report inquiry.   An ANSI Data Maintenance Action has been prepared to obtain a unique qualifier for UIT Item Control Report will be available in a future release. 

 	W5	Weapons Control Report Reconciliation
DLMS Note:   Use when the transaction set contains UIT reconciliation report.  An ANSI Data Maintenance Action has been prepared to obtain a unique qualifier for UIT Item Report Reconciliation will be available in a future release. 

Use as follows:  as an original reconciliation report; or as a rejection of a reconciliation report (use with BGN08 code U); or as a correction to a previously submitted report which was rejected by the receiving registry.

	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                                                                                          _
 	T	Status Query
DLMS Note:   Use in conjunction with BGN07, codes G3, RP, RQ, or W4 when the transaction set contains a UIT program report inquiry.

 	U	Reject
DLMS Note:   Use in conjunction with BGN07 code W5 when the transaction set contains a rejection of a UIT reconciliation report.

 	51	Complete
DLMS Note:   Use in conjunction with BGN07, code, RQ to use transaction set to report completion of UIT sight verification.   An ANSI Data Maintenance Action has been prepared to obtain a unique qualifier for Sight Verification Complete and will be available in a future release.  Sight Verification functionality is scheduled for DSS UIT Phase 2.  

 	AC	Acknowledge
DLMS Note:   Use to identify the resubmission of a reject transaction for which a response is not received within the allotted time frame. When using, cite code W5 in BGN07.

	O	ID	1/2	Used		

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

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

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/040 to identify the organization originating the transaction set.
 
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:   1. Use only one of the following codes.

2. Following is a list of preferred codes.

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

	Code 	Name                                                                                          _
 	B6	Registering Parent Party
DLMS Note:   Use to identify the DoD Small Arms Serialization Program registry.

 	KK	Registering Party
DLMS Note:   Use to identify the component registry.

 	RL	Reporting Location
DLMS Note:   Use to identify the reporting activity.

 	SF	Ship From
DLMS Note:   Use in UIT item reports of receipt to identify the activity which shipped UIT items.

 	ST	Ship To
DLMS Note:   Use in UIT item reports of shipment or inquiries about UIT item reports of shipment to identify the ship-to 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 3a. 

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

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

 	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 3c.

 	UR	Uniform Resource Locator (URL)
DLMS Note:   DLMS enhancement; see introductory DLMS note 3a.
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 
Federal Note:   Must use with the appropriate 1/N101/040 code to indicate the organization is originating the transaction set.

	Code 	Name                                                                                          _
 	FR	Message From
Federal Note:   Must use with the appropriate 1/N101/040 code to indicate the organizations cited in N104 is originating the transaction set.

	O	ID	2/3	Must use		

PER	Administrative Communications Contact	
Pos: 0900	Max: 2
Heading - Optional
Loop: N1	Elements: 8	

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

Syntax:
1.  PER03 P0304 -- If either PER03 or PER04 are present, then the others are required.
2.  PER05 P0506 -- If either PER05 or PER06 are present, then the others are required.
3.  PER07 P0708 -- If either PER07 or PER08 are present, then the others are required.

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

2. Use to identify a POC and multiple communication numbers.  When using multiple repetitions to identify different communication numbers for a single POC, repeat the name cited in PER02.

Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	PER01	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 in the first repetition to identify the primary point of contact (POC) and their primary communication number.

	M	ID	2/2	Must use		
	PER02	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 as POC.  Include blank spaces between name components and periods after initials.  Do not include NMN or NM1 when a middle initial is not available.

	O	AN	1/60	Must use		
	PER03	365	Communication Number Qualifier
Description: Code identifying the type of communication number 
Federal Note:   1.  Use to identify the preferred method of communications in PER03/04.  Use PER05/06 and PER07/08 to identify additional communications numbers.  Use additional repetitions of the PER segment to identify more than three communications numbers.

2.  Do not include blank spaces or dashes between numbers.

	Code 	Name                                                                                          _
 	AU	Defense Switched Network
 	EM	Electronic Mail
 	FX	Facsimile
 	IT	International Telephone
Federal Note:   Include country and city code.

 	TE	Telephone
 	TL	Telex
 	TX	TWX
	X	ID	2/2	Must use		
	PER04	364	Communication Number
Description: Complete communications number including country or area code when applicable 
	X	AN	1/256	Must use		
	PER05	365	Communication Number Qualifier
Description: Code identifying the type of communication number 
Federal Note:   1. Use to identify an alternate, or secondary, communications number which can be used to contact the entity identified in PER01. 

2. Do not include blank spaces or dashes between numbers.

	Code 	Name                                                                                          _
 	AU	Defense Switched Network
 	EM	Electronic Mail
 	EX	Telephone Extension
Federal Note:   Use immediately following code AU, IT, or TE to identify telephone extension.

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

 	TE	Telephone
 	TL	Telex
 	TX	TWX
	X	ID	2/2	Used		
	PER06	364	Communication Number
Description: Complete communications number including country or area code when applicable 
	X	AN	1/256	Used		
	PER07	365	Communication Number Qualifier
Description: Code identifying the type of communication number 
Federal Note:   1. Use to identify an alternate, or secondary, communications number which can be used to contact the entity identified in PER01. 

2. Do not include blank spaces or dashes between numbers.

	Code 	Name                                                                                          _
 	AU	Defense Switched Network
 	EM	Electronic Mail
 	EX	Telephone Extension
Federal Note:   Use immediately following code AU, IT, or TE to identify telephone extension.

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

 	TE	Telephone
 	TL	Telex
 	TX	TWX
	X	ID	2/2	Used		
	PER08	364	Communication Number
Description: Complete communications number including country or area code when applicable 
	X	AN	1/256	Used		

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

To reference a line number in a transaction set 
Federal Note:
Must use as a counter to identify the number of 2/LX/010 loop iterations in the 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:   In the first 2/LX/010 loop iteration cite numeric 1. In each subsequent loop iteration increase incrementally by 1.

	M	N0	1/6	Must use		

REF	Reference Identification	Pos: 0150	Max: >1
Detail - Optional
Loop: LX	Elements: 3	

To specify identifying information 

Syntax:
1.  REF02 R0203 -- At least one of REF02 or REF03 is required.

Semantics:
1.	REF04 contains data relating to the value cited in REF02. 

Federal Note:
Must use to identify the transaction number and suffix associated with the transaction.
 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	REF01	128	Reference Identification Qualifier
Description: Code qualifying the Reference Identification 
	Code 	Name                                                                                          _
 	TN	Transaction Reference Number
	M	ID	2/3	Must use		
	REF02	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	Must use		
	REF04	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                                                                                          _
 	W8	Suffix
DLMS Note:   Use with code TN to identify the transaction number suffix.

	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		

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

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

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. 

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:   For DLMS use, only the following codes are authorized.

	Code 	Name                                                                                          _
 	B6	Registering Parent Party
DLMS Note:   Use to identify the DoD Small Arms Serialization Program central registry.

 	KK	Registering Party
DLMS Note:   Use to identify the component registry.

 	QD	Responsible Party
DLMS Note:   Use to identify the accountable organization responsible for the UIT items.  Identify the organization that last possessed the UIT item when transmitting UIT reports of shipment.  Identify the new accountable organization when changing or correcting the accountable activity.

 	RL	Reporting Location
DLMS Note:   Use to identify reporting activity when different from accountable activity.

 	SF	Ship From
DLMS Note:   Use in UIT item reports of receipt to identify the activity which shipped UIT items.

 	ST	Ship To
DLMS Note:   Use in UIT reports of shipment or inquiries about UIT reports of shipment to identify the ship-to 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 3a.

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

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

 	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 3c.

 	UR	Uniform Resource Locator (URL)
DLMS Note:   DLMS enhancement; see introductory DLMS note 3a.
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                                                                                          _
 	TO	Message To
Federal Note:   Use with the appropriate 2/N101/020 codes to indicate the organizations cited in N104 are receiving the transaction.

	O	ID	2/3	Used		

LM	Code Source Information	Pos: 0860	Max: 1
Detail - Optional
Loop: LM	Elements: 2	

To transmit standard code list identification information 
Comments:
1.	LM02 identifies the applicable industry code list source information. 

Federal Note:
Must use the 2/LM/086 loop to identify coded information maintained in department or agency documentation.
 
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		
	LM02	822	Source Subqualifier
Description: A reference that indicates the table or text maintained by the Source Qualifier 
	O	AN	1/15	Used		

LQ	Industry Code	Pos: 0870	Max: 100
Detail - Mandatory
Loop: LM	Elements: 2	

Code to transmit standard industry codes 

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

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

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 3c.

 	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 3d.

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

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 be reflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 3c.

 	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 3a.

 	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 3a.

 	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	Must use		
	LQ02	1271	Industry Code
Description: Code indicating a code from a specific industry code list 
	X	AN	1/30	Must use		

LIN	Item Identification	Pos: 0900	Max: 1
Detail - Mandatory
Loop: LIN	Elements: 4	

To specify basic item identification data 

Syntax:
1.  LIN04 P0405 -- If either LIN04 or LIN05 are present, then the others are required.
2.  LIN06 P0607 -- If either LIN06 or LIN07 are present, then the others are required.
3.  LIN08 P0809 -- If either LIN08 or LIN09 are present, then the others are required.
4.  LIN10 P1011 -- If either LIN10 or LIN11 are present, then the others are required.
5.  LIN12 P1213 -- If either LIN12 or LIN13 are present, then the others are required.
6.  LIN14 P1415 -- If either LIN14 or LIN15 are present, then the others are required.
7.  LIN16 P1617 -- If either LIN16 or LIN17 are present, then the others are required.
8.  LIN18 P1819 -- If either LIN18 or LIN19 are present, then the others are required.
9.  LIN20 P2021 -- If either LIN20 or LIN21 are present, then the others are required.
10.  LIN22 P2223 -- If either LIN22 or LIN23 are present, then the others are required.
11.  LIN24 P2425 -- If either LIN24 or LIN25 are present, then the others are required.
12.  LIN26 P2627 -- If either LIN26 or LIN27 are present, then the others are required.
13.  LIN28 P2829 -- If either LIN28 or LIN29 are present, then the others are required.
14.  LIN30 P3031 -- If either LIN30 or LIN31 are present, then the others are required.

Semantics:
1.	LIN01 is the line item identification 

Comments:
1.	See the Data Dictionary for a complete list of IDs. 
2.	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. 

Federal Note:
Must use this 2/LIN/090 loop to identify the material unique item identifier (UII) data and date information on UIT items. 

 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	LIN02	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 UIT item.  Must use National Stock Number (NSN) when known.

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).

 	F4	Series Identifier
DLMS Note:   Use to identify the manufacturer's series number of the end item.

 	FS	National Stock Number
 	MG	Manufacturer's Part Number
 	MN	Model Number
DLMS Note:   Use to identify the manufacturer's model number of the end item.

 	SN	Serial Number
DLMS Note:   Use to identify the manufacturer's serial number of the end item.

	M	ID	2/2	Must use		
	LIN03	234	Product/Service ID
Description: Identifying number for a product or service 
	M	AN	1/48	Must use		
	LIN04	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 the preferred code(s).

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

	Code 	Name                                                                                          _
 	ZB	Commercial and Government Entity (CAGE) Code
DLMS Note:   Use with LIN02 code MG to uniquely identify the manufacturer's part number.

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

QTY	Quantity	Pos: 1100	Max: 1
Detail - Optional
Loop: LIN	Elements: 4	

To specify quantity information 

Syntax:
1.  QTY02 R0204 -- At least one of QTY02 or QTY04 is required.
2.  QTY02 E0204 -- Only one of QTY02 or QTY04 may be present.

Semantics:
1.	QTY04 is used when the quantity is non-numeric. 

DLMS Note:
Use to report the quantity of items that do not have a unique item identifier.
STAFFING NOTE:  This use is consistent with the ANSI ASC X12 note on page 1:  “2/1100 The QTY segment is used to reflect the quantity of items that do not have a serial number. QTY01 will have a discrete quantity qualifier of 01.” 
 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	QTY01	673	Quantity Qualifier
Description: Code specifying the type of quantity 
All valid standard codes are used.

01	Discrete Quantity
	M	ID	2/2	Must use		
	QTY02	380	Quantity
Description: Numeric value of quantity 
	X	R	1/15	Used		

DTM	Date/Time Reference	Pos: 1200	Max: >1
Detail - Optional
Loop: LIN	Elements: 2	

To specify pertinent dates and times 

Syntax:
1.  DTM02 R020305 -- At least one of DTM02, DTM03 or DTM05 is required.
2.  DTM04 C0403 -- If DTM04 is present, then DTM03 is required
3.  DTM05 P0506 -- If either DTM05 or DTM06 are present, then the others are required.

Federal Note:
Use to identify dates associated with UIT items shipments, receipts and receipt inquiries.
 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	DTM01	374	Date/Time Qualifier
Description: Code specifying type of date or time, or both date and time 
Federal Note:   Following is the list of preferred codes.

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

	Code 	Name                                                                                          _
 	011	Shipped
DLMS Note:   Use to indicate the UIT items shipment date.

 	050	Received
DLMS Note:   Use to indicate the UIT items receipt date.

 	097	Transaction Creation
DLMS Note:   Use to indicate the date of transaction preparation.

 	598	Rejected
DLMS Note:   Use to indicate the date of transaction rejection.

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

REF	Reference Identification	Pos: 1300	Max: >1
Detail - Optional
Loop: LIN	Elements: 2	

To specify identifying information 

Syntax:
1.  REF02 R0203 -- At least one of REF02 or REF03 is required.

Semantics:
1.	REF04 contains data relating to the value cited in REF02. 

Federal Note:
Must use at least one repetition to identify unique item identifier (UII) data for UIT items.
 
Element Summary:

	   Ref  _ 	 Id_ 	                                               Element Name                                            _	Req	Type	Min/Max	 Usage_		
	REF01	128	Reference Identification Qualifier
Description: Code qualifying the Reference Identification 
Federal Note:   Following is the preferred code(s). 

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

	Code 	Name                                                                                          _
 	SE	Serial Number
DLMS Note:   Use to identify the UII.

	M	ID	2/3	Must use		
	REF02	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	Must use		

N1	Name	Pos: 1400	Max: 1
Detail - Optional
Loop: N1	Elements: 3	

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

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:
Use to identify the manufacturer of the UIT item(s) if duplicate UIIs are assigned to the same item identified in 2/LIN/090.
 
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 
	Code 	Name                                                                                          _
 	MF	Manufacturer of Goods
	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                                                                                          _
 	33	Commercial and Government Entity (CAGE)
	X	ID	1/2	Must use		
	N104	67	Identification Code
Description: Code identifying a party or other code 
	X	AN	2/80	Must use		

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

To transmit standard code list identification information 
Comments:
1.	LM02 identifies the applicable industry code list source information. 

Federal Note:
1. Use the 2/LM/450 loop to identify coded information maintained in department agency documentation.

2. Use the 2/LM/450 loop for reject reports and resubmissions, but only when the reject code varies among UIIs reported for the UIT item.

3. Use only one iteration of the 2/LM/450 loop for each iteration of the 2/LIN/090 loop.

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		

LQ	Industry Code	Pos: 4600	Max: 100
Detail - Mandatory
Loop: LM	Elements: 2	

Code to transmit standard industry codes 

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

Federal Note:
1.  Must use to identify codes, as appropriate, consistent with management information requirements.

2.  Use only one repetition for each iteration of the 2/LIN/090 loop.
 
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                                                                                          _
 	79	Priority Designator Code
DLMS Note:   Recommend using in all requisitions.

 	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 3d.

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

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 be reflected exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 3c.

 	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 3a.

 	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 3a.

 	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

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

SE	Transaction Set Trailer	Pos: 4700	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) 
Comments:
1.	SE is the last segment of each transaction set. 

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