ENCLOSURE 3 TO ADC 333

Revision to DLMS, Volume 2, Chapter for Logistics Asset Support Estimate (LASE); and
Administrative Updates to DLMS 846L, 870L, LASE Request Codes and Reject Advice Codes

APPENDIX AP2.14

REQUEST CODES
(LOGISTICS ASSET SUPPORT ESTIMATE (LASE) REQUESTS)

NUMBER OF CHARACTERS: One

TYPE OF CODE: Alphabetic

EXPLANATION: Identifies the type of data requested and furnished.
MILSTRAP RECORD POSITION: 7

DLMS SEGMENT/QUALIFIER: — 2/LQ/270 segment, LQO1 Data Element ID 1270
Qualifier ‘EU — Request Code’

CODE EXPLANATION

A Request for Asset data. Input of this code results in output of DI Code DTB.

B Request for Backorder data. Input of this code results in output of DI Code DTC.

Cc Request for both Asset and Backorder data. Input of this code results in output of both
DI Codes DTB and DTC.

J Output by IMM in response to a follow-up which contained Request Code A.

K Output by IMM in response to a follow-up which contained Request Code B.

L Output by IMM in response to a follow-up which contained Request Code C.

AP2.14-1
ADC 333
Enclosure 3


ARMY

Submission Authorized Submission Authorized
Routing Activity Routing Activity
Identifier DoDAAC Identifier DoDAAC
Al2 W58HZ1 B16 W80YBX
A35 W25PVR B16 W80YBY
AKZ WS6HZV B17 WS58H0Z
AKZ W56KXS B29 W62G2W
AKZ W80KTY B40. WI6GIA
APS W25LMQ B46 W73HYT
B1O W52G2J BSO W45N7V
B14 W52H09 B64 W31G3H
B14 WS81YWB - B69 W23MWR
B16 W15GK8 BAO. W31G1Y
B16 WIS5P61 BGO. W22L11
B16 WI15P62 BKO W25G1Q
B16 WI5P66 BLO W22G1F
B16 WI5P7U BRO W45G18
B16 WISP86 BTO W67G22
B16 WISQPC BYO W25GIV
B16 W80KQR BY7 W25P02
B16 W80SLL C17 WK4NP7
B16 W80YBO W82 W23RYX

$ The DoD Component Supply PRC/MILSTRAP representatives are responsible for ensuring information
listed is kept current by sending changes to the Supp/y PRC MILSTRAP Administrator as they occur.

C24-6
ADC 333 Enclosure 1
DLMS Chapter 24-LASE


CORRELATION OF MILSTRAP DOCUMENT IDENTIFIER (DI) CODE
FUNCTIONALITY TO DLMS SUPPLEMENTS (DS)

