Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-SCM (Application Component) Schedule Manager⤷
KPEP_WORKLISTS (Package) Worklist in the Schedule Manager
Basic Data
| Data Element | KPEP_WL_OBJSTAT |
| Short Description | Processing Status of Object in Worklist |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KPEP_WL_OBJSTATUS | |
| Data Type | NUMC | Character string with only digits |
| Length | 3 | |
| Decimal Places | 0 | |
| Output Length | 3 | |
| 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
The processing status of an object indicates whether processing was successful. The worklist of the Schedule Manager shows the processing status of each processing step for each object. The processing status is set by the system when the object is processed. The status can be changed manually in the monitor of the worklist.
In addition to showing the success of processing, the processing status also shows whether further processing is allowed. This ensures that an object which was not processed because it was flagged as having errors in a given processing step cannot enter the next processing step.
Use
The worklist of the Schedule Manager uses the processing status to control whether an object is processed in the subsequent processing step. The following processing statuses are set by the system autmatically:
Automatic Processing Statuses
- Not Processed
The object was not processed.
- OK
The object was processed without errors.
- Minor Error
A warning was issued or an error occurred while the object was being processed, but the object can still be processed in the subsequent step.
- Flagged for Postprocessing
This status is set in the following situation:
The object is required to be processed in a processing step, for example because processing was forced (Processing Forced Manually). In the subsequent processing step, the object has one of the following processing statuses:
- OK
- Not Relevant
- Minor Error
- Filtered
Because the object would not normally be processed when it has one of these processing statuses, the system changes the processing status of the subsequent processing step to Flagged for Postprocessing. This ensure that an object which was processed in a given processing step is always included in the steps following that step. The processing status is changed to Flagged for Postprocessing regardless of whether the object was changed in the previous processing step.
- Error
An error occurred while the object was being processed, which prevents processing in the next step. You can eliminate the cause of the error or have the system include the object in the subsequent processing step even though you have not corrected the error (processing status Skipped Manually).
- Followup Error
An object receives the processing status Followup Error for a processing step if the object is part of a group of objects that are being processed together, and in a previous processing step one or more of the objects was flagged as having errors (processing status Error) or was not processed at all.
Objects with the processing status Followup error are not processed in the processing step in which they received this status. This ensures that the entire group of objects cannot be processed until none of the objects in the group has an error that would affect the processing of any other objects in the group.
An example for the processing status Followup Error and Hierarchy Error can be found at the end of this text.
- Hierarchy Error
An object receives this processing status for a processing step when the object is part of a group of objects to be processed together, and one or more of the objects was flagged as having errors in the current processing step (processing status Error).
Objects with the processing status Hierarchy Error are not processed in the processing step for which they receive this status. This ensures that the entire group of objects cannot be processed until none of the objects has an error that would influence processing.
An example for the processing statuses Followup Error and Hierarchy Error can be found at the end of this text.
- Filtered
The user has excluded the object from processing by using an application-specific filter.
- Not Relevant
- The object is not relevant for processing in this processing step due to its attributes derived from master data or Customizing
- The object is not relevant due to a status set for the object
Examples:
Example 1:
When variances were calculated in the period-end closing process for the Product Cost by Order component, the system selected all production orders in a plant in accordance with the selection parameters. Some of the production orders do not have a variance key. These production orders are not included in the variance calculation process. The production orders receive the processing status Not relevant.
Example 2:
When overhead was calculated in the period-end closing process of the Product Cost by Order component, the system selected all production orders in a plant in accordance with the selection parameters. Some production orders have a system status or user status that prevents processing. This is the case with the statuses Created, Closed, Deletion Flag, and Locked.
Note:
A status may make the object relevant or not relevant only in certain processing steps.
Example:
A production order has a settlement rule with the settlement type FUL (full). If the production order has neither the status DLV (delivered) nor the status TECO (technically completed), the order is not relevant for the calculation of variances, and receives the corresponding processing status. For the other processing steps of the period-end closing process such as template allocation, overhead calculation, WIP calculation, and settlement, however, the order is relevant both when it has either of the two statuses and when it has neither status.
When the processing status is Not Relevant, no messages are normally issued for the object and processing step. To see the messages that caused the processing status to be set to Not Relevant, you can have the object processed in individual processing. You can also force messages to be issued by using user-defined error management to set the message type higher.
Note:
In WIP calculation and results analysis, it is possible to force messages to be issued when the status is Not Relevant. You assure that messages are issued by setting the indicator Log Information Messages before executing WIP calculation or results analysis. If this indicator is set, all information messages are issued - both during processing within the multilevel worklist (even if the status is set to Not Relevant for the object and processing step) and outside of the multilevel worklist.
Manual Processing Statuses
You can set the following processing statuses manually:
- Processing Skipped Manually
In the object list, the user manually sets the processing status for an object and processing step to Skip processing. The system changes the processing status to Processing skipped manually.
Objects with this processing status are not included in the relevant processing step, and enter the next processing step.
- Processing Forced Manually
In the object monitor, the user manually sets the processing status for an object and processing step to Repeat processing. The system changes the processing status to Processing forced manually. The object is processed in the relevant processing step again even if no errors occurred when that processing step was executed the previous time.
Note:
When an object successfully participates in project interest calculation in an update run, the interest calculation must be reversed before a new run can be initiated. If no such reversal is performed, the object will not be included in the new interest calculation run despite the processing status.
Dependencies
The processing status is shown in the worklist of the Schedule Manager. It is not updated to the processed object.
For information on the following topics, refer to the section Using the Monitor of the Worklists.
- When you should skip processing or force processing manually
- How decision making on this point is supported
- How to change the processing status manually
Examples
Example for the processing statuses Followup Error and Hierarchy Error:
When actual overhead expenses were calculated in the period-end closing process, a production order assigned to a WBS element was not processed due to faulty Customizing settings. The production order receives the processing status Error for the processing step Actual Overhead.
Additional production orders are assigned to this WBS element. In the processing step Actual Overhead, all other production orders assigned to the WBS element receive the processing status Hierarchy Error. This status indicates that in the current processing step, one object (the production order) in an object group (all production orders assigned to a WBS element) is flagged as having errors.
The step&
History
| Last changed by/on | SAP | 20000128 |
| SAP Release Created in |
