1 of 10

ADC 313

Attachment

ATTACHMENT TO ADC 313

Revisions to DLMS 527R to Add Code for MILSTRAP DRB Functionality and to Address Enhancement 

for Advice Codes Used with 527R Receipt and Response to Inquiry for Materiel Receipt 

(Supply/MILSTRIP/DLMS)

1. ORIGINATOR:

a. Service/Agency: DLA Logistics Management Standards 

 b. Originator: Ms. Mary Jane Johnson, DOD MILSTRAP Administrator, e-mail: 

Mary.Jane.Johnson@dla.mil; (703) 767-0677; and, DSN 427-0677.

2. FUNCTIONAL AREA: Primary: Supply/MILSTRIP/DLMS Receipt/DLMS MRA

3. REFERENCES: 

a. DOD 4000.25-2-M, Military Standard Transaction Reporting and Accounting 

Procedures (MILSTRAP)

b. Modernization of Defense Logistics Systems (MODELS) enhancement number 90-010

c. DOD 4000.25-M, DLMS, Volume 2 (Supply), http://www2.dla.mil/j6/dlmso/elibrary/manuals/dlms/v2.asp

d. DOD 4000.25-1-M, Military Standard Requisitioning and Issue Procedures (MILSTRIP), 

http://www2.dla.mil/j-6/dlmso/elibrary/Manuals/MILSTRIP/Default.asp

e. DLMSO memorandum, December 24, 2008, subject: Request for Implementation Date for 

ADC 313, Revisions to DLMS 527R for Materiel Receipt Acknowledgement (MRA) to Add Code 

for MILSTRAP Document Identifier (DI) Code DRB Functionality and to Address Enhancement for 

Advice Codes Used with 527R Receipt and 527R Response to Inquiry for Materiel Receipt (Supply), 

http://www2.dla.mil/j-6/dlmso/elibrary/changes/DLMS/RFID/RFID_ADC313_DS527R.pdf

f. DLMSO memorandum, July 2, 2010, subject: ADC 387, DLMS Enhancement: DLMS 

Supplement (DS) 846A Asset Reclassification Transaction and Associated Procedures, and 

Administrative Update to DS 947I Inventory Adjustment (Supply)

g. DLMS Data Dictionary, http://www.dla.mil/j-6/dlmso/eApplications/LogDataAdmin/dlmsdicdir.asp

 h. DOD 4140.1-R, DOD Supply Chain Materiel Management Regulation, available at: 

www.dtic.mil/whs/directives/corres/pdf/414001r.pdf

4. APPROVED CHANGE DESCRIPTION: This change addresses two separate and distinct 

requirements as follows:

a. Provides a new DLMS 527R beginning segment action code to provide functionality of 

MILSTRAP (reference 3a) Document Identifier Code (DIC) DRB-MRA Reply to Follow-up. In 
2 of 10

ADC 313

Attachment

the original DLMS 527R design for MRA, the function that an MRA was sent in response to a 

followup was not incorporated by intent. The current MILSTRAP Administrator later 

reconsidered that decision in favor of including the DRB functionality. Initially the MILSTRAP 

Administrator anticipated using an advice code to identify that the MRA was in response to a 

followup. The DLMS 527R advice code field was updated with a DLMS note to reflect this, but 

an advice code was never assigned for that function. Upon further consideration, the administrator 

determined a beginning segment level code would better address the DIC DRB functionality.

Accordingly, this change provides for use of 527R beginning segment (BR06) Action Code V–

Respond, used in conjunction with BR02 Transaction Type Code for MRA (Transaction Type 

Code TH), to indicate that an MRA is being sent in response to an MRA follow-up.

b. Highlights the procedures for a 1990 MODELS (now known as DLMS) enhancement 

(reference 3b) for use of advice codes with DLMS 527R receipt transaction and with the DLMS 

527R response to inquiry for materiel receipt transaction. This change also updates the 

enhancement to add an additional advice code for use with ‘response to inquiry for materiel 

receipt’ to identify when the storage activity has no receipt in process but there is a Prepositioned 

Materiel Receipt (PMR) file. This change also updates the associated DOD 4000.25-M, DLMS,

Volume 2 (reference 3c), Chapter 13 procedures for response to inquiry for materiel receipt. The 

MODELS enhancement is summarized at the enclosure. The original enhancement added the 

following advice code values to MILSTRIP for use with DLMS 527R receipt, and with DS 527R 

