|
|
824R |
REF01 |
WL |
Federal Supply Classification Code |
Use to identify the supply classification of an item of supply identified under the federal cataloging program, an item of production and/or a homogeneous area of commodities in respect to their physical or performance characteristics. The first two digits identify the federal supply group and the last two digits identify the specific class within the specified group |
1. Use for nonstandard materiel when used in the transaction being rejected. Use REF03 to provide the appropriate description.
2. DLMS enhancement; see introductory DLMS note 6a. |
4/4 |
|
|
824R |
REF01 |
X7 |
Batch Sequence Number |
Identifies the batch control number assigned to each batch of transactions forwarded to a single activity for validation |
Use to identify the batch control number from the beginning segment of the transaction being rejected, when DLMS 517M is being rejected. |
1/30 |
|
|
824R |
REF01 |
XD |
Subsistence Identification Number |
Use to identify a brand name resale subsistence item |
Use to identify subsistence items when used in the transaction being rejected. |
15/15 |
|
|
824R |
REF01 |
ZZ |
Mutually Defined |
|
1. Use to identify nonstandard materiel when all other authorized codes do not apply or cannot be determined (includes management control numbers and locally assigned control numbers) when used in the transaction being rejected.
2. DLMS enhancement; see introductory DLMS note 6a. |
|
|
|
824R |
REF01 |
ACC |
Status |
Use to identify the current state, i.e. availability, condition, or progress |
Use to identify the Status Report Code (Data Element 850) from the Beginning Segment of the transaction being rejected, when applicable. A data maintenance action was approved in version 5050. The approved code/name is "X11 – Status Report Code ". |
|
|
|
824R |
REF01 |
PRT |
Product Type |
Use to identify the Schedule Type Qualifier |
Use to identify the Schedule Type Qualifier (Data Element 675) from the Beginning Segment of the transaction being rejected, when applicable. A data maintenance action was approved in version 5040. The approved code/name is "XX7 - Schedule Type Code". |
1/30 |
|
|
824R |
REF02 |
|
|
|
|
|
|
|
824R |
REF03 |
|
|
|
|
|
|
|
824R |
REF04 |
|
|
|
|
|
|
|
824R |
REF04-01 |
OQ |
Order Number |
Use to identify the legacy four-position call/order number associated with the PIIN or Contract Line Item Number (CLIN) |
1. Use to identify the legacy four position call/order number associated with the CLIN in 2/REF01/020 Code C7.
2. Do not use for the PIID call/order number. The PIID call/order number is mapped to OTI02 Code CT. Refer to ADC 1161. |
4/4 |
|
|
824R |
REF04-01 |
W7 |
Commercial and Government Entity (CAGE) Code |
Code assigned to establishments which either fabricates items of production and/or have design control of items procured by the federal government, or to identify certain military specifications or standards, and certain numbering systems developed by government agencies, panels or committees |
1. Use with REF01 code MF to uniquely identify the manufacturer's part number when cited in the transaction being rejected.
2. Authorized DLMS enhancement; see introductory DLMS note 6e. |
5/5 |
|
|
824R |
REF04-02 |
|
|
|
|
|
|
|
824R |
DTM01 |
097 |
Transaction Creation |
Use to identify the date of transaction preparation |
|
8/8 |
|
|
824R |
DTM02 |
|
|
|
|
|
|
|
824R |
DTM03 |
|
|
|
|
|
|
|
824R |
NM101 |
Z4 |
Owning Inventory Control Point |
Use to indicate the source of supply |
For use with 2/LQ01/086 qualifier ET (Reject Advice Code), code value ‘AB’ (Rejected, submitted to incorrect manager), to identify the correct manager. |
1/60 |
|
|
824R |
NM102 |
6 |
Organization |
|
|
|
|
|
824R |
NM108 |
10 |
Department of Defense Activity Address Code (DODAAC) |
Use to identify specific units, activities, and/or organizations |
DLMS enhancement; See introductory DLMS note 6a. |
6/6 |
|
|
824R |
NM108 |
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 |
|
3/3 |
|
|
824R |
NM109 |
|
|
|
|
|
|
|
824R |
TED01 |
848 |
Incorrect Data |
Use to indicate that specific reject advice |
Use to indicate that specific reject advice is conveyed under 2/LQ01/086. Qualifier ET. |
2/2 |
|
|
824R |
TED01 |
OTH |
Other |
Use to provide narrative message reject information from DAAS |
1. DLA Transaction Services uses to provide narrative message reject information. Use with the 2/NTE/080 segment
2. DLMS enhancement. See introductory DLMS note 6a. |
1/80 |
|
|
824R |
TED02 |
|
|
|
|
|
|
|
824R |
TED07 |
|
|
|
|
|
|
|
824R |
NTE01 |
OTH |
Other Instructions |
Use to provide other instructions |
|
1/2000 |
|
|
824R |
NTE02 |
|
|
|
|
|
|
|
824R |
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. |
|
|
|
|
824R |
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 DLSS DIC is retained in the DLMS to facilitate transaction conversion in a mixed DLSS/DLMS environment. Continued support of the DIC in a full DLMS environment will be assessed at a future date.
2. The DIC is not to be applicable to every rejection transaction.
3. May use 2 iterations of LQ01 code 0 when the rejected transaction contained an LQ01 code 0. Use one iteration with LQ02 code value DZG, when applicable, to represent DLMS 824R equated to MILSTRAP DIC DZG in a mixed DLSS/DLMS environment. Use another iteration of LQ01 code 0 with the code value from the transaction being rejected when applicable.
4. Future Streamlined data; See introductory DLMS note 6c. |
3/3 |
|
|
824R |
LQ01 |
ET |
Reject Advice Code |
Identifies to the originator of a transaction the reason for rejection and indicates return of the transaction for correction and resubmission |
Use to identify reason original transaction was rejected. |
2/2 |
|
|
824R |
LQ02 |
|
|
|
|
|
|
|
824R |
SE01 |
|
|
|
|
|
|
|
824R |
SE02 |
|
|
|
|
|
|
|
830D |
ST01 |
830 |
Planning Schedule with Release Capability |
Use a single occurrence of this transaction set to transmit Demand Data Exchange (DDE) Projected Supply Plan transactions to one or more Inventory Control Points (ICPs)/Integrated Material Managers (IMMs). At this time, DDE Projected Supply Plans are only submitted to the Defense Logistics Agency (DLA) ICP/IMM.” Use one occurrence of this transaction set to transmit a single or multiple transactions. DoD logistics users should refer to the Defense Logistics Management Standards (DLMS) Implementation Convention (IC) available at URL: www.dla.mil/does/DLMS. The DLMS IC provides specific business rules, conditions, and authorized codes necessary for appropriate use of this IC within the DLMS. |
|
|
|
|
830D |
ST02 |
|
|
|
|
|
|
|
830D |
ST03 |
|
|
|
|
|
|
|
830D |
BFR01 |
00 |
Original |
Indicates the initial transaction |
|
|
|
|
830D |
BFR01 |
77 |
Simulation Exercise |
Use to identify a simulated mobilization exercise transaction set |
Activities initiating simulated mobilization exercises must ensure complete coordination with all activities involved. All transaction set recipients must use caution to ensure that transactions do not process as action documents which affect accountable records. |
|
|
|
830D |
BFR02 |
|
|
|
|
|
|
|
830D |
BFR04 |
PR |
Planned Requirement Based |
|
Use to indicate that data reflect DDE Projected Supply Plan requirements. |
|
|
|
830D |
BFR05 |
A |
Actual Discrete Quantities |
|
Use to indicate that quantities reflect discrete requirements. |
|
|
|
830D |
BFR06 |
|
|
|
|
|
|
|
830D |
BFR07 |
|
|
|
|
|
|
|
830D |
BFR08 |
|
|
|
|
|
|
|
830D |
BFR12 |
AA |
Customized Ordering Forecast |
|
Must use to indicate the transaction is a DDE Projected Supply Plan. |
|
|
|
830D |
BFR13 |
FI |
File |
|
Authorized only for DAAS use to provide an information only image of the demand data exchange projected supply plan transaction to DLA RIC-TO SMS when DLA is not the source of supply. |
|
|
|
830D |
N101 |
41 |
Submitter |
Use to identify participating activity which submits proposed data directly to the DLA logistics information service for approval. The submitting activity may be the activity which originates the data, or an intermediate monitoring activity, e.g., DLA supply center, defense atomic support agency, through which the originating activity is required to submit its proposals to DLA logistics information service |
Must use to identify the submitter of the DDE requirement. |
|
|
|
830D |
N103 |
10 |
Department of Defense Activity Address Code (DODAAC) |
Use to identify specific units, activities, and/or organizations |
Use to identify the submitter. |
6/6 |
|
|
830D |
N104 |
|
|
|
|
|
|
|
830D |
N106 |
FR |
Message From |
Use to identify the party originating the transaction set |
Must use to indicate the organization cited in N104 is originating the transaction set. |
1/60 |
|
|
830D |
LIN01 |
|
|
|
|
|