CATALOGING DATA AND TRANSACTION STANDARDS

VOLUME 8

DOCUMENT IDENTIFIER CODE INPUT / OUTPUT FORMATS (FIXED LENGTH)

**Originating Office:**	Enterprise Business Standards Office 

**Effective:**	March 2017

**VOLUME 8DOCUMENT IDENTIFIER CODE INPUT / OUTPUT FORMATS**

**(FIXED LENGTH)**

**CHANGE HISTORY**

Cataloging Data and Transaction Standards, Volume 8

Current as of March 2017

CHANGE HISTORY

# CHAPTER 1

**DOCUMENT IDENTIFIER CODE FORMAT**

## DOCUMENT IDENTIFIER CODE - LAB

TITLE - ADD U.S. NATIONAL/NATO STOCK NUMBER AS INFORMATIVE REFERENCE

DEFINITION - USED TO ADD A U.S. NATIONAL/NORTH ATLANTIC TREATY ORGANIZATION/FOREIGN COUNTRY STOCK NUMBER AS AN INFORMATIVE/SECONDARY REFERENCE TO AN ITEM IDENTIFICATION WITH MATCHING CHARACTERISTICS. A U.S. ACTIVITY DIRECT SUBMITTAL WHICH IS USED TO CROSS-INDEX A

U.S. ASSIGNED NSN AND A NATO/FC NSN, AS INFORMATIVE REFERENCES IN BOTH FLIS DATA BASE FILE PACKAGES AFTER IT IS DETERMINED THAT THEY ARE INTERCHANGEABLE ITEMS OF SUPPLY.

INSTRUCTIONS - FOR USE BY U.S. ACTIVITIES ONLY. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

**8.1-********1**

## DOCUMENT IDENTIFIER CODE - LAD

TITLE - ADD DATA ELEMENT(S)

DEFINITION - USED TO ADD ONE OR MORE DATA ELEMENTS TO AN EXISTING NSN. THOSE DATA ELEMENTS WHICH MAY BE ADDED BY THIS DIC ARE LIMITED -- SEE ATTACHED TABLE OF PERMISSIBLE DRNS.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.SEGMENT DATA ELEMENTS WILL NOT BE INCLUDED IN COMBINATION WITH OTHER SEGMENT DATA ELEMENTS. DATA ELEMENTS WILL BE SUBMITTED IN THE SEQUENCE REFLECTED ON THE TABLE OF PERMISSABLE DRNS. ADDITIONAL CARDS MAY BE REQUIRED FOR THE SEGMENTS. IF REQUIRED, THE SAME FORMAT AS THE FIRST CARD WILL BE USED. SEE VOLUME 10, SECTION 10.2.5 FOR EAM CARD USAGE GRID. ACTIONS WHICH INVOLVE SEGMENT G DATA WILL GENERATE AN OUTPUT DIC KVN ONLY.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

Segment for which data elements may be added are:

Data elements authorized to be added to the segments indicated above are as follows:

NOTE: DLA Logistics Information Service will process DIC LAD as DIC LCD when submitted data element is present on NSN in the FLIS data base. Transaction will process as DIC LAD with appropriate output DIC.

### 1. Identification Data, Segment A.

2. **MOE Rule Data, Segment B. DRN	Title**

 2871	Acquisition Method Code

 2876	Acquisition Method Suffix Code

 2507	Acquisition Advice Code

The Major Organizational Entity Rule Number DRN (8290) and the applicable MOE Rule Number is the mandatory first entry in an LAD transaction when any of the following segment B DRNs are being added:

### DRN	Title

 3/0099	Card Identification Code, Item Management Coding (IMC)

 1/3/2744	Item Management Code

 1/2748	Item Management Coding Activity

 0903	Depot Source of Repair

 2/2533	Supplementary Collaborator

 2/2534	Supplementary Receiver 1/See standard note NP

2/When DRNs 2533 and/or 2534 are submitted, they must be supplementary to those specified in the MOE Rule Number.

3/DRN 0099 is used to update IMC statistics only and is removed before recordation on the FLIS data base.

### 3. Freight Classification Data, Segment G.

4. **Catalog Management Data, Segment H. DRN	Title**

 #2128	Date, Effective, Logistics Action

 #2833	Major Organizational Entity Code

 #0137	Maintenance Action Code

 2934	Reparable Characteristics Indicator Code - DLA (Defense Logistics Agency)

 2892	Recoverability Code - Army

 2832	Material Control Code - Navy

 2655	Expendability, Recoverability, Reparability Category Code - AF (Air Force)

Mandatory data elements. For DRN 2833 and 0137, see chapter 8.4 , standard note AT. DRNs 2128, 2833, or 0137 are not required when a single segment R is input that contains DRN 0217 or 0794. Enter only the applicable DRN 2128, 2833, or 0137 value for either DRN 0217 or 0794.

Phrase Code R or Q must accompany and will dictate requirements for DRN 2893 . Phrase Codes N, V, and T, numerics and symbols when no replacement NSN is applicable, are permissible for this DIC.

NOTE: A maximum of 15 Phrase Codes will be accepted on this DIC.

### 5. Packaging Data, Segment W

**DOCUMENT IDENTIFIER CODE - LAF**

TITLE - ADD FREIGHT DATA

DEFINITION - USED TO ADD FREIGHT CLASSIFICATION DATA TO AN EXISTING NSN.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS, AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.THIS DIC IS AUTHORIZED FOR USE BY THE DESIGNATED ACTIVITIES WITHIN THE MILITARY SERVICES/AGENCIES WHEN AN INITIAL FREIGHT CLASSIFICATION DATA RECORD IS TO BE ESTABLISHED ON AN NSN.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LAM

TITLE - ADD CATALOG MANAGEMENT DATA

DEFINITION - A TRANSACTION SUBMITTED TO FLIS TO RECORD CATALOG MANAGEMENT DATA TO AN EXISTING NATIONAL ITEM IDENTIFICATION NUMBER (NIIN) RECORD.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.FROM A MILITARY SERVICE OR A RECORDED INTEGRATED MATERIEL MANAGER. THE LAD DIC CAN BE USED TO ADD ELEMENTS OF CATALOG MANAGEMENT DATA.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LAR

TITLE - ADD REFERENCE NUMBER AND RELATED CODES

DEFINITION - USED TO ADD A REFERENCE NUMBER AND ITS MANDATORY REFERENCE NUMBER CODES (I.E., RNAAC, DAC, RNCC, ETC.) TO AN EXISTING ITEM IDENTIFICATION (NSN/PSCN).

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REFER TO DIC LMD WHEN LAR IS TO BE ACCOMPANIED BY OTHER DIC(S) UNDER THE SAME DOCUMENT NUMBER.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3A03	D3A07	D3X00

## DOCUMENT IDENTIFIER CODE - LAS

TITLE - ADD STANDARDIZATION RELATIONSHIP

DEFINITION - USED TO ADD A STANDARDIZATION REPLACEMENT RELATIONSHIP REFLECTING THE REPLACEMENT NATIONAL STOCK NUMBER AUTHORIZED FOR PROCUREMENT THAT REPLACES AN NSN NOT AUTHORIZED FOR PROCUREMENT (ITEM STANDARDIZATION CODE 3 OR E) AND TO ESTABLISH GENERIC RELATIONSHIPS BETWEEN NSNS. SEGMENT E, USED AS INPUT TO AND OUTPUT FROM DLA LOGISTICS INFORMATION SERVICE, CONSISTS OF THE ELEMENTS OF DATA NECESSARY TO PORTRAY THE RELATIONSHIP OF NATIONAL ITEM IDENTIFICATION NUMBERS (NIINS) INVOLVED IN A STANDARDIZATION DECISION.

INSTRUCTIONS - THE ELEMENTS OF DATA COMPRISING THIS SEGMENT ARE CONTAINED ON A SINGLE CARD; HOWEVER, WHEN THREE OR MORE NSNS ARE INVOLVED IN A STANDARDIZATION RELATIONSHIP, SUFFICIENT ADDITIONAL SEGMENT E CARDS WILL BE REQUIRED TO ACCOMODATE ALL PERTINENT NSNS. A MAXIMUM OF 50 REPLACED NSNS AND ASSOCIATED DATA ELEMENTS MAY BE SUBMITTED UNDER ONE DOCUMENT CONTROL SERIAL NUMBER. (MULTIPLE REPLACEMENT NSNS ARE PROHIBITED.)

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LAU

TITLE - ADD MOE RULE NUMBER AND RELATED DATA

DEFINITION - USED TO ADD A MOE RULE NUMBER (WHICH REPRESENTS THOSE MANAGEMENT DATA ELEMENTS (I.E., PICA, SICA, ETC.) PRE-ESTABLISHED IN THE MOE RULE TABLE BY THE U.S. SERVICES/AGENCIES) TO AN EXISTING NSN. ALSO SUBMITTED CONCURRENTLY WITH THE MOE RULE NUMBER ARE THE ITEM MANAGEMENT STATUS CODES APPLICABLE TO THE ITEMS. ANY KNOWN SUPPLEMENTARY AUTHORIZED DATA COLLABORATORS/RECEIVERS APPLICABLE TO THE II (WHICH ARE NOT REPRESENTED BY THE MOE RULE NUMBER) MAY BE INCLUDED WHEN SUBMITTING THIS DIC.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.A MAXIMUM OF 60 MOE RULE NUMBERS MAY BE ADDED FOR A NIIN RECORD UNDER ONE DOCUMENT CONTROL NUMBER.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LBC

TITLE - REINSTATE PARTIAL DESCRIPTIVE METHOD II (NIIN ONLY)

DEFINITION - USED TO REINSTATE AN ITEM IDENTIFICATION (II) INTO THE FEDERAL CATALOG SYSTEM WHICH HAS BEEN PREVIOUSLY CANCELLED. APPLICABLE TO TYPE 4, 4A(M), OR 4B(N) REINSTATEMENTS ONLY.

INSTRUCTIONS - TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LBK

TITLE - REINSTATE REFERENCE METHOD II

DEFINITION - USED TO REINSTATE AN ITEM IDENTIFICATION (II) INTO THE FEDERAL CATALOG SYSTEM WHICH HAS BEEN PREVIOUSLY CANCELLED. APPLICABLE TO TYPE 2 REINSTATEMENTS ONLY (NATIONAL ITEM IDENTIFICATION NUMBER (NIIN) ONLY).

INSTRUCTIONS - TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LBR

TITLE - REINSTATE FULL DESCRIPTIVE METHOD II WITH REFERENCE NUMBER

DEFINITION - USED TO REINSTATE AN ITEM IDENTIFICATION (II) INTO THE FEDERAL CATALOG SYSTEM WHICH HAS BEEN PREVIOUSLY CANCELLED. APPLICABLE TO TYPE 1, 1A(K) AND 1B(L) REINSTATEMENTS (NATIONAL ITEM IDENTIFICATION NUMBER (NIIN) ONLY.)

INSTRUCTIONS - TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LBW

TITLE - REINSTATE FULL DESCRIPTIVE METHOD II WITHOUT REFERENCE NUMBER

DEFINITION - USED TO REINSTATE AN ITEM IDENTIFICATION (II) INTO THE FEDERAL CATALOG SYSTEM WHICH HAS BEEN PREVIOUSLY CANCELLED. APPLICABLE TO TYPE 1 REINSTATEMENTS ONLY (NATIONAL ITEM IDENTIFICATION NUMBER (NIIN) ONLY).

INSTRUCTIONS - TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LCC

TITLE - CHANGE CHARACTERISTICS DATA

DEFINITION - USED TO ADD, CHANGE OR DELETE FIIG SECTION I OR III CHARACTERISTICS DATA FOR AN EXISTING ITEM IDENTIFICATION REGARDLESS OF WHETHER THE DESCRIPTION UNDER THE ASSIGNED NATIONAL ITEM IDENTIFICATION NUMBER (NIIN) IS PARTIAL OR COMPLETE. REFER TO DIC LMD WHEN LCC IS ACCOMPANIED BY OTHER DICS UNDER THE SAME DOCUMENT NUMBER.

INSTRUCTIONS - TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LCD

TITLE - CHANGE DATA ELEMENT(S)

DEFINITION - USED TO CHANGE ONE OR MORE DATA ELEMENTS RECORDED ON AN EXISTING NSN. THOSE DATA ELEMENTS WHICH MAY BE CHANGED BY THIS DIC ARE LIMITED -- SEE ATTACHED TABLE OF PERMISSIBLE DRNS.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.SEGMENT DATA ELEMENTS WILL NOT BE INCLUDED IN COMBINATION WITH OTHER SEGMENT DATA ELEMENTS. DATA ELEMENTS WILL BE SUBMITTED IN THE SEQUENCE REFLECTED ON THE TABLE OF PERMISSIBLE DRNS. ADDITIONAL CARDS MAY BE REQUIRED FOR THE SEGMENTS. IF REQUIRED, THE SAME FORMAT AS THE FIRST CARD WILL BE USED. SEE VOLUME 10, SECTION 10.2.5 FOR EAM CARD USAGE GRID. ACTIONS WHICH INVOLVE SEGMENT G DATA WILL GENERATE AN OUTPUT DIC KVN ONLY.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## TABLE OF PERMISSIBLE DRNs

Segments for which data elements may be changed are:

Data elements authorized to be changed for the segments indicated above are as follows:

### 1. Identification Data, Segment A.

NOTE: DLA Logistics Information Service will process DIC LCD as DIC LAD if submitted data element is not present on NSN in FLIS data base. Except for DRNs 0903, 2533 and 2534. Transaction will process as DIC LCD with appropriate output DIC.

### 2. MOE Rule Data, Segment B.

The Major Organizational Entity Rule Number DRN (8290) and the applicable MOE Rule Number is the mandatory first entry in an LCD transaction when any of the following segment B DRNs are being changed: (The data elements must be submitted in sequence as reflected.)

### DRN	Title

 6/2128	Date, Effective, Logistics Action

 1/0099	Card Identification Code, Item Management Coding

 2/2871	Acquisition Method Code

 2/2876	Acquisition Method Suffix Code

 1/3/2744	Item Management Code

 3/#2748	Item Management Coding Activity

 7/0903	Depot Source of Repair

 7/0904	Former Depot Source of Repair

 4/2533	Supplementary Collaborator

 4/#2931	Former Supplementary Collaborator

 5/2534	Supplementary Receiver

 5/#2936	Former Supplementary Receiver

 2/2507	Acquisition Advice Code

 6/0076	Nonconsumable Item Material Support Code

#Informative data elements only (cannot be changed). LCD can be used to change the IMCA on a 01 or 02 only. This is for DIC LCD in FLIS, Volume 8, under #2 MOE Rule Data Segment B

1/DRN 0099 mandatory when submitting DRN 2744. DRN 0099 is used to update IMC statistics only and is removed before recordation on the FLIS data base.

2/DRN 2871, DRN 2876, DRN 2507 may be submitted as individual items. 3/See standard note NP ( chapter 8.4 ).

4/When DRN 2533 is submitted for change, it must be supplementary to the MOE Rule and DRN 2931 must also be submitted.

5/When DRN 2534 is submitted for change, it must be supplementary to the MOE Rule and DRN 2936 must also be submitted.

6/When DRN 0076 is submitted, DRN 2128 must also be submitted. DRNs 0903 and 0904 are the only DRNs that can be submitted with 0076 and 2128.

7/When DRN 0903 is submitted for a change, DRN 0904 must also be submitted. The order of DRNs is 0903s first, followed by 0904s.

NOTE: This DIC cannot be used to change a supplementary data receiver to a supplementary data collaborator or vice versa. To accomplish this type of action requires the submittal of LDD and LAD transactions.

### 3. Freight Classification Data, Segment G.

DRN 0864 can only be submitted by SDDC.

### 4. Catalog Management Data, Segment H. DRN	Title

 #2128	Date, Effective, Logistics Action

 #2833	Major Organizational Entity Code

 #0137	Maintenance Action Code

 2507	Acquisition Advice Code

 3690	Source of Supply Code

 2948	Source of Supply Modifier Code

 7075	Dollar Value, Unit Price

 6106	Quantity per Unit Pack Code

 2863	Controlled Inventory Item Code (CIIC)

 2943	Shelf Life Code

 2934	Reparable Characteristics Indicator Code - DLA (Defense Logistics Agency)

 2892	Recoverability Code - Army

 2832	Material Control Code - Navy

 2655	Expendability, Recoverability, Reparability Category Code - Air Force

 2891	Recoverability Code - Marine Corps

 2680	Materiel Category Code - Army

 2665	Accounting Requirements Code - Army

 2695	Fund Code - Air Force

 3765	Air Force Budget Code - Management Data List

### DRN	Title

 2836	Materiel Management Aggregation Code - Air Force

 2959	Stores Account - Marine Corps

 3311	Combat Essentiality Code - Marine Corps

 2790	Management Echelon Code - Marine Corps

 4126	Materiel Identification Code - Marine Corps

 0572	Operational Test Code - Marine Corps

 0573	Physical Category Code - Marine Corps

 2608	Cognizance Code - Navy

 2834	Special Material Identification Code

 0132	Issue, Repair, and/or Requisition Restriction Code

 0121	Special Material Content Code

 *0218	Unit of Issue Change Data

 0216	Former Phrase Relationship Group

 *2862	Phrase Code - Management Data List

 *8575	Quantitative Expression

 0858	Price Validation Code, Air Force

#Mandatory data elements. For DRN 2833 and 0137, see chapter 8.4 , standard note AT. DRNs 2128,2833, or 0137 are not required when a single segment R is input that contains DRN 0216 or 0218.

*DIC LCD may be used to initiate a Unit of Issue change only when the change is from a definitive to definitive Unit of Issue or from a nondefinitive to a nondefinitive Unit of Issue. For a Unit of Issue change, DRN 0218 is mandatory. For definition of chains, see Data Element Dictionary ( volume 12, chapter 12.4 ). DRN 2862 may only be used for Phrase Code K which must accompany, and will dictate requirements for, DRN 8575.

If DRN 0216 is entered in cc 41-44, the DRN Value will be entered in cc 46-79, and the Continuation Indicator Code (DRN 8555) in cc 80. A second card is required with cc 1-40 completed as instructed in the additional card format. The Data Element Terminator Code (DRN 8268) will be entered in cc 41, and cc 42-80 will be blank.

If DRN 2128 is entered in cc 41-44, the DRN Value will be entered in cc 46-50 and the Data Element Terminator Code (DRN 8268) in cc 51. Card columns 52-79 of card 1 and cc 41-79 of second (and succeeding) card(s) will contain the repeated data group composed of permissible DRN, DRN Value, and Data Element Terminator Code, as required.

If DRN 0218 is entered in cc 41-44, the DRN Value will be entered in cc 46-71, the Data Element Terminator Code (DRN 8268) in cc 72, cc 73-79 blank, and the Continuation Indicator Code (DRN 8555) in cc 80.

NOTE: A maximum of 15 Phrase Codes will be accepted on this DIC.

### 5. NIIN Status/Cancellation Data, Segment K.

**DRN	Title**

 0167	Demilitarization Code

### 6. Packaging Data, Segment W.

**DOCUMENT IDENTIFIER CODE - LCF**

TITLE - CHANGE FREIGHT DATA

DEFINITION - USED TO CHANGE FREIGHT DATA FOR AN EXISTING NSN.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS, AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.THIS DIC IS AUTHORIZED FOR USE BY THE DESIGNATED ACTIVITIES WITHIN THE MILITARY SERVICES/AGENCIES WHEN FREIGHT CLASSIFICATION DATA ELEMENTS ARE TO BE CHANGED ON AN EXISTING FREIGHT RECORD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LCG

TITLE - CHANGE FSC, ITEM NAME, TYPE OF ITEM IDENTIFICATION, OR RPDMRC

DEFINITION - USED TO CHANGE FEDERAL SUPPLY CLASS ONLY OR FSC WITH ANY COMBINATION OF CHANGES TO ITEM NAME, TYPE OF ITEM IDENTIFICATION, OR REFERENCE/PARTIAL DESCRIPTIVE METHOD REASON CODE FOR AN EXISTING ITEM IDENTIFICATION (NSN).

INSTRUCTIONS - SUBMIT THE COMBINATION OF DRNS REQUIRED TO ACCOMPLISH ACTION DEFINED. WHEN A CHANGE TO EITHER GUIDE NUMBER, ITEM IDENTIFICATION GUIDE (LCD) OR CHARACTERISTICS DATA (LCC) FOR AN ITEM IS ALSO INVOLVED, DIC LCD AND/OR LCC MUST BE USED UNDER AN LMD TRANSACTION. IF CONCURRENT LCC AND LCG PROCESSING IS REQUIRED, BOTH SHOULD BE SUBMITTED UNDER LMD. SEGMENT R MUST CONTAIN DRN 2128, DATE, EFFECTIVE, LOGISTICS ACTION. REFER TO DIC LMD WHEN LCG IS ACCOMPANIED BY OTHER DICS UNDER THE SAME DOCUMENT NUMBER.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LCI

TITLE - CHANGE NIIN STATUS CODE

DEFINITION - A TRANSACTION USED TO CHANGE THE NIIN (NATIONAL ITEM IDENTIFICATION NUMBER ) STATUS CODE ON AN EXISTING NSN.

INSTRUCTIONS - THIS DIC WILL CONSIST OF ONE CARD. THE STATUS CODE CAN BE CHANGED FROM 0 TO 1, 1 TO 0, 1 TO 9, 6 TO 9, OR 9 TO 6 (SEE VOLUME 10, TABLE 18 FOR NIIN STATUS CODES).

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3A08

## DOCUMENT IDENTIFIER CODE - LCM

TITLE - CHANGE CATALOG MANAGEMENT DATA

DEFINITION - A TRANSACTION SUBMITTED TO DLA LOGISTICS INFORMATION SERVICE TO CHANGE PREVIOUSLY SUBMITTED CATALOG MANAGEMENT DATA IN THE FLIS DATA BASE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.FROM A MILITARY SERVICE OR RECORDED INTEGRATED MATERIEL MANAGER, THE LCD DIC CAN BE USED TO CHANGE ELEMENTS OF CATALOG MANAGEMENT DATA.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LCR

TITLE - CHANGE REFERENCE NUMBER RELATED CODES

DEFINITION - USED TO CHANGE THE REFERENCE NUMBER CODE(S) RELATED TO A REFERENCE NUMBER RECORDED IN THE FLIS DATA BASE FOR AN EXISTING ITEM IDENTIFICATION (NSN). THE RNAAC, DAC, RNCC, RNVC AND SADC MAY BE CHANGED INDEPENDENTLY OR IN COMBINATION (I.E., RNACC AND DAC, RNCC AND RNVC, ETC.). THE RNCC CANNOT BE CHANGED TO C OR CHANGED FROM C WITH THIS DIC. THE REFERENCE NUMBER AND CAGE CANNOT BE CHANGED WITH THIS DIC. A COMBINATION OF AN LDR (DELETE REFERENCE NUMBER) AND AN LAR (ADD REFERENCE NUMBER) IS REQUIRED.

INSTRUCTIONS - WHEN USING THIS DIC, THE REFERENCE NUMBER AND CAGE FOR WHICH THE CHANGE(S) ARE APPLICABLE MUST BE REFLECTED ON THE “SEGMENT C” INPUT RECORD. REFER TO DIC LMD WHEN LCR IS ACCOMPANIED BY OTHER DICS UNDER THE SAME DOCUMENT NUMBER. THE JUSTIFICATION CODE CAN BE CHANGED OR ADDED, THROUGH THE USE OF DIC LCR.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3A03	D3A07	D3X00

## DOCUMENT IDENTIFIER CODE - LCS

TITLE - CHANGE STANDARDIZATION DECISION DATA FOR A REPLACED NSN, STANDARDIZATION RELATIONSHIP

DEFINITION - USED TO CHANGE THE ITEM STANDARDIZATION CODE (ISC), AND/OR ORIGINATOR, AND/OR DATE OF STANDARDIZATION OF A REPLACED NSN IN A STANDARDIZATION RELATIONSHIP; HOWEVER, THE ISC CAN ONLY BE CHANGED TO AN ISC THAT WILL RETAIN THE AFFECTED NSN IN A VALID STANDARDIZATION RELATIONSHIP. SEGMENT E, USED AS INPUT TO AND OUTPUT FROM FLIS, CONSISTS OF THE ELEMENTS OF DATA NECESSARY TO PORTRAY THE RELATIONSHIP OF NSNS INVOLVED IN A STANDARDIZATION DECISION.

INSTRUCTIONS - THE ELEMENTS OF DATA COMPRISING THIS SEGMENT ARE CONTAINED ON A SINGLE CARD. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LCU

TITLE - CHANGE MOE RULE NUMBER AND RELATED DATA

DEFINITION - USED TO CHANGE A MOE RULE NUMBER (WHICH REPRESENTS THOSE MANAGEMENT DATA ELEMENTS (I.E., PICA, SICA, ETC.) PRE-ESTABLISHED IN THE MOE RULE TABLE BY THE U.S. SERVICES/AGENCIES) RECORDED AGAINST AN EXISTING NSN OR NATO STOCK NUMBER TO A DIFFERENT MOE RULE NUMBER FOR THE SAME SERVICE/AGENCY OR TO A DIFFERENT SERVICE/AGENCY. FOR U.S. S/A ONLY, ALSO SUBMITTED CONCURRENTLY WITH THE MOE RULE NUMBER ARE THE ITEM MANAGEMENT STATUS CODES APPLICABLE TO THE ITEM. ANY KNOWN SUPPLEMENTARY AUTHORIZED DATA COLLABORATORS/RECEIVERS APPLICABLE TO THE II (WHICH ARE NOT REPRESENTED BY THE MOE RULE NUMBER) MAY BE INCLUDED WHEN SUBMITTING THIS DIC.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.A MAXIMUM OF 60 MOE RULES MAY BE CHANGED FOR A NIIN RECORD UNDER ONE DOCUMENT CONTROL NUMBER.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LCZ

TITLE - CHANGE ITEM STANDARDIZATION DECISION DATA NOT IN A STANDARDIZATION RELATIONSHIP

DEFINITION - USED TO CHANGE THE ITEM STANDARDIZATION CODE, AND/OR ORIGINATOR, AND/OR DATE OF STANDARDIZATION DECISION FOR AN NSN NOT INCLUDED IN A STANDARDIZATION RELATIONSHIP.

INSTRUCTIONS - THE ELEMENTS OF DATA COMPRISING THIS SEGMENT ARE CONTAINED ON A SINGLE CARD. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LDD

TITLE - DELETE DATA ELEMENT(S)

DEFINITION - USED TO DELETE ONE OR MORE DATA ELEMENTS RECORDED AGAINST AN EXISTING NSN. THOSE DATA ELEMENTS WHICH MAY BE DELETED ARE LIMITED -- SEE ATTACHED TABLE OF PERMISSIBLE DRNS.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.SEGMENT DATA ELEMENTS WILL NOT BE INCLUDED IN COMBINATION WITH OTHER SEGMENT DATA ELEMENTS. DATA ELEMENTS WILL BE SUBMITTED IN THE SEQUENCE REFLECTED ON THE TABLE OF PERMISSIBLE DRNS. ADDITIONAL CARDS MAY BE REQUIRED FOR THE SEGMENTS. IF REQUIRED, THE SAME FORMAT AS THE FIRST CARD WILL BE USED. SEE VOLUME 10, SECTION 10.2.5 FOR EAM CARD USAGE GRID AND INSTRUCTIONS. ACTIONS WHICH INVOLVE SEGMENT G DATA WILL GENERATE AN OUTPUT DIC KVN ONLY.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## TABLE OF PERMISSIBLE DRNs

Segments for which data elements may be deleted are:

Data elements authorized to be deleted from the segments indicated above are as follows:

### 1. Identification Data, Segment A. DRN	Title

 0167	Demilitarization (Demil) Code

 3843	Criticality Code

 2043	Electrostatic Discharge Code (ESDC)

 0801	Automatic Data Processing Equipment Identification Code (ADPEC).

### 2. MOE Rule Data, Segment B.

The Major Organizational Entity Rule Number DRN (8290) and the applicable MOE Rule Number are the mandatory first entry in an LDD transaction when the following segment B DRNs are being deleted:

### DRN	Title

 1/2533	Supplementary Collaborator

 1/2534	Supplementary Receiver

 2/0903	Depot Source of Repair

1/When DRN 2533 and/or 2534 are submitted, they must be supplementary to those specified in the MOE Rule Number.

2/A maximum of one Depot Source of Repair Code may be deleted. See Standard Note GQ ( Chapter 8.4 ).

### 3. Freight Classification Data, Segment G. DRN	Title

 2720	Hazardous Materiel Code

### DRN	Title

 2760	Less Than Carload Rating Code

 4760	Rail Variation Code

 0864	Integrity Code

### 4. Catalog Management Data, Segment H.

**DRN	Title**

 #2128	Date, Effective, Logistics Action

 #2833	Major Organizational Entity Code

 #0137	Maintenance Action Code

 2934	Reparable Characteristics Indicator Code - DLA (Defense Logistics Agency)

 2892	Recoverability Code - Army

 2832	Material Control Code - Navy

 2655	Expendability, Recoverability, Reparability Category Code - Air Force

 2891	Recoverability Code - Marine Corps

 2680	Materiel Category Code - Army

 2665	Accounting Requirements Code - Army

 2695	Fund Code - Air Force

 3765	Air Force Budget Code - Management Data List

 2836	Materiel Management Aggregation Code - Air Force

 2959	Stores Account - Marine Corps

 3311	Combat Essentiality Code - Marine Corps

 2790	Management Echelon Code - Marine Corps

 4126	Materiel Identification Code - Marine Corps

 0572	Operational Test Code - Marine Corps

 0573	Physical Category Code - Marine Corps

 2608	Cognizance Code - Navy

 2834	Special Material Identification Code

 0132	Issue, Repair, and/or Requisition Restriction Code

 0121	Special Material Content Code

 0217	Phrase Relationship Group

 *2862	Phrase Code - Management Data List

 *2893	Technical Document Number

 1/0794	I&S Jump to Code Relationship Group

 2895	Related National Stock Number

 0792	Jump to Code (JTC)

NOTE:

1. When submitting DRN 0794 data chain (I&S Jump to Code Relationship Group) to delete a JTC, the following criteria applies:

a. The NSN in the input header must be the Master NSN (DRN 0797), or Generic Master NSN (DRN 0796).

b. DRN 2895 (Related NSN) and DRN 0792 (JTC) are mandatory.

c. A maximum of 1 JTC will be accepted for this DIC.

d. A maximum of 15 Phrase Codes will be accepted on this DIC.

#Informative data elements. For DRN 2833 and 0137, see chapter 8.4 , standard note AT. DRNs 2128, 2833, or 0137 are not required when a single segment R is input that contains DRN 0217.

*Phrase Code R or Q must accompany, and will dictate requirements for, DRN 2893. Phrase Codes, numerics and symbols when no replacement NSN is applicable, are permissible for this DIC.

If DRN 0217 is entered in cc 41-44, the DRN Value will be entered in cc 46-66, the Data Element Terminator Code (DRN 8268) in cc 67, cc 68-79 blank and the Continuation Indicator Code (DRN 8555) in cc 80.

NOTE: A maximum of 15 Phrase Codes will be accepted on this DIC.

### 5. Packaging Data, Segment W.

**DRN	Title**

 5175	Special Packaging Instruction Number

 5176	SPI Revision

 5177	SPI Date

 5178	Container National Stock Number

 5179	Packaging Design Activity Code

## DOCUMENT IDENTIFIER CODE - LDF

TITLE - DELETE FREIGHT DATA

DEFINITION - USED TO DELETE FREIGHT CLASSIFICATION DATA FROM AN EXISTING NSN.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS, AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.THIS DIC IS AUTHORIZED FOR USE BY THE DESIGNATED ACTIVITIES WITHIN THE MILITARY SERVICES/AGENCIES WHEN A FREIGHT CLASSIFICATION DATA RECORD IS TO BE DELETED FROM AN NSN.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LDM

TITLE - DELETE CATALOG MANAGEMENT DATA

DEFINITION - A TRANSACTION SUBMITTED TO FLIS TO DELETE PREVIOUSLY SUBMITTED CATALOG MANAGEMENT DATA FROM THE FLIS DATA BASE.

INSTRUCTIONS - FROM A MILITARY SERVICE OR A RECORDED INTEGRATED MATERIEL MANAGER. THE LDD DOCUMENT IDENTIFIER CODE CAN BE USED TO DELETE ELEMENTS OF CATALOG MANAGEMENT DATA.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LDR

TITLE - DELETE REFERENCE NUMBER(S)

DEFINITION - USED TO DELETE A REFERENCE NUMBER(S) AND RELATED REFERENCE NUMBER CODES (I.E., RNAAC, DAC, RNCC, ETC.) RECORDED AGAINST AN EXISTING ITEM IDENTIFICATION (NSN).

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REFER TO DIC LMD WHEN LDR IS ACCOMPANIED BY OTHER DIC(S) UNDER THE SAME DOCUMENT NUMBER.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3A03	D3A07	D3X00

## DOCUMENT IDENTIFIER CODE - LDS

TITLE - DELETE STANDARDIZATION RELATIONSHIP

DEFINITION - USED TO DELETE A STANDARDIZATION RELATIONSHIP FROM THE SYSTEM. DELETION OF A RELATIONSHIP WILL REQUIRE A CHANGE TO THE ITEM STANDARDIZATION CODE OF THE REPLACED NSN, EXCEPT WHEN THE NSN IS IN A GENERIC RELATIONSHIP, AND MAY REQUIRE A CHANGE TO THE ITEM STANDARDIZATION CODE OF THE REPLACEMENT NSN. SEGMENT E, USED AS INPUT TO AND OUTPUT FROM DLA LOGISTICS INFORMATION SERVICE, CONSISTS OF THE ELEMENTS OF DATA NECESSARY TO PORTRAY THE RELATIONSHIP OF NATIONAL STOCK NUMBERS INVOLVED IN A STANDARDIZATION DECISION.

INSTRUCTIONS - THE ELEMENTS OF DATA COMPRISING THIS SEGMENT ARE CONTAINED ON A SINGLE CARD; HOWEVER, WHEN THREE OR MORE NSNS ARE INVOLVED IN A STANDARDIZATION RELATIONSHIP, SUFFICIENT ADDITIONAL SEGMENT E CARDS WILL BE REQUIRED TO ACCOMODATE ALL PERTINENT NSNS. WHEN A CHANGE TO THE ITEM STANDARDIZATION CODE (S) IS/ARE REQUIRED, ENTER THE NEW ITEM STANDARDIZATION CODE(S) AS APPLICABLE. A MAXIMUM OF 50 REPLACED NSNS AND ASSOCIATED DATA ELEMENTS MAY BE SUBMITTED UNDER ONE DOCUMENT CONTROL SERIAL NUMBER.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LDU

TITLE - DELETE MOE RULE NUMBER

