Hierarchy

⤷

⤷

Basic Data
Data Element | PPFDINCONSISTTE |
Short Description | PPF: Clean Up Inconsistencies in Configuration |
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 | Config. |
Medium | 20 | Clean Configuration |
Long | 40 | Clean Up Configuration |
Heading | 30 | Clean Up Configuration |
Documentation
Definition
The Post Processing Framework (PPF) includes the determination technology "transportable conditions" (maintenance transaction through IMG of the application, SPPFDETCRM or SPPFCADM). Transportable conditions that can no longer be instanced are deleted by this clean-up report.
This clean-up report does not identify any inconsistencies between Customizing of the action definitions and the transportable conditions.
Use
The report must be called once all PPF Customizing and configuration activity is complete.
IMPORTANT: As a rule, you must call all PPF clean-up reports in test mode first, analyze their logs, and then call 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
History
Last changed by/on | SAP | 20041216 |
SAP Release Created in | 700 |