Test Developer Authorizations

eCATT Authorizations in the Central Test 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	Package(s) whose objects the user may work with.
	OBJNAME	Any values, for example Y, Z for any package in the customer namespace	Object type the user may work with.

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	This allows the user to start transaction SM59.
S_ADMI_FCD	S_ADMI_FCD	NADM	This S_ADMI_FCD authorization gives access to all RFC administration functions.

eCATT Authorizations in the Tested 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 following authorizations are required:

Authorization Object	Field	Value	Description
S_RFC	RFC_TYPE	FUGR	Function group
	ACTVT	16	Execute
	RFC_NAME	SCAT	Test tool access routines
		SECATT_SFW	eCATT functions to Switch Framework
		STTF	CATT test tool functions
		ECATT_REMOTE_EXECUTE	Execution of external eCATT modules
		ECATT_SUT	eCATT Info in the System Under Test (tested system)
		SDIFRUNTIME	Interfaces for Type Runtime Objects
		SETRM	eCATT tested system: DDIC, FUN, ABAP, SAPGUI
		THFB	Task handler functions
		SBDR	Batch Input Recording
		SDYN	ABAP screen analysis
		STTM	CATT - Controls in CATT
		ECATT_REPOSITORY	eCATT Tested System: Access ABAP Workbench Repository
		ECATT_RTTI	Runtime Type Identification
S_RFC	RFC_TYPE	FUNC	Function module
	ACTVT	16	Execute
	RFC_NAME	DELIVERY_GET_INSTALLED_COMPS	Information about installed Software Components
		ABAP4_LEAVE_TO_TRANSACTION	Leave to transaction
		RFC_SYSTEM_INFO	Information about the system
		ECATT_REPOSITORY_F4_LONG_NAMES	Remote F4 help for repository objects
		ECATT_SET_CALLER_ATTR	Store caller information in global data
		PRGN_RFC_CHECK_TRANSACTIONS	Check via RFC the existence of a transactions list
S_DEVELOP	OBJTYPE	ECSC	Test Script
	ACT	16	Execute
	OBJNAME	*	The name of the script to be run.

Note

Note also, that the authorizations listed above do not allow to record or replay function modules (FUN).

To be able to record and replay functions modules, you need to assign additionally either the role SAP_BC_ECATT_TEST_FUN (with profile S_ECFUN) or the following authorizations:

Authorization Object	Field	Value	Description
S_TABU_DIS	ACT	03	Display
	DICBERCLS	SS
S_TABU_NAM	ACT	03	Display
	TABLE	TFDIR, USR01	Table TFDIR contains all existing function modules and USR01 all existing users. TFDIR authorization is needed, for example, that eCATT can check in the target system, if a certain function module exists. USR01 authorization is needed to get the date format of a user.