DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

February 22, 2018

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

SUBJECT: Approved Addendum to Approved Defense Logistics Management Standards 

(DLMS) Change (ADC) 1230A to include the DLMS 867I Issue Transaction and 

Associated Procedures for Air Force Government Furnished Property Accountability 

(GFP-A) (Supply/Finance)

We are forwarding the attached approved change to DLM 4000.25, Defense Logistics 

Management Standards (DLMS), for implementation. The Enterprise Business Standards 

Office will post the updated DLMS Implementation Convention (IC) to the Web at

http://www.dla.mil/HQ/InformationOperations/DLMS/elibrary/Transformats/140_997/,

within 10 days from the above date.

Addressees may direct questions to Mr. Eric Flanagan, MILSTRIP Administrator, email: 

Eric.Flanagan@dla.mil, Mr. Rafael Gonzalez, DOD MILSTRAP Administrator, email: 

Rafael.Gonzalez@dla.mil, or DLMS Supply, DLMSSupply@dla.mil. Others must contact their 

designated Supply PRC representative available at 

http://www.dla.mil/HQ/InformationOperations/DLMS/allpoc/. 

 

HEIDI M. DAVEREDE

Director

Enterprise Business Standards Office

Attachment

As stated 

cc: 

ODASD (SCI)

OUSD DPAP (PDI)

Air Force Finance PRC Representative

Air Force IUID Working Group Representative
Attachment, ADC 1230A

Page 1

Attachment to ADC 1230A

Approved Addendum to Include the DLMS 867I Issue Transaction 

and Associated Procedures for Air Force Government Furnished 

Property Accountability (GFP-A) 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Mr. John “Jack” Dillon, HAF/A4PT; 937-904-0815; DSN: 674-

0815; or email: john.dillon.2.ctr@us.af.mil

b. Functional POC: Mr. Colquitt “Quitty” Lawrence, HAF/A4LR; 703-692-2348; 

DSN: 222-2348; or email: colquitt.lawrence.civ@mail.mil

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply/Finance

b. Primary/Secondary Functional Process: Serialized item management/tracking

2. REFERENCES:

a. ADC 1230, Revise Balance Affecting Transactions to Authorize Air Force Contractor 

Inventory Control Points (CICP) use of Batch Number, Serial Number, and Unique Item 

Identifier (UII) for Air Force Government Furnished Property (GFP) Accountability (GFP-A) 

(Supply/Finance), September 1, 2017

b. ADC 1198A, Establishing and Maintaining Accountability for Service Owned Capital 

Equipment Stored at DLA Distribution Centers – (Missing Serial Numbers and Remove 867I 

Issue Transactions), September 6, 2017

c. ADC 1198, Establishing and Maintaining Accountability for Service Owned Capital 

Equipment Stored at DLA Distribution Centers, October 6, 2016

d. DLM 4000.25, Defense Logistics Management Standards (DLMS), Volume 2, Supply 

Standards and Procedures

e. DODI 5000.64, Accountability and Management of DOD Equipment and Other 

Accountable Property

f. ADC 1226, Revise DLMS 824R Reject Advice Transaction in Support of Intra-Air 

Force Government Furnished Property-Accountability (GFP-A), May 10, 2017
Attachment, ADC 1230A

Page 2

3. APPROVED CHANGE(S):

a. Brief Overview of Change:

(1) ADC 1230 (Reference 3.a.) authorized Air Force Contractor Inventory 

Control Points (CICPs) to use a batch number, serial number, and unique item identifier (UII) in 

balance-affecting transactions transmitted to the Air Force Property System of Record (APSR). 

This approved addendum to ADC 1230 authorizes the same data elements for inclusion in 

DLMS 867I issue transactions sent from the Air Force CICPs to the Air Force APSR.

(2) This change includes updates that are not specific to Air Force GFP-A, such 

as authorizing the beginning segment date and time for creation of the transaction set.

