|
|
870S |
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 |
|
|
|
870S |
N106 |
FR |
Message From |
Use to identify the party originating the transaction set |
Must use with the appropriate 1/N101/050 code to indicate the organization cited in N104 is originating the transaction set. |
|
|
870S |
HL03 |
W |
Transaction Reference Number |
|
Use to identify the individual transaction supply status lops. |
|
|
870S |
DTM01 |
97 |
Transaction Creation |
|
Use to indicate the date of transaction preparation. |
|
|
870S |
CS04 |
83 |
Extended (or Exhibit) Line Item Number (ELIN) |
|
Use to identify the ELIN, or the ELIN including the Sub Exhibit Line Item Number (SUBELIN), as appropriate. |
|
|
870S |
CS04 |
C7 |
Contract Line Item Number |
|
Use to identify the CLIN, or the CLIN including the Sub Contract Line Item Number (SUBCLIN), as appropriate. |
|
|
870S |
CS07 |
AD |
Accept at Destination |
|
|
|
|
870S |
CS07 |
AO |
Accept at Origin |
|
|
|
|
870S |
CS07 |
ZZ |
Mutually Defined |
|
Use Z to indicate Acceptance by Other when destination acceptance shall be performed by an activity other than the ship-to activity. |
|
|
870S |
CS13 |
IM |
Inspect at Destination |
|
Use when origin inspection does not apply and inspection requirements shall be satisfied by the ship-to activity. |
|
|
870S |
CS13 |
IO |
Inspect at Origin G052 Government Inspection |
|
Use code G052 to indicate Inspection Performed by Other when origin inspection does not apply and inspection requirements shall be satisfied by an activity other than the ship-to activity. |
|
|
870S |
CS17 |
N |
No |
|
|
|
|
870S |
CS17 |
Y |
Yes |
|
|
|
|
870S |
CS18 |
N |
No |
|
|
|
|
870S |
CS18 |
Y |
Yes |
|
|
|
|
870S |
REF01 |
43 |
Supporting Document Number |
|
Used to perpetuate/convey a Supporting Maintenance Document Number as Necessary. The content in this field may only be meaningful to the receiver of this transaction. May be used to convey maintenance control/document numbers. |
|
|
870S |
REF01 |
86 |
Operation Number |
|
1. Use to identify the Key Operation (KO) Number associated with the JO. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. |
|
|
870S |
REF01 |
9R |
Job Order Number |
|
Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. |
|
|
870S |
REF01 |
CO |
Customer Order Number |
|
1. Use to identify the Customer Order Acceptance Record (COAR) applicable to the Job Order Number. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381 (or as applicable). |
|
|
870S |
REF01 |
FG |
Fund Identification Number |
|
Use to identify the fund purpose code. Cite any fund purpose code in REF02 except CR or DR. |
|
|
870S |
REF01 |
TN |
Transaction Reference Number |
A unique number generated by the original submitter of a pre-defined transaction and assigned to any pre-defined information exchange within the department of defense The transaction reference number retains its identity for the life of the generated transaction |
1. Must use to identify the customer assigned transaction number. , , 2. This is the document number. 3. When status is applicable to a requisition alert, this field will perpetuate the alert document number. The requisition alert is an Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. |
|
|
870S |
REF01 |
WO |
Work Order Number |
|
1. Use to identify a maintenance work order number. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 379. |
|
|
870S |
REF01 |
BDG |
Badge Number |
|
Use with local industrial activity worksite delivery status of the artisan to whom the materiel was delivered. Refer to ADC 379. |
|
|
870S |
REF01 |
PWC |
Preliminary Work Candidate Number |
|
1. Use to identify a Requisition Alert Document Number. 2. Used in support of Navy Shipyards to associate the funded requisition with a previously submitted requisition alert. 3. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. |
|
|
870S |
REF01 |
X17 |
General Terms and Conditions Identifier |
|
1. Use to identify the Fiscal Service (FS) Form 760A General Terms and Conditions (GT&C) number when taking on an order from a government customer covered by a G-Invoicing agreement. Refer to PDC 1465B. 2. DLMS enhancement; see introductory DLMS note 3a. 3. Approved for use in X12 version 8060. |
|
|
870S |
REF04-01 |
10 |
Account Managers Code |
Use to identify the authorized accounting activity (AAA)/accounting disbursing station number (ADSN)/fiscal station number (FSN) |
Use in one of REF04-03 or REF04-05 to identify the authorized accounting activity (A)/accounting disbursing station number (ADSN)/fiscal station number (FSN). |
|
|
870S |
REF04-01 |
AT |
Appropriation Number |
|
Use in one of REF04-01 or REF04-03 to identify the basic appropriation data. |
|
|
870S |
REF04-01 |
FU |
Fund Code |
Designation of the billing method (interfund or non-interfund) and the fund account to be charged (disbursed) or credited (refunded) |
Use with REF01 code FG. |
|
|
870S |
REF04-01 |
W1 |
Disposal Turn-In Document Number |
|
1. Use in conjunction with the controlling document number for the transaction cited in REF01 Code TN. 2. Use for DLA Disposition Services requisition supply status to identify the specific DTID number shipped under the controlling document number/suffix code. Authorized DLMS enhancement. Refer to ADC 45A. |
|
|
870S |
REF04-01 |
W8 |
Suffix |
Use to identify supply transaction partial actions taken on the original document without duplicating or causing loss of identity of the original document number |
1. When used in association with the Requisition Alert Document Number (Qualifier PWC, above), this will be the requisition alert document suffix. 2. The Requisition Alert Document Number Suffix is an Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. |
|
|
870S |
REF04-03 |
10 |
Account Managers Code |
Use to identify the authorized accounting activity (AAA)/accounting disbursing station number (ADSN)/fiscal station number (FSN) |
Use to identify the authorized accounting activity (A)/accounting disbursing station number (ADSN)/fiscal station number (FSN). |
|
|
870S |
REF04-03 |
60 |
Account Suffix Code |
Use to identify the Disposal turn-in document (DTID) suffix code that equates to the suffix used on the original property turn-in and retained by DLA Disposition Services for accountability and tracking |
Use in conjunction with the DTID Number (REF04 Qualifier W1) to identify the DTID Suffix Code, when , , applicable. DLMS enhancement, see ADC 466. |
|
|
870S |
REF04-03 |
AT |
Appropriation Number |
|
Use to identify the basic appropriation data. |
|
|
870S |
N101 |
C4 |
Contract Administration Office |
|
Use with Supply Status BV for direct vendor deliveries. (Refer to ADC 465). |
|
|
870S |
N101 |
GP |
Gateway Provider |
|
Use to identify Defense Automatic Addressing System (DAS) as the “TO” organization for Component-generated supply status forwarded for DAS distribution to status recipients under MILSTRIP/DLMS distribution rules (DLMS equivalent of AE8). |
|
|
870S |
N101 |
KK |
Registering Party |
|
1. Use to identify the Component UIT registry. May be used by a Component when their UIT process requires that a copy of the transaction should also be sent to a UIT registry for information purposes. Must be used with 2/N106/90 code ‘PK-Party to Receive Copy’ to identify that this is only an information copy of the transaction, for use with the Component UIT registry. Cite the applicable Routing Identifier in 2/N104. 2. Authorized DLMS enhancement for Air Force use with PIC NWRM UIT program. For PIC UIT, must use in conjunction with 2/N106 code PK and cite the applicable Routing Identifier in 2/N104. |
|
|
870S |
N101 |
PR |
Payer |
|
Use for direct vendor deliveries to identify the paying office for the related acquisition action. |
|
|
870S |
N101 |
SB |
Storage Area |
|
1. Use to identify the storage activity applicable to the status provided. 2. When implemented as a DLMS enhancement to allow specific separate identification of Owning Inventory Control Point and Storage Activity RIC for and ammunition related transactions, the storage activity may be the actual initiator of the status on behalf of the ICP identified at 1/N101/50 Code Z4 , , (N106=FR). Refer to ADC 41. |
|
|
870S |
N101 |
SH |
Shipper |
|
Use for direct vendor deliveries to identify the organization that will initiate the materiel shipment for the related acquisition action. |
|
|
870S |
N101 |
SU |
Supplier/Manufacturer |
|
Use with Supply Status BV for direct vendor deliveries to identify the contractor providing the materiel for the related acquisition order. (Refer to ADC 465). |
|
|
870S |
N101 |
UQ |
Subsequent Owner |
|
Use only on supply status subsequent to a referral order to initiate an inter-Service ammunition or ammunition-related ownership transfer with no physical movement of materiel. Use to identify the RIC to which ownership is being transferred (the New Owner RIC). DLMS enhancement. Refer to ADC 1020. |
|
|
870S |
N101 |
WD |
Storage Facility at Destination |
|
1. Use to identify the Material Processing Center (MPC). 2. When used with Status Code NY, this will identify the MPC to which materiel is transshipped. Identify the shipping MPC as the transaction originator. Refer to ADC 1279. |
|
|
870S |
N101 |
XN |
Planning/Maintenance Organization |
|
1. Used to identify a Shop Service Center/Shop Store. 2. Use in conjunction with N103 Identification Code Qualifier 92. 3. Refer to ADCs 284A, 381, and 1454 for known applications. |
|
|
870S |
N101 |
Z1 |
Party to Receive Status |
The entity to receive status for the designated document number |
Use multiple iterations to identify all status recipients. |
|
|
870S |
N101 |
Z4 |
Owning Inventory Control Point |
Use to indicate the source of supply |
Use to identify the owner/manager when implemented as a DLMS enhancement to allow specific separate identification of owner/manager and storage activity RIC for ammunition and ammunition related transactions. Refer to Approved Addendum to ADC 41A. |
|
|
870S |
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. Authorized DLMS enhancement; see introductory DLMS note 3f. Refer to ADC 109A. |
|
|
870S |
N101 |
Z8 |
Last Known Source of Supply |
|
1. Use for requisition supply status transactions to identify the supply source to which any future inquires should be addressed. 2. For intra-AF supply status for lateral movements, may be used to identify the shipping activity to which any future inquires should be addressed. Refer to ADC 407. |
|
|
870S |
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 |
|
|
|
870S |
N103 |
33 |
Commercial and Government Entity (CAGE) |
|
Use with Supply Status BV for direct vendor delivery 2/N1/090 supplier (Code SU) to identify the contractor providing the materiel. |
|
|
870S |
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. |