ADC 465, Page 1

ADC 465

Additional Contract-Related Data for 870S with BV Status

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Ellen Hilert, 

Supply PRC Co-Chair, 703 767-0676, ellen.hilert@dla.mil

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply/MILSTRIP

b. Secondary Functional Process: Supply Chain Visibility

3. REFERENCES:

a. Item Unique Identification (IUID) Workshop chaired by ODASD (SCI), October 27,

2010.

b. Modernization of Defense Logistics (Models) Recommendation 89-104 Augmentation 

of Prepositioned Material Receipt Data to include selected contract data. 

4. BACKGROUND:

 a. General

 (1) During the 2011 IUID workshop (Reference 3.a), a requirement was identified to 

provide notification of a destination acceptance to status recipients when materiel was procured 

by the supply source on contract for direct shipment to a consignee. This would be identified on 

a DLMS 870S, Supply Status (Document Identifier Code (DIC) AE_) transaction also containing 

BV Status. 

(2) When the DLMS supplements were created, placeholders were incorporated in the 

multiple transactions (including the 870S) to carry contract-related data. However, no formal 

requirement in the DLMS manuals to provide the contract data was established. At the time, 

contract data was typically provided in paper format. It was envisioned that these placeholders 

would be implemented as enhancements to the DLMS at a future date. 

b. Intent of the change: This change modifies the DLMS to require contract-related data 

be included in the DLMS 870S (DI Code AE_) Supply Status transaction when BV Status is 

provided (Item Procured and on contract for direct shipment to the consignee). This will enable 

the recipients to integrate destination acceptance contract data within logistics systems used 

during receipt processing since the relevant contract data will have been received electronically 

from the previously transmitted supply status transaction. This eliminates the need to manually

research destination acceptance contract data within Electronic Document Access (EDA).
ADC 465, Page 2

c. Scenario for which the transaction is used: This transaction will be used when 

requisitioned materiel is provided directly to the consignee from the commercial source without 

prior delivery to a Government activity. The contract terms may vary.

d. Procedures, transactions, data elements, processing details in use today: Under 

MILSTRIP, the source of supply provides Supply Status BV (notifying status recipients of direct 

vendor delivery), and separately provides the contract number and call/order number via a 

second transaction (DLMS 870S or MILSTRIP DIC AB_, Direct Delivery Notice). Not all 

Components are capable of generating or receiving the Direct Delivery Notice. The Direct 

Delivery Notice does not contain notification of destination acceptance.

5. APPROVED CHANGE(S):

a. Approved change in detail: Yellow highlighting identifies significant revisions 

subsequent to the proposed change. Refer to Enclosure 3 for resolution of comments received 

during staffing.

 (1) Government sources of supply (SoS) will populate the applicable contract-related 

data content on the DLMS 870S when providing BV status. 

(2) Both the DIC AE_ and AB_ data will be carried in the enhanced supply status. 

When providing this enhanced supply status, a separate 870S (AB_) Direct Delivery Status shall 

not be prepared. The inclusion of the CS segment providing the contract number and call/order 

number will trigger DLMS-MILSTRIP conversion rules within the DLA Transaction Services 

Defense Automatic Addressing System (DAAS) so that legacy transaction recipients may 

continue to receive separate legacy transactions.1

 

(3) Component applications shall be modified to accept the additional contract-related 

data from the DLMS 870S transaction and make appropriate information available during receipt 

processing. For example, integrated processing shall be used to alert the receiving activity of 

destination acceptance requirements, inspection requirements, and allowable quantity variances 

in relation to quantity received when applicable.

b. Approved procedures:

(1) Contract Data: The contract related data identified in Enclosure 1 will be provided 

in the DLMS 870S transaction when Status Code BV is used and the specified data is applicable. 

(2) DLMS Manual Revisions: C5.2.6.3.2 currently indicates contract data is to be 

provided with the transaction; however, it does not identify specific contract data elements to be 

provided. Current procedures with updated text identified in bold/italics are shown below. 

