Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-PRX (Application Component) Proxy Generation⤷
SAI_PROXY_GENTIME (Package) ES Tools: Proxy Generation
Basic Data
| Data Element | PRX_HDR_MODE |
| Short Description | Proxy Generation:Mapping Mode Coupled/Decoupled |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | PRX_HDR_MODE | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Map. mode |
| Medium | 15 | Mapping mode |
| Long | 20 | Mapping mode |
| Heading | 30 | Mapping mode |
Documentation
Definition
With the help of a Consumer Mapping, a call of a consumer can be mapped to a different web service than initially intended. For asynchronous operations, the mapping mode defines whether this consumer mapping is executed in the application context (coupled) or in a separate context (decoupled).
Use
- Decoupled mapping (Default)
Decoupled mapping is executed in a separate context, with an asynchronous border between the call of the consumer proxy and the mapping. This means that the mapping implementation cannot access the application data and that errors are handled separately in the message monitor.
- Coupled mapping
Coupled mapping is executed in the application program context without an asynchronous border in between. This offers the chance to access the application data in the mapping implementation, and to use it for message assembly. It also means that the error handling is carried out within the application.
Dependencies
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 803 |
