Below you will find the example of Int4 IFTT role based on Int4 IFTT authorizations.
The role below is a full access role in the Int4 IFTT itself as well as it contain basis authorizations needed for initial customizing and building connections to tested systems.
Basic Int4 IFTT user tcodes
...
TCODE
...
Description
...
/INT4/IFTT_COCKPIT
...
Test Cockpit
...
/INT4/IFTT_TCOCKPIT
...
Test Cockpit
...
/INT4/IFTT_TC_REPORT
...
Test Cockpit
...
/INT4/IFTT_CONF
...
Automation Object
...
/INT4/IFTT_CONF_MASS
...
Automation Object
...
/INT4/IFTT_CONF_EXP
...
Automation Object
...
/INT4/IFTT_ADMIN
...
Customizing
...
/INT4/IFTT_CUST
...
Customizing
...
/INT4/IFTT_IMG
...
Customizing
...
/INT4/IFTT_LNDSCP
...
Customizing
...
/INT4/IFTT_RUN
...
Test Cockpit
...
/INT4/IFTT_REM_COMP
...
Parallel run
...
/INT4/IFTT_LICENSE
...
Customizing
...
/INT4/IFTT_VIEW_WRAP
...
Customizing
...
/INT4/IFTT_PI_ROBOT
...
Int4 IFTT role templates contain only essential authorization values directly related to the usage of IFTT.
Based on typical usage scenarios in Testing projects following object/transactions might also be added to the created roles.
Troubleshooting interface issues:
TCODE | Description |
---|---|
SRT_UTIL | Tracing Utilities for Web Service |
SRT_LOG | Tracing Utilities for Web Service |
SU53 | Evaluate Authorization Check |
SECATT | Extended Computer Aided Test Tool for record and playback of SAP ECC, S/4HANA transactions |
ST22 (with right to debug) | System Dumps |
...
ABAP Short Dumps |
Description | Object | Field Name | Activities | Execute / Add Test cases | /INT4/IFTT | ACTVT | 02|
View / Edit Int4 IFTT entries | S_TABU_DIS | ACTVT | 02 | ||||
DICBERCLS | INT4 | ||||||
Import / Export files by SAP GUI | S_GUI | ACTVT | 60 | ||||
for SRT_LOG to check status of SAP PI/PO webservices | S_XMB_MONI | ACTVT | 03 | Role to call the Int4 IFTT API by webservice | S_SERVICE | Type: external service |
Roles for initial customizing that requires basis authorizations (optional)
...
Initial Int4 IFTT customizing:
Below t-codes and authorization objects are needed to build connectivity with SAP PO and SAP Backend systems (SAP ECC or SAP S/4HANA)
TCODE | Description |
---|---|
SM59 | RFC Destinations |
SICF | HTTP Service Hierarchy Maintenance |
SOAMANAGER | SOA Manager |
...
Description | Object | Field Name | Activities |
Add RFC connections | S_RFC_ADM | ACTVT | 01 |
Activate BSP for Int4 IFTT | S_ICF_ADM | ACTVT | 03 |
Logical ports maintenance | S_SRT_CF_C | ACTVT | 01 |
Testing in SAP Backend (ECC or S/4HANA)
TCODE | Description |
---|---|
SECATT | Extended Computer Aided Test Tool for record and playback of SAP ECC, S/4HANA transactions |
WE02 | IDoc monitor |
SXMB_MONI | Proxy monitor |
WE19 | IDoc test tool |
WE20 | Partner Profiles |
VA01, VA02, VA03 | Sales Orders |
VL01, VL02, VL03, | Deliveries |
VF01, VF02, VF03 | Invoices |
Any other business transaction which IFTT will be using to test (e.g., ME22N, CI42) and others. In general, this should be the same role that is assigned to external functional consultants |
|