SAP ABAP Data Element /IBS/E_RBAPIDEST (RBD: Destination System for BAPI Call)
Hierarchy
☛
EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
⤷ FS-RBD (Application Component) Value Adjustment
⤷ /IBS/RB_BA (Package) iBS: RBD General Basis Objects
⤷ FS-RBD (Application Component) Value Adjustment
⤷ /IBS/RB_BA (Package) iBS: RBD General Basis Objects
Basic Data
Data Element | /IBS/E_RBAPIDEST |
Short Description | RBD: Destination System for BAPI Call |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RFCDEST | |
Data Type | CHAR | Character String |
Length | 32 | |
Decimal Places | 0 | |
Output Length | 32 | |
Value Table | RFCDES |
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 | BAPI Dest. |
Medium | 15 | BAPI Dest. Sys. |
Long | 27 | Dest. System for BAPI Call |
Heading | 32 | Dest. System for BAPI Call |
Documentation
Definition
Destination system/host for BAPI calls
System administrators can use transaction SM59 to configure settings for BAPI calls in the same way as they do for Remote Function Calls. Here, the destination host and client can be specified, among other things. A destination system should be entered only if the BAPI is located in a different system. The field should be left blank for local BAPI calls.
Enter a destination system that is called by the RBD extractors.
Example: An RFC from the Customizing table "RFC Table for Extractors of Linked Systems" cannot be used to link SAP-AM because an RBD extractor is not installed on the destination system. If you enter a destination system here, BAPI modules on a destination system can be called.
History
Last changed by/on | SAP | 20041209 |
SAP Release Created in | 600 |