Relevant text from 4000.25-M Volume 2, Chapter 5:

C5.2.6.3. Normal Requisitioning Processing. Sources of supply (SoS) must provide supply 

 1 Due to incomplete implementation, MILSTRIP Direct Delivery Status may be suppressed at DAAS by Component 

request.
ADC 465, Page 3

status based on normal requisition processing, including additional supply status due to changes 

in requisition processing, such as, cancellation actions, modifications, item substitutions, DVD 

actions, changes in ESDs (when retransmitting requisitions to another supply source), and 

requisition inquiries (follow-ups and requests for supply assistance). In addition, the SoS shall

send:

C5.2.6.3.1. DLMS 870S with Status Code BB (citing the scheduled ESD for release of 

material from stock to the customer) when backordering a requisition against a due-in to stock. 

The SoS shall always send additional Status Code BB to organizations with a revised ESD when 

adjusting shipping dates.

 C5.2.6.3.2. DLMS 870S with Status Code BZ with an ESD after deciding to process the 

requirement as a DVD shipment. The SoS shall give Status Code BV after effecting contracts or 

procurement actions and establishing an agreed to contract shipping date. Status Code BV must 

contain contract shipping date and also the contract data that provides organizations with a crossreference to the original requisition. At a minimum, contract data shall include the contract 

number, call/order number, notification of destination/origin acceptance, allowable quantity 

variances, and identification of the contractor by CAGE. The contract required shipping date 

shall be discretely identified and may be equal to the estimated shipment date. Additional 

contract data may be included as available.

C5.2.6.3.3. DLMS 870S with additional Status Code BV with a revised ESD to 

organizations when adjusting contract shipping dates on items scheduled for DVu

c. Alternatives: An alternative solution would be to retain the separate Direct Delivery 

Notice under DLMS and include the enhanced contract-related data in that transaction. 

6. REASON FOR CHANGE:

a. This change is required to provide receiving organizations with the necessary 

procurement data for requisitions that are procured for direct delivery. Recipients do not always 

have the relevant procurement data although efforts have been made to make this information 

available within EDA. However, this requires separate query action rather than the push concept 

used in this proposal. Lack of relevant procurement data makes it more difficult for receiving 

activities to comply with DOD requirements for destination acceptance via Wide Area Workflow 

(WAWF). The receiving activity may not recognize acceptable quantity variances and file an 

unnecessary supply discrepancy report (SDR).

b. Coordination of Component-requested placeholders for DLMS enhancements will 

support elimination and removal of those no longer considered necessary and implementation 

planning for those that are appropriate and desirable under modernization.

7. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Requiring the relevant contract data to be provided on Supply Status 

transactions with BV status will improve the ability of receiving activities to provide timely 

notification of destination acceptance. Additional information, such as the allowable 
ADC 465, Page 4

overage/shortage under contract terms, may be used in determining when it is appropriate to 

submit an SDR.

b. Disadvantages: There can be a long lead time for implementation of DLMS 

enhancements such as this.

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

DEVELOPMENT: Requires modernization under DLMS for implementation. 

9. NOTE ANY REGULATIONS OR GUIDANCE: Internal implementing guidance may 

require update.

10. ADDITIONAL FUNCTIONAL REQUIREMENTS: Requires retention and integration 

of acquisition information within the Component automated information system (AIS).

11. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: The earliest authorized 

implementation date is September 1, 2012. Supply PRC members are asked to provide a target 

implementation date and subsequently monitor implementation status. Implementation dates 

should be reported to the MILSTRIP Administrator when known.

12. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Not available.

13. IMPACT:

a. Automated Information Systems (AIS): This change requires full integration 

between contract information and supply/logistics appropriate to enterprise resource systems 

(ERPs). DLMS capable applications must ensure that transmission of the expanded content will 

not cause transaction failure.

b. DLA Transaction Services:

(1) Requires update to conversion processing to generate separate AE_, Supply Status, 

and AB_ Direct Delivery Notification, transactions when both are communicated in a single 

870S (identified by inclusion of the CS segment).