(3) This change includes several administrative updates to the DLMS 867I IC.

b. Background:

(1) ADC 1230 authorized Air Force CICPs to include a batch number, serial 

number, and UII in balance-affecting transactions transmitted to the Air Force APSR. The Air 

Force’s original PDC submission to EBSO contained the DLMS 867I Issue in the list of balanceaffecting transactions to contain the authorized data elements. However, EBSO removed the 

DLMS 867I during internal coordination before releasing the PDC for Component review. This 

decision was influenced by ADC 1198A (Reference 3.b), which removed the DLMS 867I from 

the list of balance-affecting transactions to carry unique item data for capital equipment 

candidate assets stored at Defense Logistics Agency (DLA) Distribution Centers.

(2) ADC 1198 (Reference 3.c.) contained the wording, “The storage activity will 

include the serial numbers and UIIs when available on the DLMS 945A Materiel Release 

Confirmation and/or DLMS 867I Issue.” However, DLA Distribution Centers send the DLMS 

867I Issue transaction immediately upon allocation, decrementing the available for issue balance. 

At this point, the DLMS 867I does not affect the on hand balance since the distribution center 

personnel have not yet physically selected the item from the storage location. As a result, the 

DLMS 867I does not contain the item unique information. Based on these considerations, ADC 

1198A removed the serial number/UII requirement for capital equipment from the DLMS 867I. 

ADC 1198 does allow the inclusion of the serial number and UII in the DLMS 867I on an intraService basis. 

(3) Upon release of ADC 1230, the Air Force reported the need to include the 

DLMS 867I in accordance with the original PDC requirements. The Air Force explained that the

CICPs will use the DLMS 867I when a customer picks up an item locally, as indicated by

Transportation Method Code X (bearer, walk-through). In this case, the CICP processes the 

DLMS 867I when the customer picks up the item, which allows the CICP to identify the serial 

number and UII within the transaction. Use of Transportation Method Code X in the 867I 

prevents the APSR from retaining the item in the Air Force program manager’s property record 

or recording the item in an in-transit status. The serial number is required to provide 

serialization data for serially tracked GFP assets, as is the UII when it is available.
Attachment, ADC 1230A

Page 3

(4) Air Force CICPs, using their own inventory management systems (IMS), will 

send DLMS 867I Issue Transaction to the Air Force APSR in accordance with Reference 3.d. 

The CICP must forward this transaction to the APSR in order to adjust inventory balances. The 

Air Force APSR will be a mirror image of the CICP’s IMS and, in order to maintain accuracy, 

certain data elements must be added or authorized within DLMS transactions.

c. Approved Change in Detail:

(1) Air Force CICPs must enter serial numbers on serially managed Air Force 

GFP assets when sending transactions to the Air Force APSR. The CICP will include the UII 

when available. The tracking requirement applies to property identified by NSN or Air Forceassigned LSNs in accordance with the CICP contract requirements. The CICP will use the Air 

Force serialized report code to indicate serial management of an asset to the Air Force APSR.

The Air Force serialized report code is restricted to the data exchanges between the CICPs and 

the Air Force APSR.

(2) The CICP will include the batch number for property with shelf-life usage 

implications.

(3) Serially-managed GFP assets require serialization data visibility to comply 

with Financial Improvement and Audit Readiness (FIAR) and DODI 5000.64, Accountability 

and Management of DOD Equipment and Other Accountable Property (Reference 3.e.). The 

following paragraphs identify changes to the DLMS 867I that establish visibility of seriallymanaged GFP assets in support of FIAR compliance.

(a) Air Force CICPs will prepare a DLMS 867I Issue transaction when 

issuing serially-managed GFP that is picked up locally by a customer and is not shipped or intransit. The Air Force CICPs will prepare a DLMS 945A Materiel Release Confirmation if 

materiel is shipped and in-transit. The serial number is mandatory in both transactions, as is the

UII when available. The Air Force program managers’ account in the APSR will indicate that 