DS# DLMS Supplement Title DI Code(s) | DS Accredited Standards Committee (ASC) X12
Functional Equivalent to MILSTRAP DI Code
Beginning Segment | Additional Information needed
846L Logistics Assets Support Estimate | DTA 1/BIA02/020 None.
(LASE) Asset Support Request Report Type Code
TA — Asset Si rt
When used to Use to Identify a Tig a MPPOF
LASE request.
846L Logistics Assets Support Estimate | DTB 1/B1A02/020 2/QTYO1/320 identifies type of
(LASE) Asset Support Request Report Type Code information being provided (On-
. " TB — Asset Support hand, due-in, backorder, etc)
When used to identify a LASE Advi
iVICe
response.
846L, Logistics Assets Support Estimate | DTC 1/BIA02/020 2/QTY01/320 identifies type of
(LASE) Asset Support Request Report Type Code information being provided (On-
TB — Asset Support hand, due-in, backorder, ete’
When used to identify a LASE sae and’, eue=In, DaeKor )
response.
NONE NONE DTD NONE. DI Code DTD was eliminated from DLMS by
intent. In DLMS, authorized activities send new DS 846L
LASE request (DI Code DTA functionality) rather than
follow up.
870L Special Program Requirements | DYK 1/BSRO1/020 None.
(SPR) Status; or SPR/ Logistics Status Report Code 9 —
2 ‘ gift Response to a
Asset Support Estimate (LASE) Requirement Forecast
Notification SPR-LASE-Status
When used to provide SPR status,
(ICPAMM uses to provide SPR
status to an SPR forecasting
activity.)
4o0f7

ADC 333
Attachment



ENCLOSURE 2 TO ADC 333

Revision to DLMS, Volume 2, Chapter for Logistics Asset Support Estimate (LASE); and
Administrative Updates to DLMS 846L, 870L, LASE Request Codes and Reject Advice Codes

AP2.8 APPENDIX 2.8
REJECT ADVICE CODES

NUMBER OF CHARACTERS: Two
TYPE OF CODE: Alphabetic

EXPLANATION: Identifies to the originator of a transaction, the
reason for rejection, and indicates return of the
transaction for correction and resubmission."

MILSTRAP RECORD POSITION: 79-80

DLMS SEGMENT/QUALIFIER: LQ segment, LQO1 Data Element ID 1270
Qualifier ‘ET — Reject Advice Code ’

CODE EXPLANATION

AA Rejected. Document identifier code invalid.

AB Rejected. Submitted to incorrect manager; routing identifier code of correct manager
indicated if known. (When known, incorrect manager is identified in MILSTRAP
record positions 54-56 or appropriate DLMS segment)

AC Rejected. Type of physical inventory code invalid or blank.
AD Rejected. Stock or part number unidentifiable.

AE Rejected. Quantity field invalid.

AF Rejected. Document number invalid.

AG Rejected. Ship-to address unidentifiable.

AH Rejected. Required signal code invalid or blank.

4 Codes in the A_ and B_ series not listed above are reserved for future use and are not to be
used unless authorized and disseminated by the DoD MILSTRAP System Administrator. Codes
in the C through Z series are reserved for intra-Component use.

AP2.8-1
ADC 333
Enclosure 2


C24.1.3.1.2. LASE Response Transaction is DS 846L identified by Report
Type Code TB - Asset Support Advice. IMMs use this transaction to respond to LASE
requests. This transaction provides MILSTRAP DI Codes DTB and DTC functionality.

€24.1.3.1.3. MILSTRAP DI Code DTD, LASE Follow-up, is eliminated from
DLMS by intent. Under DLMS, authorized activities send new LASE Request Transactions
rather than follow-up.

C24.1.3.2. DS to Federal IC 870L, Special Program Requirements (SPR) Status;
or SPR/LASE Notification. DS 870L only applies to this chapter when it is used as a Status
Notification Transaction. DS 870L Status Notification Transaction is identified by beginning
segment (I/BSRO1/20) Status Report Code 3 — Unsolicited Report. DAASC uses the Status
Notification Transaction to notify the submitter that a LASE (or SPR) transaction was
rerouted or the Federal Supply Class (FSC) has changed. This transaction provides
MILSTRAP DI Code DZ9 functionality.

24.2. LASE REQUEST

24.2.1. Authorized Activities. Only the authorized activities listed in section paragraph
24.8. may submit LASE Request Transactions to IMMs. All authorized activities do not
qualify for assignment of a routing identifier (RI) code. However, the activity address,
DoDAAG, and the RI Code which each activity shall use to submit request are identified in
section C24.8. IMMs shall validate she RI Code (from) and the DoDAAC of incoming requests
and reject those with invalid or unauthorized entries as prescribed in paragraph C24.3.5.

24.2.2, Data Requirement Determination. Authorized activities shall determine the type
of logistic data required and shall send LASE Requests Transactions ¥sing-DS-8465 citing the
appropriate LASE request code applicable to the type of asset information required. The LASE
request code shall determine if asset data will be for issuable on-hand and due-in assets,
backorder, or both asset and backorder availability.

24.3. LASE RESPONSE. MMs shall do the following in response to LASE Request
Transactions: inevivies:

24.3.1. Prepare LASE Response Transactions #si#g-DS-846£ containing the data
specified by the submitting activity.

C24,3.1.1. For IMMs operating under DLMS, a single LASE Response
Transaction shall provide the data requested, whether it be asset data, backorder data, or both.

24.3.1.2.. For IMMs still operating under MILSTRAP, the constraints of the 80-
record position transactions dictate that two separate LASE Reply Transactions may be
required, one for LASE replies providing asset data (DI Code DTB) and one for LASE replies
providing backorder data (DI Code DTC).

C24,3.2. Normally respond to LASE requests inquiries within 5 working days after receipt
and, in all instances, must respond within 10 working days.

C24-2
ADC 333 Enclosure |
DLMS Chapter 24-LASE


Item Location Revision to DS 846L Reason Federal

# IC
Impact
3 DLMS Revise DLMS introductory note 5 to add ADC 333: Identifies DLMS No
Introductory Changes included in | impact.
Notes - ADC 333, Revision to DLMS, Volume 2, Chapter for | the DS.

Logistics Asset Support Estimate (LASE); and
Administrative Updates to DLMS 846L, 870L, LASE
Request Codes and Reject Advice Codes

(Supply/MILSTRAP).
4 1/BIA02/020 | Revise DLMS notes for Report Type Codes: Administrative No
update to show impact.
TA Asset Support Inquiry MILSTRAP DI Code

DLMS Note: Use to identify a Logistics Asset Support | correlation to the
Estimate (LASE) request. Authorized activities use to | beginning segment

request LASE from ICPs/IMMs, (MILSTRAP DI Report Type Code,
Code DTA functionality) consistent with other

MILSTRAP related
TB Asset Support Advice DS.

DLMS Note: Use to identify a LASE response.
IMMS/ICPs use to provide a LASE response to the
appropriate Component activity. (MILSTRAP DI
Code DTB and DTC functionality)

5 2/REF01/140 | Add a DLMS note to qualifier TN: Administrative No
update to clearly impact.
TN Transaction Reference Number state that the DLMS
transaction number is
DLMS Note: Use to identify the transaction number. the document
This is the document number, number,

(6) Administrative updates to DS 870L:

ion Revision to ]

