Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-GBT-PPF (Application Component) Post Processing Framework⤷
SPPF_CUST (Package) PPF: Customizing
Basic Data
| Data Element | PPFDINCONSISTCU |
| Short Description | PPF: Delete Non-Referenced Customizing Entries |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PPFDBOOL | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Cust. |
| Medium | 20 | Non-Referenced Cust. |
| Long | 40 | Non-Referenced Customizing Entries |
| Heading | 40 | Non-Referenced Customizing Entries |
Documentation
Definition
Within the Post Processing Framework (PPF) exist hierarchies of Customizing objects that are maintained using transaction SPPFC. When maintaining these settings, if entries arise which no longer have references of the PPF linking to them, then these can no longer be addressed. The associated inconsistency report identifies these entries and deletes them, as long as it is not running in test mode.
Use
Call the report once all PPF Customizing activity is complete.
IMPORTANT: As a rule, all PPF clean-up reports must be called in test mode first, and their logs analyzed, before calling them actively.
Dependencies
The clean-up report works across all applications. For this reason, you must make sure prior to the active execution that the Customizing work is complete for every application that exists in the system.
To execute the clean-up report, activity "Execute" (16) of authorization object S_PPF_ADM must be assigned to your user.
Example
For scenarios that are more complex, deleting at a level that is higher up the hierarchy (for example, an action definition is hierarchically higher than an assigned processing type) can lead to persistent entries that are no longer referenced, as the dependent objects are not deleted.
History
| Last changed by/on | SAP | 20041216 |
| SAP Release Created in | 700 |
