Hierarchy

⤷

⤷

Basic Data
Data Element | PPFDINCONSISTTECU |
Short Description | PPF: Inconsistencies Between Customizing and 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 | Cust Conf. |
Medium | 20 | Clean Cust. Config. |
Long | 40 | Clean Up Customizing Configuration |
Heading | 30 | Customizing Configuration |
Documentation
Definition
In the Post Processing Framework (PPF), the actions stored and scheduled in the various types of determination technology are represented by what are known as action templates. Action definitions with corresponding processing types must always form the basis of these templates. Inconsistencies resulting from changing the action definitions at a later time are corrected by this clean-up report.
Use
The report must be called:
- After all PPF Customizing and configuration work is complete
- When canceling the configuration of transportable conditions using exception CX_OS_OBJECT_NOT_FOUND
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 |