BANNER ACCOUNTS PAYABLE CHECK PRINT PROBLEMS
The check print job submission process (FZBCHKP) defaults the printer to
ACC_LAZR_2, which is the print in Accounts Payable. This program has been tested on
a HP4000 printer and may not print the checks correctly on another type or model of
NOTE: If you run the accounting process (FABCHKA) after check printing, the
checks cannot be re-run.
If the problem developed after the first check printed correctly:
You can re-run the process by exiting the job submission (GJAPCTL) screen and
returning to the FAABATC screen. Do a rollback and then a page down. The
screen will prompt for the last good check number and for a restart check number.
The “restart check number” is the number of the first check you will print.
If the problem developed before the first check was printed or the first check did not print
Contact the Computing Center. One of the Administrative Computing Team
members will have to run a SQL*Plus script to delete the check from the
temporary tables. When the team member notifies you that this is copleted, you
just start over with the FAABATC screen.
NOTE: Afer the SQL*Plus script has been run, check selection process
(FABCHKS) sometimes aborts and does not select the checks for printing. Have
the Administrative Computing Team member check the log file for FABCHKS to
make sure it has completed successfully. If it aborts, you will have to run it again.
Note for the programming staff.
NOTE: Do not run the script if the accounting process (FABCHKA) has been run.
The SQL*Plus script delete-all.sql is in the directory:
This is the script:
delete from fatckdt;
delete from fatckin;
delete from fatckno;
delete from fabchks
where fabchks_check_num > '&&last_good_check_number';
delete from fabinck
where fabinck_check_num > '&&last_good_check_number';
This script deletes data from the temporary tables created in FABCHKS and updated in
The „last_good_check_number‟ is one less than the first check number in the bad run.
For example, if the first check number in the bad run were 00000528 and it did not print,
the last_good_check_number would be 00000527.
After you run the script, accounts Payable should exit all the way to the Finance or
banner main menu, go back into AABATC, and start the process over again. In testing
this process the check selection program (FABCHKS) will frequently about. Since there
is no print for the job, you have to check the .log file to see if the program terminated
normally. Below is a copy of a .log file produced with the program aborts:
Starting FABCHKS (Release 5.1)...
Run Sequence Number: fabchks completed successfully
0 lines written to
Run Sequence number is invalid, aborting job
request id is acc_lazr_2-165 (1 file)
Note the contradiction in “fabchks completed successfully” and “Run Sequence number
is Invalid, aborting job”.
This error happens most of the time and is resolved by submitting the job again. If the
job still does not run then the delete-all.sql script should be ran.