ADC 20

Revision of Status Code CX and SK

1. ORIGINATOR:

a. Service/Agency: Navy

b. Originator: Naval Supply Systems Command

2. FUNCTIONAL AREA: Supply

3. REQUESTED CHANGE:

a. Description of Change: This change will require a valid

bill-to/credit-to address on requisition and customer asset

reporting transactions. If the transaction does not pass the

prescribed validation criteria it wi11 be rejected with status code

CX or SK, as appropriate.

b. Procedures:

(1) Short Term: Revise MILSTRIP as indicated below.

Validation will be performed at the Defense Automated Addressing

System Center (DAASC). Applicable DI Codes are: A0_, AM_, AT_, A3_,

A4_, APR, FTA, FTE, and FTF.

Appendix B16, modify explanation for Status Codes CX, SJ, and SK:

REQUISITION TRANSACTION STATUS CODES

CODE EXPLANATION

CX Rejected. Unable to identify the bill-to and or ship-to

address as designated by the signal code or the

signal code is invalid. If still required, submit a

new requisition with valid data entries.

CUSTOMER ASSET REPORTING TRANSACTION STATUS CODES

SJ Rejected. Signal code is blank or incorrect. (Assign a

new document number if a new asset report is

submitted.) (Use on DI FTQ or FTR.)
SK Rejected. Signal code requires compatible fund code.

Unable to identify the ship-from or credit-to address

as designated by the signal code. (Assign a new

document number if a new asset report is submitted.)

(Use on DI FTQ or FTR.)

Chapter 3, revise figure 3-1 (page 3-29):

CODE ENTRY IS BLANK OR INCORRECT

Supplementary Reject (CX status) if blank or invalid and the signal

Address code is B, J, K, L, or M.

 Fund No edit is required unless signal code is C or L. Reject

(CX status) if signal code is C or L, and fund code

does not identify a valid bill-to activity as prescribed

by MILSBILLS (reference (hh)).

[Note: MILSTRIP reference (hh) will be updated to reflect MILSBILLS manual vice

MILSBILLS supplement upon republication of MILSBILLS.]

Chapter 9, revise paragraph L.3. and insert new paragraph L.5.

(renumber remaining paragraphs):

L. DEFENSE AUTOMATIC ADDRESSING SYSTEM

DAAS will accomplish the following:

1. DIs FTL, FTM, FTP, and FTT will be passed to the activity

represented by the RI in rp 4-6.

2. DIs FTB, FTD, FTQ, FTR, FTZ, and FT6 will be routed using the

M&S code.

3. DI FTA will be passed to the RI in 4-6. DIs FTC, FTE, and FTF

containing M&S 9 will be passed to the RI in rp 4-6. by DAAS when the signal

code is C or L and the code in rp 52 identifies a valid bill-to DoDAAC using the

fund code supplement to MILSBILLS (reference (hh)). If the signal code is not

C or L or the activity in rp 52 cannot be identified, DAAS will return the

transaction to the originating station with a narrative explanation of the reason

for return. When DI FTA does not contain M&S 9, DAAS will pass the

transaction to the RI in rp 4-6.

4. When DIs FTC, FTE, and FTF do not contain M&S 9, DAAS will

perform an NSN/NIIN validation and SOS edit as follows:
a. If the NSN is correct and managed by the ICP/IMM identified

in rp 4-6, Advice Code 3T will be entered in rp 65-66 and the document will be

transmitted to that ICP/IMM.

b. If the NSN is correct but is not managed by the ICP/IMM

identified in rp 4-6, the correct ICP/IMM RI will be entered in rp 4-6, Advice

Code 3T will be entered in rp 65-66, and the document will be transmitted to

the correct ICP/IMM. DAAS will furnish the reporting activity a DAAS Customer

Asset Report Status (DI FTQ) with Status Code TZ in rp 65-66.

c. If the FSC/NIIN/NSN validation indicates that the FSC is

incorrect, the FSC will be changed and the RI of the ICP/IMM in rp 4-6 will be

changed where applicable. Advice Code 3T will be entered in rp 65-66 and

the document will be transmitted to the managing ICP/IMM. DAAS will furnish

the reporting activity an DI FTQ with Status Code TZ in rp 65-66.

d. If routing to an ICP/IMM cannot be accomplished by DAAS,

the document will be passed to the activity identified in rp 4-6.

5. DAAS will validate DI FTA, FTE, and FTF transactions for valid

ship-from and credit-to addresses as designated by the signal code.

When the signal code is C or L, the code in rp 52 must identify a valid

credit-to activity as prescribed by MILSBILLS (reference (hh)). If DAAS

cannot identify the ship-from or credit-to address, the transaction will be

rejected to the originating activity using DI FTQ with SK status.

(2) DLMS. Implement corresponding changes under the

DLMS.

(3) Long Term. Above validation will be performed at the

supply source. This will require access to DOD 4000.25-7-M-S-1,

MILSBILL Fund Code Supplement information through automated

interface or data sharing techniques.

4. REASON FOR CHANGE: This change is required to reduce the number

of unprocessed bills. MILSBILLS interfund reimbursement procedures

were revised to prohibit reimbursing sellers when they identify

invalid DoDAACs as bill-to addresses. Accordingly, ICP/IMMs will

not be reimbursed for issues charged to invalid DoDAACs. ICPs/IMMs

are bearing the burden; that is, expending considerable effort to

research and correct, requisitioner invalid bill-to DoDAAC errors.

This change will help to correct the problem at the source.

5. ADVANTAGES/DISADVANTAGES:

a. Advantages: This change will significantly reduce the

number of unbillable bills and transfer the burden of such problems

to the source.
b. Disadvantages: Requisitions will be returned without supply

action, therefore, causing delay in filling the requisition.

6. IMPACT: Implementation of the short-term procedures will not

require changes to Component systems. Long-term procedures will be

accomplished as Components migrate to modernized systems.