Connection between development and productive system using SCAT?

[Former Member]

Hello all,

a colleague wants to use SCAT. He runs this transaction in the development system to change data in the productive system.

Now, he says, for each data set he has to apply at the productive system. Normally there is on access for all data sets.

I try to find out how the access between development and productive system is built.

Can someone tell me what connection is normally used by SCAT?

Many thanks!

[mvoros]

as usual, [RFC connection|http://help.sap.com/saphelp_erp2005/helpdata/EN/d7/e21407408e11d1896b0000e8322d00/frameset.htm].

Cheers

[Former Member]

Hi LittleIcebear,

Warning:

It is not recommended to use SCAT (or eCATT) against a productive system because these tools are for testing. Also the execution of CATTs or eCATTs is not allowed in the production system.

Cheers,

Sebastian

[Former Member]

Hi,

The SCAT or SECATT are executed remotely via Development into Production. The CATT uses RFC connection. You can verify the RFC connection Development is pointing towards Production using transaction code SM59 in development. It is not a good idea toa apply SCAT in Prodution and SECATT have to be used remotely.

Regards.

[Former Member]

Hello,

many thanks for your answers and the warnings, too.

Nevertheless when my colleague uses SCAT remote he gets for every data set a new popup to log in into the target system.

Normally you log in one time and afterwards all data sets will be transferred.

Do you have an idea what's wrong?

Thanks a lot!

[Former Member]

Hi,

check the RFC connection in transaction sm59.

Best practice is to use a trusted RFC. Is this not possible, so use a RFC with one static user (important: save the password in the RFC connection!)

[Link to SM59-SAP-Help|http://help.sap.com/erp2005_ehp_04/helpdata/EN/e2/7efb40ef74f923e10000000a155106/frameset.htm]

Best regards

Sebastian

[Former Member]

Hi,

depending on the tool you are really using I can give some comments:

- Usually both SECATT and SCAT do keep RFC sessions open between multiple runs of test cases or variants of the same

- Keeping RFC sessions open will ask the user only one time for logon to target system

-> If you find no way to provide credentials in RFC connection setup like suggested, you have to care for the RFC connection not beeing closed between your variants

Possible causes for your connection not keept open:

- in eCATT (SECATT) you have start options (Close RFC Connection) which would care for closing the connections per testcase run -> advantage for testing purposes by seperating the effects of several tests from each other

-> In your case this option might be contra-productive

- There are also some script commands in SECATT which would force a close of RFC connection, e.g. RESCON

- Last but not least RFC connections are terminated by the system once a serious error in target session is faced (e.g. dump)

Best Regards

Jens

[Former Member]

Hello,

Create an RFC with the generic user and password and then use this RFC and create a System data container in SECATT.

In SDC link the RFC with the logical name of the target system.

Now use this logical name when you run the system , so the script uses the generic user to login and you wont get the login information everytime when you execute the script.

Are you using CATT or ECATT? CATT is obselete in usage.

Thanks & Best regards,

Ajay