DLA Transaction Services Integrated Email Logistics 

(DIELOG) 

User’s Guide 

Revised October 13, 2015
This page is intentionally left blank.

Page 2 
Record of Review and Changes 

DATE Version Description of Change 

December 08, 2008 1.0 Rewrite of Original User’s Guide date May 11, 1999 (MLR) 

Page 3 
This page is intentionally left blank.

Page 4 
 Table of Contents 

INTRODUCTION.........................................................................................................................................................6

BECOMING A USER OF DIELOG..........................................................................................................................6

TESTING......................................................................................................................................................................6

TRAFFIC FLOW .........................................................................................................................................................7

FORMATS TO BE USED WITH DIELOG ..............................................................................................................7

EXAMPLES OF DAAS DIELOG FORMAT............................................................................................................9

MAILING SYSTEM...................................................................................................................................................11

USER GENERATED EMAIL MESSAGE RESTRICTIONS...............................................................................11

EMAIL GENERATED FROM DAASC...................................................................................................................12

DAASC ROUTED TRANSACTION FORMAT.....................................................................................................12

EXCEPTION/REJECT FORMAT ...........................................................................................................................13

Page 5 
Introduction 

The DLA Transaction Services (DLA-TS) provides the ability to send and receive Military 

Standard Logistics Transactions via the electronic mail system. This manual is a guide for 

users when sending and receiving Military Standard Logistics Transactions to DLA-TS using 

Email. 

Important User Information

DIELOG is intended for LOW VOLUME use, which is less than 2,500 records per day. If a user 

anticipates a continuously higher volume of transactions, please contact DLA-TS Help Desk to 

discuss an alternate method of communication. 

Becoming a User of DIELOG 

To become a registered user of the DIELOG process, access the DLA-TS web site: 

https://www.transactionservices.dla.mil

1. Choose "Request Login ID and Password"

2. Read and accept the access warning

3. Read and accept the “DLA General Rules of Behavior”

4. Then click on “DIELOG” system link.

5. Fill out the online “DIELOG System Access Request” form and submit it.

Note: The Email address provided by you on the registration form as: "Email Address for Data 

Transmission/Receive" will be used as the path to send DIELOG messages back to you. Therefore, 

it is very CRITICAL that the Email address that you want registered as a DLA-TS DIELOG user 

must be set up properly on your system. It is recommended that you use an Organizational Email 

address rather than an individual one, because of personnel changes. 

The DLA Transaction Services DIELOG point of contact is: 

DLA Transaction Services Information Center 

E-Mail dieloghelp@dla.mil 

Or phone DSN 986-3247 

Or commercial (937) 656-3247 

Testing 

New DIELOG users will be required to send test messages to ensure that all of the formatting 

requirements are met before a user conducts a live transmission. The test message will be 

Page 6 
validated and the transactions will be returned to the new DIELOG user. The Segment Header 

will appear as follows when in test mode: 

*BEG IAZZ/RUQACZA/R

Note: The “RUQACZA” in the Segment Header above is an example of the user’s COMMRI 

assigned to them by DAASC. 

When a User is in TEST mode the Email Subject line should look like this: 

SUBJECT: Test Military Standard Transactions For Review Enclosed From "COMMRI" 

(Where “COMMRI” is the COMMRI assigned to you by DLA-TS on approval letter) 

If there are no problems with the message format and transmission, as determined by DLA-TS

personnel, then live processing can commence. 

IMPORTANT: As soon as you are ready to begin submitting LIVE transactions, You must 

change your *BEG line to reflect the following destination COMMRI:

RUSAZZA (otherwise your ‘live’ transactions will loop back to you.) 

Note: It is the DIELOG User’s responsibility to request that DLA Transaction Services put 

their account LIVE after the testing procedure. 

Traffic Flow 

The process that DIELOG messages will flow through is as follows: 

A. Inbound to DLA Transaction Services

Send your traffic to the Email address of: 

DIELOG@DAAS.DLA.MIL

As these messages are received at DLA-TS, the DIELOG process will extract 

transaction segments from the Email message and either: 1) direct the transaction to the 

destination cited in the segment header or 2) pass the transactions to DLA-TS for 

automatic value-added processing. 

B. Outbound from DLA Transaction Services 

As transactions are received from DLA-TS and are destined to a DIELOG customer, 

they will be encapsulated in an Email message and forwarded to the DIELOG customer 

utilizing the Email address as identified by the DIELOG registration form. 

Formats To Be Used With DIELOG 

Page 7 
Email processing will allow the use of multiple formats for Email messages. Users may use one 

of the three following formats: 

1. DLA-TS DIELOG File Format

2. DLA-TS DDN File Format

3. Defense Logistics Management System/Electronic Data Interchange File Format

(DLMS/EDI) 

1. DLA Transaction Services DIELOG File Format

DIELOG format is a format that has been designated specifically for Email. DIELOG was 

developed for those users that have Email capabilities as a means of entering logistics 

transactions into the logistics environment. 

