afh23-123v1.pdf

Administrative Changes to AFH 23-123V1, Materiel Management Reference Information

OPR: AF/A4LR Supply Chain Materiel Policy Branch

References throughout to “AF/A4LM” are hereby changed to “AF/A4LR”.

References throughout to “AFMC SCM-R Activity” are hereby changed to “AFMC”.

References throughout to “DLM 4000.25-2-M” are hereby changed to “DLM 4000.25-2”.

References throughout to “DoD 4140.1-R” are hereby changed to “DoDM 4140.01”.

References throughout to “AFJMAN 23-215” are hereby changed to “DLMS 4000.25”.

8 January 2015

BY ORDER OF THE

SECRETARY OF THE AIR FORCE

AIR FORCE HANDBOOK 23-123, Volume 1

8 AUGUST 2013

Incorporating Change 1, 6 NOVEMBER 2014

Materiel Management

MATERIEL MANAGEMENT REFERENCE

INFORMATION

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: Publications and forms are available on the e-Publishing website at www.e-publishing.af.mil.

RELEASABILITY: There are no releasability restrictions on this publication.

OPR: AF/A4LM

Supersedes: AFPAM23-118, 15 January 2003

Certified by: AF/A4L

(Maj Gen John B. Cooper)

Pages: 275

This handbook facilitates the implementation of AFI 23-101, Air Force Materiel Management and AFMAN 23-122, Materiel Management Procedures. It provides information regarding

Integrated Logistics System – Supply (ILS-S) and supports the execution of guidance in AFI 23-

101, Air Force Materiel Management and AFMAN 23-122, Materiel Management Procedures.

This guidance applies to all personnel (military, civilian, and contractors) working for the United

States Air Force (USAF) including major commands (MAJCOMs), direct reporting units (DRU), field operating agencies (FOA) and other individuals or organizations as required by binding agreement or obligation with the Department of the Air Force (DAF). This handbook should be used in conjunction with AFI 23-101 and AFMAN 23-122 in the execution of materiel management operations. Refer recommended changes and questions about this publication to the

Office of Primary Responsibility (OPR) using AF Form 847, Recommendation for Change of

Publication; route AF Forms 847 from the field through the appropriate functional’s chain of command. Ensure that all records created as a result of processes prescribed in this publication are maintained in accordance with Air Force Manual (AFMAN) 33-363, Management of

Records, and disposed of in accordance with the Air Force Records Disposition Schedule (RDS) located in the Air Force Records Information Management System (AFRIMS) https://www.my.af.mil/afrims/afrims/afrims/rims.cfm. In accordance with the Paperwork

Reduction Act and DoD policy, ensure that reports of information collections that are collected and/or are compiled and transmitted from the general public are cleared and licensed by the

Office of Management and Budget prior to collection. Information that is collected from other http://www.e-publishing.af.mil./ https://www.my.af.mil/afrims/afrims/afrims/rims.cfm

2 AFH23-123V1 8 AUGST 2013

DoD components or Federal agencies must be approved by DoD and licensed with a report control symbol. See Attachment 1 for a glossary of references and supporting information.

SUMMARY OF CHANGES

This interim change revises AFH 23-123V1 by deleting obsolete material that was erroneously included during the transition from AFMAN 23-110, Air Force Supply System. Changes include deletion of Special Allowance Flags, Special Allowance Code descriptions and the modification of the Classes of Supply Table.

Chapter 1—HANDBOOK OVERVIEW 8

1.1. Purpose

1.2. Description of Volumes

1.3. Relation to other Publications

1.4. Changes to this publication

Chapter 2—DATA ELEMENTS, DEFINITIONS & STANDARD SUPPLY CODES 9

2.1. Purpose

2.2. References

2.3. Data Elements and Definitions

Table 2.1. Action Code--AFEMS

Table 2.2. Action Flag

Table 2.3. Action Taken Codes

Table 2.4. Activity Codes

Table 2.5. Address Type

Table 2.6. Intra-Air Force Advice Codes

Table 2.7. AFEMS Request Number

Table 2.8. AFTO Form 95 Code

Table 2.9. AL/2LM Flag Identification

Table 2.10. Allowance Maintenance Level

Table 2.11. Allowance Maintenance Type

Table 2.12. Allowance Mobility Type Indicator

Table 2.13. AFVSPO Fuel Codes And Comments

Table 2.14. Application Code

Table 2.15. Approval Activity

Table 2.16. Area Code

AFH23-123V1 8 AUGSUT 2013 3

Table 2.17. Authority for Issue Flag and Descriptions

Table 2.18. Non-Stocked Item Due-Out Cause Codes

Table 2.19. Stocked Item Due-Out Cause Codes

Table 2.20. Special Purpose Due-Out Cause Codes

Table 2.21. Basis of Relationship Code

Table 2.22. Scrap Classification and Segregation Guide

Table 2.23. Data Location Flags

Table 2.24. Demand Code

Table 2.25. Intra-Air Force Demand Codes

Table 2.26. Denial Codes

Figure 2.1. Deployed Flag

Table 2.27. Detail Output Flags

Table 2.28. Document File Code (DFC)

Table 2.29. DIFM Status Flags

Table 2.30. Equipment Codes

Table 2.31. Equipment Management Exception Flags

Table 2.32. Evaluator Type

Table 2.33. Exception Flag Codes

Table 2.34. Exception Notice Code (ENC)

Table 2.35. Excess Cause Identification Table

Table 2.36. Expense Record Output Code

Table 2.37. Foam-In-Place Code

Table 2.38. Hold Code Cargo

Table 2.39. Interrogation Code and Date

Table 2.40. Inventory Management Record Adjustment Code--Stock Fund

Table 2.41. Item Codes

Table 2.42. Joint Management Codes

Table 2.43. Lateral Requisition Flag

Table 2.44. MPC Codes

Table 2.45. Major Command Code

Table 2.46. Major Command Reporting Designator

Table 2.47. MACR Update Codes (BC Z Transactions)

Table 2.48. MUC Field Identifiers

4 AFH23-123V1 8 AUGST 2013

Table 2.49. Media of Communication Code

Table 2.50. MICAP Codes

Table 2.51. Mode of Shipment Codes

Table 2.52. National Codification Bureau (NCB) Code

Table 2.53. Organization Code

Table 2.54. Over/Short Flag

Figure 2.2. FAD and UND Conversion Charts

Table 2.55. Quantity Purchased Variation Codes

Table 2.56. Quantity Variance Flag