Revise DS title FROM: “Special Program Requirements | To more accurately Revision
(SPR)/Logistics Asset Support Estimate (LASE) Status” | reflect transaction Required.
TO: “Special Program Requirements (SPR) Status; use. Previous title

or SPR/ Logistics Asset Support Estimate (LASE) implied LASE status

Notification” was provided by
870L, however LASE
status is provided by
846L. SPR Status is
provided by 870L.

6 of7
ADC 333
Attachment


CORRELATION OF MILSTRAP DOCUMENT IDENTIFIER (DI) CODE
FUNCTIONALITY TO DLMS SUPPLEMENTS (DS)
DS# DLMS Supplement Title DI Code(s) | DS Accredited Standards Committee (ASC) X12
Functional Equivalent to MILSTRAP DI Code
Beginning Segment | Additional Information needed
870L Special Program Requirements | DZ9 1/BSRO1/020 None.
(SPR) Status; or SPR/ Logistics Sie Ree Code 3—
Asset Support Estimate (LASE) SSI Neon
Notification SPR-LASE-Status
When used to provide Status
Notification. (DAASC uses status
notification to notify the
submitter that an SPR or LASE
transaction was rerouted or that
the FSC changed.)
(5) Make administrative updates to DS 846L:
Item Location Revision to DS 846L Reason Federal
# IC
Impact
1 Title Revise DS title FROM “Logistics Asset Support Administrative Revision
Request” TO: “Logistics Asset Support Estimate update to clearly required
(LASE)” associate DS 846L
with the LASE
process. Also, DS
846L is used for both
the request and the
response. Previous
title implied
transaction was only
for the request.

2 DLMS Revise DLMS introductory note 1: Administrative No
Introductor a . ‘ it update to document in | j q
Notes ory da, Organizations use This transaction set to inquire about fhe Sahat DI Code impact

material availability for support of contingency operations, | DPD fynctionality was
special projects, or other operational requirements. eliminated from
Integrated Material Managers (IMMs)/Inventory Control DLMS by intent in
Points (ICPs), use this transaction set to respond to favor of submitting a
material availability inquiries. This transaction new LASE re

+ "i quest.
encompasses the functionality of MILSTRAP Document
Identifier (DI) Codes DTA, DTB, and DTC. MILSTRAP
DI Code DTD (LASE Follow-up) was eliminated from
DLMS by intent. In DLMS, a new LASE request
transaction is submitted rather than a follow-up.

5 of 7
ADC 333

Attachment



CODE
AJ
AK
AM
AP
AQ

AR
AS

AT
AU

AV

AW

AX

AY

EXPLANATION

Rejected. Required fund code invalid or blank.
Rejected. Ownership/purpose code invalid or blank.
Rejected. Supply condition code invalid or blank.
Rejected. Required management code invalid or blank.

Rejected. Processing/count date invalid or blank. Location Reconciliation Request
cutoff date invalid.

Rejected. Unit of issue incorrect.

Rejected. Support date invalid. Location Reconciliation Request and/or Transaction
History Transmittal received past scheduled deadline.

Rejected. Logistics Asset Support Estimate (LASE) request code invalid or blank.

Rejected. Assetsupport LASE request is for an item not centrally managed and
stocked (Acquisition Advice Codes F, L, P, or W).

Rejected. Activity identified in record positions 30-35 (DoDAAC) and/or 27-29 (RI
code (From)) is not authorized to submit LASE transactions. Activity identified in
Location Reconciliation Request record positions 67-69 (RI Code (From)) not valid.

Rejected. Logistic Reassignment Transaction (DEE, DEF, DDX) received more than
1 year after the ETD. (The D4X will be rejected if no memorandum due-in is on
record at the GIM to indicate it is a valid procurement receipt.)

Rejected. GSA is SOS for requested LASE or SPR. GSA does not participate in
MILSTRAP LASE and SPR procedures. If required, submit funded DoD MILSTRIP
requisition citing applicable required delivery date.

Rejected. Location Reconciliation Request and/or Transaction History Transmittal
does not equal the number of transactions recorded in the Location Reconciliation
Notification and/or Location Reconciliation History Notification.

Rejected. Number of Location Reconciliation Requests received from storage
activity exceed reasonable variance from owner/manager.

AP2.8-2
ADC 333
Enclosure 2


ENCLOSURE 1 TO ADC 333

Reyision to DLMS, Volume 2, Chapter for Logistics Asset Support Estimate (LASE); and
Administrative Updates to DLMS 846L, 870L, LASE Request Codes and Reject Advice Codes

C24. CHAPTER 24
LOGISTICS ASSET SUPPORT ESTIMATE

ADC 333 NOTE: Content changes from current DLMS LASE procedures (Vol 2, chapter 5) are
identified by bold, red, italics, Some of these changes pick up MILSTRAP language that was missing
from the DLMS chapter

24.1, GENERAL