The DIELOG format consists of three parts: 

a). Segment Header 

b). Transaction Header 

c). Closing Trailer 

a. Segment Header

The segment header consists of four parts. The first part is the *BEG which signifies the 

starting of a new segment. Then the next three parts follow it, in order: 

Content Indicator Code – identifies the file content type. Determines if special processing 

rules apply to this type of data (i.e. IFBB is for Billing content) 

Destination COMMRI – is the address to which the transaction segment will be sent (i.e. 

RUSAZZA) 

Precedence – is the priority of the transaction segment (i.e. P - priority; R – routine) 

The Segment Header layout is as follows: 

*BEG Content Indicator Code/Destination COMMRI/Precedence

Example: *BEG IAZZ/RUSAZZA/R

Note: The *BEG and segment header parameters will be separated by a space. The rest 

of the segment header parameters will be separated by a "/". 

The default values for the above Segment Header example are as follows: 

Page 8 
Content Indicator Code = IAZZ (Data Pattern logistics) 

Destination COMMRI = RUSAZZA (DAAS processing) 

Precedence = R (routine) P (priority) 

b. Transaction Section

The transaction section consists of Military Standard Logistics Transactions (DLSS, 

DLMS/EDI). 

Defense Logistics Standard System (DLSS) fixed length 80 character record format 

(Milstrip, Milstrap, etc.) 

Defense Logistics Management Standards (DLMS), Electronic Data Interchange (EDI) 

variable length format, Accredited Standards Committee X12 transaction sets. 

Examples: 527 Material Due-In and Receipt 

812 Credit/Debit Adjustment 

858 Shipment Information 

Note: If you are unfamiliar with what belongs in each 80 card column in Milstrip, you 

may request a Milstrip Document Guide. It tells what belongs in each card column.

You may also access this information via the DLA-TS WEB site. 

See various examples in this User’s Guide of each message/file format. 

c. Closing Trailer

The closing trailer consists of two parts. The first part is the "*END" which is mandatory. 

This signifies the end of the message. The second part is an optional parameter where a 

user can provide the transaction counter for the entire message, which includes the *BEG

line, all milstrip lines and the *END line. 

 EXAMPLE: *END XXXXX (This indicates END of entire message.) 

Usage of this optional field will provide additional assurance to users that all data 

sent was received and processed by DLA-TS. 

Examples of DLA Transaction Services DIELOG Format 

First is an example of the STANDARD basic transaction: 

*BEG IAZZ/RUSAZZA/P

A0AS9MS6520007826469 SE000021W33M8S30499800RYL17C5ATK 06059 

A0AS9MU5930009267458 EA00001W81N7130480600RW33M8SKTK 13000 

Page 9 
A0AS9MS6505000599017 BT00001W33XTF30494002RYMEPHATK 13000 

A0AS9MS6505001538750 BT00001W33XTF30499013RYMEPHYTK 13000 

*END 00006

Multiple segments is an option that may be included in each Email message 

(see NEXT example below). 

*BEG IAZZ/RUSAZZA/P

A0AS9MS6520007826469 SE000021W33M8S30499800RYL17C5ATK 06059 

A0AS9MU5930009267458 EA00001W81N7130480600RW33M8SKTK 13000 

A0AS9MS6505000599017 BT00001W33XTF30494002RYMEPHATK 13000 

A0AS9MS6505001538750 BT00001W33XTF30499013RYMEPHYTK 13000 

*BEG

A0AS9M65200078260469 SE00002W33M8S30499800RYL17C5ATK 06059 

A0AS9MU5930009267458 EA00001W81N7130480600RW33M8SKTK 13000 

*BEG

A0AS9M65200078264691 SE00002WEEM8S30499800RYL17C5ATK 06059 

*END 00011

2. DLA Transaction Services DDN Format

DDN is a variable or fixed-length format for exchanging logistics transactions over packet 

switched networks. This option is provided for customers that have the capability to read/write 

DDN format. Email DDN formatted messages, include a valid DDN type transaction in an 

Email message addressed to: 

DIELOG@DAAS.DLA.MIL

The rules for DDN formatted transactions apply. The following is an example of a file in DDN 

format. Upon request DLA-TS will supply documentation supporting this format (DDN 

Documentation). 

FH*010378*RUQAAAC*0001*930218*1455 

SH*F**0080*0006*P*IEDB*RUQAAAC**0001*930218*1455*RUEOZZA* 

A0AS9MS6520007826469 SE000021W33M8S30499800RYL17C5ATK 06059 

A0AS9MU5930009267458 EA00001W81N7130480600RW33M8SKTK 13000 

A0AS9MS6505000599017 BT00001W33XTF30494002RYMEPHATK 13000 

A0AS9MS6505001538750 BT00001W33XTF30499013RYMEPHYTK 13000 

3. DLMS/EDI Format

The DLMS/EDI format utilizes American National Standards Institutes (ANSI) Accredited 

Standards Committee (ASC) X12 transactions for electronic data interchange. This option is 

