AP - F110 - SAPFPAYM - Adobe Checks - Printing Issue

Question

We have ECC 6.0, and we recently started using Payment medium workbench to print adobe check forms.  All configuration and programming is done, except that we encounter an issue once in a while.
Using F110, we will complete a proposal, review it and then execute the payment medium run.  Out of 60 or so check runs, we will have a batch that does not print the last few checks out.
For example, in one instance, out of 100-200 checks, the last 4-6 did not print.  All tables (PAYR, etc.) and vendor were updated with a payment document and check number, and the spool does show an adobe image available for those particular items.
The most recent occurrence involved 587 checks, where the last 54 did not print.  They are visible on the spool. 
The logs of the payment run do not show any error messages or warnings.  We verified with our Basis team that there are no messages or logs associated with the actual printers, and yet, they just do not print!
I have searched notes, forums and boards trying to find anyone with a similar issue but no luck thus far.
I have created the issue in Qas as well, by using the same steps to create 588 checks via F110, but only 27 print out?  I tried the "Reprint" option on the F110 screen, and the same 27 checks print out.  (Its the first 27 of the spool that print each time.) 
Again, the spool shows all 588 checks with images and all data/tables are updated appropriately.
In OBPM4, we have the box for "Payment Document Validation" checked, and the correct printers assigned.
Does anyone have any suggestions on what might trigger this? 
Where else should we be looking to find some type of status or error message?
Would it be helpful to run through the process with some type of trace running in the background?

Answer 1

Thank you for your response.
I wondered about a printer memory issue as well...however, I am not sure how much space an adobe check might take up versus the SapScript check form we used before. 
Any suggestions on how to go about verifying this theory?  (Basis should monitor from their side when I start the print program?)  (Is there a report or status I can physically check or create from the printer itself?)