IN REPLY 

REFER TO 

DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060·6221 

January 07, 2013 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

SUBJECT: Approved Defense Logistics Management System (DLMS) Change (ADC) 1042, 

Revise Wide Area Workflow (W A WF) Advance Shipment Notice (ASN) to 

Accommodate DLA Interface for Reparable Government Furnished Property (GFP) 

(Supply/Logistics) 

The attached change to Defense Logistics Manual (DLM) 4000.25-M, Defense Logistics 

Management System (DLMS) is approved for joint implementation among DLA, WAWF, 

Defense Automatic Addressing System, and Global Exchange (GEX) February 2013. 

Adch·essees may direct questions to Ms. Ellen Hilert, DOD MILSTRIP Administrator, 

703-767-0676; DSN 427-0676; or, e-mail: ellen.hilert@dla.mil or Ms. Heidi Daverede, DOD 

MILSTRIP Alternate, 703-767-5111 ; DSN 427-5111 , email heidi.daverede@dla.mil. Others 

may direct questions to their Service or Agency designated Supply PRC representative. 

Attachment 

As stated 

cc: 

ODASD(SCI) 

Director 

DLA Logistics Management 

Standards Office 

Federal Recycling Program 0 Printed on Recycled Paper 
Attachment, ADC 1042

Page 1

Attachment to ADC 1042

Revise Wide Area Workflow (WAWF) Advance Shipment Notice (ASN) 

to Accommodate DLA Interface for Reparable

Government Furnished Property (GFP) 

1. ORIGINATING SERVICE/AGENCY: Defense Logistics Agency (DLA) HQ

2. SPONSOR: Defense Logistics Agency Business Integration Office, J335, 703-767-2531, 

DSN 427-2531

3. FUNCTIONAL AREA: 

a. Primary/Secondary Functional Area: Supply/Logistics

b. Primary/Secondary Functional Process: Government Furnished Property (GFP)

4. REFERENCES: 

a. Defense Federal Acquisition Regulation Supplement (DFARS) 252.211-7007. The 

updated clause defines expanded reporting requirements for Government-furnished property to 

include uniquely and non-uniquely identified items.

b. DFARS Procedures, Guidance and Information PGI 245.1 – General, revised 

December 12, 2012. Provides amplifying information to define government property, furnishing 

government property to contractors and transferring government property accountability. 

c. DODI 8320.04, Item Unique Identification (IUID) Standards for Tangible Personal 

Property, dated June 16, 2008, at: www.dtic.mil/whs/directives/corres/pdf/832004p.pdf. 

Established the DOD IUID Registry as the master data source for GFP and requires DOD 

Components to identify and track GFP using Unique Item Identifiers (UII) in transaction-derived 

data from electronic business transactions.

d. DODI 4161.02, Accountability and Management of Government Contract Property, 

dated April 27, 2012. Assigns responsibilities and provides procedures for Government contract

property in the custody of defense contractors and upon return of property to DOD. 

5. APPROVED CHANGE:

a. Brief Overview: This change establishes interim interface procedures to document

property movement of GFP from a contractor’s repair location to a DLA receiving activity. Use 

of DLMS transaction sets and mapping of data passed between the WAWF system and 
Attachment, ADC 1042

Page 2

Distribution Standard System (DSS) will provide source data updates to the DOD IUID Registry, 

including the GFP module. These changes support Financial Improvement Audit Readiness 

(FIAR) efforts to improve DOD property accountability. The long-term solution will require 

WAWF functionality to accept the DLMS 527R.

b. Background:

(1) The DOD Item Unique Identification (IUID) Registry, including the GFP module,

was established as a centralized repository to collect IUID and GFP data. 

(2) Property transfers must be reported electronically using Defense Logistics 

Management System (DLMS) transaction data sets. GFP data will be updated using the WAWF

system. The WAWF Property Transfer Document (PTD 856) (not the DLMS Supplement) used 

for this purpose is identified by Transaction Type Code TS, with guidance as follows:

“Use to indicate the shipment/movement of Government Property (from Government 

to Contractor, Contractor to Contractor, Contract to Contract, and Contractor to 

Government, Government to Government and to indicate shipment of Contractor 

Acquired Property (CAP) from Contractor to Government. Does not include shipment 

of new acquisition contract items from the selling contractor to the government.”

(3) WAWF requires reporting activities to include the contract/delivery order number, 

vendor-assigned shipment number, and Item Unique Identification (IUID), if applicable, when

reporting transfer of GFP.

(4) The DLA DSS/WAWF functional interface currently supports receipt acceptance 

of new procurement receipts. In support of this process, DSS receives the WAWF Advance 

Shipment Notice (ASN 856) using the DLMS Supplement format. This change expands this 

DSS/WAWF interface capability to report a GFP custody transfer from a contractor’s facility to 

a government facility and update the DOD IUID Registry for GFP receipt.

c. Summary of Interim Procedures and Processes: The approved procedures will 

utilize the WAWF PTD 856, the WAWF Advance Shipment Notice (ASN 856), and the DLMS

Receipt (527R) transaction sets.

(1) A Global Exchange (GEX) correlation database will be established to transmit 

GFP and receipt data across functional interfaces and to the IUID Registry for update of the GFP 

module.

(2) The GEX will map the WAWF PTD 856 to data fields in the WAWF ASN 856

when the WAWF PTD is the result of Government acceptance of the repair service as reported to 
Attachment, ADC 1042

Page 3

WAWF via the contractor input Reparable Receiving Report (RRR) 856. GEX will limit PTD 

data fields to those required to process the WAWF GFP ASN transaction. The newly formatted 

GFP ASN (also referred to as a pseudo ASN) will be identified by unique coding in the 

beginning segment to differentiate it from other 856 transactions associated with WAWF and 

will be sent to DSS. 

Staffing Note: This interim solution is for a specific segment of the GFP business procedures

applicable to the contractor’s return of a reparable. Full integration of PTD business procedures 

will be addressed via GFP Data Reporting Phase II. 

(3) DSS will use the Beginning Segment Transaction Type Code TS Property 

Transfer (BSN06) with Status Reason Code 036 Automatic Conversion (BSN07) to ensure the 

depot receiver selects the appropriate receipt transaction format. DSS will generate a receipt 

(DLMS 527R) transaction with a LIN01 Code E equivalent to MILSTRAP Document Identifier 

Code (DIC) D4M, Materiel Receipt - Procurement Instrument Source (Repair or NonDestructive Test/ Evaluation). DIC D4M identifies the return to inventory of items previously 

issued to a commercial activity for repair or nondestructive test/evaluation.

(4) DLA Transaction Services will send WAWF a copy of the DSS-generated 527R

Receipts via GEX when the receipt transaction includes LIN01 Code E/DIC D4M. 

(5) GEX will map the 527R data into the WAWF 856 GFP Receipt transaction to 

update the WAWF GFP Property Transfer Document (PTD) records and the DOD IUID Registry 

for GFP receipt.

d. Procedures and Detailed Changes:

(1) The presence of the Transaction Type Code TS with Status Reason Code 036 in 

the Beginning Segment of the WAWF GFP ASN EDI 856 will be interpreted by DSS as a

contractor’s return of a reparable GFP to a DLA Distribution Depot location. 

(2) The GEX correlation look-up table will match DLA Distribution Depot Routing 

Identifier Code (RIC) to the corresponding DLA Distribution Depot ship-to DoDAAC. This 

information is required by the WAWF system to update the GFP record. 

(3) The GEX correlation data base will use the DSS receipt data including contract 

number, call/delivery order number, shipment number, and contract line item number to find the 

associated WAWF GFP PTD. When a match is found WAWF will update the WAWF GFP 

record and transmit the updated receipt to the IUID Registry for GFP receipt.

Staffing Note: GEX will not pass the condition code of the GFP item to WAWF.
Attachment, ADC 1042

Page 4

(4) Depot receivers will be required to utilize the WAWF website to identify which 

unique item identifier (UII) values were received and/or to close out the receipt when the

received quantity is less than the contractor’s shipped quantity if UII. Depot receivers must 

submit a Supply Discrepancy Report (SDR) for any GFP shipment when the quantity received 

is different than quantity shipped or the IUID data does not match when compared to the 

WAWF ASN data.

(5) DLA Distribution Depots will include the UII in the DLMS 527R/DIC D4M 

when machine readable at time of receipt.

e. Transaction Flow: See Enclosure 1.

f. DLMS Supplement Revisions: The DLMS Supplements for the DLMS 856 ASN 

and 527R Receipt are updated as shown in Enclosure 2.

g. Revisions to DLM 4000.25 DLMS Manual: Requires update to DLM 4000.25-4, 

Defense Automatic Addressing System (DAAS).

h. Data Mapping of DLMS 856 Transactions: See Enclosure 3.

i. Proposed Change Comment Resolution: See Enclosure 4.

6. REASON FOR CHANGE: Implementation of full WAWF property transfer capability is 

not within the scope of current capability and would require significant programming resources. 

This change will provide an interim solution to document the custody transfers of GFP from the 

contractor’s facility to a DLA storage facility. It supports DOD’s policy requirements for 

property accountability and the FIAR mandate. 

7. ADVANTAGE: Provides property movement in-transit visibility and the impetus to report 

custody location of GFP to the DOD IUID Registry, including the GFP module. Facilitates 

receipt processing if the vendor employs passive Radio Frequency Identification (pRFID) for the 

shipment and incorporates the pRFID tag values in the WAWF transaction. Using the WAWF 

856 ASN format and the DLMS 527R will significantly reduce program changes for DSS 

allowing for a rapid implementation.

8. DISADVANTAGE: Will require DLA receivers to access the WAWF system to identify 

which items with IUID were received when less than full contractor-shipped quantity is received. 

This disadvantage is temporary. Once DSS updates the 527R capabilities, the DLA receiver will 

be able to identify which items with IUID were received.
Attachment, ADC 1042

Page 5

9. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW 

DEVELOPMENT:

a. The WAWF system will continue to apply current accumulation business rules to 

allow incremental receipt processing for GFP receipts, e.g., the contractor ships a GFP quantity 

of four (4); however, the four GFP items are received via two separate receipt transactions:

(1) WAWF system will apply the auto-close rule when partial quantity receipts 

are posted to a GFP record and the receipt has no IUID/UII reported. The WAWF auto-close

rule is applied when the WAWF record has received no receipt updates for a period of 15 days 

from the Date of Last Activity (DOLA). 

(2) The WAWF system will not close any GFP record when the item shipped has

IUID/UII until the full shipment quantity is reported or an authorized WAWF user manually 

closes the GFP record via the WAWF website. 

b. GEX will screen out any DLA Distribution Depot receipts forwarded by DLA 

Transaction Services but not associated with a WAWF PTD. Prior to conversion and forwarding 

to WAWF, GEX will match DLMS 527R receipts against a table of PTDs previously converted 

to the pseudo ASN format and sent to DSS. Receipts appropriate for conversion/forwarding will 

be determined by matching on contract number, call/order number, and CLIN. Any unmatched 

receipts will be dropped. 

10. ADDITIONAL FUNCTIONAL REQUIREMENTS:

a. The DSS generated receipt for reparable GFP will include the UII when machine 

readable and readily available.

b. The WAWF system will populate the ‘Inspect By DoDAAC’ into the ‘Services Ship 

To’ field when the PTD is for a source inspected and accepted reparable item. 

Staffing Note: The WAWF Services Ship To is a misleading term identifying the organization 

“receiving” the repair; it is comparable to the acceptor. It does not refer to physical shipment of 

the repaired item. Since DSS does not perform acceptance of repairs at this time, WAWF will 

ensure that the activity responsible for inspection/acceptance is identified as the Service Ship To.

11. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Target implementation is 

February 2013. Inclusion of IUID data in the DLMS 527R may require subsequent phased 

implementation.
Attachment, ADC 1042

Page 6

12. IMPACT: 

a. Data Elements: The data element Transaction Type Code is updated to include the 

value TS identifying a Property Transfer Document with a clarifying note indicating restricted 

use under the DLMS ASN. The data element Status Reason Code is updated to include the value 

036 Automatic Conversion to clarify that special mapping to perpetuate WAWF PTD data to the 

WAWF ASN is employed to forward shipment notification to DOD activities per agreement 

under ADC 1042.

b. DLA Transaction Services: DAAS will direct a copy of each DSS-generated 527R 

citing LIN01 Code E/DIC D4M to the GEX for conversion to the required WAWF GFP receipt 

format (the transaction itself will not identify WAWF as a party-to-receive copy).

c. Non-DLA Logistics Management Standards Office Publications: Requires update 

to WAWF documentation and may require update to DLA internal publications.

d. Systems/Applications: 

(1) DSS: 

(a) DSS must be updated to recognize the WAWF PTD variant mapped to 

the ASN.

(b) IUID reporting capability must be implemented for the DLMS 

527R/DIC D4M.

(2) WAWF System: Minor updates are required to populate the ‘Inspect By’ 

DoDAAC into the ‘Services Ship To’ data field, allow DLA Distribution Depot DoDAACs to 

act as the Property Ship To in the PTD, and to incorporate the accumulation logic into the 

property transfer process.

(3) GEX: Through the reutilization of existing interfaces and transactional data, 

GEX will support GFP business procedures and provide an interim pathway to update GFP 

records. Refer to Enclosure 1 for GEX requirements.
Enclosure 1, ADC 1042

Page 1

Enclosure 1, Transaction Flow

WAWF

DSS

GEX

DLA Transaction 

Services

Vendor Creates 

Source/Source 

Reparables

Receiving 

Report (RRR)

Inspector/ 

Acceptor 

accepts RRR

Property 

Transfer 

856_GFP

PIN, SPIIN, 

CLIN

Pseudo 

856_ASN

Store

Pseudo 

856_ASN

DSS User 

receives Item

DSS User 

receives 

856_ASN

DSS creates 

D4M EDI 527R

527R

527R

Match

Transform

Property 

Transfer 

Receipt 

856_GFP

Transform

Accumulate 

Property 

Transfer 

Receipts

Close RRR. 

Send UID GFP 

Extract and 

PSN Extract

*For RRR with IUID:

Accumulate until 

entire quantity is 

receipted or user 

closes out manually 

via web interface 

*For RRR without IUID:

Accumulate until 15 

days has elapsed from 

date of last activity
Enclosure 2, ADC 1042

Page 1

Enclosure 2, DLMS Supplement Revisions

a. Revise the DLMS 527R as follows:

b. Revise the DLMS 856 as follows:

# Location Revision to DLMS 527R

Receipt, Inquiry Response, and MRA

Reason

1. DLMS 

Introductory 

Notes

Add to existing DLMS introductory note 7:

- ADC 1042, Revise Wide Area Workflow (WAWF) Advance 

Shipment Notice (ASN) to Accommodate DLA Interface for 

Reparable Government Furnished Property (GFP) 

Identifies change 

associated with the 

transaction.

2. 2/REF01/250 Add new DLMS note 3 and renumber the existing note 3:

U3 Unique Supplier Identification Number (USIN)

DLMS Note: 

1. Use to identify the UII. Place UII value in REF03. The UII may 

not exceed 50 characters in accordance with UID Policy. A data 

maintenance action was approved in version 5020. The approved

code/name is "UII - Department of Defense Unique Item Identifier.

2. Authorized DLMS enhancement for DLA Disposition Services 

use in receipt and historical receipt to identify the UII for SA/LW or 

industrial plant equipment. The UII is for use by both the DLA 

Disposition Services Field Offices and the DLA Disposition 

Services ICP. Refer to ADC 442.

3. Authorized DLMS enhancement for DLA Distribution Depot 

receipt processing to identify the UII for reparable items returned 

to DoD inventory by repair contractors. Refer to ADC 1042.

4. Authorized DLMS migration enhancement. See DLMS 

introductory note 5g.

Clarifies limited use.

# Location Revision to DLMS 856 

Advance Shipment Notice (ASN)

Reason

1. DLMS 

Introductory 

Notes

Insert new DLMS Introductory Note 3 (and renumber remaining 

notes): 

3. This transaction may be used to forward Property Transfer 

Document (PTD) information submitted to WAWF by a contractor

for return of Government Furnished Property to DoD inventory. 

This is an interim use pending full implementation of the WAWF 

PTD facilitated by Global Exchange (GEX) conversion mapping.

Identifies an additional 

use of the transaction 

2. DLMS 

Introductory 

Notes

Add to existing DLMS introductory note 8:

- ADC 1042, Revise Wide Area Workflow (WAWF) Advance 

Shipment Notice (ASN) to Accommodate DLA Interface for 

Reparable Government Furnished Property (GFP) 

Identifies change 

associated with the 

transaction.
Enclosure 2, ADC 1042

Page 2

# Location Revision to DLMS 856 

Advance Shipment Notice (ASN)

Reason

3. 1/BSN06/20

Beginning 

Segment

Add Qualifier TS and associated Federal and DLMS note:

TS Transfer Statement

Federal Note: Use to indicate the shipment/movement of 

Government Property (from Government to Contractor, Contractor 

to Contractor, Contract to Contract, Contractor to Government,

Government to Government and to indicate shipment of Contractor 

Acquired Property (CAP) from Contractor to Government. Does 

not include shipment of new acquisition contract items from the 

selling contractor to the government.

DLMS Note: 

1. This DLMS Supplement does not contain full WAWF property 

transfer functionality. Refer to the WAWF guide for 

implementation guidance for the Property Transfer Document 

(PTD).

2. Use by agreement only with BSN07= 036 for interim procedures 

supporting PTD implementation. Refer to ADC 1042.

Perpetuates existing 856 

Federal Note to the 

DLMS Supplement.

Clarifies limited usage 

restriction.

4. 1/BSN07/20 Open BSN07 to add Qualifier 036 and associated DLMS note: 

036 Automatic Conversion

DLMS Note:

1. Use only with BSN06 Code TS to indicate this transaction is a 

variant of the full WAWF PTD used on an interim basis to facilitate 

DLMS processing of GFP receipts by DoD activities pending full 

integration of WAWF. This variant perpetuates the PTD Qualifier 

TS and PTD information in the ASN format using GEX conversion 

mapping. (Also referred to as a pseudo ASN.)

2. Use to indicate when transaction is provided to report location 

movement of GFP. This procedure updates the Accountable 

Property System of Record with the change of GFP custodial 

location. Refer to ADC 1042.

Provides reference to 

indicate WAWF ASN is 

transmitting property 

transfer data.
Enclosure 3, ADC 1042

Page 1

Enclosure 3, Data Mapping of DLMS 856 Transactions

a. WAWF GFP PTD conversion to pseudo ASN for GFP Property Transfer for transmission to 

DLA Distribution Depot:

DLMS 856 ASN X12 TO DSS DLMS 856 GFP PTD X12

1/BSN/020

BSN06

Transaction

Type Code

ID 2/2 O BSN06 Transaction 

Type code

ID 2/2 O TS Transfer 

Statement

Adding as new

Data element to 

indicate property 

location transfer

2/N1/220

N101

Entity Identifier

Code

ID 2/3 M SF= 

Ship 

From

ST = 

Ship to

2/N1/220 

N101

Entity 

Identifier 

Code

ID 2/3 M PG= Prime 

Contractor 

(shipper) 

AQ=Account of 

Destination Party 

(Receiver)

PG mapped to SF 

AQ mapped to ST

2/PRF/050

PRF01

Purchase Order 

Number

AN 1/22 M 2/GF/330 

GF03

Furnished 

Goods and 

Services

Contract 

Number

AN 1/19 C Use to identify the 

GFP contract 

number

GF03 mapped to 

PRF01

PRF06 Contract 

Number

AN 1/30 O GF06 Reference 

Number

AN 1/30 O Reference 

Procurement 

Instrument 

Number

Gf06 Reference 

number will be 

mapped to PRF06

2/DTM/200

DTM01

Date/Time 

Qualifier

ID 3/3 M 011 

Shipped

2/DTM/200

DTM01

Date/Time 

Qualifier

ID 3/3 M GFP 35 = 

Delivered on this 

date

WAWF will send 011 

date shipped. WAWF 

ASN doesn’t carry 

DTM code of 35

b. DLMS 527R Receipt conversion to WAWF user defined file (UDF) for transmission to WAWF:

WAWF UDF 856 DLMS 527R X12

1/BSN/020

BSN01

Transaction 

Set Purpose 

Code

ID 2/2 M 00 -

Original

1/BR/020

BR01

Transaction 

Set Purpose 

Code

ID 2/2 M 00 - Original Beginning Mat 

Mgmt. segment (BR) 

will be mapped to 

Beginning segment 

for ship notice 

(BSN)

BSN02 Shipment 

Identification

AN 2/30 M Shipment 

Number

2/N9/090 

N902

Reference 

Identification

AN 1/30 O SI = Shipper’s 

Identifying 

Number (SID) 

Shipment 

Number

N9 Reference 

Identification 

shipment number 

data moves to 

BSN02

BSN03 Date 

transaction is 

created

DT 8/8 M CCYYM

MDD 

Transmiss

ion date

1/BR/020 

BR03

Date 

transaction 

was created

DT 8/8 M CCYYMMDD

BSN04 Time - clock T

M

4/8 M HHMM BR09 Time- clock TM 4/8 M HHMM

BSN06 Transaction 

Type Code

ID 2/2 O TS –

Transfer 

Statement 

to indicate 

transfer of 

GFP

BR02 Transaction 

Type Code

ID 2/2 O D4M Receipt D4M data will be 

mapped using 

LQ01=0 

(Transaction Type 

Code=D4 and 

LIN01=E (Receipt to 

inventory of items 

previously issued to 

a commercial or 

government activity 

for repair or 

nondestructive 

test/evaluation) 
Enclosure 3, ADC 1042

Page 2

WAWF UDF 856 DLMS 527R X12

2/N1/220 

N101

Entity 

Identifier 

Code

ID 2/3 M ST – Ship 

To

1/N1/070

N101

Entity 

Identifier 

Code

ID 2/3 M RC – Receiving 

Location

N103 Identification 

Code 

Qualifier

ID 1/2 M 10 N103 Identification 

Code 

Qualifier

ID 1/2 X M4 DoD 

Routing 

Identifier Code 

(RIC)

GEX correlation 

table will convert the

Distribution Depot 

RIC to DLA 

Distribution Depot 

DoDAACs for the 

WAWF system

2/DTM/200

DTM01

Date/Time 

Qualifier

ID 3/3 M 050 

Received

1/G62/050

G6201

Date/Time ID 2/2 M 35 = Delivered 

on this date

527R does not use 

050 for receipt date

2/GF/330

GF03

Furnished 

Goods and 

Services

AN 1/19 C Contract 

Number

2/CS/020

CS01

Contract 

Number

AN 1/30 O Contract 

number

GF07 Delivery 

Order 

Number 

AN 4/17 O Delivery 

order 

number

CS03 Release 

Number

AN 1/30 O Delivery Order 

Number 

2/LIN/020 

LIN01

Assigned 

Identification

, CLIN/SLIN 

or ELIN

AN 4/6 M 2/CS/020 

CS05

CLIN AN 1/30 O CS04 C7 = 

Contract Line 

Item Number

LIN02 Product/Svc 

ID Qualifier

ID 2/2 M FS = NSN 2/LIN/020 

LIN02

Product/Svc 

ID Qualifier

ID 2/2 M FS =NSN

LIN03 Product/Svc 

ID

AN 1/32 M FS = NSN LIN03 Product/Svc 

ID

AN 1/48 X NSN 

SN102 Number of 

Units 

Shipped

N 1/10 M RCD02 Quantity Units 

Received or 

Accepted

R 1/9 X Quantity 

Received

SN102 used in 

property transfer for 

quantity shipped or

received.
Enclosure 4, ADC 1042

Page 1

Enclosure 4, GEX Requirements

GEX Requirements

# WAWF 856 ASN WAWF 856 PTD ASN DLMS 527R Receipt Data Mapping Notes

1. Beginning Segment for 

Ship Notice Pos. 

1/BSN/020

BSN06=TS Transfer 

Statement

BSN07=036 Automatic 

Conversion

GEX will enter TS in BSN06 data 

field of the WAWF ASN to 

indicate the transaction set is to 

record GFP movement from a 

contractor’s location to a DLA 

receiving activity. GEX will open 

BSN07 identifying 036 to

distinguish this variant of the TS 

from the standard WAWF PTD.

2. Beginning Segment for 

Shipment Identification 

1/BSN/020

BSN02=Shipment 

number

Beginning Segment for 

Shipment Identification 

1/BSN/020 

BSN02=Shipment 

number

N9 – Reference 

Identification

2/N9/090 (N901=SI)

GEX will map 527R shipment 

number data to WAWF 856

N901=Shipment Identifier data to 

BSN02=shipment number

3. PRF Segment –

Purchase Order 

Reference, 

1/PRF/050 

PRF01=Contract 

number

GF Segment –

Furnished Goods and 

Services 2/GF/330

GF03=Contract number

GF Segment, Furnished 

Goods and Services

2/GF/330 is mapped to 

1/PRF/050

GEX will map the Contract data 

provided in the GF Segment to 

the PRF Segment of the WAWF 

856 ASN

4. PID Segment 

Product/Item 

Description 

2/PID/070

PID Segment 

Product/Item 

Description 

2/PID/070

PID Segment is not 

available in 527R receipt 

- NSN is used in lieu of

nomenclature

GEX will use FLIS data to 

populate NSN nomenclature to 

update the WAWF 856 ASN 

record with receipt data

Staffing Note: Currently, there is 

no interface with FLIS; this aspect 

of the requirement will be 

deferred for later implementation.

Pending this interface the PID,

GEX will insert the placeholder: 

“Description not provided by 

DSS”.

5. DTM Segment 

Date/Time Reference 

2/DTM/200

DTM Segment 

Date/Time Reference, 

2/DTM/200

G62 Segment 

Date/Time 

GEX will map the 527R 

G6201=35 (Delivered on this 

date) to WAWF 856 DTM 

Segment to update the ASN with 

the goods receipt date
Enclosure 4, ADC 1042

Page 2

# WAWF 856 ASN WAWF 856 PTD ASN DLMS 527R Receipt Data Mapping Notes

6. N1 Segment 

Name

2/N1/220

N101= SF (Ship From) 

N101= ST (Ship To)

N1 Segment 

Name

2/N1/220

PG=Prime Contractor 

(shipper)

AQ=Account of 

Destination Party 

(Receiver)

GEX will map WAWF 856 ASN 

Name Segment going to

Receiving activity

N101= ST (AQ/Receiver) 

N101= SF (PG/Prime Contractor)

Ship From and Ship To will be

the only identifier codes used

7. N1 Segment

Name

2/N1/220

N101

N1 Segment 

Name

2/N1/220

N101

N1 Segment 

Name

1/N1/070

N103=M4 (DOD 

Routing Identifier Code 

(RIC) 

N104=RIC of DLA 

Receiving Activity

GEX will map 527R receipt data 

from a DLA activity to the 

WAWF GFP Receipt. RIC data is 

used to report location. WAWF 

identifies locations via 

DoDAACs. GEX will translate 

the RIC to a DoDAAC using a 

correlation table to update the 

WAWF ASN records

8.

N1 Segment

Name

1/N1/220

N1 Segment

Name

1/N1/070

N101=RC 

GEX will map 527R Name 

Segment custody and ownership 

data from the Receiving Activity

to the WAWF 856 GFP Receipt

Name Segment to update the GFP 

record. 

N101=RC (Receiving Location)

9. N1 Segment

Name

2/N1/220

N1 Segment

Name

1/N1/070

N101=Z4

GEX will map 527R Name 

Segment custody and ownership 

data from the Receiving Activity 

to the WAWF 856 GFP Receipt 

Name Segment to update the GFP 

record.

N101=Z4 (Owning Inventory 

Control Point)

10. PER Segment

Administration 

Communications 

Contact

2/PER/270

PER Segment 

Administration 

Communications 

Contact 

2/PER/270

PER Information not 

available in 527R receipt

GEX will enter a generic value in 

the PER segment

11. LIN Segment

Item Detail 2/LIN/020

LIN Segment

Item Detail 2/LIN/020

CS Contract Summary

2/CS05/020

GEX will map the line item 

number appearing in CS05 of the 

527R to the LIN01 line item field 

of the WAWF 856 ASN
Enclosure 5, ADC 1042

Page 1

Enclosure 5, Proposed Change Comment Resolution

Submitter Response/Comment Resolution

1. DLA Concur Noted.

2. Army Concur Noted.

3. Navy Concur

Preliminary comments: Who will be putting 

something into WAWF to initiate this?

Are we expecting the Contractor who has 

initial custody of the GFP to do something? 

I'm wondering if it would be something done 

in CAV, that might eventually feed into 

WAWF?

Or would the DLA Depot initiate the WAWF 

transaction?

Noted.

The contractor is required to submit 

the WAWF 856 Reparable 

Receiving Report (RRR) when they 

have finished repair (normally the 

item is about to be shipped to a 

DLA depot for storage, or could be 

shipped directly to a Navy 

customer). The contractor will not 

get paid until the service performed 

is accepted. Once the service is 

accepted WAWF converts the RRR 

to a property transfer (another 

flavor of 856) because that is how

the registry and Service property 

record systems get updated. In the

past these property transfers were 

excluded from DLA Depots partly

because DLA Depots are only 

programmed to process WAWF 

Advance Shipment Notice 856 

transactions (for new procurement). 

So we are asking WAWF to send us 

the property transfer for repaired 

items going to a depot, but to make 

it look more like the ASN.

Then on the flip side, when the 

MILSTRAP/DLMS receipt is 

created by the depot for the 

repaired item, DLA TS will send to 

GEX for conversion to an 856 GFP 

receipt (because WAWF cannot yet 

accept a DLMS 527R and WAWF

needs to close out the shipment 

record).

4. Air Force Concur with comments on PDC 1042 to 

change WAWF ASN to interface with DLA 

for managing shipments of reparable GFP 

Noted.
Enclosure 5, ADC 1042

Page 2

Submitter Response/Comment Resolution

to/from contact facilities. 

Additionally, for information. Interfaces 

between WAWF and CAS may be required as 

a material solution for receiving updates for 

reparable GFP at contact facilities. AF is 

working on efforts to devise a single Air 

Force solution to GFP management. 

Request 24 month lead time prior to 

implementation, so we can plan and budget 

for this IT change.

5. Marine Corps Concur Noted.

6. USTRANSCO

M

Abstain. There is no impact to 

USTRANSCOM systems based on this 

change.

Noted.

7. ODASD(SCI) No concerns Noted.

8. GEX GEX only has one outstanding issue with the 

PDC. We had mentioned before that the 

mapping below was not a part of the original 

requirements:

2/PID/070 PID Segment Product/Item 

Description 

GEX will use FLIS data to populate the NSN 

nomenclature to update the WAWF 856 ASN 

record with receipt data.

Currently, we do not have an interface to 

FLIS to be able to populate this data. The 

PID will have the placeholder: “Description 

not provided by DSS”.

We can keep it as a part of the DLMS 

Change, but it will be a future enhancement, 

and out of scope for phase 1.

Noted. ADC updated.

9. DLA 

Transaction 

Services

DLA Transaction Services will be ready to 

send the DLMS 527R information copy to 

GEX/WAWF in February .

Noted.