Hierarchy
⤷ PA-AS (Application Component) HR Administrative Services
⤷ PAOC_ASR_GENERIC_FUNCTIONS (Package) General Functions
Basic Data
Data Element | ASR_ERROR_CATEGORY |
Short Description | Error Category |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | ASR_ERROR_CATEGORY | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
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 | Error Cat. |
Medium | 15 | Error Category |
Long | 20 | Error Category |
Heading | 15 | Error Category |
Documentation
Definition
Category of an error that can occur in a workflow step when or due to processing user input.
Note
The error category for an error is determined using program logic and cannot be configured. However, certain entries in Customizing control whether specific error categories can occur at all (see below in the list of error categories in the Comment column.
Use
Different error categories ensure that a workflow step can be forwarded to various experts if an error occurs.
The following error categories exist:
Error category Name Comment
COLLISION Data Collision A data collision occurs, for example, if the content of a field has changed in the database during the processing of a form and it is specified in Customizing that this case is to be checked (see collision check within the IMG activity Create Form Scenario).
NO_AUTH No Authorization
INCONSIST Inconsistent Data This error category is used for errors in the business logic - for example, if a certain content does not exist in the check table. For the Inconsistent Data error category, the user is able to forward to work item to an expert. The user is only able to do this if the container element SEND_EXPERT_IF_INCONSISTENT_DATA has the content X in the relevant workflow step.
OBJ_LOCKED Object is Locked (Only for Background Steps)
WRONG_CUST Incorrect Customizing Incorrect Customizing occurs if form scenarios are inconsistent. You can use the IMG activity Check Consistency of Form Scenarios to detect inconsistencies.
POBJEXE Exception for Process Object
APPEXE Exception in Application
OTHERS All Other Categories
Dependencies
Example
History
Last changed by/on | SAP | 20050411 |
SAP Release Created in | 600 |