DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

004030F650C1CA05 1 February 24, 2022

650 Maintenance Service Order

Functional Group=MO

Purpose: This Draft Standard for Trial Use contains the format and establishes then data contents of the Maintenance Service Order

Transaction Set (650) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set provides a uniform,

singular medium for the exchange of maintenance related information among organizations involved in the reporting, requesting, scheduling,

planning, estimating, coordinating and performing of maintenance actions. It provides the structure to convey maintenance-related information,

including maintenance action directives, maintenance actions, cost estimates, maintenance action assignments, maintenance action status,

and completion reports. This transaction set can be used in a bi-directional environment alone or in conjunction with the Project Schedule

Reporting Transaction Set (806) to link schedule and maintenance action information as well as with the Specifications/Technical Information

Transaction Set (841) to link maintenance-related, media independent, technical data.

DLMS Note:

1. This transaction set is used by the Assembly Activity to notify the Assembly Manager that packing has been completed at the Assembly

Activity for the designated component within the specified parameters.

a. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit

Conversion Table and the Transportation Mode of Shipment Conversion Table which can be found on the Defense Enterprise Data

Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS.

2. This DLMS IC is an enhancement over the current Defense Logistics Standard System (DLSS), and provides functionality not available in

the DLSS. This DLMS IC supports functionality of the non-DLSS C-series Document Identifier Code C2F, Component Packing Confirmation.

3. This DLMS Implementation Convention (IC) 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 DEDSO prior to use.

b. Data which is retained in the DLMS for a transition period to support transaction conversion in a mixed DLSS(and non-DLSS

C-series)/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components may coordinate

with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment. 

c. Data elements which have an expanded field size above existing DLSS ( or non-DLSS C-series) capability which may not be supported

by the recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

4. This revision to the DLMS IC incorporates Proposed DLMS Change (PDC) and Approved DLMS Change (ADC) listed. PDCs/ADCs are

available from the DEDSO Web site http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

- ADC 145, New DLMS Supplement (DS) and Federal Implementation Convention 650C, Component Packing Confirmation in Support of

Medical Requirements (Supply)

- ADC 189, Revise DLMS Supplement (DS) 650C, Component Packing Confirmation, to Allow for Functionality of Decimal Capability in

Quantity Packed

- ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on June 26, 2014

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 21, 2016

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

August 09, 2018

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on February 24, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

1. This transaction set is used by the Assembly Activity to notify the Assembly Manager that packing has been completed at the Assembly

Activity for the designated component within the specified parameters.

a. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit

Conversion Table and the Transportation Mode of Shipment Conversion Table which can be found on the Defense Enterprise Data

Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS.

2. This DLMS IC is an enhancement over the current Defense Logistics Standard System (DLSS), and provides functionality not available in

the DLSS. This DLMS IC supports functionality of the non-DLSS C-series Document Identifier Code C2F, Component Packing Confirmation.

3. This DLMS Implementation Convention (IC) 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 DEDSO prior to use.

b. Data which is retained in the DLMS for a transition period to support transaction conversion in a mixed DLSS(and non-DLSS

C-series)/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components may coordinate

with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment. 

c. Data elements which have an expanded field size above existing DLSS ( or non-DLSS C-series) capability which may not be supported

by the recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

4. This revision to the DLMS IC incorporates Proposed DLMS Change (PDC) and Approved DLMS Change (ADC) listed. PDCs/ADCs are

available from the DEDSO Web site http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

- ADC 145, New DLMS Supplement (DS) and Federal Implementation Convention 650C, Component Packing Confirmation in Support of

Medical Requirements (Supply)

- ADC 189, Revise DLMS Supplement (DS) 650C, Component Packing Confirmation, to Allow for Functionality of Decimal Capability in

Quantity Packed

- ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on June 26, 2014

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 21, 2016

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

August 09, 2018

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on February 24, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

Not Defined:

Pos Id Segment Name Req Max Use Repeat Notes Usage

* ISA Interchange Control Header M 1

* GS Functional Group Header M 1

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 Must use

0300 REF Reference Identification O >1 Used
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004030F650C1CA05 2 February 24, 2022

* 0400 DTM Date/Time Reference O >1

LOOP ID - N1 LOOP ID - N1 >1 N1/0500L N1/0500L

0500 N1 Name O 1 N1/0500 Used

* 0600 N2 Additional Name Information O 2

* 0700 N3 Address Information O 2

* 0800 N4 Geographic Location O 1

* 0900 PER Administrative Communications

Contact

O >1

* 1000 REF Reference Identification O >1

LOOP ID - LM LOOP ID - LM >1

1100 LM Code Source Information O 1 Used

1200 LQ Industry Code M >1 Must use

* 1300 PER Administrative Communications

Contact

O >1

* 1400 REF Reference Identification O >1

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL LOOP ID - HL >1 N2/0100L N2/0100L

