1. Defense Logistics Management Standards Office
Overview of Select Transaction Services Web Resources Supporting MILSBILLS
Defense Logistics Management Standards Office
The Defense Logistics Management Standards Office (DLMSO) has developed in collaboration with Transaction Services. Transaction Servicces is the logistics hub for routing, archiving, editing and conversion of transactions between eighty record position MILS transactions and DLMS variable length transaction depending on trading partner capability.
DLMS transactions are able to carry additional data, or extended data, such as Standard Line of Accounting (SLOA) data. All systems processing MILS transactions must be DLMS capable by 2019.
This presentation introduces Web resources developed by Transaction Services that may be of particular interest to those who often research logistics billing issues. If you need a quick refresher on Defense Logistics Management Standards (DLMS), and particularly the Military Standard Billing System (MILSBILLS), you may first want to review Module 10 of the DLMS Training posted to the DLMSO Web site.
Be aware that for DAAS has to maintain compatibility between the legacy 80 column MILS formats and DLMS. DAAS maintains the data warehouses that support these reports based on MILS. So, even where transactions start out as DLMS, the context for understanding some of these tools are still reliant on legacy record positions.

2. Topics Logistics Data Gateway (LDG)
Web Visual Logistics Information Processing System (WEBVLIPS)
Military Standard System Inquiry (MILSINQ)
Enhanced Defense Automatic Addressing System Inquiry (eDAASINQ)
Logistics Reports
These are the five Web resources this presentation will focus on. While these are just some of the systems Transaction Services supports, each can provide particular insight into MILSBILLS transactions and support data captured at Transaction Services.

3.
Before you can access any of these, you must complete a System Access Request (SAR) identifying to which system you want access and provide justification for granting access.

4. Access to Web Resources and Customer Support
Access (CAC required)
To submit System Access Request (SAR) choose Request Login ID and Password, navigate to appropriate SAR page.
Applications are accessed through the Transaction Services Portal once a System Access Request (SAR) is approved.
You must log-on every 30 days or account will become be revoked; after 60 days it is deleted. For revoked accounts contact Customer Support.
Link to send an under "Contact Us" or
For 24 hour 7 days-a-week Phone Support:
Telephone: (937)
DSN:
When access is granted, your common access card (CAC) will be able to log you into the Transaction Services Web Portal, which will display links to each system. Note that each system must be accessed within 30 days of your last login or access to that system will be revoked. Once account access is revoked, you have an additional 30 days to contact the DAAS Help Desk to request access be restored or the SAR process has to be restarted to regain access.

5. First resource we’ll look at is the Logistics Data Gateway.

6. Logistics Data Gateway
Overview
LDG is a data warehouse environment that provides users the ability to access Transaction Services-managed data/information using business intelligence tools or a web browser.
Data is generally retained for 3 years
Billing transactions are retained as far back as 1 April 2005
LDG queries are restricted to a 31-day search range.
Unlike WEBVLIPS, LDG can query all Document Identifier Codes (DIC) that route through DAAS (not restricted to requisitions).
Retransmitted bills are visible in LDG (unlike MILSINQ)
Password is required due to the COTS software.
Reports can be saved in several formats: e.g., PDF, .CSV, Crystal Reports, etc.
Logistics Data Gateway (LDG) is a data warehouse environment that provides users the ability to access Transaction Services-managed data/information using business intelligence tools or a web browser. The LDG provides easy web access to the current and historical data that flows through the Transaction Services and provides this data in an integrated fashion. Unlike the other CAC-enabled applications, LDG requires password authentication due to the Business Objects COTS software.

7. Logistics Data Gateway
Available Queries
Historical Requisition Counts by Project Code
Interfund Bills (by Buyer or Seller) and Bill Number or DAAS Received Date
Project Codes
Raw Transactions by Document Number
Raw Transactions by PIIN and Call Order
Transactions by DoDAAC and DIC (Document Identifier Code)
Transactions by Header Destination COMMRI
Transactions by NSN/DIC/Document Number
Transactions by Originating COMMRI (External View)
Here are the queries that are available to external LDG users. Transaction Services personnel have access to a greater number of queries.

