on 05-30-2008 12:59 PM
If we are using sendor side RFC adapter we are using TCP/IP RFC destination type why?
Hi Sushma,
Simply:
Use
For an RFC call that uses a TCP/IP connection to call a registered program, the AS ABAP is the initiator of the communication and the registered program is the acceptor.
One example of such a connection is the connection from an AS ABAP to an AS Java server. In this case, the AS ABAP uses the Java Connector (JCo) to establish the connection.
Thanks,
Satya Kumar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Transmission Control Protocol/Internet Protocol.
A software protocol developed for communication between computers.
R/3 systems which are tied together via TCP/IP are always RFC capable. One R/3
system can call function modules in a remote RFC system, just as if the function
where part of the own calling system.
During the initialization process, the RFC Server Module registers with the SAP Gateway using a specified Program ID. This Program ID must be set using the RfcProgramID connector configuration property and set up as a TCP/IP port in the SAP application. For more information on setting up a TCP/IP port, see Registering the RFC Server Module with the SAP gateway.
To register the RFC Server Module as an RFC destination:
In the SAP application, go to transaction SM59.
Expand the TCP/IP connections directory.
Click Create (F8).
In the RFC destination field, enter the name of the RFC destination system. It is recommended that you use RFCSERVER.
Set the connection type to T (Start an external program via TCP/IP).
Enter a description for the new RFC destination, and then click Save.
Click the Registration button for the Activation Type.
Set the Program ID. It is recommended that you use the same value as the RFC destination (RFCSERVER), and then click Enter
Thanks,
Satya Kumar
Edited by: SATYA KUMAR AKKARABOYANA on May 30, 2008 2:12 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bcoz the rfc sender communication channel is made such a way that it accepts the Program ID. This unique program-id has to be registered in R3 system. This registration occurs when u create a TCP/IP type RFC destination and provide an arbitary name there for Program-id
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.