|
|
869F |
N101 |
Z1 |
Party to Receive Status |
The entity to receive status for the designated document number |
1. Use when different from Service/Agency prescribed status recipient. Use multiple iterations to identify all status recipients, as required. 2. The DLMS provides the capability to carry additional status recipients beyond those identified by the legacy MILSTRIP. The Media and Status Code and the Distribution Code will be retained in the DLMS to facilitate transaction conversion in a mixed legacy MILSTRIP/DLMS environment. Additional status recipients identified here cannot be passed to legacy MILSTRIP users. |
|
|
869F |
N101 |
Z3 |
Potential Source of Supply |
|
Use when requisitioning nonstandard materiel to identify potential supply sources. |
|
|
869F |
N101 |
Z5 |
Management Control Activity |
|
Use for submission of GFM and CFM transactions. |
|
|
869F |
N101 |
Z7 |
Mark-for Party |
|
1. Use to identify an entity located within the ship-to address that is to actually receive the materiel. 2. May be identified by DODAAC, RIC, clear text, or a combination of these. Only one of DODAAC or RIC may be used. 3. Maximum length is 24 positions: mark-for clear text (with no DODAAC or RIC) displays on DoD shipment documents as two lines of 12 characters each. If text is combined with a DODAAC, up to 17 clear text characters will be allowed. If text is combined with a RIC, up to 20 clear text characters will be allowed. A slash (/) will be inserted during printing of shipment documentation to separate the DODAAC or RIC from clear text; do not perpetuate the slash (/) in the DLMS transaction. 4. Authorized DLMS enhancement; see introductory DLMS note 4g. Refer to ADC 109A. 5. Also use for Requisition Exception Data Transaction (DLA Code YRZ-Transaction Code MF) to identify delivery information. See introductory DLMS note 4f. |
|
|
869F |
N101 |
Z8 |
Last Known Source of Supply |
|
Use to identify the supply source to receive the transaction set. |
|
|
869F |
N101 |
ZL |
Party Passing the Transaction |
|
Use to identify the processing point passing the requisition followup to another supply source for continued processing. |
|
|
869F |
N101 |
3 |
Application Party |
|
Used with Supply Status CX to identify the Routing Identifier of the internet ordering application in notification to DAS that the requisition follow-up failed to receive authorization for continued processing under funds verification procedures. DAS shall prepare CX Supply Status on behalf of the identified internet ordering application rather than continue processing the follow-up. Refer to ADC 328. |
|
|
869F |
N101 |
IAD |
Foreign Office |
|
1. Use for clear-text exception data FMS in-country address. 2. Use for Requisition Exception Data Transaction (DLA DIC YRZ-Transaction Code MA) FOR FMS in-country mark-for address. See introductory DLMS note 4f. |
|
|
869F |
N103 |
10 |
Department of Defense Activity Address Code (DODAAC) |
Use to identify specific units, activities, and/or organizations. The first position indicates the Component or other Government element of ownership or sponsorship. The remaining five positions are assigned under established products by the Service point of the participating Component |
DLMS enhancement; see introductory DLMS note 4a. |
|
|
869F |
N103 |
33 |
Commercial and Government Entity (CAGE) |
|
Use when the organization is a contractor not assigned a DODAAC. |
|
|
869F |
N103 |
50 |
Business License Number |
Use to identify buying or selling entities processing intragovernmental transactions |
1. Use for SFIS to map to SFIS Data element “Business Partner Number TP3”. Enter the buyer’s BPN in N104. 2. Authorized DLMS enhancement; see introductory DLMS note 4g. |
|
|
869F |
N103 |
92 |
Assigned by Buyer or Buyer's Agent |
|
Use with N101 Entity Identifier Code XN to identify the user assigned Shop Service Center/Shop Store Identifier. Refer to ADCs 284A, 381, and 1454. |
|
|
869F |
N103 |
A2 |
Military Assistance Program Address Code (MAPAC) |
Use to identify the consignee in transportation documents and to obtain clear-text address and other shipment information from the military assistance program address directory (MAPAD) |
Use to indicate the SA structured address data. |
|
|
869F |
N103 |
C4 |
Department of Defense Communication Routing Identifier (COMMRI) |
|
1. Use only when N101 is UK. 2. A data maintenance action was approved in version 8060. The approved code/name is 'C4 - Department of Defense Communication Routing Identifier (COMMRI)'. |
|
|
869F |
N103 |
M4 |
Department of Defense Routing Identifier Code (RIC) |
Use to serve multiple purposes; supply source codes, inter-system routing codes, intra-system routing codes, and consignor (shipper) codes |
|
|
|
869F |
N106 |
FR |
Message From |
Use to identify the party originating the transaction set |
Must use with the appropriate 2/N1/10 code to indicate the organization cited in N104 is originating the transaction set. |
|
|
869F |
N106 |
TO |
Message To |
Use to identify the party to receive the transaction set |
Must use with appropriate 2/N1/10 codes to indicate the organization cited in N104 is receiving the transaction. |
|
|
869F |
PER01 |
IC |
Information Contact |
|
Use to identify the point of contact. |
|
|
869F |
PER03 |
AU |
Defense Switched Network |
|
Use to identity the DSN telephone number. |
|
|
869F |
PER03 |
EM |
Electronic Mail |
|
|
|
|
869F |
PER03 |
EX |
Telephone Extension |
|
Use immediately following codes AU, IT, or TE. |
|
|
869F |
PER03 |
FX |
Facsimile |
|
|
|
|
869F |
PER03 |
IT |
International Telephone |
|
Include country and city code. |
|
|
869F |
PER03 |
TE |
Telephone |
|
Use to identify the commercial telephone number. Include the area code and number. |
|
|
869F |
PER03 |
TL |
Telex |
|
|
|
|
869F |
PER03 |
TX |
TWX |
|
|
|
|
869F |
PER05 |
AU |
Defense Switched Network |
|
Use to identify the DSN telephone number. |
|
|
869F |
PER05 |
EM |
Electronic Mail |
|
|
|
|
869F |
PER05 |
EX |
Telephone Extension |
|
Use immediately following codes AU, IT or TE. |
|
|
869F |
PER05 |
FX |
Facsimile |
|
|
|
|
869F |
PER05 |
IT |
International Telephone |
|
Include country and city code. |
|
|
869F |
PER05 |
TE |
Telephone |
|
Use to identify the commercial telephone number. Include the area code and number. |
|
|
869F |
PER05 |
TL |
Telex |
|
|
|
|
869F |
PER05 |
TX |
TWX |
|
|
|
|
869F |
PER07 |
AU |
Defense Switched Network |
|
Use to identify the DSN telephone number. |
|
|
869F |
PER07 |
EM |
Electronic Mail |
|
|
|
|
869F |
PER07 |
EX |
Telephone Extension |
|
Use immediately following codes AU, IT or TE. |
|
|
869F |
PER07 |
FX |
Facsimile |
|
|
|
|
869F |
PER07 |
IT |
International Telephone |
|
Include country and city code. |
|
|
869F |
PER07 |
TE |
Telephone |
|
Use to identify the commercial telephone number. Include the area code and number. |
|
|
869F |
PER07 |
TL |
Telex |
|
|
|
|
869F |
PER07 |
TX |
TWX |
|
|
|
|
869F |
LM01 |
DF |
Department of Defense (DoD) |
Executive department of the U.S. federal government charged with coordinating and supervising the U.S. Armed Forces and related functions and agencies. |
|
|
|
869F |
LQ01 |
0 |
Document Identification Code |
Identifies transaction specific operation to which they apply and indicates the intended purpose and use of the transaction data |
1. The legacy MILSTRIP DIC is retained in the DLMS to facilitate transaction conversion in a mixed legacy MILSTRIP/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date. 2. Use two iterations to identify requisition DIC and Requisition Exception Data Transaction (DLA DIC YRZ), when applicable. 3. Future streamlined data; see introductory DLMS note 4c. |
|
|
869F |
LQ01 |
67 |
Type of Assistance Code |
|
1. For Security Assistance (SA) transactions, use when the coded address in the transaction number does not identify the type of assistance and financing. 2. DLMS enhancement; see introductory DLMS note 4a. |
|
|
869F |
LQ01 |
74 |
Demand Code |
|
|
|
|
869F |
LQ01 |
78 |
Project Code |
Identifies requisitions and related documentation as to special programs, exercises, projects, operations, or other purposes |
1. Use to identify special programs, exercises, projects, operations, and other purposes. 2. For DoD SLOA/Accounting Classification compliance the Project Code may be repeated as a Project Identifier (FA201 Qualifier 90). Refer to ADC 1043. |
|
|
869F |
LQ01 |
79 |
Priority Designator Code |
A code to communicate the relative importance to the requisitioner's mission based upon its force activity designator (FAD) and urgency of need designator (UND) |
|
|
|
869F |
LQ01 |
80 |
Advice Code |
Use to transmit instructions considered by the creators of requisitions to be essential to the desired supply action |
Use to convey information to the supply source which is considered essential to the supply system. |
|
|
869F |
LQ01 |
81 |
Status Code |
Inform recipients of the status of requisitions or customer asset reports and related transactions |
Used by internet ordering applications to notify DAS that the requisition follow-up failed to receive authorization for continued processing under funds verification procedures. Only Supply Status CX is applicable. This is an authorized DLMS enhancement. Refer to ADC 328. |