8. Logistics Data Gateway
Click “Public Folders” and then click “Logistics Data Gateway.”
The list of queries will appear.
For the purpose of this training, we will use the “Raw Transactions by Document Number” query.

9. Logistics Data Gateway
This slide displays the available queries we saw earlier.
We will use the Raw Transactions by Document Number query and use document N A requisition document number is constructed using the requisitioner’s DoDAAC for the first six characters, followed by a four character Julian ordinal date, and then a four character serial number.

10. Logistics Data Gateway
This slide is just a snapshot of the document we queried: N You can save the report in several formats: PDF, Excel, .CSV, Crystal Reports, Rich Text Format, XML, etc.
You can navigate through the pages of the report, zoom in and out, or use the search function (field with the binoculars).
The search function is useful for queries that return large results. Some queries allow you to search for up to 60,000 records, but be aware that the application may time out once you get over 40,000 records.

11. Logistics Data Gateway
Here’s the chronological history for document N
The transactions are shown by the date/time that they were received by DAAS (Greenwich Mean Time – GMT).
The A0A was received first, followed by an A5A Materiel Release Order (MRO), AE_ Supply Status, AR0 Materiel Release Confirmation.
Note: DAAS allows for interoperability between DLMS and non-DLMS applications. However, at this time, all transactions in LDG and other DAAS applications appear in the legacy MILS format. However, LDG does append the DLMS transaction data

12. Logistics Data Gateway
This slide shows page two of the transaction history. You can see that an AS_ Shipment Status is sent immediately following the Material Release Confirmation. A DRA Material Receipt Acknowledgment is shown, and finally, an FA1 Interfund Bill from Stock. In a later slide, we will use the LDG query “Interfund Bills by Buyer DoDAAC and Bill Number” search to query the billing information for this document.
Some transactions are processed by DAAS simultaneously. In our example, the source of supply sends the AS8 (DLMS 856S) to DAAS, and based on MILSTRIP distribution rules, DAAS creates the AS1. Although the AS1 is displayed above the AS8, the time stamp for both is 27-Aug :20 GMT. Other times, the AS8 might appear on top.
This is important to remember since sometimes transactions are rejected by DAAS, and an AE9 with negative supply status will process at the same time as the requisition, etc. Therefore the AE9 might appear before the transaction that rejected, but they will have the same timestamp.

13. Logistics Data Gateway
This slide is an illustration of the MILSTRIP Requisition Cycle flow diagram. The transaction history for document N corresponds to this process flow.

14. Logistics Data Gateway
Starting in late Spring 2015, transactions sent to DAAS in DLMS format that are addressed to DLMS-compliant systems appear as hyperlinks.
Clicking on the hyperlink opens a sub-report that displays the DLMS segments within the “extended data.” Extended data is denoted by the ‘\\’ in legacy record position (rp) followed by select DLMS data segments. Extended data is data present in the DLMS transaction that cannot be mapped into MILS, but nonetheless must be delivered to a DLMS-capable trading partner.
In some queries, the extended data runs off the screen, in this case, the data is not fully displayed. The LDG developers are generally aware of this.

15. Logistics Data Gateway
This slide shows the extended data sub-report.
The A0A came out of Navy ERP, which is a DLMS compliant system; therefore it is a clickable hyperlink.
As a result of ADC 1043, requisitions must contain Standard Line of Accounting (SLOA) data, and DAAS must valid discrete SLOA data elements. Because of this, the FA2 Accounting Segments (which contains SLOA data elements) are included in the extended data and therefore are viewable in the extended data sub-report.

16. Logistics Data Gateway
On this slide, notice how the FA1 Interfund Bill does not display as a hyperlink.
Although it was generated by EBS, which is a DLMS compliant system, the destination system (DFAS Cleveland) is not capable of processing DLMS transactions. Therefore, DAAS converts the DLMS transaction to an 80 character MILS transaction. The extended data is not carried, and thus there is no need to show the transaction as a hyperlink. [DLMSO Note: We think the report should include the DLMS extended data anyway. Will discuss with Transaction Services.]