Table 2.57. Reason Why Codes

Table 2.58. RAMPS Report Codes

Table 2.59. Relationship Codes (RC)

Table 2.60. Disposition Code and Ship-To-Account Code

Table 2.61. Routing Identifier Code Examples

Table 2.62. Serialized Report Code

Table 2.63. DELETED

Table 2.64. SPRAM Flag

Table 2.65. Special Requirements Flag

Table 2.66. SPC Assignment Rules

Table 2.67. Stockage Priority Subgroup Codes

Table 2.68. Stop/Restart Codes

Table 2.69. Substitute Action Codes

Table 2.70. Supply Response Designator Codes and Definitions

Table 2.71. Supportability Code

Table 2.72. Retail System Designator Code (SDC)

Table 2.73. Wholesale System Designator Codes

Table 2.74. Type Adjustment Code

Table 2.75. WRM Type Authorizations

Table 2.76. Type Balance Code

Table 2.77. Not Used

Table 2.78. Type Fuel Code

Table 2.79. Guide to Assigning Type Level Flags

Table 2.80. Type Organization Code

AFH23-123V1 8 AUGSUT 2013 5

Table 2.81. Type Procurement Code

Table 2.82. Type Record Code

Table 2.83. Category Review Codes

Table 2.84. Type Ship-Not-Credited (SNC) Flag

Table 2.85. Type Spares Codes

Table 2.86. Unserviceable Status Codes

Table 2.87. Urgency of Need Funding Flag

Table 2.88. Use Codes

Table 2.89. Vehicle Registration Number

Table 2.90. Vehicle Status Codes

Table 2.91. Vehicle Maintenance Work Order Numbers

Table 2.92. War Reserve Materiel (WRM) Application Code

Table 2.93. Wartime Category (WC) Code

Table 2.94. WPC Codes

Table 2.95. Error Codes and Message/Solutions

Table 2.96. Weapon Control Transaction Code

2.4. Transportation Account Code

Table 2.97. TAC Assignment Chart

2.5. Document Identifier Code (DIC) And Transaction Identification Code (TRIC) ... 110

Table 2.98. DIC/TRIC Codes Chart

2.6. Document Number

Table 2.99. Document Numbers, Example One

Table 2.100. Document Numbers, Example Two

Table 2.101. Document Numbers, Example Two

Table 2.102. Document Numbers, Example Three

Table 2.103. Document Numbers, Example Four

Table 2.104. Document Numbers, Example Five

2.7. Expendability, Recoverability, Reparability, Cost Designator (ERRCD)

Table 2.105. ERRCD Breakout

Table 2.106. EMC Codes

2.8. Materiel Category and/or Source of Supply Code

Table 2.107. Materiel Category and/or Source of Supply Code

2.9. Organization Identification Code

6 AFH23-123V1 8 AUGST 2013

Table 2.108. Organization Identification Code

Table 2.109. Identity Edits

2.10. Transaction Exception Code (TEX)

Table 2.110. Code Breakout - TEX Code Sequence

Table 2.111. Code Breakout - DIC/TRIC Sequence

2.11. Type Transaction Phrase and Code (TTPC)

Table 2.112. Type Transaction Phrase and Code (TTPC)

2.12. Acquisition Advice Code (AAC)

2.13. Budget Code

Table 2.113. Budget Codes

Table 2.114. Centrally Managed Budget Programs Codes

2.14. Custody Receipt Account Code/Shop Code

Table 2.115. Custody Receipt Account Codes

2.15. Disposal Authority Code

Table 2.116. Air Force Disposal Authority Codes

2.16. Document Identifier Code, Wholesale

Table 2.117. Document Identifier Codes

Table 2.118. Document Identifier Code--Intra-Air Force

2.17. Excess Transaction Status Code

Table 2.119. Excess Status Codes

2.18. Level Justification Code

Table 2.120. Level Justification Code (LJC)

2.19. Status/Cancellation Justification Code/Phrase

Table 2.121. Intra-Air Force Status Codes

Table 2.122. Intra-Base Status Codes

2.20. Urgency Justification Code

Table 2.123. Urgency Justification Code (UJC)

2.21. Screen Name/Number Index

Table 2.124. Screen Name/Number Index

2.22. MICAP Codes

Table 2.125. MICAP Condition Codes

Table 2.126. MICAP Hour Codes

Table 2.127. MICAP Delete (Termination) Codes

AFH23-123V1 8 AUGSUT 2013 7

Table 2.128. MICAP Advice Codes

2.23. ES-S Definitions

2.24. Classes Of Supply

Table 2.129. Classes of Supply

Chapter 3—FORMATS & STANDARDS FOR THE DOD SUPPLY CHAIN 257

3.1. Overview

3.2. DLM 4000

3.3. DLM 4000

3.4. DLM 4000

3.5. DLM 4000

3.6. DLM 4000

3.7. DoD 4100

3.8. DoD 4140

3.9. CJCSI 4110

Chapter 4—EXTERNAL MATERIEL MANAGEMENT SYSTEMS 259

4.1. Overview

4.2. Mobility Inventory Control Accountability System (MICAS)

4.3. Hazardous Materials Information Resource System (HMIRS)

Attachment 1—GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION 260

Attachment 2—UPDATED TERMS FOR AF SUPPLY CHAIN SUPPORT 274

8 AFH23-123V1 8 AUGST 2013

Chapter 1

HANDBOOK OVERVIEW

1.1. Purpose. The purpose of this handbook is to provide system interface guidance related to the execution of materiel management procedures outlined in AFMAN 23-122.

1.2. Description of Volumes. This manual is divided into the following volumes and parts:

1.2.1. AFH 23-123, Volume 1, Materiel Management Reference Information, provides ready identification and use of various codes and terms applicable to procedures covered in

AFMAN 23-122.

1.2.2. AFH 23-123, Volume 2, Integrated Logistics System – Supply (ILS-S), prescribes standardized processes for all materiel management activities operated or supported by the

Integrated Logistics System – Supply (ILS-S). It applies to all ILS-S users.

1.2.2.1. AFH 23-123, Volume 2, Part 1, ILS-S, Materiel Management Operations provides system interface guidance related to the execution of materiel management processes outlined in AFMAN 23-122.

1.2.2.2. AFH 23-123, Volume 2, Part 2, ILS-S, Standard Base Supply System Operations specifies the functional and technical processes applicable to status inquiries, notices, record maintenance and associated information within the Standard Base Supply System

(SBSS).

