Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
CO-PC-OBJ (Application Component) Cost Object Controlling⤷
OBJ0_LOG (Package) Basic List/Processing Log
Basic Data
| Data Element | OBJ_LOG_STATISTICS_OBJECTS |
| Short Description | Processing Category |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 52 | |
| Decimal Places | 0 | |
| Output Length | 52 | |
| 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 | Category |
| Medium | 15 | Category |
| Long | 0 | |
| Heading | 40 | Processing category |
Documentation
Definition
The processing category indicates the state of the processed objects. The processing category is shown in the basic list. Since each object is assigned to a particular processing category, you can tell from this how many objects are in which state of processing.
Use
The processing category, which indicates whether the object was processed without errors, is always named according to the processing step that was successfully executed.
Example:
One thousand objects are processed in the processing step Variance Calculation. Variances are successfully calculated for all objects. The processing category Variances calculated shows a quantity of 1,000 objects processed without errors.
The basic list also contains the following processing categories:
- No change
The object was processed in the processing step. However, no new values were calculated because no relevant changes occurred since the last time the processing step was executed.
- Not relevant
The object is not relevant for processing in this step due to its attributes as derived from master data or Customizing. Time-dependent attributes or those that depend on transaction data (such as an inappropriate status) are not covered by this status.
Example: In variance calculation in the period-end closing process for Cost Object Controlling, the system selects all production orders in a plant on the basis of the selection parameters. Some of the production orders do not have a variance key. These production orders are not included in variance calculation. The production orders receive the processing category Not relevant.
- Inappropriate status
The object is currently not relevant for processing in this processing step. This is due to the fact that a status is set for the object which does not allow processing.
Example: You have specified the settlement type FUL (full settlement) for all production orders. This means that only the production orders that have the status DLV (delivered) and TECO (technically completed) are included in variance calculation. All production orders that were selected according to the selection criteria and that have a variance key receive the processing category Inappropriate status if neither of the above status codes has been set for them.
- Minor error
An error or warning message occurred while this object was being processed. This error does not, however, prevent further processing in a subsequent step.
Example:
An error in WIP calculation in a statistical results analysis version does not prevent the object from being settled.
- Error
An error occurred while the object was being processed that prevents further processing in a subsequent step. If you are using the worklist of the Schedule Manager, you can either eliminate the cause of the error or have the system process the object in the next processing step even though you have not corrected the error.
- Followup error
An object receives the processing category Followup error if it is the highest object in an object hierarchy and another object in the hierarchy was flagged as having errors in the previous processing step (processing category Error).
When an object is flagged as having errors in the previous processing step, this means that the entire object hierarchy cannot be processed until the error is corrected. You can view the objects that caused the followup error in the monitor of the worklist.
The object with the processing category Followup error is not processed in the processing step for which it receives this processing category. This ensures that processing for the entire group of objects can only be continued when none of the objects in the object hierarchy has an error that would adversely affect processing of the highest object.
For all other objects in the object hierarchy whose highest object has the processing category Followup error, the processing category Hierarchy error is updated in the same processing step.
- Hierarchy error
The processing category Hierarchy error is assigned to all objects in an object hierarchy that are not the highest node if the highest object in the hierarchy has the processing category Followup error or Error.
Objects with the processing category Hierarchy error only enter the next processing step when the error for the objects that are responsible for setting the processing category has been corrected. If you are using the worklist of the Schedule Manager, you can have the system process the object further without having to correct the error (processing status Processing skipped manually).
Dependencies
The following processing categories in the basic list correspond to the processing statuses of the same name in the generalized worklist of the Schedule Manager:
- Minor error
- Error
- Subsequent error
- Hierarchy error
- Not relevant
See also:
Processing Statuses in Worklist of Schedule Manager
This section also contains an example on subsequent errors and hierarchy errors, as well as additional information on the worklist of the Schedule Manager.
Examples
History
| Last changed by/on | SAP | 19990310 |
| SAP Release Created in |
