Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-GBT-PPF (Application Component) Post Processing Framework⤷
SPPF_CORE (Package) PPF: Central Logic
Basic Data
| Data Element | PPFDTSTAT |
| Short Description | PPF: Action Status |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PPFDTSTAT | |
| 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 | Status |
| Medium | 15 | Status |
| Long | 20 | Processing Status |
| Heading | 10 | Status |
Documentation
Definition
Use
The symbol displays the status of the action:
Yellow = Not processed (0)
Green = Successfully processed (1)
Red = Errors occurred during processing (2)
Dependencies
When using the action status as a selection option in transaction SPPFP, note the following:
If the report is scheduled in batch, actions are selected and automatically processed. If you do not restrict the status during selection, all actions are selected (not processed, successfully processed, processed with errors). For processing, a copy of the actions with errors and the actions processed successfully is made, and this copy is processed. In this way, two actions are generated for an application object, and for the second action the attributes 'changed', 'repeated' and 'manual' are set.
As a result of this copying procedure, it may happen that an action that has already been processed successfully is selected again during the next run of the report, and is copied and processed for a second time. During the run after that, two successful actions are then copied and processed again, meaning that the number of actions doubles with every run. The same is true for actions processed with errors.
Example
- Status = 0
Only unprocessed actions are selected and processed. This setting is the most appropriate for most applications if the report is scheduled repeated in batch.
- Status = 2
Execution of actions with errors is repeated. This may make sense, for example, when processing actions that could not be successfully processed due to a temporary lock problem related to the application object. It can be assumed that by the time the action is executed for the second time, the lock problem has been corrected.
This option is not appropriate as a batch variant, since the actions with errors are copied prior to processing. If the second processing also results in errors, you have then generated two actions with errors. This must be checked by a user.
- Status = space
Not appropriate if the batch option is used, since it causes the number of successful actions and actions processed with errors to be doubled. You must only use this option in dialog, for example if you want to select all actions for a particular action definition or document.
Alternatively, you can restrict the selection even further by choosing the flag for the additional option 'repeated' or 'generated manually'.
History
| Last changed by/on | SAP | 20010130 |
| SAP Release Created in |