17. Logistics Data Gateway
Those of you that work on the systems side of the house may be interested in understanding what’s referred to as the DAAS interface data. This is the string of data directly below the transaction displayed in LDG. Here is a screenshot of the interface data “cheat sheet.”
Interface data is useful for researching the system (identified by COMMRI) that sent or received the transaction. You can query the COMMRI using another Transaction Services application, EDAASINQ. Bills that were retransmitted by MILSINQ will show COMMRI “RUSAZZQ” as the Originator.
Interface data is also useful if you are researching a transaction that may have routed to a different source of supply than expected. For example, the order may have used Army CECOM, Routing Identifier Code (RIC) B16, but was redirected to DLA EBS RIC “SMS.” Rp would display “B16” (RIC as received) while RP will show ZZZSMS (ZZZ placeholder for RICs followed by SMS) (destination RIC). Alternatively, a transaction that routes to a DODAAC, such as a status, will show the DODAAC in this field.
Transaction Services personnel use this information to identify the originating or destination Communication Routing Identifier, or the unique message serial number when looking for specific messages within a file transmission.

18. Logistics Data Gateway
Recall the FA1 Interfund Bill From Stock in document N We will use the Interfund Bills by Billed DoDAAC (buyer) and Bill Number query.
Despite the use of the term “Interfund Bill,’’ you can query Non-Interfund bills as well.

19. Logistics Data Gateway
This is the query form. Due to the “J” signal code in the FA1, we derive the billed DoDAAC from the DLMS requisition DoDAAC (rp 30-35) and the Bill Number from rp of the detail billing record in this case.
Though optional, I recommend entering the date (YMM) in the Billing YR/MO field, since bill numbers may be reused from year to year.

20. Logistics Data Gateway
This slide is a snapshot of the bill we queried. We’re looking at the summary billing record, or SBR.

21. Logistics Data Gateway
Interfund Bill queries will always display the Summary Billing Record (SBR), Document Identifier Code FS_ (Interfund) or GS_ (Non-Interfund).
An SBR can contain up to 494 detail bills. Therefore, your results will likely contain several pages of data; our example contains 34 pages. Clicking on the next page arrow, or manually entering a page number will display that page of detail billing information.

22. Logistics Data Gateway
You can use the search field (similar functionality to “ctrl-F”) to quickly find information. This is useful when LDG returns large amounts of data.
Our FA1 detail bill for document N is highlighted. The transaction containing the information you search will always be highlighted in orange. This transaction was on page 17!

23. Web Visual Logistics Information Processing System (WEBVLIPS) is the next application we’ll look at for querying logistics transaction data.

24. WEBVLIPS
Like LDG, WEBVLIPS has set query capabilities based on how you want to be the focus of your results. Here we’ll look at the WEBVLIPS version of the query we did in LDG for the same document number.

25. WEBVLIPS Default View is the “In Process” > “Main” tab.
WEBVLIPS displays the data in forms that make it easier to read than the raw transaction data. The Main view provides a summary of pertinent information about the requisition. Here we see the data for document number N that we examined in LDG.
The hyperlinks on the page perform one of three functions: 1) generate a pop-up explaining what a code means; 2) executes a table look-up for an identifier to get more related information to show in a pop-up (for example, the SUPPAD DoDAAC and the depot RIC); or 3) executes a query for transactions associated with that piece of data and presents in a new browser window (for example, NSN or TCN).
Default View is the “In Process” > “Main” tab.

26. WEBVLIPS
The Pipeline tab provides a snapshot of milestones based on transaction data.

27. WEBVLIPS
The History tab presents the transaction data in MILS format, even for transactions sent in DLMS format. Unlike LDG, WEBVLIPS does not have the ability to see the additional DLMS data. The information displayed beyond the 80 characters of the MILS format is DAAS processing information.

28. In MILSINQ we can conduct a billing transaction search similar to the earlier LDG example. Generally speaking, MILSINQ is easier to use than LDG when perform MILSBILLS research. However, MILSINQ is restricted to MILSBILLS, while LDG can be used for many different purposes, namely searching for older bills since MILSINQ generally retains data no longer than one year (two years for FMS).

