Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-SCM (Application Component) Schedule Manager⤷
PROC_LIST (Package) Processing Log
Basic Data
| Data Element | OBJ2_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 | 52 | Processing Category |
Documentation
Definition
Indicates the state of the processed object. The processing category is output in the basic list. Each object is assigned to a processing category.
Use
The processing categories show how many objects were processed and how the objects were processed.
Objects processed without errors in a processing step are assigned to the processing category named according to the successfully executed processing step.
Example: 1,000 objects are processed in the Variance Calculation step. Variances are successfully calculated for all 1,000 objects. The processing category Variances Calculated shows that 1,000 objects were processed without errors.
In addition to the processing categories named according to the processing steps, there are also the following processing categories:
- No Change
The object was processed in a processing step. However, there are no new values because no relevant changes were made since the last time that processing step was executed.
- Not Relevant
The object is not relevant for processing in this processing step due to its attributes derived from Customizing or master data. Attributes that are time-dependent or that depend on transaction data (suchas an inappropriate status) do not trigger this processing category.
Example: In the period-end closing process of Cost Object Controlling, all production orders in a plant are selected for variance calculation based on the selection criteria. No variance key has been specified for some of the production orders. These production orders are not included in variance calculation. The processing category Not Relevant is assigned to the production orders.
- Inappropriate Status
The object is currently not relevant for processing in the processing step because it has a status that does not allow processing.
Example: You have specified the settlement type FUL (full settlement) for all production orders. This means that only production orders that have the status DLV (final delivery) and TECO (technically completed) are included in variance calculation. All production orders that were selected based on the selection parameters and have a variance key but do not have one of these statuses are assigned to the processing category Inappropriate Status.
- Minor Error
A warning or error occurred while the object was being processed. However, this error does not prevent further processing in a subsequent step.
Example: An error during WIP calculation in a statistical results analysis version does not prevent the object from being settled.
- Error
An error occurred that prevents further processing. If you are using the worklist of the Schedule Manager, you can correct the error or specify that the object should be included in the next processing step despite the error.
- Followup Error
An object is assigned to the processing category Followup Error for a processing step when the object is the highest object in an object hierarchy that contains an object which was assigned to the processing category Error in a previous processing step.
The entire object hierarchy cannot be processed as a result of the faulty object in the previous processing step. You can display the object that caused the followup error in the worklist monitor.
Objects with the processing category Followup Error are not processed in the processing step in which they were assigned to that category. This ensures that the entire group of objects can only be processed when none of the objects of the object hierarchy contains an error that prevents the highest object from being processed.
All other objects of an object hierarchy whose top object has the processing category Followup Error are assigned to the processing category Hierarchy Error for that processing step.
- Hierarchy Error
The processing category Hierarchy Error is assigned to all objects that are not the highest node in an object hierarchy if the highest object in the hierarchy has the processing category Followup Error or Error.
Objects with the processing category Hierarchy Error only move on to the next processing step when the errors in the objects that caused this processing category are corrected. If you are using theworklist of the Schedule Manager, you can have processing continue even without correcting the errors (processing status Skipped Manually).
Dependencies
The following processing categories in the basic list correspond to the processing statuses of the same name in the multilevel worklist of the Schedule Manager:
- Minor Error
- Error
- Followup Error
- Hierarchy Error
- Not Relevant
See also:
Processing Status of Object in Worklist
There you will find an example for hierarchy errors and additional information on the worklist of the Schedule Manager.
Example
History
| Last changed by/on | SAP | 20040312 |
| SAP Release Created in |