the serial numbers and UIIs are no longer available for issue. The APSR will exclude serial 

numbers and UIIs issued for internal CICP deliveries, local disposal, and customer pick up from 

being recorded as in-transit. The exclusions eliminate property that is no longer tracked by the 

owner and is not retained in the owner’s property record after issue. The exclusions are triggered 

by the Transportation Mode Code X in the DLMS 867I.

(b) If the Air Force APSR does not have a record of the serial number and 

UII sent in a DLMS 867I Issue from the Air Force CICP, the Air Force APSR will report the 

transaction to the Air Force Program Manager’s daily task list and reject the transaction using 

DLMS 824R Reject Advice (with Reject Advice Code BA1) in accordance with ADC 1226 

procedures (Reference 3.g.). The same action will apply if the serial number and UII are at a 

different location than the reporting activity. In support of FIAR compliance, for seriallymanaged GFP assets requiring serialization data visibility, either of these conditions may require 

the Air Force Program manager to initiate a complete inventory at all storage locations for all 

owners and supply condition codes. For serial number/UII mismatches, the Air Force CICP and 

 1 Refer to DLM 4000.25-2, MILSTRAP, Appendix 2.8 Reject Advice Codes; or Logistics Data Resources 

Management System (LOGDRMS) Data Element ID 1270 qualifier ET - Reject Advice Codes. 
Attachment, ADC 1230A

Page 4

Air Force Program Manager will need to collaborate and take appropriate steps to resolve the 

discrepancy.

(4) This change authorizes a DLMS enhancement that identifies the date and time 

that the originator created the transaction set (BPT Beginning Segment, BPT03 Date and BPT08 

Time). This change identifies the date and time as a way to provide a systemic beginning 

segment transaction set preparation date/time stamp for all transactions. This date and time is 

not for functional use even though they may coincide with the date and time of a business 

process.

(5) This change includes administrative updates to remove Federal Notes or

change them to DLMS Notes where needed.

d. Revisions to DLM 4000.25 Manuals: Revise DLMS 867I Issue Transaction, as 

shown in the enclosure.

e. Approved Transaction Flow: This change does not modify existing transaction flows

for the CICP interface with the Air Force APSR.

f. Alternatives: None

5. REASON FOR CHANGE: This change supports the Air Force GFP-A Capability Initiative 

by addressing a material weakness on the Air Force Financial Statements and supports FIAR

compliance. The CICP will pass the serial number, UII, and batch number to the Air Force 

APSR to provide the Air Force Program Manager GFP visibility and contract oversight.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Providing detailed information for inventory accounting transactions 

and records allows the Air Force to automatically update asset valuation and maintain key 

supporting documents used by FIAR auditors for contractor-managed and possessed, Air Force 

owned GFP in the Air Force APSR. This change also allows the Air Force to serially-manage 

and track GFP assets.

b. Disadvantages: The Air Force CICPs systems may require modification in order to 

accommodate the batch number and IUID data.

7. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW 

DEVELOPMENT:

a. The Air Force will identify Air Force GFP-A items requiring serial number/UII in the 

Air Force CICP’s contract.

b. The Air Force will develop procedures for conducting the initial inventory (i.e. 

recording, creating, and applying any required serial numbers and UIIs to bare items or 

packaging) of GFP-A serial tracked assets at Air Force CICP warehouses.
Attachment, ADC 1230A

Page 5

8. ADDITIONAL COMMENTS TO CONSIDER: The Air Force GFP-A Capability

Initiative relies on DLMS transactions from the Air Force CICPs to accurately record asset 

quantities and valuation. The Air Force requires a manual workaround if the Air Force APSR 

cannot receive serial number, batch number, and UII information through DLMS transactions.

Manual workarounds increase the risk that the contractor will misreport the Air Force contractor 

managed and possessed, Air Force-owned GFP assets on its financial statements.

9. ADDITIONAL FUNCTIONAL REQUIREMENTS: This approved change authorizes the 