29. MILSINQ
YYYY (Year) - 4 characters - all numeric
MONTH (Month) - 2 characters - all numeric
RADAY (Day of the Year) - 3 Characters - numeric
BILLED DODAAC (BILLTO) - 6 characters - alphanumeric
BILLING DODAAC (BILLFM) - 6 characters - alphanumeric
BILL NUMBER - 6 characters - alphanumeric
DESTINATION COMMRI - 6 alpha
MILSINQ has two options for searching by date. YYYY is derived from the one position year in the seventh position of the DLMS requisition document number (which is rp 36 in a legacy MILS transaction. MM is derived from the eighth and ninth position of the document number (MILS rp 37-38). The option RADAY looks at the interface data and shows only data received on a particular Julian date. It is possible to see a bill from Month 01, for instance, that wasn't processed until Julian day 038 (February 7th).
The DESTINATION COMMRI is for searching bills based on where DAAS routed the bill. Will look closer at COMMRIs when discussing the eDAASINQ system.

30. MILSINQ
Notice how we have the same information we used in our LDG search populated in the search fields.

31. MILSINQ
This is the DAAS MILSBILLS Header Inquiry screen. We’ll click “List/Download/Retransmit Selected Messages”

32. MILSINQ This is the DAAS MILSBILLS List Messages screen.
You can see the summary billing record (FS1) followed by the detail billing records. Our example document (N ) is conveniently the first detail bill shown. I chose this document for that reason; I do not know why this document is on page 17 in LDG however.

33. MILSINQ
Now, we’ll demonstrate a Seller researching rejected bills. In this case all rejected bills sent from EBS during January 2015.

34. MILSINQ
The TO COMMRI of RURRRRR indicates all these bills failed an edit during processing at DAAS and was rejected.

35. MILSINQ
Clicking on the Reject code in the right most column provides the reason for rejection. Code Z means the Bill-To DoDAAC is not recorded in DAAS. Code V is used when the identified Bill-To DoDAAC does not have an Authority Code that allows that activity to be routed interfund bills.

36. MILSTRAP Appendix 2.8 MILSINQ
BU Rejected. Discrete values for the SLOA data elements in the transaction do not match data elements from the SFIS Fund Code to Fund Account Conversion Table for the Fund Code cited in the transaction.
BV Rejected. DoDAAC in the transaction does not have the appropriate authority code for its intended use
BW Rejected. Suspense account is not authorized for Interfund use
BX Rejected. Total dollar value of detail bills is not equal to total dollar value of the summary bill
BY Rejected. Count of detail bills is not equal to the count in the summary bill (MILS RP 5-7, DLMS 810L 3/CTT01/070)
BZ Rejected. DoDAAC is not valid in DAAS
U –
SLOA ELEMENTS INVALID IAW SFIS FUND CODE TABLE
V - Unauthorized "Bill To"
  ADDR BILL TO NOT AUTHORIZED FOR INTERFUND USE
BILL OFC ADDR NOT AUTHORIZED FOR INTERFUND USE
VALIDATE VALUE OF FE/GE ENTRY
W - F3885 Not Authorized
ACCOUNT UNAUTHORIZED FOR USE IN INTERFUND BILL
X - Dollar Value Summary not equal to Details
DOLLAR VALUE OF DETAIL NOT EQUAL TO SUMMARY
Y - Card Count Summary not equal to Details
DOC COUNT NOT EQUAL TO COUNT IN RP 5-7 OF SBR
Z - Invalid "Bill To"
BILLING ADDRESS IN RP NOT IN DAAS RECORDS
ADDR BILL TO IS INVALID FOR DOCUMENT ID
The codes in MILSINQ are based on billing related codes in in MILSTRAP Appendix 2.8, Reject Reason Codes.

37. MILSINQ
The List/Download Selected Messages button formats a report for the selected bills to include the individual detailed bills.

38. MILSINQ
Here is the report for the bill we checked. Clicking on the Download All Messages creates a text file of the transactions.

39. Next we’ll look at eDAASINQ and compare it to the publicly accessible DAASINQ.

40. eDAASINQ Two versions available:
eDAASINQ (enhanced-DAASINQ) is an enhanced version of the basic DAASINQ, includes all of the above, plus
Communication Routing Identifiers (COMMRI)
Distribution Codes
eDAASINQ Provides additional queries and downloads by service or "All" in "TA1" delimited format in addition to all the basic functionality that is available in DAASINQ.
eDAASINQ is PKI-enabled and access to the application may be requested by submitting a System Access Request (SAR).
DAASINQ provides information on
DOD Activity Address Codes (DODAAC)
National Item Identification Number (NIIN)
Routing Identifier Codes (RIC)
Military Assistance Program Address Codes (MAPAC)
Enhanced DAAS Inquiry (eDAASINQ) is a DLA Transaction Services web application that allows users to query DoDAACs, RICs, MAPACs, Distribution Codes, NIINs, and COMMRIs.
User can also download various reports which include Fund Codes, the DoDAAD file, and the MAPAD file among others.
User can perform wildcard searches or search using a wide range of criteria such as by Major Command, Service/Agency, etc.
A stripped-down version of eDAASINQ, simply called DAASINQ is available for users who have not been granted access to the CAC-enabled site.
Downloads are not available in DAASINQ, and a user can only query one code at a time.

41. eDAASINQ
EDAASINQ Home Page
Displayed is the eDAASINQ home page.

42. eDAASINQ
This slide displays the MILSBILLS header inquiry for the bill we queried earlier in MILSINQ. The buyer DoDAAC, N69117 populates DoDAAC field.

43. eDAASINQ
DoDAAC Central Service Points assign authority codes to restrict the use of a DoDAAC. Authority codes are applicable to all Components/Agencies, and there are many supply and finance business process edits based on the authority code.
Authority Code 00 allows unrestricted use of the DoDAAC.
Here is the information returned:
We are looking at the DoDAAC Information tab
The top section displays important information such as the Authority Code for example. The authority code of the DoDAAC must be approved for how it is used in the transaction for requisitioning, billing, shipping or administrative purposes. These are shown on the following slide.
Note here that the authority code for this DoDAAC is 03, which means that this DoDAAC may be used to requisition materiel and to process bills, but materiel may not be shipped to this activity. Requisitions for this activity should never contain a signal code of A/B/C/D.

44. eDAASINQ
Code
Description
Definition 00
Requisition
Authorized to initiate a requisition/purchase for goods and services. Authorized ship-to and bill-to.
Required: TAC 1, TAC 2, TAC 3
Restriction: None
Business Rules: Can be used for any business process.
DAAS DoDAAC Authority Code Edit: No additional edit. 01
Ship-To Only
Can only be used as a ship-to address with no other implicit authority.
Required: TAC 1, TAC 2
Restriction: Not authorized for requisition or bill-to.
Business Rules: Used as a ship-to designation.
DAAS DoDAAC Authority Code Edit: DoDAAC may only be used in the MILSTRIP legacy requisition supplementary address field (record positions 45-50) with signal code J, L, M, X. Under DLMS, DoDAAC may not be used in N101 with codes OB, BT, and BS, and may not be used in N901 with code TN. 02
Finance (Bill-to Only)
DoDAAC can only be used as a bill-to.
Required: TAC 1, TAC 3
Restriction: Cannot requisition or be used as a ship-to designation.
Business Rules: Used as a bill-to designation.
DAAS DoDAAC Authority Code Edit: DoDAAC may only be used in the MILSTRIP legacy requisition supplementary address field (record positions 45-50) with signal code B. Under DLMS, DoDAAC may not be used in N101 with codes OB, ST, Z7 and BS, and may not be used in N901 with code TN. 03
Do Not Ship-to
Cannot be used as a ship-to designation.
Restriction: Cannot be used as a ship-to designation.
Business Rules: Can requisition or be used as a bill-to designation.
DAAS DoDAAC Authority Code Edit: If DoDAAC used in the MILSTRIP legacy requisitioner field (record positions 30-35), it must contain signal code J, K, L, M, or X. If used in the requisition supplementary address field (record positions 45-50, it must contain signal code A, B, C, or D. Under DLMS, DoDAAC may not be used in N101 with codes ST, Z7 or BS.
Here are the Authority Codes and business rules from DLM , Volume 6, Chapter 2 on the DoDAAD. See that code 00 has no restrictions.

45. eDAASINQ 04 DLA Disposition Services Only
DLA Disposition Services Only (e.g. State agencies surplus). Used to identify activities that have no requisition authority other than for DLA Disposition Services Only materiel.
Required: TAC 1, TAC 2, TAC 3
Restriction: Cannot requisition new materiel. Only authorized to obtain materials from DLA Disposition Services (DOD excess only).
Business Rules: Although the material is normally provided as a free issue; in some instances a cost may be required. Consequently, TACs 1 through 3 are required to cover every possibility.
DAAS DoDAAC Authority Code Edit: DoDAAC may only be used with DLA Disposition Services RIC (S9D) in record positions Under DLMS, DoDAAC may only be used with DLA Disposition Services RIC (S9D) in RIC To. 05
Non-Requisition
Cannot initiate a purchase or request for goods and services.
Required: TAC 1, TAC 2
Restriction: Cannot requisition/purchase goods/services.
Business Rules: Used as a ship-to designation.
DAAS DoDAAC Authority Code Edit: DoDAAC cannot be used in the MILSTRIP legacy requisitioner field (record positions 30-35). Under DLMS, DoDAAC cannot be used as N101 code OB or N901 code TN. 06
Free Issue
No cost option. The activity is restricted to items that are available without cost (e.g., DLA Disposition Services, NGA Maps).
Restriction: Cannot requisition/purchase any good/services.
Business Rules: Similar to DLA Disposition Services, but can request free of cost items (e.g., maps from National Geospatial-Intelligence Agency (NGA)). Can be used as a ship-to designation.
DAAS DoDAAC Authority Code Edit: DoDAAC may only be used with signal code D or M. Under DLMS, DoDAAC may only be used with PO105 code NC. 07
Administrative
Administrative only. This code is used for information/identification purposes only (e.g., Defense Courier Service (DCS), or contingency/emergency use).
Required: TAC 1
Restriction: Cannot requisition, be used as a ship-to- designation, or be used as a billing designation (TAC 2 and TAC 3 are not allowed).
Business Rules: Information/identification use only.
DAAS DoDAAC Authority Code Edit: DoDAAC may not be used in MILSTRIP legacy requisition in record positions or in record positions as a “ship to” or “bill to”. Under DLMS, DoDAAC cannot be used with N101 codes OB, BT, BS, ST, or Z7 or in N901 code TN.

46. eDAASINQ Bills that route TO N69117 will be delivered TO RUQAEXC
All other transactions that route to N69117 will be delivered to RUSAIDJ
If no BILL COMMRI exists, the billing transaction will be delivered to the DP COMMRI.
Returning to our DoDAAC, the COMMRI Information section is highlighted here.
The data-pattern (DP) COMMRI is where supply-related transactions are sent to. In this example, RUSAIDJ represents Navy ERP. For example, status and MRA follow-up transactions for DoDAAC N69117 would route to this COMMRI.
The billing (BILL) COMMRI is where billing-related transactions are sent. RUQAEXC is DFAS Cleveland. Interfund Bills would route to this COMMRI.

47. eDAASINQ vs DAASINQ eDAASINQ DAASINQ
This slide shows eDAASINQ and DAASINQ side-by-side.
Notice the additional menu options in eDAASINQ along with the additional tabs on the query display.

48. eDAASINQ Here is an example of a RIC query.
RIC NUA, NAVSUP WSS MECHANICSBURG is associated to COMMRI RUSAIDJ. Notice however that the “Last Transmit Info” shows RUSAYLB in the header which is the COMMRI for DLA’s Enterprise Business System (EBS). To correlate this with our example, the item ordered in our example document is managed by DLA and you can see DLA is the Billing DoDAAC (SL4701)

49. eDAASINQ COMMRI RUSAIDJ and RUQAEXC
This slide displays COMMRI query results:
The query on the left is Navy ERP. This is the system performing the billing in our example.
The query on the right is DFAS Cleveland. This is the system receiving the bill

50. eDAASINQ DAAS COMMRIs
RUTTTTT – Terminate. Transactions are written to history (e.g., VLIPS, LDG), but terminate in DAAS.
RURRRRR – Rejected. The transaction has failed a DAAS edit.
RUMMMMM – Mail. An outdated COMMRI that functions the same as RUTTTTT. Transactions process but terminate.
RUSAZZZ – A COMMRI assigned automatically by DAAS when new DoDAACs or RICs are created.
The COMMRIs on the right are some used exclusively by DAAS. I included a description of each since you will often see them when using DAAS applications.
RUTTTTT is used to “terminate” transactions in DAAS. Sometimes this is performed when a transaction has rejected with AE9 supply status. Other times, it is used to terminate the A_8 status transaction from the SoS. Additionally, it associated to DODAACs and RICs that have no COMMRI assignment.
RURRRRR denotes that a transaction was “rejected” and terminated in DAAS.
RUMMMMM was used for the DAAS mailer. That was an decommissioned process where GSA customers could received physical mail in lieu of electronic transaction status. This COMMRI essentially serves the same purpose as RUTTTTT, but will presumably be replaced with RUTTTTT in the future.
RUSAZZZ is assigned automatically by DAAS when new DoDAACs or RICs are created. Transactions that route to this COMMRI build up in an “Intercept” queue, and the system periodically attempts to re-transmit the queued messages to a valid COMMRI.

51. Routing vs Delivery Transactions ROUTE to DODAACs or RICs.
ROUTING is determined by MILSTRIP, MILSBILLS and DLMS manuals, in addition to service-unique business rules.
Transactions are packaged in messages that are DELIVERED to a COMMRI.
DELIVERY is a communications function separate from ROUTING.
In our example, the Interfund Bill was submitted by SL4701 and it came to DAAS from COMMRI RUSAYLB.
It ROUTED to N69117 but was DELIVERED to RUQAEXC.
This slide provides some clarifications between routing and delivery:
Individual transactions route to DoDAACs or RICs
Transactions route according to a multitude of business rules that come from the DLMs and Component-specific guidance
Transactions are packaged into messages that are delivered to a COMMRI

52. eDAASINQ Recap
Authority Code explanations from DLM , Defense Logistics Management System (DLMS), Vol 6, Logistics Interoperability Support Services, Chapter 2 DoD Activity Address Directory,
BILL COMMRIs are assigned by direction from the Service/Agencies. They associate to an ADSN for Air Force, and an FSN for Army.
Bills are delivered to BILL COMMRIs, unless none exists in DAASINQ, then delivered to DP COMMRI
There are many DAAS use-only COMMRIs. RUTTTTT usually means a DoDAAC is not tied to a supply system. The data must be sent somewhere. RUMMMMM was used for the DAAS Mailer Process and will eventually be cleansed. RURRRRR means the transaction rejected.
eDAASINQ Review

53. The last report system we’ll look at is Logistics Reports.

54. Logistics Reports
Here is the home page for Logistics reports. There are links to jump to the five sections for reports. Each section has a dropdown of caned reports that can be run for an identified month. All reports are available for the past twelve completed months.

55. Logistics Reports Select the last completed month.
For this example of generating the current SFIS Fund Code to Fund Account Conversion Table, we are going to treat January 2016 as the most recently completed month. I.e. the current date would be in February 2016.

56. Logistics Reports
This is the top of the report. This single report is split into three sections for DLMS Volume 4, Appendix 1:
1.1 – SFIS Fund Code to Fund Account Conversion Table
1.2 – Fund Code to Billed Office DoDAAC
1.3 –Table of H Series DoDAACs, Authorized Interfund Billing
This report is used to update DLMS Vol. 4, Appendix 1. All three parts of the appendix are included in this fund code report.

57. Logistics Reports Select the desired month to be queried.
The MILSBILLS section has a number of reports pulled from billing transactions.

58. Logistics Reports
Here is an example of the Billing Adjustments report. It prioritizes some specific billing advice code request types:
(19/41) seeks the bill to be resent, or for 19 provide credit
(21/24/26) request credit refund due to a discrepancy report (i.e. TDR/PQDR/SDR)
(34) missing bill for received materiel
Also, the following billing status responses are highlighted:
(AM) discrepancy report required the return of the discrepant or deficient materiel, before credit can be provided
(DF) no record of cited document number or bill number is on file
(CA/DM) Duplicate, adjusted, or corrected bill will be sent in the next billing cycle
(DD) Billing or adjustment was rendered under a bill number being provided back
(EL/EM) report the cited discrepancy report not found

59. Logistics Reports
Here are some of the other billing reports that can be generated.

60. Questions?