Response to Inquiry for Receipt status:

CODE EXPLANATION

3K Storage activity response to inquiry for receipt status. Storage activity has the receipt in process.

3N Storage activity response to inquiry for receipt status. Storage activity has no receipt in process 

and no record of the due-in. 

3P Storage activity response to inquiry for status on receipt or reclassification action that is a 

duplicate of the original receipt or adjustment provided by the storage activity.

This ADC approves adding a new advice code for use with DLMS 527R response to inquiry for 

receipt status as follows:

CODE EXPLANATION

3M Storage activity response to inquiry for receipt status. Storage activity has no receipt in 

process but there is a Prepositioned Materiel Receipt (PMR)) file. Refer to ADC 313

This change also updates the associated DLMS Volume 2, Chapter 13 procedures for the 

new advice code 3M. 

5. BACKGROUND FOR ESTABLISHING IMPLEMENTATION DATE: Many years ago, 

DLA Logistics Management Standards and the Supply PRC stopped using the established Request 

for Implementation Date (RFID) process to identify joint implementation dates for approved 

changes. The process stopped being effective because many of the Components were in the 

process of developing ERPs and were unable to provide projected implementation dates; and they 

were not making changes in legacy systems. In December 2008, since some ERPs were 

implemented, the DOD MILSTRAP Administrator attempted to establish a joint Component 
3 of 10

ADC 313

Attachment

implementation date for ADC 313 using a Request for Implementation Date memorandum 

(reference 3.e.), as a planning tool to assist in implementing changes. This attempt had mixed 

results and did not achieve the goal of identifying a joint implementation date and the ADC has 

since remained in limbo. 

6. IMPLEMENTATION TARGET: The DOD Component implementation date information 

for ADC 313, provided in response to the December 2008 Request for Implementation Date and 

subsequent follow-up, is shown at paragraph 13. Responses were not satisfactory to establish a 

joint DOD implementation date. This ADC therefore documents implementation status 

available as of the date of this memorandum, and requires that the Components monitor 

for implementation of ADC 313 and advise of firm implementation dates when known. This 

supports the DOD 4140.1-R (reference 3h.), Appendix 13, requirement for the DOD 

Components to provide the DLA Logistics Management Standards office with status on 

implementation of approved DLMS changes.

7. PUBLICATION. ADC 313 will be published in the reissuance of DOD 4000.25-M (DLMS)

and DOD 4000.25-1-M (MILSTRIP), anticipated for 3rd Quarter FY 2012. Components should 

ensure that inclusion of data described in this change in the 527R does not cause inappropriate 

rejection of the transaction. Data includes: 

a. 527R Receipt Advice Codes-Requirements for:

1) Storage activities to:

a) Generate Advice Code 3P with DLMS 527R receipt transactions (527R with 

1/BR02/20 Transaction Type Code D4-Receipt) when sending a duplicate receipt in response to a 

DLMS 527R inquiry for receipt status transaction (527R 1/BR02/20 Transaction Type Code INInquiry (DIC DXA/DXB functionality))

b) Generate the following advice codes when storage activity sends DLMS 527R

Response to Inquiry for receipt status (527R 1/BR02/20 Transaction Type Code DG-Response (DIC

DXC/DXD functionality)):

• Advice Code 3K when the storage activity has the receipt in process.

• New Advice Code 3M when storage activity has no receipt in process but there 

is a PMR.

• Advice Code 3N when storage activity has no receipt in process and no record 

of PMR.

2) Inventory Control Points (ICPs) recognize and process the above Advice 

Codes 3K, 3M, and 3N when received in DLMS 527R Response to Inquiry for Receipt Status; 

and Advice Code 3P when received in DLMS 527R Receipt transactions, and take action 

accordingly for delinquent intransit dues-in.

b. 527R MRA Beginning Segment Action Code V. DLMS 527R MRA to include use 

of beginning segment Action Code V when sending an MRA in response to a follow-up. 
4 of 10

ADC 313

Attachment

Provides a means to differentiate at the beginning segment whether this is an initial MRA 

(MILSTRAP DRA functionality), or an MRA in response to a follow-up (MILSTRAP DRB 

functionality).

8. REASON FOR CHANGE: 

 a. Supports the DLMS enhancement for use of advice codes documented in 527R, 

2/LQ/130 code 80-Advice Code DLMS Note 1. “Use when submitting a duplicate receipt in 