0100 HL Hierarchical Level M 1 N2/0100 Must use

* 0200 SPI Specification Identifier O 1

0300 REF Reference Identification O >1 Used

0400 LIN Item Identification O >1 Used

* 0500 DTM Date/Time Reference O >1

0600 QTY Quantity O >1 Used

* 0700 YNQ Yes/No Question O >1 N2/0700

* 0800 AMT Monetary Amount O >1

* 0900 PCT Percent Amounts O >1

* 1000 MEA Measurements O >1

* LOOP ID - CLI * LOOP ID - CLI >1

* 1100 CLI Cost Line Item O 1

* 1200 QTY Quantity O >1

* 1300 AMT Monetary Amount O >1

* 1400 RPA Rate Amounts or Percents O >1

* LOOP ID - LM * LOOP ID - LM >1 N2/1500L N2/1500L

* 1500 LM Code Source Information O 1 N2/1500

* 1600 LQ Industry Code M >1

* 1700 REF Reference Identification O >1

* 1800 DTM Date/Time Reference O >1

* LOOP ID - NM1 * LOOP ID - NM1 >1 N2/1900L N2/1900L

* 1900 NM1 Individual or Organizational Name O 1 N2/1900

* 2000 N2 Additional Name Information O 2

* 2100 N3 Address Information O 2

* 2200 N4 Geographic Location O 1

* 2300 COM Communication Contact

Information

O >1

* 2400 REF Reference Identification O >1

* LOOP ID - MTX * LOOP ID - MTX >1

* 2500 MTX Text O 1

* 2600 DTM Date/Time Reference O >1

* 2700 NM1 Individual or Organizational Name O >1

* 2800 REF Reference Identification O >1
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004030F650C1CA05 3 February 24, 2022

2900 SE Transaction Set Trailer M 1 Must use

Not Defined:

Pos Id Segment Name Req Max Use Repeat Notes Usage

* GE Functional Group Trailer M 1

* IEA Interchange Control Trailer M 1

Notes: 

1/0500L The N1 segment identifies the organization originating and receiving the transaction set.

1/0500 The N1 segment identifies the organization originating and receiving the transaction set.

2/0100L The HL levels are group work candidate and work candidate. Valid HL parent-child relationships are 1) group work

candidate-group work candidate and 2) group work candidate-work candidate.

2/0100 The HL levels are group work candidate and work candidate. Valid HL parent-child relationships are 1) group work

candidate-group work candidate and 2) group work candidate-work candidate.

2/0700 The YNQ segment identifies conditions related to a maintenance or repair requirement.

2/1500L The LM loop identifies management data that pertains to each use of the HL loop.

2/1500 The LM loop identifies management data that pertains to each use of the HL loop.

2/1900L The NM1 segment identifies individuals and organizations involved in identifying, coordinating or performing maintenance.

2/1900 The NM1 segment identifies individuals and organizations involved in identifying, coordinating or performing maintenance.
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

004030F650C1CA05 4 February 24, 2022

ST Transaction Set Header Pos: 0100 Max: 1

Heading - Mandatory

Loop: N/A Elements: 3

User Option (Usage): Must use

Purpose: 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

M ID 3/3 Must use

CodeList Summary (Total Codes: 314, Included: 1)

Code Name

650 Maintenance Service Order

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

DLMS 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
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

004030F650C1CA05 5 February 24, 2022

BGN Beginning Segment Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 4

User Option (Usage): Must use

Purpose: To indicate the beginning of a transaction set

Syntax Rules: 

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

M ID 2/2 Must use

CodeList Summary (Total Codes: 65, Included: 2)

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.

BGN02 127 Reference Identification

Description: Reference information as defined for a

particular Transaction Set or as specified by the

Reference Identification Qualifier

DLMS Note: Use code 'Z' for this data element to

satisfy mandatory X12 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

DLMS Note: This date corresponds to the Universal

Time Coordinate (UTC).

M DT 8/8 Must use

BGN07 640 Transaction Type Code

Description: Code specifying the type of

transaction

O ID 2/2 Used

CodeList Summary (Total Codes: 500, Included: 1)

Code Name

ZB Report of Work Candidate

DLMS Note:

Use for component packing confirmation. (non-DLSS DIC C2F). An ANSI data maintenance action will

be taken to obtain a more appropriate code for Component Packing Confirmation for use in a future

version/release. 
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

004030F650C1CA05 6 February 24, 2022

REF Reference Identification Pos: 0300 Max: >1

Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

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

Semantics: 

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

DLMS Note:

Must use this 1/REF/0300 to identify the Build Directive Number for this transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

REF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

CodeList Summary (Total Codes: 1631, Included: 1)

Code Name

WO Work Order Number

DLMS Note:

Use to identify the Build Directive Number for medical/surgical component assembly. (A data

maintenance action was approved in version 5010. The approved code/name is BDN – Build Directive

Number).

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 Used
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

004030F650C1CA05 7 February 24, 2022

N1 Name Pos: 0500 Max: 1

Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): Used

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

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is 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.

DLMS Note:

Must use this 1/N1/0500 loop to identify the organizations originating the transaction set and to receive 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

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

CodeList Summary (Total Codes: 1446, Included: 2)

Code Name

WZ Final Maintenance Organization

DLMS Note:

Use to identify [final] assembly/maintenance activity for medical/surgical component assembly. This

organization will complete kit assemblies and ship to final destination activity.

Z4 Owning Inventory Control Point

DLMS Note:

Use to identify the supply source/Assembly Manager.

N103 66 Identification Code Qualifier

Description: Code designating the system/method

of code structure used for Identification Code (67)

X ID 1/2 Used

CodeList Summary (Total Codes: 223, Included: 2)

Code Name

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)

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

O ID 2/3 Used

CodeList Summary (Total Codes: 1446, Included: 2)

Code Name

FR Message From
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

Code Name

004030F650C1CA05 8 February 24, 2022

DLMS Note:

Use with 1/N101/0500 code WZ to indicate that the organization cited in N104 is originating the

transaction set.

TO Message To

DLMS Note:

Use with 1/N101/0500 code Z4 to indicate that the organization cited in N104 is the action organization

receiving the transaction set.
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

004030F650C1CA05 9 February 24, 2022

LM Code Source Information Pos: 1100 Max: 1

Heading - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

Use this 1/LM/1100 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

M ID 2/2 Must use

CodeList Summary (Total Codes: 187, Included: 1)

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

004030F650C1CA05 10 February 24, 2022

LQ Industry Code Pos: 1200 Max: >1

Heading - Mandatory

Loop: LM Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

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

DLMS Note:

Use to identify codes, as appropriate, 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

DLMS Note: The following codes are authorized.

O ID 1/3 Used

CodeList Summary (Total Codes: 768, Included: 1)

Code Name

0 Document Identification Code

DLMS Note:

1. The DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS

environment. Continued support of the DIC in a full DLMS environment will be assessed at a future

date.

2. Future streamlined data; see introductory DLMS note 3b.

LQ02 1271 Industry Code

Description: Code indicating a code from a specific

industry code list

X AN 1/30 Used
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

004030F650C1CA05 11 February 24, 2022

HL Hierarchical Level Pos: 0100 Max: 1

Detail - Mandatory

Loop: HL Elements: 4

User Option (Usage): Must use

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments

Comments: 

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment

data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure.

3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01

could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL

segment and would be incremented by one in each subsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

5. HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in

the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring

to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

DLMS Note:

For use in Component Packing Confirmation loop.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

HL01 628 Hierarchical ID Number

Description: A unique number assigned by the

sender to identify a particular data segment in a

hierarchical structure

DLMS Note: In the first 2/HL/0100 loop iteration,

cite numeric 1. In each subsequent loop iteration,

increase incrementally by 1.

M AN 1/12 Must use

HL02 734 Hierarchical Parent ID Number

Description: Identification number of the next

higher hierarchical data segment that the data

segment being described is subordinate to

O AN 1/12 Used

HL03 735 Hierarchical Level Code

Description: Code defining the characteristic of a

level in a hierarchical structure

DLMS Note: The following codes are authorized.

M ID 1/2 Must use

CodeList Summary (Total Codes: 218, Included: 1)

Code Name

F Component

DLMS Note:

For Medical use in Component Packing Confirmation loop.

HL04 736 Hierarchical Child Code

Description: Code indicating if there are

hierarchical child data segments subordinate to the

level being described

All valid standard codes are used. (Total Codes:

2)

O ID 1/1 Used
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

004030F650C1CA05 12 February 24, 2022

REF Reference Identification Pos: 0300 Max: >1

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

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

Semantics: 

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

DLMS Note:

Use in Component Packing Confirmation loop.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

REF01 128 Reference Identification Qualifier

Description: Code qualifying the Reference

Identification

DLMS Note: The following codes are authorized.

M ID 2/3 Must use

CodeList Summary (Total Codes: 1631, Included: 2)

Code Name

55 Sequence Number

DLMS Note:

Use to identify the Sort Sequence Number.

SQ Container Sequence Number

DLMS Note:

Use to identify the Container Sequence Number.

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 Used
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

004030F650C1CA05 13 February 24, 2022

LIN Item Identification Pos: 0400 Max: >1

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To specify basic item identification data

Syntax Rules: 

1. P0405 - If either LIN04 or LIN05 is present, then the other is required.

2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

3. P0809 - If either LIN08 or LIN09 is present, then the other is required.

4. P1011 - If either LIN10 or LIN11 is present, then the other is required.