Air Force to pass an internal code value to the APSR to designate a requirement for serialized 

tracking/management for GFP. As the DOD transitions to standard procedures for tracking items 

identified to a Unique Item Tracking (UIT) Program, the Air Force should consider using the 

UIT Designator in FLIS for NSN items under an established program. Standard procedures 

ensure consistency across DOD as requirements are identified for comparable procedures for 

other Components requiring internal tracking.

10. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: February, 2018

11. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: The Air Force is unable to provide a savings/cost

estimate at this time. The Air Force does not have adequate data to calculate the cost of a

manual workaround. This change will enable the DLMS compliant services to meet 2017 FIAR 

requirements.

a. New DLMS Data Elements: None

b. Changes to DLMS Data Elements: None

c. Automated Information Systems (AIS): This change applies to the Air Force APSR

(Defense Property Accountability System (DPAS)) and Air Force CICP inventory management 

systems. This change does not apply to other DOD Component systems, but they may optionally 

use the beginning segment for transaction date and time preparation.

d. DAAS: DAAS must implement mapping updates as shown in Enclosure 1.

e. Non-DLM 4000.25 Series Publications: The Air Force should update procedures 

documenting requirements contained herein as necessary.

12. PROPOSED DLMS CHANGE (PDC) 1230A RESPONSE/COMMENT 

RESOLUTION: 

Originator Response/Comment Disposition

1. DLA Concur without Comment Noted.

2. Navy Concur without Comment Noted.

3. Air Force Concur without Comment Noted.

4. Army (SDR) Concur without Comment Noted.
Attachment, ADC 1230A

Page 6

5. US Army Concur without Comment Noted.

6. US Air Fore Concur without Comment Noted.

7. USMC Concur without Comment Noted.

8. DAAS Concur with Comment

1/29/181/29/18: Para 11.d states there are no DAAS 

changes but DAAS will need to add LQ*SRC to mapping 

for AF GFP usage as shown on page 2 of Encl 1.

Noted.

9. USTRANSCOM Concur without Comment Noted.
Enclosure 1, ADC 1230A

Page 1

Enclosure 1, Revisions to the DLMS 867I Issue

# Location Revisions to DLMS 867I Issue Reason

1. Cover page 

Federal 

Notes

Delete Federal Notes:

Federal Note:

1. Storage organizations use this transaction set to report materiel 

issues to Inventory Control Points (ICPs) or Integrated Materiel 

Managers (IMMs).

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 Standards (DLMS) Implementation Convention (IC) 

available at

URL: http://www.dla.mil/j-6/dlmso. The DLMS IC provides 

specific business rules, conditions, and authorized codes necessary 

for appropriate use of this IC within the DLMS.

DLMS Note:

2. Use a single occurrence of this transaction set to exchange 

transactions between a single storage organization and a single or 

multiple ICPs or IMMs. DoD logistics users should refer to the 

Defense Logistics Management Standards (DLMS) 

Implementation Convention (IC) available at URL:

http://www.dla.mil/HQ/InformationOperations/DLMS/elibrary/Tr

ansformats/140_997/#867. The DLMS IC provides specific 

business rules, conditions, and authorized codes necessary for 

appropriate use of the IC within the DLMS

Administrative 

update to delete 

Federal notes.

Federal Notes 1 and 

2 are currently 

repeated as

introductory DLMS 

Notes 1 and 2. 

Add content of 

Federal Note 3 to 

existing DLMS Note 

2.

2. Cover page 

DLMS 

Introductory 

Notes

Revise DLMS introductory note 6: 

This transaction may only be used to provide item unique 

identification (IUID) information only on a limited scope. in 

accordance with DLMS procedures for the Unique Item Tracking 

(UIT) program for Positive Inventory Control (PIC) Nuclear 

Weapon Related Materiel (NWRM). Loop ID LX (2/LX/280) 

documents the authorized uses of unique item identifier (UII) and 

