eCATT & RFC & Different Users + Languages

[Former Member]

Hello, we have the following scenario:

We have a development and testsystem on different servers. We want to store the scripts in the development system and record/run in the testsystem -> with a RFC-connection.

Everytime we run the script we want to enter the different users (logon screen) - like SD-end-user for organization 1 with different languages.

When we don't store a user (we don't use trusted system) - in the RFC-connection we get the error "no authorization for transaction VA01 (for example)" - in the testsystem the user has this right. When we store a user in the RFC-connection then we can't switch between different useres.

Does this SD-end-user needs some specific rights for the RFC-connection?

Or do you have other solutions for testing the same testscript in a target system with different users + languages?

Many thanks in advance!

[Former Member]

Denise,

We had the similar issue specifically for user who tests the HR transactions due to different country setting based on user profile. So we created a new RFC connection from our system where we stored our script to the system where we want to execute those scripts. In that RFC connection we don't use trusted system and we left the username and password blank (did not provide).

Then we created a new target system using this new RFC connection in our System data container and we use this target system in our script.

When we execute this script the system will prompt for the logon where any user can provide their user id and password so that script will execute based on that user's authorization in the target system.

This is working perfect for all our HR users who are testing in different country based on their user profile country setting.

Try this information in your script and let me know if it works.

Let me know if you need more information.

thanks

Venkat

[Former Member]

Hello Venkat,

that is exactly the way we want to handle this. The logon-screen should always appear - so different users can log in (and enter the language).

I created new RFC-connection, left everything standard ("blank") in the authorization register, and put this to the system data container.

But when I want to record the script, the logon screen appears, but then the target system says: "No authorization for transaction VA01". If I log on to the target system with this user via the normal SAP-logon - then I have the rights.

Our Development and Quality System are two different machines - not two different clients.

Did you set some special user parameters?

Did you use the Authorization object S_RFC for the users?

Edited by: Denise Nepraunig on Mar 9, 2010 4:19 PM

[Former Member]

Denise,

Couple of options to check the issue.

1. Check the RFC connection using the test connection from SM59 to make sure it connects well with the target system. Basis has to setup the connection from SM59 for any missing authorization.

2. Before you start the recording from the script, edit the script and navigate thru the menu GOTO->Log Into the Target system.

System will pop-up the logon screen and provide the user and password. Now check the authorization with tcode you want to record. if there is any issue, basis has to check the eCatt authorization in the target system if any.

Let me know .

thanks

Venkat

[Former Member]

Hello Venkat,

Situtation 1: User + Password + Client + Language stored in RFC-Connection

SM59: Remote-Login, Connection Test and Utilities->Test->Authorization Test works

In Testscript: everything works, but no logon-screen of course

Situation 2: no user/password/client in the RFC-connection

SM59: Remote-Login and Connection Test works, Utilities->Test->Authorization Test fails (Name or password incorrect -> but didn't enter user/password - and I have the same user + password in both systems

-> In Testscript: GOTO->Log Into the Target system->enter transactions (f.e. VA01) ->everything works

-> Record Pattern SAPGUI in Testscript: logon-screen, target-system opens-> ERROR: "You are not authorized to use transaction VA01"

Any ideas?

[Former Member]

Denise,

In situation 2 instead of test the authorization, you can test for Remote logon button in SM59 and provide the user and password to enter the target system. Then try for the transaction VA01. If you get the authorization error then run the transaction /nSU53 to see what are the authorization objects are missing. With that information your SAP basis team can help you to fix that issue.

See if that helps,

thanks

Venkat

[Former Member]

Hello,

Does this occur for all the transaction or only to VA01.

Also check if the scripting is enabled for the target system.

Thanks & Best regards,

Ajay

[Former Member]

Hello Venkat, hello Ajay!

Everything works fine if we save the user and password in the RFC-Connection. If we want the logon-screen (for different users + languages) we have problems - we got the following error message in the SM21 in the target system:

R1 H Internal Error in Roll Out

R0 B Roll out failed, return code -01

R4 7 Delete session 002 after error 008

for the Program SAPMSYST, An internal error has occurred in the task handler. Contact SAP Support. ThRollOinternathxxmem.1709

We have release SAP ECC 6.0 and Kernel Release 700 - Patch 236

I think this is a SAP-Problem, we must post a OSS-message.

At the moment we have no other possibility and we do it this way:

We generate a RFC-connection for every test-user and store there the userpasswordclient in this connection and when we start the testscript we change the RFC-connection so that we can simulate different users. User must only exist in the target system. If we want another language we start the development-system (there we store the testscripts) in this language.