Hierarchy
⤷ IS-U-IDE (Application Component) Intercompany Data Exchange
⤷ EE_IDE_SWITCH (Package) IDE Change of Supplier and Service
Basic Data
Data Element | EIDESWTCHECKMETH |
Short Description | Method for Implementation of Checks |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | CHAR30 | |
Data Type | CHAR | Character String |
Length | 30 | |
Decimal Places | 0 | |
Output Length | 30 | |
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 | ChkMethd |
Medium | 15 | Check Method |
Long | 20 | Check Method |
Heading | 30 | Check Method |
Documentation
Definition
Two different types of check are differentiated between in the check framework:
- Checks carried out by the check method in the check framework
- Workflow exception handling
Use
Checks carried out by the check method in the check framework
The check defined in Customizing is executed and, depending upon the result of the check, the corresponding exception is triggered.
Note:
You must implement the check as a static ABAP-OO method. The method must have public
visibility, and cannot contain nested parameters in the interface. Only single values or flat structures that can be transported in a workflow container are permitted as parameters. The check method cannot return parameters to the workflow. The check result is returned in the form of an exception with a transparent error message (message ... raising ...
). The check method then takes over the determination of the necessary exception handling.
Workflow exception handling
In addition to checks that are executed directly in the check framework, the system can also react to exceptions that have occurred in the workflow (such as if the old supplier does not send a termination notification to the distributor within the termination period).
Note:
You can also handle project-specific workflow exceptions in the check framework. To do this, copy the definition of the check WFEXC_CHECK, including the parameter definition, and define all exceptions that are handled in the process. When accessing the check framework from the workflow, you must then enter your workflow check ID, the technical name of the exception, and an optional error message.
Dependencies
Example
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 471 |