SCC4 Settings

Hi John,

CATT = Computer Aided TESTING tool.

This is simply an on-or-off switch saying CATTs can be run or CATTs can not be run.

Ideally one should let CATTs run in DEV and sometimes in QAS but never PRD, unless, it is for initial data loads purposes - and then shut it off as soon as possible.

Implication

Someone with access to SCAT in production could upload false or bad data into your system. Especialy when it comes to configuration. Without the other areas locked as well, someone could really mess with your tables, load users, etc.

If someone is allowed to use SCAT and wants to upload something, they could potentially upload during peak usage of the system and cause a major slowdown.

You usually don't allow anyone to do this in Production once the system is up and running. There may be a rare config occasion, but then they need to request the system to be open during a specific time frame and for how long. Most likely this is all setup during a "change control" process so that everyone knows exactly what that person is doing.

Example:

There are functions in the scat related objects, which serve the sole purpose of calling other functions once the first check has been passed at "1" (read the docu). There are also several transactions and reports (SA38 ect) which lead to CATT runs. Therefore, any person with FUGR authorizations for SCAT objects has potentially an SAP_ALL authorization on the system.

Source:

http://sapbasisnotes.blogspot.com/2007/11/scc4-and-catt-settings.html

Hope this helps.

Regards,

Varun