serial number. For all other purposes, the UII/serial number

information is a placeholder for DLMS enhancements pending 

development of DLMS procedures and overarching OSD Supply 

Policy. Refer to the item unique identification (IUID) web at URL: 

http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy.

3. Cover pages 

DLMS 

Introductory 

Notes

Add ADC 1230A to DLMS Introductory Note 7: 

- ADC 1230A, Approved Addendum to include the DLMS 867I 

Issue Transaction and Associated Procedures for Air Force 

Government Furnished Property Accountability (GFP-A) 

(Supply/Finance)

Identifies DLMS 

Changes included in 

the IC.
Enclosure 1, ADC 1230A

Page 2

# Location Revisions to DLMS 867I Issue Reason

4. 1/BPT01/20 Delete DLMS Note from Transaction Set Purpose Code:

DLMS Note: DLMS enhancement; see introductory DLMS note 

5a.

Administrative 

update. Transaction 

Set Purpose Code is 

not identified as a 

DLMS enhancement 

in DLMS ICs.

5. 1/BPT03/20 Change Federal note to DLMS Note 1 and renumber existing 

DLMS Note to DLMS Note 2as shown:

DATE

Federal Note: Use to identify the date of transaction set 

preparation. This date corresponds to the Universal Time

Coordinate (UTC).

DLMS Note: 

1. Use to identify the date of transaction set preparation. This date 

corresponds to the Universal Time Coordinate (UTC).

2. Authorized DLMS enhancement; see introductory DLMS note 

5ea.

Allows for use of 

the transaction set 

preparation date as 

an authorized 

DLMS 

enhancement, as 

needed, without 

further coordination 

at the DOD level. 

6. 1/BPT08/20 Change Federal Notes to DLMS Notes 1 and 2 and renumber 

existing DLMS Note to DLMS Note 3as shown:

TIME

Federal Note: 1. Use to identify the originator's time of 

transaction set preparation in UTC. 

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

DLMS Note: 

1. Use to identify the originator's time of transaction set preparation 

in UTC.

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

3. Authorized DLMS enhancement; see introductory DLMS note 

5ea.

Allows for use of 

the transaction set 

preparation time as 

an authorized 

DLMS 

enhancement, as 

needed, without 

further coordination 

at the DOD level.

7. 2/LQ01/270 Add qualifier and DLMS Note:

SRC Serialized Report Code

DLMS Note:

1. Use to cite the Air Force Serialized Report Code. The Air Force 

uses this code to indicate that an item requires serialized 

management. Applicable to property identified by national stock 

number (NSN) or Air Force-assigned local stock number (LSN) in 

accordance with CICP contract requirements. Authorized for Air 

Force GFP-A. Refer to ADC 1230A.

2. Local code SRC is established for use in the 867I version 4010. 

A data maintenance action will be submitted to establish ‘SRCSerialized Report Code' in a future version. The following values 

will be conveyed in 2/LQ02/130:

A Small Arms

Identifies an Air 

Force GFP-A 

requirement.
Enclosure 1, ADC 1230A

Page 3

# Location Revisions to DLMS 867I Issue Reason

C Communications Security (COMSEC)

D Reserved

R Nuclear Weapons Related Material (NWRM) COMSEC

W NWRM

8. 2/LX/280 Revise segment level notes as follows:

1. Use the LX segment as a counter to identify the number of 

2/LX/280 loop iterations in the transaction set.

12. The entire 2/LX//280 loop (LOOP ID - LX) is an authorized 

DLMS enhancement for use to provide item unique identification 

(IUID) data as noted below for specific implementations; see 

introductory DLMS note 5e. For all other applications, see 

introductory DLMS note 5a. At this time, the 2/LX/280 loop is 

not authorized for use to provide item unique identification (IUID) 

or Unique Item Tracking (UIT) information, except for the Positive 

Inventory Control (PIC) Nuclear Weapon Related Materiel 

