!--a11y-->
Postprocessing Order 
Business object, which represents 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 via an interface to the Postprocessing Office.
In the Postprocessing Desktop, you can process and complete postprocessing orders manually, or they can be completed and deleted by 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 |
Complete postprocessing orders |
/SAPPO/DELETE_ORDERS |
Delete postprocessing orders |
To call up the
documentation for this report, choose
Program
Documentation in the application toolbar on the initial screen of the
report.

You may be provided with specific transactions in each application menu for the implementations delivered by SAP for the Postprocessing Office, for example, Account Management (FS-AM).
Business Application Programming Interface (BAPI)
You can 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 opened postprocessing orders |
PostprocessingOrder.SetContext |
/SAPPO/BAPI_ORDER_SET_CONTEXT |
Define context data for creating a postprocessing order |

You may be provided with specific BAPIs for the implementations delivered by SAP of the Postprocessing Office.
You can find the available Business Add-Ins (BAdIs) in Customizing for the Postprocessing Office under Business Add-Ins.
To use the Postprocessing Office, you need to process the IMG activity Activate Creation of Postprocessing Orders in the Customizing for the Postprocessing Office under Postprocessing Office - Business Processes.
All other IMG activities for the Postprocessing Officeare optional.
You find the postprocessing order GUID on the Order Data II tab page on the detail screen.
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 IMG activity Define Software Components in the Customizing for the 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 processed the IMG activity, you can use the Postprocessing Desktop across software components, but also have the option of restricting the selection of the postprocessing orders to certain software components on the initial screen.
For more information, see Connection of a Software Component.
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. Specify the corresponding logical systems for this by choosing Cross-Application Components ® Postprocessing Office ® Current Settings from the SAP Easy Access screen, or in the relevant transaction in the application menu of the implementation.
Action in which an error occurred, which leads to creation of a postprocessing order. A business process can, for example, be a mass run. 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 the 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 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 the standard environment objects 1 and 2. To do so, you can use the BAdI Add Environment Objects for Detail Screen Processing.
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 another 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).

Technical errors are not created in postprocessing orders. Therefore, the control for the job control is essential.
A postprocessing order can have the status New, In Processing or Created.
Processing note that you can create for a postprocessing order.
Action that you can execute for main, base or environment object.
You define the priority in the Customizing for the Postprocessing Office under Business Processes ® Assign Business Process Priority. If you do not process this IMG activity, the average priority 5 is assigned to all postprocessing orders.
You can define up to eight separate filter attributes/selection criteria in the Customizing for the Postprocessing Office under Selection Criteria/Filter ® Define Own Filter Attributes.
The postprocessing order (/SAPPO/ORD) authorization object is used to check authorization for displaying and processing postprocessing orders.
The postprocessing order filter (/SAPPO/FLT)authorization object is used to check 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 already created.