DEFINITION - USED TO DELETE A MOE RULE NUMBER (WHICH REPRESENTS THOSE MANAGEMENT DATA ELEMENTS (I.E., PICA, SICA, ETC.) PREESTABLISHED IN THE MOE RULE TABLE BY THE U.S. SERVICES/AGENCIES) RECORDED AGAINST AN EXISTING NSN. IN ADDITION TO THE MOE RULE NUMBER, THE APPLICABLE ITEM MANAGEMENT STATUS CODES AND AUTHORIZED DATA COLLABORATORS/RECEIVERS WHICH ARE RECORDED AS SUPPLEMENTARY TO THE MOE RULE NUMBER BEING DELETED WILL ALSO BE REMOVED.

INSTRUCTIONS - A MAXIMUM OF 10 MOE RULE NUMBERS MAY BE SUBMITTED FOR DELETION FROM A NIIN RECORD UNDER ONE DOCUMENT CONTROL NUMBER.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LDZ

TITLE - DELETE LOGISTICS TRANSFER (DLA LOGISTICS INFORMATION SERVICE ONLY).

DEFINITION - USED BY THE ITEM STATUS PROGRAM MANAGER TO DELETE A LOGISTICS TRANSFER RECORDED AGAINST AN EXISTING NSN IN THE FUTURES FILE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.THESE PERMISSIBLE DRNS MUST BE ENTERED IN THE FOLLOWING ORDER: DRN 0131, DOCUMENT CONTROL NUMBER, FOLLOW-UP; DRN 3921, DOCUMENT IDENTIFIER CODE, INPUT; DRN 2128, DATE, EFFECTIVE, LOGISTICS ACTION; DRN 0733, DESTINATION ACTIVITY CODE FIELD, OUTPUT. ENTER VALUES FROM THE ORIGINAL TRANSACTION FOR DRNS 0131, 3921, AND 2128.SEE NOTE TS FOR THE VALUE TO BE ENTERED FOR DRN 0733.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LFN

TITLE - FOLLOW-UP INTERROGATION, NATO ONLY

DEFINITION - USED TO INTERROGATE THE STATUS OF A PREVIOUSLY SUBMITTED TRANSACTION FOR WHICH NO OUTPUT DATA HAS BEEN RECEIVED WITHIN THE REQUIRED TIME FRAME.

INSTRUCTIONS - FOR USE BY NORTH ATLANTIC TREATY ORGANIZATION (NATO) AND OTHER FOREIGN GOVERNMENTS ONLY.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3N02

## DOCUMENT IDENTIFIER CODE - LFU

TITLE - FOLLOW-UP INTERROGATION

DEFINITION - USED TO INTERROGATE THE STATUS OF A PREVIOUSLY SUBMITTED TRANSACTION WITHIN 60 DAYS OF ITS ORIGINAL TRANSMITTAL, FOR WHICH NOTIFICATION HAS NOT BEEN RECEIVED BY THE SUBMITTING ACTIVITY.

INSTRUCTIONS - NONE. MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LKD

TITLE - CANCEL-DUPLICATE

DEFINITION - USED TO CANCEL AN ITEM IDENTIFICATION AS A DUPLICATE OF ANOTHER ITEM IDENTIFICATION. INSTRUCTIONS - SEE VOLUME 10, TABLE 12.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

NOTE: When a stand alone LKD is processed, a system generated Phrase Code will automatically be added.

## DOCUMENT IDENTIFIER CODE - LKI

TITLE - CANCEL-INACTIVE (DLA LOGISTICS INFORMATION SERVICE ONLY)

DEFINITION - USED ONLY BY FLIS TO CANCEL-INACTIVE (NO RECORDED MOE RULE NUMBERS FOR FIVE YEARS) AN ITEM IDENTIFICATION (NATIONAL ITEM IDENTIFICATION NUMBER (NIIN) ONLY).

INSTRUCTIONS - NOT APPLICABLE. MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LKU

TITLE - CANCEL-USE

DEFINITION - USED TO CANCEL AN ITEM IDENTIFICATION TO “USE” ANOTHER ITEM IDENTIFICATION WHEN IT HAS BEEN DETERMINED THAT ONE CAN BE USED FOR THE OTHER EVEN THOUGH THEY ARE NOT EXACT DUPLICATES. (NATIONAL ITEM IDENTIFICATION NUMBER (NIIN) ONLY.)

INSTRUCTIONS - NOT APPLICABLE. MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

NOTE: When a stand alone LKU is processed, a system generated Phrase Code will automatically be added.

## DOCUMENT IDENTIFIER CODE - LKV

TITLE - CANCEL-INVALID

DEFINITION - USED TO CANCEL AN INVALID ITEM IDENTIFICATION (NATIONAL ITEM IDENTIFICATION NUMBER) (NIIN) WITHOUT REPLACEMENT.

INSTRUCTIONS - NOT APPLICABLE. MEDIA/FORMAT -

FUNCTIONAL DESCRIPTION SECTION -

NOTE: When a stand alone LKV is processed, a system generated Phrase Code will automatically be added.

## DOCUMENT IDENTIFIER CODE - LMD.A

TITLE - MULTIPLE DIC INPUT

DEFINITION - USED AS THE PRIMARY INPUT DIC WHEN MULTIPLE DIC TRANSACTIONS ARE SUBMITTED UNDER THE SAME DOCUMENT NUMBER FOR AN EXISTING ITEM IDENTIFICATION (II) (NIIN).

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS, AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2. THIS FORMAT REPRESENTS THE POSSIBLE SEGMENTS TO BE USED UNDER DIC LMD. REFER TO THE ATTACHED GRID FOR ALLOWABLE DIC COMBINATIONS. WHEN PREPARING THE LMD TRANSACTION REFER TO THE APPROPRIATE DIC FORMAT FOR APPLICABLE SEGMENTS, NUMBER OF CARDS FOR EACH SEGMENT AND NOTES REQUIRED. THE DIC LMD WILL APPEAR IN THE HEADER AND APPLICABLE COMBINATIONS OF DICS WILL BE ENTERED IN ALL SUBSEQUENT SEGMENTS. WHEN A LMD TRANSACTION INVOLVES A TRANSFER FROM TYPE 2 TO ANY DESCRIPTIVE TYPE OF II, THE GUIDE NUMBER, IIG (DRN 4065) AND CRITICALITY CODE, IIG (DRN 3843) ARE MANDATORY DATA ELEMENTS IN SEGMENT R OF DIC LCD. A LMD IS LIMITED TO A HEADER AND 9 TRANSACTIONS. 3.ALLOWABLE DIC COMBINATIONS ARE LIMITED TO LDR, LAR AND LCR IN THE LMD TRANSACTION FOR NATO AND OTHER FOREIGN COUNTRIES. AN LMD IS LIMITED TO A HEADER AND 9 TRANSACTIONS.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## MULTIPLE DIC INPUT

1. A combination of any of the following DICs may be included in an LMD package when applicable to system requirements. Combinations including two or more of the same DICs must contain at least one other different DIC. The following DICs may be submitted to FLIS in any sequence; however, FLIS will sequence and process them in the order reflected below:

a. LCG, LDD, LAD, LCD, LDU, LCU, LAU, LDR, LAR, LCR, LCC, LPA, LPC

b. LKD with LAD or LCM; LKU with LAD or LCM

c. LKV with LAD, LCM

d. LAU with LAM or LCM. The combination of DIC LAU with LAM or LCM will be used in accordance with the return code RJ edit/validation for DIC LAU in volume 11 .

e. LDU with LDM or LCM or LAD

(1) The combination of DIC LDU with CMD (LCM or LAD) must be used when the Delete MOE Rule (LDU) contains a Primary Inventory Control Activity Level of Authority (PICA LOA) of 01, 02, 06, 11, 15, 22, 23 (AZ), or 26 (military) and active CMD is currently recorded in the FLIS data base, and the MOE Rule is for the last recorded DoD/Civil manager on the item. LDM may only be used with LDU if the CMD is already inactive.

(2) The LMD must be submitted by the current item manager.

(3) The combination or DIC LDU with CMD (LCM or LAD) may be submitted by the SICA when the delete MOE Rule (LDU) contains a SICA LOA of 5D, 5G, 5H, 8C, 8D, 67, 68, 9D, 9G, 9H, 96 or 97 and active CMD is currently recorded in the FLIS.

f. LCU, LCU and LAU, LCU and LDU or LCU and LAU and LDU with LCM or LAM.

(1) The combination of DICs LDU/LCU/LAU with CMD (LCM or LAM) will be used when there is a logistics reassignment (including a change of PICA or PICA LOA) in accordance with the return code RJ edit/validation for DIC LCU in volume 11 .

(2) DIC LCG may be included in this combination when there is an FSC class change on the item involved in the logistics reassignment.

g. LCG with LCM.

h. Only one CMD record may be included in a single LMD package and will reflect a Maintenance Action Code of MM, MS, SS, or TG, or blank as appropriate.

i. All effective dated DICs within an LMD transaction must contain the same effective date. (Effective date standard time frames for concurrent submittal of item management decisions and catalog management data are listed in volume 10, table 145 .) NOTE: T-Moe Rules cannot be effective dated and therefore cannot be added or deleted in an LMD package with effective dated actions.

j. LCC, LCD (Segment A data elements i.e., type, IIG, etc.) and LCM to accommodate change type 2 or type 4 to a Full Descriptive Type II).

(1) Characteristic (DIC LCC) Segment V portion and Segment A (DIC LCD) may be effective dated immediately (on processing date). The Segment H portion of the transactions remains effective dated in the futures file until the effective date.

(2) The combination of DICs LCG, LCM, and LCC will be used to process a FSC change with CMD and characteristics changes. DIC LCC must be future effective dated along with the FSC and CMD change.

k. LCD with LCM

(1) The combination of DICs LCD (DEMIL Code Change) and LCM (CIIC Change) will be used to process a DEMIL Code and Controlled Inventory Item Code (CIIC) changes.

(2) The DEMIL position (LCD) will be processed immediately. The Segment H (LCM) CIIC portion of the transaction remains effective dated in the futures file until the effective date.

2. Data elements, when submitted, must be input in the following sequence within the DICs:

a. LCG, segment R. Assigned FSC (DRN 3990) Date, Effective, Logistics Action (DRN 2128) Item Name Code (DRN 4080) Item Name, Non-Approved (DRN 5020) Type of Item Identification Code (DRN 4820) Reference/Partial Descriptive Method Reason Code (DRN 4765)

b. LKD, segment T.

c. LKU, segment T.

d. LKV, segment T.

e. LDD, segment R.

(1) Segment B data elements. (Not acceptable in combination with segment A/H data elements if segment A/H data elements are contained in DICs LAD, LCD, or LDD. Segment B data elements (DIC LDD) are not acceptable in combination with DICs LAU, LCU, or LDU.) Supplementary Collaborator (DRN 2533)Supplementary Receiver (DRN 2534) Depot Source of Repair (DRN 0903)

(2) Segment H data elements, see DIC LDD format, this volume or volume 9 , for permissible sequence. (Not acceptable in combination with segment A/B data elements if segment A/B data elements are contained in DICs LAD, LCD, or LDD.)

f. LAD, segment R.

(1) Segment A data elements. (Not acceptable in combination with segment B/H data elements if segment B/H data elements are contained in DIC LAD, LCD, or LDD.)

(a) Reference/Partial Descriptive Method Reason Code (DRN 4765).

(b) Demilitarization Code (DRN 0167) - Applicable if LMD includes LAU containing initial recording of a Military Service MOE Rule.

(c) Electrostatic Discharge Code (FSDC) (DRN 2043)

(d) Precious Metals Indicator Code (PMIC) (DRN 0802)

(e) Automatic Data Processing Equipment Identification Code (ADPEC) (DRN 0801)

(f) Hazardous Material Indicator Code (0865)

