Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U (Application Component) SAP Utilities⤷
EE80 (Package) IS-U: Customizing
IMG Activity
| ID | _ISUUTDE_000076 | Define Exception Handling for Checks |
| Transaction Code | S_KK4_82001256 | (empty) |
| Created on | 20030828 | |
| Customizing Attributes | _ISUUTDE_000076 | Define Exception Handling for Checks |
| Customizing Activity | _ISUUTDE_000076 | Define Exception Handling for Checks |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | _ISUUTDE_000076 |
Use
In this activity you define the project-specific exception handling for checks and switch views.
Requirements
Only define project-specific, standard exception handling in the following cases:
- You use the same check in different switch views, and a different standard exception handling is necessary for each switch view.
- You must redefine the exception handling for the standard checks.
Standard settings
Checks and exception handling are predefined by SAP. The predefined checks and preconfigured exception handling can be found in Customizing, under SAP Utilities -> Tools -> System Modifications -> User-Defined Enhancements for IDE -> Change of Supplier -> Define Checks.
If you do not define project-specific standard exception handling, the preconfiguration for the exception handling from the exceptions definition is adopted.
Activities
The following values can be used for exception handling:
00 No error -> Resume process
The check was carried out successfully, the result is logged, and the process is resumed.
Note: If you select this exception handling when an error occurs, the error is ignored and the process is resumed, as though no exception were triggered.
01 Temporary error -> Repeat check
A temporary error occurred during the check (for example, an object was blocked for processing). The check is automatically repeated several times according to the workflow system settings.
02 Critical error -> Cancel processing
A critical error occurred during the check. The processing of the message is cancelled (message status 006). The agent is not informed of the problem via information in his inbox.
03 Critical error -> Cancel processing + Agent information
A critical error occurred during the check. The processing of the message is cancelled (message status 006). In addition, the agent asynchronously receives information in his workflow inbox.
04 Critical error -> Agent decision necessary
A critical error occurred during the check. The agent receives a decision task with the following options in his workflow inbox:
- Continue processing / Modify data manually
- Reject notification / Cancel Processing
The process is only continued once the agent has made his/her decision. Both the result of the check and the agent decision are logged in the switch document.
05 Warning -> Resume process
The check results are logged in the switch document as a warning. The processing is resumed.
06 Warning -> Resume process + Agent information
The exception from the check is handled as a warning. The process is resumed. In addition, the agent asynchronously receives information in his/her workflow inbox.
07 Warning -> Agent decision necessary
The check provides a warning. The agent receives a decision task with the following options in his workflow inbox:
- Continue processing / Modify data manually
- Reject notification / Cancel processing
The process is resumed once the agent has reached a decision.
08 Unexpected exception -> Inform administrator
An unexpected error occurred during the check. The agent cannot handle this error. The administrator has the following options:
- Continue processing / Modify Data Manually
- Reject notification / Cancel processing
09 No error -> Continue according to agent decision
No errors occurred during the check. However, the agent must decide how to continue the process. The agent does not make the decision for this error handling within the workflow for the check framework, but in the calling workflow. For this exception handling, the agent receives case-relevant decision texts (such as, change switch type to end of supply). A handling of this type is not possible using the generic decision task from the check framework. In addition, however, the logging from the check framework is to be used.
Note: When using this exception handling, you must ensure in the workflow that, after the check framework has been called, a project-specific dialog step for the agent decision is called in the workflow.
Example
Business Attributes
| ASAP Roadmap ID | ||
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | _ISUUTDE_000076 | 0 | SK40000003 | Intercompany Data Exchange |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_EIDESWTCHECKEV | V - View | SM30 |
History
| Last changed by/on | SAP | 20030828 |
| SAP Release Created in | 472 |