reply to a receipt inquiry; when submitting a response to a receipt inquiry when there is a 

receipt in process; when there is no receipt in process and no advance receipt information file; 

when there is no receipt in process but there is an advance receipt information file; ... DLMS 

enhancement, see DLMS introductory note 5a.”

b. Revises DLMS 527R to accommodate MILSTRAP DIC DRB functionality by use of 

a beginning segment action code.

9. PROCEDURES:

a. Revise DOD MILSTRIP (references 3.d), Appendix AP2.15, Advice Codes, as

revised by ADC 387 (reference 3.f.), to add new advice code 3M; administrative update to 

codes 3N and 3P; and to identify in the code list a separate category applicable to DLMS 

Receipt, Response to Receipt Inquiry, and Inventory Adjustment Transaction Advice Codes. 

The addition of the new category is consistent with the existing Advice Code list which identifies 

categories to include: Requisition Transaction Advice Codes and Materiel Returns Program 

Advice Codes. Corresponding changes will be made to advice code in the DLMS Data 

Dictionary (reference 3.g.). Changes are identified by red, bold italics:

DLMS RECEIPT, RESPONSE TO RECEIPT INQUIRY, AND INVENTORY ADJUSTMENT 

TRANSACTION ADVICE CODES 13

CODE EXPLANATION

3K Storage activity response to inquiry for receipt status. Storage activity has the receipt in process. 

Refer to ADC 313.

3M Storage activity response to inquiry for receipt status. Storage activity has no receipt in process 

but there is a Prepositioned Materiel Receipt (PMR)) file. Refer to ADC 313.

3N Storage activity response to inquiry for receipt status. Storage activity has no receipt in process and 

no record of the due-in/PMR. Refer to ADC 313.

3P Storage activity response to an inquiry for status on receipt, or in response to a follow-up for asset 

reclassification, followup to indicate that the transaction being submitted is a duplicate of the 

original receipt transaction, or inventory adjustment transaction, provided by the storage activity.

Caution must be used by the recipient to assure that the transaction is not processed twice. Refer to 

ADC 313 and ADC 487.

13 DLMS enhancement. Not for use in corresponding legacy 80 record position transactions. Refer 

to ADC 313. DOD Components must provide DLA Logistics Management Standards Office with

their Component implementation date for ADC 313.
5 of 10

ADC 313

Attachment

b. Revise DOD 4000.25-M, DLMS, Volume 2, Chapter 13 (Receipt), Paragraph C13.4,

as follows (changes identified by red, bold, italics):

“C13.4. STORAGE ACTIVITY RESPONSE TO INQUIRY ON MATERIAL RECEIPT1

C13.4.1. Material Receipt Previously Processed. When material has been received, and a receipt was 

previously submitted, storage activities shall submit a duplicate Receipt Transaction citing Advice Code 3P.

C13.4.2. Receipt in Process. When the storage activity has the receipt in process, storage activities 

shall reply using the Response to Inquiry Transaction citing Advice Code 3K.

C13.4.3. No Receipt but Record of Due-In. When the storage activity has no receipt in process but 

there is a Prepositioned Materiel Receipt (PMR)) file, the storage activity shall reply using the Response to 

Inquiry Transaction citing Advice Code 3M.

C13.4.4. No Receipt and No Record of Due-In. For nonreceipt of material, storage activities shall 

reply using the Response to Inquiry Transaction citing Advice Code 3N which indicates that the storage 

activity has no receipt in process and no record of the due-in. When the storage activity has no receipt in 

process and no record of an PMR file, the storage activity shall reply using the Response to Inquiry 

Transaction citing Advice Code 3N.”

c. Revise DOD 4000.25-M, DLMS, Volume 2, Chapter 10, Material Receipt 

Acknowledgement, Paragraph C10.1.2, as follows (changes identified by red, bold, italics):

“C10.1.2. Transactions. This chapter addresses the procedures applicable to the following ASC 

X12 transaction functions identified by their beginning segment (1/BR02/020) transaction type 

code. Other DLMS formats, such as XML, are also available. See the DLA Logistics 

Management Standards website for available DLMS formats: http://www.dla.mil/j6/dlmso/elibrary/TransFormats/140_997.asp. The corresponding MILSTRAP transaction 

functionality is identified for information purposes in a mixed DLSS/DLMS environment.

C10.1.2.1. Material Receipt Acknowledgement (MRA) Transaction is DS to the 

