ADC 276 

Attachment 

1

 

ATTACHMENT TO ADC 276 

Addition of Party to Receive Copy to Support Requirements for TEWLS Requisitions 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Agency (DLA)

b. Originator: DLA Order Fulfillment

2. FUNCTIONAL AREA: Primary: Supply/Logistics.

3. REFERENCES: Defense Logistics Agency and Theater Enterprise-Wide Logistics System 

(TEWLS) Army Medical Material Agreement (AMMA) Functional Requirements Document. 

4. REQUESTED CHANGE: 

 a. Description of Change: This change establishes capability to identify a “Party to Receive 

Copy” in a requisition, modification, and follow-up, and subsequent transmission of a copy transaction 

to the identified party by the Defense Automatic Addressing System (DAAS). This allows visibility of 

the General Services Administration (GSA)/Non-DLA requisitions for medical and industrial kitting 

component parts, when DLA is acquiring the parts, as the Medical Executive Agent, in support of 

Army under the TEWLS/AMMA business model. 

b. Background: The TEWLS AMMA process will be implemented with Enterprise Business 

Systems (EBS) in FY08. DLA acquires parts by the Army placing orders for items via Defense 

Medical Logistics Standard Support (DMLSS)/TEWLS. The Party to Receive Copy will be used 

between the Army and DLA for their integrated set assembly program, when an assembly component 

part being ordered by the Army is not managed by DLA, and DLA is acquiring it in support of Army 

medical mission.

(1) The Army-placed orders will use a third party fund code to be used with Signal Code L, 

which will cause GSA and others to bill DLA for the ordered materiel. 

(2) DLA requires a copy of these orders placed on other Supply Sources, with this new fund 

code for proper financial accounting, and to obligate funds prior to billing. Adding the capability to 

identify a party to receive a copy in the DLMS requisition format will support this process, allowing 

DAAS to forward the copy transaction to DLA. 

c. Follow-on Requirements. DLA is to be identified on the order as a status recipient (e.g., via 

a Distribution Code). In that manner, if backorders, cancellations, rejections, or modifications took 

place, DLA would know this via receiving the associated status generated by the Source of Supply 

(SoS) such as GSA. 

(1) In a pure DLMS world, the Army customer would just need to add EBS as a party to 

receive status (functionality currently in the DLMS Transaction). However, since DAAS will convert 

the Army TEWLS 511R to an 80 rp A0_ transaction for a non-DLA SoS, this technique could not be 
ADC 276 

Attachment 

2

used (as the DLMS party to receive status does not fit in the MILS format). Initially, DLA considered 

putting their DoDAAC in the supplementary address field, and requiring Media and Status Code F, 

which indicates 100 percent status to requisitioner and the supplementary address. However, the 

Army needs the supplementary address field to identify the ship-to for these orders. 

(2) Distribution Code. Based on the above, Army/DLA must establish a new 

distribution code for these orders which would identify DLA. That way, DAAS will provide status to 

the distribution code IAW MILSTRIP rules. If the Army requires a distribution code in these orders, 

the second character of the distribution code (rp 55 in the 80 rp format) may be used to identify DLA, 

and DAAS will provide status based on this coding until DLMS implementation is complete. 

 c. Procedures. Revise DS 511R, 511M, and 869F as shown in the table below: 

Item 

# 

Location DS 511R and 511M 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 276 to DLMS Introductory note 5: 

- ADC 276, Addition of Party to Receive Copy to 

Support Requirements for Theater Enterprise-Wide 

Logistics System (TEWLS) Requisitions. 

Identifies DLMS 

Changes included in the 

DLMS Supplement. 

2. 2/N101/180 Revise to add qualifier and note: 

PK Party to Receive Copy 

DLMS note: 

1. Use as needed to identify an organization to be 

provided a copy of this transaction. Use with N103, 

qualifier M4 (Routing Identifier) and N106, qualifier 

To (Message To). 

2. Must be used between Army and DLA for their 

integrated set assembly program, when an assembly 

component part being ordered by the Army is not 

managed by DLA, and DLA is acquiring it in support 

of the Army medical mission. 

3. DLMS enhancement; see introductory DLMS 

Note 3a.

Supports functionality 

for DAAS generation of 

a copy transaction 

required under AMMA. 

May have wider use in 

other functional areas. 

 
ADC 276 

Attachment 

3

Item 

# 

Location DS 869F 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 276 to DLMS Introductory note 5: 

- ADC 276, Addition of Party to Receive Copy to 

Support Requirements for Theater Enterprise-Wide 

Logistics System (TEWLS) Requisitions. 

Identifies DLMS 

Changes included in the 

DLMS Supplement. 

2. 2/N101/110 Revise to add qualifier and note: 

PK Party to Receive Copy 

DLMS note: 

1. Use as needed to identify an organization to be 

provided a copy of this transaction. Use with N103, 

qualifier M4 (Routing Identifier); and, N106, 

qualifier To (Message To). 

2. Must be used between Army and DLA for their 

integrated set assembly program, when an assembly 

component part being ordered by the Army is not 

managed by DLA, and DLA is acquiring it in support 

of the Army medical mission. 

3. DLMS enhancement; see introductory DLMS 

Note 3a.

Supports functionality 

for DAAS generation of 

a copy transaction 

required under AMMA. 

May have wider use in 

other functional areas. 

d. DAASC Processing: DAASC must respond to the inclusion of the new qualifier and forward a 

copy of the transaction to the identified party. 

 e. Additional Impact: Requires establishment of a new Distribution Code (unless other 

alternative is identified prior to implementation).

 f. Alternatives: 

 (1) DLA has stated that EBS will not be able to support the TEWLS processes using the 

EDI 511R without this change, and will need to consider nonstandard options. 

 (2) It is anticipated that eventually this process will need to be reevaluated when the Financial 

Management Regulation (FMR) and Business Enterprise Architecture (BEA) establish a requirement 

for an upfront check to ensure a commitment has been established. 

 (3) Alternative Mapping. The possible addition of a beginning segment code indicating that 

the requisition is a copy, and not an active requisition, was discussed and considered unnecessary. If 

added in addition to the 'PK' qualifier in the N1 segment, it becomes somewhat redundant, and requires 

a special edit to be built by DAAS. That is, in a pure DLMS world, DAAS would need to send one 
ADC 276 

Attachment 

4

version of the 511R on to the Source of Supply, without the beginning segment code indicating ‘copy,’ 

and a second version of the 511R with the 'copy' code in the beginning segment, to the recipient of the 

copy as indicated in the N1 segment. If DLA determines it would be better to have this code in the 

beginning segment, it could be pursued. However, at this time it is understood that EBS would build 

edits identifying the order as a 'copy' versus a 'live' order, based on the N1 segment, which will have 

the qualifier for 'copy,' and the RIC SMS as the to RIC to receive the 'copy'. If DLA can key on this, 

then no special DAAS edit will be required, and the order can be processed based on the coding alone.

5. REASON FOR CHANGE: EBS requires the Party to Receive Copy in order to receive and 

process TEWLS requisition transactions, and identify components purchased with DWCF which are 

not DLA managed. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: EBS and TEWLS will be able to comply with DLMS standards for the 

TEWLS/AMMA issue processes.

b. Disadvantages: N/A.