Hierarchy

⤷

⤷

Basic Data
Data Element | /SAPPO/DTE_RFCDEST_DIALOG |
Short Description | RFC Destination Dialog |
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 | RFC | |
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | DestDialog |
Medium | 20 | RFC Dest. Dialog |
Long | 35 | RFC Destination Dialog |
Heading | 40 | RFC Destination Dialog |
Documentation
Definition
The RFC destination dialog defines the connection to a remote system. You can use an RFC destination to set up a connection to another SAP system or client within the system landscape. In the context of the PPO, the RFC destination dialog has connection type '3' = ABAP.
Based on the Postprocessing Desktop, the RFC destination dialog is meant to restrict user access to certain data in the remote system. The RFC destination dialog is used primarily for business-related remote access. This RFC destination dialog guarantees RFC user access to business-related data in the remote system by means of the corresponding authorizations. The indicator 'Current User' (see transaction SM59, Tab 'Logon & Security' must be active so that the user name of the Postprocessing Desktop is passed on to the remote system and the authorizations to the business-related data are taken into account.
Use
- PPO postprocessing orders from remote systems can be loaded to the Postprocessing Desktop and processed.
- In the Postprocessing Desktop, Business Objects that are relevent to eliminating errors can be processed in the remote systems.
History
Last changed by/on | SAP | 20100420 |
SAP Release Created in | 30 |