Federal IC 527R, identified by beginning segment Transaction Type Code TH – Receipt 

Acknowledgement Advice. This transaction provides MILSTRAP DIC DRA functionality.

C10.1.2.2. MRA Response to Inquiry Transaction is DS to the Federal IC 527R, 

identified by beginning segment Transaction Type Code TH – Receipt Acknowledgement Advice, 

used in conjunction with 1/BR06/20 Action Code V-Respond. This transaction provides 

MILSTRAP DIC DRB functionality.1

C10.1.2.3. MRA Inquiry Transaction is DS to the Federal IC 527R, identified by 

beginning segment Transaction Type Code TG – Receipt Acknowledgement Inquiry. This 

transaction provides MILSTRAP DIC DRF functionality.

 1 Refer to ADC 313. DOD Components must provide DLA Logistics Management Standards Office with their

Component implementation date for ADC 313.
6 of 10

ADC 313

Attachment

d. Revise Correlation of MILSTRAP DIC Functionality to DLMS Supplement (DS)

Tables as follows (the tables are available at: http://www.dla.mil/j6/dlmso/eApplications/LogDataAdmin/dlssdlmscrossreftable.asp):

1) Correlation Table in DIC sequence:

DIC(s) MILSTRAP TITLE DS # DS Accredited Standards Committee (ASC) X12

Functional Equivalent to MILSTRAP DIC

Beginning Segment Additional Information needed

DRA Materiel Receipt 

Acknowledgment (MRA)

527R 1/BR02/020 

Transaction Type 

Code TH – Receipt 

Acknowledgement 

None.

DRB MRA in reply to follow-up 527R 1/BR02/020 

Transaction Type 

Code TH – Receipt 

Acknowledgement

With 1/BR06/020 

Action Code VRespond

None.

DRF Follow-Up For Delinquent 

MRA

527R 1/BR02/020 

Transaction Type 

Code TG – Receipt 

Acknowledgement 

Inquiry

None.

2) Correlation Table in DLMS sequence:

DS # DLMS Supplement Title DIC(s) DS Accredited Standards Committee (ASC) X12

Functional Equivalent to MILSTRAP DIC

Beginning Segment Additional Information needed

527R Receipt, Inquiry, Response, 

MRA

Materiel Receipt 

Acknowledgement (MRA)

DRA

1/BR02/020 

Transaction Type 

Code TH – Receipt 

Acknowledgement 

None.
7 of 10

ADC 313

Attachment

DS # DLMS Supplement Title DIC(s) DS Accredited Standards Committee (ASC) X12

Functional Equivalent to MILSTRAP DIC

Beginning Segment Additional Information needed

527R Receipt, Inquiry, Response, 

MRA

MRA in Response to 

Inquiry/Follow-up

DRB

1/BR02/020 

Transaction Type 

Code TH – Receipt 

Acknowledgement

With 1/BR06/020 

Action Code VRespond

None.

527R Receipt, Inquiry, Response, 

MRA

Inquiry for Delinquent MRA DRF

1/BR02/020 

Transaction Type 

Code TG – Receipt 

Acknowledgement 

Inquiry

None.

e. Revise DLMS 527R to add a beginning segment action code to capture MILSTRAP DIC 

DRB functionality for MRA sent in response to an Inquiry for Delinquent MRA, as follows:

Item # Location Revision to 527R

Receipt, Inquiry, Response and MRA

Reason

1. DLMS 

Introductory

Note

Added ADC 313 to Introductory note 7

- ADC 313, Revisions to DLMS 527R to Add Code 

for MILSTRAP DRB Functionality and to Address 

Enhancement for Advice Codes Used with 527R 

Receipt and Response to Inquiry for Materiel 

Receipt

To identify DLMS changes 

included in the DS

2. 1/BR02/

20

Revise DLMS note for Transaction Type Code 

TH:

TH Receipt Acknowledgment Advice

DLMS Note: MRA Transaction. Use for MRA 

to acknowledge the receipt or nonreceipt of 

materiel (MILSTRAP DIC DRA functionality). 

Use in conjunction with BR06 Action Code VRespond when sending MRA in response to an 

Inquiry for Delinquent MRA (MILSTRAP DIC

DRB functionality.) 

To provide functionality of 

MILSTRAP DIC DRB (MRA 

Reply to Follow-up)
8 of 10

ADC 313

Attachment

Item # Location Revision to 527R

Receipt, Inquiry, Response and MRA

Reason

