Postprocessing Order 
Business Object that
maps an automatically generated order for checking and processing events in the Postprocessing Office that occur in business processes such as mass runs.
The data required for creating a postprocessing order is transferred from the business process to Postprocessing Office with an interface
In Postprocessing Desktop, you can process postprocessing orders manually and complete them, or you can complete and delete them using reports.
You can call up the following transactions in dialog mode:
Transaction Code |
Short Description |
/SAPPO/PPO2 |
|
/SAPPO/PPO3 |
|
/SAPPO/WL_CHANGE |
|
/SAPPO/WL_DISPLAY |
|
/SAPPO/CLOSE_ORDERS |
Completing Postprocessing Orders* |
/SAPPO/DELETE_ORDERS |
Deleting Postprocessing Orders* |
/SAPPO/RESUBMIT |
Restarting Postprocessing Orders* |
*To call up the documentation for these reports, choose
(Program Documentation) in the application toolbar on the initial screen for reports.
Note
You may be provided with specific transactions in the relevant application menus for the implementations of the Postprocessing Office (such as Account Management (FS-AM)) delivered by SAP.
Business Application Programming Interface (BAPI)
Use the BAPI Explorer to call up the following methods:
Method |
Function Module |
Short Description |
PostprocessingOrder.Close |
/SAPPO/BAPI_ORDER_CLOSE |
Close postprocessing orders that were opened for processing |
PostprocessingOrder.Create |
/SAPPO/BAPI_ORDER_CREATE |
Create postprocessing order |
PostprocessingOrder.GetDetail |
/SAPPO/BAPI_ORDER_GET_DETAIL |
Read postprocessing order |
PostprocessingOrder.GetDetails |
/SAPPO/BAPI_ORDER_GET_DETAILS |
Read postprocessing orders |
PostprocessingOrder.GetList |
/SAPPO/BAPI_ORDER_GET_LIST |
Read list of postprocessing orders |
PostprocessingOrder.MassChange |
/SAPPO/BAPI_ORDER_CHANGE |
Mass change of postprocessing orders |
PostprocessingOrder.Open |
/SAPPO/BAPI_ORDER_OPEN |
Open postprocessing orders for processing |
PostprocessingOrder.Refresh |
/SAPPO/BAPI_ORDER_REFRESH |
Update global memory |
PostprocessingOrder.Save |
/SAPPO/BAPI_ORDER_SAVE |
Save postprocessing orders |
PostprocessingOrder.Set |
/SAPPO/BAPI_ORDER_SET |
Change open postprocessing orders |
PostprocessingOrder.SetContext |
/SAPPO/BAPI_ORDER_SET_CONTEXT |
Set context data for creating a postprocessing order |
Note
You may be provided with specific BAPIs for implementations of the Postprocessing Office delivered by SAP.
You can find the Business Add-Ins (BAdIs) that are available in Customizing for Postprocessing Office under Business Add-Ins.
To use Postprocessing Office, you need to execute the Customizing activity Activate Creation of Postprocessing Orders in Customizing for Postprocessing Office under Business Processes.
All other Customizing activities for Postprocessing Office are optional.
The GUID for postprocessing orders is found on the Detail Screen of the Additional Data tab page.
Required for the unique selection of postprocessing orders, since all other attributes assigned to a postprocessing order in different software components may have characteristics with similar names.
When you have processed the Customizing activity Define Software Components in Customizing for Postprocessing Office under Software Components, the display and processing of postprocessing orders with the Postprocessing Desktop is done by software component. If you have not executed the Customizing activity, you can use Postprocessing Desktop across software components. However, you also have the option of restricting the selection of the postprocessing orders to certain software components on the initial screen.
For more information, see Connecting Software Components.
You can process postprocessing orders from other logical systems when you in the logical system in which you connected your software component to the Postprocessing Office. To do so, on the SAP Easy Access, specify the related logical systems under or in the relevant transaction in the application menu of the implementation.
Action during which an error occurred and that leads to the creation of a postprocessing order. A business process can be a mass run, for example. Each mass run is identified by a business process ID.
Object for which a business process could not be executed successfully, which resulted in a postprocessing order being created for Postprocessing Office.
Object that is the source of the main object. A base object does not exist for every main object.
Objects that can be called to process the event in addition to the main and base object and that are the source of a postprocessing object.
An environment object does not exist for every main object.
You can add additional environment objects to standard environment objects 1 and 2. You can use the BAdI Add Environment Objects for Detail Screen Processing for this purpose.
Type of main, base, or environment object, for example, business object type.
Key that uniquely identifies an object along with the object category, object type, and the logical system.
Currently not used on the user interface or in BAPI structures. Specifies whether this is a business object or other type of object.
The messages are stored as a copy in the structure of the postprocessing order.
Main message
Messages that were issued during the runtime of the business process (for example, the mass run).
Caution
Technical errors are not entered in postprocessing orders. Therefore, controlling job control is essential.
A postprocessing order can have the status New, In Process, or Completed.
Processing note that you can create for a postprocessing order.
Action that you can execute for the main, base, or environment object.
You define the priority in the Customizing for Postprocessing Office under . If you do not execute this Customizing activity, the average priority 5 is assigned to all postprocessing orders.
You can define up to eight separate filter attributes or selection criteria in Customizing for Postprocessing Office under .
You use the Postprocessing Order (/SAPPO/ORD) authorization object to check the authorization for displaying and processing postprocessing orders.
You use the Postprocessing Order Filter (/SAPPO/FLT) authorization object to check the authorization for managing filter variants.
You can also use the BAdI Authorization Check for Postprocessing Office to implement additional authorization checks.
During the Execute Standing Orders mass run in Account Management (FS-AM), the system determines the valid working day rule based on your settings in Customizing. If you have not defined a working day rule for all relevant bank posting areas, the mass run issues a corresponding error message and a postprocessing order is created.
During the Activate PLM Documents mass run in Posting Lock Management (FS-AM-PLM), the system determines the new status for the PLM documents based on your settings in Customizing If you have not defined an automatic status transfer for the initial status, the mass run issues a corresponding error message and a postprocessing order is created.
If you are already processing in dialog mode, an object that is to be processed in a mass run, a postprocessing order is also created.