1.2.2.3. AFH 23-123, Volume 2, Part 3, ILS-S, Standard Base Supply System Reference specifies the functional and technical processes applicable to system operations within the SBSS.

1.2.2.4. AFH 23-123, Volume 2, Part 4, ILS-S, Ancillary Components addresses the Air

Force Supply Central Database (AFSCDB) and the Enterprise Solution-Supply (ES-S).

The AFSCDB is designed to replicate the SBSS processes without changing its business practices. This part of the handbook provides detailed information on the AFSCDB.

Additionally, an introduction to the ES-S and link to the online ES-S handbook is provided.

1.2.3. AFH 23-123, Volume 3, Air Force Equipment Management, specifies processes and information applicable in the management of organizational equipment under the Air Force

Equipment Management System (AFEMS).

1.3. Relation to other Publications. If the information in this handbook appears to conflict with other volumes, parts, or chapters of this handbook, the conflicts will be referred to the designated OPR for resolution.

1.4. Changes to this publication. Command staff offices or AF bases desiring to make recommended changes to the information contained herein will make such recommendations through their respective MAJCOM/command chain. Supplements to this publication are allowed at MAJCOM level or higher and must be routed to the OPR of this publication for coordination prior to certification and approval.

AFH23-123V1 8 AUGSUT 2013 9

Chapter 2

DATA ELEMENTS, DEFINITIONS & STANDARD SUPPLY CODES

2.1. Purpose. This chapter is designed to provide AF’s worldwide logistics customers with a practical, ready reference for all codes used in the Military Standards (MILS) systems such as accounting, reporting, requisitioning, etc. The codes contained herein are intended to standardize procedures and, unless otherwise specified, these codes will be used and apply to all applicable

AF activities.

2.2. References. The information provided in this section is intended to supplement lists and glossaries found in other AF references. For additional definitions, acronyms, and abbreviations refer to the publications listed in Attachment 1.

2.3. Data Elements and Definitions.

2.3.1. Purpose. To define data elements consisting of codes, flags, numbers, or quantities used internally or externally to the Air Force Logistics legacy systems.

2.3.1.1. Arrangement. The elements are listed alphabetically by full name. (Some entries are also listed under their acronyms, with cross-references to the full names and definitions.)

2.3.1.2. Contents. Each entry includes the title of a data element, followed by the number and type of digits it contains. The purpose of each element is explained, and cross-references to applicable chapters.

2.3.2. Glossary of Terms.

2.3.2.1. ACCOUNTING AND DISBURSING STATION NUMBER (ADSN) (6-

position N). Identifies the Accounting & Finance Office that disburses, collects, reports, or accounts for materiel transactions. These data elements are recorded on output documents and PFMR.

2.3.2.2. ACQUISITION ADVICE CODE (AAC) (1-position A). Indicates how (as distinguished from where) and under what restrictions an item will be acquired. The AAC will reflect applications of three basic methods: (1) by requisition; (2) by fabrication or assembly; (3) by local purchase. See DoD 4100.39-M, Vol 10, Table 58, for a list of these codes. Also see Para. 2.12

2.3.2.3. ACQUISITION METHOD SUFFIX CODE (AMSC) (2-position A). This code reflects the decision of the Primary Inventory Control Activity (PICA) from a planned procurement review. A combination of the two codes is required. See DoD

4100.39-M, Vol 10, Table 71, for a list of codes.

2.3.2.4. ACTION CODE--AFEMS (C001) TRANSACTION (1-position A). This is a standard code for on-line transactions in the AFEMS (C001).

Table 2.1. Action Code--AFEMS.

Code Value

A Add a record

10 AFH23-123V1 8 AUGST 2013

C Change a record

D Delete a record

2.3.2.5. ACTION CODE--FILE MAINTENANCE (1-position A). Indicates what action to take on certain SBSS input and output formats. The action codes are identified in AFH 23-123, Vol 2, Pt 2, Ch 7 with the required input for the transaction being processed.

2.3.2.6. ACTION FLAG--VENDOR/AF-OWNED CONTAINERS (1-position

A). Indicates the action the program should take on certain input formats.

Table 2.2. Action Flag.

Code Description

C Will change purchase order number/BPA call number number/return date/ optional data

F Reverse post of shipment of AF-owned container for credit. Positions 1-43 must contain valid data which can be obtained from the 1VS input in the CTH.

2.3.2.7. ACTION TAKEN CODE--MAINTENANCE (1-position A/N). Indicates maintenance actions which dictate Standard Base Supply System (SBSS) updating of repair cycle records. See Table 2.3. below.

2.3.2.8. ACTION TAKEN CODE--SUPPLY (1-position A). Indicates Logistics

Readiness Squadron (LRS)/Materiel Management Activity actions which dictate updating of repair cycle records. These codes apply to Economic Order Quantity (EOQ), supply point, War Reserve Materiel (WRM) spares, and equipment turn-ins. (See Table 2.3 below for the Action Taken Codes.)

Table 2.3. Action Taken Codes.

Code Description Remarks/Notes

A Bench checked and repaired.

B Bench checked--serviceable (no repair required).

