In addition to the user-defined user exits, the generated print program contains further static user exits that you can specify in the user exit include in the configuration of an application form.
Static user exits fulfill functions that are independent of the actual data procurement and processing of the hierarchy.
Static user exits are subroutines that have no parameters. Customers can define them in the user exit include. The Print Workbench gives the name of a user exit.
At the time of activation, the Print Workbench recognizes the existence of the subroutines, creates corresponding calls from the generated print program, and performs the user exits. You can use the following static user exits:
·
FORM
CHANGE_SF_OPTIONS
This form routine is called immediately before the processor for Smart Forms
is opened. There you can modify the import parameters of the module SSF_OPEN
(if necessary) with ABAP programming:
c-sf_control_parameters_ TYPE SSFCTRLOP
c-sf_output_options TYPE SSFCOMPOP
At this point, the application data from the application form or from the form class has not been read yet.
·
FORM
CHANGE_PDF_OPTIONS
This form routine is called immediately before the processor for PDF-based
forms is opened. There you can modify the import parameter c-pdf_output_options TYPE SFPOUTPUTPARAMS of the
module FP_JOB_OPEN.
At this point, the application data from the application form or from the form class has not been read yet.
·
FORM
EXIT_BEFORE_PRINT
This form is called immediately before the call of a generated module of an
individual SAPscript form, Smart Form, or PDF-based form. At this point, the
application data from the application form or from the form class is read
completely.