24.1.1. Purpose. This chapter prescribes an automated procedure for authorized
activities of the DoD Components to determine the ability of the Integrated Materiel Managers
(IMMs) to support contingency or operational plans, projects, and other important programs.
This program is not intended for routine supply status stock inquiries as-deseribed-ebove where
normal MILSTRIP/DLMS should be employed. Rather, this program is to get a general
estimate of the type of supply support that might be anticipated when a specific requisition is not
pertinent to the inquiry. Personnel responsible for scheduling, planning, or reporting on the
overall supply support status of major equipment or systems, shall initiate LASE inquires
Request Transactions in conjunction with particular programs or projects.

24.1.2. Applicability. The provisions of this section are applicable to DLA, Defense
Supply Centers (DSCs) except the Defense Fuel Supply Center, Component Inventory Control
Points (ICPs) functioning as IMMs, and authorized wholesale and below wholesale activities of
the Army, Navy, Air Force, Marine Corps, and Coast Guard.

24.1.3. Transactions, This chapter addresses the procedures to DS to ASC X12 Federal
IC 846L and 870L (when used to provide Status Notification) functions identified by their
beginning segment report type code (846L-1/BIA02/20), or status report code (870L-
1/BSRO1/20), respectively; and their DLSS (MILSTRAP) counterparts identified by their
document identifier (DI) codes (DI Codes DTA, DTB, DTC, and DZ9). Both DLMS and DLSS
are covered to allow for processing in a mixed DLMS/DLSS environment. Other formats, such
as XML, are also available. See the DLMSO website for available DLMS and DLSS formats:
http:/Avww.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp.

C24.1.3.1. DS to Federal IC 846L, LASE identified by beginning segment report
type code (1/BIA02/20).

C24.1.3.1.1, LASE Request Transaction is DS 846L identified by Report Type
Code TA - Asset Support Inquiry. Authorized activities use this transaction to submit LASE
requests to IMMs. This transaction provides MILSTRAP DI Code DTA functionality.

C24-1
ADC 333 Enclosure 1
DLMS Chapter 24-LASE


DEFENSE LOGISTICS AGENCY
HEADQUARTERS
8725 JOHN J. KINGMAN ROAD
FORT BELVOIR, VIRGINIA 22060-6221

INREPLY — DLMSO August 5, 2009

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (SPRC)

SUBJECT: Approved Defense Logistics Management System (DLMS) Change (ADC) 333,
Revision to DLMS, Volume 2, Chapter for Logistics Asset Support Estimate
(LASE); and Administrative Updates to DLMS 846L, 870L, LASE Request
Codes and Reject Advice Codes (Supply/MILSTRAP) (Staffed as PDC 355)

The attached changes to DOD 4000.25-M, DLMS, and DoD 4000.25-2-M,
MILSTRAP, are approved. The updated DLMS Supplements will be posted to the
Defense Logistics Management Standards Office (DLMSO) Web site
http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/formats.asp within 10 days from the
above date for implementation planning. Changes to DLMS and MILSTRAP will be
published in the next reissuance of the manuals.

Addressees may direct questions to the DLMSO point of contact, Ms. Mary Jane

Johnson, 703-767-0677; DSN 427-0677; or, e-mail: Mary.Jane.Johnson@dla.mil. Others
must contact their Component designated SPRC representative.

DONALD C., PIPP

Director
Defense Logistics Management
Standards Office

Attachment

ce:

DUSD(L&MR)SCI


authorized activity is collocated with the IMM, the DI Code DTD LASE Follow-up may be
submitted directly to the appropriate office.

24.4.2.2.2. IMM Processing of Follow-Up. The IMM shall process the
MILSTRAP LASE follow-up (DI Code DTD) as a LASE request as outlined in section C24.3.
The record position 7 request code will be changed from code A, B, or C to code J, K, or L,
respectively. Codes J, K, and L will indicate to the submitting MILSTRAP activity that replies
are in response to a follow-up and not to an initial request.

iainiocone Se saitcineiaecee netinenns

PDC STAFFING NOTE: ; SECTIONS HIGHLIGHTED in blue directly above (and with strike-through)
ARE REPLACED WITH THE FOLLOWING, CONSISTENT WITH COMPARABLE CHANGES
IDENTIFIED IN ADC 287 FOR THE SPR PROCESS. DAASC FSC/NIIN EDIT PROCESS IS THE SAME
FOR LASE AND SPR, AND IS THE SAME AS THE PROCESS CURRENTLY IDENTIFIED IN
MILSTRAP CHAPTER 9.

24.5. DEFENSE AUTOMATIC ADDRESSING SYSTEM CENTER (DAASC) PROCESSING
for LASE REQUEST TRANSAC: TIONS.' Upon receipt of the LASE Request Transactions (and
under MILSTRAP only, LASE DI Code DTD Follow-up Transactions), DAASC shall edit the
National Stock Number (NSN) of the incoming transaction. This edit shall determine if the
National Item Identification Number (NIIN) can be identified, if the Federal Supply Class (FSC)
is compatible with the NIIN, and if the transaction is directed to the correct Source of Supply
(SOS). DAASC shall pass the transaction, reject the transaction, or effect necessary changes to
process the transaction and provide appropriate DS 870L Status Notification Transactions or DS
to Federal IC 824R Reject Advice Transactions to the submitter as follows:

