SAP ABAP Data Element BS_SOA_WS_ACTIVE (Activate WebService Enablement classes)
Hierarchy
☛
SAP_BS_FND (Software Component) SAP Business Suite Foundation
⤷
CA-SOA (Application Component) Enterprise SOA
⤷
BS_SOA_REUSE_COMMON_OBJECTS (Package) Business Suite SOA: Reuseable Tools and Objects
⤷
⤷
Basic Data
| Data Element | BS_SOA_WS_ACTIVE |
| Short Description | Activate WebService Enablement classes |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| 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 | Active |
| Medium | 15 | Active |
| Long | 20 | Active |
| Heading | 10 | Active |
Documentation
Definition
Selected asynchronous Enterprise Service support point-to-point communication through the Web Service protocol.
This requires additional logic for both a service provider and the service consumer:
- Dependent on the protocol (XI vs. WS) a service consumer needs to differentiate certain features. 'Exactly Once In Order' for instance is available within the XI protocol only - the Web Service protocol instead provides 'sequences' which need to be administered by the consumer.
- In a Request Confirmation pattern a service provider needs to correlate a response message (Confirmation) to the pertaining request message so that the reponse is routed correctly.
- Correct message sequencing between the message sender and recipient needs to be ensured on the application level to ensure data consistency. A persistent sequence closed by a service provider - or messages transferred and rejected in 'Forward Error Handling' might lead to out-of-sequence situations which cannot be avoided on the technical layer.
To support the required additional functionality a reuse library is provided in Business Suite Reuse layer. This library can be activated with this switch.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in | 702 |