EDI Setting RFC Destination

Several applications besides ALE and EDI use RFC destinations. RFC's they are used to access external print programs, fax programs, tax programs, and bar code readers.

RFC destination is used to start the online help program on your computer when you select Help, R/3 library from any menu in SAP.

An RFC destination is a logical name used to identify a remote system on which a function has to be executed. In the RFC destination, you specify the characteristics of the remote system, such as the host name and the program containing the function to be executed.

An RFC destination is used for the subsystem because the subsystem is an external system from SAP's perspective, no matter whether it resides on the same system as SAP or a separate system. The following two prerequisites apply when executing a function remotely.

The systems should be accessible to each other via TCP/IP or one of the supported network protocols.An operating system−level SAP user ID should be able to start a program remotely on the destination system. This feature requires configuration at the operating system level.

The program that implements the functions must use RFC protocols to communicate with SAP. RFC protocols are implemented via a set of APIs (Application Programming Interfaces) that both the sending and receiving programs use.

The subsystem is considered a remote system because it is not an SAP program. It can be installed locally on the SAP box or on an external system. Any communication between SAP and the subsystem requires the RFC destination .

For connectivity to occur, you must meet two prerequisites.

1.You must connect the systems via TCP/IP and maintain a "trusted user ID" on each system so that each can execute programs on the other system.

2· The subsystem vendors must write their subsystem programs using RFC protocols. You can circumvent this problem by using the rfcexec program shipped with the standard SAP system. rfcexec is a program at the operating system level that acts as the RFC server and can respond to SAP's RFC requests.

When it has to start the subsystem, SAP calls the function RFC_REMOTE_EXEC, which is implemented in the program rfcexe6c . SAP passes the name of the shell script for the subsystem, and the RFC_REMOTE_EXEC function executes the shell script. This strategy means that the EDI subsystem program does not have to use RFC protocols.

RFC_REMOTE_EXEC is a function in the rfcexec program and, hence, cannot be seen in the function library on the SAP system via SE37.

The trusted user setting is necessary to allow the SAP system to trigger rfcexec remotely. Assume that you have two systems, one running SAP and the other running the EDI subsystem. Assume further that the TCP/IP host names of the two systems are hostsap and hostedi.

Before you proceed with any settings, make sure that the systems are configured at the TCP/IP level to see each other. You can execute the ping command at the OS level to verify that the two systems are connected and can see each other.

After verifying the connection, you must set up the rhosts files and users on both systems. Because of the security implications of these settings, your system administrator and security specialists should participate in the design.(62.3)

Related Posts

EDI basic components configuration part one and two
EDI sub system part one and Two
EDI inbound process overview
EDI subsystem architecture and mapping



No comments :

Post a Comment