(2) Requires update to WebVLIPS to capture contract-related data elements for display 

with supply status information.

(3) Comparable contract detail data elements (most existing as DLMS enhancement 

placeholders) may be proposed for implementation within the DLMS 527D, Pre-positioned 

Materiel Receipt, subsequent to staffing of this proposal.

c. New DLMS Data Elements that support this change: The majority of data elements 

associated with this change are already established for use with other transactions. Not all the 

data elements established as placeholders were previously identified in the DLMS dictionary and 

will be added upon approval of this change. The Contract Required Delivery Date, Certificate of
ADC 465, Page 5

Conformance Indicator, and Certificate of Quality Conformance Indicator are new data elements. 

 d. Changes to DLMS Data Elements: See Enclosure 1. 

 e. DLMS Supplement Revisions: Refer to Enclosure 2.
ADC 465, Enclosure 1, Page 1

Enclosure 1 to ADC 465

The following data elements will be carried in the DLMS 870S in association with this change. 

Staffing Note for DoD Components: The listed contract-related data elements were added as 

placeholders in the 870S transaction years ago. Service/Agency PRC representatives were

asked to review the proposed list in coordination with their contracting office. Responses are 

noted in the comment resolution at Enclosure 3. The following data elements were retained and 

are approved for implementation.

Approved

Data Element for 

Implementation in DLMS 

870S

Code Values/Usage Notes Field 

Length

1. Acceptance Point

Designator

Identifies the acceptance point for the material:

Accept at Destination 

Accept at Origin

Acceptance at Other. Applicable when destination acceptance 

is performed by an activity other than the ship-to activity.

(Field length for DLMS mapping using the code from the 

commercial standard is not the same as the internal AIS 

indicator; internal indicators shall be mapped to the codes used 

in the X12 format for transaction exchange only. A one 

position internal code is recommended.)

1

2. Quantity Variation -

Overage

This will be used to indicate the permissible overage as a 

percentage of the total contract line item number quantity. This 

will be expressed as a decimal.

10

3. Quantity Variation -

Shortage

This will be used to indicate the permissible shortage as a 

percentage of the total contract line item number quantity. This 

will be expressed as a decimal.

10

4. Excess Quantity Clause 

Dollar Amount

This is the permissible overage dollar value specified by the 

contract above which discrepancy action is taken. The dollar 

amount is expressed as a whole number.

10

5. Inspection Point

Designator

Identifies where the contract specifies that material will be 

inspected as the procurement quality assurance site):

Inspect at Destination 

Inspect at Origin

Inspect at Other

(Field length for DLMS mapping using the code from the 

commercial standard is not the same as the internal AIS 

indicator; internal indicators shall be mapped to the codes used 

in the X12 format for transaction exchange only. A one 

position internal code is recommended.)

1
ADC 465, Enclosure 1, Page 2

Approved

Data Element for 

Implementation in DLMS 

870S

Code Values/Usage Notes Field 

Length

6. Certificate of 

Conformance Indicator

A ‘Y’ or ‘N’ will be used to indicate whether a Certificate of 

Conformance is required with the shipment.

1

7. Certificate of Quality 

Conformance Indicator

A ‘Y’ or ‘N’ will be used to indicate whether a Certificate of 

Quality Conformance is required with the shipment. 

1

8. Contract Administration 

Office

This is the office responsible for contract administration 

identified by DoDAAC.

6

9. Vendor Identifies the Vendor supplying the material by CAGE. This 

may be other than the manufacturer: 

Code ‘SU’ (Supplier/Manufacturer) is assigned for this usage 

and Code ‘33’ is used for the CAGE. 

5

10. Part Number Purchased Identifies the manufacturers part number of the item purchased.

Code ‘MG’ is assigned for this usage.

30

11. Manufacturer of Part 

Number Purchased

Identifies Commercial and Government Entity (CAGE) of the 

manufacturer of the purchased part. 

Code ‘ZB’ is assigned for this usage

5

12. Purchase Unit of 

Measure

This is the unit of measure from the contract if different from 