C Bench checked--repair deferred. (This code is used for turn-in of Deficiency Report exhibits, to include latent defects.

D Bench checked--transferred to another base (for bench check, calibration, or repair).

Note 1, 2

F Repaired. (This code will not be used to code on-equipment work if another code will apply.)

G Repaired and/or replaced attaching units, seals gaskets, packing, tubing, etc.

J Calibrated--no adjustment required.

K Calibrated--adjustment required.

AFH23-123V1 8 AUGSUT 2013 11

L Adjusted.

R Unserviceable turn-in of an item from other than a maintenance activity. If the item is Not Repairable This

Station (NRTS) or condemned by maintenance, use the appropriate maintenance action taken code (1-7 or 9).

Supply Action Taken code. Not to be used for

Turn-in of a Due-In From

Maintenance (DIFM) asset.

S Serviceable turn-in of an item originally requested as an initial issue.

Supply Action Taken code. Not to be used for

Turn-in of a DIFM asset.

T Serviceable turn-in of WRM spares, Supply Point, Mobility Readiness Spares Package (MRSP), and

Mission Support Kit (MSK) assets, and other situations where demand data would not be affected.

Supply Action Taken code. Not to be used for

Turn-in of a DIFM asset.

U Serviceable turn-in of an item originally requested as a replacement issue. (Cumulative recurring demands data will be reduced by the quantity turned in.)

Supply Action Taken code. Not to be used for

Turn-in of a DIFM asset.

V Cleaned.

X Tested, inspected, serviced.

Z Painted.

1 Bench checked (NRTS)--repair not authorized.

2 Bench checked (NRTS)--lack of equipment, tools, or facilities.

3 Bench checked (NRTS)--lack of technical skills.

4 Bench checked (NRTS)--lack of parts.

5 Bench checked (NRTS)--shop backlog.

6 Bench checked (NRTS)--lack of technical data.

7 Bench checked (NRTS)--lack of resources. (The repair is authorized by the -6 maintenance T.O. but not accomplished due to the lack of authority to possess or obtain resources.)

8 Bench checked--return to depot facility by direction of system manager or item manager.

Note 3

9 Condemned.

Blank Action taken code used for turn-in of EOQ items will be blank with the following exceptions:

a. Serviceable turn-in from detail records such as

WRM will contain supply action taken code T.

b. Action taken code U will decrease the cumulative recurring demands by the quantity turned in.

12 AFH23-123V1 8 AUGST 2013

c. When the item turned in is a Deficiency Report exhibit, use supply condition code Q and action taken code C. For Deficiency Report credit policy, see the materiel deficiency procedures.

Notes:

1. Action taken code D is used to indicate an item was 1) bench checked at a forward operating base, dispersed operating base, or en route base, 2) found to be unserviceable, and 3) transferred to a main operating base or home base for repair. If a turn-in input contains a supplementary address in positions 45-50, action taken code D will cause the item to be shipped to that address. Do not use code D for turn-in of items with

Expendability/Recoverability/Repairability/Cost Designator (ERRCD) XB, and do not use it when shipping unserviceable items to Inventory Managers, special repair activities, or other official depot level repair functions.

2. Under the conditions listed below, items turned in with other action taken codes will be shipped to other Air Force bases and the code will be automatically changed to D.

a. Override record address. When the override record correlates with the shipment exception code, the item is shipped to the override record address.

b. Reparable destination address. When the reparable destination/ disposition code contains an address, the item is shipped to that address.

c. Missing address reject. When the turn-in does not direct a shipment to another Air Force base, an invalid action taken code reject will be generated.

3. Action Taken Code 8 forces the automatic shipment of items to AFMC depots. Do not use it with ERRCD XB items; do not use it for shipment to repair facilities other than AFMC; and do not use it when the Inventory Manager directs the return of an awaiting parts (AWP) asset for lack of parts.

2.3.2.9. ACTIVITY CODE (1-position A). Identifies the method that an organization uses when submitting an issue or turn-in request to the supplies and equipment manager.

This code appears in the first position of an organization document number. The activity codes are listed below:

Table 2.4. Activity Codes.

Code Description

A Special level.

B Bench stock (bench stock issues).

C Contract maintenance/in-house repair/ Unsatisfactory Report (UR) exhibits.

D Special Purpose Recoverables Authorized Maintenance (SPRAM) issues.

E Equipment manager.

AFH23-123V1 8 AUGSUT 2013 13

F Internally assigned to the local manufacturer receipts of stock funded (budget code 9) items. For transaction identification codes (TRIC) other than receipts, this code is the service code portion of the MILSTRIP document number.

Also, the organizations and/ or LRS/Materiel Management Activities use this code for miscellaneous DO NOT POST transactions. Such transactions are not processed through the SBSS but are transferred to DLADS.

J Maintenance (IMDS/CAMS- FM) issues.

K Retail outlet transactions. General outlet (BSS/TIC) uses this code for issues and turn-ins.

L Bulk issue point (Base Service Store, Individual Equipment Element, and GSA

Self-Service Store).

M Mission support kit (MSK).

P Non- Equipment Authorization Inventory Data

(EAID) Equipment. Equipment items (ERRCD NF/ND) for which authorized or in-use detail records are not maintained.

R Routine maintenance.

S Identifies a transaction related to a supply point. It is used for across-the-counter issues, for turn-ins, and for action between the supply point and the

CSB account.

U RSP.

W War Reserve Materiel consumables and spares.

X Expedite.

Y Identifies file maintenance transactions that were assigned document numbers under program control.

Z Internal transactions.

2.3.2.10. ADDRESS TYPE (1-position N). Indicates whether an "in the clear" address is to be used for mail, freight, or billing.

Table 2.5. Address Type.

Code Meaning

1 Mail address

2 Freight address

3 Bill to address

2.3.2.11. ADJUSTMENT ACTION CODE (1-position A/N). Used on Accounting and Finance inputs to specify processing actions for programs (see DFAS-DE 7077.10-

M, SBSS On-Line Users Manual). https://ceds.gunter.af.mil/Publications.aspx .

https://ceds.gunter.af.mil/Publications.aspx

14 AFH23-123V1 8 AUGST 2013

2.3.2.12. ADVICE CODE--REQUISITIONING (2-position A/N). Provides the source of supply with coded instructions that specify processing actions for programs.

The requisition transaction advice codes flow from requisition originators to initial processing points and are thereafter perpetuated into passing actions and release/receipt documents. See DLM 4000.25-1 for a list of these codes.

Table 2.6. Intra-Air Force Advice Codes.

Code Explanation

6A Request for shipment of unserviceable (reparable) materiel (fill or kill).

6B Request for shipment of TOC materiel (fill or kill).

6C If unable to ensure availability before expiration of priority or indicated delivery date, reject and furnish a source of supply from which purchase may be made from funds of requisitioner.

6D Request for incomplete materiel (fill or kill).

6E Required to replace an item lost to the equipment management reporting inventory/EAID; that is, redistribution and marketing, inventory adjustment voucher, and other relief of accountability documents.

6F Required for issue to non EAID reporting function or agency; that is, DD Form

780, Aircraft Inventory Record, CE real property training device, bench mock-up or other governmental agencies, NASA, ARMY, NAVY, etc., and contractors.

6G Required as replacement issue to support an EAID authorization.

6H Required to satisfy shortage resulting from increased EAID authorization subsequent to the last RCS: LOG-MM(M) 7328 EAID report.

6J Required to satisfy initial shortage previously reported in the EAID report.

6K Item is required for an AWP end item (fill or kill).

6L Item is required for an AWP item. Quantity not shipped will be back ordered.

6M Pick, pack, and hold materiel for port call. Use of this code is restricted to aggregation type Air Force supply directive (perpetuated only in the Inventory

Manager Stock Control and Distribution (IM SC&D) system).

