Using Different Roles in Ecatt

[Former Member]

I am fairly new to ecatt. I have been able to record basic scripts. I have looked for tutorials on how to create scripts where you can use different roles. What I want to do is be able to create a purchase order with one role, then some how be able to log out and log in as our warehouse test user, and receipt the item. Then I want to log back out and log back in as one of our AP roles to process and pay for the item.

Is this possible and if it is can anybody point me in the right direction. Thank you very much for your help.

[Former Member]

Go to SM59 and create a RFC. The type of RFC is dependent on the type of connection that you need.

The general details required are : Description, host name, system number, login details (client, userid and password) etc.,

Create 2 RFC's - one with each role / userid and link these RFC's to 2 different target systems in the System data container.

While recording, use the corresponding target system and get your requirement solved !

Hope this helps!

[Former Member]

HI Marcus,

Though this is a common requirment,It is not possible as far I know.

I would suggest to have a set of test plan assigned to a tester and get them tested.

If in a scenario,if it is involves testing by several roles,it is required to login back out and log back in again.

Thanks and Regards,

SSN.

>

> I am fairly new to ecatt. I have been able to record basic scripts. I have looked for tutorials on how to create scripts where you can use different roles. What I want to do is be able to create a purchase order with one role, then some how be able to log out and log in as our warehouse test user, and receipt the item. Then I want to log back out and log back in as one of our AP roles to process and pay for the item.
> 
> Is this possible and if it is can anybody point me in the right direction. Thank you very much for your help.

[Former Member]

I believe it can be done. Just the consider the below idea:

Clearly you need to create an integrated eCATT script which refers individual eCATT scripts to perform your requirement.

Individual eCATT script-1 :

Create a purchase order recording and the use the proper target system where RFC login details should be of the AP role / user

Individual eCATT script-2 :

Create a recording to 'receipt the item' and use the proper target system where RFC login details should be of the warehouse test user.

Individual eCATT script-3 :

Create a recording to process and pay for the tiem and use the proper target system where RFC login details should be of the AP role / user.

Hope this is of some help!

[uwe_schieferstein]

Hello Marcus

That's exactly the way you should do it. Assuming that you are recoding your eCATT scripts on a stand-alone system (e.g. Solution Manager) you have to connect via RFC to the target system.

Normally you assign a system data container to your script and choose a default RFC destination.

However, you can define the target RFC directly within the eCATT, e.g.:

In a test script, you could have:

TCD ( <transaction code>, <command interface> , TARGET_A ).

TCD (<transaction code>, <command interface> , TARGET_B )

CHETAB ( <table>, <command interface>, TARGET_C ).

WEBDYNPRO ( <command_interface>, TARGET_A ).

For more details please refer to: [Specifying Target Systems|http://help.sap.com/saphelp_erp2005/helpdata/en/f4/de0c3c22a8ab4ee10000000a11402f/content.htm]

Regards

Uwe

[Former Member]

Hi Uwe,

This is exactly what I had in my mind while writing my response.

As eCATT has split the entire process into 4 main objects when in comparision with CATT, a lot of permutations and combinations are possible thus leading to flexibility.

[Former Member]

Do you know of any step by step guide for this sort of process. I am not too familar with setting up RFC's.

Thanks for the adivce though, it gives me a lot more to look into.

[Former Member]

Go to SM59 and create a RFC. The type of RFC is dependent on the type of connection that you need.

The general details required are : Description, host name, system number, login details (client, userid and password) etc.,

Create 2 RFC's - one with each role / userid and link these RFC's to 2 different target systems in the System data container.

While recording, use the corresponding target system and get your requirement solved !

Hope this helps!

[Former Member]

Aren't RFC just when you are crossing systems? Do I really need to create an RFC to run two different roles on the same system?

Thanks again for your help

[Former Member]

RFC is not just for crossing systems as it can also be used to connect to the same system (same or different id)

It has login details in it and hence helps you to login with a different user id within the same system.

[Former Member]

Thanks again for the help. So basically I can create RFC for each of my test users. Then assign the user name and password to those RFC's. Then, when I create the ecatt I can link the different process from different RFC's to make one process, but it will use multiple roles.

The other question, these roles must have the authorization to run ecatt correct? Currently our department has access to Ecatt, but our test users do not.

Thanks

[uwe_schieferstein]

Hello Marcus

The system on which you want to execute the eCATT scripts must allow to run CATT/eCATT (check using transaction SE03 or SALE ). The RFC users used to run the scripts do not need any eCATT authorizations.

Regards

Uwe

[Former Member]

Sorry, if the questions seem rather easily answerd, but from what you're saying as long as I can run an ecatt script on this system, then I shouldn't have to create special authorizations for the test users.

I have been able to create basic scripts, but I have not been using a target system. I have just been using "none". When I try to use the RFC I have been getting the following errors:

"Recording and Replaying are not possible with this user in teh target system. This is only possible in Target Systems with Basis 46C or Higher. See Note 519858 to make such a system ecatt-enabled."

Then if I plug in my user name and password in the RFC it gives me "RFC: You have no authorization to create destination ECATT_SAPAP2_115_E"

I am assuming there is something not properly set up with my RFC, do you know of what it may possibly be.

Thanks