the unit of issue. Authorized code values are contained in the 

DLMS Unit of Measure Conversion Guide.

2

13. Contract Required 

Delivery Date

This is the required delivery date identified in the 

contract/delivery order.

Qualifier Code for Required Delivery. 

Used with 2/DTM02/240 Code 996.

8
ADC 465, Enclosure 2, Page 1

Enclosure 2 to ADC 465, 870S, Supply Status Revision

Item

#

Location Revision to

4010 DS 870S Supply Status – Contract Related Data

Reason

1. DLMS 

Introductory 

Note

Add ADC 465 to DLMS Introductory note:

- ADC 465, Additional Contract-Related Data for 870S 

with BV Status

To identify DLMS 

changes included in 

the DS

2. 1/BSR01/20 Revise DLMS Notes as follows:

Status Report Code

4 Response to Requisition

DLMS Note:

1. Use to indicate requisition supply status.

2. Also used to provide detailed contract information in 

combination with Supply Status BV (combined MILSTRIP DIC

AE_ and AB_). (Refer to ADC 465.)

5 Notice of Response to Direct Vendor Delivery

DLMS Note:

Use to indicate that the supply source is providing the required 

material directly from a commercial source. Use when direct 

vendor delivery notice is provided as a separate transaction 

(MILSTRIP DIC AB_) pending transition to enhanced BV 

Status under ADC 465.

Expands usage 

instructions for 

comprehensive 

combined supply 

status. This will 

support use of a 

single supply status 

transaction to 

provide BV status 

plus the associated 

contract information.

3. 2/CS07/86 Add the following Data Element level DLMS Note: 

Special Services Code

Federal Note: Use to identify the contract specification for 

material acceptance.

DLMS Note: 

Use with Supply Status BV to identify the acceptance point. 

(Refer to ADC 465.)

Add additional Qualifier ZZ with DLMS Note:

AD Accept at Destination 

AO Accept at Origin 

ZZ Mutually Defined

DLMS Note: 

Use ZZ to indicate Acceptance by Other when destination 

acceptance shall be performed by an activity other than the 

ship-to activity.

Updated per Navy 

comments.
ADC 465, Enclosure 2, Page 2

Item

#

Location Revision to

4010 DS 870S Supply Status – Contract Related Data

Reason

4. 2/CS09/86 Add the following Data Element level DLMS Notes:

Percent

DLMS Note: Use with Supply Status BV to identify the 

allowable overage by percent. (Refer to ADC 465)

Clarification of 

expanded data 

content.

5. 2/CS10/86 Add the following Data Element level DLMS Notes:

Percent

DLMS Note: Use with Supply Status BV to identify the 

allowable shortage by percent. (Refer to ADC 465)

Clarification of 

expanded data 

content.

6. 2/CS11/86 Add the following Data Element level DLMS Notes:

Monetary Amount

Federal Note: Use the dollar amount from the excess quantity 

clause. Express as a whole number with no decimal

DLMS Note: Use with Supply Status BV to identify the 

allowable dollar amount specified in the excess quantity clause 

when applicable. (Refer to ADC 465)

Clarification of 

expanded data 

content.

7. 2/CS12/86 Remove existing qualifier 21 and mark this data element as not 

used:

21 Fast Pay

This information is 

not applicable to the

ship-to activity 

receipt processing. 

Removed per DLA 

comments.
ADC 465, Enclosure 2, Page 3

Item

#

Location Revision to

4010 DS 870S Supply Status – Contract Related Data

Reason

8. 2/CS13/86 Add the following Data Element Level DLMS Note:

Special Services Code

Federal Note: Use to identify the contract specification for 

material inspection.

DLMS Note: Use with Supply Status BV to identify when 

contract terms specify inspection requirements. (Refer to ADC 

465)

Add additional Qualifier G0052 with DLMS Note:

IM Inspect at Destination

DLMS Note: Use Code IM to indicate Inspection Performed at 

Destination when origin inspection does not apply and 

inspection requirements shall be satisfied by the ship-to activity.

