Controlled Exceptions

CHAPTER 9

CONTROLLED EXCEPTIONS

9.1. General.

9.1.1. This chapter describes the reasons the Item Manager Wholesale Requisition Process (IMWRP)

D035A subsystem creates controlled exceptions and what actions a D035A user may take to clear

these controlled exceptions. A controlled exception is a transaction that has been suspended for manual review and action. For each type of controlled exception, which is identified by a two-character

exception type code, an attachment is provided that lists the exception code and title (which may not

match the abbreviated title displayed on a D035A screen) and contains the following sections:

9.1.1.1. Reason for Exception. This section explains the possible reasons why the controlled

exception was created.

9.1.1.2. Transaction Types. This section lists by Document Identifier (DI) code the types of transactions that can be suspended to create the controlled exception.

9.1.1.3. Corrective Action: This section explains what corrective actions are allowed to clear the

controlled exception.

9.1.1.4. Applicable Chapters: Due to the complex nature of processing a suspended transaction, it

is recommended that the user consult the applicable chapter of AFMAN 23-110, Volume 3, Part

3 to gain a detailed understanding of how D035A processes a specific transaction before working

a controlled exception. This section lists the applicable chapters.

9.1.2. All transactions processed by D035A are first edited to ensure the field values contain valid

data. Certain data errors are automatically corrected by the system. However, other errors must be

manually corrected. When a transaction cannot be automatically corrected, it is suspended as a controlled exception. For example, if a requisition transaction is received that contains a stock number

not recognized by D035A, the transaction is suspended as a controlled exception. This requires that a

D035A user research the stock number to determine if the requisition should be rejected...