6N Organic depot maintenance projected materiel requirements (use is restricted to

AFMC depot supply only.

6P Specifies “New and Unused Materiel Only” will be shipped to satisfy this specific requirement. This code will be used by AF for selected Foreign Military Sales

(FMS) case requisitions and will cause the phrase “New and Unused Materiel

Only” to be printed on the DD Form 1348-1, DoD Single Line Item Release/Receipt

Document, shipment documentation.

6Q Item requires calibration, repair, and return.

6R Complete overhaul of “ND2” item required to insure performance, safety or maximum utilization. Replacement item must be available before item can be released.

AFH23-123V1 8 AUGSUT 2013 15

6S Repair costs for “NF2” item exceed economic repair criteria. Operational requirement prevents condemnation until replacement is received.

6V Request for single vendor integrity control for a FMS requisition, procurement action required by the Item Manager (IM).

6W Specified materiel required to be delivered to FMS country by date.

6X Used to request back order of lateral requests authorized only for lateral (base to base) actions.

6Y Fill in backorder required quantity as update cumulative recurring demands (EOQ items only).

6Z Routed repair replacement requirement (fill or kill). Authorized for Air Force

Recoverable Assembly Management System

(AFRAMS) only.

61 FW2020 requisitions received will be output as “9A” controlled exceptions. Split actions are not allowed.

62 Materiel requested is for replacing installed equipment in next higher assembly.

63 The item is required to replace a time change asset that was issued to satisfy a local requirement.

64 Used on deployed Combat Supply System (CSS) requisitions submitted to the supporting base. Processed by the supporting base as a fill or pass, and released to zero balance. Generated by the CSS under program control.

65 Asset requires calibration prior to shipment calibration facility to ship directly to using activity upon completion.

66 Used only by AFMC Forward Stockage sites to indicate manual materiel release transactions.

67 Not used.

68 Not used.

69 Not used.

2.3.2.13. ADVICE CODE--DIFM (1-position A/N). Indicates either awaiting parts

(AWP) dispositions or requests for AWP disposition action.

2.3.2.14. AFEMS REQUEST NUMBER (11-position N). Control number assigned for an action into the AFEMS (C001) which consists of three parts. The first part of the

AFEMS request number denotes the type of user responsible for initiating an allowance change request. Valid values are as follows:

Table 2.7. AFEMS Request Number.

Code Value

1 EQUIPMENT CUSTODIAN (USER)

2 EAE

3 Command Equipment Management

16 AFH23-123V1 8 AUGST 2013

Office (CEMO)

4 ALLOWANCE MANAGER

5 AFMC

6 HQ USAF

2.3.2.14.1. The second part of the AFEMS request number is a 5-position date

(YYDDD), showing when the change request was initially entered into the AFEMS

(C001). The third part of the AFEMS request number is a 5-position sequence number.

2.3.2.15. AFTO FORM 95 CODE (1-position A). Used to prevent LRS/Materiel

Management Activities from shipping assets to repair activities unless historical records/time change data accompanies the assets.

Table 2.8. AFTO Form 95 Code.

Code Definition

X Life Limited Data Required

Y AFTO Form 95 Required

Z AFTO Form 95/Life Limited Data Required

2.3.2.16. AGILE LOGISTICS/TWO-LEVEL MAINTENANCE FLAG (1-position

A). To provide rules and metrics used for Agile Logistics (AL) and Two-Level

Maintenance (2LM) requisition processing.

Table 2.9. AL/2LM Flag Identification.

AL/2LM Flag Req

Pri

Retro -Grade

Pri

PC Required

Delivery

Date

(RDD)

Type

Account

A - AL w/Cargo Movement processing

06 03 879 777 FB

B - AL w/DSE processing* 06 03 879 777 FY

C - 2LM w/Cargo Movement processing

06 03 858 777 FB

D - 2LM w/DSE processing* 06 03 858 777 FY

Note: (*)Decentralized Support Element (DSE) processing applies to AL/2LM reparable shipments when base transportation channels are not used.

2.3.2.17. ALLOWANCE CHANGE DESCRIPTION (79-position A/N). Describes a change to an allowance standard updated in the AFEMS (C001). This description appears on an email allowance change notice.

AFH23-123V1 8 AUGSUT 2013 17

2.3.2.18. ALLOWANCE IDENTIFIER (7-position A/N). Identifies the specific allowance basis of issue from which the authorization was derived. This element is made up of the allowance source code and the allowance identifier suffix.

2.3.2.19. ALLOWANCE IDENTIFIER SUFFIX (4-position A/N). Identifies a mission application and mission exception within an allowance standard when used with the mission application (4A). The suffix for miscellaneous allowances (041, 048, 063, etc.) and special allowances (rentals, local manufacture) is structured.

2.3.2.20. ALLOWANCE MAINTENANCE LEVEL (1-position N). Identifies individual allowances that may be used only by organizations performing that level of maintenance.

Table 2.10. Allowance Maintenance Level.

Code Value

1 Organizational level

2 Intermediate level

3 Depot level

4 Organizational and intermediate level

2.3.2.21. ALLOWANCE MAINTENANCE TYPE (1-position A). Indicates whether the allowance standard is for a combat or non-combat oriented maintenance organization.

These codes are:

Table 2.11. Allowance Maintenance Type.

Code Value

C Combat

N Non-combat

2.3.2.22. ALLOWANCE MAJCOM (3-position A/N). Identifies allowance standards that may be used only by organizations assigned to that MAJCOM.

2.3.2.23. ALLOWANCE MOBILITY TYPE INDICATOR (3-position A). Identifies the mobility concept for a specific allowance.

Table 2.12. Allowance Mobility Type Indicator.

Code Value

DEP Dependent mobility mission

IND Independent mobility mission

2.3.2.24. ALLOWANCE UNIT KIND CODE (3-position A/N). Identifies individual allowances that may be used only by organizations with an equal unit kind code.

2.3.2.25. ALLOWANCE UNIT TYPE CODE (5-position A/N). Identifies individual allowances that may be used only by organizations that are tasked to the specified unit type code.

18 AFH23-123V1 8 AUGST 2013

2.3.2.26. ALLOWANCE SOURCE CODE (ASC) (3-position N). Identifies the appropriate allowance standard from which the authorization was derived, or miscellaneous sources (041, 055, etc.) on which the authorization is based.

2.3.2.27. ALTERNATE STORAGE LOCATION CODE (3-position A/N). Identifies the base at which WRM equipment is stored when that location is not the reporting base or the base of planned use. These codes and their definitions can be retrieved from the

AFEMS (C001) using the WRM base code list (OWBL) on-line query (classified users only). The WRM Monitor or the EAE can obtain a listing through their parent major command CEMO.

2.3.2.28. ALTERNATIVE FUEL CODE (1-position A/N). Identifies type fuel used in vehicle. Complies with Department of Energy Policy Act 1992 to reduce dependence on foreign fuel and Clean Air Act. See Table 2.13.

Table 2.13. AFVSPO Fuel Codes And Comments.

New

Fuel

Code

AFVSPO’S

Fuel Description

Source

AFVSPO’s Comments

Old

Fuel

Code

FLEX-FUEL = Passenger cars designed to run on blends of unleaded gasoline and either ethanol or methanol

1 A Ethanol (15% G / 85% E)

‘Flex-Fuel’

OEM (Also known as ethyl alcohol, grain alcohol) can be produced chemically from ethylene or biologically from the fermentation of various sugars from carbohydrates found in agricultural crops & cellulosic residues from crops or wood.

A

2 M Methanol (15% G / 85%

M)’Flex-Fuel’

OEM (Also known as methyl alcohol< wood alcohol) A liquid fuel formed by catalytically combining

CO with hydrogen in a 1:2 ratio under high temperature and pressure.

M

BI-FUEL = a vehicle with two separate fuel systems designed to run on either an alternative fuel or conventional gasoline, using only one fuel at a time

BI-FUEL systems are usually used in passenger cars or trucks.

AFH23-123V1 8 AUGSUT 2013 19

3 B Gasoline or CNG (Bi-Fuel) OEM Burns either gasoline or CNG B

4 F Gasoline or CNG (Bi-Fuel) CONV Burns either gasoline or CNG F

5 Q Gasoline or Propane (Bi-

Fuel)

OEM Burns either gasoline or propane Q

6 R Gasoline or Propane (Bi-

Fuel)

CONV Converted to burn either gasoline or propane

None

7 H Gasoline or LNG (Bi-Fuel) CONV LNG on board storage (CNG fuel) H

8 G Gasoline OEM Designed for unleaded gasoline G

9 C Compressed Natural Gas

(Dedicated)

OEM Designed for CNG C

10 D Diesel Fuel OEM Designed for Diesel Fuel D

‘REPOWER’=replacement of conventional diesel fueled engine with dedicated CNG engine.

11 U CNG - dedicated Diesel

‘REPOWER’

CONV Modified to burn only CNG ‘ None

DUAL-FUEL - a vehicle capable of operating on a combination of alternative fuel, such as CNG or LPG, and a conventional fuel, such as gasoline or diesel.

A vehicle has two separate fuel tanks from which both fuels are injected into the combustion chamber simultaneously.

A dual-fuel system is used in heavy-duty or diesel engines.

12 S Diesel and CNG (Dual

Fuel)

CONV Converted to burn Diesel and

CNG

None

13 W Diesel and Propane (Dual-

Fuel)

CONV Converted to burn diesel and propane

None

BIO-DIESEL-a biodegradable transportation fuel for use in diesel engines that is produced through transesterification of organically derived oils or

Biodiesel is used as a component of diesel fuel. In the future it may be used as a replacement for diesel.

20 AFH23-123V1 8 AUGST 2013

fats

14 Z BIO Diesel ( 80%> Diesel) OEM Designed for 80% or more bio-diesel

None

15 E BIO Diesel 100% (NEAT) OEM Designed for 100% Bio-Diesel

(NEAT)

None

16 J JP-8 Aviation Fuel Single battlefield fuel J

17 L Diesel and Liquefied

Natural Gas

OEM Diesel > 50 gal CNG on board storage

L

18 P Liquefied Petroleum Gas OEM Designed for dedicated LPG P

19 N No Fuel OEM Towed Vehicles and Equipment

Items

N

ELECTRIC VEHICLE = A

vehicle powered by electricity, generally provided by storage batteries but also provided by photovoltaic cells or a fuel cell.

20 V Electric OEM Battery Powered (EVs) V

Hybrid Electric Vehicle

(HEV) = a vehicle that is powered by two or more energy sources, one of which is electricity. HEVs combine the engine and fuel tank of a conventional vehicle with the battery and electric motor of an electric vehicle in a single drive rain.

21 T Electric and Diesel OEM Hybrid - Electric T

22 X Electric and Gasoline OEM Hybrid Electric Vehicle X

23 Y Electric and CNG OEM Hybrid Electric Vehicle Y

FUEL-CELL: an electrochemical engine (no moving parts) that converts the chemical energy of a fuel such as hydrogen, and an oxidant, such as oxygen, directly to electricity. The

AFH23-123V1 8 AUGSUT 2013 21

principal components of a fuel cell are catalytically activated electrodes for the fuel (anode) and the oxidant (cathode) and an electrolyte to conduct ions between the two electrodes.

24 6 Hydrogen Fuel Cell OEM To include (1) Phosphoric Acid,

(2) Proton Exchange Membrane cell, (3) Solid Oxcide, (4) Molten

Carbonate, Fuel Cells

25 8 Miscellaneous (Any Other) 8

26 9 Fossil Fuels OEM WR-ALC Use Only 9

The following codes are available for future use -

(Note: Try not to use I-O-

0-1)

27 I

28 K

29 O

30 1

31 2

The following codes are available for future use -

(Note: Try not to use I-O-

0-1)

32 3

33 4

34 5

35 7

36 0

2.3.2.29. APPLICATION CODE (2-position A/N/Blank). Identifies items relative to a specific system, subsystem, or end item. These codes are assigned locally, except for those appearing in the FK account. These codes are listed below:

22 AFH23-123V1 8 AUGST 2013

Table 2.14. Application Code.

Code Description

AO Packaged aviation oil products (alpha) only.

HF Utility/heating, fuel item records.

N(X) Reserved for future use.

R(X) Reserved for future use.

DT C-17 Weapon System - Limited Restrictions (Note)

11 C-5 Weapon System - Limited Restrictions (Note)

Notes:

1. The AFMC SCM-R Records Maintenance Activity is primarily responsible for processing all required actions for managing these codes for supported LRS/Materiel Management

Activities identifying enterprise weapon system support. AFMC

SCM-Records Maintenance Activity supported activities will process required inputs for all local stock number items.

2. Do not use Application code AO. This code applies to

Packaged Aviation products which are no longer maintained in the SBSS, although the supply logic will still update the EEIC to 602 when AO is used."

2.3.2.30. APPROPRIATION FUND CODE (2-position N). Identifies which appropriation should be charged or credited for issue/turn-in of materiel. Reference http://www.dfas.mil/contractorsvendors/fundcodes.html for additional information.

2.3.2.31. APPROVAL ACTIVITY (1-position A/N). Identifies the appropriate level for an individual allowance.

Table 2.15. Approval Activity.

Code Value

A HQ USAF

B HQ AFMC

C MAJCOM

D Allowance Manager/Item Manager

E Base Level

2.3.2.32. APPROVED SIGNATURE CODE (1-position A/N). See CERTIFYING

SIGNATURE CODE.

2.3.2.33. AREA CODE (1-position N). Assigned to each stock record account number within AFEMS (C001) for use during redistribution of assets.

Table 2.16. Area Code.

Code Value http://www.dfas.mil/contractorsvendors/fundcodes.html

AFH23-123V1 8 AUGSUT 2013 23

1 All bases in North, Central, and

South America

2 All bases in European theater of operations (other than Germany)

3 All bases within Germany.

4 All bases in Asian theater of operations

2.3.2.34. ASSET STATUS REPORT CODE (1-position A/N). Identifies in the Asset

Status Reporting Request the type of reporting required and indicates whether a request is for commencement, change, or termination of reporting. Each new code will update the reporting requirement. Identifies in asset status reports the type of reporting being furnished. See DLM 4000.25-2 for a list of these codes.

2.3.2.35. ATTACHMENT INDICATOR (1-position A). Used on electronic AF Form

601, Equipment Action Request, on AFEMS terminal. Indicates that the allowance change request has one or more attachments. May also have T/O data, manning documents, etc. This information will help to evaluate an allowance change request.

Valid values are as follows:

2.3.2.35.1. Y = YES

2.3.2.35.2. Blank = NO

2.3.2.36. AUTHORITY FOR ISSUE FLAG (1-position A). Indicates under what authority an item can be issued.

Table 2.17. Authority for Issue Flag and Descriptions.

AI Flag Description

A Individual Equipment

B Real Property Installed Equipment (RPIE)

C Reimbursement Issues to Non-Appropriated Fund Activities

D Assembly/Disassembly (Bench Sets, Parachutes, etc.)

E Reserved by AFMC SCM-R Information Technology Activity

F Medical Organization Issues

G Air Drop

H Test Projects/Research and Development Project Expenditures

I End-Item Components

J Commissary Store Equipment

K Printing Plant

L Laundry Equipment

M Tools Authorized in Tool Kits/Shadow Boards

N Reimbursable Issues to DMA Units

O Issue of Replacement Items to General Officers

P Reimbursable Issues to DLADS

Q Reimbursable Issues to DIS

24 AFH23-123V1 8 AUGST 2013

R HQ USAF/MAJCOM Directed Projects

S Reimbursable Issue to Agencies/Contractors Not Assigned Another Authority for Issue Code

T-Y Reserved by AFMC SCM-R Information Technology Activity

Z Equipment Management Code (EMC) 1 Items

2.3.2.37. AUTHORIZED PERCENT VARIANCE CODE (1-position A). A

percentage used on Local Procurement Status transactions to indicate the variation in quantity authorized by the contract. This code is stored on the status detail. The percent variance is shown as an alpha character: A = 10%; B = 1%; C = 2%; D = 3%; E = 4%; F

= 5%; G = 6%; H = 7%; I = 8%; J = 9%.

2.3.2.38. AUTHORIZED QUANTITY (5-position N). Designates the maximum quantity authorized for a particular activity. It is used on the authorized/in-use, MRSP/MSK, WRM spares, and supply point detail records Note: This field is used only on authorized detail records. On substitute detail records, leave it blank.

2.3.2.39. AUTOMATIC DATA PROCESSING EQUIPMENT (ADPE) CODE (1-

position A/N). Identifies ADPE equipment being transferred to DLA Disposition

Services (DLADS) See DoD 4100.39-M, Vol 10, Table 159, for a list of these codes.

Also, see Reference; DoD 4100.39-M, Vol 10, Table 161 for a list of ADPE identification codes.

2.3.2.40. BACKORDER (DUE-OUT) CAUSE CODE. Backorder (due-out) cause codes identify the stock position in the retail supply system at the time a customer backorder is established. The due-out cause code is also used to isolate causes for backorders, and what action(s) is needed to prevent recurrence of the problem.

Table 2.18. Non-Stocked Item Due-Out Cause Codes.

Cause Code Explanation

A No stock level established – First time recurring demand. No previous demand or reparable generation before this request. This code is assigned to change/transfer/or stop MICAP report (B9(*)) transactions by the retail supply system when the type account code is E (equipment) or K (munitions).

B No stock level established - Past recurring demand or reparable generation experience but Air Force stockage policy precluded establishment of a demand-based stock level.

C Air Force stockage policy permits a demand-based stock level, but an external decision by HQ AFMC has determined that stocking the item at the base should be restricted. This Cause Code is also assigned when Air Force stockage policy permits a demand-based stock level for the item, but only non-recurring demands have occurred on the NSN.

D Base decision not to stock the item. A demand-based stock level exists, but the base has taken action not to stock the item such as assigning a maximum level of zero.

AFH23-123V1 8 AUGSUT 2013 25

Table 2.19. Stocked Item Due-Out Cause Codes.

Cause Code Explanation

F Full base stock - Depth of stock insufficient to meet MICAP/due-out requirement.

G Full base stock - Quantity necessary for requirement is in AWP status.

The number of recoverable items in need of repair is equal to or greater than the authorized stock level. Identifies repair part shortages. Assumes if repair parts had been available, a serviceable asset would have been available.

H Less than full base stock - Stock replenishment requisition exceeds priority group UMMIPS standards. Focus attention on source of supply processing of stock replenishment requisitions

J Less than full base stock - Stock replenishment requisition does not exceed priority group UMMIPS standards. Additional follow-up or upgrade action may be required.

K Less than full base stock - No stock replenishment due-in established.

Take action to determine the reason.

R Full base stock – Assets cannot be used to satisfy this requirement because they are deployed, inaccessible (off-base supply point), or unavailable.

S Less than full base stock. Stock replenishment requisition exceeds

UMMIPS time standards by priority group and AWP assets are on order at time of MICAP.

T Less than full base stock. Stock replenishment requisition does not exceed

UMMIPS time standards by priority group and AWP assets are on order at time of MICAP.

X Less than full base stock. No due-in established and AWP assets are on hand at time of MICAP.

26 AFH23-123V1 8 AUGST 2013

Table 2.20. Special Purpose Due-Out Cause Codes.

2.3.2.41. BASE CLOSURE/PHASEDOWN FLAG (1-position binary). Identifies items in the base closure or phasedown program. This flag appears on the item record data control field. The field will contain either a zero, indicating the base closure flag is off, or a one, indicating the base closure flag is in effect.

2.3.2.42. BASE INITIATED CANCELLATIONS (5-position N). Represents the requisitions that have been canceled by the requisitioner. The canceled requisitions are listed by priority group. Such data are accumulated for one year on the routing identifier record.

2.3.2.43. BASE OF PLANNED USE (3-position A/N). Identifies the exact base on which WRM is to be used when the base of planned use is not the reporting base. These codes and their definitions can be retrieved using the WRM base code list (OWBL) from the AFEMS (C001) on-line query (classified users only). The WRM monitor or the operations support branch can obtain this listing through their parent major command

CEMO, for a description of these codes as used for FCI input.)

