SAP ABAP Data Element SXMSOPER (Pipeline Element Operator)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-XI-IS-IEN (Application Component) Integration Engine
⤷
SXMSF (Package) XI: Integration Engine Runtime

⤷

⤷

Basic Data
Data Element | SXMSOPER |
Short Description | Pipeline Element Operator |
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 | 64 | |
Decimal Places | 0 | |
Output Length | 64 | |
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 | Operator |
Medium | 15 | Operator |
Long | 35 | Pipeline Element Operator |
Heading | 35 | Pipeline Element Operator |
Documentation
Definition
The field operator distinguishes services.
The actual service (a routing or mapping service, for example) always has the operator MAIN.
The service sends possible causes of error in the interface parameter ERROR_KEY. There should be a service for each error cause that processes these exceptions. The operator who calls the exception handler must have the details from ERROR_KEY .
Example:
- A routing service generates the error NO_ROUTING_INFORMATION.
- A pipeline element with the operator NO_ROUTING_INFORMATION exists. The service linked to the pipeline service processes this exception, for example by generating alert information.
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 46D |