IO Inspect at Origin

G0052 Government Inspection

DLMS Note: Use Code G0052 to indicate Inspection Performed 

by Other when origin inspection does not apply and inspection 

requirements shall be satisfied by an activity other than the 

ship-to activity.

Clarification of 

expanded data 

content.

Updated per Navy 

comments.

9. 2/CS14/86 Revise Data Element Level DLMS Notes as follows:

Unit or Basis for Measurement Code

Federal Note: Use to identify the purchase unit of issue, if 

different from the standard unit of issue.

DLMS Note:

1. Use with Supply Status BV to identify the purchase unit if 

different from the unit of issue. (Refer to ADC 465)

2. DLMS users see the Unit of Issue and Purchase Unit 

Conversion Table for available codes.

Clarification of 

expanded data 

content.

10. 2/CS16/86 Remove existing qualifier 22 and mark this data element as not 

used:

22 Cash Discount Terms Apply 

This information is 

not applicable to the 

ship-to activity 

receipt processing.

Removed per DLA 

comments.
ADC 465, Enclosure 2, Page 4

Item

#

Location Revision to

4010 DS 870S Supply Status – Contract Related Data

Reason

11. 2/CS17/86 Add the following Data Element Level DLMS Note:

Yes/No Condition or Response Code

DLMS Note: Use with Supply Status BV to identify when the 

contract specifies a Certificate of Conformance (CoC) is 

applicable. (Refer to ADC 465)

Y Yes

N No

Clarification of 

expanded data 

content.

12. 2/CS18/86 Add the following Data Element Level DLMS Note:

Yes/No Condition or Response Code

DLMS Note: Use with Supply Status BV to identify when the 

contract specifies a Certificate of Quality Conformance (CoQC) 

is applicable. (Refer to ADC 465)

Y Yes

N No

Clarification of 

expanded data 

content.

13. 2/N101/90 Revise the following DLMS notes to existing qualifier C4 and 

SU:

C4 Contract Administration Office

DLMS Note Use with Supply Status BV for direct vendor 

deliveries to identify the Contract Administration Office (CAO) 

for the related acquisition action. (Refer to ADC 465)

SU Supplier/Manufacturer

DLMS Note: Use with Supply Status BV for direct vendor 

deliveries to identify the contractor providing the materiel for the 

related acquisition order. (Refer to ADC 465)

Clarification of 

expanded data 

content.

14. 2/N103/90 Revise the following DLMS Note to existing qualifier 33:

33 Commercial and Government Entity Code:

DLMS Note: Use with Supply Status BV for direct vendor 

delivery 2/N1/090 supplier (Code SU) loops to identify the 

contractor providing the material. when the contractor is not 

assigned a DODAAC.

Clarification of 

expanded data 

content.

15. 2/PO112/150 Open PO112- PO113 and add Qualifier MG with DLMS Note:

MG Manufacturer’s Part Number

DLMS Note: Use with Supply Status BV to provide the 

manufacture’s part number when the primary materiel 

identification is by NSN (P0106, Code FS). (Refer to ADC 465)

Clarification of 

expanded data 

content.
ADC 465, Enclosure 2, Page 5

Item

#

Location Revision to

4010 DS 870S Supply Status – Contract Related Data

Reason

16. 2/PO114/150 Open PO114- PO115 and add new Qualifier ZB with DLMS 

Note:

ZB Commercial and Government Entity Code

DLMS Note: Use with manufacturer’s part number (P0112, 

Code MG) to provide the manufacturer’s CAGE.

Clarification of 

expanded data 

content.

17. 2/DTM01/240 Add new Qualifier 996 with DLMS Note:

996 Required Delivery

DLMS Note: Use with Supply Status BV to indicate Contract 

Required Delivery Date. This date may differ from the 

customer’s required delivery date. (Refer to ADC 465)

Clarification of 

expanded data 

content.

18. 2/LQ01/145 Add DLMS Note to existing Qualifier 0:

0 Document Identification Code

