{"id":592,"date":"2011-12-31T02:10:03","date_gmt":"2011-12-31T02:10:03","guid":{"rendered":"http:\/\/sapsecurityanalyst.com\/WP\/?page_id=592"},"modified":"2015-05-03T08:10:43","modified_gmt":"2015-05-03T08:10:43","slug":"secatt","status":"publish","type":"page","link":"https:\/\/sapsecurityanalyst.com\/WP\/secatt\/","title":{"rendered":"SECATT"},"content":{"rendered":"


\nIn this section we will discuss about SECATT<\/strong> – how it can be used for performing mass tasks and hence how it helps in saving a lot of manual effort.<\/span>
\n<\/span>
\n
\nBut before SECATT can be applied, it is necessary to check and confirm if the client settings in SCC4 allows for executing this transaction.
\n<\/span>
\nThis can be checked in tcode SCC4 as shown in the below screen<\/span>
\n<\/span>
\n
\n\"\"
\n<\/a>
\n
\nThere are four processes which need to be followed for successful execution of SECATT:<\/span><\/span><\/p>\n


\n<\/span>
\n (1) Step 1<\/span> – <\/strong>Recording the tcode execution<\/span>
\n<\/span><\/h3>\n

For this we use the option “Test Script” option in SECATT tcode as shown in the figure below:<\/span><\/p>\n

\"\"<\/a><\/span>
\n
\nHere we execute the necessary tcode for which we are creating the SECATT script and record the steps which are required for successful execution of the tcode. It is important to note that we should be very careful while executing this process and only those steps should be followed which are necessary. Any mistake can result in wrong recording of the script which may lead to failure of SECATT task which we want to complete.<\/span>
\n<\/span>
\n<\/span><\/p>\n


\n(2) Step 2<\/span> – <\/strong>Creating the Parameters
\n<\/span><\/h3>\n

During the execution of Step 1<\/strong>, we would have entered certain values for the tcode (e.g. for creation of users through SU01 we would have entered user id, password etc). These values are called VALINS.<\/strong> These need to be changed to Parameter Values <\/strong>during this step (Step 2<\/strong>). We will see how this is done when we start performing the SECATT activity in our later sections where we will show how to create SECATT scripts for various mass tasks.<\/span>
\n<\/strong>
\n<\/span><\/p>\n


\n
\n(3) Step 3<\/span> – <\/strong>Creating Test Configuration
\n<\/span><\/h3>\n

Once Test Script has been created and VALINS have been defined, we need to create “Test Configuration”. The option “Test Configuration” is used for this as shown in the figure below:<\/span><\/p>\n

\"\"<\/a><\/span>
\n
\n<\/span>(4) <\/span>Step 4<\/span> – <\/strong><\/span>Updating and Uploading the Variant file<\/span><\/span>
\n<\/span><\/h3>\n

Once the Test Configuration is over, a variant file gets created. This file needs to be saved and updated with the new values for the mass creation purpose (e.g. for mass creation of users, this file needs to be updated with list of new user ids, passwords etc.) Once the file is ready, it can be used to perform the mass task. <\/span>
\n
\nThis discussion was just to give an overview of the steps which we need to perform while executing SECATT. We will see how these are actually performed in our next sections where we will go through various SECATT related activities.<\/span>
\n