RFC (Remote Function Call) 

For several functions, GuiXT uses an RFC connection to the SAP System (Remote Function Call).  In order to logon to the system, the RFC needs a user name and password. GuiXT uses the logon values stored in GuiXT profile. As a default, the GuiXT profile contains the user “SAPCPIC”. Since this user is often locked in productive systems, we suggest you create a special GuiXT RFC user with appropriate rights. For testing purposes, you can also fill in your own user name and password in GuiXT profile.

The following table contains the GuiXT actions that use an RFC connection, the name of the called function, the client in which the logon takes place, and the necessary user rights.  

Instead of logging on to client 000, you can ensure via a profile option that GuiXT always uses the current client. This has the advantage that no RFC user has to be created in client 000. On the other hand, if you have numerous clients, you then have to create the RFC user in each client.

Creating an RFC user can be done in the SAP system with transactions  SU01, SU02, SU03. As an example below, we show how to create the necessary user rights for web repository access.

Action Client 
Function

Required RFC user rights

Read scripts for transaction variants 000 
RS_HDSYS_GET_GUIXT_SCRIPT
S_RFC: RFC_TYPE=FUGR, RFC_NAME=SHD0, ACTVT=16
Read web repository objects Objects “SAPWR:…” 000 
WWW_DISPATCH_REQUEST
S_RFC: RFC_TYPE=FUGR, RFC_NAME=SURL, ACTVT=16
Read data dictionary (symbolic offsets in variables) 000 
RPY_TABLE_READ
S_RFC: RFC_TYPE=FUGR, RFC_NAME=SIFD, ACTVT=16
S_DEVELOP
: DEVCLASS=*,OBJTYPE=TABL,OBJNAME=*,ACTVT=03
“Call” statement in GuiXT Script current client 
(function is specified in script)
S_RFC: RFC_TYPE=FUGR, RFC_NAME=xxxx, ACTVT=16

here xxxx is the function group of the called function

if Q[Role=...] and if Q[Profile=...] current client  
BAPI_USER_GET_DETAIL
S_RFC: RFC_TYPE=FUGR, RFC_NAME=SU_USER, ACTVT=16

S_USER_GRP: CLASS=*,ACTVT=03
S_USER_SYS: CLASS=*,ACTVT=90
(if central user administration)

Read images from “SAPDB:…” 000 
RS_HDSYS_GET_GUIXT_IMAGE
S_RFC: RFC_TYPE=FUGR, RFC_NAME=RSIMG, ACTVT=16
Read images from “SAPIM:…” (Business Document Server) 000 
RS_HDSYS_GET_BDS_IMAGE
S_RFC: RFC_TYPE=FUGR, RFC_NAME=RSIMG, ACTVT=16
S_BDS_DS: CLASSNAME=cccc, CLASSTYP=OT, ACTVT=30

here cccc is the class name of the BDS image file

 

Tracing and testing in the SAP System

  • Transaction ST01: Checking user rights during RFC
  • Transaction ST05: RFCs
  • Program sapinfo in directory sapgui/rfcsdk/bin: Test of RFC connection parameters
Creating a user with the appropriate rights

Sap Guixt profile rfc1 Remote Function Call
Figure  1: Start with transaction SU01

Sap Guixt profile rfc2 Remote Function Call
Figure 2: Create a separate profile
Sap Guixt profile rfc3 Remote Function Call
Figure 3: Grant rights for web repository access, according to the table above
Sap Guixt profile rfc4 Remote Function Call
Figure 4: Display user rights

Remote Function Call