DLMS Note: Use a second iteration to indicate multiple DICs

are applicable for combination supply status with direct delivery 

notice (DIC AE_ and DIC AB_). (Refer to ADC 465)

Clarification of 

usage for 

consolidated DLMS 

transaction 

exchange.
ADC 465, Enclosure 3, Page 1

Enclosure 3, Comment Resolution for PDC 448

Originator Response/Comment Disposition

1. Army Concur with comment:

1. Acceptance Point Designator - Yes (questioned field 

length) 

2. Quantity Variation - Overage - Yes 

3. Quantity Variation - Shortage - Yes 

4. Excess Quantity Clause Amount - No 

5. Fast Pay Indicator - Yes 

6. Inspection Point Designator - No, but could be dependent 

on commodity 

7. Cash Discount Stipulation Code - Yes 

8. Certificate of Conformance Indicator - No (delete) 

9. Certificate of Quality Conformance Indicator - Yes 

10. Contract Administration Office - Yes 

11. Vendor - Yes 

12. Part Number Purchased - Yes 

13. Manufacturer of Part Number (CAGE Code) Purchased 

- Yes (questioned field length) 

14. Purchase Unit of Measure - Yes 

15. Contract Required Delivery Date – Yes

An implementation date cannot be determined at this time. 

Noted.

Notes for field length in 

Enclosure 1 have been 

expanded for clarification.

2. Air Force AF concurs with additional comments. Please see below.

1. Recommend this requirement be reviewed by ECSS for 

implementation in the supply replacement system.

2. This PDC could potentially be implemented in ES-S. 

The change would require developer funding to allow ES-S 

to use the additional direct vendor delivery information that 

is being sent on the 870S transaction. We would need 

additional information – see below.

3. If we do not implement this change in ES-S, then the 

additional Direct Vendor Delivery information will not be 

captured in ILS-S. The current legacy system (SBBS) does 

not accept DLMS transactions; thus any changes to 

accommodate this PDC will have to be made in ES-S.

--------

1. ILS-S (SBSS) only partially implemented the use of the 

MILS AB(x) transaction. ILS-S accepts the MILS AB(x) 

and creates a record that is linked to the corresponding 

requisition (due-in). The retail supply user has no access to 

this record; there is no user interface screen to retrieve this 

data; thus it is not used.

Noted.
ADC 465, Enclosure 3, Page 2

Originator Response/Comment Disposition

2. In order to use the contract information for Direct Vendor 

Delivery requisitions; we envision building an ILS-S Direct 

Vendor Delivery (DVD) record and allow the user to query 

this record by contract number/call number/order 

number/requisition number when receiving/accepting the 

DVD items. The 870S will serve two purposes (a) we will 

build our supply status detail as well as (b) the new DVD 

record. 

3. We need to know how the requisition number (due-in) 

relates to the contract number and the call/order number? 

On a given 870S - will both the contract number and 

call/order number always be provided?

4. For a given contract number -- there will be/could be 

multiple call/order numbers?

5. For a given contract number and call/order number -- will 

there be/could there be more than one requisition against it? 

Or is this a one to one relationship?

6. When the property (assets) physically arrive at the 

acceptance destination -- what information is going to be on 

the shipping/receiving document? We realize this may be a 

mixed bag depending upon the contract -- but in order for us 

to implement this we need to know what information may 

be available as well as what information will always be 

available in order

to know how we can access the ILS-S DVD record. 

-- Contract Number

-- Call Number /Order Number 

-- MILS Requisition Number

-- National Stock Number

-- Part Number

3. Yes, both the requisition 

number and the contract 

number will always be 

provided with BV status.

4. There is only one 

call/order per DIC AB_ in 

the legacy format. The 

transaction has been 

updated to allow looping.

5. It is possible for a single 

vendor shipment to fill 

multiple requisitions, but 

each requisition would have 

a separate 870S/AB 

transaction providing 

contract info. However, in 

some rare circumstance it 

could require two vendors 

to fill a large order. The 

transaction has been 

updated to allow looping.

