1 / 6

Transportation Control Number (TCN) Construction Issue (MILSTRIP Requisitions)

Transportation Control Number (TCN) Construction Issue (MILSTRIP Requisitions). Heidi Daverede HQ DLA J-3733 November 29, 2006. Background. DSS shipment transactions are being rejected by downstream systems due to use of numeric values in rp15 of the TCN.

dolan
Download Presentation

Transportation Control Number (TCN) Construction Issue (MILSTRIP Requisitions)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Transportation Control Number (TCN) Construction Issue(MILSTRIP Requisitions) Heidi Daverede HQ DLA J-3733 November 29, 2006

  2. Background • DSS shipment transactions are being rejected by downstream systems due to use of numeric values in rp15 of the TCN. • Impact: advanced shipment information is not prelodging in the port systems, which slows the incheck processing of the cargo • MILSTRIP guidance indicates that numeric values are authorized in rp15 • A DTR change was proposed to clarify the TCN construction policy; however, the proposed change is being held in suspense due to a conflict with suffix code assignments.

  3. Defense Transportation Regulation Part II, Appendix LParagraphs B and C • TCN Construction in response to MILSTRIP requisitions: • rp1-14: Enter MILSTRIP requisition document number • rp15: Enter the suffix code; if none, enter “X” • rp16: Enter the partial shipment code • rp17: Enter the split shipment code

  4. Military Standard Requisitioningand Issuing ProceduresAppendix 2.8 • Suffix Codes: • Decentralized distribution system block assignment to preclude duplication: • A through E Initial Processing Source • F through H,J,K First Secondary Processing Source • L,M,Q,T,U Second Secondary Processing Source • V through X Third Secondary Processing Source • 2 through 9 Fourth Secondary Processing Source • Centralized distribution system assignment: • A through Z, 2 through 9, exclusive of I,N,O,P,R,S,Y,Z • Demand Codes: I,N,O,P,R,S,Z,1,0

  5. Issue • MILSTRIP and DTR Suffix Code Guidance are in conflict • MILSTRIP allows “X” as a valid suffix code • DTR allows “X” as a default when the suffix code in the document number is blank • Impact: • If tracking a MILSTRIP order by TCN and if there is an “X” in rp15, there is no way to know by looking at the TCN if the requisition was partialled or not. The user has to perform a further inquiries to review the supply data to determine if the initial order was partialled.

  6. Recommendation • Modify MILSTRIP to remove “X” as a suffix code • Insert MILSTRIP table into DTR to clearly identify the valid values for rp15 of the TCN and a default value of “X” when there is no suffix code.

More Related