Constraints for Frontend Printing
The following constraints apply to frontend printing, due to the special way in which it works:
· You cannot perform frontend printing in the background, as there is not connection to the frontend.
· Since SAP Basis 4.5A, you can print from the update process to the frontend. To do this, the user must still be logged on when the print request is sent in the update process.
However, we recommend that you do not use frontend printing from the update process, as it is not possible to check whether multiple update work processes are attempting to perform frontend printing simultaneously. Frontend printing does not work for more than one work process.
· A free session is required for frontend printing, so it must not be the case that all sessions are occupied.
However, frontend print requests are not lost if all sessions are occupied, but are temporarily stored in the database. The printing is performed once there are sufficient sessions available on the user terminal again. The print requests are output on the current terminal even if the user is now working from a different terminal.
You can subsequently print the print requests in transaction SP01 by choosing Restart Frontend Printing in online operation without requiring an additional session.
· Up to SAP Basis 4.6A, the print formatting is performed in the dialog work process, meaning that the dialog timeout applies for formatting. However, as of SAP Basis 4.6A, the print requests are processed in the spool work process, meaning that no timeouts apply in this case.
· Frontend printing should not be used for production or mass printing.
For more information about constraints for frontend printing, see SAP Note 114426 in the SAP Service Marketplace.
See also:
Frontend Printing on Local Printers
