Table 4: Reasons for rejected items (continued)
Failed Saving
Image
Magnetic MICR
Response
Missing
Cannot
Process
Printer Data
Required Item
Expected
Only One Item
of this Type
Expected
New
Transaction
Required
Jamsorts
The Jams section lists the reasons for the jams that occur.
Table 5: Reasons for jams
Duplicate Batch Detected
Too Many Consecutive
Rejects
Software Problem
Detected
138
Results when there is an error trying to add or rescan a
piece to a batch.
Results when the software does not receive a response
from the magnetic MICR when it is expecting one.
Results when there is an error in sending the audit trail
information down to the printer.
Results when an item is of the wrong priority to be scanned
in the current location within a transaction. (Structured
batches only.)
Results when only one item of the scanned item's priority is
allowed, and that required item is already present within the
batch. (Structured batches only.)
Results when a new transaction must be started in order to
add this item to the batch. (Structured batches only.)
All input pieces immediately following a reject when the job
parameter "Stop Machines for Rejects" is set to something
other than 'No' until the reject is cleared. All input pieces
immediately following a jam until the jam is cleared.
A batch could not be started because a batch
with the same name already exists.
Results when the number of consecutive rejects
is greater than the machine parameter
maximum consecutive reject count.
Results when the controller receives invalid
information from the host or there is an assert or
exception within the controller.
Falcon+ Operator Manual
OPEX Corporation