CVI: Settings for Postprocessing Office

During error processing, the Postprocessing Office (PPO) replaces the application log. Use of the PPO is optional, which means that you have to explicitly activate the PPO.

Caution Caution

If you have not activated the PPO, errors that occur during the synchronization process may cause a short dump.

End of the caution.

Procedure

In SAP ERP, make the following settings. Customizing for the PPO refers to a software component and to certain business processes (this term has a special meaning in the PPO). You can monitor postprocessing orders using transaction MDS_PPO2.

Configure the internal PPO software component AP-MD (Application Platform Master Data). To do this, use transaction SM30, view /SAPPO/VS_CMPNT.

The PPO needs this internal component to be able to distinguish postprocessing orders created by master data synchronization from postprocessing orders belonging to other projects. Moreover, all PPO Customizing settings are specific to each component.

Software Component	Change	Description	Title	Standard Display Mode for Order Assignment	Standard Editing Mode for Order Assignment
`AP-MD`	`MDS_PPO2`	Application Platform Master Data	Master Data Synchronization	All Orders	All Orders

For the software component AP-MD, define the PPO business processes that you want to use for the initial load. To do this, use transaction SM30, view /SAPPO/VS_BPROC.

You have to define each combination of source and target object as a business process.

Component	Business Process	Process Description
`AP-MD`	`CVI_01`	Customer -> Business Partner
	`CVI_02`	Vendor -> Business Partner
	`CVI_03`	Business Partner -> Customer
	`CVI_04`	Business Partner -> Vendor

Activate the PPO business processes for the component AP-MD using transaction SM30, view /SAPPO/VA_BPROC. Enter only those business processes that you need for your application. Activate each combination of source and target object that you have defined as a business process.

Component	Business Process	Active
`AP-MD`	`CVI_01`	X
	`CVI_02`	X
	`CVI_03`	X
	`CVI_04`	X

For all object types defined for the master data synchronization (in the controller Customizing view MDSV_CTRL_OBJ), configure a PPO object type for the component AP-MD. To do this, use transaction SM30, view /SAPPO/VS_OBJECT. If a corresponding BOR object already exists, use the technical key of the BOR object.

Object Type	Internal –> External	Entry	Description
`BUS1006`	`MDS_PPO_BP_GET_DESCR`	`MDS_PPO_BP_GET_OBJKEY`	Business Partner
`KNA1`	`MDS_PPO_CUSTOMER_GET_DESCR`	`MDS_PPO_CUSTOMER_GET_OBJKEY`	Customer
`LFA1`	`MDS_PPO_VENDOR_GET_DESCR`	`MDS_PPO_VENDOR_GET_OBJKEY`	Vendor
`PRODILVND`	`MDS_PPO_PRODILVND_GET_DESCR`	`MDS_PPO_PRODILVND_GET_OBJKEY`	Interlinkage Vendor

Internal –> External
This column displays the name of the function module used to convert the internal format of an object key (such as a GUID) into an external format to be displayed on the PPO screen. If no conversion is necessary, these function modules do not contain any coding.
Entry
On the selection screen of the PPO transaction Display Postprocessing Order, you can use the IDs of the objects contained in the orders to select postprocessing orders. If you want to support the user with a search help function, you can program a special function module to provide this. You enter the technical name of this function module in the Entry column.

Define which object types are permitted for which PPO business process. To do this, call transaction SM30, view /SAPPO/VSVALIDOT, and enter all the relevant object types for each PPO business process. For the initial load, define the source object type as the main object and the target object as the base object.

Software Component	Business Process	Object Role	Object Category	Object Type
`AP-MD`	`CVI_01`	Main Object	Business Object	`KNA1`
	`CVI_01`	Base Object	Business Object	`BUS1006`
	`CVI_02`	Main Object	Business Object	`LFA1`
	`CVI_02`	Base Object	Business Object	`BUS1006`
	`CVI_03`	Main Object	Business Object	`BUS1006`
	`CVI_03`	Base Object	Business Object	`KNA1`
	`CVI_04`	Main Object	Business Object	`BUS1006`
	`CVI_04`	Base Object	Business Object	`LFA1`

Define the processing methods that are available for each object type. To do this, use transaction SM30, view /SAPPO/VS_OBJBOR. These processing methods can be either a method of the corresponding BOR object or a self-programmed function module. If the latter is the case, enter the technical name of the corresponding function module.