(2) Segment B data elements. (Not acceptable in combination with segment A/H data elements if segment A/H data elements are contained in DIC LAD, LCD, or LDD. Segment B data elements (DIC LAD) are not acceptable in combination with DIC LAU, LCU, or LDU. NOTE: The combination of LAD and LDD cannot be included in this LMD package.

(a) Item Management Code (DRN 2744)

(b) Item Management Coding Activity (DRN 2748)

(c) Depot Source of Repair (DRN 0903)

(d) Supplementary Collaborator (DRN 2533)

(e) Supplementary Receiver (DRN 2534)

(3) Segment H data elements, see DIC LAD format, this volume or volume 9 , for permissible sequence. (Not acceptable in combination with segment A/B data elements if segment A/B data elements are contained in DIC, LAD, LCD, or LDD.)

g. LCD, segment R.

(1) Segment A data elements. (Not acceptable in combination with segment B/H data elements if segment B/H data elements are contained in DIC LAD, LCD, or LDD.)

(a) Guide Number, IIG (DRN 4065)

(b) Item Name Code, (DRN 4080) - If the LMD includes a concurrent LCG input, submit this data element in the LCG and do not duplicate it in the LCD.

(c) Item Name, Non-Approved (DRN 5020) - If the LMD includes a concurrent LCG input, submit this data element in the LCG and do not duplicate it in the LCD.

(d) Type of Item Identification Code (DRN 4820) - If the LMD includes a concurrent LCG input, submit this data element in the LCG and do not duplicate it in the LCD.

(e) Reference/Partial Descriptive Method Reason Code (DRN 4765) - If the LMD includes a concurrent LCG input, submit this data element in the LCG and do not duplicate it in the LCD.

(f) Demilitarization Code (DRN 0167) - Applicable to initially add or change an existing DEMIL Code if the LMD includes an LAU containing initial recording of a Military Service MOE Rule.

(g) Criticality Code, IIG (DRN 3843).

(h) Hazardous Material Indicator Code (DRN 0865)

(i) Electrostatic Discharge Code (ESDC) (DRN 2043)

(j) Precious Metals Indicator Code (PMIC) (DRN 0802)

(k) Automatic Data Processing Equipment Identification Code (ADPEC) (DRN 0801)

(2) Segment B data elements. (Not acceptable in combination with segment A/H data elements if segment A/H data elements are contained in DIC LAD, LCD, or LDD. Segment B data elements (DIC LCD) are not acceptable in combination with DIC LAU, LCU, or LDU.)

(a) Acquisition Method Code (DRN 2871)

(b) Acquisition Method Suffix Code (DRN 2876)

(c) Date, Effective, Logistics Action (DRN 2128)

(d) Item Management Code (DRN 2744)

(e) Item Management Coding Activity (DRN 2748)

(f) Depot Source of Repair (DRN 0903)

(g) Supplementary Collaborator (DRN 2533)

(h) Former Supplementary Collaborator (DRN 2931)

(i) Supplementary Receiver (DRN 2534)

(j) Former Supplementary Receiver (DRN 2936)

(k) Nonconsumable Item Material Support Code (DRN 0076)

(3) Segment H data elements, see DIC LCD format, this volume or volume 9 , for permissible sequence. (Not acceptable in combination with segment A/B data elements if segment A/B data elements are contained in DIC LAD, LCD, or LDD.)

h. LDU, segment T.

i. LCU, segment B.

j. LAU, segment B.

k. LDM, segment H.

l. LCM, segment H.

m. LAM, segment H.

n. LDR, LAR, LCR, segment C. A maximum of 30 reference numbers may be submitted under the same Document Control Number. If a combination of LAR/LCR/LDR transactions is submitted, the combined total of reference numbers cannot exceed 30.

o. LCC, segments A and V. Segment A will contain IIG and Item Name Code or Item Name, Non- Approved (when applicable). Utilize the “change to” IIG and Item Name Code or Item Name, Non-Approved if they are being changed within the same LMD; otherwise use the recorded FLIS data elements. The Guide number, IIG or item name data in these A segments will not change the FLIS data base. If they require change, include the Guide Number, IIG in the R segment of DIC LCD and the name data in the R segment of DIC LCG (if an FSC change is also involved) or LCD (if no FSC change is involved).

p. All effective dated DICs within an LMD transaction must contain the same effective date.

3. The following example provides a guide for the preparation of LMD transactions:

a. FLIS Input Header (DRN 9094) reflecting “LMD” in card columns 1-3

b. When the first DIC following the input header is an LAU transaction:

(1) Card columns 1-3 will reflect “LAU”.

required.

(2) Card columns 4-6 will reflect the appropriate Package Sequence Number.

(3) Card columns 7-39 will reflect the same data as the input header card.

(4) Refer to DIC LAU format for completion of card columns 40 through 80 and continuation card, if

c. If the second DIC input is an LAD transaction:

(1) Card columns 1-3 will reflect “LAD”.

(2) Card columns 4-6 will reflect the appropriate PSN.

(3) Card columns 7-39 will reflect the same data as the input header card.

(4) Refer to DIC LAD format for completion of the LAD transaction.

4. Output resulting from processing an LMD package will be produced as follows:

a. On the date of processing output will reflect:

(1) When multiple reference number transactions are included on input, file maintenance KDR, KAR, and KCR will be generated in that sequence within DIC KMD. If only one reference number transaction (LDR or LAR or LCR) was input under LMD, KMD will not be output. The appropriate KDR or KAR or KCR will be output.

(2) Informative Data for Pending Effective Dated Actions, KIF, will be output with segment Z in the following DIC sequence of LCG, LCD, LDU, LAU, LCU, and LCC (which contains DRN 9111 only with no values to indicate that characteristics have been deleted, added, or changed). The submitted DRNs and values will be output in the same sequence as applicable to input.

b. On the effective date of the submitted package, file maintenance will be furnished in the following DIC sequence:

KMD, KCG, KDD, KAD, KCD, KDU, KAU, KCU, and KTD

(If only characteristics data transactions were submitted within an LMD not including any other actions, output on processing date will be KTD. KMD will not be in the header record.)

c. Output from concurrent submittal of item management decisions and catalog management data is outlined in volume 6, appendix 6-2-B .

d. Output resulting from segment H data submitted in an LMD will reflect the segment H DIC contained in the LMD as the input DIC.

5. The submitter of an LMD which contains CMD may not be the activity which would normally submit the CMD. Therefore, CMD submitted in an LMD will be edited/processed as though it were submitted in accordance with the following criteria:

### Condition	Submitter

Cancellations	Activity which submitted last Integrated Materiel Manager/ Lead Service CMD

Withdrawal of last DoD Manager	Activity which submitted last IMM/ Lead

Service CMD

FSC Changes	Activity which submitted last IMM/ Lead Service CMD

LN_, LB_	*

Reactivation	*

Logistics Transfers	*

### * Service/Agency Submitting	Change to this Submitter

DLA	PICA Activity

GSA	75

Army	PICA Activity, unless the PICA is AT or AV, then change to BS.

Marine Corps	PA

Navy	HD, HW, HX, JG, JN, or KE if PICA; GM for all other Navy PICAs

Air Force	SJ, SP, or ST if PICA, TW for all other Air Force PICAs

Coast Guard	PICA Activity

NOTE: The activity determined to be the CMD submitter by the above criteria will be reflected as the Submitting Activity Code in the document control number on the resulting CMD output.

## DOCUMENT IDENTIFIER CODE - LMD.B

TITLE - NATO MULTIPLE DIC INPUT

DEFINITION - DIC LMD WILL BE USED BY NORTH ATLANTIC TREATY ORGANIZATION (NATO) CODIFICATION BUREAUS AS A DIRECT SUBMITTAL. IT IS USED AS THE PRIMARY INPUT DIC WHEN MULTIPLE DIC TRANSACTIONS (LDR, LCR, LAR) ARE SUBMITTED UNDER THE SAME DOCUMENT NUMBER FOR A U.S. ASSIGNED NATIONAL STOCK NUMBER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS, AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

2.ALLOWABLE DIC COMBINATIONS ARE LIMITED TO LDR, LAR AND LCR IN THE LMD TRANSACTION FOR NATO AND OTHER FOREIGN COUNTRIES. AN LMD IS LIMITED TO A HEADER AND 9 TRANSACTIONS.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LMX

TITLE - MULTIPLE NSN INPUT

DEFINITION - USED AS THE PRIMARY INPUT DIC WHEN MULTIPLE NSN TRANSACTIONS (NECESSARY TO ESTABLISH/MAINTAIN I&S DATA) ARE SUBMITTED UNDER THE SAME DOCUMENT NUMBER FOR AN I&S FAMILY/GROUP MASTER NSN.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.WHEN PREPARING THE LMX TRANSACTION THE ALLOWABLE DIC COMBINATIONS AND APPLICABLE SEGMENTS ARE IDENTIFIED IN THE INSTRUCTIONS FOLLOWING THE FORMAT BELOW.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## MULTIPLE I&S FAMILY NSN INPUT

1. A maximum of fifty different NSNs may be submitted in an LMX package.

2. Each NSN included in an LMX package must meet one of the following conditions:

a. Currently recorded in a DoD I&S Family.

b. Being added to a DoD I&S Family.

3. Any one of the following DICs may be submitted for a NSN in an LMX package: LAU, LCU, LDU, LAM, LCM, LKU, LMD.

a. If DIC LMD is used within an LMX it may include any of the following DICs: LAU, LCU, LDU, LCG, LAM, LCM, LKU.

(1) Any combination of DICs LAU/LCU/LDU.

(2) Any combination of DICs LDU/LCU/LAU with CMD (LCM or LAM) must be in accordance with the Return Code RJ edit/validation in volume 11 . DIC LCG may be included in this combination when there is an FSC class change on an item involved in a logistics reassignment, but not characteristic data change needed.

(3) LCG with LCM.

(4) Only one CMD record may be included in a single LMD package and will reflect a Maintenance Action Code of MM, MS, SS or blank as appropriate.

b. Output from concurrent submittal of item management decisions and Catalog Management Data (CMD) is outlined in volume 6, appendix 6-2-B .

c. Output resulting from Segment H data submitted in an LMD will reflect the Segment H DIC contained in the LMD as the input DIC.

4. Data elements, when submitted, must be input in the following sequence within the DICs:

a. LCG, Segment R.

Assigned FSC (DRN 3990) Date, Effective, Logistics Action (DRN 2128) DIC LMX

b. LDU, Segment T.

c. LCU, Segment B.

d. LAU, Segment B.

e. LCM, Segment H.

f. LAM, Segment H.

5. If DIC LAM or LCM is submitted against any NSN contained within an LMX transaction, each NSN in the LMX transaction must have a DIC LAM or LCM submitted against it.

6. All DICs within an LMX package must contain the same effective date.

7. The LMX Input Header as well as the header for the first DIC following the input header must reflect the I&S Family Master NSN whose Order of Use, DRN 0793, is being established, changed, or deleted.

8. The following example provides a guide for the preparation of LMX transactions:

a. FLIS input header (DRN 9094) reflecting “LMX” as submitted DIC and the I&S Family Master NSN as the submitted NSN.

b. When the first DIC following the input header is an LMD transaction:

(1) FLIS input header (DRN 9094) consisting of “LMD” as DIC, I&S Family Master NSN as NSN and appropriate Package Sequence Number (PSN).

(2) Refer to DIC LMD format for completion of LMD transaction.

c. If second DIC input is an LCM transaction:

(1) FLIS input header (DRN 9094) consisting of “LCM” as DIC, I&S Related NSN as NSN and appropriate PSN.

(2) Refer to DIC LCM format for completion of LCM transaction.

9. Output resulting from processing an LMX transaction will be produced in accordance with procedures for output that the allowable DICs would receive if submitted independently of an LMX transaction.

10. If any DIC in an LMX transaction is invalid, the entire LMX transaction is rejected.

11. The submitter of an LMX which contains CMD may not be the activity which would normally submit the CMD. Therefore, CMD submitted in an LMX will be edited/processed as though it were submitted in accordance with the following criteria:

### Condition	Submitter

Withdrawal of last DoD Manager

Activity which submitted last IMM/Lead Service CMD

### Condition	Submitter

FSC Changes	Activity which submitted last IMM/Lead Service CMD

Logistics Transfers

DLA	PICA Activity

GSA	75

Army	PICA Activity

Marine Corps	PA

Navy	HD, HH, HW, HX, JG, JS, or KE if

PICA; GM for all other Navy PICAs

Air Force	SJ, SP, or ST if PICA; TW for all other Air Force PICAs

NOTE: The activity determined to be the CMD submitter by the above criteria will be reflected as the Submitting Activity Code on the resulting CMD output.

NOTE: When DIC LCG is submitted in a DIC LMX, there must be a DIC LCG for each NSN (for all family members) in the PICA's I&S Family.

## DOCUMENT IDENTIFIER CODE - LNC

TITLE - REQUEST FOR NIIN ASSIGNMENT (PARTIAL DESCRIPTIVE METHOD)

DEFINITION - USED TO SUBMIT A PROPOSED ITEM IDENTIFICATION FOR NIIN ASSIGNMENT. APPLICABLE TO TYPE 4, 4A(M), AND 4B(N) PROPOSALS ONLY.

INSTRUCTIONS - TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LNK

TITLE - REQUEST FOR NIIN ASSIGNMENT (REFERENCE METHOD)

DEFINITION - USED TO SUBMIT A PROPOSED ITEM IDENTIFICATION FOR NIIN ASSIGNMENT. APPLICABLE TO TYPE 2 PROPOSALS.

INSTRUCTIONS - TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.1-********109**

## DOCUMENT IDENTIFIER CODE - LNR

TITLE - REQUEST FOR NIIN ASSIGNMENT (FULL DESCRIPTIVE METHOD WITH REFERENCE NUMBERS)

DEFINITION - USED TO SUBMIT A PROPOSED ITEM IDENTIFICATION FOR NIIN ASSIGNMENT. APPLICABLE TO TYPE 1, 1A(K) AND 1B(L) PROPOSALS.

INSTRUCTIONS - TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LNW

TITLE - REQUEST FOR NIIN ASSIGNMENT (FULL DESCRIPTIVE METHOD WITHOUT REFERENCE NUMBERS)

DEFINITION - USED TO SUBMIT A PROPOSED ITEM IDENTIFICATION FOR NIIN ASSIGNMENT. APPLICABLE TO TYPE 1 PROPOSALS.

INSTRUCTIONS - TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.1-********119**

## DOCUMENT IDENTIFIER CODE - LPA

TITLE - ADD PACKAGING DATA

DEFINITION - USED TO ADD PACKAGING DATA TO AN EXISTING NSN FOR A MILITARY SERVICE OR AGENCY INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELMENTS IN THE FIXED DIC FORMAT

BELOW. THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.THIS DOCUMENT IDENTIFIER CODE IS FOR USE BY SUPPLEMENTARY SUBMITTERS ONLY. (PICA, SICA OR ACTIVITY CODE AN)

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

C. THIRD CARD WILL BE CODED L IF A FOURTH CARD IS REQUIRED OR IF NOT REQUIRED USE CODE 3.

D. FOURTH CARD WILL BE CODED M IF A FIFTH CARD IS REQUIRED OR IF NOT REQUIRED USE CODE 4.

E. FIFTH CARD WILL BE CODED 5.

## DOCUMENT IDENTIFIER CODE - LPC

TITLE - CHANGE PACKAGING DATA

DEFINITION - USED TO ADD OR CHANGE PACKAGING DATA TO AN EXISTING NSN FOR MILITARY SERVICE OR AGENCY

INSTRUCTIONS - 1. TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN ARE REQUIRED IN POSITION 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.THIS DOCUMENT IDENTIFIER CODE IS FOR USE BY SUPPLEMENTARY SUBMITTERS ONLY (PICA, SICA OR ACTIVITY CODE AN).

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

NOTE: CONTINUATION INDICATOR CODES WILL BE ASSIGNED AS FOLLOWS:

A. FIRST CARD WILL BE CODED J .

B. SECOND CARD WILL BE CODED K .

C. THIRD CARD WILL BE CODED L IF A FOURTH CARD IS REQUIRED OR IF NOT REQUIRED USE CODE 3 .

D. FOURTH CARD WILL BE CODED M

E. FIFTH CARD WILL BE CODED 5 .

## DOCUMENT IDENTIFIER CODE - LPD

TITLE - DELETE PACKAGING DATA

DEFINITION - USED TO DELETE PACKAGING DATA TO AN EXISTNG NSN FOR MILITARY SERVICE OR AGENCY INSTRUCTIONS - THIS DOCUMENT IDENTIFIER CODE IS SUPPLEMENTARY FOR USE BY THE (PICA, PICA

SUPPLEMENTARY SUBMITTER, SICA OR ACTIVITY CODE AN) MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LSA

TITLE - REQUEST FOR CODIFICATION AND FOR REGISTRATION OF USER

DEFINITION - A MAILED REQUEST FOR SEARCH AND CODIFICATION OF AN ITEM AND USER REGISTRATION FOR THE CORRESPONDINNG ITEM IDENTIFICATION. USED TO REQUEST THE CODIFICATION OF AN ITEM IDENTIFIED BY THE REFERENCE NUMBER(S) AND THE RELATED MANUFACTURERS CODE(S) AND TO REGISTER THE REQUESTING COUNTRY AS A USER OF THE CORRESPONDING ITEM IDENTIFICATION.

INSTRUCTIONS - 1.IN THE LSA TRANSACTION PACKAGE, THE CONTROL DATA ELEMENTS REQUIRED IN EACH CARD IMAGE OF ALL SEGMENTS ARE SHOWN BELOW IN POSITIONS 1-23.THE PSN (DRN 1070) IN CC 4-6 SHALL BE INCREMENTED BY ONE (1) IN EACH CARD. THE INFORMATION IN POSITIONS 37 AND 39 SHALL APPEAR IN THE CARD(S) CONTAINING A REFERENCE NUMBER BUT NOT IN THE SUBSEQUENT CARD CONTAINING THE NAIN OR INC AND/OR FSC. 2.THE SEGMENT 2 RECORD CONTAINING THE NAIN OR INC AND FSC SHALL BE SUBMITTED ONLY ONCE FOR EACH LSA. IT SHALL BE THE LAST SEGMENT 2 RECORD AND SHALL APPLY TO ALL PRECEDING SEGMENT 2 RECORDS CONTAINING A REFERENCE NUMBER. THE CONTINUATION INDICATOR CODE (CIC) FIELD (CC 80) FOR THE LAST RECORD SHALL CONTAIN THE NUMBER 2 (TWO). THE PRECEDING SEGMENT 2 RECORD SHALL CONTAIN THE LETTER J IN THE CIC FIELD. THE CIC SHALL BE 1 FOR ANY RECORD THAT MAY PRECEDE THE RECORD CONTAINING J IN THE CIC FIELD. 3.TO BE USED BY NATIONAL CODIFICATION BUREAU ONLY. 4.THE CODIFYING COUNTRY IS NOT OBLIGATED TO USE THE INC/NAIN/FSC REFLECTED IN THIS TRANSACTION.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.1-********129**

## DOCUMENT IDENTIFIER CODE - LSB

TITLE - REQUEST FOR CODIFICATION AND FOR REGISTRATION ON NON-U.S. MANUFACTURED ITEMS

DEFINITION - REQUEST FOR U.S. ACTIVITIES FOR NORTH ATLANTIC TREATY ORGANIZATION (NATO) REFERENCE NUMBER SEARCH OF THE FLIS DATA BASE OR SUBSEQUENT CODIFICATION BY NATO NATIONAL CODIFICATION BUREAU (NCB) IF THERE IS NO CORRESPONDING ITEM IDENTIFICATION BY THE FLIS DATA BASE.

INSTRUCTIONS - 1.IN THE LSB TRANSACTION PACKAGE, THE CONTROL DATA ELEMENTS REQUIRED IN EACH CARD IMAGE OF ALL SEGMENTS ARE SHOWN BELOW IN POSITIONS 1-23.THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. FOR SEGMENT 2 ONLY, THE INFORMATION IN POSITIONS 37 AND 39 SHALL APPEAR IN THE CARD(S) CONTAINING A REFERENCE NUMBER BUT NOT IN THE SUBSEQUENT CARD CONTAINING THE DEMIL CODE/IN/NAIN/FSC. FOR SEGMENTS B AND H, POSITIONS 24-39 SHALL BE BLANK. 2.THE SEGMENT 2 RECORD CONTAINING THE DEMIL CODE/INC/NAIN/FSC SHALL BE SUBMITTED ONLY ONCE FOR EACH LSB. IT SHALL BE THE LAST SEGMENT 2 RECORD AND SHALL APPLY TO ALL PRECEDING SEGMENT 2 RECORDS CONTAINING A REFERENCE NUMBER. THE CONTINUATION INDICATOR CODE (CIC) FIELD (CC 80) OF THE LAST SEGMENT 2 RECORD SHALL CONTAIN THE NUMBER 2 (TWO). THE PRECEDING SEGMENT 2 RECORD SHALL CONTAIN THE LETTER J IN THE CIC FIELD. THE CIC SHALL BE 1 FOR ANY RECORD THAT MAY PRECEDE THE RECORD CONTAINING A J IN THE CIC FIELD. 3.THE CODIFYING COUNTRY IS NOT OBLIGATED TO USE THE INC/NAIN/FSC REFLECTED IN THIS TRANSACTION.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LSF

TITLE - SEARCH BY NATIONAL ITEM IDENTIFICATION NUMBER

DEFINITION - USED TO SEARCH BY NIIN IN SUPPORT OF PROVISIONING AND OTHER PREPROCUREMENT REQUIREMENTS TO DETERMINE THE VALIDITY OF THE NIIN AND EXTRACT THE APPLICABLE FLIS DATA BASE DATA.

INSTRUCTIONS - REFER TO VOLUME 10, TABLE 30 TO DETERMINE THE OUTPUT DATA REQUEST CODE (DRN 4690) WHICH REPRESENTS THE SEGMENTS OF DATA REQUIRED TO BE EXTRACTED FROM THE FLIS DATA BASE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LSN

TITLE - SEARCH BY REFERENCE NUMBER FOR OTHER THAN PROVISIONING AND PREPROCUREMENT

DEFINITION - USED TO SUBMIT REFERENCE NUMBERS TO BE SCREENED AGAINST THE FLIS DATA BASE TO DETERMINE IF THE REFERENCE NUMBER IS RELATED TO AN EXISTING ITEM IDENTIFICATION.

INSTRUCTIONS - REFER TO VOLUME 10, TABLE 30 TO DETERMINE THE OUTPUT DATA REQUEST CODE (DRN 4690) WHICH REPRESENTS THE SEGMENTS TO BE EXTRACTED FROM THE FLIS DATA BASE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LSR

TITLE - SEARCH BY REFERENCE NUMBER

DEFINITION - USED TO SUBMIT REFERENCE NUMBERS TO BE SCREENED AGAINST THE FLIS DATA BASE TO DETERMINE IF THE REFERENCE NUMBER IS RELATED TO AN EXISTING ITEM IDENTIFICATION.

INSTRUCTIONS - REFER TO VOLUME 10, TABLE 30 TO DETERMINE THE OUTPUT DATA REQUEST CODE (DRN 4690) WHICH REPRESENTS THE SEGMENTS OF DATA REQUIRED TO BE EXTRACTED FROM THE FLIS DATA BASE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LSS

TITLE – DLA TRANSPORTATION SERVICES CRITICAL SOURCE OF SUPPLY UPDATE

DEFINITION - USED TO ADD A NEW OR CHANGE AN EXISTING SOURCE OF SUPPLY. THIS DIC WILL BE USED ONLY WHEN THE SOURCE OF SUPPLY TO BE ADDED OR CHANGED IS CONSIDERED A CRITICAL (TYPE II) UPDATE.

INSTRUCTIONS - THIS DIC IS AUTHORIZED FOR USE BY DLA LOGISTICS INFORMATION SERVICE PROGRAM MANAGERS AND AUTHORIZED SERVICES/AGENCIES.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3F07	D3X00

## DOCUMENT IDENTIFIER CODE - LTI

TITLE - INTERROGATE BY NIIN

DEFINITION - USED TO INTERROGATE FOR COMPLETE OR SELECTED FILE DATA RECORDED AGAINST A SPECIFIC ITEM.

INSTRUCTIONS - REFER TO VOLUME 10, TABLE 34 TO SELECT THE APPLICABLE OUTPUT DATA REQUEST CODE DRN OR TO TABLE 35 FOR THE INDIVIDUAL DATA ELEMENT DRN WHICH REPRESENTS THE FLIS DATA BASE DATA BEING INTERROGATED. SUBMIT THE DRNS ASSIGNED TO THE INDIVIDUAL DATA ELEMENTS, COMBINATION OF SEGMENTS, OR ACCESS KEY DATA ELEMENTS. SEGMENT R MAY BE REPEATED A MAXIMUM OF THREE (3) TIMES IN ORDER TO ACQUIRE THE REQUIRED MIX OF SEGMENTS OR INDIVIDUAL DATA ELEMENTS TO BE EXTRACTED. IN SEGMENT R ON AN INTERROGATION TRANSACTION (LTI), DATA RECORD NUMBER (DRN 0950) ONLY WILL BE SUBMITTED.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LTU

TITLE - ADD NUCLEAR ORDNANCE SOURCE OF SUPPLY

DEFINITION - USED TO ADD A SOURCE OF SUPPLY CODE(S). THIS DIC WILL BE USED ONLY BE DEFENSE NUCLEAR AGENCY TO ADD A SOURCE OF SUPPLY.

INSTRUCTIONS - THIS DIC IS AUTHORIZED FOR USE BY DEFENSE NUCLEAR AGENCY ONLY. ENTER DRN 0296 (SPECIAL SOURCE OF SUPPLY) IN CC 41-44.THIS INPUT DATA GROUP CONSISTS OF THE FOLLOWING DRNS WITH REPLIES IN THE CARD COLUMNS INDICATED: CC 46-50 DATE, EFFECTIVE, LOGISTICS ACTION, DRN 2128, (ALWAYS ZERO EFFECTIVE DATED), CC 51-62 SOURCE OF SUPPLY CODE/PSEUDO SOURCE OF SUPPLY CODE, DRN 3690/0133 (E.G., CC 51-53 INTEGRATED MATERIEL MANAGER (IMM) FIELD, CC 54-56 AIR FORCE FIELD, CC 57-59 ARMY FIELD, CC 60-62 NAVY FIELD): CC 63-64 NAVY SPECIAL SOURCE OF SUPPLY CODE, DRN 0135.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LTV

TITLE - CHANGE NUCLEAR ORDNANCE SOURCE OF SUPPLY

DEFINITION - THIS DIC WILL BE USED TO CHANGE SPECIFIC SOURCE OF SUPPLY CODE(S) FOR A NUCLEAR ORDNANCE ITEM TO ANOTHER SOURCE OF SUPPLY CODE(S), OR TO CHANGE THE FEDERAL SUPPLY CLASS (FSC) RELATED TO THE SOURCE OF SUPPLY.

INSTRUCTIONS - THIS DIC IS AUTHORIZED FOR USE BY DEFENSE NUCLEAR AGENCY ONLY. ENTER DRN 0296 (SPECIAL SOURCE OF SUPPLY) IN CC 41-44.THIS INPUT DATA GROUP CONSISTS OF THE FOLLOWING DRNS WITH REPLIES IN THE CARD COLUMNS INDICATED: CC 46-50 DATE, EFFECTIIVE, LOGISTICS ACTION, DRN 2128, (ALWAYS ZERO EFFECTIVE DATED), CC 51-62 SOURCE OF SUPPLY CODE/PSEUDO SOURCE OF SUPPLY CODE, DRN 3690/0133 (E.G., CC 51-53 INTEGRATED MATERIEL MANAGER (IMM) FIELD, CC 54-56 AIR FORCE FIELD, CC 57-59 ARMY FIELD, CC 60-62 NAVY FIELD), CC 63-64 NAVY SPECIAL SOURCE OF SUPPLY CODE, DRN 0135.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.1-********135**

## DOCUMENT IDENTIFIER CODE - LTW

TITLE - DELETE NUCLEAR ORDNANCE SOURCE OF SUPPLY

DEFINITION - THIS DIC WILL BE USED TO INACTIVATE/DELETE SOURCE OF SUPPLY CODE(S) FOR A NUCLEAR ORDNANCE ITEM.

INSTRUCTIONS - THIS DIC IS AUTHORIZED FOR USE BY DEFENSE NUCLEAR AGENCY ONLY. ENTER DRN 0296 (SPECIAL SOURCE OF SUPPLY) IN CC 41-44.THIS INPUT DATA GROUP CONSISTS OF THE FOLLOWING DRNS WITH REPLIES IN THE CARD COLUMNS INDICATED: CC 46-50 DATE, EFFECTIVE, LOGISTICS ACTION, DRN 2128, (ALWAYS ZERO EFFECTIVE DATED), CC 51-62 SOURCE OF SUPPLY CODE/PSEUDO SOURCE OF SUPPLY CODE, DRN 3690/0133 (E.G., CC 51-53 INTEGRATED MATERIEL MANAGER (IMM) FIELD, CC 54-56 AIR FORCE FIELD, CC 57-59 ARMY FIELD, CC 60-62 NAVY FIELD), CC 63-64 NAVY SPECIAL SOURCE OF SUPPLY CODE, DRN 0135.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LVA

TITLE - IMC DATA

DEFINITION - USED BY THE INVENTORY CONTROL POINT (ICP) TO SUBMIT ITEM MANAGEMENT CODING (IMC) DATA FOR INTEGRATED MATERIEL MANAGER (IMM) MANAGEMENT. ALSO USED BY THE IMM AS A RESULT OF A SUPPLY SUPPORT REQUEST TO OBTAIN FLIS DATA BASE FILE DATA ON AN ITEM.

INSTRUCTIONS - TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LVE

TITLE - EXTRACT AND EDIT CODED ITEM CHARACTERISTICS DATA BY NSN

DEFINITION - THIS DIC IS USED TO EXTRACT CURRENT SEGMENT V DATA AND PROCESS THROUGH CURRENT IIG EDITS FOR A FULL DESCRIPTIVE ITEM IDENTIFICATION. A CURRENT TYPE 4 WILL BE EDITED AS A TYPE 1, A TYPE M AS A TYPE K, A TYPE N AS A TYPE L. (CANNOT BE USED FOR ITEMS WHICH ARE TYPE 2 OR ARE RECORDED UNDER IIG A23900.)

INSTRUCTIONS - NONE. MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - LVI

TITLE - SUBMITTAL TO UPDATE KVI SUSPENDED ITEM

DEFINITION - USED TO UPDATE THE KVI SUSPENSE FILE AND ITEM MANAGEMENT CODING/ITEM MANAGEMENT CODING ACTIVITY (IMC/IMCA) STATISTICAL REPORTS.

INSTRUCTIONS - DATA ELEMENTS ARE MANDATORY AND WILL BE SUBMITTED IN THE SEQUENCE REFLECTED IN THE DIC FORMAT. DATA RECORD NUMBERS AND DATA RECORD NUMBER VALUES MUST BE SEQUENCED AS FOLLOWS: (1) DRN 8290, MAJOR ORGANIZATIONAL ENTITY (MOE) RULE NUMBER, (2) DRN 0099, CARD IDENTIFICATION CODE (CIC), ITEM MANAGEMENT CODING, AND (3) DRN 2744, ITEM MANAGEMENT CODE. THE PSN (DNR 1070) IN CC 4-6 MUST BE Z01 IN EACH CARD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

# CHAPTER 2

**DOCUMENT IDENTIFIER CODE FORMAT**

## DOCUMENT IDENTIFIER CODE - KAD

TITLE - ADD DATA ELEMENT(S)

DEFINITION - THE DATA ELEMENT(S) REFLECTED IN THIS “SEGMENT R” RECORD AND IDENTIFIED BY THE APPLICABLE DATA RECORD NUMBER (DRN) AND VALUE HAS BEEN ADDED TO THE NSN REFLECTED IN THE OUTPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.ADD THIS DATA ELEMENT(S) FOR THIS NSN TO YOUR FILE(S).

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.2-1**

## DOCUMENT IDENTIFIER CODE - KAF

TITLE - ADD FREIGHT DATA

DEFINITION - THE FREIGHT CLASSIFICATION DATA REFLECTED IN THIS SEGMENT G RECORD IS APPLICABLE TO THE NSN INDICATED IN THE OUTPUT HEADER. THIS OUTPUT WILL BE FURNISHED TO ALL AUTHORIZED FREIGHT CLASSIFICATION DATA RECEIVERS.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.IF FREIGHT CLASSIFICATION DATA WAS PREVIOUSLY ASSIGNED, REPLACE DATA WITH THIS RECORD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.2-********99**

## DOCUMENT IDENTIFIER CODE - KAM

TITLE - ADD CATALOG MANAGEMENT DATA

DEFINITION - THE INPUT TRANSACTION IDENTIFIED BY THE DIC IN THE OUTPUT HEADER HAS BEEN PROCESSED, AND THE DATA HAS BEEN RECORDED IN THE CURRENT OR FUTURE FLIS DATA BASE AS INDICATED BY THE EFFECTIVE DATA REFLECTED IN THE SEGMENT H.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.ADD THIS DATA FOR THIS NSN TO YOUR FILE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KAR

TITLE - ADD REFERENCE NUMBER AND RELATED CODES

DEFINITION - THE REFERENCE NUMBER AND RELATED REFERENCE NUMBER CODES (I.E., RNAAC, DAC, RNCC, ETC.) REFLECTED IN THIS SEGMENT C RECORD HAVE BEEN ADDED TO THE FLIS DATA BASE FOR THE NSN REFLECTED IN CC 27-39.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.ADD THIS DATA TO YOUR FILES(S).

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KAS

TITLE - ADD STANDARDIZATION RELATIONSHIP

DEFINITION - A SUBMITTAL, WHICH CAUSED AN ADD TO A STANDARDIZATION REPLACEMENT RELATIONSHIP FOR AN NSN “NOT AUTHORIZED FOR PROCUREMENT” BEING REPLACED BY AN NSN “AUTHORIZED FOR PROCUREMENT”, HAS BEEN PROCESSED AND APPROVED. THE STANDARDIZATION DATA ELEMENTS RELECTED IN THIS SEGMENT HAVE BEEN ADDED TO THE FLIS DATA BASE FOR THE NSN REFLECTED IN CC 27-39.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.ADD THE STANDARDIZATION REPLACEMENT RELATIONSHIP FOR THIS NSN TO YOUR FILE. THE ELEMENTS OF DATA COMPRISING THIS SEGMENT ARE CONTAINED ON A SINGLE CARD; HOWEVER, WHEN THREE OR MORE NSNS ARE INVOLVED IN A STANDARDIZATION RELATIONSHIP, SUFFICIENT ADDITIONAL SEGMENT E CARDS WILL BE REQUIRED TO ACCOMMODATE ALL PERTINENT NSNS.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KAT

TITLE - ADD FLIS DATA BASE DATA

DEFINITION - FORWARDED IS THE FLIS DATA BASE DATA GENERATED AS A RESULT OF: (A) NEW NATIONAL ITEM IDENTIFICATION NUMBER (NIIN) ASSIGNMENT OR (B) REINSTATEMENT OF AN NSN OR (C) YOUR ACTIVITY BEING ADDED AS A DATA RECEIVER TO THIS ITEM IDENTIFICATION.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.ADD THIS DATA TO YOUR FILE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3A01		D3A03	D3A06	D3A07	D3F01	D3F02	D3F05 D3N01	D3Y00

## DOCUMENT IDENTIFIER CODE - KAU

TITLE - ADD MOE RULE NUMBER AND RELATED DATA

DEFINITION - THE MOE RULE NUMBER (WHICH REPRESENTS THOSE MANAGEMENT DATA ELEMENTS (PRIMARY/SECONDARY INVENTORY CONTROL ACTIVITY (PICA/SICA), ETC.) PREESTABLISHED BY THE SERVICES/AGENCIES) AND ITEM MANAGEMENT STATUS CODES APPLICABLE TO THE ITEM HAVE BEEN RECORDED IN THE FLIS DATA BASE FOR THE NSN IN THE OUTPUT HEADER. THE SEGMENT B RECORD MAY ALSO REFLECT SUPPLEMENTARY SUPPLEMENTARY DATA COLLABORATORS/RECEIVERS APPLICABLE TO THE ITEM IDENTIFICATION WHICH ARE NOT REPRESENTED BY THE MOE RULE NUMBER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.ADD THIS DATA TO YOUR FILE(S).

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KCD

TITLE - CHANGE DATA ELEMENT(S)

DEFINITION - THE DATA ELEMENT(S) REFLECTED IN THIS “SEGMENT R” RECORD AND IDENTIFIED BY THE APPLICABLE DATA RECORD NUMBER AND VALUE HAS BEEN CHANGED FOR THE NSN REFLECTED IN THE OUTPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.USE THE DATA ELEMENT(S) IN THIS “SEGMENT R” RECORD TO REPLACE THE CORRESPONDING DATA ELEMENT(S) FOR THIS NSN IN YOUR FILE(S).

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KCF

TITLE - CHANGE FREIGHT DATA

DEFINITION - THE FREIGHT CLASSIFICATION DATA REFLECTED IN THIS SEGMENT G RECORD HAS BEEN CHANGED FOR THE NSN INDICATED IN THE OUTPUT HEADER. THIS OUTPUT WILL BE FURNISHED TO ALL SUPPLEMENTARY FREIGHT CLASSIFICATION DATA RECEIVERS.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. (2) REPLACE THE FREIGHT CLASSIFICATION DATA IN YOUR FILE WITH THIS DATA.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KCG

TITLE - CHANGE FSC

DEFINITION - A SUBMITTAL HAS BEEN PROCESSED AND APPROVED TO CHANGE: FEDERAL SUPPLY CLASS ONLY OR FSC WITH ANY COMBINATION OF CHANGES TO ITEM NAME, TYPE OF ITEM IDENTIFICATION OR REFERENCE/PARTIAL DESCRIPTIVE METHOD REASON CODE (RPDMRC) FOR AN EXISTING ITEM IDENTIFICATION (NATIONAL ITEM IDENTIFICATION NUMBER (NIIN)).

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REPLACE THE GIVEN DATA ELEMENT(S) IN THIS “SEGMENT R” RECORD IN YOUR FILE. IF THE CHANGED DATA ELEMENT(S) WAS FOR A TYPE 1, 1A(K), 1B(L), 4, 4A(M) OR 4B(N) FII, REVISED CHARACTERISTICS DATA (TOTAL DATA) WILL BE FURNISHED UNDER OUTPUT DIC KTD. THE FIRST SEGMENT R RECORD WILL REFLECT THE NEW FSC, DRN 3990, ITS VALUE AND A DATA ELEMENT TERMINATOR CODE. IF A SECOND/SUCCEEDING DATA GROUP (DRN, DRN VALUE, DATA ELEMENT TERMINATOR CODE) CAN BE FULLY ACCOMMODATED IN THE REMAINING UNUSED POSITIONS ON ANY GIVEN CARD, THEY WILL BEGIN IMMEDIATELY FOLLOWING THE TERMINATOR CODE. IF THEY CANNOT BE FULLY ACCOMMODATED, THEY WILL BE STARTED IN CARD COLUMN 41 OF THE SUCCEEDING CARD, LEAVING ANY UNUSED POSITIONS BLANK, WITH DRN 8555 IN CARD COLUMN 80.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KCI

TITLE - CHANGE NIIN STATUS CODE

DEFINITION - THE NIIN (NATIONAL ITEM IDENTIFICATION NUMBER) STATUS CODE REFLECTED IN THIS SEGMENT R RECORD AND IDENTIFIED BY THE APPLICABLE DATA RECORD NUMBER AND VALUE HAS BEEN CHANGED FOR THE NSN REFLECTED IN THE OUTPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.THIS DIC IS SUPPLEMENTARY FOR FLIS USE ONLY AND WILL CONSIST OF AN OUTPUT HEADER AND ONE SEGMENT R RECORD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3Y00

## DOCUMENT IDENTIFIER CODE - KCM

TITLE - CHANGE CATALOG MANAGEMENT DATA

DEFINITION - THE INPUT TRANSACTION IDENTIFIED BY THE DIC IN THE OUTPUT HEADER HAS BEEN PROCESSED, AND THE DATA RECORDED IN THE FUTURE FLIS DATA BASE AS INDICATED BY THE EFFECTIVE DATE REFLECTED IN THE SEGMENT H.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REPLACE THIS DATA FOR THIS NSN IN YOUR FILE WITH THIS NEW SEGMENT “H” RECORD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KCR

TITLE - CHANGE REFERENCE NUMBER RELATED CODES

DEFINITION - ONE OR MORE REFERENCE NUMBER CODES (I.E., RNAAC, DAC, RNCC, ETC.) RELATED TO THE REFERENCE NUMBER REFLECTED IN THIS SEGMENT C HAS BEEN CHANGED IN THE FLIS DATA BASE FOR THE NSN REFLECTED IN CC 27-39.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REPLACE THE “SEGMENT C” RECORD IN YOUR FILE (CONTAINING THIS FSCM AND REFERENCE NUMBER) WITH THIS UPDATED “SEGMENT C” RECORD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KCS

TITLE - CHANGE STANDARDIZATION DECISION DATA IN A STANDARDIZATION RELATIONSHIP

DEFINITION - A SUBMITTAL, WHICH CAUSED A CHANGE TO STANDARDIZATION DATA ELEMENT(S) FOR AN ITEM IN A STANDARDIZATION RELATIONSHIP, HAS BEEN PROCESSED AND APPROVED. ONE OR MORE OF THE DATA ELEMENTS OF EITHER THE NSN IN CC 27-39 OR 50-62 HAS BEEN CHANGED IN THE FLIS DATA BASE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REPLACE THE DATA IN YOUR FILE WITH THIS STANDARDIZATION DATA CODED KCS.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KCU

TITLE - CHANGE MOE RULE NUMBER AND RELATED DATA

DEFINITION - THE FORMER MOE RULE NUMBER REFLECTED IN THIS SEGMENT B RECORD HAS BEEN CHANGED IN THE FLIS DATA BASE FOR THE NSN REFLECTED IN THE OUTPUT HEADER. IN ADDITION TO THE FORMER MOE RULE NUMBER, THE SEGMENT B RECORD WILL REFLECT THE NEW MOE RULE NUMBER AND ALL APPLICABLE DATA.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REMOVE THE FORMER MOE RULE NUMBER, ITS ASSOCIATED DATA, AND ANY SUPPLEMENTARY AUTHORIZED DATA COLLABORATORS/RECEIVERS RECORDED AGAINST THE FORMER MOE RULE NUMBER AND REPLACE WITH THIS NEW SEGMENT B RECORD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KCZ

TITLE - CHANGE ITEM STANDARDIZATION DECISION DATA NOT IN A STANDARDIZATION RELATIONSHIP

DEFINITION - A SUBMITTAL, WHICH CAUSED A CHANGE TO STANDARDIZATION DATA ELEMENTS FOR AN ITEM NOT IN A STANDARDIZATION RELATIONSHIP HAS BEEN PROCESSED AND APPROVED. ONE OR MORE OF THE DATA ELEMENTS FOR THE NSN REFLECTED IN CC 27-39 HAS BEEN CHANGED IN THE FLIS DATA BASE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REPLACE THE STANDARDIZATION DECISION DATA IN YOUR FILE WITH THIS DATA.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KDD

TITLE - DELETE DATA ELEMENT(S)

DEFINITION - THE DATA ELEMENT(S) REFLECTED IN THIS “SEGMENT R” RECORD AND IDENTIFIED BY THE APPLICABLE DATA RECORD NUMBER HAS BEEN DELETED FROM THE NSN REFLECTED IN THE OUTPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.DELETE THIS DATA ELEMENT(S) FOR THIS NSN FROM YOUR FILE(S).

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KDF

TITLE - DELETE FREIGHT DATA

DEFINITION - THE NMFC/NMFC SUB-ITEM NUMBER/UFC REFLECTED IN THIS SEGMENT G RECORD HAS BEEN DELETED FROM THE NSN INDICATED IN THE OUTPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. (2) DELETE THIS NMFC/NMFC SUB-ITEM NUMBER/UFC FROM THE NSN ON YOUR FILE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KDM

TITLE - DELETE CATALOG MANAGEMENT DATA

DEFINITION - THE INPUT TRANSACTION IDENTIFIED BY THE DIC IN THE OUTPUT HEADER HAS BEEN PROCESSED, AND THE ACTION RECORDED IN THE “FUTURE” FLIS DATA BASE AS INDICATED BY THE EFFECTIVE DATE REFLECTED IN THE SEGMENT H.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.DELETE THE DATA FOR THIS NSN FROM YOUR FILE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KDR

TITLE - DELETE REFERENCE NUMBER DATA

DEFINITION - THE REFERENCE NUMBER REFLECTED IN THE SEGMENT C RECORD HAS BEEN DELETED FROM THE FLIS DATA BASE FOR THE NSN REFLECTED IN CC 27-39.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.DELETE THE RELATED REFERENCE NUMBER (HAVING THE SAME CAGE/NATO COMMERCIAL AND GOVERNMENT ENTITY CODE

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KDS

TITLE - DELETE STANDARDIZATION RELATIONSHIP

DEFINITION - A SUBMITTAL WHICH CAUSED A DELETE TO A STANDARDIZATION REPLACEMENT RELATIONSHIP HAS BEEN PROCESSED AND APPROVED. THE STANDARDIZATION RELATIONSHIP DATA REFLECTED IN CC 50-80 HAS BEEN DELETED FROM THE FLIS DATA BASE FOR THE NATIONAL STOCK NUMBER (NSN) IN THE OUTPUT HEADER. THE STANDARDIZATION DATA ELEMENTS IN CC 41-49 FOR THE NSN IN CC 27-39 MAY OR MAY NOT HAVE CHANGED IN THE FLIS DATA BASE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.DELETE THE STANDARDIZATION REPLACEMENT RELATIONSHIP FOR THIS NSN FROM YOUR FILE. CHANGE THE STANDARDIZATION DECISION DATA FOR THE INDIVIDUAL ITEMS TO REFLECT THE NEW ITEM STANDARDIZATION CODES, ORIGINATOR AND DATA OF STANDARDIZATION, IF APPLICABLE. THE ELEMENTS OF DATA COMPRISING THIS SEGMENT ARE CONTAINED ON A SINGLE CARD; HOWEVER, WHEN THREE OR MORE NSNS ARE INVOLVED IN A STANDARDIZATION RELATIONSHIP, SUFFICIENT ADDITIONAL SEGMENT E CARDS WILL BE REQUIRED TO ACCOMMODATE ALL PERTINENT NSNS.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KDU

TITLE - DELETE MOE RULE NUMBER

DEFINITION - THE MOE RULE NUMBER REFLECTED IN THIS SEGMENT B RECORD HAS BEEN DELETED FROM THE FLIS DATA BASE FOR THE NSN REFLECTED IN THE OUTPUT HEADER. ALL RELATED ITEM MANAGEMENT STATUS CODES AND ANY SUPPLEMENTARY SUPPLEMENTARY DATA COLLABORATORS/RECEIVERS WHICH MAY HAVE BEEN RECORDED AGAINST THE DELETED MOE RULE NUMBER FOR THIS ITEM HAVE ALSO BEEN REMOVED.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.IF THIS MOE RULE NUMBER AND ITEM MANAGEMENT STATUS CODES APPLICABLE TO THIS ITEM, INCLUDING SUPPLEMENTARY AUTHORIZED DATA COLLABORATORS/RECEIVERS NOT REPRESENTED BY THE MOE RULE NUMBER, IS FOR YOUR ACTIVITY, REMOVE ALL DATA FOR THIS NSN FROM YOUR FILE(S). IF NOT FOR YOUR ACTIVITY, ONLY REMOVE THE MOE RULE NUMBER, ITEM MANAGEMENT STATUS CODES APPLICABLE TO THE ITEM AND ANY SUPPLEMENTARY AUTHORIZED DATA COLLABORATORS/RECEIVERS NOT REPRESENTED BY THE MOE RULE NUMBER.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KDZ

TITLE - DELETE LOGISTICS TRANSFER

DEFINITION - THE LOGISTICS TRANSFER REFLECTED IN THIS TRANSACTION HAS BEEN DELETED FROM THE FUTURE FILE FOR THE NSN REFLECTED IN THE OUTPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REMOVE THE FUTURE SEGMENT B, H, AND T RECORD(S) INDICATED IN THIS NOTIFICATION.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KEC

TITLE - OUTPUT EXCEEDS ELECTRONIC DATA TRANSFER LIMITATIONS

DEFINITION - THIS IS A NOTIFICATION INDICATING THAT THE OUTPUT TRANSACTION GENERATED BY PROCESSING YOUR SUBMITTAL RESULTED IN AN OUTPUT TRANSACTION PACKAGE CONSISTING OF 39,841 OR MORE CHARACTERS. THE TRANSACTION PACKAGE WILL BE FORWARDED BY MAIL AND WILL CONTAIN THE SAME DOCUMENT CONTROL NUMBER.

INSTRUCTIONS - NOT APPLICABLE MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3A01		D3A03		D3A07		D3F02	D3F05	D3G06	D3G09 D3G10	D3K00		D3N04		D3Y00

## DOCUMENT IDENTIFIER CODE - KFA

TITLE - MATCH THROUGH ASSOCIATION

DEFINITION - YOUR SUBMITTAL IS A POSSIBLE DUPLICATE OF AN EXISTING FEDERAL ITEM IDENTIFICAITON (FII) REVEALED BY A REFERENCE NUMBER MATCH THROUGH ASSOCIATION CODE RELATIONSHIP SCREENING. FLIS DATA BASE DATA CODED KFA IS FORWARDED. A SEGMENT 1 MAY ALSO BE PROVIDED REFLECTING THE SUBMITTED AND CHANGE VALUE. ALL SCREENING RESULTS ARE BASED ON THE USE OF THE REPLACED CAGE/NATO COMMERCIAL AND GOVERNMENT ENTITY (NCAGE).

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REVIEW THE FLIS DATA BASE DATA AND IF THE EXISTING FII REPRESENTS YOUR ITEM OF SUPPLY SUBMIT, IF NECESSARY, THE APPROPRIATE LAU OR LCU TRANSACTION. IF THE EXISTING FII DOES NOT REPRESENT YOUR ITEM OF SUPPLY RESUBMIT THE PROPOSAL WITH THE APPROPRIATE REFERENCE NUMBER JUSTIFICATION CODE IN ALL REFERENCE NUMBER(S) THAT CAUSED THE POSSIBLE DUPLICATION. NOTE: KFA IS SECONDARY TYPE OUTPUT WHICH IS GENERATED AS A RESULT OF INPUT DIC/S LAR, LBC, LBK, LBR, LCR, LNC, LNK, LNP OR LNR. PRIMARY OUTPUT IS FORWARDED UNDER KRP.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KFD

TITLE - FLIS DATA BASE FILE DATA

DEFINITION - FLIS DATA BASE FILE DATA FORWARDED BECAUSE THE SUBMITTED ITEM (1) IS A POSSIBLE DUPLICATION OF AN EXISTING ITEM OR (2) IS AN ACTUAL DUPLICATION OF AN EXISTING ITEM OR (3) WAS PREVIOUSLY CANCELLED AS A DUPLICATE (THE KFD DATA IS FOR THE DUPLICATE ITEM) OR (4) WAS CANCELLED TO USE ANOTHER ITEM (THE KFD DATA IS FOR THE “USE” ITEM) OR (5) WAS CANCELLED WITH REPLACEMENT (THE KFD DATA IS FOR THE REPLACEMENT ITEM) OR (6) IS INACTIVE (NO RECORDED MOE RULE NUMBER) OR (7) CONTAINED ERROR CONDITIONS FOUND DURING PROCESSING WHICH PROHIBIT INTRODUCING THE SUBMITTED DATA INTO THE FLIS DATA BASE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REVIEW THIS FLIS DATA BASE DATA IN CONJUNCTION WITH YOUR SUBMITTAL AND THE OTHER OUTPUT DIC(S) IN THIS PACKAGE. INITIATE ACTION AS INDICATED IN THE INSTRUCTIONS FOR THE OUTPUT DIC(S). KFD IS SECONDARY TYPE OUTPUT. FOR DATA CONTENT OF KFD, SEE THE PRIMARY OUTPUT PACKAGES KKD, KMU, KPE, KRE, KRM, AND KRP. 3.TO AUTOMATICALLY INCLUDE SEGMENT Z DATA (DRN 9119) TO REFLECT AN INCOMPATIBILITY WITH PENDING FUTURE EFFECTIVE DATED ACTIONS.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3A01		D3A03		D3A06		D3A07	D3F01	D3F02	D3F04 D3F05	D3F09		D3N01		D3Y00

## DOCUMENT IDENTIFIER CODE - KFE

TITLE - FLIS DATA BASE DATA FOR REPLACEMENT OF A CANCELED NSN, RELATED GENERIC NSN, OR REFERENCE NUMBER SCREENING RESULTS

DEFINITION - FLIS DATA BASE DATA IS FORWARDED AS A RESULT OF A REFERENCE NUMBER MATCHING A NSN. THIS DIC IS ALSO USED TO FORWARD FLIS DATA BASE DATA FOR A REPLACEMENT NSN OF AN ITEM THAT HAS BEEN CANCELLED, AND TO FORWARD FLIS DATA BASE DATA FOR A RELATED GENERIC NSN.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REVIEW THIS FLIS DATA BASE DATA FOR SUITABILITY FOR YOUR APPLICATION. KFE IS USED AS SECONDARY OUTPUT FOR CANCELLED/REPLACED ITEMS OR REFERENCE NUMBER MATCHES. PRIMARY OUTPUT IS FORWARDED AS KSR FOR REFERENCE NUMBER SCREENING (WITHOUT CAGE OR NATO COMMERCIAL AND GOVERNMENT ENTITY CODE (NCAGE)), KFS FOR NIIN SCREENING AND INTERROGATIONS, AND KIR FOR ITEM MANAGEMENT CODING.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KFF

TITLE - FILE REPLACEMENT DATA FOR NATO OR OTHER FOREIGN GOVERNMENTS

DEFINITION - USED TO FORWARD FLIS DATA BASE DATA TO A NATO COUNTRY, NATO AGENCY, OR OTHER FOREIGN GOVERNMENT. THE DATA IS TO BE USED BY THE DATA RECEIVER AS A FILE REPLACEMENT.

INSTRUCTIONS - TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3Y00

## DOCUMENT IDENTIFIER CODE - KFM

TITLE - NOTIFICATION TO INCREMENT FMSN

DEFINITION - THE TRANSACTION REPRESENTED BY THE INPUT DIC REFLECTED IN THE OUTPUT HEADER HAS BEEN PROCESSED, THE FLIS DATA BASE UPDATED, AND THE FILE MAINTENANCE SEQUENCE NUMBER (FMSN) INCREMENTED. YOUR ACTIVITY IS RECORDED AS A DATA RECEIVER FOR THE NSN ALSO REFLECTED IN THE OUTPUT HEADER. HOWEVER, MECHANIZED OUTPUT FILE MAINTENANCE DATA HAS BEEN SUPPRESSED FOR YOUR ACTIVITY.

INSTRUCTIONS - USE THIS RECORD TO INCREMENT THE FILE MAINTENANCE SEQUENCE NUMBER IN YOUR MECHANIZED FILE(S).

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KFN

TITLE - FOLLOW-UP INTERROGATION RESULTS, NATO ONLY

DEFINITION - FORWARDED ARE THE RESULTS OF YOUR FOLLOW-UP INTERROGATION FOR THE STATUS OF THE DOCUMENT CONTROL NUMBER REFLECTED IN THE SEGMENT R RECORD OF THIS TRANSACTION PACKAGE. THE CURRENT STATUS OF THAT DOCUMENT CONTROL NUMBER IS REFLECTED BY THE TRANSACTION STATUS CODE ALSO CITED IN THE SEGMENT R RECORD.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.FOR USE BY NORTH ATLANTIC TREATY ORGANIZATION (NATO) AND OTHER FOREIGN GOVERNMENTS ONLY.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3N02

## DOCUMENT IDENTIFIER CODE - KFP

TITLE - FOLLOW-UP NOTIFICATION

DEFINITION - THIS FOLLOW-UP NOTIFICATION IS FORWARDED BECAUSE DATA REQUIRED TO BE ADDED TO OR CHANGED FOR THE NSN REFLECTED IN THIS OUPUT HEADER HAS NOT YET BEEN RECEIVED BY FLIS.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.SEE VOLUME 10, SECTION 10.2.7 FOR THE APPLICABLE FOLLOW-UP CONDITION CODE DEFINITIONS CONTAINED IN SEGMENT R. REVIEW THE FOLLOW-UP CONDITION CODE AND SUBMIT THE DATA TO BE ADDED OR CHANGED AS INDICATED.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KFR

TITLE - FILE DATA FOR REPLACEMENT NSN WHEN NOT AUTHORIZED FOR PROCUREMENT

DEFINITION - FLIS DATA BASE IS FORWARDED FOR THE REPLACEMENT NATIONAL STOCK NUMBERS (NSNS) WHICH ARE RELATED TO AN NSN “NOT AUTHORIZED FOR PROCUREMENT” REFLECTED IN AN ADOPTION ACTION SUBMITTED BY YOUR ACTIVITY. THE DOCUMENT NUMBER IS IDENTICAL TO THE DOCUMENT NUMBER USED IN THE ADOPTION TRANSACTION.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.THIS DATA MAY BE ADDED TO YOUR FILE, IF APPROPRIATE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KFS

TITLE - NIIN STATUS/INDEX

DEFINITION - USED TO NOTIFY THE ACTIVITY IN THE DESTINATION CODE, SCREENING FIELD OR SUBMITTING ACTIVITY FIELD THAT THE SUBMITTED NATIONAL ITEM IDENTIFICATION NUMBER (NIIN) IS RECORDED IN THE FLIS DATA BASE WITH NIIN STATUS CODE AS REFLECTED IN THE SEGMENT K RECORD.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.NIIN STATUS CODE DEFINITIONS ARE CONTAINED IN VOLUME 10, TABLE 18.DRNS 8875/8878 IN SEGMENT K MAY BE REPEATED, IF REQUIRED.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3A01		D3A03		D3A07		D3F01	D3F02	D3F05	D3F09 D3G03	D3G06		D3N03		D3Y00

## DOCUMENT IDENTIFIER CODE - KFU

TITLE - FOLLOW-UP INTERROGATION RESULTS

DEFINITION - FORWARDED ARE THE RESULTS OF YOUR FOLLOW-UP INTERROGATION FOR THE STATUS OF THE DOCUMENT CONTROL NUMBER (DRN 0131) REFLECTED IN SEGMENT R RECORD OF THIS TRANSACTION PACKAGE. THE CURRENT STATUS OF THAT DOCUMENT CONTROL NUMBER IS REFLECTED BY THE FOLLOW-UP STATUS CODE (DRN 0166) ALSO CITED IN SEGMENT R RECORD.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.REVIEW THE OUTPUT PACKAGE FOR APPROPRIATE ACTION. IF THE CITED FOLLOW-UP STATUS CODE (DRN 0166) IN THE SEGMENT R RECORD IS “GS” OR “HX”, THE TRANSACTION WILL TERMINATE WITH SEGMENT R RECORD. ALL OTHER FOLLOW-UP STATUS CODES SPECIFY WHAT ADDITIONAL DATA WILL FOLLOW THE SEGMENT R RECORD IN CONVENTIONAL SEGMENT FORMAT. IF THE FOLLOW-UP STATUS CODE INDICATES FLIS DATA BASE DATA WILL BE OUTPUT, THIS DATA WILL BE REFLECTED UNDER DIC KIR IN A SEPARATE PACKAGE REFLECTING THE DOCUMENT NUMBER OF THE ORIGINAL LFU/KFU PACKAGE. SEE VOLUME 10, SECTION 10.2.6 FOR KFU FOLLOW-UP STATUS CODES.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## FOLLOW-UP INTERROGATION RESULTS DIC LFU/ODRC CROSS REFERENCE GRID

The following grid depicts the Output Data Codes that will be used in the FLIS-generated LTI, based on the DIC being followed-up, and the segments interrogated as a result of the applied ODRC(s). The generation of the LTI and its KIR output only occurs when the Follow-Up Status Code returned in the KFU is AX, CX, or FX.

NOTES:

2. FLIS data base data will be output when KFU Follow-Up Status Code is AX, CX, or FX per volume 10, section 10.2.6 . FLIS data base data will never be output for follow-ups on DICs LAB, LAF, LCF, LCI, LDF, LDZ, LPA, LPC, LPD, LSS, LTU, LTV, LTW, LVA AND LVI.

## DOCUMENT IDENTIFIER CODE - KHN

TITLE - O.E. SSR FILE MAINTENANCE DATA

DEFINITION - USED TO TRANSMIT THE ACCUMULATED O.E. OUTPUT MAINTENANCE TRANSACTIONS RESULTING FROM APPROVED PROCESSING OF INPUT DICS.

INSTRUCTIONS - 1.THIS DIC IS TRANSMITTED DAILY, VIA ELECTRONIC DATA TRANSFER, TO UPDATE S/A O.E. FILE(S) WHEN THIS DIC IS OUTPUT AS THE RESULT OF APPROVED PROCESSING OF INPUT DICS APPLICABLE TO O.E. (CAGE/NATO COMMERCIAL AND GOVERNMENT ENTITY CODE) FILE, IT WILL CONSIST OF SSR OUTPUT SEGMENT FOLLOWED BY O.E. FILE MAINTENANCE DATA SEGMENTS.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KHP

TITLE - NOTIFICATION OF APPROVAL, SSR TRANSACTION

DEFINITION - USED TO NOTIFY THE ACTIVITY IN THE SUBMITTING ACTIVITY FIELD THAT A TRANSACTION REPRESENTED BY THIS DOCUMENT NUMBER WAS APPROVED AND PROCESSED.

INSTRUCTIONS - NOT APPLICABLE MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KHR

TITLE - NOTIFICATION OF RETURN, SSR TRANSACTION

DEFINITION - USED TO NOTIFY SUBMITTER OF A TRANSACTION WHICH CONTAINED ERROR CONDITIONS. THIS DIC WILL PROVIDE ONLY THE SUBMITTED PACKAGE SEQUENCE NUMBER, THE DATA RECORD NUMBER AND THE APPLICABLE RETURN CODE IDENTIFYING THE SPECIFIC ERROR CONDITION(S).

INSTRUCTIONS - NOT APPLICABLE MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KHS

TITLE - NOTIFICATION OF UNPROCESSABLE PACKAGE, SSR

DEFINITION - YOUR ACTIVITY WAS RECORDED AS THE SUBMITTER FOR THE TRANSACTION REPRESENTED BY THIS DOCUMENT NUMBER WHICH WAS RETURNED AS UNPROCESSABLE BECAUSE OF MISSING OR UNIDENTIFIABLE CONTROL SEGMENTS.

INSTRUCTIONS - CHECK THE CONTROL DATA IN YOUR SUBMISSION (CARD COLUMNS 1-26 FOR CARD FORMATS: DRNS 3920 THROUGH 0225 FOR OPTICAL CHARACTER RECOGNITION (OCR) FORMATS). CORRECT MISSING AND/OR ERRONEOUS DATA AND RESUBMIT.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KIE

TITLE - ADVANCE INFORMATIVE FLIS DATA BASE DATA

DEFINITION - THIS FLIS DATA BASE DATA IS FURNISHED AS A RESULT OF ONE OF THE FOLLOWING EFFECTIVE DATED TRANSACTIONS HAVING BEEN RECORDED IN THE FLIS DATA BASE FUTURE FILE: ADDING (LAU) OR CHANGING (LCU) A MOE RULE AND RELATED ITEM STATUS DATA FOR YOUR SERVICE/AGENCY: A FEDERAL SUPPLY CLASS (FSC) CHANGE (LCG) FOR THE ITEM: OR AN LMD CONTAINING AN LCG AND AN LAU/LCU.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.FILE MAINTENANCE OUTPUT WILL BE FURNISHED IN ACCORDANCE WITH NORMAL OPERATING PROCEDURES WHEN THE “EFFECTIVE DATE” HAS BEEN REACHED.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KIF

TITLE - INFORMATIVE DATA FOR PENDING EFFECTIVE DATED ACTIONS

DEFINITION - AN EFFECTIVE DATED TRANSACTION HAS BEEN PROCESSED AND RECORDED IN THE FUTURE FILE. THE FLIS DATA BASE WILL BE UPDATED ON THE EFFECTIVE DATE INDICATED IN THIS SEGMENT Z RECORD FOR THE NSN REFLECTED IN THE OUTPUT HEADER. IN ADDITION TO THE EFFECTIVE DATE, THE SEGMENT Z RECORD WILL REFLECT THE INPUT DIC AND THE ORIGINATOR OF THE TRANSACTION.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD.

2.NOTIFICATION AND FILE MAINTENANCE OUTPUT WILL BE FURNISHED IN ACCORDANCE WITH NORMAL OPERATING PROCEDURES WHEN THE EFFECTIVE DATE HAS BEEN REACHED. 3. FOLLOWING THE FUTURES DATA SEGMENT (DRN9119) WILL BE THE SEGMENT REPRESENTED BY THE REPLY TO DRN0950) (CC 53–56) SUCH AS SEGMENT B, H, R, T, WHICH WILL INCLUDE THE EFFECTIVE DATED DATA ELEMENTS. THE FORMAT FOR THE ADDITIONAL SEGMENT IS FOUND IN VOL 8, CHAPTER 3.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KIM

TITLE - CATALOG MANAGEMENT DATA AS RESULT OF IMM/LEAD SERVICE INPUT

DEFINITION - AN INTEGRATED MATERIEL MANAGER (IMM) OR LEAD SERVICE TRANSACTION HAS BEEN APPROVED AND RECORDED FOR THE NSN REFLECTED IN THE OUTPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.REVIEW THE OUTPUT AND SUBMIT THE APPLICABLE TRANSACTION IN RESPONSE TO DIC LAM, LBM, LAU OR LCU REFLECTED IN CC 42-44; FOR DICS LCM, LDM, OR LDU REFLECTED IN THE HEADER, SUBMIT THE APPLICABLE DIC; LCM, LCD, LBM, LDD OR LDM.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KIP

TITLE - INTERCHANGEABILITY AND SUBSTITUTABILITY (I&S) DATA AS A RESULT OF A SECONDARY INVENTORY CONTROL ACTIVITY (SICA) INPUT

DEFINITION - A SECONDARY INVENTORY CONTROL ACTIVITY (SICA) I&S FAMILY TRANSACTION HAS BEEN APPROVED AND RECORDED FOR THE MASTER OR GENERIC MASTER NSN REFLECTED IN THE INPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.REVIEW THE OUTPUT AND UPDATE YOUR FILES/RECORDS TO REFLECT THE CURRENT INFORMATION FOR THE APPLICABLE SICA'S I&S FAMILY DATA.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KIR

TITLE - INTERROGATION RESULTS

DEFINITION - USED FOR INTERROGATION RESULTS OF DIC LTI WHEN THE NATIONAL ITEM IDENTIFICATION NUMBER (NIIN) SUBMITTED FOR INTERROGATION IS FOUND TO BE VALID AND REQUESTED FLIS DATA BASE DATA /INTERCHANGEABILITY AND SUBSTITUTABILITY (FLIS DATA/I&S) DATA IS AVAILABLE. THE REQUESTED DATA WILL BE OUTPUT TO THE SUBMITTER. IF ALL OF THE REQUESTED SEGMENTS ARE NOT INCLUDED IN THE OUTPUT AND THE PSNS ARE IN PROPER SEQUENCE, IT CAN BE ASSUMED THAT THE OMITTED SEGMENTS ARE NOT RECORDED IN THE FLIS DATA BASE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.COMPLETE SEGMENT DATA WILL BE FURNISHED (IF AVAILABLE) WHEN DRNS CONTAINED IN VOLUME 10, TABLE 34 ARE SUBMITTED FOR INTERROGATION.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.2-********109**

## DOCUMENT IDENTIFIER CODE - KIS

TITLE - SEARCH RESULTS OF NATIONAL ITEM IDENTIFICATION NUMBER SCREENING

DEFINITION - FORWARDED IS THE FLIS DATA BASE FILE DATA REQUESTED BY YOUR ACTIVITY FOR THE NATIONAL ITEM IDENTIFICATION NUMBER (NIIN) REFLECTED IN THE OUTPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.COMPLETE SEGMENT DATA WILL BE FURNISHED IF AVAILABLE DEPENDING ON SUBMITTED OUTPUT DATA REQUEST CODE (DRN 4690).

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KKD

TITLE - CANCEL-DUPLICATE

DEFINITION - THE NSN IN THE OUTPUT HEADER WILL BE CANCELLED AS A DUPLICATE OF THE NSN IN THE SEGMENT K RECORD ON THE CITED EFFECTIVE DATE.

INSTRUCTIONS - MAJOR ORGANIZATIONAL ENTITY (MOE) RULE NUMBER(S), ITEM MANAGEMENT STATUS CODES, AND ANY SUPPLEMENTARY DATA COLLABORATORS/ RECEIVERS OF THE CANCELLED ITEM THAT REPRESENT A UNITED STATES ACTIVITY WILL NOT BE ADDED TO THE DUPLICATE NSN. FLIS DATA BASE DATA CODED KFD FOR THE DUPLICATE NSN IS FORWARDED. NATO AND OTHER FOREIGN GOVERNMENT (NATO/FG) MOE RULE NUMBERS RECORDED ON THE CANCELED NSN WILL BE MOVED TO THE DUPLICATE NSN ON THE EFFECTIVE DATE IF NOT ALREADY PRESENT. FLIS DATA BASE DATA CODED KAT FOR THE DUPLICATE NSN WILL BE FORWARDED TO NEWLY RECORDED NATO/FG(S). REFERENCE NUMBERS WILL BE TRANSFERRED, IF PROCESSABLE, TO THE DUPLICATE ITEM ON THE EFFECTIVE DATE OF THE CANCELLATION. REFERENCE NUMBERS THAT CANNOT BE TRANSFERRED WILL BE RETURNED TO THE SUBMITTER OF THE CANCELLATION UNDER DIC KRE. A SEGMENT P WILL CONTAIN THE DRN OF THE DATA ELEMENT AND THE RETURN CODE RELATED TO THE ITEM OF SUPPLY CONCEPT PROBLEM FOLLOWED BY THE SEGMENT C RECORD OF THE UNPROCESSABLE REFERENCE NUMBER. COMPLETE FILE DATA OF THE REPLACEMENT ITEM WILL ALSO ACCOMPANY THIS PACKAGE UNDER DIC KFD, REFERENCE NUMBERS THAT CANNOT BE TRANSFERRED BECAUSE OF RESULTANT ACTUAL OR POSSIBLE MATCH CONDITIONS WILL ALSO BE RETURNED TO THE SUBMITTER UNDER DICS KRM AND KRP RESPECTIVELY, CONTAINING THE FILE DATA OF THE MATCHING ITEM(S) AND THE SEGMENT C RECORD OF THE REFERENCE NUMBER TO BE TRANSFERRED. THE DOCUMENT NUMBER AND THE INPUT DIC OF THE ORIGINAL TRANSACTION WILL BE REFLECTED IN THE HEADERS OF THESE KRE, KRM, OR KRP OUTPUTS WITH THE EXCEPTION OF “97” IN THE ORIGINATOR FIELD. REMOVE ALL APPLICABLE DATA FOR THE CANCELLED NSN AND REPLACE WITH THIS SEGMENT K INDEX RECORD ON THE EFFECTIVE DATE SHOWN. REVIEW THE KFD DATA FOR THE DUPLICATE NSN AND, IF REQUIRED, SUBMIT THE APPLICABLE LAD, LAU, LAR OR LCU TRANSACTION. KFD DATA WILL BE FORWARDED TO ALL ACTIVITIES RECORDED ON THE CANCELLED ITEM.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KKI

TITLE - CANCEL-INACTIVE

DEFINITION - THE NSN REFLECTED IN CC 27-39 HAS BEEN CANCELLED-INACTIVE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITION 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REMOVE ALL APPLICABLE DATA FOR THE CANCELLED NSN AND REPLACE WITH SEGMENT K INDEX RECORD ON THE EFFECTIVE DATE SHOWN.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KKU

TITLE - CANCEL USE

DEFINITION - THE NSN REFLECTED IN CC 27-39 WILL BE CANCELLED TO USE THE NSN REFLECTED IN CC 54-66 (SEGMENT K) ON THE CITED EFFECTIVE DATE. THE MAJOR ORGANIZATIONAL ENTITY RULE NUMBER(S), ITEM MANAGEMENT STATUS CODES AND ANY SUPPLEMENTARY SUPPLEMENTARY DATA COLLABORATORS/RECEIVERS NOT REPRESENTED BY THE MOE RULE NUMBER RECORDED ON THE ITEM WHICH WAS CANCELLED WILL NOT BE ADDED TO THE “USE” NSN. NOR WILL ANY REFERENCE NUMBER(S) BE ADDED. FLIS DATA BASE DATA CODED KFD FOR THE “USE” NSN IS FORWARDED.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REMOVE ALL APPLICABLE DATA FOR THE CANCELLED NSN AND REPLACE WITH THIS SEGMENT K INDEX RECORD ON THE EFFECTIVE DATE SHOWN. REVIEW THE KFD DATA FOR THE “USE” NSN AND, IF REQUIRED, SUBMIT AN LAD, LAU, LCU OR LAR TRANSACTION. KFD DATA WILL BE FORWARDED TO ALL ACTIVITIES RECORDED ON THE CANCELLED ITEM.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.2-********119**

**DRN	DATA ELEMENT/IDENTIFIER NAME	FORMAT**

**SEG CODE**

**INST/ NOTES**

**CARD COLUMN**

BLANK	70-80

## DOCUMENT IDENTIFIER CODE - KKV

TITLE - CANCEL-INVALID

DEFINITION - THE NSN REFLECTED IN CC 27-39 HAS BEEN “CANCELLED AS INVALID”.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REMOVE ALL APPLICABLE DATA FOR THIS NSN FROM YOUR FILES AND REPLACE WITH THIS SEGMENT K INDEX RECORD ON THE EFFECTIVE DATE SHOWN.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KMA

TITLE - ASSOCIATION CODE MATCH (SCREENING)

DEFINITION - THIS OUTPUT DIC IS THE RESULT OF LSR OR LSN INPUT WHEN THE SUBMITTED CAGE AND REFERENCE NUMBER MATCHES AN IDENTICAL REFERENCE NUMBER ASSOCIATED TO A DIFFERENT CAGE WHICH HAS BEEN ESTABLISHED UNDER A CAGE ASSOCIATION CODE RELATIONSHIP WITHIN THE SAME INDUSTRIAL CORPORATE COMPLEX. DIC KMA INDICATES THAT THE MATCH IS AN ASSOCIATION MATCH. IF A MATCH IS MADE UNDER THE SUBMITTED CAGE, NO ASSOCIATION CODE MATCH SEARCH WILL BE MADE ASSOCIATION MATCH CONDITIONS ARE TO BE CONSIDERED IN A LEVEL EQUIVALENT TO A POSSIBLE MATCH CONDITION, UNDER P TYPE SCREENING OR A PARTIAL MATCH CONDITION UNDER S TYPE SCREENING OR F TYPE SCREENING (SEE M&V FOR NATO/FC ONLY). THE SCREENING RESULTS CAN BE BASED ON BOTH THE REPLACEMENT CAGE CODE/NATO COMMERCIAL AND GOVERNMENT ENTITY CODE AND THE CANCELED CAGE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.REVIEW THE FLIS DATA BASE DATA FOR SUITABILITY FOR YOUR APPLICATION. KMA IS SECONDARY OUTPUT WHICH IS GENERATED AS A RESULT OF INPUT DIC LSR OR LSN. PRIMARY OUTPUT IS FORWARDED UNDER DIC KSR. A SEGMENT “J” RECORD REFLECTING OUTPUT DIC KMR FOR THE MATCHING INPUT REFERENCE NUMBER(S) INCLUDED IN YOUR SUBMITTAL PACKAGE WILL ALWAYS PRECEDE THE SECONDARY OUTPUT DIC IN THIS OUTPUT PACKAGE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KMD

TITLE - MULTIPLE DICS

DEFINITION - USED AS THE PRIMARY OUTPUT DIC IN THE OUTPUT HEADER TO INDICATE THAT AN OUTPUT FROM FLIS CONTAINS MULTIPLE FILE MAINTENANCE OUTPUT DICS UNDER THE SAME DOCUMENT NUMBER. KMD APPEARS IN THE OUTPUT HEADER FOLLOWED BY OTHER APPLICABLE FILE MAINTENANCE OUTPUT DICS AND ASSOCIATED SEGMENT WHICH RELATE THE PROCESSING RESULTS OF SELECTED INPUT DICS WITHIN ALLOWABLE COMBINATIONS SUBMITTED UNDER LMD.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.THIS FORMAT REPRESENTS THE POSSIBLE SEGMENTS TO BE OUTPUT UNDER DIC KMD.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.2-********129**

## DOCUMENT IDENTIFIER CODE - KME

TITLE - EXACT MATCH (SCREENING)

DEFINITION - OUTPUT AS A RESULT OF DIC LSR OR LSN INPUT FOR TYPE S OR TYPE F CONCEPT SCREENING. DIC KME SIGNIFIES THAT THE RESULTS OF SCREENING REFLECT AN EXACT MATCH, INDICATING THERE ARE NO ADDITIONAL REFERENCE NUMBERS REFERENCED TO THE MATCHED NSN. (SEGMENTS M AND V ARE FOR NATO AND OTHER FOREIGN COUNRIES ONLY).

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY 1 (ONE) IN EACH CARD. 2.REVIEW THE FLIS DATA BASE DATA FOR SUITABILITY FOR YOUR APPLICATION. KME IS SECONDARY OUTPUT WHICH IS GENERATED AS A RESULT OF INPUT DIC LSR OR LSN. PRIMARY OUTPUT IS FORWARDED UNDER DIC KSR. A SEGMENT “J” RECORD REFLECTING OUTPUT DIC KMR FOR THE MATCHING INPUT REFERENCE NUMBER(S) INCLUDED IN YOUR SUBMITTAL PACKAGE WILL ALWAYS PRECEDE THE SECONDARY OUTPUT DIC IN THIS OUTPUT PACKAGE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KMG

TITLE - POSSIBLE MATCH (SCREENING)

DEFINITION - OUTPUT AS THE RESULT OF DIC LSR OR LSN INPUT FOR TYPE P CONCEPT SCREENING. DIC KMG SIGNIFIES THAT THE RESULTS OF SCREENING REFLECT A POSSIBLE MATCH CONDITION INDICATING THAT THE INPUT REFERENCE NUMBER, MATCHED ONE OR MORE REFERENCE NUMBERS IN THE FLIS FILE, BUT THE INPUT REFERENCE NUMBER CATEGORY CODES AND REFERENCE NUMBER VARIATION CODES DID NOT MEET A VALID RNCC/RNVC MATCHING CRITERIA.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITION 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REVIEW THE FLIS DATA BASE DATA FOR SUITABILITY FOR YOUR APPLICATION. KMG IS SECONDARY OUTPUT WHICH IS GENERATED AS A RESULT OF INPUT DIC LSR OR LSN. PRIMARY OUTPUT IS FORWARDED UNDER DIC KSR. A SEGMENT “J” RECORD REFLECTING OUTPUT DIC KMR FOR THE MATCHING INPUT REFERENCE NUMBER(S) INCLUDED IN YOUR SUBMITTAL PACKAGE WILL ALWAYS PRECEDE THE SECONDARY OUTPUT DIC IN THIS OUTPUT PACKAGE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.2-********139**

## DOCUMENT IDENTIFIER CODE - KMH

TITLE - ACTUAL MATCH (SCREENING)

DEFINITION - OUTPUT AS A RESULT OF DIC LSR OR LSN INPUT FOR TYPE P CONCEPT SCREENING. DIC KMH SIGNIFIES THAT THE RESULTS OF SCREENING REFLECT AN ACTUAL MATCH CONDITION INDICATING THAT THE SUBMITTED REFERENCE NUMBER, ITS FSCM AND APPLICABLE RNCC AND RNVC MATCH A SINGLE NSN UNDER THE RULES OF THE FLIS/RNCC/RNVC VALIDATION CRITERIA.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITION 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REVIEW THE FLIS DATA FOR SUITABILITY FOR YOUR APPLICATION. KMH IS SECONDARY OUTPUT WHICH IS GENERATED AS A RESULT OF INPUT DIC LSR OR LSN. PRIMARY OUTPUT IS FORWARDED UNDER DIC KSR. A SEGMENT “J” RECORD REFLECTING OUTPUT DIC KMR FOR THE MATCHING INPUT REFERENCE NUMBER(S) INCLUDED IN YOUR SUBMITTAL PACKAGE WILL ALWAYS PRECEDE THE SECONDARY OUTPUT DIC IN THIS OUTPUT PACKAGE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.2-********149**

## DOCUMENT IDENTIFIER CODE - KMN

TITLE - MATCHED STOCK NUMBER ASSIGNED BY ANOTHER NATO COUNTRY (SCREENING)

DEFINITION - DIC KMN SIGNIFIES THAT DIC LSF OR LSR MATCHED A STOCK NUMBER ASSIGNED BY A NORTH ATLANTIC TREATY ORGANIZATION COUNTRY OTHER THAN THE UNITED STATES. ONLY THE STOCK NUMBER IS PROVIDED BECAUSE, ACCORDING TO AGREEMENT BY PARTICIPATING NATO COUNTRIES, NO DATA EXCEPT THE STOCK NUMBER CAN BE RELEASED FROM THE FLIS DATA BASE TO ANYONE OUTSIDE THE U.S. GOVERNMENT.

INSTRUCTIONS - 1.REVIEW THE MATCHED STOCK NUMBER TO DETERMINE THE NATO COUNTRY RESPONSIBLE FOR PROVIDING FILE DATA (COMPARE POSITIONS 5 AND 6 OF THE STOCK NUMBER WITH VOLUME 10, TABLE 9). KMN IS SECONDARY OUTPUT. PRIMARY OUTPUT IS FORWARDED UNDER DIC KIS FOR LSF. PRIMARY OUTPUT IS FORWARDED UNDER DIC KSR FOR LSR. A SEGMENT J RECORD REFLECTING OUTPUT DIC KMR WILL PRECEDE KMN WHEN THE SUBMITTED DIC IS LSR. 2.IN ORDER TO BE CONSIDERED FOR NATO STOCK NUMBER FILE DATA, THE FOLLOWING ACTIONS SHOULD BE TAKEN: A. THE NON- GOVERNMENT AGENCY (CONTRACTOR) SHOULD CONTACT THE GOVERNMENT ON WHOSE BEHALF THE WORK IS BEING PERFORMED. B. THE GOVERNMENT AGENCY SHOULD SUBMIT DIC LTI TO DLA LOGISTICS INFORMATION SERVICE TO OBTAIN THE FLIS DATA BASE DATA.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KMP

TITLE - PARTIAL MATCH (SCREENING)

DEFINITION - OUTPUT AS A RESULT OF DIC LSR OR LSN INPUT FOR TYPE S OR TYPE F CONCEPT SCREENING. DIC KMP SIGNIFIES THAT THE RESULTS OF SCREENING REFLECT A PARTIAL MATCH INDICATING THE SUBMITTED REFERENCE NUMBER(S) MATCHED ONE OR MORE NSN WHICH HAVE MORE OR LESS REFERENCE NUMBERS (THAN THOSE SUBMITTED) REFERENCED TO THE MATCHED NSN.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOW, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSATION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REVIEW THE FLIS DATA FOR SUITABILITY FOR YOUR APPLICATION. KMP IS SECONDARY OUTPUT WHICH IS GENERATED AS A RESULT OF INPUT DIC LSR OR LSN. PRIMARY OUTPUT IS FORWARDED UNDER DIC KSR. A SEGMENT “J” RECORD REFLECTING OUTPUT DIC KMR FOR THE MATCHING INPUT REFERENCE NUMBER(S) INCLUDED IN YOUR SUBMITTAL PACKAGE WILL ALWAYS PRECEDE THE SECONDARY OUTPUT DIC IN THIS OUTPUT PACKAGE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KMQ

TITLE - PROBABLE MATCH (SCREENING)

DEFINITION - OUTPUT AS A RESULT OF DIC LSR OR LSN INPUT FOR TYPE P CONCEPT SCREENING. DIC KMQ SIGNIFIES THAT THE RESULTS OF SCREENING REFLECT A PROBABLE MATCH CONDITION INDICATING THAT THE SUBMITTED REFERENCE NUMBER, ITS FSCM AND APPLICABLE RNCC AND RNVC MATCHED MORE THAN ONE NIIN UNDER THE FLIS RNCC/RNVC VALIDATION CRITERIA.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOW, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REVIEW THE FLIS DATA FOR SUITABILITY FOR YOUR APPLICATION. KMQ IS SECONDARY OUTPUT WHICH IS GENERATED AS A RESULT OF INPUT DIC LSR OR LSN. PRIMARY OUTPUT IS FORWARDED UNDER DIC KSR. A SEGMENT “J” RECORD REFLECTING OUTPUT DIC KMR FOR THE MATCHING INPUT REFERENCE NUMBER(S) INCLUDED IN YOUR SUBMITTAL PACKAGE WILL ALWAYS PRECEDE THE SECONDARY OUTPUT DIC IN THIS OUTPUT PACKAGE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.2-********159**

## DOCUMENT IDENTIFIER CODE - KMR

TITLE - MATCHING REFERENCE (SCREENING)

DEFINITION - THE REFERENCE NUMBER REFLECTED IN SEGMENT J RECORD CREATED A MATCH CONDITION. THE DIC REFLECTED IN THE SEGMENT L RECORD, WHICH FOLLOWS THIS DIC, IDENTIFIES THE TYPE/DEGREE OF MATCH CONDITION. (UNMATCHED REFERENCE NUMBER(S) WILL BE IDENTIFIED BY OUTPUT DIC KNR.) THIS SEGMENT J CONTAINS THE REFERENCE DATA AS SUBMITTED IN THE INPUT TRANSACTION. IF THE SUBMITTED CAGE/NATO COMMERCIAL AND GOVERNMENT ENTITY CODE HAS BEEN CANCELED AND REPLACED, A SEGMENT 1 WILL FOLLOW THE APPLICABLE SEGMENT J INDICATING THE SUBMITTED AND CHANGED VALUE. ALL SCREENING RESULTS ARE BASED ON THE USE OF THE REPLACEMENT CAGE/ NATO COMMERCIAL AND GOVERNMENT ENTITY CODE. THE SCREENING RESULTS CAN BE BASED ON BOTH THE REPLACEMENT CAGE CODE/ NATO COMMERCIAL AND GOVERNMENT ENTITY CODE AND THE CANCELED CAGE.

INSTRUCTIONS - KMR IS A SECONDARY OUTPUT AS A RESULT OF INPUT DIC LSA, LSB, LSR OR LSN. PRIMARY OUTPUT IS FORWARDED UNDER DIC KSR.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KMS

TITLE - REFERENCE NUMBER SUBMITTED FOR SCREENING MATCHED TO A SECURITY CLASSIFIED ITEM

DEFINITION - THE REFERENCE NUMBER SUBMITTED FOR SCREENING MATCHED AN ITEM IN THE FLIS DATA BASE THAT IS SECURITY CLASSIFIED. NO FILE DATA WILL BE OUTPUT. THIS SEGMENT J CONTAINS THE REFERENCE DATA AS SUBMITTED IN THE INPUT TRANSACTION. IF THE SUBMITTED CAGE/ NATO COMMERCIAL AND GOVERNMENT ENTITY CODE HAS BEEN CANCELLED AND REPLACED, A SEGMENT 1 WILL FOLLOW THE APPLICABLE SEGMENT J INDICATING THE SUBMITTED AND CHANGED VALUE. ALL SCREENING RESULTS ARE BASED ON THE USE OF THE REPLACEMENT CAGE/ NATO COMMERCIAL AND GOVERNMENT ENTITY CODE. THE SCREENING RESULTS CAN BE BASED ON BOTH THE REPLACEMENT CAGE CODE/ NATO COMMERCIAL AND GOVERNMENT ENTITY CODE AND THE CANCELED CAGE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.VERIFY SUBMITTED REFERENCE NUMBER; IF IN ERROR CORRECT AND RESUBMIT. SECONDARY OUTPUT AS A RESULT OF INPUT DIC LSA, LSB, LSR, OR LSN. PRIMARY OUTPUT IS FORWARDED UNDER DIC KSR. DRN 4080 OR 5020 (CARD 2) WILL BE OUTPUT WITH THIS DIC ONLY WHEN IT WAS INPUT WITH DIC LSA.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KMT

TITLE - STANDARDIZATION RELATIONSHIP PREFERRED ITEM DATA

DEFINITION - FLIS DATA IS FORWARDED FOR THE STANDARD OR REPLACEMENT NSN/PSCCN WHICH IS RELATED TO A NON-STANDARD NSN ENCOUNTERED AS A RESULT OF A SUBMITTED SEARCH TRANSACTION (LSF, LSR, LSN).

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOW, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.DATA IS OUTPUT SUBSEQUENT TO, AND IN ADDITION TO, FILE DATA FOR THE SUBMITTED NIIN (LSF) OR MATCHED NSN (LSR, LSN) UTILIZING THE SAME CONTROL DATA ELEMENTS.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.2-********169**

## DOCUMENT IDENTIFIER CODE - KMU

TITLE - EXACT MATCH WITH ERRORS IN SUBMITTED FII (SUBMITTER)

DEFINITION - YOUR SUBMITTAL, WHICH CONTAINED ERROR CONDITION(S), REQUESTING NIIN ASSIGNMENT, OR REINSTATEMENT OF AN FII (NIIN ONLY), OR REVISION OF AN FII (NIIN ONLY), REVISION (ADJUSTMENT) OF AN FII (NIIN), TRANSFER OF AN FII (NIIN ONLY), OR THE ADDITION, DELETION OR CHANGE OF REFERENCE NUMBER(S) AND RELATED DATA WAS REVEALED DURING PROCESSING TO BE AN ACTUAL DUPLICATE OF AN EXISTING FII. FLIS DATA CODED KFD FOR THE ACTUAL DUPLICATE IS FORWARDED. IN ADDITION, A SEGMENT P OR Q RECORD(S) IDENTIFYING THE ERROR CONDITION(S) WILL BE INCLUDED IN THE OUTPUT AND WILL PRECEDE THE KFD DATA. A SEGMENT 1 MAY ALSO BE PROVIDED REFLECTING THE SUBMITTED AND CHANGED VALUE. ALL SCREENING RESULTS ARE BASED ON THE USE OF THE REPLACED CAGE/ NATO COMMERCIAL AND GOVERNMENT ENTITY CODE.

INSTRUCTIONS - SEE INSTRUCTIONS FOLLOWING FORMAT MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

1. To eliminate multiple entries of control data elements in the fixed DIC format, these elements are shown in the first card image only. Control data elements as shown are required in positions 1-39 of all segment card images in the transaction package. The PSN (DRN 1070 ) in card columns 4-6 must be incremented by one (1) in each card.

2. If your submittal was for National Item Identification Number (NIIN) assignment and the matching FLIS data contains an NSN:

3. If your submittal was a request for reinstatement of a Federal Item Identification (FII) and the matching FLIS data contains an NSN:

4. If your submittal was a request for revision of an FII; revision (adjustment) of an FII; transfer of an FII; or the addition, deletion, or change of reference number(s) and related data; and the matching FLIS data contains an NSN:

Review the FLIS data. Submit, if applicable, an LKD transaction in accordance with the Priority for Cancellation Table (volume 10, table 12 ). If necessary, correct errors and resubmit.

## DOCUMENT IDENTIFIER CODE - KNA

TITLE - NOTIFICATION OF APPROVAL

DEFINITION - YOUR ACTIVITY WAS RECORDED IN THE ORIGINATING OR SUBMITTING ACTIVITY FIELD OF A TRANSACTION, REPRESENTED BY THIS DOCUMENT NUMBER, WHICH HAS BEEN PROCESSED AND APPROVED. A SEGMENT 1 MAY ALSO BE PROVIDED REFLECTING THE SUBMITTED AND CHANGED VALUE. ALL SCREENING RESULTS ARE BASED ON THE USE OF THE REPLACED CAGE/ NATO COMMERCIAL AND GOVERNMENT ENTITY CODE.

INSTRUCTIONS - THIS NOTIFICATION IS FORWARDED TO ADVISE YOUR ACTIVITY OF THIS APPROVED ACTION. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

D3A01		D3A03		D3A05		D3A06		D3A07		D3F01		D3F02 D3F04	D3F05		D3F07		D3F09		D3K00		D3N01		D3N04

D3Y00

**DRN	DATA ELEMENT/IDENTIFIER NAME	FORMAT**

**SEG CODE**

**INST/ NOTES**

**CARD COLUMN**

 9977	CHANGED DRN/MRC VALUE/REPLY	0005X	1	01	64-68

## DOCUMENT IDENTIFIER CODE - KNI

TITLE - CONFLICT NOTIFICATION

DEFINITION - THE INPUT TRANSACTION DIC IDENTIFIED IN THE OUTPUT HEADER HAS BEEN PROCESSED AND THE DATA HAS BEEN RECORDED IN THE FLIS DATABASE “CURRENT” OR “FUTURE” FILE. A CONFLICT WAS REVEALED DURING THAT PROCESSING.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOW, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.SEE VOLUME 10, TABLE 109 FOR THE CONFLICT CODE DEFINITION. REVIEW THE SPECIFIC CONFLICT CODE(S) CONTAINED IN THE SEGMENT R AND SUBMIT THE NECESSARY CORRECTIVE ACTION. THE FIRST SEGMENT R WILL CONTAIN THE DRN AND VALUE OF THE APPLICABLE CONFLICT CODE. THE SECOND SEGMENT R IN THIS OUTPUT WILL CONTAIN THE DRN AND VALUE OF THE DATA ELEMENT(S) OR DATA ELEMENT CHAIN IN CONFLICT. SEGMENT R WILL BE REPEATED AS REQUIRED. 3.IF THIS OUTPUT CONTAINS A NATO/FG CODE IN THE SUBMITTING ACTIVITY CODE FIELD, FORWARD THE OUTPUT TO ACTIVITY 9Z FOR RESOLUTION.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3A01		D3A03	D3A06	D3A07	D3F01	D3F04	D3F05 D3F09	D3Y00

## DOCUMENT IDENTIFIER CODE - KNN

TITLE - NOTIFICATION OF NATIONAL CODIFICATION BUREAU (NCB) PROCESSING

DEFINITION - YOUR ACTIVITY WAS RECORDED IN THE ORIGINATING OR SUBMITTING ACTIVITY FIELD OF A TRANSACTION, REPRESENTED BY THIS DOCUMENT NUMBER, AGAINST A NATO STOCK NUMBER OR A NON-US REFERENCE NUMBER. THE TRANSACTION HAS BEEN PREEDITED AND FORWARDED TO DLA LOGISTICS INFORMATION SERVICE FOR TRANSMITTAL OF AN INTERNATIONAL TRANSACTION TO THE APPROPRIATE NATO COUNTRY FOR PROCESSING. OUTPUT RESULTS WILL BE FORWARDED SUBSEQUENT TO PROCESSING THROUGH THE NATO COUNTRY DATA SYSTEM AND FLIS DATA BASE UPDATE (IF APPROPRIATE). IF A SUBMITTED NATO COMMERCIAL AND GOVERNMENT ENTITY (NATO COMMERCIAL AND GOVERNMENT ENTITY CODE) HAS BEEN CANCELLED AND REPLACED. A SEGMENT 1 WILL FOLLOW THE OUTPUT HEADER INDICATING THE SUBMITTED AND CHANGED VALUE.

INSTRUCTIONS - APPLICABLE TO LAR/LCR/LDR, LAU (FOR FIRST U.S. ACTIVITY REGISTRATION), LSB, LTI, LSN, AND LMD (LAR/LCR/LDR ONLY). TO BE FORWARDED TO U.S. ACTIVITIES ONLY.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**DRN	DATA ELEMENT/IDENTIFIER NAME	FORMAT**

**SEG CODE**

**INST/ NOTES**

**CARD COLUMN**

**8.2-********179**

 9977	CHANGED DRN/MRC VALUE/REPLY	0005X	1	01	64-68

## DOCUMENT IDENTIFIER CODE - KNR

TITLE - NEGATIVE REPLY (SCREENING)

DEFINITION - YOUR SUBMITTAL OF A REFERENCE NUMBER TO BE SCREENED AGAINST THE FLIS DATA BASE TO OBTAIN RELATED NSN(S) HAS BEEN PROCESSED. HOWEVER, THE SUBMITTED REFERENCE NUMBER IS NOT RECORDED IN THE FLIS DATA BASE, OR WAS NOT RELEVANT TO THE HIGHEST DEGREE OF MATCH OUTPUT FOR THE PACKAGE. NOTE: CARD 2 IS OUTPUT ONLY IN RESPONSE TO NATO/FOREIGN GOVERNMENT INPUT. SEGMENT J CONTAINS THE REFERENCE DATA AS SUBMITTED. IF THE SUBMITTED CAGE/ NATO COMMERCIAL AND GOVERNMENT ENTITY CODE HAS BEEN CANCELED AND REPLACED, A SEGMENT 1 WILL FOLLOW THE APPLICABLE SEGMENT J INDICATING THE SUBMITTED AND CHANGED VALUE. THE SCREENING RESULTS CAN BE BASED ON BOTH THE REPLACEMENT CAGE/NATO COMMERCIAL AND GOVERNMENT ENTITY CODE AND THE CANCELED CAGE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.DETERMINE IF THE CORRECT CAGE AND REFERENCE NUMBER(S) WERE SUBMITTED. IF NOT, CORRECT AND RESUBMIT.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KNS

TITLE - NOTIFICATION OF CHANGE TO STANDARDIZATION DECISION DATA (STANDARDIZATION ORIGINATOR)

DEFINITION - A SUBMITTAL OF A CANCELLATION-DUPLICATION TRANSACTION THAT WAS PROCESSED AND APPROVED AND WOULD HAVE CREATED AN INVALID STANDARDIZATION REPLACEMENT RELATIONSHIP WITH THE RETAINED NSN INSTEAD OF THE CANCELLED NSN/PSCN. DLSC HAS CHANGED THE RETAINED NSN STANDARDIZATION DECISION DATA TO REFLECT THE CANCELLED NSN/PSCN STANDARDIZATION DECISION DATA TO REFLECT A VALID COMBINATION OF ITEM STANDARDIZATION CODES FOR THE STANDARDIZATION RELATIONSHIP(S). THE DELETED STANDARDIZATION RELATIONSHIP WILL BE FORWARDED UNDER OUTPUT DIC KDS, THE CURRENT STANDARDIZATION RELATIONSHIP UNDER OUTPUT DIC KAS.

INSTRUCTIONS - THIS NOTIFICATION IS FORWARDED TO ADVISE YOUR ACTIVITY OF THIS CONDITION. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KPA

TITLE - ADD PACKAGING DATA

DEFINITION - THE DATA ELEMENTS REFLECTED IN THE PACKAGING SEGMENT HAVE BEEN ADDED FOR THE NSN REFLECTED IN THE OUTPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REPLACE THIS PACKAGING DATA TO YOUR FILE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KPC

TITLE - CHANGE PACKAGING DATA

DEFINITION - THE DATA ELEMENTS REFLECTED IN THE PACKAGING SEGMENT HAVE BEEN CHANGED FOR THE NSN REFLECTED IN THE OUTPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REPLACE THE PACKAGING DATA TO YOUR FILE WITH THIS DATA.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KPD

TITLE - DELETE PACKAGING DATA

DEFINITION - PACKAGING DATA HAS BEEN DELETED FROM THE NSN REFLECTED IN THE OUTPUT HEADER. INSTRUCTIONS - DELETE PACKAGING DATA FOR THIS NSN IN YOUR FILE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KPE

TITLE - POSSIBLE DUPLICATE WITH ERRORS IN SUBMITTED FII (SUBMITTER)

DEFINITION - YOUR SUBMITTAL, (WHICH CONTAINED ERRORS) REQUESTING NIIN ASSIGNMENT, OR REINSTATEMENT OF AN FII (NIIN ONLY); REVISION OF AN FII (NIIN ONLY), REVISION (ADJUSTMENT) OF AN FII (NIIN), TRANSFER OF AN FII (NIIN ONLY), OR THE ADDITION, DELETION OR CHANGE OF REFERENCE NUMBER(S) AND RELATED DATA WAS REVEALED DURING PROCESSING TO BE A POSSIBLE DUPLICATE OF AN EXISTING FII. FLIS DATA CODED KFD FOR THE POSSIBLE DUPLICATE IS FORWARDED. IN ADDITION, A SEGMENT P OR Q RECORD(S) IDENTIFYING THE ERROR CONDITIONS WILL BE INCLUDED IN THE OUTPUT AND WILL PRECEDE THE KFD DATA. IF THE OUTPUT CONTAINS A PURGE DATE, THE ORIGINAL SUBMITTAL HAS BEEN PLACED IN THE SUSPENSE FILE. A SEGMENT 1 MAY ALSO BE PROVIDED REFLECTING THE SUBMITTED AND CHANGED VALUE. ALL SCREENING RESULTS ARE BASED ON THE USE OF THE REPLACED CAGE/NATO COMMERCIAL AND GOVERNMENT ENTITY CODE.

INSTRUCTIONS - SEE INSTRUCTIONS FOLLOWING FORMAT MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

**8.2-********189**

## POSSIBLE DUPLICATE WITH ERRORS IN SUBMITTED FII (SUBMITTER) (INSTRUCTIONS)

1. To eliminate multiple entries of control data elements in the fixed DIC format, these elements are shown in the first card image only. Control data elements as shown are required in positions 1-39 of all segment card images in the transaction package. The PSN (DRN 1070 ) in card columns 4-6 must be incremented by one (1) in each card.

2. If your submittal was for National Item Identification Number (NIIN) assignment and the matching FLIS data contains an NSN:

3. If your submittal was a request for reinstatement of a Federal Item Identification (FII) and the matching FLIS data contains an NSN:

4. If your submittal was a request for revision of an FII; revision (adjustment) of an FII; transfer of an FII: or the addition, deletion, or change of reference number(s) and related data; and the matching FLIS data contains an NSN:

Review the FLIS data. If the NSN is acceptable for your application, submit, if applicable, an LAD, LAU, or LCU transaction. Submit, if applicable, an LKD transaction in accordance with the Priority for Cancellation Table (volume 10, table 12 ) or correct the submittal errors, apply the appropriate justification code(s), and resubmit.

## DOCUMENT IDENTIFIER CODE - KPM

TITLE - PROCESSING MALFUNCTION

DEFINITION - THIS DIC SIGNIFIES THAT OUTPUT TRANSACTIONS WERE GENERATED BY FLIS DURING A HARDWARE/SOFTWARE MALFUNCTION, AND OUTPUT HAS BEEN REPROCESSED AFTER THE ERRONEOUS CONDITION HAS BEEN CORRECTED. DATA OUTPUT BY THIS DIC WILL BE USED TO REPLACE ERRONEOUS DATA PREVIOUSLY TRANSMITTED, OR MISSING OUTPUT DATA LOST BETWEEN PROCESSING AND TRANSMISSION.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOW, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.USE THIS OUTPUT TO REPLACE DATA PREVIOUSLY RECEIVED WITH A MATCHING DOCUMENT CONTROL NUMBER. IF DIC DOES NOT MATCH DOCUMENT CONTROL NUMBER OF ANY DATA PREVIOUSLY RECEIVED, PROCESS AS NORMALL OUTPUT DATA.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3A01		D3A03	D3A06	D3A07	D3F02	D3F04	D3F05 D3F07	D3Y00

## DOCUMENT IDENTIFIER CODE - KRE

TITLE - NOTIFICATION OF RETURN (SUBMITTER)

DEFINITION - USED TO NOTIFY THE ACTIVITY IN THE SUBMITTING ACTIVITY FIELD THAT A TRANSACTION REPRESENTED BY THIS DOCUMENT NUMBER CONTAINED ERRORS. A MAXIMUM OF 10 ERRORS MAY BE RETURNED FOR AN INPUT TRANSACTION.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOW, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. IF SEGMENT K IS PRESENT, CC 27-39 MAY CONTAIN DRN 3790 (CANCELED NSN) 2.SEGMENTS P, Q OR K MAY BE USED WITH THIS DIC UNDER THE FOLLOWING CONDITIONS: SEGMENT P WILL REFLECT ONLY THE DRN/MRC AND THE APPLICABLE RETURN CODES IDENTIFYING THE SPECIFIC ERROR CONDITION(S). SEGMENT Q WILL BE REPEATED AS REQUIRED AND WILL REFLECT THE DRN/MRC, APPLICABLE RETURN CODE(S) IDENTIFYING THE SPECIFIC ERROR CONDITION(S) AND THE VALUE OF EACH RETURNED DRN/MRC IS INCLUDED. SEGMENT K WILL BE REPEATED AS REQUIRED AND USED WITH THIS DIC WHEN THE STATUS OF THE NIIN IS NOT APPROPRIATE FOR THE INPUT DIC. SEGMENT K WILL NEVER BE THE ONLY SEGMENT USED WITH THIS DIC. AS A MINIMUM, THERE MUST BE A CORRESPONDING SEGMENT P WITH A RETURN CODE INDICATING THE NECESSITY FOR THIS SEGMENT. 3.TO AUTOMATICALLY INCLUDE SEGMENT Z DATA (DRN 9119) TO REFLECT AN INCOMPATIBILITY WITH PENDING FUTURE EFFECTIVE DATED ACTIONS.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3A01		D3A03		D3A05		D3A06		D3A07		D3F01		D3F02 D3F04	D3F05		D3F07		D3F09		D3G03		D3G06		D3G09

D3G10	D3G11	D3G13	D3G17	D3K00	D3N01	D3N03 D3N04	D3Y00

## DOCUMENT IDENTIFIER CODE - KRF

TITLE - RETURN OF CANCELLATION ACTION, RETAINED FII INVALID

DEFINITION - YOUR SUBMITTAL TO CANCEL AS DUPLICATE (LKD) OR TO CANCEL-USE (LKU) IS RETURNED BECAUSE THE NATIONAL ITEM IDENTIFICATION NUMBER IN THE REPLACEMENT NSN FIELD OF THE SUBMITTED SEGMENT T DOES NOT REPRESENT AN EXISTING FEDERAL ITEM IDENTIFICATION (NIIN STATUS CODE 3, 4, 5, 7 OR 8). THE STATUS CODE FOR THE PROPOSED REPLACEMENT NSN WILL BE REFLECTED IN THE RETURNED SEGMENT K, WHICH WILL ALSO CONTAIN A VALID REPLACEMENT/USE NIIN , IF APPLICABLE. IN ADDITION, A SEGMENT L REFLECTING THE SUBMITTED PROPOSED REPLACEMENT/USE NSN IS INCLUDED IN THIS OUTPUT. A SEGMENT 1 MAY ALSO BE PROVIDED REFLECTING THE SUBMITTED AND CHANGED VALUE. ALL SCREENING RESULTS ARE BASED ON THE USE OF THE REPLACED VALUE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REVIEW THE REPLACEMENT NSN. IF INCORRECT, CORRECT AND RESUBMIT. IF CORRECT, TAKE APPROPRIATE ACTION BASED ON THE STATUS OF THE REPLACEMENT NSN.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.2-********199**

## DOCUMENT IDENTIFIER CODE - KRM

TITLE - NOTIFICATION OF EXACT MATCH (SUBMITTER)

DEFINITION - YOUR SUBMITTAL REQUESTING NIIN ASSIGNMENT/REINSTATEMENT OF FII (NIIN ONLY); REVISION OF FII (NIIN ONLY); REVISION (ADJUSTMENT) OF FII (NIIN ), TO TRANSFER FII (NIIN ONLY); OR ADDITION, DELETION OR CHANGE OF REFERENCE NUMBER(S) AND RELATED DATA; OR ATTEMPT TO TRANSFER REFERENCE NBR AS A RESULT OF YOUR CANCEL-DUPLICATE ACTION, WAS REVEALED DURING PROCESSING TO BE ACTUAL DUPLICATE OF EXISTING FII. FLIS DATA CODED KFD FOR ACTUAL DUPLICATE IS FORWARDED. SUBMITTED ADDITIONAL REFERENCE NBR(S), MOE RULE NBR(S), ITEM MGMT STATUS CODES, AND OTHER SUPPLEMENTARY AUTHORIZED DATA COLLARBORATORS/RECEIVERS NOT REPRESENTED BY MOE RULE NBR WILL NOT BE ADDED TO DUPLICATE FII (NIIN). A SEGMENT 1 MAY ALSO BE PROVIDED REFLECTING THE SUBMIITED AND CHANGED VALUE. ALL SCREENING RESULTS ARE BASED ON THE USE OF THE REPLACED CAGE/NATO COMMERCIAL AND GOVERNMENT ENTITY CODE.

INSTRUCTIONS - SEE INSTRUCTIONS FOLLOWING FORMAT. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

**DRN	DATA ELEMENT/IDENTIFIER NAME	FORMAT**

**SEG CODE**

**INST/ NOTES**

**CARD COLUMN**

 9977	CHANGED DRN/MRC VALUE/REPLY	0005X	1	01	64-68

## NOTIFICATION OF EXACT MATCH (SUBMITTER) (INSTRUCTIONS)

1. If your submittal was for National Item Identification Number (NIIN) assignment or NSN reinstatement and the matching FLIS data contains an NSN:

2. If your submittal was for revision of a Federal Item Identification (FII); revision (adjustment) of an FII; transfer of an FII; or the addition, deletion, or change of reference number(s) and related data; and the matching FLIS data contains an NSN:

Review the FLIS data. Submit, if applicable, an LKD transaction in accordance with the Priority for Cancellation Table (volume 10, table 12 ).

## DOCUMENT IDENTIFIER CODE - KRP

TITLE - NOTIFICATION OF POSSIBLE DUPLICATE (SUBMITTER)

DEFINITION - YOUR SUBMITTAL REQUESTING NIIN ASSIGNMENT; REINSTATEMENT OF AN FII (NIIN ONLY); REVISION OF AN FII (NIIN ONLY); REVISION (ADJUSTMENT) OF AN FII (NIIN ONLY); TRANSFER OF AN FII (NIIN ONLY); OR THE ADDITION, DELETION OR CHANGE OF REFERENCE NUMBER(S) AND RELATED DATA, OR AN ATTEMPT TO TRANSFER A REFERENCE NUMBER AS A RESULT OF YOUR CANCEL-DUPLICATE ACTION, WAS REVEALED DURING PROCESSING TO BE A POSSIBLE DUPLICATE OF AN EXISTING FII. FLIS DATA CODED KFD FOR POSSIBLE DUPLICATE IS FORWARDED. IF THE OUTPUT CONTAINS A PURGE DATE, THE ORIGINAL SUBMITTAL HAS BEEN PLACED IN THE SUSPENSE FILE. A SEGMENT 1 MAY ALSO BE PROVIDED REFLECTING THE SUBMITTED AND CHANGED VALUE. ALL SCREENING RESULTS ARE BASED ON THE USE OF THE REPLACED VALUE.

INSTRUCTIONS - SEE INSTRUCTIONS FOLLOWING FORMAT. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

## NOTIFICATION OF POSSIBLE DUPLICATE (SUBMITTER) (INSTRUCTIONS)

1. If your submittal was for National Item Identification Number (NIIN) assignment or reinstatement of an NSN and the matching FLIS data contains an NSN:

Review the FLIS data. If the NSN is acceptable for your application, submit, as applicable, an LAD, LAU, or LCU transaction. If the NSN is not acceptable, resubmit transaction with the appropriate Reference Number Justification Code (volume 10, table 4 ).

2. If your submittal was for revision of an NSN; revision (adjustment) of an NSN; transfer of an NSN; or the addition, deletion, or change of reference number(s) and related data; and the matching FLIS data contains an NSN:

Review the FLIS data. If the NSN is acceptable for your application, submit LAD, LAU, or LCU if appropriate. Submit, if applicable, an LKD transaction in accordance with the Priority for Cancellation Table (Volume 10, Table 12 ), or apply the appropriate Reference Number Justification Code (Volume 10, Table 4 ), and resubmit.

## DOCUMENT IDENTIFIER CODE - KRU

TITLE - NOTIFICATION OF UNPROCESSABLE PACKAGE (SUBMITTER)

DEFINITION - YOUR SUBMITTAL IS RETURNED BECAUSE A CONTROL ELEMENT(S) REQUIRED FOR PROCESSING WAS MISSING OR NOT IDENTIFIABLE CAUSING THE TRANSACTION TO BE UNPROCESSABLE.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.SINCE THIS TRANSACTION DIC WAS NOT SUBJECTED TO THE SYSTEM EDITS, SCREENS AND OTHER PROCESSES BECAUSE OF THE MISSING OR INCORRECT CONTROL ELEMENT(S) THE TRANSACTION MUST BE CORRECTED AND RESUBMITTED IN ITS ENTIRETY. SEE THE ENCLOSED SEGMENT(S) P AND/OR Q WHICH REFLECT THE RETURN CODE(S) AND APPLICABLE DRNS AND (Q ONLY) THE EDITED VALUES TO DETERMINE THE CORRECTIONS REQUIRED.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3A01		D3A03		D3A05		D3A06		D3A07		D3F01		D3F02 D3F04	D3F05		D3F07		D3F09		D3G03		D3G09		D3G11

D3G13	D3K00	D3N01	D3N03	D3N04	D3Y00

## DOCUMENT IDENTIFIER CODE - KSN

TITLE - RESULTS OF CHARACTERISTIC(S) SEARCH (NO MATCH)

DEFINITION - DIC KSN IS USED TO INDICATE THAT YOUR SEARCH REQUEST (LSC) WITH SPECIFIC CHARACTERISTICS DATA ELEMENTS HAS BEEN PROCESSED. HOWEVER, YOUR SUBMITTED DATA DID NOT PRODUCE A RECORDED CHARACTERISTIC MATCH WITHIN THE FLIS DATA BASE FOR THE SUBMITTAL AS REFLECTED IN THE OUTPUT HEADER. THIS TRANSACTION WILL BE OUTPUT TO THE ACTIVITIES AUTHORIZED BY THE PROVISIONING SCREENING MASTER ADDRESS TABLE (VOLUME 10, TABLE 23) IN ACCORDANCE WITH THE SINGLE/MULTIPLE OUTPUT CODE (DRN 4535) SUBMITTED ON INPUT.

INSTRUCTIONS - VERIFY THE SUBMITTED SEARCH REQUEST; IF IN ERROR, CORRECT AND RESUBMIT. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION - D3G10

**8.2-********209**

## DOCUMENT IDENTIFIER CODE - KSR

TITLE - SCREENING RESULTS

DEFINITION - USED IN THE OUTPUT HEADER AS THE PRIMARY OUTPUT DIC FOR SCREENING. ONE OR MORE OTHER OUTPUT DICS WILL BE INCLUDED TO REFLECT SPECIFIC SCREENING RESULTS. THE ADDITIONAL OUTPUT WILL BE A PART OF THIS PACKAGE AND WILL IMMEDIATELY FOLLOW THE KSR OUTPUT HEADER.

INSTRUCTIONS - NONE MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KSS

TITLE – DLA TRANSACTION SERVICES SOURCE OF SUPPLY UPDATE

DEFINITION - THIS NOTIFICATION IS PROVIDED TO ADD, CHANGE, INACTIVATE, OR DELETE SOURCE OF SUPPLY FOR ROUTING MILSTRIP (MILITARY STANDARD REQUISITIONING AND ISSUE PROCEDURES) REQUISITIONS AT THE DEFENSE AUTOMATIC ADDRESSING SYSTEM. ALL OUTPUT OF THIS SEGMENT WILL BE IN FIXED FORMAT, REGARDLESS OF THE MEDIA USED FOR TRANSMISSION.

INSTRUCTIONS - ADD THIS DATA TO YOUR FILES. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

D3A01	D3A03	D3A07	D3F01	D3F05	D3F07	D3Y00

## DOCUMENT IDENTIFIER CODE - KTA

TITLE - MASS DATA RETRIEVAL RESULTS (FLIS DATA BASE)

DEFINITION - THIS DIC IS DESIGNED TO FORWARD THE RESULTS OF A FLIS DATA BASE MASS DATA RETRIEVAL TRANSACTION. THE NSNS AND REQUESTED FLIS DATA BASE SEGMENTS APPLICABLE TO THE SUBMITTED KEY DATA ELEMENT(S) ARE FORWARDED.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. IF SEGMENT K IS PRESENT, CC 27-39 MAY CONTAIN DRN 3790 (CANCELED NSN) 2.THIS OUTPUT IS GENERATED AS A RESULT OF A DLA LOGISTICS INFORMATION SERVICE INTERNAL DIC LTM, SUBMITTED AS REQUESTED BY YOUR ACTIVITY. ALL OUTPUT ITEMS APPLICABLE TO THE INPUT LTM TRANSACTION WILL INCLUDE THE SAME DOCUMENT CONTROL NUMBER. A SEPARATE KTA WILL BE OUTPUT FOR EACH NIIN WITH THE REQUESTED FLIS DATA BASE SEGMENTS. THE PACKAGE SEQUENCE NUMBER (PSN) WILL BE APPLIED TO THE RECORDS FOR EACH NIIN AS A SEPARATE PACKAGE WITHIN THE OVER- ALL DOCUMENT CONTROL NUMBER PACKAGE. THE ITEMS WITHIN THE OVER-ALL PACKAGE WILL BE IN NIIN SEQUENCE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KTD

TITLE - TOTAL DATA

DEFINITION - TOTAL CHARACTERISTICS DATA IS FORWARDED AS A RESULT OF: (1) ADD, DELETE OR CHANGE OF CHARACTERISTICS DATA, OR (2) FEDERAL SUPPLY CLASS ONLY, OR (3) FSC AND ITEM NAME, OR (4) FSC AND TYPE, OR (5) FSC, ITEM NAME AND TYPE FOR THE NSN REFLECTED IN THE OUTPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REPLACE THE CHARACTERISTICS DATA IN YOUR FILE FOR THE NSN WITH THIS NEW DATA.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

**8.2-********219**

## DOCUMENT IDENTIFIER CODE - KTN

TITLE - INTERROGATED/SEARCH DATA NOT AVAILABLE

DEFINITION - YOUR INTERROGATION/SEARCH REQUEST FOR SPECIFIC DATA ELEMENTS OR DATA GROUPS HAS BEEN PROCESSED; HOWEVER, THE REQUESTED DATA IS NOT RECORDED IN THE FLIS DATA BASE FOR THE NSN REFLECTED IN THE OUTPUT HEADER. THE SUBMITTED NATIONAL ITEM IDENTIFICATION NUMBER IS VALID BUT THE DATA REQUESTED WAS NOT AVAILABLE, SUCH AS REQUESTED MAJOR ORGANIZATIONAL ENTITY (MOE) RULE DATA (SEGMENT B) FOR A NIIN STATUS CODE 6 ITEM OR AN ITEM WITH NO CATALOG MANAGEMENT DATA (SEGMENT H) RECORDED.

INSTRUCTIONS - VERIFY THE SUBMITTED NSN; IF IN ERROR, CORRECT AND RESUBMIT. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KTQ

TITLE - TAILORED CHARACTERISTICS DATA (DEFENSE SUPPLY CENTERS ONLY)

DEFINITION - TAILORED CHARACTERISTICS DATA IS FORWARDED AS A RESULT OF: (1) ADD, DELETE OR CHANGE OF CHARACTERISTICS DATA, OR (2) FEDERAL SUPPLY CLASS ONLY, OR (3) FSC AND ITEM NAME, OR (4) FSC AND TYPE, OR (5) FSC, ITEM NAME AND TYPE FOR THE NSN REFLECTED IN THE OUTPUT HEADER.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. 2.REPLACE THE CHARACTERISTICS DATA IN YOUR FILE FOR THE NSN WITH THIS NEW DATA.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KTS

TITLE - INTERROGATION RESULTS MINUS SECURITY CLASSIFIED CHARACTERISTICS DATA

DEFINITION - FLIS DATA BASE RECORD/INTERCHANGEABILITY AND SUBSTITUTABILITY (FLIS/I&S) DATA IS FORWARDED FOR THIS NSN; HOWEVER, CHARACTERISTICS DATA IS NOT INCLUDED INASMUCH AS THIS DATA IS SECURITY CLASSIFIED.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD.

2.CHARACTERISTICS DATA MUST BE REQUESTED FROM THE APPLICABLE PRIMARY INVENTORY CONTROL ACTIVITY.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

## DOCUMENT IDENTIFIER CODE - KUA

TITLE - ADD TOTAL CATALOG TOOLS MOE RULE RECORD

DEFINITION - A NEW CATALOG TOOLS MOE RULE HAS BEEN ESTABLISHED OR A PREVIOUSLY CANCELLED CATALOG TOOLS MOE RULE HAS BEEN REINSTATED.

INSTRUCTIONS - ADD TOTAL NEW MOE RULE RECORD TO YOUR FILE. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

**8.2-********229**

## DOCUMENT IDENTIFIER CODE - KUB

TITLE - CANCEL CATALOG TOOLS MOE RULE WITH REPLACEMENT

DEFINITION - THE MOE RULE REFLECTED IN THE CATALOG TOOLS MOE RULE MAINTENANCE SEGMENT (801) HAS BEEN CANCELLED AND REPLACED BY THE MOE RULE REFLECTED IN THE SEGMENT (803) NOTE.

INSTRUCTIONS - CANCEL THIS MOE RULE AND APPLY THE CATALOG TOOLS MOE RULE SHOWN IN THE MANAGEMENT EXCEPTION NOTES SEGMENT (803). THE PREVIOUS SEGMENT (802) WILL ALSO BE RETAINED.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3Y00

## DOCUMENT IDENTIFIER CODE - KUC

TITLE - CHANGE CATALOG TOOLS MOE RULE RECORD

DEFINITION - A CHANGE INVOLVING EITHER THE ITEM IDENTIFICATION SUBMITTER, COLLABORATOR, RECEIVER OR MOE RULE MANAGEMENT EXCEPTION NOTES HAS BEEN PROCESSED AND APPROVED.

INSTRUCTIONS - REPLACE TOTAL MOE RULE RECORD WITH FURNISHED DATA. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION - D3Y00

## DOCUMENT IDENTIFIER CODE - KUD

TITLE - CANCEL WITHOUT REPLACEMENT OR DELETE CATALOG TOOLS MOE RULE RECORD DEFINITION - USED TO CANCEL OR DELETE A MOE RULE BASED UPON MOE RULE STATUS CODE.

INSTRUCTIONS - IF MOE RULE STATUS CODE EQUALS 1 (CANCELLED WITHOUT REPLACEMENT) IN CARD COLUMN 36, THE CANCELLED MOE RULE WILL BE RETAINED AS REFERENCED INFORMATION IN YOUR FILE. IF STATUS CODE IS NOT PRESENT, DELETE THIS MOE RULE FROM FILE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3Y00

## DOCUMENT IDENTIFIER CODE - KUE

TITLE - NEW CATALOG TOOLS STANDARD FSC MANAGEMENT RECORD

DEFINITION - THIS DIC IS THE RESULT OF NEW FSC MANAGEMENT RECORD BEING ESTABLISHED FOR THE FIRST TIME OR PROVIDES A NEW UPDATED FSC MANAGEMENT RECORD DUE TO DATA ELEMENTS BEING ADDED, CHANGED OR DELETED AGAINST A PREVIOUSLY ESTABLISHED RECORD (TOTAL OVERLAY CONCEPT APPLIES).

INSTRUCTIONS - ASSIGN THIS NEW MANAGEMENT RECORD FOR CITED FSC TO YOUR FILE. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

D3F08	D3Y00

## DOCUMENT IDENTIFIER CODE - KUF

TITLE - DELETE TOTAL CATALOG TOOLS STANDARD FSC MANAGEMENT RECORD

DEFINITION - THE FSC REFLECTED IN CC 39-42 IS NO LONGER VALID. THE FSC AND THE RELATED MANAGEMENT DATA HAS BEEN DELETED FROM THE SYSTEM SUPPORT RECORD STANDARD FSC MANAGEMENT TABLE.

INSTRUCTIONS - DELETE THE FSC AND ITS ATTRIBUTE MANAGEMENT DATA FROM YOUR FILES. MEDIA/FORMAT - FIXED LENGTH

FUNCTIONAL DESCRIPTION SECTION -

D3D00	D3Y00

## DOCUMENT IDENTIFIER CODE - KVI

TITLE - ITEM MANAGEMENT CODING ADVICE NOTIFICATION

DEFINITION - FORWARDED IS THIS ITEM MANAGEMENT CODING (IMC) ADVICE NOTIFICATION RECORD. THE KVI IS OUTPUT, BY SPECIAL PROJECT ONLY, TO THE MILITARY SERVICE INVENTORY CONTROL POINTS (ICPS) HAVING PRIMARY INVENTORY CONTROL ACTIVITY (PICA) LEVEL OF AUTHORITY 06, 22, 23 OR 26. THE IMC CARD IDENTIFICATION CODE IDENTIFIES THE REASON THIS RECORD WAS GENERATED.

INSTRUCTIONS - 1.TO ELIMINATE MULTIPLE ENTRIES OF CONTROL DATA ELEMENTS IN THE FIXED DIC FORMAT BELOW, THESE ELEMENTS ARE SHOWN IN THE FIRST CARD IMAGE ONLY. CONTROL DATA ELEMENTS AS SHOWN, ARE REQUIRED IN POSITIONS 1-39 OF ALL SEGMENT CARD IMAGES IN THE TRANSACTION PACKAGE. THE PSN (DRN 1070) IN CC 4-6 MUST BE INCREMENTED BY ONE (1) IN EACH CARD. IN EACH ADDITIONAL CARD, CC 41-42 WILL BE BLANK AND THE REST OF THE CARD (CC 40, 43-79) WILL BE IN THE SAME SEQUENCE AS LISTED FOR CARD 1.2.DETERMINE THE APPLICABLE ITEM MANAGEMENT CODE FOR THE NSN AND SUBMIT THE APPROPRIATE IMC INFORMATION TO DLA LOGISTICS INFORMATION SERVICE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3Y00

**8.2-********231**

## DOCUMENT IDENTIFIER CODE - KWA

TITLE - ELECTRONIC DATA TRANSMISSION MESSAGE CONTROL

DEFINITION - AN OUTPUT MESSAGE USED TO FURNISH ELECTRONIC DATA TRANSMISSION RECEIVERS THE STATION SERIAL NUMBERS AND TOTAL NUMBER OF ELECTRONIC MESSAGES GENERATED BY FLIS FOR A SPECIFIED DATE.

INSTRUCTIONS - FOUR (4) HOURS SUBSEQUENT TO RECEIPT, PARTICIPATING ACTIVITIES MAY MATCH TRANSMITTED KWA TRANSACTIONS AGAINST THEIR SUSPENSE FILE OF MESSAGES PREVIOUSLY RECEIVED. PARTICIPATING ACTIVITIES WILL NOTIFY THEIR COMMUNICATIONS CENTERS OF MESSAGES NOT RECEIVED. IN THE EVENT THE COMMUNICATIONS CENTER IS UNABLE TO LOCATE THE MESSAGE(S) NOT RECEIVED, FIRST CONTACT COMMUNICATIONS DIVISION, DLA LOGISTICS INFORMATION SERVICE, AND THEN IF THE PROBLEM IS NOT RESOLVED, NOTIFY DLA LOGISTICS INFORMATION SERVICE BY TELEPHONE.

MEDIA/FORMAT - FIXED LENGTH FUNCTIONAL DESCRIPTION SECTION -

D3Y00

# CHAPTER 3 SEGMENT FORMATS

## FLIS INPUT HEADER (9094)

Necessary basic control information has been combined with individual segment data into a consolidated record wherever possible in order to reduce the keypunch workload for those activities which are unable to computer- generate FLIS submission. Thus, separate header records are not required when submitting fixed formats, except when submitting DIC LMD. In those transactions which do require an input header which is an entity in itself, the header record must precede all other segments which are included in the package.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

 1/ This field is interchangeable and can contain either data element listed. Field will contain DRN 0177 or 1120 for provisioning and other preprocurement screening transactions, DICs LSR and LSF.

**8.3-1**

 2/ Field will be blank unless DRN 1515 is applicable in accordance with quality assurance/files compatibility/ item identification data comparison transactions.

 3/ This field is interchangeable and can contain any one of the data elements listed. If the data element is not applicable in accordance with the DIC, the field will be blank.

**8.3-********70**

## FLIS OUTPUT HEADER (DRN 9098)

Output header data is a mandatory requirement for inclusion with all transaction packages transmitted from the FLIS. The FLIS output header will be the first record of each primary output DIC of the output transaction package.

 1/ Card columns 8-9 will contain DRN 0177 and card columns 10-26 will contain DRN 1120 for provisioning and other preprocurement screening transactions. DRN 1120 will always begin in card column 10; any unused positions in the field provided for DRN 1120 will be left blank. On all other transactions, DRNs 4210, 3720, 2310, 1000, and 1515 will be shown in card columns 8-26. If DRN 1515 is not included, card columns 24-26 will be blank.

 2/ A NIIN, Master NSN, Generic Master NSN, Related NSN, or SCN will be entered in these card columns unless none is applicable in accordance with the DIC.

 3/ Field will contain either DRN 3880 or 3890, when 3880 is present, it will be entered in card columns 46-47, and balance of field will be blank.

 4/ This data element applies only to output to the International Codification Division, DLA Logistics Information Service (activity code 9Z). Other submitting activities should disregard this data element.

* Applicable to Provisioning Screening.

## SEGMENT 1 NOTIFICATION OF FLIS CHANGE DATA (DRN 9121)

This segment is created by the DLA Logistics Information Service as output only to notify the activity that the submitted Commercial and Government Entity Code/NATO Commercial and Government Entity (CAGE/NCAGE), Deletion Reason Code or Item Standardization Code has been changed.

1/ Card columns 8-9 will contain DRN 0177 and card columns 10-26 will contain DRN 1120 for provisioning and other preprocurement screening transactions. DRN 1120 will always begin in card column 10; unused positions in the field provided for DRN 1120 will be left blank. For all other transactions, card columns 8-23 will contain DRN 4210, 3720, 2310, and 1000, and card columns 24-26 will be left blank.

2/ This segment will contain two records for each change: First record (type S) for the submitted value and the second record (type R) for the change value. Value for DRN 9979 is used with type S reply for DRN 0238.

Value for DRN 9977 is used with type R reply for DRN 0238.

3/ Card columns 52-56 are limited to the values for four data elements - DRNs 9250, 4140, 4540, and 2650. When this field contains a submitted value for DRN 4540 or 2650, it will be entered in card column 52, and card columns 53-56 will be blank.

4/ When card columns 64-68 contains a changed value for DRN 4540 or 2560, it will be entered in card column 64, and card columns 65-68 will be blank.

5/ Segment 1 is used in FLIS as output notification only, to reflect a data element as it was submitted and the data element as it was changed mechanically by DLA Logistics Information Service, utilizing a segment 1 format for each changed element. This segment 1 will be within an output DIC sent only to the originator/submitter, except KSR. The following data elements submitted under the cited input conditions are subject to FLIS change:

### Data Element	When Subject to Change

Commercial and Government Entity Code (DRN 9250)/NATO Commercial and Government Entity Code (DRN 4140)

Only on submittals which reflect a code which has been cancelled and replaced.

Deletion Reason Code (DRN 4540)	Only on cancellations or Delete Major

Organizational Entity (MOE) Rule actions when the recorded Item Standardization Code is 3 or E, and the submitted Deletion Reason Code is other than 3.

Item Standardization Code (DRN 2650)	Only on requests for new National Stock Number

(NSN) assignment when an E segment is submitted by an unauthorized submitter of standardization and the ISC is changed to 0 or 5.

 6/ The purpose for changing these data elements is (1) to permit further FLIS processing of a submittal which contained such data and (2) to provide notification to the appropriate activity of such change (e.g., file update, etc.). Segment 1 may apply to approvals, returns, match conditions, and screening results as applicable. The change feature to allow further FLIS processing of the item will not, however, exempt the submittal from any further edits which may cause an error condition and subsequent package disapproval.

 7/ In instances where submittals are entered on a FLIS suspense after a segment 1 change has occurred, the suspense will reflect these changes. Any subsequent Service/Agency correction submittals (e.g., LRN) must reflect the corrected data as applicable.

* Applicable to Provisioning Screening.

## SEGMENT 2 SCREENING REQUEST, REFERENCE NUMBER DATA (DRN 9125)

This segment is used as input to FLIS for submission of requests for provisioning and other preprocurement screening in those instances when no National Stock Number (NSN) is available.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

1st Card

2nd Card

 1/ Submittals by U.S. Services/Agencies will contain DRN 0177 in card columns 8-9 and DRN 1120 in card columns 10-26. DRN 1120 will always start in card column 10; any unused positions in the field provided for DRN 1120 may be left blank. Submittals by North Atlantic Treaty Organization (NATO)/foreign countries will contain DRNs 4210, 3720, 2310 and 1000, and card columns 24-26 will be blank.

 2/ DRN 3880 (left justified - blank filled) is applicable only with a submittal by NATO.

 3/ This data element is not applicable to DIC LSA or DIC LSB.

 4/ This data element is applicable only to DIC LSA and DIC LSB.

 5/ Enter DRN 9250 or 4140 in this field.

 6/ DRN 3570 will always begin in card column 48; any unused positions in the field provided for DRN 3570 will be left blank.

 7/ This field applicable to DIC LSB.

 8/ Enter DRN 4080 or 5020 in this field. This field is applicable only with a submittal by NATO for U.S. codification or by U.S. for NATO codification. When DRN 5020 is entered in a segment 2 record, it will begin in card column 44. Any unused positions in the field provided for DRN 5020 will be left blank.

 9/ This data element is applicable to DIC LSA.

## SEGMENT 3 SCREENING REQUEST, NIIN DATA (DRN 9124)

This segment is used as input only for provisioning and other preprocurement screening by NIIN.

## SEGMENT 4 DLA TRANSACTION SERVICES SCREENING, REFERENCE NUMBER DATA (DRN 9126)

This segment is designed specifically for DLA Transaction Services screening by reference number (DIC LSD) against the FLIS and DLA Logistics Information Service response (DIC KSD) showing results of screening.

This segment will be used as input to and output from FLIS in a tailored format.

1/ This field is interchangeable and will contain either of the data elements listed.

## SEGMENT 5 DLA TRANSACTION SERVICES CRITICAL SOURCE OF SUPPLY UPDATE (DRN 0139)

This segment is used as input to the DLA Logistics Information Service to effect an immediate source of supply update to be utilized by the DLA Transaction Services. This segment will be utilized by the Service/Agency and DLA Logistics information Service program manager.

## SEGMENT 6 DLA TRANSACTION SERVICES SOURCE OF SUPPLY UPDATE (DRN 0153)

This segment is generated by the DLA Logistics Information Service as output to the DLA Transaction Services for notification of a source of supply update to be utilized in the routing of Military Standard Requisitioning and Issue Procedures (MILSTRIP) requisitions.

## SEGMENT 7 ITEM MANAGEMENT CODING ADVICE NOTIFICATION (DRN 0154)

This segment is used as output from FLIS to Service inventory control points (ICPs), by special project only, to indicate that Item Management Coding must be performed in accordance with the Card Identification Code contained in the notification. In those instances where more than three Major Organizational Entity (MOE) Rule numbers are involved, a continuation card(s) will be required. In each second/succeeding card, cc 41-42 will be blank and the rest of the continuation card will be in the same format at the first card.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

80	Continuation Indicator Code	8555

## SEGMENT 9 ITEM MANAGEMENT CODING DATA (DRN 0732)

This segment is used as input to and output from the DLA Logistics Information Service. It consists of the elements of data necessary to perform Item Management Coding (IMC) and to allow the Integrated Materiel Manager (IMM) to manage the item of supply. This segment will be used by a Military Service wishing to Item Management Code an item for IMM management, or by a IMM to obtain FLIS file data for the IMC process. A continuation card is required for all submittals, with the exception of change coding not involving estimated demand and Demand Indicator Code.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

1st Card

2nd Card

## SEGMENT A IDENTIFICATION DATA (DRN 9100)

This segment, used as input to and output from the DLA Logistics Information Service consists of those elements of data common to the identification of an item.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

1st Card

2nd Card

 1/ Card columns 8-9 will contain DRN 0177 and card columns 10-26 will contain DRN 1120 for provisioning and other preprocurement screening transactions. DRN 1120 will always start in card column 10; any unused positions in the field provided for DRN 1120 may be left blank. For all other transactions, DRNs 4210, 3720, 2310, 1000, and 1515 will be shown in card columns 8-26 in accordance with the DIC. Should DRN 1515 not be included, card columns 24-26 will be left blank.

 2/ This data element will start in card column 52 but the end of the field cannot be predicted because of the variable length of this type of data. Unused positions in this field will be left blank.

 3/ This data element applies only to input by the International Codification Division, DLA Logistics Information Services (activity code 9Z). Other submitting activities should disregard this data element.

## SEGMENT B MOE RULE DATA (DRN 9101)

This segment, used as input to and output from DLA Logistics Information Service, consists of the elements of data necessary to portray an Individual Service/Agency management profile in relation to a specific item identification. The data elements that comprise this segment and contained on a single card, except when more than three collaborators/receivers are applicable, in which case a continuation card is required.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

1st Card

2nd Card

NOTES

 1/ This field is interchangeable and can contain either data element listed. Field will contain DRN 0177 or 1120 for provisioning and other preprocurement screening transactions DICs LSR and LSF.

 2/ Field will be blank unless DRN 1515 is applicable in accordance with quality assurance/files compatibility/item identification data comparison transactions.

 3/ This field is interchangeable and can contain any one of the data elements listed. If the data element is not applicable in accordance with the DIC, the field will be blank.

 4/ Present only on input transactions.

 5/ This data element applies only to input by the International Codification Division, DLA Logistics Information Service (activity code 9Z). Other submitting activities should disregard this element.

 6/ All A, F, M or N MOE Rules with a PICA/SICA LOA 22/80 must have DRN 0903.

## SEGMENT C REFERENCE NUMBER DATA (DRN 9102)

This segment is used as input to and output from DLA Logistics Information Service. It consists of the elements of data required in the structuring of a logistics reference number, including the related item-of-supply concept codes. The elements of data that normally comprise this segment are contained on a single card. In those instances where the reference numbers exceeds 16 positions, a continuation card will be required.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

1st Card

2nd Card

76-79

80

Blank

Continuation Indicator Code

8555

NOTES:

 1/ Card columns 8-9 will contain DRN 0177 and card columns 10-26 will contain DRN 1120 for provisioning and other preprocurement screening transactions. DRN 1120 will always begin in card column 10; any unused

positions in the field reserved for DRN 1120 may be left blank. For all other transactions, DRNs 4210, 3720, 2310, 1000, and 1515 will be shown in card columns 8-26. If DRN 1515 is not included, card columns 24-26 will be blank.

 2/ Either DRN 9250 or DRN 4140 will be entered in this field.

 3/ DRN 3570 will always begin in card column 60; any unused positions in the field provided for DRN 3570 may be left blank.

 4/ If DRN 3570 exceeds 16 positions, it will be continued on card 2 beginning in card column 60. Any unused positions in the field provided for DRN 3570 may be left blank.

 5/ Except for activity code 9Z, DRN 0780 will never apply to the Services/Agencies.

## SEGMENT D FLIS DATA MESSAGE CONTROL SEGMENT (DRN 0752)

This unique FLIS segment contains the data elements necessary to generate an output message used to furnish Electronic Data Transmission receivers the Electronic Data Transmission Station Serial Numbers and total number of Electronic Data Transmission messages generated by FLIS for a specified date.

NOTES: 1/ Electronic Data Transmission Station Serial Numbers will be included when applicable and may be repeated as required.

## SEGMENT E STANDARDIZATION DECISION DATA (DRN 9104)

This segment, used as input to and output from DLA Logistics Information Service, consists of the elements of data necessary to portray the relationship of NIINs involved in a standardization decision. The elements of data comprising this segment are contained on a single card; however, when three or more NSNs are involved in a standardization relationship, sufficient additional segment E cards will be required to accommodate all pertinent NSNs.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

75-80	Blank

NOTES:

 1/ Card columns 8-9 will contain DRN 0177 and card columns 10-26 will contain DRN 1120 for provisioning and other preprocurement screening transactions. DRN 1120 will always begin in card column 10; unused positions in the field provided for DRN 1120 may be left blank. For all other transactions, card columns 8-26 will contain DRNs 4210, 3720, 2310, 1000, and 1515 in accordance with the DIC. Should DRN 1515 not be included, card columns 24-26 will be left blank.

 2/ This field is interchangeable and will contain any one of the data elements listed.

 3/ This field is interchangeable and either DRN 2650 or 8525 must appear in this field. Applies to the NSN reflected in card columns 27-39.

 4/ Data applies to NSN reflected in card columns 27-39.

 5/ This field is interchangeable and may contain the data elements listed. If the data elements are not applicable, the field will be blank.

 6/ This field is interchangeable and either DRN 2650 or 8525 will appear in this field if an NSN appears in card columns 50-62.

 7/ Data applies to NSN in card columns 50-62. Will be blank if card columns 50-62 are blank.

## SEGMENT F FLIS I&S RELATIONSHIP DATA (DRN 9106)

This segment is used as output from the DLA Logistics Information Service It consists of the elements of data necessary to portray the family group of NSNs involved in the Interchangeability and Substitutability (I&S) decision of a Service/Agency. The elements of data that comprise this segment may require three cards for each Related NSN per Service/Agency. However, when there is more than one Related NSN involved in an I&S family, multiple cards will be output.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

1st Card

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

2nd Card

## SEGMENT G FREIGHT CLASSIFICATION DATA (DRN 9107)

This segment, used as input to and output from DLA Logistics Information Service, contains freight classification information. For some DICs this segment will consist of a minimum of one card, but two cards may be necessary in order to accommodate all data elements required for specific DICs. The use of a Continuation Indicator (DRN 8555) in card column 80 will be governed by the requirements of the specific DIC involved. The data element positions indicating filled and/or blank relate to the Master Freight Table segment G data records only.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

1st Card

2nd Card

 1/ The Integrity Code will only be input by SDDC. It will be provided on all Freight Outputs, when available.

 2/ This code is used on all known hazardous items only.

 3/ The classification tariffs do not always provide a than-car rating for all entries.

 4/ This code is used only when there is a variation between the rail and motor freight classification tariffs.

## SEGMENT H CATALOG MANAGEMENT DATA (DRN 9108)

This segment is used as input to and output from the DLA Logistics Information Service. It consists of the elements of management data that are associated with the CMD cards (input codes LAM, LBM, LCM, and LDM). For some Document Identifier Codes (DICs) this segment will consist of a minimum of one card, but additional cards may be necessary to accommodate all data elements required for specific DICs. In those instances where one or more Technical Document Numbers or Related National Stock Numbers apply, continuation cards will be required.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

1st Card

2nd Card

 1/ Blank on input. Output will contain either File Maintenance Sequence Number or blanks in the first two positions with the Type of Special Processing Indicator Code in the third position.

 2/ Either the Major Organization Entity Code or the Maintenance Action Code will be shown. (See standard note AT, chapter 8.4.)

 3/ Either the Source or Supply or the Source of Supply Modifier will be present.

 4/ If present, will reflect Recoverability Code, Army; Material Control Code, Navy; Expendability, Recoverability, Reparability Category Code, Air Force; Recoverability Code, Marine Corps; Reparability Code, Coast Guard; or Reparable Characteristics Indicator Code, DLA (Defense Logistics Agency).

 5/ Field will contain management control data for the Army, Air Force, Marine Corps, Navy or Coast Guard, as applicable, or blank.

 6/ Output only. Will be blank on input.

 7/ May not be input. Output only for a Unit of Issue change.

 8/ Either the Technical Document Number, Quantitative Expression, Related NSN, Master NSN, or Generic Master NSN will be reflected as dictated by Phrase Code-MDL. When the Technical Document Number is entered/applied, cc 43-62 may be utilized/filled.

 9/ Mandatory for Marine Corps when Phrase Code Q is present.

 10/ Either the Assigned NSN, Master NSN, Generic Master NSN, or Related NSN will be reflected.

Mandatory for valid I&S submitter (See Volume 6, Chapter 6 ) when Phrase Code-MDL blank, G, 7, or S is present. Otherwise blank except when positions are used for Technical Document Number.

 12/ Optional .

 13/ Phrase Code-MDL (DRN 2862) cc 41 will be blank for the first entry only for the Master NSN. Succeeding H segments must contain DRN 2862.

## SEGMENT J SCREENING RESPONSE HEADER (DRN 9122)

This segment is generated by the DLA Logistics Information Service as output only. It is included in the output package(s) resulting from reference number screening requests to indicate the specific reference number that caused a match or no-match condition. Card 2 of a segment J record will be output only to North Atlantic Treaty Organization (NATO)/foreign governments.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

1st Card

2nd Card

 1/ Output for LSR input will contain DRN 0177 in card columns 8-9 and DRN 1120 in card columns 10-26. Output to NATO/foreign governments will contain DRNs 4210, 3720, 2310, and 1000 in card columns 8-23, and card columns 24-26 will be blank.

 2/ DRNs 2910 and 4780 will be shown only if included in the input transaction.

 3/ Either DRN 9250 or DRN 4140 will be shown in this field.

 4/ DRN 3570 will always begin in card column 48 of card 1; any unused positions remaining in the field provided for DRN 3750 will be left blank.

 5/ DRN 0167 will be shown only when included in input DIC LSB.

 6/ Either DRN 4080 or DRN 5020 is mandatory for output when included in input DIC. Any unused positions in the field provided for DRN 5020 may be left blank.

 7/ DRN 3990 will be shown only when included in input DIC LSA or DIC LSB.

 8/ DRN 2694 will be output to DLA Logistics Information Service only.

## SEGMENT K NIIN STATUS/CANCELLATION DATA (DRN 9109)

This segment is generated by DLA Logistics Information Service as output and will be used by the recipient as a cancellation index record in some instances, and merely to show the status of a NSN in other instances. This segment will also be used in input for files compatibility transactions.

 1/ Card columns 8-9 will contain DRN 0177 and card columns 10-26 will contain DRN 1120 for provisioning and other preprocurement screening transactions. DRN 1120 will always start in card column 10; any unused

positions in the field provided for DRN 1120 will be left blank. For all other transactions, card columns 8-26 will contain DRNs 4210, 3720, 2310, 1000, and 1515 in accordance with the DIC. Should DRN 1515 not be included, card columns 24-26 will be blank.

 2/ Pertains to the NSN in card columns 27-39.

 3/ DRN 8875 will be shown in this field (see applicable DIC).

## SEGMENT L OUTPUT FILE DATA HEADER(DRN 9110)

This segment is created by the DLA Logistics Information Service, as output only, when file data is included in the output package or when a search request matches a stock number assigned by a North Atlantic Treaty Organization (NATO) country other than the U.S. Except for output DIC KMN, segment L serves as an intermediate header in the output package and identifies the specific NSN for which file data is being furnished. DIC KMN provides only segment L, featuring a stock number assigned by a NATO country other than the U.S. This data is contained on a single card.

NOTES:

 1/ Card columns 8-9 will contain DRN 0177 and card columns 10-26 will contain DRN 1120 for provisioning and other preprocurement screening transactions. DRN 1120 will always start in card column 10; any unused positions in the field provided for DRN 1120 may be left blank. For all other transactions, card columns 8-26 will contain DRN 4210, 3720, 2310, 1000, and 1515 in accordance with the DIC. When DRN 1515 is not included, card columns 24-26 will be left blank.

 2/ Field will contain 3960, 4120, 8875, 9525, 0797 or 0796 as applicable.

## SEGMENT M CLEAR TEXT CHARACTERISTICS (DRN 9111)

This segment is generated by the DLA Logistics Information Service, as output only, to furnish decoded characteristics data. In addition to the clear text data, the applicable Master Requirement Code is included. The format for this data will satisfy the item identification requirement. Record are not the most efficient manner to convey this type of information; however, if records are used, multiple occurrences will be required.

Positions 41-44 of each segment M record will contain either an MRC (DRN 3445) or be left blank. Continuation of a Requirement Statement (DRN 3614) and/or MRC Clear Text Reply (DRN 0113) will always commence in position 46. Portions of the record may be left blank if not required to complete the clear text reply for an MRC. (See attached segment M concepts for detailed explanation.)

 1/ When Standard Requirement 1 Specification/Standard Control Data (SR-1) and/or Standard Requirement 5 the Manufacturers Data (DR-5) are transmitted to a segment M record, the characters “SR-1” or “SR-5” will appear in the field designated for the MRC (position 41-44). SR-1/SR-5 data elements (e.g., the manufacturer's data, nondefinitive Government spec/std reference) will appear in the field designated for the requirement statement. The values for these data elements will be reflected in the field designated for the MRC value/reply.

 2/ Data element will start in this position but the final position cannot be predetermined because of the variable length of this type of data.

 3/ This data element is required, however, and it will appear in the position immediately following the preceding variable length data element.

 4/ The position reflected for this entry are representative only. Actual entries will commence in card positions in which they can be accommodated, immediately following the preceding data element. In the event the entry for this element cannot be accommodated on the first record on which it appears, it will be continued on a succeeding record beginning in position 46.

SEGMENT M CONCEPTS

1. Segment M is used to transmit clear text descriptive characteristics for use in printing a visual display as required by the user. A standard segment M includes the MRC (Primary Address Code (PAC)), requirement statement, and MRC reply data. In fixed format usage, these data elements will be repeated to the extent necessary to complete a segment M record as outlined below, and will require the generation of multiple records.

2. Immediately following these concepts is a Sample Segment M format Characteristics Data chart. The chart is divided into two parts. The upper position, Segment Data Portion of Segment M, illustrates segment M data as it would appear in the form of 13 records containing characteristics data pertinent to an item identification. This chart illustrates all the conventions that apply to segment M usages as outlined below.

3. There are three data elements provided for use in controlling the printing of a visual display from a segment M record.

a. The Print Control Code (DRN 0234) will appear in position 45 of every card in a segment M record. It has three numeric values - 1, 2, and 3. Code 1 can be used to instruct a print program to begin printing what appears in position 46 at the left margin of the area reserved for the requirement statement (the margin labeled (1) in the representation). Use of code 2 can readily instruct a program to begin printing what appears in position 46 at the left margin of the area reserved for the reply data. Code 3 is an instruction to continue printing information that could not be completed on the previous line of the segment M data format. The overflow information will be displayed beginning in position 46 of the next line in the segment M data format. 5/

b. The Control Character Code (DRN 8255) is a special character that is always entered by DLA Logistics Information Service immediately following the requirement statement. It signals the end of the requirement statement and can serve to instruct a print program to begin printing what appears in the next position at the left margin of the area reserved for reply data. 1/

c. The Data Element Terminator Code will always appear in FLIS output immediately following the reply data and it signals the end of an individual segment M data group (MRC, requirement statement, control character, and reply data). 2/

4. Record 1 on the attached segment M chart illustrates the completion of a segment M data group on one record. The MRC (NAME) is entered in position 41-44; the Print Control Code (with value of 1) is entered in position 45; and the requirement statement commences in position 46. The Control Character Code (the commercial “at” (\@) sign) appears immediately following the requirement statement. The reply data begins in the position next following the Control Character Code and it is ended by the Data Element Terminator Code (#). Because there are additional records in this segment M record, the Continuation Indicator Code (-) is entered in position 80.

5. Records 2 and 3 illustrate the overflow of a requirement statement to a continuation record. The MRC (CPLM) is entered in position 41-44; the Print Control Code with a value of 1 appears in position 45; and the requirement statement begins in position 46. The requirement statement cannot be completed on record 2; therefore a Continuation Indicator Code is entered in position 80.

a. Record 3 is blank in the MRC field and contains a Print Control Code with a value of 3 in position 45. The overflow requirement statement begins in position 46 and is followed by the Control Character Code, the reply data, and the Data Element Terminator Code. The remainder of the record through position 79 is blank. Because more records are required to complete the segment M record, the Continuation Indicator Code (-) appears in position 80.

b. If the requirement statement should end in position 79, position 80 will contain the Continuation Indicator Code. The next record will be blank in the MRC field, a Print Control Code of 3 will be entered in position 45, and the control character will appear in position 46, followed by the reply data.

6. Records 4, 5, and 6 illustrate the overflow of reply data. Record 4 contains the MRC (CPXC) in position 41- 44, and a print Control Code with a value of 1 is entered in position 45. As the reply data cannot be fully accommodated on record 4, the Continuation Indicator Code is entered in position 80.

a. Record 5 is blank in the MRC field, and a Print Control Code with a value of 3 is entered in position 45. The overflow reply data begins in position 46. As the overflow cannot be accommodated on record 5, a Continuation Indicator Code appears in position 80.

b. Record 6 is blank in the MRC field, and a value of 3 is entered in the Print Control Code field; the overflow reply data begins in position 46 and is ended by the Data Element Terminator Code. The remainder of the record through position 79 is blank and, as additional records are required to complete the segment M record, A Continuation Indicator Code is entered in position 80.

7. Records 4-8 illustrate the use of secondary address coding to accommodate multiple replies to a single requirement statement. Records 4-6 contain the first reply.

a. In record 7, which contains the second reply, the MRC field is blank; a Print Control Code of 2 is entered in position 45, and the second reply begins in position 46. Because the second reply cannot be entirely accommodated on record 7, the Continuation Indicator Code is entered in card column 80.

b. Record 8 is blank in the MRC field; it contains a Print Control Code with a value of 3 in position 45, and the overflow reply data begins in position 46. The Data Element Terminator Code follows the reply data, and the remaining unused positions are left blank. As there are additional records in the segment M record, a Continuation Indicator Code appears in position 80.

c. Second/succeeding replies to a single requirement statement portrayed with the AND/OR symbology will be handled in the same way as secondary address coding

8. Records 9-13 show the portrayal of SR-1 data. In record 9, the characters “SR-1” are entered in the MRC field; the Print Control Code with a value of 1 is entered in position 45, and the phrase SPEC/STD CONTROLLING DATA is entered beginning in position 46. This phrase is immediately followed by the Data Element Terminator Code. The remaining unused positions on the record are left blank, and the Continuation Indicator Code is entered in position 80.

a. The next record (record 10) is blank in the MCR field; it contains a Print Control Code with a value of 1 in position 45, and the phrase COMMERCIAL AND GOVERNMENT ENTITY CODE is entered beginning in position 46. It is immediately followed by the Control Character Code. The value for the manufacturers code (81349) is entered following the Control Character Code and is ended by the Data Element Terminator Code. The remainder of the card is left blank, and the required Continuation Indicator Code is entered in position 80.

b. The next record (record 11) is blank in the MRC field; a Print Control Code of 1 is entered in position 45, and the phrase NON-DEFINITIVE GOVERNMENT SPEC/STND REFERENCE is entered beginning in position

46. 3/ As that phrase cannot be entirely accommodated on this record, the Continuation Indicator Code is entered in position 80.

c. The next record (record 12) is blank in the MRC field; a Print Control Code with a value of 3 is entered in position 45; the remainder of the phrase is entered beginning in position 46; and the Control Character Code immediately follows the end of the phrase. The reference number follows immediately and is ended by the Data Element Terminator Code.

(1) A fixed field of 32 positions has been allocated for SR-1 reference number information. When a reference number requires less than the allocated 32 positions, the remainder of the field will be blank filled.

(2) As the 32-position reference number cannot be entirely accommodated on record 12, the Continuation Indicator Code is entered in position 80.

d. The Data Element Terminator Code will appear in the 33rd position, which equates to position 54 of record

13. As record 13 is the last card in this sample M record, position 80 is left blank. 4/

9. SR-5 data will be handled in the same way as SR-1 data. The characters “SR-5” will be recorded in the MRC field as shown on record 9; a Print Control Code with a value of 1 will be entered in position 45, and the phrase THE MANUFACTURERS DATA will appear beginning in position 46, immediately followed by a Data

Element Terminator Code. The remainder of the record will be blank through position 79, with a Continuation Indicator in position 80.

a. The MRC field (positions 41-44) of the next record (as in record 10) will be blank; the Print Control Code field (position 45) will contain the value of 1; MANUFACTURERS CODE will be shown as the requirement statement, and the applicable Commercial and Government Entity Code (CAGE) will be given as the reply data.

b. As applies to the SR-1 data example in record 11, the next record will also be blank in the MRC field (positions 41-44); the Print Control Code (with a value of 1) will be entered in position 45; and DESIGN CONTROL REFERENCE (as applicable to Reference Number Category Code (RNCC) 3) will be reflected as the requirement statement. The actual reference number will be entered as the reply data.

10. The clear text characteristics data of the M segments will be in the following sequence:

Item Identification Guide Section I Data IIG Section III Data (including MRC ZZZV) Standard PACs (MRCs FEAT, ZZZS, ZZZT, ZZZW, ZZZY, ELRN, ELCD, and CRTL as applicable Administrative PAC (MRC 9001) SR-1 Data SR-5 Data

11. The using Services/Agencies are responsible for developing and maintaining programs for printing the clear text characteristics description in the visible display they desire. The entire content of the visible display can be extracted from the output package as follows:

### Data	Segment

National Stock Number	Output Header or Segment L (Matched Items) Document Control Number		Output Header

Input Document Identifier Code	Output Header

Type of Item Identification Code	Segment A Criticality Code	Segment A

Guide Number, IIG	Segment A

Item Name Code	Segment A

Clear Text Characteristics	Segment M

NOTES:

 1/ If a requirement statement ends in position 79, the Continuation Indicator Code will be entered in position

80. The next record will be blank in the MRC field, a Print Control Code with a value of 3 will appear in position 45, and the Control Character Code will be entered in position 46. Should a requirement statement end in position 78, the Control Character Code will be entered in position 79, and the Continuation Indicator will appear in position 80. The next record will be blank in the MRC field; a Print Control Code with a value of 2 will be entered in position 45, and the reply data will commence in position 46.

 2/ There is one exception to this rule. The Data Element Terminator Code always immediately follows the phrases SPEC/STD CONTROLLING DATA and THE MANUFACTURER'S DATA when SR-1 and/or SR-5

data are entered in a segment M record.

 3/ The phrases MFR SOURCE CONTROLLING REFERENCE or DEFINITIVE GOVERNMENT SPEC/STD

REFERENCE may be entered as SR-1 data in lieu of NON-DEFINITIVE GOVERNMENT SPEC/STANDARD REFERENCE.

For complete details on the use of the Continuation Indicator Code, refer to volume 10 , section 10.2.5 and volume 2 , section 2.3.2 .

 5/ A fixed field of 32 positions has been allocated for SR-1 reference number information. When a reference number requires less than the allocated 32 positions, the remainder of the field will be blank filled.

SAMPLE SEGMENT M/DD 146 FORMAT CHARACTERISTICS DATA SEGMENT DATA PORTION OF SEGMENT M

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . DATA AS PRINTED IN DD 146 FORMAT

### MRC	REQUIREMENT STATEMENT	REPLY DATA

**MRC	REQUIREMENT STATEMENT	REPLY DATA**

(1)	(2)

NAME	ITEM NAME	CIRCUIT

BREAKER

CPLM	MAXIMUM CONTINUOUS LOAD CURRENT RATING PER POLE

12.5

AMPERES AC

CPXC	TRIPPING TIME IN SECONDS	0.055

MINIMUM AT 200 PCT RATED CONTINUOU S CURRENT 0.950 MAXIMUM AT 200 PCT RATED CONTINUOU S CURRENT

SR-1	SPEC/STD CONTROLLING DATA MANUFACTURERS CODE

NON-DEFINITIVE GOVERNMENT SPEC/STND REFERENCE

81349

MILC39019-5

## SEGMENT P DATA ELEMENT ORIENTED WITHOUT VALUE (DRN 9113)

This segment is generated by DLA Logistics Information Service, as output only, to return errors, conflicts and possible duplicates revealed during processing. The data element(s) involved are identified by the applicable DRN/MRC and return code to indicate specific error conditions. Any number of DRNs/MRCs may be included within this segment to identify pertinent data elements and related return codes in the transaction; however, there is a limit of three (3) occurrences per single card. If more than three errors are involved, continuation card(s) will be generated. The Date, Suspense Purge (DRN 8680) will appear on the first card and all continuation cards (when applicable) in card columns 41-46. The three data groups of SPSN/FMSN, DRN/MRC, and return code will be shown in the same format as on the first card. Any unused positions in the last card will be left blank.

When more than a single card is required to accommodate a submitted DRN value/data group, the SPSN cited in the segment will be the first SPSN in which the DRN value/data group originated (i.e., the second and succeeding PSNs required in the submission of the DRN value/data group will not be referenced in the SPSN field).

 1/ Card columns 8-9 will contain DRN 0177 and card columns 10-26 will contain DRN 1120 for provisioning and other preprocurement screening transactions. DRN 1120 will always start in card column 10; any unused positions in this field provided for DRN 1120 may be left blank. For all other transactions, card columns 8-26 will contain DRNs 4210, 3720, 2300, 1000, and 1515 in accordance with the DIC.

 2/ A NIIN or SCN will be shown in this field unless none is applicable in accordance with the DIC.

 3/ This field will be blank when MRC errors are reflected or when the output DIC was KPE or KRP.

## SEGMENT Q DATA ELEMENT ORIENTED WITH VALUE AND RETURN/ACTION CODE (DRN 9114)

This segment is used as input to and output from the DLA Logistics Information Service. It is generated by FLIS to return errors or conflicts revealed during processing. In addition to the applicable DRNs/MRCs and return codes, the values/replies are included. This segment will also be used as input to FLIS when correcting data which has been suspended by FLIS. Any number of DRNs/MRCs may be included within this segment to identify pertinent data elements and related return/action codes in the transaction package. The number of cards of this type which will be generated for a given package is unpredictable because of the variable length of the values/replies.

When more than a single card is required to accommodate a submitted DRN value/data group, the Submitted PSN cited in the segment will be the first SPSN in which the DRN value/data group originated (i.e., the second and succeeding PSNs required in the submission of the DRN value/data group will not be referenced in the SPSN field).

 1/ Card columns 8-9 will contain DRN 0177 and card columns 10-26 will contain DRN 1120 for provisioning and other preprocurement screening transactions. DRN 1120 will always start in card column 10; unused positions in the field provided for DRN 1120 may be left blank. For all other transactions, card columns 8-26 will contain DRNs 4210, 3720, 2310, 1000, and 1515 in accordance with the DIC. When DRN 1515 is not included, cc 24-26 will be blank.

 2/ A NIIN or SCN will be shown in this field unless none is applicable in accordance with the DIC.

 3/ Either DRN 8328 or DRN 1515 will be entered in this field.

 4/ This blank one-position field will be repeated in each second/succeeding repetition of the data group SPSN/FMSN, DRN/MRC, Return/Action Code, Submitted DRN/MRC Value/Reply, and Data Element Terminator Code.

 5/ Data element will start in this position, but the final position cannot be predetermined because of the variable length of this type of data. In the event this field cannot accommodate the entire data element, the entry will be continued on second (and succeeding) card(s), beginning in card column 47.

 6/ This card column is not precise because of the variability of the preceding data length. The data element is required to be shown, however, and will appear in the card column immediately following the preceding variable length data element. If DRN 9979 ends in cc 79, the Data Element Terminator Code (DRN 8268) will appear on the next succeeding card in card column 47.

 7/ Card columns reflected for these elements are representative only. If a second/succeeding data groups of SPSN/FMSN, DRN/MRC, Return/Action Code, Submitted Value Reply, and Data Element Terminator Code can be entirely accommodated in the remaining unused positions on any given card, it will be started in the

position immediately following the preceding Data Element Terminator Code. If it cannot be so accommodated, it will be started in card column 47 of the succeeding card.

 8/ This data element applies only to input by the International Codification Division, DLA Logistics Information Service (activity code 9Z). Other submitting activities should disregard this data element.

## SEGMENT R DATA ELEMENT ORIENTED WITH VALUE (DRN 9115)

This dual purpose segment is used as input to and output from DLA Logistics Information Service. The value/reply field will apply when this segment is being used as input/output for maintenance action on specific data element(s). The value/reply will not be used when this segment is prepared for input interrogation purposes. This segment may be a single or multiple card(s) depending on the range of data involved.

 1/ For provisioning and other preprocurement screening requests (DICs LSR and LSF), cc 8 and 9 will contain DRN 0177, Activity Code, Screening, and cc 10 through 26 will contain DRN 1120, Submitter Control Number.

 2/ This blank one-position field will be repeated following the Data Record Number (DRN 0950) in each subsequent repetition of the data group composed of DRN, DRN Value, and Data Element Terminator Code.

 3/ Data element will commence in this position, but the actual ending card column cannot be predetermined because of the variable length of this type of data. In the event this field cannot accommodate the entire data element value, the entry will be continued on second (and succeeding) card(s) beginning in card column 41.

 4/ This card column is representative only, owing to the variable length of the preceding data element. The data element is required to be shown, however, and will appear in the card column immediately following the preceding data element. If DRN 9975 ends in card column 79, cc 80 will contain the Continuation Indicator Code, and the Data Element Terminator Code (DRN 8268) will be entered in cc 41 of the next succeeding card.

 5/ Card columns reflected for these elements are representative only. If a second/succeeding data group of Segment R DRN, DRN Value, and Data Element Terminator can be accommodated in the remaining unused positions on any given card, they will be started in the position immediately following the Data Element Terminator Code. If they cannot be fully accommodated, they will be started in card column 41 of the succeeding card, leaving any unused positions blank, with DRN 8555 in card column 80.

## SEGMENT S RELATED SCREENING DATA (DRN 9116)

This segment is used on input only. It contains the control data elements required when submitting data to be characteristically screened in the master file.

## SEGMENT T CANCELLATION/DELETE MOE RULE (DRN 9117)

This segment is used primarily for input. It is used for output only when included with segment Z (Future Data). It is used when a MOE Rule is to be deleted from an existing NSN. It is also used when an NSN is to be cancelled in the FLIS master file, (i.e., cancel-inactive, cancel-use, etc.). When the cancellation/delete MOE Rule transaction is involved with a future effective date, segment T will be input, stored in the future data file, and output only when required with segment Z.

 1/ Card columns 8-9 will contain DRN 0177 and card column 10-26 will contain DRN 1120 for provisioning and other preprocurement screening transaction. DRN 1120 will always begin in card column 10; unused positions in the field provided for DRN 1120 will be left blank. For all other transactions, card columns 8-23 will contain DRNs 4210, 3720, 2310 and 1000, and card columns 24-26 will be blank.

 2/ Replacement NSN Cancellation will be shown in this field

## SEGMENT V CODED ITEM CHARACTERISTICS DATA (DRN 9118)

This segment is on input only when submitting characteristics for maintenance and search actions. This segment may also be received as interrogation output and as maintenance output to NATO/FGs only. Multiple occurrences of cards for this segment will usually be required.

 1/ Position 8-9 will contain DRN 0177 and position 10-26 will contain DRN 1120 for provisioning and other preprocurement screening transactions. DRN 1120 will always begin in position 10; unused positions in the field provided for DRN 1120 will be left blank. For all other transactions, position 8-23 will contain DRNs 4210, 3720, 2310 and 1000, and position 24-26 will be blank, except for NATO/FG data receivers. Output to NATO/FGs may contain a NATO File Maintenance Sequence Number in position 24-26.

 2/ The field showing this data element is representative only. The element will begin in the first column as shown but, owing to the variable length of the element, its end cannot be predicted. In the event the entry cannot be accommodated on the first record it will be continued on a second (or succeeding) record(s) beginning in position 42.

 3/ The position reflected for this data element is representative only, owing to the variable length of the preceding data element. This code is required, however, and it will appear in the position immediately following the data element to which it applies. If DRN 3317 ends in position 79, position 80 will contain the Continuation Indicator Code and DRN 8268 will be entered in position 42 of the next succeeding record.

 4/ This field is representative only. The initial position cannot be predicted owing to the variable length of the preceding characteristics group, nor can the end of the field be predicted as the length of this data is variable. If a second/succeeding Characteristics Data Group can be fully accommodated in the remaining unused positions on any given record, it will begin immediately following the preceding data element (DRN 8268). If a second/succeeding Characteristics Data Group cannot be so accommodated, it will begin on the next succeeding record in position 42, leaving blank unused positions following the first Characteristics Data Group. (DRN 8555 will be entered in position 80.)

 5/ The positions reflected for this data element are representative only, owing to the variable length of the preceding data elements. If the last Characteristics Data Group ends in position 78, DRN 0339 may be accommodated in position 79 of the same record and position 42 in the next record. DRN 0339 may be accommodated in position 42 and 43 only if the last Characteristics Data Group began in position 42 of the preceding record; otherwise, DRN 0339 may be in any position within position 42-79.

## SEGMENT W PACKAGING DATA SEGMENT

This segment, used as input to and output from DLA Logistics Information Service, contains packaging information. It may be repeated up to 3 times per National Stock Number based on the Level of Protection Code.

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

1st Card

2nd Card

3rd Card

4th Card

5th Card

### NOTE	COLUMN	DATA ELEMENT NAME	DRN

80	Continuation Indicator Code (Use Code5)	8555

NOTES:

 1/ Mandatory Entries.

 2/ Blank fields for future expansion.

## SEGMENT Z FUTURE DATA (DRN 9119)

This segment is generated by the DLA Logistics Information Service as output only. It is used to notify authorized data recipients of maintenance type actions which have been received by DLA Logistics Information Service and placed in a suspense status. These actions will be processed into the FLIS data base on the established effective date. This segment will also be included in file data packages resulting from interrogations or screening. Multiple occurrences of records for this segment may be generated.

When these maintenance actions will affect a single data element, the Data Record Number for segment R (DRN 9115) will be entered in position 53-56, and the remainder of the record through position 80 will be blank. The next succeeding record(s) will be in segment R format containing the affected data element and value. When maintenance actions will affect an entire segment, the DRN for that segment will be entered in position 53-56, and the remainder of the record will be blank. The next succeeding record(s) will be in the format of the segment affected. Each data element or segment affected by these maintenance actions will require a separate segment Z record.

This segment will be output in the DIC package in which the affected segment is output. Immediately following segment Z will be the segment represented by the DRN given in segment Z in reply to DRN 0950 (cc 53-56) such as segment B, H, R, or T, which will include the effective dated data elements.

NOTES:

 1/ Activity Code, Screening (DRN 0177) and Submitter Control Number (DRN 1120) apply exclusively to provisioning and preprocurement screening requests from U.S. Services/Agencies and resulting output.

 2/ Represents the originator of the future dated transaction.

 3/ This DRN represents the segment which contains the futures data.

# CHAPTER 4 STANDARDIZED DIC INPUT/OUTPUT NOTES

The following notes provide specific information for the data elements included in the DIC input/output formats and also for the edit/validation criteria contained in volume 11 . All Data Record Numbers (DRNs) are listed and defined in volume 12, chapter 12.4 .

### NOTE	DEFINITION

1 Data element is mandatory.

2 Data element is optional. When the data element is not submitted, the field will be left blank.

3 Data element or segment is repeated as required.

4 Data Record Number or Master Requirement Code as appropriate. If cited Action Code is AA, AC, or AD, field must contain one or the other; except Submitted DRN/MRC Value Reply (DRN 9979 ) field will be blank for MRC deletions actions. For segment actions AS or DS all fields will be blank, except for segment V deletion actions which require submittal of value 9118 in the DRN 0950 field. When adding, changing, or deleting segment H data elements, it is required that DS and AS actions be submitted, as applicable, to replace the entire segment H. Action Codes AS and DS are not applicable to suspended transfer-from- type-2 transactions.

5 FLIS computer-generated.

6 Right justified.

7 Left justified.

10 NIIN or System Control Number (SCN) mandatory. The appropriate data element will be reflected.

11 The applicable Assigned NSN will be reflected.

12 DRN (0950) or MRC (3445) mandatory. The appropriate data element will be reflected.

15 Variable length data element. Format may express minimum length or arbitrary size of field developed for automatic data processing. When 9999 is reflected, it indicates a variable length field of more or less than 9999 characters.

16 Management Control Data, Army (DRN 8930 ); Management Control Data, Air Force (DRN 8925 ); Management Control Data, Marine Corps (DRN 8935 ); Management Control Data, Navy (DRN 8940 ); or Management Control Data, Coast Guard (DRN 0707 ) as appropriate. Left justified; when the data element is not required, the field will be blank. DRNs are data chains consisting of codes with tables in volume 10 as follows:

**8.4-1**

18 Mandatory when supplemental to the Major Organizational Entity (MOE) Rule Number.

19 Item Name Code or Item Name, Non-Approved will be included only if the data element was in the input transaction. This field is used only when NATO activities are submitting to the U.S. for codification of U.S.-manufactured items or when U.S. is submitting to NATO activities for codification of foreign-manufactured items.

20 Pertains to the Assigned NSN reflected in the input/output header or the supplement output file data header (segment L).

21 Master NSN, Generic Master NSN or Replacement NSN mandatory. The appropriate data element will be reflected.

29 This is an optional segment.

30 Applicable Item Name Code from Cataloging Handbook H-6, Federal Item Name Directory, section B, will be reflected. When item name is not approved, field will be left blank.

31 When the Item Name Code (DRN 4080 ) field is blank, the Item Name, Approved/Item

**8.4-********11**

Name, Non-Approved will be reflected in clear text. If less than 19 positions, the remaining positions will be blank.

35 Cancelled NSN mandatory. The appropriate data element will be reflected.

36 The following data elements apply. Submit only the affected or required data element(s) with value. For example, a change in FSC from 5305 to 5306 would require DRN 3990 followed by the value (5306) in the segment R record.

Subnotes:

### DRN	Data Name	Value

**Record Format**

3990 (a,d)	Federal Supply Class	4N

2128 (a)	Date, Effective, Logistics Action	5N

4080 (d)	Item Name Code	5N

5020 (b,d)	Item Name, Non-Approved	19AN

4820 (d)	Type of Item Identification Code	1AN 4765 (c,d)	Reference/Partial Descriptive Method Reason Code	1N

a. Mandatory with this DIC.

b. Submitted when an Item Name Code is not applicable.

c. Submitted when not in file or requires a change.

d. Approved output returned under DIC KCG will contain the data elements which correspond to those submitted under the LCG's segment R record(s).

37 This data element brought forward from input transaction, or when output is the result of a roll- up or overlay of Catalog Management Data, the field will contain the last Document Control Number involved in the roll-up or overlay.

38 Source of Supply Code (DRN 3690 ) or Source of Supply Modifier Code (DRN 2948 ) required. The appropriate data element will be submitted or returned.

39 Data element is mandatory. The reference number which identifies the item of supply will be reflected. If the primary reference number exceeds 32 positions, the Extra Long Reference Number Indicator (a dash, (-)) will be reflected in the 32nd position and the complete reference number in segment V under Master Requirement Code ELRN. (The primary reference number cannot exceed 32 positions for a type 2 item identification.) Additional extra long reference numbers will employ the same technique except the complete reference number will not appear in segment V.

40 Optional field. Quantitative Expression (DRN 8575 ), Related NSN (DRN 2895 ), Master NSN (DRN 0797 ), Generic Master NSN (DRN 0796 ), or Technical Document Number (DRN 2893 ) will be reflected as appropriate. For DRN 2893 the maximum record length is 20 positions and is left justified, blank filled. For all other DRNs listed above, the maximum record length is 13 positions and left justified.

44	Not required for Nuclear Ordnance Cataloging Office (NOCO). Mandatory for all other activities.

46 The Package Sequence Number of the original submittal which contained the error to be corrected will be reflected when other than characteristics data is being added (AA), changed (AC), or deleted (AD). Required for delete segment action (DS) except when segment V (DRN 9118 ) is being deleted. This field will always be blank for all AS actions, segment V deletions, and all Master Requirement Code/Primary Address Code deletions.

47 Not applicable, leave field blank.

48 When adding (AS) a segment(s) to suspended transaction, submit the segment with its related DRNs. Each segment added must reflect a blank field for the Submitted Package Sequence Number (DRN 8328 ). When deleting (DS) a segment(s), the Submitted Package Sequence Number will be submitted, except for segment V deletions which will be left blank. The DRN 0950 field will also be blank except for segment V deletions which will reflect DRN 9118 .

49 The appropriate data element, Reparable Characteristics Indicator Code - DLA (DRN 2934 ); Reparability Code - Coast Guard (DRN 0709 ); Recoverability Code - Army (DRN 2892 ); Material Control Code - Navy (DRN 2832 ); Expendability - Recoverability -Reparability Category Code - AF (DRN 2655 ); or Recoverability Code - Marine Corps (DRN 2891 ) will be forwarded. When no data element is applicable, the field will be left blank.

51	Will contain Destination Code, Screening (DRN 3890 ) applicable to provisioning and other preprocurement screening results only (input DICs LSF and LSR). Destination Activity Code, Output (DRN 3880 ) applicable to all others.

55	Submitted Federal Supply Class (DRN 9075 ) will be forwarded when the submitted FSC differs from the recorded FSC. When not applicable, the field will be left blank.

66 Assigned NSN (DRN 3960 ) not returned when the input transaction DIC is LNC, LNK, LNR, or LNW. However, the Assigned FSC (DRN 3990 ) will be output followed by either the System Control Number (DRN 3735 ) or 9 spaced-filled positions.

67 SCN (DRN 3735 ) will be assigned to suspended input transactions requesting assignment of NIIN.

68 Matched NSN (DRN 4120 ). The appropriate DRN is returned.

70	Item Name, Approved (DRN 5010 ) or Item Name Non-Approved (DRN 5020 ) is mandatory. The appropriate data element will be output.

72 The data element or a blank field will be returned as appropriate for the NSN reflected in the output header or the Output File Data Header (segment L).

73 This optional segment, used as input to and output from FLIS, consists of the elements of data required in the structuring of a logistics reference number, including the related item- of- supply concept codes. May be repeated. Segment not required for descriptive method without reference number item identification.

74 Segment M is not required for a reference method item identification. Standard Requirement 1, Specification/Standard Control Data (SR-1) will be included in the output of segment M when a reference number with Reference Number Category Code 1, 2, 4, or 7 is recorded.

SR-5 Manufacturers Data will be included in the output of segment M when the type of item identification is 1A(K), 1B(L), 4A(M), or 4B(N). Segment M will not be output in DIC KFD when KFD is provided as secondary output to DICs KFS, KKD, KKU, KRE, and KRM.

75 Activity Code, Screening (DRN 0177 ) and Submitter Control Number (DRN 1120 ) apply exclusively to provisioning and preprocurement screening requests from U.S. Services/Agencies and resulting output. The following DRNs will be reflected for other type transactions: Originating Activity Code (DRN 4210 ), Submitting Activity Code (DRN 3720

), Date Transaction (DRN 2310 ), Document Control Serial Number (DRN 1000 ), and either File Maintenance Sequence Number (DRN 1515 ) for U.S. requests or NATO File Maintenance Sequence Number (DRN 1516 ), if available, for NATO/foreign country (FC) requests.

86	The DRNs assigned to identify FLIS input/output headers and segment data chains are included for information and will not be input or output for this DIC. The length portrayed for these DRNs will be as follows:

a. Segments appearing in both fixed and variable DIC formats will show the segment DRN length as the minimum required for the variable format (e.g.; segment A, DRN 9100 - 0012X).

b. Segments appearing only in fixed DIC formats will usually show the segment DRN length as 80 positions or multiples thereof (e.g.; segment 6, DRN 0153 - 0080X).

88 This data element must be in position 80 of a card format when applicable in accordance with conventions outlined in volume 10 , sections 10.2.4 . and 10.2.5 .

89 This data element is not required with this segment for this DIC. The data field will be left blank.

90 This DIC may require use of continuation card(s) to complete this segment. See volume 10 , sections 10.2.4 and 10.2.5 for detailed information concerning circumstances requiring preparation/transmittal of continuation cards.

93 When this card image is used, at least one occurrence of either Authorized Item Identification Data Collaborator Code (DRN 2533 ) or Authorized Item Identification Data Receiver Code (DRN 2534 ) is necessary.

94 Data element mandatory only when the reply to Address Card Sequence Code (DRN 0233 ) is a numeric 1 in the second position of the two- position field. If other than the number 1, the field for this data element will be blank.

95 The card column or position associated with this data element is representative only, since it is preceded by a variable length data element.

96 When the segment is used with this DIC, only the first card is required.

97 This data element will be included if it is available in FLIS file(s) or was contained in the input transaction. When this note is used in conjunction with File Maintenance Sequence Number (DRN 1515 ) or NATO File Maintenance Sequence Number (DRN 1516 ), the FMSN or NFMSN will always be shown. NOTE: The NFMSN is applicable only to NATO and other foreign governments.

98 The data element will be included when applicable.

99 The appropriate DRN will be submitted or returned.

AA	Data element is mandatory. Pertains to the NSN as applicable, contained in the header/segment L which precedes this segment.

AB	This data element is mandatory for this DIC and will be perpetuated from the input transaction.

AC	Pertains to the Replaced NSN, Standardization Relationship (DRN 8977 ) or Replacement NSN, Standardization Relationship (DRN 9525 ) in the segment E record as applicable for variable format or card columns 50-62 for fixed formats.

AD	Computer-generated Originator of Standardization Decision (DRN 9325 ) extracted from Originating Activity Code (DRN 4210 ) field or Submitting Activity Code (DRN 3720 ) field, as applicable, from input transaction.

AE	Computer-generated Date, Standardization Decision (DRN 2300 ) extracted from Date, Transaction (DRN 2310 ) field from input transaction.

AH	Pertains to the Assigned National Stock Number (DRN 3960 ); Replaced NSN, Standardization Relationship (DRN 8977 ) or Replacement NSN, Standardization Relationship (DRN 9525 ) reflected in the input/output header for variable format or in card columns 27-39 for fixed formats.

AK	Data element is mandatory. The assigned NSN (DRN 3960 ); Replacement NSN, Standardization Relationship (DRN 9525 ); Replaced NSN, Standardization Relationship (DRN 8977 ); Master NSN (DRN 0797 ); Generic Master NSN (DRN 0796 ) will be reflected as appropriate.

AM	Data element is optional. Required when applicable NSN is cancelled. When the data element is not applicable, the field will be left blank.

AN	Data element is optional. Required when standardization relationship is applicable. When a standardization relationship is not included, the field will be left blank for fixed format records. For variable length format, the record will be truncated when no data follows.

AT	Major Organizational Entity Code (MOE) (DRN 2833 ) is required for General Services Administration only, when submittal is for GSA-managed items for which GSA is not the Integrated Materiel Manager (IMM) for DoD Services/Agencies. MOE Code is required for Veterans Administration when submittal is for items which the VA is the IMM for Civil Agencies. Maintenance Action Code (DRN 0137 ) is required for IMM, Service, TACOM, or GSA as Lead Service use. Code MM indicates an IMM record only, SS a Service record only, and MS both IMM and Service. When neither DRN is applicable, the field will be blank.

AU	For segment H, will contain either the File Maintenance Sequence Number (DRN 1515 ) with a value of 001, or blanks in the first two positions with the Type of Special Processing Indicator Code (DRN 0568 ) in position 3 (see volume 10, table 125 ).

AV	This field will contain the Date, Effective, Logistics Action (DRN 2128 ) when the segment B data was added or changed for your Service/Agency. Other B segments in this output will be left blank.

AW	Data element not required when (1) an Integrated Materiel Manager/Lead Service is preestablished as the Primary Inventory Control Activity on the recorded MOE Rule or (2) for NATO recordings, foreign countries, and certain exception-type MOE Rules (e.g., Defense Industrial Plant Equipment Center, Defense Nuclear Agency, National Security Agency with PICA Level of Authority 07 or 08).

AZ	Data element is mandatory. The Assigned NSN will be reflected.

BB	Commercial and Government Entity Code or NATO Commercial and Government Entity Code mandatory. If a United States or Canadian manufactured item, the applicable CAGE Code from Cataloging Handbook H4/H8 will be reflected. Must have a Type of

Organizational Entity (O.E.) Code of “A” (manufacturer). If a NATO Foreign country (FC) manufactured item, the applicable CAGE Code from Cataloging Handbook H4/H8, Section C and D will be reflected.

BD	Mandatory when code P is given in reply to the Type of Screening Code (DRN 9505 ) (Reference Number Category Code can be 1, 2, 3, 5, or 7). Otherwise, this field will be left blank.

BE	Input DIC for which the follow-up has been submitted will be reflected. Perpetuate as contained in DIC submittal (applicable DICs LAR, LAU, LCR, LDR, LDU, LFN, LMD, and LSA.)

BJ	Mandatory data field. Must be zero filled when data element to which it applies is absent. BL	Enter the input DIC for which the follow-up is being submitted (applicable DICs LAR, LAU,

LCR, LDU, LFN, LMD, and LSA). If a second follow-up, “LFN” must be reflected.

BN	The entry will be DRN 3921 (Document Identifier Code, Input). BQ	The entry will be DRN 0854 (Transaction Status Code)

BS	Item Name Code (DRN 4080 ) and non-approved item name (DRN 5020 ) are alternate mandatory fields. If multiple reference numbers are submitted in the same document control number package, the item name code or item name, non-approved will be given only in the last segment 2 record.

BU	The first entry will be DRN 0131 (Document Control Number, Follow-Up) followed by the value.

BV	The second entry will be DRN 3921 (Document Identifier Code, Input) followed by the value of the input DIC of the original transaction on which the follow-up was submitted.

BW	The third entry will be DRN 0166 (Follow-Up Status Code) followed by the value.

BX	When applicable, a fourth entry will be DRN 3920 (Document Identifier Code) followed by the value of the output DIC representing the resultant output of the original transaction on which the follow-up was submitted.

BY	Data element is mandatory. Computer generated by submitting activity on input and by FLIS on output. All characters, including the count field, are added together to make up this element.

BZ	Mandatory when the MOE pre-established in the MOE Rule Table is a Military Service, a DoD manager, or a Defense Supply Center for the MOE Rule Number being deleted from the

NIIN record or when a NIIN is being cancelled (i.e., cancel-invalid, cancel-duplicate, etc.).

CA	An Association Code, CAGE Code NCAGE (DRN 8855 ) will only be included in input when the Replacement Code is the new parent of a corporate complex and the new Association Code is recorded on the file. Whenever an Association Code is reflected in input, it must be equal to the Replacement Code (DRN 3595) with the fifth position converted to a twelve overpunch.

CC	Mandatory for use with Association Code, CAGE/NCAGE (DRN 8855 ) on affiliate Organizational Entity records. Not applicable for parent O.E. record.

CD	Applicable for O.E. type A only.

CE	Submitted Package Sequence Number (DRN 8328 ), Data Record Number (DRN 0950 ), and Return Code (DRN 9480 ) will be used in segment 822 only by the DLA Logistics Information Service program manager for returning errors found during review of the submittal.

CG	Applicable for O.E. type E only.

CH	Applicable for O.E. type F only.

CJ	CAGE Code (DRN 9250 ) or NATO Commercial and Government Entity Code (DRN 4140 ) as applicable. The appropriate value will be input by the program manager.

CL	This DRN value will be output in cc 23-27 only with an O.E. File Maintenance Transaction Code (DRN 0244 ) 002 indicating that it is a correction of the erroneous code reflected in cc 2-6. No clear text data will be output. When a 002 transaction is output, there will always be a 003 transaction output in the same cycle, which will provide the valid code and the applicable clear text data. Applies to DIC KHN only.

CM	Identifies the recipient of the outgoing interrogation data. The Destination Activity Code (DRN 3880 ) will reflect the Submitting Activity Code (DRN 3720 ) for Services/Agencies (external Customers) submittals and the Originating Activity Code (DRN 4210 ) for internal DLA Logistics Information Service submittals.

CO	Replacement CAGE Code (DRN 3595 ), Replacement NATO Commercial and Government Entity Code.

CP	Commercial and Government Entity Code (DRN 9250 ), for NATO Commercial and Government Entity Code (DRN 4140 ), or Organizational Entity Fabricated Code (DRN 0074

) as applicable.

CT	When value of O.E. Line Segment Number (DRN 1001 ) is 10 (O.E. types A and F only), the entry will be followed by O.E. Clear Text Data Counter (DRN 0248 ) and by optional elements ZIP Code (DRN 4400 ), Contract Administration Office Code (DRN 8870 ), and Automatic Data Processing Point Code (DRN 8835 ) as applicable. Data Element Terminator Code (DRN 8268 ) will be contained in the next succeeding position when DRNs 4400

/8870/8835 are shown. Applies to DIC KHN only.

CU	Not applicable as replacement for cancelled O.E. types A and E.

CV	Data element is mandatory. A combination of any 7 alphanumeric characters (e.g., CPT0001) assigned for control purposes by the originator will be reflected. Must not be repeated for

another transaction on the same day. For KVI special projects, the first position must be K (e.g., K000001).

CX	Not applicable to O.E. type F.

CZ	If no NIIN is applicable, this field will show the NCB Codes of the addressee.

DA	The Package Sequence Numbers (PSN) is constructed of an alpha A through Z in the first position and the numerics 00 through 99 in the next two positions. If a transaction contains only one record the PSN will be Z01. When a transaction contains multiple records, the first segment record in a transaction package will begin with A01; the second A02; the third A03; the final record will be assigned a Z in the first position and the next sequential number in the next two positions. If the package exceeds 99 segment records, the 100th segment record will be B00; the 101st B01; etc. If the package exceeds PSN Y99, then Y99 will be repeated until the final record which will be Z00. DICs LSF and LSR are an exception. The LSR input transaction cannot exceed PSN Z25 for the same Submitter Control Number (DRN 1120 ). If a transaction package consists of only one segment record, PSN Z01 will be used. Output from these DICs will be in alpha-numeric format. (See volume 1 , paragraph 1.4.1.d ).

DB	Computer generated when input contains Organization Entity Designator (DRN 2620 ) values 3, 4, 5, 6, 7, or G.

DC	When the erroneous code has been used as an Association Code (the fifth digit converted to twelve overpunch), the erroneous Association Code will automatically be changed to reflect the corrected Association Code on the parent and each affiliate record.

DE	“Z” required when input contains Contract Administration Office Code (DRN 8870 ) and Automatic Data Processing Point Code (DRN 8835 ).

DF	O.E. Designator (DRN 2620 ) values G, 3, or 6 only. DG	Applicable to type A if domestic; type E if foreign.

DH	The assigned NIIN of the transaction being followed-up will be reflected, exception: a follow- up for a DIC LSA.

DJ	The Military Surface Deployment and Distribution Command (SDDC) is the only authorized submitter of the Integrity Code. Data Element should be blank for transactions input by Services/Agencies other than SDDC.

DL	O.E. Line Segment Number 08 is mandatory if Minimum Address Code (DRN 2645 ) is not present.

DM	For reference number screening results (LST) Matched NSN (DRN 4120 ) will be given. For FLIS file data for replacement of a canceled NSN during NIIN interrogation/search (LTI or LSF), either the Replacement NSN, Cancellation (DRN 8875 ); Master NSN (DRN 0797 ); Master Generic NSN (DRN 0796 ); or Related NSN (DRN 2895 ) will be given.

DO	Mandatory for all FLIS-originated transactions.

DP	Omission of Replacement CAGE Code (DRN 3595 )/Replacement NATO Commercial and Government Entity Code input when changing status from R or Y to N, P, U, or W will automatically cause DRN 3595 to be deleted from the O.E. record.

DQ	This data element will be included if it is available in FLIS file(s) or was contained in the

input transaction. When output is the result of a roll-up of Catalog Management Data, the field will contain DIC LCM.

DR	The Demilitarization Code is mandatory when the MOE preestablished in the MOE Rule Table is a Military Service, Coast Guard activity, or Defense Agency manager recorded Primary/Secondary Inventory Control Activity (activity code AA through XC, XF through XW). Activity code XD is an exception. The Demilitarization Code is not required when the MOE preestablished in the MOE Rule Table is a Civil Agency (numeric activity code) PICA/SICA on submitted MOE Rule Number. However, if the Civil Agency is supporting a Military Service, the DEMIL Code is required (activity code of AA through XC, XF through XW is the PICA/SICA on submitted MOE Rule Number). The Demilitarization Code is not required when the MOE preestablished in the MOE Rule Table is a foreign country (FC) (activity code prefixed by a W, Y, or Z) on the submitted MOE Rule Number. This data element will be included on output when recorded in the FLIS files. When the Demilitarization Code is not applicable, the field will be left blank.

DS	Organizational Entity Code type A or F is acceptable as replacement for cancelled O.E. type F.

DT	For O.E.s located in Canada, Automatic Data Processing Point Code (DRN 8835 ) and Contract Administration Office Code (DRN 8870 ) are computer-assigned when Exception Code C is present.

DU	Computer-assigned when CAO/ADP Exception Processing Code (DRN 8868 ) is omitted and ZIP Code (DRN 4000 ) is present.

DV	Required when Automatic Data Processing Point Code (DRN 8835 ) is input. DW	Required when Contract Administration Office Code (DRN 8870 ) is input.

DX	Required when submission is suspended for program manager review.

DY	Required if resubmittal of previously suspended (or rejected) input include(s) System Support Record (SSR) name match(es).

DZ	Optional if originated by Canadian government.

ED	Required when the submitted MOE Rule Number is a Primary Inventory Control Activity (PICA) MOE Rule reflecting Level of Authority 22 or a Secondary Inventory Control Activity MOE Rule reflecting SICA LOA 8D.

EE	DLA Logistics Information Service use only.

EF	O.E. Line Segment Number (DRN 1001 ) 10 only. Value mandatory for O.E. types A and F when DRN 2645 is omitted in segment 820.

EH	Data element is applicable to O.E. types A and F only.

EJ	The Submitted Package Sequence Number (DRN 8328 ) will never be output for error conditions related to characteristics data (Master Requirement Code/Primary Address Code (MRC/PAC)).

EK	Unless special deviation is indicated, the data applicable to this DRN will not be generated onto the O.E. SSR.

EM	Required when O.E. System Support Record contains DRN 4539 .

EP	The code to be reinstated (DRN 9250 /4140) must be on the file in a cancelled status.

ES	Unless otherwise indicated, DRN value will be computer generated upon approval of proposed input transaction.

ET	Data element is required for first card of name type 0 only, or name type 2 (with DRN 4065 - all except USA); otherwise this field is blank. (DLA Logistics Information Service /DLA Disposition Services only.)

EU	Optional, if originated by DLA Logistics Information Service.

EV	Item Name Code (DRN 4080 ) or Name Code, Non-Approved (DRN 8470 ) is mandatory. (DLA Logistics Information Service /DLA Disposition Services only.)

EW	Item Name (DRN 5000 ), Index Entry (DRN 0094 ), Basic Name (DRN 9561 ), or Colloquial Name (DRN 4955 ) is mandatory. (DLA Logistics Information Service /DLA Disposition Services only.)

EX	CAGE Code, NCAGE, or O.E. Fabricated Code. The appropriate data elements will be reflected.

EY	Data element is required for first card (DLA Logistics Information Service /DLA Disposition Services only.)

EZ	Data element is required for name type 0. (DLA Logistics Information Service /DLA Disposition Services only.)

FA	Data element is optional for name type 0 only, otherwise this field is blank. (DLA Logistics Information Service /DLA Disposition Services only.)

FB	External submission reflecting O.E. Line Segment Number(s) 02 through 07 and 09 are acceptable.

FC	Must be coded 1 or 3 when Type of Organization Entity Code (DRN 4238 ) is A; 2 when type is E; 1, 2, or 3 when type is F.

FD	O.E. Line Segment Number(s) 01 and 08 are not permitted.

FE	The use of Old Item Name Code (DRN 0100) and Item Name Code (DRN 4080 ) will indicate the type of notification. Only DRN 2646 will be output for a cancel INC without replacement. Only DRN 4080 will be output for a new INC establishment. Both DRNs will be used for cancellation with replacement. Freight data and item name will apply to DRN 4080 when necessary.

FF	Replacement CAGE Code, Replacement NCAGE is required when O.E. Status Designator is R when data element is already recorded on the Organizational Entity file with an O.E. Status Designator of R. The appropriate data element will be reflected.

FG	DRN 1001 not applicable for input transactions by itself; must be in combination with DRN 0010 .

FH	The correct code (CAGE or NCAGE) will be entered in this field.

FI	This data element/segment is for representative purposes only. Individual/original DIC formats should be referenced for actual note numbers.

FJ	Required if input contains Organizational Entity Line Segment Number (DRN 1001 ) as

applies to note FB.

FO	If program manager determines that Association Code, CAGE/NCAGE (DRN 8855 ) no longer applies to a given O.E. record, the omission of DRN 8855 on the parent O.E. record will cause the Association Code to be deleted from the parent O.E. record and the Association Code and the Type of Affiliate Codes for all records for that corporate complex.

FP	Omission of Association Code, CAGE/NCAGE (DRN 8855 ) in input will automatically cause deletion of Organizational Entity Designator (DRN 2620 ), percent symbol (%), when transaction affects parent O.E. record.

FQ	The Alternate Output Media Code (DRN 0420 ) is mandatory when the reply to Output Mode/Media Code (DRN 3740 ) is A1 or A2.

FR	Change of Foreign/Domestic Code (DRN 4235 ) from 1 to 2 or 3 will require purging of O.E. System Support Record ZIP Code (DRN 4400 ).

FS	Change of Foreign/Domestic Code (DRN 4235 ) from 2 or 3 or 1 requires inclusion of ZIP Code in O.E. input transaction.

FT	Change of CAO/ADP Exception Processing Code (DRN 8868 ) from C to Z requires inclusion of CAO/ADP Codes in O.E. input transaction.

FU	Change of CAO/ADP Exception Processing Code (DRN 8868 ) from Z to C requires purging of O.E. System Support Record CAO/ADP Codes (DRNs 8870 and 8835 ).

FW	This field is optional. If not required, the field will be completely omitted by using zeros in the reply data counter field.

FX	Either the Requirement Statement, SR-1 Spec/Std Controlling Data, or SR-5 Manufacturers Data may be given. If not required, the field will be completely omitted by using zeros in the Requirement Statement Counter field.

FY	Required if Minimum Address Code (DRN 2645 ) is excluded and Foreign/Domestic Code (DRN 4235 ) is coded domestic.

FZ	Required if O.E. Line Segment 08 is excluded from input.

GA	This DIC will contain Replacement CAGE Code (DRN 3595 ) or Replacement NCAGE Code in the Reference Number, Logistics (DRN 3570 ) field as applicable (DLA Logistics Information Service /DLA Disposition Services use only).

GB	Applicable only when changing replacement code on O.E.s with status R.

GC	Replacement CAGE Code (DRN 3595 ) or Replacement NCAGE is applicable. (DLA Logistics Information Service /DLA Disposition Services use only.)

GG	This data element is required if element Subject to Integrated Materiel Management Code (DRN 9545 ), Subject to Item Management Coding (DRN 9546 ), or Subject to Single Submitter Procedure (DRN 9544 ) is submitted as Y.

GI	Overflow of data which requires additional card(s) to accommodate will continue beginning in cc 31 of second and/or succeeding cards.

GJ	Required entry for output resulting from trans- actions other than requests for NIIN assignments.

GO	Data Element should be blank for transactions input by the Military Surface Deployment and Distribution (SDDC). SDDC is not authorized to submit the Hazardous Materiel Code or the various MILSTAMP Codes.

GP	Data Element will either be perpetuated from input transaction or extracted from DLA Logistics Information Service file(s).

GQ	All A, F, M or N MOE Rules with PICA/SICA LOA 22/8D must have a Depot Source of Repair (DSOR) Code. Civil Agency LOA 22/8D MOE Rules must not have a DSOR.

GR	For LTIs submitted by “AN”, the Originating Activity Code (DRN 4210 ) response (alpha and/or numeric) can be either included or not included on volume 10, table 104 .

GS	The occurrences of DoD I&S Family data (DRNs 2833 , 0793 , 0792 , and 0795 ) will be output in the following sequence when two or more MOEs are output on the same DoD I&S Family: Commodity Integrated Materiel Manager, Army, Air Force, Marine Corps, and Navy, as applicable.

GT	This field will be blank if one Mode Code is applicable, contain a Mode Code if two Mode Codes are applicable, or an asterisk (*) if three Mode Codes are applicable to a given Primary Address Code (PAC).

GU	Required for provisioning/preprocurement screening transactions. Optional for all others.

GV	Value of 1-9 indicates number of times a Phrase Code appears following this field. If there are no Phrase Codes, this position will be blank. If it is also the last position of the segment (there is no other data element information following the segment), it will be truncated by omitting this space. The space will not be included in the segment length.

HA	This field will reflect either the date of processing of a future effective dated Catalog Management Data and/or logistic management transfer or the processing date of withdrawal of support.

HB	A maximum of 30 reference numbers may be submitted under the same Document Control Number.

HC	Field can reflect a date from 30 up to 120 days in the future, adjusted to the first day of a month. Use last two digits of year and Julian day. May be zero filled (00000) only for MOE Rules reflecting Level of Authority Codes 07, 08, 11, and 48. Field must be filled, except for NATO/foreign government recordings (LOA 81) which must be zero filled or blank. For SICA submitted LDUs the effective date time frame is 0-60 days, (field can be zero filled (00000)).

HD	Can reflect a date from 30 to 180 days in the future, adjusted to the first day of a month. Use last two digits of year and Julian day. Minimum of 30 to 120 days for non-Integrated Material Manager/Lead Service transfers. Minimum of 75 to 180 days for IMM/Lead Service transfers. Minimum of 0 to 120 days for transfers of Coast Guard MOE Rules from USCG as Primary Inventory Control Activity (PICA) LOA 26 to USCG as Secondary Inventory Control Activity (SICA) LOA 5D, 5G, or 67. Field must be filled.

HE	This data element and correlating related data can be repeated to a maximum of 50. HF	When there are multiple entries for this data element, the data element will be output

consecutively until completed.

HH	Data Element is mandatory when Q phrase code is entered for all except the Army.

Otherwise, data element is optional.

NA	Data element is mandatory and may be repeated as required. Applicable MRCs/PACs will be reflected with their mode codes and replies, using the applicability key in the appropriate Item Identification Guide (IIG). Enter the Data Element Terminator Code (DRN 8268 ) at the end of the Characteristics Data Group, except the last one in the segment.

NB	Data element is mandatory. A crosshatch (#) must terminate each DRN value.

NC	Applicable code will be reflected. See DRN to Data Code Table Cross Reference ( volume10, section 10.2.2 ) for proper table reference containing data codes.

ND	Data element is mandatory. Applicable segment code will be reflected. NE	Data element is mandatory. Enter “9995”.

NF	Data element is mandatory. Enter NATO/foreign country (FC) NSN in numeric format as follows: XXXX-XX-XXX-XXXX. Must be 16 positions.

NG	Data element is mandatory. Enter either the United States/Canada or NATO/foreign country (FC) NCAGE that is recorded in the FLIS against the reference number for which the related code(s) are being changed/deleted.

NH	For card formats, continue the reference number from the first card. To delete a primary reference number which exceeds 32 positions and is supported with Primary Address Code ELRN in segment V of the FLIS data base, submit DIC LCC with DIC LDR under DIC LMD. DIC LCC is used to delete PAC ELRN from segment V. If PAC ELRN is not in the file, no LCC or LMD is required.

NJ	Data element is mandatory for input/output for all NATO/Foreign Governments. The field will be blank for activities other than NATO/FG. Enter RNFC as recorded in FLIS data base against the reference number to be deleted.

NK	Data element is mandatory. Applicable Document Identifier Code will be reflected. NL	Submitting Activity Code may be the same as Originating Activity Code.

NM	Data element is mandatory. Date the transaction originated will be reflected, using the last two digits of the year and the Julian day (e.g., 83213 for 1 Aug 83).

NN	Data element is mandatory. The reference number which identifies the item of supply will be reflected. If more than 16 positions are needed, a continuation card will be used. If the reference number exceeds 32 positions, the Extra Long Reference Number Indicator (a dash, (-)) will be reflected in the 32nd position and the complete reference number in segment V under MRC ELRN. (The primary reference number cannot exceed 32 positions for a type 2 item identification.) Additional extra long reference numbers will employ the same technique except the complete reference number will not appear in segment V. See volume 10, section10.2.5 for information concerning circumstances requiring preparation of continuation cards.

NP	The Item Management Coding Activity (DRN 2748 ) must be submitted when an Item Management Code (DRN 2744 ) is entered for items under Commodity Integrated Materiel Management (Primary Inventory Control Activity Level of Authority (PICA LOA) 01, 02).

NQ	When submitting supplementary data collaborators or receivers, the associated counters (DRNs 8375 and 8380 ) will identify the number of collaborators or receivers being submitted. If not applicable, the field will be left blank.

NR	For reference number screening results or FLIS data base file data for replacement of a cancelled NSN/ during NIIN interrogation/search. Either the Assigned NSN (DRN 3960 ); Replacement NSN, Standardization Relationship (DRN 9525 ); or Replaced NSN, Standardization Relationship (DRN 8977 ) will be given.

NT	The recorded year and Julian day when a standardization decision was applied to an item under the DoD Standardization Program will be reflected, using the last two digits of the year and the Julian day (e.g., 19 March 1979 will be 79079).

NU	Data element is mandatory. Enter applicable MOE Rule Number (DRN 8290 ) or Former MOE Rule Number (DRN 8280 ). See volume 10, table 104 , and volume 13 .

NX	Data element is mandatory on input, optional on output. If characteristics are required, the applicable A or T IIG number will be reflected. First character will always be A or T. Next three characters always numeric. If the last character is 0, the fifth character must be either 0 or alphabetic. If fifth character is a dash, the last character must be alphabetic (e.g., A00100, T243-A).

NY	Data element is required for type 1, 1A, 1B, 4, 4A, and 4B items. Code M or E will be compatible with replies given to MRCs CRTL and NHCF. Code H or E will be compatible with a reply to MRC NHCF. Code Y or F will be compatible with a reply to MRC CRTL.

NZ	Data element is mandatory. Applicable Item Name Code from Cataloging Handbook H-6, Federal Item Name Directory, section B will be reflected.

PB	Data element is mandatory. Enter a count to determine the number of repetitions of the group of reflected data.

PC	Data element is mandatory. The applicable Federal Supply Class (FSC) for the item will be reflected (see Cataloging Handbook H6/A and H6/B, Federal Item Name Directory).

PE	Data element is optional. If used, the appropriate DRN will be submitted or returned.

PF	Data element is mandatory. The 17-position alphanumeric number which is used to control and sequence the transaction package will be reflected. Any locally assigned 17-position alphanumeric number may be used.

PH	A crosshatch (#) will be reflected to terminate each Characteristic Data Group except the last one in the segment.

PK	Data element is mandatory. The number of characters in the reference number will be reflected in numeric value.

PL	Data element is mandatory. If input, the number of characters in the Item Name, NonApproved will be reflected in numeric value. if not applicable, must be zero filled.

PM	Data element is mandatory. Indicates number of sets of fixed data elements included in this output package.

PN	Data element is mandatory. See DoD 4140.26-M, Defense Integrated Materiel Management for Consumable Items.

PP	Used in P type screening requests only; must be Reference Number Variation Code 2; otherwise leave field blank.

PR	This segment is generated by FLIS as output only. It is included in the output package(s) resulting from reference number screening requests to indicate the specific reference number that caused a match or no-match condition.

PS	Field can reflect a date from 30 up to 120 days in the future, adjusted to the first day of a month. Use last two digits of year and Julian day. May be zero filled (00000) only for Defense Nuclear Agency, National Security Agency, and Defense Industrial Plant Equipment Center interest-only recordings. Field must be filled. FLIS-generated LKD, LKU, and LKV transactions will reflect a date from 150 to 180 days in the future unless the item is in no-user status and segment H data is not required, then 00000 may be used. All LKI transactions will be zero filled (00000). Relative to Date, Effective, Logistics Action (DRN 2128 ) for Catalog Management Data (CMD) input, the field will reflect an effective date between 0 and 78 days after the date of submission (adjusted to the first of the month) or be zero filled. See volume2, section 2.8.3 for specific effective date criteria and minimum/maximum timeframes.

PT	A code identifying the government activity authorizing the submittal of provisioning and other preprocurement screening requests.

PU	Federal Supply Class may be submitted, but will not be edited; if other than submitted, file version will be output. No segment 1 notification will be forwarded.

PZ	The document number which is constructed in Military Standard Requisitioning and Issue Procedures (MILSTRIP) format will be reflected.

QA	First DRN of appropriate segment will be reflected in accordance with Table of Permissible DRNs.

QB	The value for preceding field will be reflected.

QC	The 16-position Document Control Number (DRN 1015 ) of the original transaction for which the follow-up interrogation is being submitted for the first segment R record will be reflected.

QD	The input DIC of the original transaction for which the follow-up interrogation is being submitted will be reflected. Cannot be DICs LFU, LKI, LPM, LSF, LSN, LSR, LTI, all System Support Record (SSR), NATO, and Utilization and Marketing input DICs.

QF	The assigned NSN being cancelled will be reflected.

QG	DRN, DRN Value, and Data Element Terminator Code are repeated as required. A blank position is mandatory between each cited DRN and DRN Value (i.e., DRN, ``blank”, DRN Value, and Data Element Terminator Code).

QH	In the event a data group (Data Record Number, DRN 0950 ; Data Record Number Value, DRN 9975 ; and Data Element Terminator Code, DRN 8268 ) begins in position 41 and cannot be completed on the same record, position 80 will contain the Continuation Indicator Code, DRN 8555 , and the entry will be continued on second and succeeding record(s) beginning in position 41. Whenever a second and succeeding data group (DRNs 0950 , 9975 , and 8268 ) can be completed on the same record in which a preceding data group appeared,

the data group may be entered on the same record. Otherwise, enter the second and succeeding data group on a new segment R record beginning in position 41, with DRN 8555 in position 80 of the preceding record.

QI	Next DRN of appropriate segment will be reflected in accordance with Table of Permissible DRNs.

QM	Enter a double crosshatch (##) (e.g., Segment V Terminator Code, DRN 0339 ) at the end of the last Characteristics Data Group of a transaction.

QN	The variable length value of the correct reply to the DRN/Master Requirement Code will be reflected. Segment action AS or DS will be left blank. If the value exceeds 21 positions, continue value in position 47 of continuation record and insert the Continuation Indicator Code (DRN 8555 ) in position 80 of this record. Maximum of 502 positions allowed for each submitted value. If over 502 positions, delete and add segment with Action Codes DS and AS. If value is for MRC, Action Code AA or AC, the MRC must be submitted in this field with mode code and the reply.

QP	The first segment H DRN must be Date, Effective, Logistics Action (DRN 2128 ), except Phrase Relationship Group (DRN 0217 ) will be entered when permissible.

QQ	The standard price of the Unit of Issue, constructed as follows, will be reflected. Prices below ten million dollars will be right justified and zero filled. Right-most two digits are always cents, no decimal point provided ($18.54 is represented as 000001854). Prices of ten million dollars and above will have a D in the right-most position. No cents value or decimal point are provided ($10,000,000.00 is represented as 10000000D).

QR	The applicable expression will be reflected when the Unit of Issue is nondefinitive (medical items excluded). Criteria for development is as follows:

First position - Decimal locator identifies position of decimal point in the quantity field: “0” whole number (no decimal)

“1” decimal point before position 11

“2” decimal point before position 10

“3” decimal point before position 9

“4” decimal point before position 8

Positions 2-11 - Quantity field indicates the number of Units of Measure contained in the Unit of Issue of the Catalog Management Data (CMD). NOTE: The Quantity field within the Quantitative Expression DRN will be right justified and zero filled.

Positions 12-13 - Applicable Unit of Measure from volume 10, table 81 .

QS	The factor by which the old quantity must be multiplied to convert to a new Unit of Issue must always be supplied when the Unit of Issue changes. Criteria for development is as follows:

First position - Decimal locator identifies position of decimal point in the multiplier field. “0” whole number (no decimal)

“1” decimal point before position 5

“2” decimal point before position 4

“3” decimal point before position 3

“4” decimal point before position 2

Positions 2-5 - Multiplier field. Standard factors are contained in volume 10, table 79 .

QT	Data element is mandatory. The original input DIC causing the data element to be effective dated will be reflected.

QU	Data element is mandatory. The originator of the futures dated transaction will be reflected. QV	Data element is mandatory. This DRN represents the segment that contains the futures data. QW	Data element is mandatory. The reference number extracted from the Military Standard

Requisitioning and Issue Procedure requisition, which is limited to 10 positions, will be reflected. The complete reference number will be recorded in the MILSTRIP remarks position. Any reference number exceeding ten positions should not be submitted in this transaction.

QX	Reference number must not exceed 32 positions. Reference number will not be submitted without its assigned Commercial and Government Entity Code/NATO Commercial and Government Entity. (CAGE/NCAGE).

QY	The first segment H DRN must be Date, Effective, Logistics Action (DRN 2128 ), except Former Phrase Relationship Group (DRN 0216 ) or Unit of Issue Change Data (DRN 0218 ) will be entered when permissible.

QZ	Data element is mandatory. The North Atlantic Treaty Organization (NATO) Stock Number will be reflected.

TA	The Data Element Terminator Code (#) will be reflected between and at the end of each address component of In The Clear Address (DRN 0045 ).

TC	If the MOE Rule Status Code equals 1 (canceled - not replaced), the cancelled MOE Rule will be retained as reference information in your file. If the status code is not present, delete this MOE Rule from file.

TD	See volume 10, table 104 and volume 13 .

TE	Element will be included only when an actual or possible duplicate has been revealed during item identification processing.

TF	Applicable code will be reflected. Source of codes is DoD 4140.17-M, supplement 1, MILSTRIP Routing Identifier Codes.

TG	Correct code will be reflected when there is knowledge of possible duplication or when code presently in FLIS is to be changed. Otherwise field will be left blank.

TH	Data element is mandatory. The Assigned NSN (DRN 3960 ), Master NSN (DRN 0797 ); Generic Master NSN (DRN 0796 ), or Related NSN (DRN 2895 ) will be reflected as appropriate.

TI	Data element is mandatory. The Master NSN (DRN 0797 ) or Generic Master NSN (DRN 0796 ) will be reflected as appropriate.

TJ	The Assigned NIIN or System Control Number (SCN) for the item being interrogated will be

reflected. If none is applicable, leave blank.

TK	Submittal is mandatory for the Federal Aviation Administration, Civil Agencies with Primary Inventory Control Activity Level of Authority 48, and National Security Agency as a PICA with PICA LOA 23 or 26.

TL	The field reflected for DRN 3317 , Characteristics Data Group, is representative only. The data element will begin in the first column as shown, but owing to the variable length of the data element, its end cannot be predicted (990 character maximum for clear text reply; maximum of 78 replies for any single Master Requirement Code (MRC) when Secondary Address Coding (SAC) or AND/OR coding is authorized). Enter a Data Element Terminator Code (#)(DRN 8268 ) at the end of each Characteristics Data Group.

TM	If deleting individual characteristics data (MRC by MRC), each Characteristics Data Group which is to be deleted will consist of the four-position MRC followed by the Data Element Terminator Code (#). If deleting all of the characteristics data (all MRCs) on file, the four- position MRC will be 9118 followed by the Data Element Terminator Code (#). This MRC must always be the first MRC in the LCC submittal, followed by a Data Element Terminator Code, and must be followed by characteristics data for the new description.

TN	Field can reflect a date up to 120 days in the future, adjusted to the first day of the month. Use last two digits of year and Julian day. For immediate effective date, submit zeroes (00000).

Field must be filled, except for NATO/foreign government recordings (LOA 81) which must be zero filled or blank.

TP	Data element is optional. If a change to the Criticality Code is required, the appropriate code will be selected from volume 10, table 181 . There must be compatibility between the new Criticality Code and MRCs CRTL and NHCF in the IIG. If the Criticality Code indicates the item is nuclear hardened MRC NHCF must be answered. If the Criticality Code indicates the presence of another critical feature MRC CRTL must be answered.

TQ	Enter the activity code of the activity requesting deletion of the logistics transfer. TR	Enter activity code 9T.

TT	Additional records will be used, if required, to reflect all Destination Activity Codes.

TU	The appropriate Item Management Classification Agency for the FSC Class should be entered from the standard FSC Table. If the item is a DLA/General Services Administration management exception item, enter the appropriate Integrated Materiel Manager (IMM) for the item regardless of the class.

TW	This card is required for all submittals, with the exception of change coding not involving estimated demand/Demand Indicator Code.

TX	When the Demand Indicator Code field contains a zero (0), this field will be zero filled. TY	Separate output will be sent to each destination activity listed on input DIC LDZ.

TZ	Enter DRN of the segment that was effective dated but is to be deleted. Segment Z will be repeated as necessary to list all segments affected.

UA	When no messages are transmitted, 0000 will appear in these positions.

UD	This data element is not applicable to a submittal by a NATO or other foreign government, or

by a Primary Inventory Control Activity Level of Authority (PICA LOA) 04 (first position T MOE Rule).

UE	A maximum of three (3) reference numbers is permitted under one Document Control Number when searching another country's reference numbers.

UF	When a NATO Commercial and Government Entity Code (DRN 4140 ) is reflected, the Type of Screening Code (DRN 9505 ) must be S or F, the Statistical Indicator Code (DRN 3708 ) must be C and the Reference Number, Logistics (DRN 3570 ) must be formatted in accordance with volume 2, chapter 2.9 of this manual.

UG	The code in this field and the manufacturers code in this search request must represent the same country. (See volume 10, table 104 , for appropriate country code. The first position must be W, Y, or Z.). For U.S. submittals that contain U.S. reference numbers, this field will be blank.

UH	Only Reference Number Category Code (RNCC) 5 or 8 may be used when a NATO/foreign government is adding a reference number to a U.S. NSN, or a U.S. activity is adding a reference number to a NATO Stock Number. See volume 4, chapter 4.11.2 for further instructions on exceptions to that rule.

UJ	NATO/foreign governments may delete only NATO/FG-assigned reference numbers with RNCC 5 or 8 from an existing U.S. NSN. U.S. Services/Agencies may delete only U.S.- assigned reference numbers with RNCC 5 or 8 from an existing NATO Stock Number in the FLIS data base. See volume 4, chapter 4.11.2 for further instructions on exceptions to that rule.

UK	This data element is mandatory for this DIC and will be perpetuated from the input transaction. Exception: When DIC KIM is output resulting from DIC LAU/LCU input and the Catalog Management Data (CMD) to be pushed has already been pushed on a 45 day KIM, this data element will reflect the effective date on the last 45 day KIM pushed instead of the effective date of the input transaction.

UL	If the transaction is to contain a Integrated Materiel Manager (IMM) Lead Service/DoD manager MOE Rule (reflecting PICA with PICA LOA 06, 22, or 23 and no Secondary Inventory Control Activity (SICA)), it must be the first MOE Rule in the package.

UM	Data element is mandatory. If a central file activity is extracting and submitting comparison data for multiple activities, this activity code must be reflected in the Submitting Activity Code field (DRN 3720 ). The Submitting Activity Code may be the same as the Originating Activity Code.

UN	If an activity receives a sample NIIN which it does not have, return 999 in the File Maintenance Sequence Number field, DRN 1515 .

UP	When a clear text reply is given for Primary Address Code/Master Requirement Code (PAC/MRC) NAME, the first 19 positions must be identical to DRN 5020 , Non-Approved Item Name (NAIN).

UR	Mandatory when submitted reference number contains Reference Number Category Code C. US	Input segment length 20 to 55 positions. Output segment length will always be 55 positions.

UT	This data element applies only to input by or output to activity 9Z. This field will reflect a Submitting Activity Code, Related Transaction, when the Originating Activity Code (DRN 4210 ) is other than 9Z and the Submitting Activity Code (DRN 3720 ) is 9Z.

UU	Catalog Management Data (segments H and R) with a Submitting Activity Code of JG and Originating Activity Code of PM will be processed as Marine Corps CMD.

UY	The MDL phrase code value of G, J, S, 7, E, F, U or 3 cannot be submitted for this DIC.

UZ	When the NSN in the input header is a Related NSN I&S Family, this data element will be blank.

VA	Order of Use sequence for each MOE must reflect “AAA” as the lowest value. Subsequent OOU values must conform to the following criteria: The third position of the OOU must be one greater than the third position of the preceding OOU. If not, the second position must be one greater than the second position of the preceding OOU and the third position must be “A”. If not, the first position must be one greater than the first position of the preceding OOU and the second and third positions must be “AA”. The Master National Stock Number must have the highest value OOU.

VB	Must be at least two subgroup values greater than the submitted OOU, and the third position must be “A”. JTC, when applied, must be recorded against the item having the highest sequence value in a subgroup. JTC may not be applied against the Master NSN.

VC	When submitting the I&S Order of Use for the Master/Generic Master NSN the Related NSN field (positions 43-55) must be blank.

VD	PICA LOA 06, 22 or 23 submittals must contain an OOU value of “ZZZ” for those related NSNs that the PICA (LOA 06, 22 or 23) has Management interest only (Non user). The PICA (LOA 06, 22 or 23) submittals must contain an OOU value of “XXX” for the Master NSN when the PICA (LOA 06, 22 or 23) reflects an OOU value of “ZZZ” for all related NSNs.

IMMs reflecting LOAs 01 or 02 must submit an OOU for each I&S Family Member. VF	When the NSN in the input header is an I&S Family Related NSN, the Phrase Code-

Management Data List field (position 41) must be E, F, 3 or U when the associated Related NSN field (positions 43-55) reflect a I&S Family Master NSN Phrase Code U can only be submitted by a PICA LOA 06, 22 or 23. The Phrase Codes other than blank, G, J, S, 7, E, F, U and 3 may be submitted as required in accordance with volume 10, table 96 .

VG	Either the Assigned NSN (DRN 3960 )/Master NSN (DRN 0797 )/Generic Master NSN (DRN 0796 )/Related NSN (DRN 2895 ) is mandatory. The appropriate data element will be reflected.

VI	When submitting Order of Use (OOU) the associated Phrase Code-Management List (MDL) field (position 41) will reflect the following contents in accordance with volume 6, chapter 6 :

a. Blank when associated with the I&S Family Master's OOU or an OOU of ZZZ.

b. Blank when the LAM/LCM is not contained within a LMD or LMX and DLA Logistics Information Service is to generate all I&S Phrase Code-MDL for the submitted I&S Family.

c. Phrase Code-MDL of G, S, or 7 in accordance with volume 10, table 96 if a and b above do not apply.

VL	This segment will be provided with those data elements available in the FLIS file(s).

VM	This data element is a mandatory data element and cannot be deleted. The submitted PMIC in Segment A must be compatible with Characteristic Data submitted/recorded in Segment V. When an LCC adds, changes or deletes Precious Metal MRCs in Segment V, the PMIC will be automatically updated unless a PMIC is submitted within an LMD/LCC/LAD or LCD package.

VN	This data element is output, if recorded, when requesting segment H file data.

VO	This code is mandatory on all requests for NIIN assignments, all NIIN reinstatements, all reactivations, adds or reinstatements submittals when the assigned Federal Supply Class is reflected in volume 10, table 161 . ADPE Code is optional for all FSCs other than those listed in table 161 .

VP	Data Element is mandatory. Master National Stock Number (DRN 0797 ), or Generic Master Stock Number (DRN 0796 ) will be reflected as appropriate.

VS	Data element is mandatory for input/output for all NATO/foreign governments. The field will be blank for activities other than NATO/FG.

VT	An RNSC submitted by a U.S. activity other than 9Z will be ignored and processing will continue.

VU	Data element is mandatory. This code is used to control and sequence category 1 remote terminal transactions.

VW	This data element is applicable to NATO submitters (except the U.S.) and other foreign submitters. This data element is not applicable to U.S. submitters.

VX	This data element is applicable only to NATO/FG submitters and Activities 9Z, Navy and FAA.

This data element is not applicable to U.S. Submitters except for Navy and FAA.

VY	HMIC (D, P, and N only) automatically generated by FLIS for all NIIN assignments or reinstatements. FOR FSC changes, DLA Logistics Information Service updates the HMIC whenever the following conditions occur:

a. FSC changes to a FSC in Table I or II of Federal Standard 313.

b. Former FSC and new FSC listed on different Tables of Federal Standard 313.

c. FSC changing from a FSC on either Table I or II of Federal Standard 313 to a FSC not on either table.

Only DLA Logistics Information Service or DGSC (Activity HM) authorized to submit HMIC using DICs LAD or LCD.

The HMIC is not permitted on nuclear ordnance items.

VZ	This data element is mandatory on all requests for NIIN assignment, (LNs), NIIN reinstatement (LBs), and FSC changes (LCGs) when the assigned FSC is reflected in volume 10, table 193 . ESDC is optional for all FSCs other than listed on table 193 .

WA	This code is automatically generated by FLIS. When the CAGE is not a Government CAGE, Specification or Standard CAGE and the RNCC/RNVC combination is 3/2, 3/1, 5/2 or 5/1,

the HCC at the NSN level will be derived from the HCCs in the Reference Number Data Segment. If all HCC codes are the same, then the HCC at the NSN level will be the definitive HCC. If the HCC codes differ in the Reference Number Data Segment, an “X1” code at the NSN level will be generated.

# CHAPTER 5 ALPHABETIC INDEX OF DIC TITLES

### TITLE	DIC(s)

Actual Match (Screening)	KMH

Add Catalog Management Data	LAM

 KAM

Add Data Element(s)	LAD

 KAD

Add MOE Rule Number and Related Data	LAU

 KAU

Add Freight Data	LAF

 KAF

Add Nuclear Ordnance Source of Supply	LTU

Add Reference Number and Related Codes	LAR

 KAR

Add Standardization Relationship	LAS

 KAS

Add FLIS Data	KAT

Add Total SSR MOE Rule Record	KUA

Add U.S. National/NATO Stock Number as Informative Reference	LAB

Advance Informative FLIS File Data	KIE

Association Code Match (Screening)	KMA

Cancel-Duplicate	LKD

 KKD

Cancel-Inactive (FLIS only)	LKI

Cancel-Inactive	KKI

Cancel-Invalid	LKV

 KKV

Cancel SSR MOE Rule with Replacement	KUB

Cancel-Use	LKU

 KKU

### TITLE	DIC(s)

Cancel without Replacement or Delete SSR MOE Rule Record	KUD

Catalog Management Data as a Result of IMM/Lead Service Input	KIM

Change Catalog Management Data	LCM

 KCM

Change Characteristics Data	LCC

Change Data Element(s)	LCD

 KCD

Change FSC, Item Name, Type of Item Identification or RPDMRC	LCG

 KCG

 LCZ

Change Item Standardization Decision Data not in a Standardization Relationship	KCZ Change MOE Rule Number and Related Data	LCU

 KCU

Change Freight Data	LCF

 KCF

Change NIIN Status Code	LCI

 KCI

Change Nuclear Ordnance Source of Supply	LTV

Change Reference Number Related Codes	LCR

 KCR

Change SSR MOE Rule Record	KUC

Change Standardization Decision Data for a Replaced NSN, Standardization Relationship

 LCS

 KCS

Conflict Notification	KNI

DLA Transaction Services Critical Source of Supply Update	LSS

DLA Transaction Services Source of Supply Update	KSS

Delete Catalog Management Data	LDM

 KDM

Delete Data Element(s)	LDD

 KDD

Delete Logistics Transfer (FLIS only)	LDZ

 KDZ

Delete MOE Rule Number	LDU

Delete Freight Data	LDF

 KDF

Delete Reference Number(s)	LDR

 KDR

### TITLE	DIC(s)

Delete Standardization Relationship	LDS

 KDS

Delete Total SSR Standard FSC Management Record	KFU

Electronic Data Transmission Message Control	KWA

Exact Match (Screening)	KME

Exact Match with Errors in Submitted FII (Submitter)	KMU File Data for Replacement NSNs when not Authorized for Procurement	KFR FLIS File Data	KFD

FLIS File Data for Replacement of a Cancelled NSN or Reference Number Screening Results

 KFE

Follow-Up Interrogation	LFU

Follow-Up Interrogation Results	KFU

Follow-Up Interrogation, NATO only	LFN

Follow-Up Interrogation Results, NATO only	KFN

Follow-Up Notification	KFP

IMC Data	LVA

Informative Data for Pending Effective Dated Actions	KIF

Interrogate by NIIN	LTI

Interrogated/Search Data Not Available	KTN

Interrogation Results	KIR

Interrogation Results Minus Security Classified Characteristics Data	KTS

Item Management Coding Advice Notification	KVI

Mass Data Retrieval Results	KTA

Matched Stock Number Assigned by Another NATO Country (Screening)	KMN Matching Reference (Screening)	KMR

Match Through Association	KFA

Multiple DIC Input	LMD.A

Multiple DICs	KMD

Multiple NSN Input	LMX

NATO Multiple DIC Input	LMD.B

Negative Reply (Screening)	KNR

New SSR Standard FSC Management Record	KUE

NIIN Status/Index	KFS

Notification of Approval	KNA

Notification of Approval, SSR Transaction	KHP

Notification of Exact Match (Submitter)	KRM

Notification of National Codification Bureau (NCB) Processing	KNN

### TITLE	DIC(s)

Notification of Possible Duplicate (Submitter)	KRP

Notification of Return, SSR Transaction	KHR

Notification of Return (Submitter)	KRE

Notification of Unprocessable Package, SSR	KHS

Notification of Unprocessable Package (Submitter)	KRU

Notification to Increment FMSN	KFM

O.E. SSR File Maintenance Data	KHN

Output Exceeds Electronic Data Transfer Limitations	KEC

Partial Match (Screening)	KMP

Possible Duplicate with Errors in Submitted FII (Submitter)	KPE

Possible Match (Screening)	KMG

Probable Match (Screening)	KMQ

Processing Malfunction	KPM

Quarterly Files Replacement to NATO Supply Centers	KFF Reference Number Submitted for Screening Matched to a Security Classified Item	KMS Reinstate Full Descriptive Method II with Reference Number	LBR

Reinstate Full Descriptive Method II without Reference Number	LBW

Reinstate Partial Descriptive Method II (NIIN only)	LBC

Reinstate Reference Method II	LBK

Request for Codification and for Registration of User	LSA Request for Codification and for Registration on Non-U.S. Manufactured Items	LSB Request for NIIN Assignment (Full Descriptive Method with Reference Numbers) LNR Request for NIIN Assignment (Full Descriptive Method without Reference Numbers) LNW Request for NIIN Assignment (Partial Descriptive Method)	LNC

Request for NIIN Assignment (Reference Method)	LNK

Results of Characteristic(s) Search (No Match)	KSN

Return of Cancellation Action, Retained FII Invalid	KRF

Screening Results	KSR

Search by National Item Identification Number	LSF

Search by Reference Number	LSR

Search by Reference Number for Other Than Provisioning and Preprocurement	LSN Search Results of National Item Identification Number Screening	KIS

Standardization Relationship Preferred Item Data	KMT

Submittal to Update KVI Suspended Item	LVI

Tailored Characteristics Data (Defense Supply Centers Only)	KTQ

Total Data	KTD

# image1.png