5. P1213 - If either LIN12 or LIN13 is present, then the other is required.

6. P1415 - If either LIN14 or LIN15 is present, then the other is required.

7. P1617 - If either LIN16 or LIN17 is present, then the other is required.

8. P1819 - If either LIN18 or LIN19 is present, then the other is required.

9. P2021 - If either LIN20 or LIN21 is present, then the other is required.

10. P2223 - If either LIN22 or LIN23 is present, then the other is required.

11. P2425 - If either LIN24 or LIN25 is present, then the other is required.

12. P2627 - If either LIN26 or LIN27 is present, then the other is required.

13. P2829 - If either LIN28 or LIN29 is present, then the other is required.

14. P3031 - If either LIN30 or LIN31 is present, then the other is 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.

DLMS Note:

1. Use in 2/HL/0100 transaction loops to identify the materiel.

2. For Medical use in Component Packing Confirmation loop.

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)

DLMS Note: The following codes are authorized.

M ID 2/2 Must use

CodeList Summary (Total Codes: 505, Included: 2)

Code Name

A3 Locally Assigned Control Number

DLMS Note:

Must use with the Component Packing Conformation loop, to identify the Assemblage Identification

Number (AIN).

FS National Stock Number

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

X ID 2/2 Used
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F650C1CA05 14 February 24, 2022

descriptive number used in Product/Service ID (234)

DLMS Note: The following codes authorized.

CodeList Summary (Total Codes: 505, Included: 1)

Code Name

OE Original Equipment Number

DLMS Note:

Use to identify the Original Component Stock Number for medical/surgical component assembly.

LIN05 234 Product/Service ID

Description: Identifying number for a product or

service

X AN 1/48 Used
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

004030F650C1CA05 15 February 24, 2022

QTY Quantity Pos: 0600 Max: >1

Detail - Optional

Loop: HL Elements: 3

User Option (Usage): Used

Purpose: To specify quantity information

Syntax Rules: 

1. R0204 - At least one of QTY02 or QTY04 is required.

2. E0204 - Only one of QTY02 or QTY04 may be present.

Semantics: 

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

DLMS Note:

1. Use in 2/HL/0100 transaction loops to identify the quantity being requested.

2. For Medical use in Component Packing Confirmation loop.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage

QTY01 673 Quantity Qualifier

Description: Code specifying the type of quantity

DLMS Note: The following codes are authorized.

M ID 2/2 Must use

CodeList Summary (Total Codes: 976, Included: 2)

Code Name

63 On Order Quantity

DLMS Note:

Use to identify the number of assemblies being requested (Total Number of Assemblages).

UA Units Completed

DLMS Note:

Use to identify the component quantity packed. To reverse all or part of a transaction, use a minus sign

in front of the quantity to be reversed.

QTY02 380 Quantity

Description: Numeric value of quantity

DLMS Note: 1. For QTY01 Code 63, express as

whole number with no decimals. A field size

exceeding 5 positions may not be received or

understood by the recipient's automated processing

system. See introductory DLMS note 3c.

DLMS Note: 1. For QTY01 Code 63, express as

whole number with no decimals. A field size

exceeding 5 positions may not be received or

understood by the recipient's automated processing

system. See introductory DLMS note 3c.

2. For QTY01 Code UA, express number with up to

two decimal positions. A field size exceeding 8

positions (three of which are the decimal point and

two decimal positions), may not be received or

understood by the recipient's automated processing

system. The non-DLSS DIC C2F carried 2 decimal

places in the quantity packed field (rp 25-31). See

introductory DLMS note 3c.

2. For QTY01 Code UA, express number with up to

two decimal positions. A field size exceeding 8

positions (three of which are the decimal point and

two decimal positions), may not be received or

understood by the recipient's automated processing

system. The non-DLSS DIC C2F carried 2 decimal

places in the quantity packed field (rp 25-31). See

introductory DLMS note 3c.

X R 1/15 Used

QTY03 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for examples of

use)

O Comp Used

QTY03-01 355 Unit or Basis for Measurement Code

Description: Code specifying the units in which a

value is being expressed, or manner in which a

M ID 2/2 Must use
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage

004030F650C1CA05 16 February 24, 2022

measurement has been taken

DLMS Note: 1. Use to identify the unit of issue for

materiel requested.

2. For use with QTY01 code UA. 

3. DLMS users see the Unit of Issue and Purchase

Unit Conversion Table for available codes. 
DLMS Implementation Convention (IC) - 650C Component Packing Confirmation ADC 145, 189, 436, 1043C, 1367 and 1412 DLM 4000.25

004030F650C1CA05 17 February 24, 2022

SE Transaction Set Trailer Pos: 2900 Max: 1

Detail - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

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

(SE) segments)

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

DLMS Note: Cite the same number as the one cited

in ST02.

M AN 4/9 Must use