If you want your application to use the Post Processing Framework (PPF), you must perform a number of programming steps. The connection between your application and PPF uses classes, but your application itself does not have to be object-oriented.
For comprehensive guidelines, see SAP Note 489334.
For an example implementation, see package SPPF_DEMO.
You must also carry out application-specific Customizing. For more information, see the Implementation Guide (IMG) activities of your application.
Business Add-Ins (BAdIs)
Dynamic Printer Determination
If you do not want to define your printer in the Customizing settings, it is possible to determine a printer dynamically by implementing the BAdI PRINTER_DETERM_PPF. You may want to do this in order to determine the printer on the basis of user master data or sales organization, for example. For more information, seeDynamic Printer Determination.
If you want to implement your own specific processing, such as to create an item in a document or create a follow-on document, you can do this by implementing the BAdI EXEC_METHODCALL_PPF. For more information, seeDynamic Processing.
Schedule conditions are used withinaction determination. As an alternative to using the workflow condition editor to implement your schedule conditions, you can use the BAdI EVAL_SCHEDCOND_PPF.
Start conditions are checked before actions are executed. An action is only executed if the start condition is fulfilled. As an alternative to using theworkflow condition editor to implement your start conditions, you can use the BAdI EVAL_STARTCOND_PPF.
For more information on implementing these condition BAdIs, seeCondition Evaluation.