2.3.2.44. BASE STOCK LEVELS. Items are generally classified as stocked and non-stocked. Stocked items are normally assigned demand-based stock levels that contain either full or less than full base stock on hand. The retail supply system makes this determination by comparing the serviceable property on hand to the demand-based stock level quantity. If the quantity on hand is less than the demand-based stock level quantity, the item is considered to be at less than full base stock. See Stocked Item – Full Base

Stock and Stocked Item - Less than Full Base Stock.

2.3.2.45. BASIS OF ISSUE (BOI) INDICATOR (1-position A/N). The basis of issue indicator identifies whether the basis of issue for calculation of the quantity allowed by various means within the AFEMS (C001). Valid values are as follows:

2.3.2.45.1. C - Calculate

2.3.2.45.2. F – Fixed

2.3.2.45.3. N - Narrative

Cause Code Explanation

Y Data not available on manually prepared MICAP Start report (B9M) transactions due to the retail supply system being inoperative for unscheduled maintenance.

Z System/Commodity received without MICAP item (initial shortage).

Cause code Z identifies MICAP incidents due to a lack of initial stockage at the base. This code alerts management to the problem and identifies the items involved. Note: Cause code Z qualifies for one of the other cause codes, but the items involved require special management attention.

1-6 Command unique.

Note: Cause codes E, I, L-Q, U-W are not used.