3. 1/BR06/

20

Add Action Code V with DLMS note:

V Respond

DLMS Note: MRA Response to Inquiry Transaction. 

Use in conjunction with BR02 Transaction Type Code 

TH when sending an MRA in response to an Inquiry 

for Delinquent MRA. (MILSTRAP DIC DRB 

functionality.) Refer to ADC 313.

To provide functionality of 

MILSTRAP DIC DRB (MRA 

Reply to Follow-up)

4. 2/LQ01/

130

Revise DLMS Note 1 for Qualifier 80:

80 Advice Code

DLMS Note 1. Use when submitting a duplicate 

receipt in reply to a receipt inquiry (Advice Code 3P); 

when submitting a response to a receipt inquiry when 

there is a receipt in process (Advice Code 3K); when 

there is no receipt in process and no prepositioned 

materiel receipt (PMR) file (Advice Code 3N); and

when there is no receipt in process but there is a PMR

file (Advice Code 3M). Otherwise do not use except as

noted below. DLMS enhancement, see DLMS 

introductory note 5a. Refer to ADC 313.

Cites applicable Advice codes 

since only 4 codes apply to this 

transaction.

Removes language for an advice 

code (which was never assigned) 

to address that an MRA is sent in 

response to an MRA inquiry. 

This functionality is being added 

as a beginning segment action 

code as noted in row above.

 

Also, incorporates term 

prepositioned materiel receipt. 

MILSTRAP Administrator will 

be making additional changes to 

DLMS procedures (Volume 2, 

Chapter 13) and DLMS 527D to 

revise DLMS term Advance 

Receipt Information (ARI) to 

Prepositioned Materiel Receipt 

(PMR). This change removes an 

inconsistency between the DLMS 

(ARI) and MILSTRAP (PMR) 

language.

10. ADVANTAGES AND DISADVANTAGES:

 

a. Advantages: Supports an existing DLMS requirement for use of advice codes and 

supports MILSTRAP DIC DRB functionality.

b. Disadvantages: None.

11. DEFENSE AUTOMATIC ADDRESSING SYSTEM (DAAS): Update DLA Transaction 

Services mapping as needed. 
9 of 10

ADC 313

Attachment

12. IMPACT: 

a. Automated Information System (AIS). 

1) Impacts Component ICP and storage activity modernized systems to have system 

logic to recognize and process the advice codes associated with DLMS 527R Receipt transactions. 

2) Impacts Component retail and wholesale modernization systems to recognize 

and process the new DLMS 527R action code for identifying in the beginning segment when an 

527R MRA transaction is being submitted in response to a follow-up (MILSTRAP DIC DRB 

functionality).

b. Publications. 

1) DoD Level: Impacts DOD 4000.25-M (DLMS); DOD 4000.25-1-M 

(MILSTRIP, Appendix AP2.15, Advice Codes); DLMS Data Dictionary; DLMS 527R; and DLA 

Transaction Services mapping require update as needed.

2) Component Level: May impact Component implementation procedures. 

13. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: The following implementation 

date information was provided in response to the Request for Implementation Date for ADC 313:

RESPONSE TO REQUEST FOR IMPLEMENTATION 

DATE

DISPOSITION

AIR 

FORCE

2/5/2010 

email 

response

Implementation date: Mar 2015. Implementation 

corresponds to the planned date for ECSS to subsume SCS 

and CAV-AF functionality.

ADC notes:

Air Force’s planned implementation 

is March 2015. Air Force Supply 

PRC representative to monitor 

for implementation of this ADC 

and advise if date changes.

ARMY

8/30/2010

email for 

Wholesale 

11/2/2010 

email-Retail 

Army National wholesale system (LMP and SDS) : 

Pending more information to be gathered the middle of 

2011 when HQ AMC approves LMP's new work schedule, 

Army's wholesale level implementation date is 2015 for this 

system.

Army's Retail projected implementation for GCSS-Army is 

3rd Qtr FY2012 (Release 1.2); SARSS legacy system will 

not implement.

October 2, 2011: Followed up for 

wholesale systems update. No 

response received.

Army Supply PRC representative 

to monitor for implementation of 

this ADC and provide 

implementation dates when 

available.

MARINE 

CORPS

7/27/2010

LPC-2 Letter 

provided 

response

1. Legacy retail systems would require significant 

modifications to address this change. The Marine Corps 

will not implement ADC 313 in legacy retail systems.

