DEFENSE LOGISTICS AGENCY HEADQUARTERS 8725 JOHN J. KINGMAN ROAD FORT BELVOIR, VIRGINIA 22060-6221 December 14, 2017 MEMORANDUM FOR SUPPLY AND FINANCE PROCESS REVIEW COMMITTEE (PRC) MEMBERS SUBJECT: Proposed Defense Logistics Management Standards (DLMS) Change (PDC) 1288, Mandatory Supply Status to Requisition Bill-To DOD Activity Address Code (DoDAAC) and Supply Status Revisions for Standard Line of Accounting (SLOA)/Accounting Classification (Supply/Finance) We are forwarding the attached proposed change to DLM 4000.25, Defense Logistics Management Standards, and DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP), for evaluation and submission of a single coordinated DOD Component position. It is the responsibility of the Component Supply and Finance PRC representatives to ensure full coordination of the proposal within their Component. Request you review the attached proposed change and provide your comments/concurrence to the Enterprise Business Standards Office not later than 45 days from the date of this memorandum. If you non-concur, please provide an alternate method to meet the requirement being addressed. Addressees may direct questions to Mr. Eric Flanagan and Ms. Ellen Hilert, email: DLMS_MILSTRIP@dla.mil, or Mr. Robert Hammond, Chair, Finance PRC, email finance@hq.dla.mil. All others must contact their Component designated Supply or Finance PRC representative available at www.dla.mil/hq/informationoperations/dlms/allpoc. Attachment As stated HEIDI M. DAVEREDE Program Manager Enterprise Business Standards Office cc: ODASD (SCI) OUSD(C)
Attachment to PDC 1288 Mandatory Supply Status to Requisition Bill-To DOD Activity Address Code (DoDAAC) and Supply Status Revisions for Standard Line of Accounting (SLOA)/Accounting Classification 1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: a. Mr. Eric Flanagan and Ms. Ellen Hilert, Military Standard Requisitioning and Issue Procedures (MILSTRIP), email: DLMS_MILSTRIP@dla.mil b. Mr. Robert Hammond, Chair, Finance PRC, email: finance@hq.dla.mil 2. FUNCTIONAL AREA: Supply/Finance 3. REFERENCES: a. DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP) b. DLM 4000.25, Defense Logistics Management Standards (DLMS), Volume 2, Supply Standards and Procedures, and Volume 4, Military Standard Billing System Finance c. Approved DLMS Change (ADC) 1043, Revisions for Department of Defense (DOD) SLOA/Accounting Classification, September 18, 2013 (also refer to PDC 1288 Addendums) d. ADC 1068, Enhanced Procedures for Requisitioning via DOD EMALL and GSA Internet Ordering: Component Verification of Funds Availability and Materiel Identification using the Supplier-Assigned Part Number and/or Supplier Commercial and Government Entity (CAGE) Code, October 3, 2013 e. ADC 328, Off-Line Requisition Processing: Internet Ordering Application Request for Component Verification of Funds Availability and Recording of the Financial Obligation, July 28, 2009 f. ADC 1009A, DLMS Enhancements for Requisitioning to Improve Use of Mark-for Addressing, Expand Authorized Priority Designator Validation, Correct EMALL Purchase/Credit Card Format Rules, and Require Distribution of Status for Requisitions associated with Purchase/Credit Card Payment, August 6, 2014 4. REQUESTED CHANGE(S): a. Brief Overview: This change will require the Defense Automatic Addressing System (DAAS) to provide mandatory supply status to the bill-to DoDAAC. The purpose of this change is to address a gap that exists when an obligation is not recorded against a requisition or appropriately updated based upon order processing. Missing obligations may be due to an order that is placed outside of a Component ordering system (e.g., orders submitted using web ordering systems) and other instances where the bill-to DoDAAC may not have visibility of the requisition (such as third party billing via the Fund Code to Billed Office DoDAAC Table). Providing supply status to the bill-to DoDAAC allows the financial system supporting the bill-to activity to establish an obligation based on the information conveyed by the status code in the event that one was not previously assigned. The Page 1
financial system will also use the supply status to update the obligation based on the original order data as this information changes during order processing. Order fulfillment systems must support creation of MILSTRIP supply status and financial systems must support use of the supply status to establish or update obligations for requisitions. Components must integrate supply and financial systems to create/adjust obligations based on receipt of applicable supply status. Staffing Note: Components please comment regarding whether routing supply status to the bill-to DoDAAC s Billing COMMRI vice the Data Processing (DP) COMMRI will route status to the correct financial system for recording/adjusting the obligation. In the absence of an automated interface between supply and financial systems, please comment on whether or not and obligations are adjusted, and if so, how. b. Background: (1) Status Transactions: MILSTRIP (Reference 3.a. and 3.b.) requires sources of supply to furnish supply status (DLMS 870S/legacy MILSTRIP Document Identifier Code (DIC) AE_) as a notice of action taken or being taken on MILSTRIP transactions, using status codes published in MILSTRIP Appendix AP2.16, Status Codes. (a) DAAS transmits status based on MILSTRIP distribution rules. Eligible status recipients include the requisitioner, ship-to, bill-to, or other organizations identified by the distribution code. Activities to receive status data and the type of data required are designated by the media and status (M&S) code and distribution code. There is also a DLMS enhancement to identify discretely all status recipients by DoDAAC. Under certain conditions, the media and status code limits status distribution. Upon approval of this change, those conditions will no longer prevent mandatory supply status being provided to the bill-to activity. (b) ADC 1043 (Reference 3.c.) added discrete SLOA/Accounting Classification data elements to logistics transactions with financial implications to implement SLOA within DLMS. Although this ADC identified the DLMS 870S Supply Status as carrying the fund code, the appropriate financial implications were not recognized and this transaction was not included for SLOA updates. Because this proposal identifies specific financial implications for the supply status transaction, SLOA updates must be incorporated in the DLMS IC at this time. Additionally, as noted in ADC 1043, DLMS transactions lacking the X12 FA2 segment for consistent mapping of the SLOA data must use the X12 REF and DTM segments to convey the SLOA data elements. The 870S is one of the transactions lacking the FA2 segment. Mapping identified for the SLOA data in the 870S is based on approved mapping for the DLMS 856S Shipment Status. (c) Supply status may be informational or require additional action by recipients based on the status code. Typically supply status indicates: item being processed for release and shipment (includes estimated shipping date), backorder, procurement or direct vendor delivery, partial issue or other partial action, processing delay, rejection, passing or referral to another source of supply, cancellation. Page 2
(2) Impact of Status on Financial Obligations: Sources of supply prepare supply status transactions alerting status recipients when adjustments to obligations are required. Changes to price or quantity, as identified by supply status, will trigger appropriate updates to financial records when the supply and financial systems are integrated. During requisition cancellation initiated by the requisitioner, funds must not be deobligated until supply status has been received indicating that cancellation has been accomplished (rather than based upon the cancellation request). Some status code definitions specifically call out required financial actions, such as those listed below. Refer to MILSTRIP Appendix 2.16 (Reference 3.a) for the full set of supply status codes. Code Explanation BN BH B9 DT Requisition being processed as free issue. Signal and fund code fields corrected as noticed. Adjust local fund obligation records. Service coordinated/approved substituted/interchangeable item, identified in stock number field, will be supplied requisition or requisition alert. Examine unit of issue, quantity, and unit price fields for possible changes. Revise appropriate records accordingly. Additional status will be provided. The activity identified by the code in rp 4-6 is in receipt of your cancellation request. Action to cancel the demand or to divert the applicable shipment is being attempted. Do not deobligate funds or delete due-in. Advice of final action will be furnished in subsequent status transactions. Free issue denied; either the complete or partial quantity of a post-post requirement (includes DIC Code C0_, CQ_, D7_) is not authorized for free issue. Fund code and/or signal code corrected as noted. Adjust local fund obligation records. Even when not specifically cited, Components must take appropriate financial actions when applicable: B7 BJ Unit price change. The latest unit price for the item identified by the stock or part number in rp 8-22 is reflected in rp 74-80. Quantity changed to conform to unit pack or because of allowable direct delivery contract variance; adjust the due-in records accordingly. Unit of issue is not changed. Receipt of supply status by the bill-to activity indicating materiel is being released for shipment must trigger interaction with financial processes/systems to confirm that the appropriate obligation is recorded: BA Item being processed for release and shipment on a requisition or requisition alert. The estimated shipping date (ESD) is contained in record position (rp) 70-73 when provided in response to a follow-up. Page 3
Even when requisition processing is delayed, the obligation should be recorded pending subsequent status that indicates successful processing, partial order fulfillment, or denial (resulting deobligation). BD Requisition is delayed: (1) Delay due to need to verify requirements relative to authorized application, item identification, or technical data. (2) Requisition alert fulfillment is delayed due to need to verify requirements relative to item identification. Re-identification of NSN materiel to unit of use LSN required. (3) Requisition for government furnished materiel (GFM) is delayed pending validation by either contracting management control activity (MCA) or between source of supply and MCA. See rp 4-6 to determine the activity performing the validation. Upon completion of review, additional status will be provided to indicate action taken. (4) If used with Management Code R, delay due to storage activity denial on the identified suffix. Clear/update local records for suffix and quantity identified. Further action on the denied quantity is anticipated to occur on a subsequent suffix code. Staffing Note: Components must be careful not to over-obligate based upon Status Code BD used with Management Code R (per Reason 4 above). Supply status must include required information to successfully post the obligation: materiel identification billed unit price fund code bill-to activity ordering activity Additionally SLOA data will be included when available from the original requisition or when populated by DAAS. c. Proposed Change in Detail: (1) Modify DAAS to furnish mandatory supply status to the bill-to DoDAAC (based on the Data Processing (DP) Communications Routing Identifier (COMMRI). For third party billing, DAAS will retrieve the bill-to DoDAAC from the Fund Code to Billed Office DoDAAC Table when necessary pending full DLMS implementation of the bill-to party in the DLMS requisition format. DAAS will transmit supply status to the bill-to party associated with third party billing by legacy DIC AE9. DAAS will provide this status regardless of the M&S code. DAAS will implement this requirement in a way that does not transmit multiple supply status transactions to the same activity. Staffing Note: Components please comment regarding whether routing supply status to the DP COMMRI vice the bill-to DoDAAC s Billing COMMRI will route status to the correct financial system for recording/adjusting the obligation. (2) Modify the DLMS 870S to carry SLOA data content. See Enclosure for details. Page 4
(3) Source of supply systems processing DLMS 511R transactions containing SLOA data will perpetuate the SLOA data content to the supply status. (4) DAAS will edit supply status transactions for SLOA data content. When available, DAAS will use the Standard Financial Information Structure (SFIS) Fund Code to Fund Account Conversion Table, to populate SLOA data when no discrete SLOA data is present in the supply status. If discrete values for the SLOA data elements in the transaction do not match data elements from the SFIS Fund Code to Fund Account Conversion Table for the Fund Code in the transaction, the unmatched SLOA data elements will be removed from the supply status. DAAS will not reject supply status transactions. DAAS will generate a separate supply status transaction (870S/legacy Document Identifier Code (DIC) AE9) with Status Code BK to provide an audit trail of the DAAS update to the transaction. (5) Components responsible for business processes that authorize requisitioning outside of the requisitioning Component s supply system (off-line ordering) associated with interfund or noninterfund billing must generate supply status under MILSTRIP business rules. Staffing Note: Components must identify any desired exclusions for this requirement (e.g., DLA Subsistence Total Order and Receipt Electronic System (STORES). (6) Components must update supply and financial systems to ensure obligations are established or updated based upon receipt of supply status by the requisitioner or by the bill-to activity (if different from the requisitioner). Refer to MILSTRIP Appendix 2.16 for the full set of supply status codes and to the background information in this proposal for examples of supply status codes that initiate financial actions. Components should expect to receive supply status transactions associated with requisitions initiated outside the Component s supply system (off-line ordering) in addition to routine supply status associated with submission of MILSTRIP requisitions from the Component s supply system. This change does not alter financial processes associated with requisitions funded by Government purchase card or Military Interdepartmental Purchase Request (MIPR); therefore, Component systems must recognize supply status transactions associated with these to preclude overobligation. d. Revisions to DLM 4000.25 Manuals: Insert new paragraphs and renumber remaining paragraphs as applicable. enclosure. (1) Revise the DLMS 870S Supply Status for SLOA data content as shown in the (2) Modify DLM 4000.25-1, Chapter 4, Status, as follows: C4.1.6.1 Mandatory Status to the Bill-To DoDAAC. DAAS will furnish mandatory supply status to the bill-to DoDAAC regardless of the media and status code. (3) Modify DLM 4000.25-1, Appendix 2.1, Document Identifier Codes, as follows: AE9 Supply Status From DAAS: (Intervening text not shown) Page 5
f. To the bill-to party to provide mandatory supply status when third-party billing applies (bill-to-party not identified as requisitioner, ship-to activity, or by distribution code). (4) Modify DLM 4000.25-1, Appendix 2.4, Media and Status Codes, as follows: AP2.4.1.6.2.5. The mandatory provision of supply status to the bill-to activity. (Intervening text not shown) AP2.4.1.11. M&S Codes are listed below. M&S Codes Used with Requisition-Related Transactions CODE EXPLANATION 0 No status to requisitioner or ship-to and/or credit other than mandatory shipment status to the ship-to activity and mandatory supply status to the bill-to activity. One hundred percent supply status and shipment status to the activity designated by a significant entry in the distribution code (first position). Y No status to requisitioner or ship-to and/or credit-to as perpetuated to the SUPADD other than mandatory shipment status to the ship-to activity and mandatory supply status to the bill-to activity. Exception supply status and shipment status to the activity designated by a significant entry in the distribution code. (5) Modify DLM 4000.25-1, Appendix 2.16, Status Codes, as follows: BK Modified. (1) Requisition data elements have been modified as requested. Examine data fields in this status document for current requisition data. (2) Used by DAAS on DIC AE9 and by GSA on DIC AE_ to advise that the requisition contained a requisition priority for which the activity was not authorized. The requisition priority has been downgraded as shown and the requisition forwarded for processing. (3) Used by DAAS on DIC AE9 to advise that the requisition contained an invalid/expired OSD/CJCS category D project code. The project code has been blanked out and the requisition forwarded for processing. (4) Used by DAAS on DIC AE9 or by source of supply to advise the customer that the requisition priority designator and/or required delivery date (RDD) data fields continued invalid or incompatible data. Customer entry has been modified or blanked out and the requisition forwarded for processing. (5) Used by DAAS on DIC AE9 or by the source of supply to advise that submitter s fund code has been replaced by Fund Code XP requiring non-interfund billing. (6) Used by DAAS on DIC AE9 to advise customers that SLOA data content mismatched to the Fund Code on the SFIS Fund Code to Fund Account Conversion Table has been removed. Page 6
(6) Modify DLM 4000.25, Volume 2, Supply Standards and Procedures, Chapter 5, Status Reporting, as follows: C5.1.6.11.1 Mandatory Status to the Bill-To DoDAAC. DAAS will furnish mandatory supply status to the bill-to DoDAAC regardless of the media and status code. (7) Modify DLM 4000.25, Volume 4, Finance, Chapter 2, Billing Procedures, as follows: C2.1.7. Obligations for Requisitioned Materiel. Establishing an obligation for the proper amount under the requisition document number is essential for the timely and automated processing of interfund bills. Failure to do so is a violation of financial management procedures and may delay processing and increase workload for both DFAS and submitting Component personnel. DoD Components that either (1) establish business processes for requisitioning outside their customer s Component sponsored supply system, e.g., via internet ordering applications, or (2) authorize their own Component personnel to satisfy requirements through the use of external ordering processes, will support adherence to standard DoD financial business processes. C2.1.7.1. DoD Components will use MILSTRIP supply status transactions to either establish or update obligations for requisitions associated with Interfund or non-interfund billing. C2.1.7.2 DoD Components may authorize manual recording of the financial obligation by the customer as a separate action until such time as an automated interface between the ordering application and a Component-sponsored financial system is available. Where an interface is not available, external ordering applications will alert users to comply with their Component-directed financial procedures. C2.1.7.3. The bill-to party should obligate the entire properly made amount of a reimbursable order when the order is accepted. C2.1.7.4. The bill-to party must record obligations in the official accounting records at the time a legal obligation is incurred, or as close to the time of incurrence as is feasible. In no instance will the requesting agency record obligations any later than 10 calendar days following the day that an obligation is incurred. C2.1.7.5. The bill-to party must record obligations at the line item level with one requisition per line item. This supports required line-item detail billing for requisitions that will be billed via the DLMS 810L Logistics Bill. Staffing Note: Components, please comment on any business process for which this will be problematic in the near term. Page 7
Proposed Transaction Flow: e. Alternatives: Providing supply status to the bill-to activity is one approach to ensuring that an obligation is established. Other options exist or are being considered, but these would not provide the capability to update the bill-to system when the order fulfillment process results in changes to the original obligation. These options currently include ADC 1068 (Reference 3.d.) where the DOD EMALL and GSA Advantage/GSA Global programs have made a funds verification transaction exchange process available to Components that would like to participate. Additionally, EBSO is evaluating the need for a DLMS 821 Obligation transaction for selected business processes. 5. REASON FOR CHANGE: This change addresses a gap that exists when the bill-to activity does not receive the supply status information that is necessary to trigger appropriate updates to financial records. These updates may be used to adjust obligations. The gap occurs when there is insufficient internal integration between the Component supply and finance systems and when an order is placed outside of the Component s ordering system, and, therefore, does not generate an obligation. Establishing an obligation for the proper amount under the requisition document number at the time the order is accepted is essential for the timely and automated processing of interfund bills and for noninterfund billing. Failure to do so is a violation of financial management procedures, may delay processing, and may increase workload for both DFAS and submitting Component personnel. Additionally, mandatory distribution of supply status to the bill-to activity ensures that changes to the supply records (e.g., based upon price changes or quantity subsequent to the initial order) are replicated in the obligation. 6. ADVANTAGES AND DISADVANTAGES: a. Advantages: This change will help the Components achieve clean audit opinions, improve financial accountability, and mitigate errors caused the manual actions that result from missing obligation records. Page 8
b. Disadvantages: None identified. 7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: The target implementation for DAAS to complete programming to pass transactions to the bill-to activity is 60 days from the release of the approved change. SLOA data enhancement may be completed by November 2018. 8. ADDITIONAL COMMENTS TO CONSIDER: Components should consider whether supply status will be sufficient for all scenarios or whether a companion requirement for mandatory transmission of shipment status to the bill-to activity is also needed to ensure obligations are established and updated appropriately for requisitioned materiel. 9. ADDITIONAL FUNCTIONAL REQUIREMENTS: a. This change does not establish a DLMS requirement for systemic transmission of an obligation notice by Components sponsoring business processes requiring customer requisitioning outside the customer s Component sponsored supply system. However, new DLMS transaction to accomplish this is under consideration in EBSO (e.g., a DLMS transaction based on the X12 821). Component feedback on this initiative is welcome. b. Upon implementation of supply status for requisitions initiated outside the requisitioning Component s supply system, ship-to activities must use incoming supply status to create a due-in record (if unmatched to an existing due-in record) or update to an existing due-in record. The goal to use status transactions to establish a due-in record at the ship-to activity was discussed in ADC 328 (Reference 3.e.) and ADC 1009A (Reference 3.f.). ADC 1009A eliminates DOD-level authorization for the DAAS block on transmission of supply and shipment status in response to requisitions originated in FEDMALL (originally DOD EMALL) that use purchase card/credit card payment. Availability of supply status for off-line ordering supports creation of due-in records, thereby facilitating receipt processing and generation of materiel receipt acknowledgment (MRA) transactions to the source of supply. 10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH IMPLEMENTATION OF THIS CHANGE: There is a significant cost avoidance associated with eliminating manual processes to maintain obligations for requisitioned materiel. 11. IMPACT: a. New DLMS Data Elements: None b. Changes to DLMS Data Elements: None c. Automated Information Systems (AIS): (1) Components must provide supply status for all requisitions including those created outside the requisitioning activities supply systems. (2) Components must update supply/financial system functionality to receive supply status transactions as a means to establish or update obligations. (3) Components must use supply status to create or update due-in records. Page 9
d. DAAS: DAAS updates are required as described above to generate supply status to the billto party and map/edit SLOA data content in the supply status transaction. DAAS logic will suppress duplication of status to the same activity (e.g. when bill-to and ship-to are the same). e. Non-DLM 4000.25 Series Publications: Internal Component guidance may require update. Page 10
Enclosure, DLMS 870S Implementation Convention (IC) Revisions # Location 870S Supply Status Reason 1. DLMS Introductory Notes Add PDC 1288 - PDC 1288, Mandatory Supply Status to Requisition Bill-To DOD Activity Address Code (DoDAAC) and Supply Status Revisions for Standard Line of Accounting (SLOA)/Accounting Classification 2. 2/HL/10 Remove existing segment level Federal note and add new DLMS notes at the segment level: Federal Note: The transaction set hierarchical data structure is transaction number only. Identifies DLMS changes included in the DLMS IC. Establishes an HL loop specifically for SLOA information. The transaction set hierarchical data structure is transaction reference number for each supply status loop and an additional 2/HL/10 loop iteration to identify financial information in support of SLOA/Accounting Classification information requirements. 3. 2/HL03/10 Add new code and FI Financial Information Use to identify the Financial Information loop to provide DoD SLOA/Accounting Classification information. The Finance loop includes only the REF/87 and DTM/240 segments. Refer to PDC 1288. 4. 2/REF/87 Remove existing segment level Federal note and revise DLMS notes at the segment level as follows: Identifies an HL loop within a transaction to provide SLOA information. Clarifies the location of SLOA data. Federal Note: To provide financial data: cite the fund purpose code and either or both of the fund code and the long-line accounting data. When citing long-line accounting data use REF03 and components of REF04. 1. Use multiple repetitions in the Supply Status loop (HL01=W) to identify the customer assigned transaction document number, Government Furnished Materiel (GFM) related information, and funding data fund code. 2. DLMS users see the Accounting Classification Appendix for specific entries for the basic appropriation number and supplemental accounting classification data. Use multiple repetitions in the Financial Information loop (HL01=FI) to comply with the DoD SLOA/Accounting Classification. Cost object elements Project Identifier, Funding Center Identifier, Functional Area, Cost Element Code, Cost Enclosure, PDC 1288 Page 1
# Location 870S Supply Status Reason Center Identifier, Activity Identifier, and Work Order Number are used as appropriate for the system. Refer to PDC 1288. 5. 2/REF01/87 Add the following qualifiers and DLMS notes: 2E Foreign Military Sales Case Number the Security Cooperation Case Designator. Refer to PDC 1288. AGY Agency Dispersing Identifier Code the Agency Dispersing Identifier Code. Refer to PDC 1288. 3. Code AGY is adopted as a migration code for use in the AGZ Agency Accounting Identifier the Agency Accounting Identifier. Refer to PDC 1288. 3. Code AGZ is adopted as a migration code for use in the AVT Availability Type the Availability Type. Refer to PDC 1288. 3. Code AVT is adopted as a migration code for use in the BET Business Event Type Code 1. Reserved for DoD SLOA/Accounting Classification use to identify the Business Event Type Code. Refer to PDC 1288. 2. Business Event Type Code is a potential future DLMS enhancement; see introductory DLMS note 2a. These qualifiers have been mapped to specific SFIS data elements for SLOA. Enclosure, PDC 1288 Page 2
# Location 870S Supply Status Reason 3. Code BET is adopted as a migration code for use in the BLI Budget Line Item the Budget Line Item. Refer to PDC 1288. 3. Code BLI adopted as a migration code for use in the 870S, version 4010. This code is approved for use in a later version. DP Department Number the Department Regular. Refer to PDC 1288. 2. Authorized DLMS enhancement; see introductory LI Line Item Identifier (Seller s) the Security Cooperation Case Line Item Identifier. Refer to PDC 1288. MAT Main Account the Main Account. Refer to PDC 1288. 3. Code MAT is adopted as a migration code for use in the REB Reimbursable Code the Reimbursable Flag. Refer to PDC 1288. 3. Code REB adopted as a migration code for use in the SAT Sub Account the Sub Account. Refer to PDC 1288. Enclosure, PDC 1288 Page 3
# Location 870S Supply Status Reason 3. Code SAT adopted as a migration code for use in the 870S, version 4010. This code is approved for use in a later version. SBA Sub-Allocation the Sub-Allocation (formerly known as Limit/Subhead). Refer to PDC 1288. 3. Code SBA is adopted as a migration code for use in the SCC Security Cooperation Customer Code the Security Cooperation Customer Code. Refer to PDC 1288. 2. DLMS enhancement; see introductory DLMS note 2d. A field size exceeding 2 positions is not supportable under current MILSTRIP and MAPAC processes. Three character codes are not authorized at this time. 3. Code SCC is adopted as a migration code for use in the SCI Security Cooperation Implementing Agency the Security Cooperation Implementing Agency. Refer to PDC 1288. A field size exceeding 3 positions is not supportable under current MILSTRIP processes. Four character codes are not authorized at this time. 3. Code IA is adopted as a migration code for use in the SCL Sub Class 1. Reserved for DoD SLOA/Accounting Classification use to identify the Sub Class. Refer to PDC 1288. 2. Sub Class is a potential future DLMS enhancement; see introductory DLMS note 2a. 3. Code SCL is adopted as a migration code for use in the Enclosure, PDC 1288 Page 4
# Location 870S Supply Status Reason TF Transfer Number the Department Transfer. Refer to PDC 1288. 2. Authorized DLMS enhancement; see introductory XX4 Object Code the Object Class. Refer to PDC 1288. 3. Code XX4 is adopted as a migration code for use in the 6. 2/REF01/87 Add the following qualifiers and DLMS notes: ECA Fund Identifier the Funding Center Identifier. Refer to PDC 1288. These qualifiers are mapped to specific SFIS data elements for SLOA cost objects. 9X Account Category the Functional Area. Refer to PDC 1288. 91 Cost Element the Cost Element Code. Refer to PDC 1288. 79 Cost Account the Cost Center Identifier. Refer to PDC 1288. BE Business Activity the Activity Identifier. Refer to PDC 1288. Enclosure, PDC 1288 Page 5
# Location 870S Supply Status Reason JB Job (Project) Number the Project Identifier. Refer to PDC 1288. 7. 2/REF01/87 Revise DLMS notes for existing qualifiers: 9R Job Order Number 1. Use to identify the Job Order (JO) Number. 2. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 381. 3. For DoD SLOA/Accounting Classification compliance the Job Order Number may be repeated as a Work Order Number (N901 Qualifier WO). Refer to ADC 1288. WO Work Order Number 1. Use to identify a maintenance work order number. Authorized DLMS enhancement under DLA industrial activity support agreement. Refer to ADC 379. 2. For DoD SLOA/Accounting Classification use to identify the Work Order Number. Refer to ADC 1288. Authorized DLMS enhancement; see introductory DLMS 8. 2/REF03/87 Remove existing Federal note: Description Federal Note: Use only with REF01 code FG and REF04 code AT to cite the supplemental accounting classification data. 9. 2/REF04/87 Remove existing Federal note: Federal Note: When providing financial data (REF01 code FG): If providing only the fund code use REF04-01 code FU and cite the fund code in REF04-02. If providing the long-line accounting data use REF04-01 code AT and cite the basic appropriation data in REF04-02. Use REF04-03 code 10 and cite the accounting station number in REF04-04. If providing both use REF04-01 code FU, REF04-03 code AT and REF04-05 code 10 citing the related data in the following data element of the pair. 10. 2/REF04-10 Remove existing Codes 10 and AT and associated DLMS note: 10 Account Managers Code Clarifies SLOA requirements related to existing data elements. This financial data enhancements replaced by SLOA data content. This financial data enhancements replaced by SLOA data content. These financial data enhancements replaced by SLOA data content. Enclosure, PDC 1288 Page 6
# Location 870S Supply Status Reason Use in one of REF04-03 or REF04-05 to identify the authorized accounting activity (AAA)/accounting disbursing station number (ADSN)/fiscal station number (FSN). 11.. 2/LQ/145 AT Appropriation Number Use in one of REF04-01 or REF04-03 to identify the basic appropriation data. Move existing Federal note to the DLMS note level. Federal Note: Use to identify codes, as appropriate, consistent with management information requirements. Administrative change to remove Federal note. 1. Use to identify codes, as appropriate, consistent with management information requirements. 2. Code lists at this level are intended to be applicable to the document number level (i.e. do not differ by suffix for split shipments). This is intended to support a future DLMS enhancement which would accommodate multiple supply status transactions within a single transmission of the 870S. At this time, only a single supply status may be transmitted per transaction set. 12. 2/LQ01/3500 Add DLMS notes for existing Qualifier 78 and remove Qualifiers 85 and A4: 78 Project Code 1. Use to identify the applicable Project Code. 2. For DoD SLOA/Accounting Classification compliance (2/HL/0100 Finance loop) the Project Code may be repeated as a Project Identifier (2/REF01//87 Qualifier JB). Refer to PDC 1288. 85 Country and Activity Code 1. Use to identify Security Cooperation Customer Code. 2. DLMS enhancement; see introductory DLMS note 2a. A4 Case Designator Number 1. Must use in FMS transactions to identify the FMS case number. For Cooperative Logistics Supply Support Arrangements (CLSSAs), repeat up to two times to identify the FMS Foreign Military Services Order (FMSO) I and FMSO II case numbers. In this instance, the first occurrence will cite the FMSO I case number, and a second occurrence, if applicable, will reflect the FMSO II case number. 2. DLMS enhancement; see introductory DLMS note 2a. SLOA compliance requires identification of the Project Identifier for which the Project Code is an authorized legacy equivalent. Project Code is retained as a separate data element for logistics business processes requiring specific identification of this information. Removing qualifier 85 as this current DLMS enhancement for the Country and Activity Code is duplicative of required Security Cooperation Customer Code. Planned DLMS enhancement for two repetitions is obsolete. There is no requirement Enclosure, PDC 1288 Page 7
# Location 870S Supply Status Reason to include both the FMSO I case identifier and the FMSO II case identifier in a single requisition. Linking the FMSO I case identifier to the FMSO II case identifier is accomplished via the Defense Security Assistance Management System (DSAMS). The FMS case number is removed from the LQ Segment because the value is not associated with a code list. Moved to HL03=FI loop. 13. 2/DTM/240 Remove Federal note and replace as DLMS note: Federal Note: Use to identify dates associated with the transaction. Administrative change to remove Federal note. Use to identify dates associated with the transaction. 14. 2/DTM01/240 Add the following qualifiers and DLMS notes: 283 Funds Appropriation Start the Beginning Period of Availability Fiscal Year Date. Refer to PDC 1288. These qualifiers are mapped to specific SFIS data elements for SLOA. 284 Funds Appropriation End the Ending Period of Availability Fiscal Year Date. Refer to PDC 1288. Enclosure, PDC 1288 Page 8