Test Developer Authorizations 

In addition to the authorizations listed below, test developers will also require authorization to run the transactions that they need to record in order to create a test script.

eCATT Authorizations in the Test Development System

In order to develop eCATT objects, users will require authorizations containing the following values:

Authorization Object	Field	Value	Description
S_TCODE	TCD	SECATT	This allows the user to start transaction eCATT.
S_DEVELOP	OBJTYPE	ECSC	Script
		ECSD	System data container
		ECTC	Test configuration
		ECTD	Test data container
	ACTVT	01	Create
		02	Change
		03	Display
		06	Delete
		16	Execute
	DEVCLASS	Any values, for example, Y*, Z* for any package in the customer namespace
	OBJNAME	Any values, for example Y*, Z* for any package in the customer namespace

If you have separate systems for developing test objects and the actual testing, your developers will also need authorization for the object S_TRANSPORT. Refer to the documentation of this object for full details.

Execution Control (New in Release 6.40)

Release 6.40 contains an execution control function, which allows you to pause, debug, or terminate a running test case. While any user can exercise this control over his or her own test cases, the following authorizations are required to take control of other users’ running tests:

Authorization Object	Field	Value	Description
S_DEVELOP	OBJTYPE	ECSC	Script
	ACTVT	70	Administer
	DEVCLASS	Any values, for example, Y*, Z* for any package in the customer namespace
	OBJNAME	Any values, for example Y*, Z* for any package in the customer namespace

Creating RFC Destinations

If a developer is to be able to create RFC destinations, he or she will require the following additional authorizations:

Authorization Object	Field	Value	Description
S_TCODE	TCD	SM59
S_ADMI_FCD	S_ADMI_FCD	NADM	This S_ADMI_FCD authorization gives access to all RFC administration functions.

eCATT Authorizations in a Remote System

If developers are creating test scripts that record in remote systems, they will require additional authorizations in that system. The communication between systems uses Remote Function Call, which contains its own authorization checks. Whenever a user tries to execute an RFC call, the system checks his or her authorization for the object S_RFC. The user must have authorization for the function group to which the function module belongs. Consequently, the following authorization is required:

Authorization Object	Field	Value	Description
S_RFC	RFC_TYPE	FUGR	Function group
	ACTVT	16	Execute
	RFC_NAME	SCAT
		STTM
		STTF	All eCATT function groups
		SBDR	A Batch Input function group - necessary to record TCD commands
		SDYN	A function group from screen processing – required for the screen simulation function in the eCATT Script Editor

eCATT Authorizations and External Tools

Normally when you work with an external tool, you will start it from eCATT. In this case, eCATT generates the user required for the RFC connection used to exchange script data (see Using Trusted RFC). If, however, you want to upload scripts from an external tool to eCATT without having started it through eCATT, you must log onto the SAP System yourself. In this case, you need the following authorizations for S_RFC (which are contained in role SAP_ECET):

Authorization Object	Field	Value	Description
S_RFC	RFC_TYPE	FUGR	Function group
	ACTVT	16	Execute
	RFC_NAME	SYST
		ECATT_EXTERNAL_TOOL