(NWRM) UIT program (UIT Designator AAJ). Refer to ADC 347 

and ADC 1136.

23. The 2/LX/280 loop is repeated for each item to be uniquely 

identified and provides flexibility to accommodate tracking by UII 

or serial number/UII.

34. May use the 2/LX/280 loop to provide batch/lot number 

information.

4. The entire 2/LX//280 loop is a DLMS enhancement. See 

introductory DLMS note 5a.

5. Authorized for use with the Positive Inventory Control (PIC) 

Nuclear Weapon Related Materiel (NWRM) UIT program (UIT 

Designator AAJ). Refer to ADC 347 and ADC 1136.

6. Authorized for use for Air Force GFP accountability of 

serially tracked assets between the Air Force CICP and the Air 

Force APSR systems. Refer to ADC 1230A.

Documents Air 

Force GFP 

accountability 

requirement. 

Administrative 

updates to rearrange 

existing notes for 

clarity.

9. 2/LX01/280 Change Federal Note to DLMS Note.

Federal DLMS Note: In the first 2/LX/280 loop iteration, cite 

numeric 1. In each subsequent loop iteration, increase

Incrementally by 1.

Administrative

update.

10. 2/REF/290 Delete segment level Federal note:

Federal Note: Use the 2/REF/290 segment to provide Item Unique 

Identification (IUID) information.

Revise segment level DLMS Notes:

DLMS Note:

1. The 2/REF/290 loop is an authorized DLMS enhancement for 

intra-Component use in Issue transactions when the item identified 

is subject to UIT requirements to provide Item Unique 

Identification (IUID) serial number/UII data as noted below for 

specific implementations; see introductory DLMS note 5e. For all 

other applications, see introductory DLMS note 5a. 

Identifies the Air 

Force GFP-A 

requirement.

Administrative 

updates to rearrange 

notes for clarity.

Authorized 

requirements are 

identified at the REF 

segment level 
Enclosure 1, ADC 1230A

Page 4

# Location Revisions to DLMS 867I Issue Reason

2. This transaction will support item identification based upon the 

serial number/UII or the serial number. This transaction also 

provides for use of a batch/lot number, when applicable.

3. Use multiple iterations of 2/REF/290 segment within the 

2/LX/280 loop, to provide identifying information for an item as 

needed.

4. Authorized for use with the Positive Inventory Control (PIC) 

Nuclear Weapon Related Materiel (NWRM) UIT program (UIT 

Designator AAJ). Refer to ADC 347 and ADC 1136

5. Authorized for use with Air Force GFP accountability. Refer 

to ADC 1230A.

DLMS notes; 

accordingly, they do 

not need to be 

repeated at each data 

element within the 

segment. 

11. 2/REF01/290 Delete Federal Note:

Federal Note: Use any code

Administrative DLMS Note updates to existing qualifiers BT, SE, 

and U3:

BT Batch Number

DLMS Note:

1. Use to identify the batch, lot, or other number identifying the 

production run. The batch/lot number may not exceed 20 

characters in accordance with IUID policy.

2. DLMS enhancement. See introductory DLMS note 5a.

SE Serial Number

DLMS Note:

1. Use to identify the serial number. Place serial number value in 

REF02. The serial number may not exceed 30 characters in 

accordance with IUID policy.

2. DLMS enhancement. See introductory DLMS note 5a.

U3 Unique Supplier Identification Number (USIN)

DLMS Note:

1. Use to identify the UII. Place UII value in REF03. The UII may 

not exceed 50 characters in accordance with IUID Policy. 

2. An ANSI Data maintenance action was approved in version 

5020. The approved code/name is "UII - Department of Defense 

Unique Item Identifier.

Administrative 

update to delete the 

DLMS enhancement 

note at data element

level. The DLMS 

enhancement note is 

not required at the 

data element level. 

The LOOP ID LX 

segment level 

notes, and the REF 

segment level 

notes, state that use 

of the loop and 