provided for customers that have the capability to read/write DLMS/EDI format. To Email 

DLMS formatted messages, include a valid DLMS/EDI type transaction set in an Email message 

to: 

Page 10 
DIELOG@DAAS.DLA.MIL

All the rules for DLMS/EDI transaction formats apply. The following is an example of a file 

in DLMS/EDI format. DLA-TS can provide, upon request, documentation supporting this 

format. 

ISA*00*0000000000*00* *10*WK4FV1 *10*SC0200 

*930920*1717*U*.......

GS*D1*WK4FV1*SC0200*930920*1717*DNCS.0001*D*002040 

ST*511*00000001 

BR*00*A0*930920*WK4FZW*10****171730 

LM*DD 

LQ*A9*YMEAAD 

LQ*52*C 

N1*TO**M4*S9M 

(.................) 

N1*ST**10*WK4FZW 

N1*Z3**D,CAMARILLO,CA 93011-6010.TEL-800- 

N1*Z3*423-2567 

SE*83*00000001 

GE*95*DNCS.0001 

IEA*1*000016838 

Information Center Help Desk at (937) 656-3247 

or 

DLA Transaction Services EC/EDI Program Management Office at (937) 656-3770 

Mailing System 

The mailing system for sending/receiving messages is the Simple Mail Transfer Protocol 

(SMTP) format. When the user sends messages, the process of stamping and removing headers 

will be transparent to the user. When the user receives a message, they will see the SMTP 

header stamped at the top of the mail message. 

User Generated Email Message Restrictions 

1. Must put new line character in messages after each record.

2. Mailer must stamp an SMTP header on it.

3. The size of the user generated Email message cannot exceed 200,000 bytes (or smaller

if your Email package has a lower maximum Email message size). Please verify this 

parameter with your System Administrator. This file limit is the limit of the mail system 

and should not be used as a gauge for transaction volume. 

Page 11 
Email Generated From DLA Transaction Services

DLA-TS Generated Email Messages 

DLA-TS will deliver two types of Email messages to a user: 

1. Transactions routed to the user

2. Returning of exceptioned transactions and rejected Email files

The DLA-TS generated transaction Email will consist of two parts: The subject line and the 

enclosed Standard Logistics Transactions. There will be a ‘Newline’ control character after 

the Subject Line and each enclosed transaction. 

The subject line consists of four components: 

1. "Subject"

2. Enclosed transaction count

3. The closing "Military Standard Transactions Enclosed From"

4. "COMMRI" of activity originating the transaction

The "Subject" is the indicator for the heading of the enclosed transactions. Following the 

"Subject" will be a count for the number of enclosed transactions. The closing statement of 

"Military Standard Transactions Enclosed" will follow the enclosed transaction count. The 

"From COMMRI" will indicate the originating site. An example of the Subject line is as 

follows: 

XXXXX Military Standard Transactions Enclosed from "COMMRI"

Note: XXXXX will be a count of all enclosed Military Standard Transactions. 

DLA Transaction Services Routed Transaction Format 

All Routed Military Standard transactions delivered by DAASC to the user will be in the 

following format: 

Return-Path: <DIELOG@daas.dla.mil> 

Message-Id: <9301181712.AA14326@192.67.251.18> 

Date: Mon Jan 18 12:12:26 1997 

>From: DIELOG@daas.dla.mil (DAASC ------ --) 

To: RUSAHNJ@USERS.Email.HOST 

Subject: 00004 Military Standard Transactions For Review 

Enclosed From RUSAHNJ 

Page 12 
Page 13 

AE1S9MS6520007826469 SE00002W33M8S30499800RYL17C5ATK 06059 

AE1S9MU5930009267458 EA00001W81N7130480600RW33M8SKTK 13000 

AE1S9MS6505000599017 BT00001W33XTF30494002RYMEPHATK 13000 

AE1S9MS6505001538750 BT00001W33XTF30499013RYMEPHYATK 13000 

Exception/Reject Format 

All exceptioned Military Standard transactions, not processed by DLA-TS due to a validation 

failure and any Email file received in error at DLA-TS will be returned in an Email message 

as described below. The first record will be an error code followed by the returned 

transactions. 

Return-Path: <DIELOG@daas.dla.mil> 

Message-Id: <9301181712.AA14326@192.67.251.18> 

Date: Mon Jan 18 12:12:26 1997 

>From: DIELOG@daas.dla.mil (DAASC ------ --) 

To: RUSAHNJ@USERS.Email.HOST 

Subject: 00004 Military Standard Transactions For Review 

Enclosed From RUSAHNJ 

************DIELOG Input has format Errors************** 

A0AS9MS6520007826469 SE00002W33M8S30499800RYL17C5ATK 06059 

A0AS9MU5930009267458 EA00001W81N7130480600RW33M8SKTK 13000 

A0AS9MS6505000599017 BT00001W33XTF30494002RYMEPHATK 13000 

A0AS9MS6505001538750 BT00001W33XTF30499013RYMEPHYATK 13000