2. Currently the Marine Corps plans to address ADC 313 in 

its retail systems as part of the GCSS-MC Block 2 

deployment.

3. The GCSS-MC Block 2 deployment is scheduled for 

FY14.

4. Legacy wholesale systems would require significant 

ADC notes:

Marine Corps anticipates 

implementation in GCSS-Marine 

Corps in FY 14; Marine Corps 

anticipates wholesale systems to 

implement no later than FY16. 

Marine Corps Supply PRC 

representative to monitor for 

implementation of this ADC and 

provide implementation dates 
10 of 10

ADC 313

Attachment

RESPONSE TO REQUEST FOR IMPLEMENTATION 

DATE

DISPOSITION

modifications to address this change and updates to comply 

with ADC 313 are not planned. 

5. The Marine Corps will determine whether to include 

wholesale functionality into Block 2 of GCSS-MC or to 

continue to maintain wholesale functionality independently 

of the ERP.

6. The Marine Corps expects wholesale systems to be 

implementing ADC 313 no later than FY16.

Recommendation: The Marine Corps expects that ADC 

313 will be fully implemented no later than FY16.

when available.

NAVY

4/10/2011

email 

response

Cannot provide a date because it requires Navy ERP 

changes. Earliest date would be 2013 but that is only a 

guess. There are too many higher priorities for Navy ERP 

ECPs right now.

ADC notes:

Navy Implementation date unknown 

at time of publication of this ADC. 

Navy Supply PRC representative 

to monitor for implementation of 

this this ADC and provide 

implementation date when 

available.

DLA

10/3/2011 

email 

response

DLA just completed prioritization for the last half of 2012, 

the next opportunity for implementation is the first half of 

2013.

NOTE: Requires DLA provide

DSS and EBS implementation 

dates.

ADC notes: 

Implementation date for DSS and 

EBS is unknown at time of 

publication of this ADC. DLA 

Supply PRC representative to 

monitor for implementation of 

this ADC and provide DSS and 

EBS implementation dates when 

available. 

GSA

1/5/2009

Email 

response

GSA will implement during the planned system 

modernization on schedule for FY2011 or later.

Noted.

Enclosure
1 of 1

Enclosure

ADC 313

ENCLOSURE TO ADC 313

Summary of 1990 MODELS Enhancement Number. 90-010 Related to use of Advice Code 

with DLMS 527R

(PROVIDED AS BACKGROUND)

MODELS RECNO 90-010

DATE: 900112

ORIGINATOR: DLA Logistics Management Standards

SUMMARY: Identify transactions submitted in reply to ICP followup for receipt transaction

DESCRIPTION: Include data in the 527 transaction to indicate when a receipt transaction is in 

reply to an ICP follow-up. Presently the follow-up reply is an exact match to the receipt 

transaction. Some Services/Agencies use internal coding to identify such duplicate receipt 

transactions; however there needs to be inter-Service/Agency capability. The present MODELS 

transaction may provide sufficient information to accomplish this goal—for instance the 

presence of the transaction date, providing the transaction date is the date of the transmission, not 

of the original transaction. Also we could assign a new code.

AFFECTS: Requires system and procedural modification.

BENEFITS: Allows ICPs to easily match the follow-up replies to original receipt transactions 

when both are received. Enhances DoD supply accountability by eliminating the possibility of 

posting both transactions.

NARRATIVE OF REQUIRED ACTION: APRIL 1990: Added Advice Code to 527R and 

533 [PDC 330 Staffing note: 533 is now 947I Inventory Adjustment] transactions and 

MILSTRAP Administrator will provide the specific advice codes to define the following:

a. To DIC DXC/DXD function in DLMS 527R [STAFFING NOTE: DXC/DXD = Beginning

Segment 1/BR02/20 Transaction Type Code IN-Inquiry], defined as “receipt in process” 

[Advice Code 3K]

b. To DIC DXC/DXD function in DLMS 527R, defined as “no record of due-in” [Advice Code 3N]

c. To DLMS 527R Receipt (D4_ and D6_) functionality [STAFFING NOTE: D4_/D6_ = 527R 

Beginning Segment 1/BR02/20 Transaction Type Code D4-Receipt], defined as “duplicate of 

previously submitted transaction in reply to follow-up” [Advice Code 3P] 

[This last advice code from the 1990 enhancement also applies to DS 947I Inventory Adjustment 

functionality, but DS 947I is not addressed by this ADC]