Hierarchy
⤷ OPU-FND-CS (Application Component) IWF Common Services
⤷ /IWFND/COS_DESTINATION_FINDER (Package) GW Framework - Destination Finder
Basic Data
Data Element | /IWFND/DEFI_IS_FOR_BEP |
Short Description | Indicates that the System Alias is to be used by BEP |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | BOOLE | |
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 | 0 | |
Medium | 20 | For Local App |
Long | 40 | For Local App |
Heading | 40 | For Local App |
Documentation
Definition
SAP NetWeaver Gateway applications can be developed either on a SAP Business Suite backend system or on a SAP NetWeaver Gateway hub system. To access the business logic from an SAP Business Suite backend system the software component IW_BEP (Backend Enablement and Event Provisioning) has to be deployed in your system landscape. IW_BEP can be deployed on the backend system or locally on the SAP NetWeaver Gateway hub system. Communication is handled via system aliases (RFC destinations).
Use
Set this flag if you use this system alias for an OData Channel application that has been developed on the BEP add-on which is deployed on the SAP NetWeaver Gateway hub system.
In this case the system alias information (such as RFC destiation, Web service group, software version) is not used by SAP NetWeaver Gateway to call the BEP API (it is called locally). Instead the system alias information is passed through to the OData Channel application, so that it could then itself make a call to the corresponding backend system.
Dependencies
Example
History
Last changed by/on | SAP | 20131122 |
SAP Release Created in | 250 |