Retain eCATT scripts during refresh

[Former Member]

I have created my eCATT scripts in one of the QA ECC systems in our landscape as local objects. Now the system is going to be refreshed from production, thus wiping out my scripts.

How can I avoid this from happening? Is there some way I can export them or save them off in a different manner?

[AjayHS]

You can download the script and later upload , its important to download every script which are referenced within the script.

Thanks,

Aj

[Former Member]

Thanks Ajay!

[Former Member]

Hello Archana,

There are 2 ways you can do.

1. You can transport the ECATT script to your production system.

    Transaction SECATT, ecactt Object -> Other features -> Write Transport Entry

2. You can download the ECATT script and then upload it later after system refresh.

  Transaction SECATT, ecactt Object -> Other features -> download/upload

Regards,

Laxman

[Former Member]

Thanks Laxman! I'm going to try the download method for now.

[pb3030]

Hi Archana,

Apart from the options provided by Ajay and Laxman, it is also suggested that the eCATT scripts should reside in a central system (example : SOLMAN or any other system) other than QA system which will make your job easy (avoide this excersie of download and upload or transport import and export) and this depends on the number of scripts that you have and it's criticality.

Regards,

PB

[Former Member]

thanks for your input, Prakash! I am still just exploring and experimenting with eCATT in my current QA system. If we get to a point where we want to implement this further as an "automated testing solution", I'll keep your input in mind.