How to create RFC Destinations for liveCache Applications

RFC Destinations for liveCache Applications

You use this procedure to use liveCache across clients, for example, to initialize liveCache correctly.

1. Create a user with the following authorizations in all production clients:

Cross-application AAAB authorization objects

Authorization object: S_TCODE Value: SE38

Authorization object: S_RFC Activity: 16

Name of RFC object to be protected : /SAPAPO/DM_LC_SYNC, SYST

Type of RFC object to be protected : FUGR

Basis development environment BC_C

Authorization object: S_DEVELOP Value: 03, 16

Authorization object: S_PROGRAM

User action ABAP/4 program : *

Authorization gr.ABAP/4 program : (no input necessary)○

Basis administration BC_A

Authorization object: 'S_BTCH_JOB'

User action: 'RELE'Note

Ensure that the user no longer has the initial password in any of the clients.

Note
Ensure that the user no longer has the initial password in any of the clients.

2. In each client, create a RFC destination by performing the following substeps:

1. Start transaction SM59.

2.Choose Create.

3. Add a CLNT string and the client number (for example, "678") to your system ID (for example, "XYZ") to determine the connection name.

4. Enter the connection name in RFC destination.

5.As a connection type, choose "3" (= SAP S/4HANA backend system destination or connection to the ABAP system).

6. Enter a description for the destination.

7. In the Logon section, enter the user credentials of the user created in this client in step 1.

Note
Ensure that the password is no longer initial, and do not select Current User.

8. Save the changes.

Verifying the Above Steps

To check that you have carried out all the steps correctly, choose Remote Login.

The system should display an SAP S/4HANA backend system window, but not an SAP S/4HANA backend system logon screen. If the system displays an SAP S/4HANA backend system logon screen, check if all steps above were performed correctly, you should check whether or not the user is actually available in this client (in particular). This test is not possible with an RFC destination with a CPIC user.

Note
You create the same user in each client only once. You must, however, ensure that the clients of the destination and user match. The user may also be a CPIC user. The authorization "Authorization object: S_TCODE Value: SE38" and similar should be assigned here also. You should also check if you can implement SAP Note 536291