6. The vendor is required to 

provide shipment 

documentation including the 

first three elements. The 

NSN is required if ordered 

from the vendor by NSN. If 

the materiel is ordered and 

shipped by NSN, we are not 

aware of a mandatory 

requirement for inclusion of 

the part number on the 

shipment document.

3. Marine Corps Concur with comment:

1. Data Elements listed in PDC 448:

 a. Acceptance Point Designator - Concur

 b. Quantity Variation (Overage) - Concur

 c. Quantity Variation (Shortage) - Concur

 d. Excess Quantity Clause Amount - Concur

 e. Fast Pay Indicator - Concur

 f. Inspection Point Designator - Concur

1. Noted.
ADC 465, Enclosure 3, Page 3

Originator Response/Comment Disposition

 g. Cash Discount Stipulation Code - Concur

 h. Certificate of Conformance Indicator - Concur

 i. Certificate of Quality Conformance Indicator - Concur

 j. Contract Administration Office - Concur

 k. Vendor - Concur

1. Part Number Purchased - Concur

 m. Manufacturer of Part Number Purchased - Concur

 n. Purchase Unit of Measure - Concur

 o. Contract Required Delivery Date – Concur

2. General:

 a. The Marine Corps performs destination HQMC 

acceptance for direct vendor delivery (DVD) shipments 

through completion of the DD Form 250.

 b. Currently there is no timetable for inclusion of systemic 

destination acceptance in GCSS-MC.

 c. Additional data elements listed below are recommended 

to ensure automated population of all fields on the DD Form

250 to the greatest extent possible:

 i. Discount Terms (Block 5)

 ii. Prime Contractor (Block 9)

 iii. Administered By (Block 10)

 iv. Shipped From (Block 11)

 v. Payment Will be Made By (Block 12)

 vi. Shipped To (Block 13)

 vii. Marked For (Block 14)

 viii. Item No. (Block 15)

 ix. Stock/Part No. (Block 16)

 x. Description (Block 16)

 xi. Unit Price (Block 19)

d. Recommended data elements are those that can be 

determined at the time supply status (BV) is sent by the

servicing SOS/ICP.

e. Marine Corps anticipates requesting changes to this PDC 

when destination acceptance is implemented in GCSS-MC.

f. The Marine Corps recommends bundling destination 

acceptance into the DS 527R. This will allow Marine Corps

units to perform receipt and destination acceptance 

simultaneously (when appropriate) greatly minimizing the 

process and paperwork burden incumbent upon the end 

user.

2. Most of the data 

elements listed are already 

included on the supply 

status or are addressed 

above. Mark For is 

applicable but is a separate 

enhancement to multiple 

DLMS transactions.

2.f. The merging of 

destination acceptance and 

receipt/receipt 

acknowledgment would be a 

major process change and 

requires separate proposal 

and coordination. 

4. Navy Concur with comment:

A. Proposed data elements:

 1. Acceptance Point Designator - Yes ("Acceptance at 

Other "is not a variation of destination acceptance. 

Acceptance at other has 

been added.
ADC 465, Enclosure 3, Page 4

Originator Response/Comment Disposition

Destination acceptance means the consignee (or ship to) is 

the acceptor. Other means acceptance is at a location other 

than the ship to and the place of contract performance. ) 

 2. Quantity Variation - Overage - Yes 

 3. Quantity Variation - Shortage - Yes 

 4. Excess Quantity Clause Amount - Yes

 5. Fast Pay Indicator - Yes 

 6. Inspection Point Designator – Same comment as 1, 

above. 

 7. Cash Discount Stipulation Code - Yes 

 8. Certificate of Conformance Indicator – See below

 9. Certificate of Quality Conformance Indicator - Yes 

 10. Contract Administration Office – Yes, agree with 

including the CAO but the information in the Code 

Values/Usage Notes does not match the Proposed Data 

Element.

 11. Vendor - Yes 

 12. Part Number Purchased - Yes 

 13. Manufacturer of Part Number (CAGE Code) 