segment is a DLMS 

enhancement.

Administrative 

update to add the 

serial number length

under IUID policy.

12. 2/REF04-01 Delete Federal Note:

Federal Note: Use any code

Administrative 

update.
Enclosure 2, ADC 1230A

Page 1

Enclosure 2, DLMS 867I Administrative Update to Remove Federal IC Notes

# 867I 

Location

Administrative Update to Remove Federal Notes from the DLMS 867I Issue

1. 1/ST02/10 Change Federal Note to a DLMS Note.

2. 1/N1/80 Change Federal Note to DLMS Note.

3. 1/N101/80 Delete Federal Note:

Federal Note: Use any code.

4. 2/PTD01/10 Delete Federal Note:

Federal Note: Use any code.

5. 2/DTM/20 Change Federal Note to DLMS Note.

6. 2/DTM01/20 Delete Federal Note:

Federal Note: Use any code.

7. 2/REF/30 Change Federal Note to DLMS Note.

8. 2/REF01/30 Delete Federal Note:

Federal Note: Use any code.

9. 2/REF04-01/ 

30

Delete Federal Note:

Federal Note: Use any code.

10. 2/N1/50 Delete Federal Note:

Federal Note:

Must use one iteration of this 2/N1/050 loop to identify the organization to receive the 

transaction.

Revise DLMS Note:

DLMS Note: Must use at least one iteration of this 2/N1/050 loop segment to identify 

the organization to receive the transaction (N106 code TO with appropriate N101 code). 

May use additional iterations to identify other organizations associated with the 

transaction.

11. 2/N101/50 Delete Federal Note:

Federal Note: Use any code.

12. 2/N106/50 Change Federal Note to DLMS Note.

13. 2/QTY/110 Change Federal Note to DLMS Note 1; renumber existing DLMS Note as DLMS Note 

2.

14. 2/QTY01/110 Delete Federal Note:

Federal Note: Use any code.

15. 2/QTY02/110 Change Federal Note to DLMS Note 1. Number existing DLMS Note as DLMS Note 2.

16. 2/QTY03-01/ 

11

Change Federal Note to DLMS Note 1. Number existing DLMS Note as DLMS Note 2.

17. 2/AMT01/140 Delete Federal Note:

Federal Note: Use any code.
Enclosure 2, ADC 1230A

Page 2

# 867I 

Location

Administrative Update to Remove Federal Notes from the DLMS 867I Issue

18. 2/MEA01/160 Delete Federal Note:

Federal Note: Use any code.

19. 2/MEA02/160 Delete Federal Note:

Federal Note: Use any code.

20. 2/DD02/240 Change Federal Note to DLMS Note 1. Renumber existing DLMS Notes as DLMS 

Notes 2 and 3.

21. 2/LM/260 Change segment level Federal Note to DLMS Note.

22. 2/LQ/270 Change segment level Federal Note to DLMS Note.

23. 2/LQ01/270 Delete Federal Note:

Federal Note: Use any code.

24. 2/DTM/300 Merge Federal Note with DLMS Note, and revise as shown:

Federal Note: Use to identify dates associated with the UIT item.

DLMS Note:

Use to identify dates associated with the UIT item. If only a date of manufacture or 

warranty expiration date is required, express the required date in DTM01/02. If both 

dates are required, convey the date of manufacture in DTM01/02, and the warranty 

expiration date in DTM06.

25. 2/DTM01/300 Delete Federal Note:

Federal Note: Use any code.

26. 2/DTM06/300 Change Federal Notes 1 and 2 to DLMS Notes 1 and 2.

27. 2/N101/310 Delete Federal Note:

Federal Note: Use any code.

28. 2/N103/310 Delete Federal Note:

Federal Note: Use any code.

29. 2/FA2/350 Change Federal Note to DLMS Note 1. Number existing DLMS Note as DLMS Note 2.

30. 2/SE02/30 Change Federal Note to DLMS Note.