AFH23-123V1 8 AUGSUT 2013 27

2.3.2.45.4. R - Range

2.3.2.45.5. S – Sets

2.3.2.45.6. V - Variance

2.3.2.46. BASIS OF RELATIONSHIP CODE (2-position N). Identifies the source from which the relationships within this Interchangeable and Substitute Group (ISG) were obtained or determined. The sources for these codes are listed below:

Table 2.21. Basis of Relationship Code.

Code Source

01 From comparison of T.O. data

02 Physical installation and test

03 Physical comparison

04 Part number and manufacturer

05 Other

2.3.2.47. BEGINNING ITEM CONTROL NUMBER (4-position N). Identifies the beginning item number to be assigned when details from one account are being merged with another account. This code is entered if the organization and custody receipt account codes are input for program selection purposes.

2.3.2.48. BENCH STOCK BACK ORDER RATE (6-position N). Indicates the percentage derived by dividing the bench stock delayed due-outs into the line items authorized bench stock. Definition and use on the Organization Effectiveness Report

(M24), for the format of the Monthly Base Supply Management Report (M32). This rate is determined and shown on both the M24 and the M32 as discussed below:

2.3.2.48.1. Due-Out More Than 14 Days. Line items due-out delayed (that is, due-out which is greater than 14 days and which applies only to on-base organizations) should be divided by line items authorized bench stock.

