You maintain the RFC sideinfo table RFCDES using Transaction SM59.Depending on the remote system, maintain one destination for the corresponding type.If you want to connect to another SAP System, you need a destination with type 3. Note that the name of a type 3 destination is case-sensitive.
If you want to ensure that the RFC logon is to a particular application server, set the Load distribution option to No. In this case, you must specify the R/3 application server using the target host and system number parameters.
If you do want to use load distribution when you log on, set the Load distribution option to Yes. In this case, you must specify the system ID, the message server, and the required server group. You can find out this information in the R/3 target system from Transactions SM51 (overview of R/3 servers) and SMLG (overview of logon groups). The message server of an SAP System is contained in the profile parameter rdisp/mshosou. You can display this using Transaction RZ11 or report RSPFPAR.
In the destination, you must enter the logon data for the user created in the target system (type 'dialog' or 'CPIC'). When the destination is used, the logon to the target system occurs automatically.If the logon language is not entered in an RFC destination, the logon language of the current caller is used.If the logon data is not complete or is faulty, a logon screen from the target system appears at runtime.
If you want to connect to an R/2 system, you need a destination with type 2. In the destination you need to specify the logon data of an R/2 user with the type 'CPIC'. You must also specify the SNA gateway (for IBM-R/2) or the host gateway (for Siemens R/2) through which the connection is made.
Note that the destination name (here, it is K50) for a type 2 destination cannot be chosen at random. It must match the name of the corresponding destination in the gateway sideinfo table .For connections to external RFC server programs, you need a destination with the type T. there are 2 variations of the T type:
1. Start: The external program is started when communication is being established.
a) On the application server: The external program is started on the current R/3 application server. You must give the complete program path including the program names.
b) On the explicit host: The external program is started on the specified host.
You must specify the following:
- Host name --> Name of the machine where the external program is located
- Path --> Complete path including program names on an external host
c) Front end workstation: The external program is started on the current front end at runtime via the SAPgui. You must enter the compete (absolute) path of the program including program names.
2. Registration: These destination variations let you access a program that has already started, which has registered itself on a gateway. This program must be started manually beforehand and registers itself using an RFC call with a program ID on a gateway (see the online documentation). With this variant, the start time is not required. It is suited to starting a program frequently. You must specify the following:
- Program-ID --> ID under which the external server program registered on the SAP gateway
- Gateway --> Host and TCP/IP service of the gateway where the external
program registered (If the gateway is the one for the current application server, this information is not required.)
These destinations are predefined standard destinations with have the following meanings:
- SPACE: Local call of a function module
- NONE: Also a local call, but the cal request is sent to the default gateway of the current application server and is handled there like an external call request. This destination is suited to the RFC test if you only have one system to test.
- BACK: You can use this destination if you want to start a function module from the called function module in the current system.
(This only functions with synchronous RFC.)
You cannot use this destination from R/2 systems.
Destination BACK cannot be used for R/3-R/2 connections.
RELATED POSTS
RFC PART 3
Analytical SAP CRm Overview
SAP CRM Solution Monitoring
CRM Backup Restoring System
No comments :
Post a Comment