Object Type	Processing Methods	Active	Position	Function	Object Category *)	BOR Method	Description
`BUS1006`	EDIT	X	2	-	1	EDIT	Change
`BUS1006`	DISPLAY	X	1	-	1	DISPLAY	Display
`KNA1`	DISPLAY	X	1	-	1	DISPLAY	Display
`KNA1`	EDIT	X	2	-	1	EDIT	Change
`LFA1`	DISPLAY	X	1	-	1	DISPLAY	Display
`LFA1`	EDIT	X	2	-	1	EDIT	Change

*) 1 = Business Object; 0 = blank

Define the layout of the postprocessing orders.

Call transaction SM30, view /SAPPO/VSSCRN_HD, and define the layout of tab pages in the order area.

Reference	Sequence	PAI	PBO	Refresh	Program	Screen	Title
STD1	1		`MDS_PPO_ORDER_SCR_ISDAT`	`MDS_PPO_ORDER_SCR_REFRESH`	`SAPLMDS_PPO_ORDER`	402	Order Data
STD2	2	`MDS_PPO_ORDER_SCR_FCODE`	`MDS_PPO_ORDER_SCR_ISDAT`	`MDS_PPO_ORDER_SCR_REFRESH`	`SAPLMDS_PPO_ORDER`	403	Administrative Data

PAI: Function modules that can be used to react to user actions.
PBO: Function modules that are used to read data before the order data is displayed.
Refresh: Function modules used to update data.

Call transaction SM30, view /SAPPO/VSSCRN_AS, and define the layout of tab pages in the object area.

Object Type	Business Process	Object Role *	PAI	PBO	Refresh	Program	Screen
`BUS1006`	`CVI_01`	2	`MDS_PPO_BP_FCODE`	`MDS_PPO_BP_ISDAT`	`MDS_PPO_BP_REFRESH`	`SAPLMDS_PPO_BP`	0200
`BUS1006`	`CVI_02`	2	`MDS_PPO_BP_FCODE`	`MDS_PPO_BP_ISDAT`	`MDS_PPO_BP_REFRESH`	`SAPLMDS_PPO_BP`	0200
`BUS1006`	`CVI_03`	1	`MDS_PPO_BP_FCODE`	`MDS_PPO_BP_ISDAT`	`MDS_PPO_BP_REFRESH`	`SAPLMDS_PPO_BP`	0100
`BUS1006`	`CVI_04`	1	`MDS_PPO_BP_FCODE`	`MDS_PPO_BP_ISDAT`	`MDS_PPO_BP_REFRESH`	`SAPLMDS_PPO_BP`	0100
`KNA1`	`CVI_01`	1	`MDS_PPO_CUS_FCODE`	`MDS_PPO_CUS_ISDAT`	`MDS_PPO_CUS_REFRESH`	`SAPLMDS_PPO_CUSTOMER`	0100
`KNA1`	`CVI_03`	2	`MDS_PPO_CUS_FCODE`	`MDS_PPO_CUS_ISDAT`	`MDS_PPO_CUS_REFRESH`	`SAPLMDS_PPO_CUSTOMER`	0200
`LFA1`	`CVI_02`	1	`MDS_PPO_VENDOR_FCODE`	`MDS_PPO_VENDOR_ISDAT`	`MDS_PPO_VENDOR_REFRESH`	`SAPLMDS_PPO_VENDOR`	0100
`LFA1`	`CVI_04`	2	`MDS_PPO_VENDOR_FCODE`	`MDS_PPO_VENDOR_ISDAT`	`MDS_PPO_VENDOR_REFRESH`	`SAPLMDS_PPO_VENDOR`	0200

* 1= Main Object; 2= Base Object

** Hide the key

PAI: Function modules that can be used to react to user actions.
PBO: Function modules that are used to read additional data for the current object (such as for display on a screen).
Program: Enter the program name of the function group of the function modules mentioned above.

Call transaction SM30, view MDSV_CTRL_OBJPPO, and activate PPO orders for platform objects online. Choose the synchronization objects that you use in your application and are flagged as platform objects in the view MDSV_CTRL_OBJ.

Synchronization Object

PPO Active

BP

X