Purchased - Yes 

 14. Purchase Unit of Measure - Yes 

 15. Contract Required Delivery Date – Yes

B. Recommend adding a PCO office field to identify the 

agency that issues the contract.

C. Acceptance at Other cannot be used interchangeably with 

Acceptance at Destination. In many cases, acceptance at 

other requires special inspection. Destination acceptance is 

only used for non-complex material where inspection is 

limited to kind, count, and condition. Also, destination 

acceptance means the acceptance site is the consignee, 

which on supply contracts is the SHIP TO DoDAAC. Will 

logic be in place to prevent this transaction from being used 

as proof of destination acceptance when acceptance is not at 

destination, or if the contract is above the simplified 

acquisition threshold?

D. Navy understands the term "conformance" used with 

supplies and "compliance" used with services, but it is not 

clear if there is a legal or policy difference between the two 

terms. Assuming these transactions will only be used for 

supply receipts, one field should be enough. If Navy 

determines that there is a difference between conformance 

and compliance, and also that both apply to supplies, a 

different indicator can be used for each term vs. using a Y/N 

indicator.

5. DLA Concur with comment: Fast Pay Indicator will be 
ADC 465, Enclosure 3, Page 5

Originator Response/Comment Disposition

1. Acceptance Point Designator - Yes (Acceptance at Other 

should be added as an option.)

2. Quantity Variation - Overage - Yes (This info may 

prevent SDRs being submitted if within the variation 

amount.)

3. Quantity Variation - Shortage - Yes (This info may 

prevent SDRs being submitted if within the variation 

amount.)

4. Excess Quantity Clause Amount – Yes (This info may 

prevent SDRs being submitted if within the variation 

amount.)

5. Fast Pay Indicator - No

6. Inspection Point Designator – Yes (This may be 

important information for Tech/Quality inspections.)

7. Cash Discount Stipulation Code - No

8. Certificate of Conformance Indicator - No 

9. Certificate of Quality Conformance Indicator - No

10. Contract Administration Office - No

11. Vendor - Yes 

12. Part Number Purchased - Yes (This may be important 

information for Tech/Quality inspections.)

13. Manufacturer of Part Number (CAGE Code) Purchased 

- Yes (This may be important information for Tech/Quality 

inspections.) 

14. Purchase Unit of Measure - Yes (May be important in 

resolving unit of issue problems.)

15. Contract Required Delivery Date – Yes (May be 

important if the date differs significantly from the 

customer’s RDD.)

removed. This information 

is not applicable to the shipto activity receipt 

processing.

Cash Discount Stipulation 

code will be removed. This 

information is not 

applicable to the ship-to 

activity receipt processing.

Certificate of Conformance 

Indicator and Certificate of 

Quality Conformance 

Indicator have been retained 

because the Services 

supported these elements 

and it is believed that they 

may be taken into 

consideration during 

receipt/acceptance 

processing.

6. DPAP Would you be creating the 870 from the 850 that we 

generate for all contract awards?

My concern is that nowhere in any procurement anything 

does it tell people to generate something other than either an 

850 or PDS (translatable to an 850). So if you want 

contract writing to generate an 870, then we have to revise 

the DFARS and modify all 15 or so contract writing 

systems. If the supply system isn't sending the 870 the data 

is available from the 850, which is coming more than 90% 

of the time today.

The 870S will not be 

prepared as spin-off of the 

850, but data should come 

from the same source. We 

are asking the ERPs to share 

the contract information so 

that the supply transaction 

will incorporate the added 

data elements. The supply 

system already has a 

requirement to provide the 

BV data and limited 

contract data on the direct 

delivery notice, so this 

change is an enhancement 

to an existing process.
ADC 465, Enclosure 3, Page 6

Originator Response/Comment Disposition

7. USTRANSCOM Approves with comment:

USTRANSCOM requests that the ADC include instructions 

that the implementation date be at least 90 days after the 

ADC release date. USTRANSCOM will require this period 

to allow IGC the necessary time to code, install, test, and 

release the changes required to process this data.

Noted.