2.3.2.48.2. Due-Out More Than 29 Days. Line items bench stock due-out delayed

(that is, due-out which is greater than 29 days and which applies only to off-base organizations) should be divided by line items authorized bench stock.

2.3.2.49. BENCH STOCK FLAG (1-position A/N). Indicates on the item record that a bench stock detail exists. This flag will contain either a zero, indicating that no details exist, or a one, indicating that bench stock details exist.

2.3.2.50. BLANKET PURCHASE AGREEMENT (BPA) CALL NUMBER (3-

position N). Identifies calls made against established blanket purchase agreements.

These codes, 001-999, are assigned by procurement.

2.3.2.51. BULK ISSUE ACCOUNTING INDICATOR (1-position A). Indicates that retail outlets are operating using the bulk issue concept. This flag can be input only through the RPS/main system, the Records Maintenance terminal, or the satellite terminal functions. This flag appears as a "B" alongside organization code 001 and 041-069. See

Organization Codes for load, change, or deleting of this flag.

28 AFH23-123V1 8 AUGST 2013

2.3.2.52. BUDGET CODE (1-position A/N or Special Character). Determines whether items are centrally procured, investment, or Supply Management Activity Group

( SMAG). In SBSS a FIL input will load this code to the item record, while FIC will change or delete it. For a list of these codes refer to DoD 4100.39-M, Vol 10, Table 67.

See Para. 2.13

2.3.2.53. BUSINESS OVERHEAD COSTS AT LAC. Downward-directed aggregate expenses that will be prorated by the inventory control point for standard sales (includes expenses for Defense Information Systems Agency (DISA), Defense Finance and

Accounting Service (DFAS), Defense Logistics Agency Transaction Services (DLATS), DLADS, DLIS, JLSC, Accumulated Operating Results (AOR), and loss and obsolescence).

2.3.2.54. BUSINESS OVERHEAD COSTS AT LRC. Downward-directed aggregate expenses that will be prorated by the inventory control point for exchange sales (includes expenses for DISA, DFAS, DLATS, DLADS, DLIS, JLSC, AOR, and loss and obsolescence).

2.3.2.55. CAUSE CODE. See Backorder (Due-Out) Cause Code.

2.3.2.56. CERTIFYING/APPROVED SIGNATURE CODE (1-position

A/N). Determines the sequence for printing the Consolidated Inventory Adjustment

Document Register according to levels of certification and approval. See AFH 23-123, Vol 2, Pt 3 on Inventory Adjustment Basic Records for application.

2.3.2.57. COMBAT SUPPLIES MANAGEMENT SYSTEM (CSMS) REPORT

FLAG (1-position A). This flag will contain either a Y or M which indicates the item record is CSMS reportable or an N which indicates it is not CSMS reportable.