24.5.1. If the NIN is valid (including NIINs coded obsolete/inactive) but the FSC and
NIIN are not compatible, DAASC shall correct the FSC and provide a Status Notification
Transaction to the submitter. DAASC shall prepare the notification whenever DAASC
corrects the FSC that was provided in the incoming transaction. DAASC shall cite the correct
FSC and Status Code BG in the Status Notification Transaction.

24.5.2. If the NIIN is valid (including NIINs coded obsolete/inactive), screen the SOS
file Service record (or IMM record when the Service record source is either another DoD

' DAASC provides routing to the correct SOS for two categories of MILSTRAP related DLMS
transactions: LASE Request Transactions and Special Program Requirements (SPR)
Transactions. This chapter specifies the DAASC processing for LASE Request Transactions,
which mirrors the DAASC process for SPR transactions

24-4
ADC 333 Enclosure |
DLMS Chapter 24-LASE


24.3.3. When receiving a LASE Request Transaction inquiry on a non-preference item,
the IMM may provide data for the replacing preferred item. When this option is exercised, the
LASE response will cite the replacing preferred item.

24.3.4. Use data contained in each LASE response for review and control. IMMs shall
retain this data for at least 90 calendar days and then destroy.

24.3.5. IMM Validation and Rejection. IMMs shall reject LASE Request Transactions
inquiries using DS to Federal IC 824R Reject Advice Transactions citing the appropriate reject
advice or DLMS/MILSTRIP status code as follows:

€24,3.5.1, YMMs shall validate the requesting activity’s RI code and DoDAAC in all
LASE requests. IMMs shall reject LASE requests containing an RI code and/or a DoDAAC not
authorized in section C24.8., using a Reject Advice Transaction citing Reject Advice Code AV.
IMMs shall reject requests containing an invalid DoDAAC using a Reject Advice Transaction
citing Reject Advice Code AF.

C24,3.5.2. IMMs shall send Fransmit a Reject Advice Transaction for LASE
inquiries received for an obsolete/inactive NSN that the IMM cannot support citing
DLMS/MILSTRIP Status Code CJ.

€24,3.5.3. IMMs shall send Fransmit a Reject Advice Transaction for LASE
inquiries received for an item that is not centrally managed and stocked citing Reject Advice
Code AU.

24.4. NONRESPONSE TO LASE REQUEST Inquiries. When the authorized activity has
not received a response to their LASE request inguiry within 15 calendar days from the
submission date:

C24.4.1. Authorized activities operating under DLMS may resubmit the LASE Request
Transaction.

C24.4.2, LASE Follow-Up (eliminated under DLMS):

C24.4.2.1, Under DLMS, the LASE Follow-Up was eliminated by intent. Under
DLMS, authorized activities send new LASE Request Transactions rather than follow up.

C24.4.2.2. Under MILSTRAP, authorized activities operating under MILSTRAP
may send a LASE follow-up (DI Code DTD): [ADC STAFFING NOTE: The language in section
C24,4,2.2, while new to the DLMS chapter, is pulled directly from MILSTRAP Chapter 14 LASE
procedures, The MILSTRAP LASE follow-up procedure is not being changed by this ADC]

C24.4.2.2.1. Authorized activities. Authorized activities operating under
MILSTRAP may send a LASE follow-up (DI Code DTD) in accordance with subparagraph
C24.2.2., through DAAS for routing using Content Indicator Code IAZZ. DAASC will
recognize DI Code DTD and place Content Indicator Code IHAC in the header of the
transmitting message upon passing or routing the request to the appropriate IMM. When the

C24-3
ADC 333 Enclosure 1
DLMS Chapter 24-LASE


2. DLMS Added ADC 333 to DLMS Introductory note 5: To identify changes lo
Introductory in the DLMS impact.
Note 5 - ADC 333, Revision to DLMS, Volume 2, Chapter for Supplements
Logistics Asset Support Estimate (LASE); and
Administrative Updates to DLMS 846L, 870L, LASE
Request Codes and Reject Advice Codes
(Supply/MILSTRAP).
3. 2/REF01/87 | Add a DLMS note to qualifier TN: Administrative No
update to clarify that | impact.
TN Transaction Reference Number the DLMS
transaction number is
DLMS Note: Must use to identify the customer the document
assigned transaction number. This is the document number.
number,

5. REASON FOR CHANGE:

a. Administrative update to DLMS Volume 2, to position the LASE chapter for a future combined
MILSTRAP/DLMS manual.

b. Revisions to DLMS LASE chapter to remove erroneous FSC/NIIN edit procedures which conflict
with MILSTRAP guidance.

ce. Administrative updates to MILSTRAP appendices AP2.8 Reject Advice Codes and AP 2.14 LASE
Codes, and corresponding DLMS Data Dictionary.

d, Administrative updates to DS 846L and 870L to clearly identify beginning segment transaction in the
context of the applicable DLMS chapter explanation, and corresponding MILSTRAP DI Code functionality.

6. ADVANTAGES and DISADVANTAGES:
a, ADVANTAGES:

(1) Removes a conflict between the MILSTRAP and DLMS procedures for FSC/NIIN edit in
favor of the established MILSTRAP procedure.

(2) Identifies in the DLMS LASE chapter, the correlation between MILSTRAP DI Codes and
associated DLMS transactions. This information is useful ina mixed DLSS/DLMS environment and
positions the LASE chapter for publication in a future combined DLMS/MILSTRAP manual.

b. DISADVANTAGES: None.

7. IMPACT: Publication revision to DOD 4000.25-M, Volume 2; DS 846L and 870L, MILSTRAP
Appendix AP2.14, and DLMS Data Dictionary.

Enclosure

Tof7
ADC 333
Attachment


ec. Procedures:

(1) Revise DoD 4000.25-M, DLMS, Volume 2, Chapter 24 LASE procedures The LASE
procedures are currently published in DLMS Vol 2, chapter 5 (Status Reporting), along with Supply
Status and Shipment Status procedures, however, this approved change establishes LASE as a separate
chapter 24. Revise DLMS, Volume 2, to:

(a) Revise chapter 5, Status Reporting, to remove Section C5.3. Logistics Asset Support
Estimate. [NOTE: Chapter 5, section C5.1, Asset Status, was previously removed from chapter 5 by
ADC 308, which will be published in the reissuance of the DLMS manual.]

(b) Establish new DLMS, Volume 2, chapter 24 for LASE as shown at Enclosure 1.
NOTE: DLMS, Volume 2 chapter 24 is currently used for Passive Radio Frequency Identification
(pRFID), however the pRFID chapter will be moved to new volume in the reissuance of the DLMS
manual, leaving chapter 24 not used. The new LASE chapter 24 includes:

[1] LASE procedures formerly published by DLMS, Vol 2, chapter 5, section C5.3.

[2] Administrative updates to the LASE procedures to incorporate a correlation
between the DLMS 846L beginning segment Report Type Codes and the DLMS 870L beginning
segment Status Report Codes, with the corresponding MILSTRAP DI Codes. This provides
information beneficial in a mixed Defense Logistics Standard System (DLSS) (aka MILS) -
DLMS environment; facilitates format neutral procedures; and positions the chapter for the
initiative to combine the MILSTRAP manual with the DLMS manual. To that end, the new
chapter also incorporates functional procedures from MILSTRAP, which are currently absent in
the DLMS chapter.

[3] Administrative updates to DAASC processing to bring the DLMS procedures in
line with the corresponding MILSTRAP procedural requirement and the existing LASE process.
The current DLMS guidance for editing the NSN field of SPR transactions for FSC/NIIN
compatibility conflicts with the MILSTRAP chapter 9 guidance. This update removes the
disconnect between the MILSTRAP and DLMS procedures as noted in description of change.

(2) Revise MILSTRAP Appendix AP2.8, Reject Advice Codes, and corresponding
DLMS Data Dictionary, to provide administrative updates as shown in Enclosure 2.

(3) Revise MILSTRAP Appendix AP2.14 request codes, and corresponding
DLMS Data Dictionary, to change the code list name from “Request Codes (Asset Support
Requests)” to “Request Codes (Logistics Asset Support Estimate (LASE)) and provide
administrative updates as shown in Enclosure 3.

(4) Revise the Table for Correlation of MILSTRAP Document Identifier (DI) Code
Functionality to DLMS Supplements (DS) (in DLMS sequence) , to capture the varied transaction
names/ purpose associated with the beginning segment Report Type Codes (table is available at:
http://www.dla.mil/j-6/dlmso/eA pplications/LogDataAdmin/dlssdlmscrossreftable.asp):

3 of 7
ADC 333
Attachment


NAVY

Submission Authorized Submission Authorized
Routing Activity Routing Activity
Identifier DoDAAC Identifier DoDAAC
N2L NO00019 P58 NO0197
N22 00023 P61 N00446
N23 N00024 P64 NO00164
N25 'N00025 P65 N60478
N32 'N00383 P71 N60701
N35 NO0104 P72 NO00109
N47 N00367 P73 00253
N77 'NO00039 P83 53825
N79 NO0708A, PGZ NO00311
N87 V57016 PIZ 00207
NAZ N68860 PPZ N00204
NDZ 00244 PTZ NO0146
NHZ N00102 Q32 NOO191
NIZ NOOIS1 Q6A N65885
NKZ NOO181 Q6C N65923
NNZ NO0189 Q65 N65886
NOZ N00228 Q6N N65887
NQZ N00221 Q6P N65889
NRZ NO00612 Q6S N65888
NUZ N00406 R22 N65584
NWZ N00251 R24 N65580
P14 NO00163 R34 N60258
R41 'N00249
C24-7

ADC 333 Enclosure 1
DLMS Chapter 24-LASE


MARINE CORPS

Submission Authorized Submission Authorized
Routing Activity Routing Activity
Identifier DoDAAC Identifier DoDAAC
MBB M93728 MRI MMR100
MCI MMC100 Q4L, RS7079
ML3 MML100 Q4M 57080
MPB M98820 Q4N RS7081
DEFENSE-LOGISTICS- AGENCY
Sith Avsth f Submissi: Aueth {
Rotting Activity Routing sail
Identifi DoDAAG. Kedentifi DoDAAC
SoC SCO700 SOF SE0500
S9E—__— S€o900— SOM. —_—$€0200
S9G- SC0400- S9T— SCOL00
SH SL4703 _ ==
COAST GUARD
Submission Authorized Submission Authorized
Routing Activity Routing Activity
Identifier DoDAAC Identifier DoDAAC
ZIC ZZ0001
ZNC ZZ0003
ZQC ZZ0002
24-9

ADC 333 Enclosure |
DLMS Chapter 24-LASE


b. Description of Change:

(1) As discussed at Supply PRC Meeting 08-1 (reference 3a), DLMSO has an ongoing
initiative to combine the DLSS and DLMS manuals. The current process of maintaining two sets of
publications, which contain essentially the same information for the different formats, is resource
intensive, duplicative in nature, and no longer practical. This change makes administrative updates to
the DLMS, Volume 2 (reference 3b) LASE chapter, which positions the chapter for movement to a
combined manual, to include:

(a) Identification at the beginning of the DLMS chapter for LASE, the correlation between the
Accredited Standards Committee (ASC) X12 beginning segment Report Type Code for the DLMS 846L
(LASE) and 870L (SPR/LASE Status) transactions, as well as the functionality of the corresponding
MILSTRAP(reference 3c) transaction Document Identifier (DI) codes DTA, DTB, DTC, and DTD.

(b) Use of generic names for the transactions throughout the chapter, so that the procedures
are format neutral and lend themselves to DLMS ASC X12, XML, and MILSTRAP use.

(c) Updates to DS 846L and 870L to clearly align the transaction titles with the beginning
segment Report Type or Transaction Type Code functions, and the corresponding MILSTRAP
functions.

(2) Revise DLMS LASE procedures to bring the DLMS procedures in line with the
corresponding MILSTRAP procedural requirement and the existing LASE process. The DLMS
guidance for editing the NSN field of LASE transactions for Federal Supply Class (FSC) and
National Item Identification Number (NIIN) compatibility conflicts with the MILSTRAP chapter 9
guidance. MILSTRAP business rules direct that DAASC will perform the FSC/NIIN compatibility
check for LASE transactions and DAASC shall generate the associated Status Notification Transaction
(MILSTRAP DZ9 (or corresponding DLMS 870L)), while the DLMS business rules have the IMM
performing the FSC/NIIN compatibility check for SPR transactions and generating the 870L Status
Notification Transaction. This update removes the disconnect between the MILSTRAP and DLMS
procedures. A parallel correction was made to the DLMS, Volume 2, Special Program
Requirements (SPR) FSC/NIIN edit procedures by ADC 287 (reference 3d).

(3) PDC 301 (reference 3e), which proposed modification to the LASE procedures, is still
outstanding awaiting feedback from Army, and is not considered in ADC 333.

(4) As part of their review of PDC 355, DLMSO requested by email of 6/12/09 and
reminder email 7/8/09 (reference 3f), that the Supply PRC representatives verify the LASE
chapter 24, section C24.8 list of their Component activities which are authorized to submit
LASE Request transactions. Only DLA provided an update to section C24.8, accordingly all
other Component activity entries remain published in DLMS/MILSTRAP as current and
valid. DLA is requested deletion of all DLA RI Codes/DoDAACs from section C24.8. As
documented in referenced PDC 301, DLA did not implement LASE under their modernized
system, EBS.

20f7
ADC 333
Attachment


ATTACHMENT TO ADC 333
Revision to DLMS, Volume 2, Chapter for Logistics Asset Support Estimate (LASE); and Administrative
Updates to DLMS 846L, 870L, LASE Request Codes and Reject Advice Codes (Supply/MILSTRAP)

1. Originator:

a. Service/Agency: Defense Logistics Management Standards Office (DLMSO)

b. Originator: Ms, Mary Jane Johnson, MILSTRAP Administrator, DLMSO, 703-767-0677,

DSN 427-0677, or e-mail: Mary.Jane.Johnson@dla.mil

2. FUNCTIONAL AREA: Supply

3. REFERENCES:

a. DLMSO memorandum, May 1, 2008, subject: DLMS Supply Process Review Committee

(PRC) Meeting 08-01, April 8-10, 2008, available at: http://www.dla.mil/j-
6/dimso/Programs/Committees/Supply/supplyPRC.asp

b. DoD 4000.25-M, DLMS, Volume 2 Supply, http://www.dla.mil/j-

6/dimso/elibrary/manuals/dlms/v2.asp

¢. DoD 4000.25-2-M, Military Standard Transaction Reporting and Accounting Procedures

(MILSTRAP), http://www.dla.mil/j-6/dlmso/elibrary/Manuals/MILSTRAP/default.asp

d. DLMSO memorandum, June 24, 2008, subject: Approved DLMS Change (ADC) 287,

Revision to DLMS 870L, SPR/LASE Status and Corresponding DLMS Manual Procedures;
Administrative Update to DLMS 830R, SPR (Supply/MILSTRAP), http://www.dla.mil/j-
6/dimso/eLibrary/Changes/approved3.asp

e. DLMSO memorandum, May 29, 2008, subject PDC 301, Alternative to the Logistics Asset

Support Estimate (LASE) Process for DLA Managed Assets Using DOD EMALL Supportability
Analysis Stock Out Report Tool (Supply/MILSTRAP), http://www.dla.mil/j-
6/dimso/eLibrary/Changes/proposed.asp

f. Emails from Mary Jane Johnson/DLMSO to Component Supply PRC representatives, 6/12/09

and 7/8/09, subject: Revision to DLMS, Chapter for Logistics Asset Support Estimate (LASE);
Reminder, requesting that as part of their review of PDC 355, the Supply PRC representatives verify
the LASE chapter 24, section C24.8 list of their Component activities which are authorized to submit
LASE Request transactions.

4, REQUESTED CHANGE:

a. Title: Revision to DLMS, Volume 2, Chapter for Logistics Asset Support Estimate (LASE);

and Administrative Updates to DLMS 846L, 870L, LASE Request Codes and Reject Advice Codes
(Supply/MILSTRAP).

lof7
ADC 333
Attachment


Component activity or matches the input transaction "from" organization) and process as
>
follows:

C24.5.2.1. Correct SOS. If the LASE inquiry Request Transaction is directed to the
correct non-GSA SOS, DAASC shall pass the transaction to that activity.

€24.5.2.2. Incorrect SOS — Reroute. If the LASE inquiry Request Transaction is
directed to an incorrect SOS, and the correct SOS is not GSA, DAASC shall reroute the
transaction to the correct SOS and send a Status Notification Transaction to the submitter citing
Status Code BM. DAASC shall identify the correct SOS in the notification transaction.

C24.5.2.3. GSA Directed Transactions. If the LASE inquiry Request Transaction
is directed to a correct GSA SOS or to an incorrect SOS, but GSA is the correct SOS, DAASC
shall reject the transaction to the submitter using DS 824R Reject Advice citing Reject Advice
Code AX.

24.5.3. If the NIN cannot be identified, DAASC shall reject the transaction to the
submitter using DS 824R citing Reject Advice Code AD.

24.6. RECIPIENT PROCESSING OF STATUS NOTIFICATION AND-REJECT ADVICE
TRANSACTIONS:

24.6.1. Recipients of Status Notification with MILSTRIP Status Code BG shall update
internal LASE records to show the correct FSC identified in the Status Notification
Transaction.

24.6.2. Recipients of Status Notification with MILSTRIP Status Code BM shall update
their internal LASE records to show the correct SOS identified in the Status Notification
Transaction.

24.6.3. Recipients of Status Notification Transactions shall notify other activities
requiring knowledge of the change and shall ensure all future transactions submitted for the
transaction number (also known as document number) reflect the change identified by the
status code in the Status Notification Transaction,

24.7. RECIPIENT PROCESSING OF REJECT ADVICE TRANSACTIONS.

24.7.1. Activities in receipt of DS 824R Reject Advice Transactions shall take
appropriate action as indicated by the reject advice code. In addition, recipients of Reject
Advice Code AB shall advise their designated Component contact point for cataloging data of
a DAASC SOS file discrepancy.

24.7.2. Reject advice codes applicable to LASE requests are AA, AB, AD, AF, AT, AU,
AV, and AX. MILSTRIP Status Code CJ, may also be received in Reject Advice Transactions.

24.8. ACTIVITIES AUTHORIZED TO SUBMIT LASE ASSEF- SUPPORF REQUESTS?

? SOS for obsolete/inactive items will be taken from the SOS file when possible; otherwise, the
SOS will be the activity identified as the TO activity in the incoming transaction.

C24-5
ADC 333 Enclosure |
DLMS Chapter 24-LASE


AIR FORCE

Submission Authorized Submission Authorized
Routing Activity Routing Activity
Identifier DoDAAC Identifier DoDAAC
DBO FB5270 FPK FD2388
DCG FB2180 FWA FAS000
DLE FB2006 FWB FB7000
DSA FA2833 FWD FAS612
F46 FB2373 FWE FB2300
FA9 FB2008 FWH FA2812
FFB FB2049 FWJ FA3012
FFZ FD2040 FWK FA3300
FGB FB2029 FWM FA6600
FGZ, FD2020 FWO FA2500
FHB FB2039 FWQ FA4413
FHZ FD2030 FWR FA5260
FLB FB2065 FWS. FA4502
FLZ FD2060 FWT FA4826
FNH FA2303 FWU FA7037
FPB FB2059 FWY FA3115
FPZ FD2050 FWZ FB6251
C24-8

ADC 333 Enclosure 1
DLMS Chapter 24-LASE