Start the SAP GUI at operating-system level of your SAP system and import a system data container that has been stored locally.
1. Log on at operating-system level of your SAP system and create an entry for your SAP system in the SAP Logon box (if it does not already exist). Log on to your SAP system with your user.
2. In the initial screen for transaction SECATT, load a system data container from the operating-system level to your SAP system. Your instructor will provide you with the name and the storage location of the related XML file.
Solution 6: Configuring the System Landscape for Using eCATT
Task 1: Checking an RFC Destination
Check whether an RFC connection to your partner system exists.
1. Check whether the PARTNER RFC destination exists that points to your partner system.
a) Call transaction SM59 (Configuration of RFC Connections, menu path Tools → Administration → Administration → Network → RFC Destinations).
b) Open the ABAP Connections folder and check whether the PARTNER connection exists. Double-click this entry to display this connection.
On the next screen, choose Remote Logon. You should now be logged on to your partner system. Log off your partner system again by choosing Exit Session (in the standard toolbar).
Task 2: Checking the System Settings for eCATT
Check whether the execution of eCATTs is allowed in your SAP system and whether the execution of scripting commands is allowed.
1. Use transaction SCC4 to check whether eCATTs can be executed in your SAP system.
a) Call transaction SCC4 (Client maintenance, menu path Tools → Administration → Administration → Client Administration → Client Maintenance).
b) Select your logon client and choose Details. Under CATT and eCATT Restrictions, you can check whether CATTs and eCATTs can be executed in your client. If necessary, change the setting to eCATT and CATT Allowed (by choosing Display → Change) and save your settings.
2. Check whether the execution of GUI scripting command is allowed in your SAP system.
a) Run report RSPFPAR, either using transaction SA38 (System → Services → Reporting) or transaction RSPFPAR.
b) On the selection screen, restrict the selection of the profile parameters to sapgui/user*. Choose Execute.
c) The value of the system profile parameter sapgui/user_scripting is displayed as a result. If this parameter has the value FALSE, executing scripting commands is not allowed in your SAP system (irrespective of the settings of your local GUI). You can change this parameter dynamically (in other words, during live operation), using transaction RZ11. To do this, select the parameter in the output list of report “RSPFPAR” and then choose Call Trans. RZ11. On the initial screen for transaction RZ11 (Display Profile Parameter Attributes), then choose Change Value. You can then switch this value to TRUE (uppercase letters) on all servers (you may have to confirm a dialog box). Then log off and on again so that the change to the profile parameter takes effect also for your user.
3. Find out whether your local SAP GUI for Windows allows scripting commands to be executed.
a) In the standard toolbar, choose Customize Local Layout. Then choose Options ... → Scripting. If you select the Enable Scripting field, GUI scripting can be executed on your local GUI.
Hint: Depending on the version of SAP GUI, the menu path could also be Options ... → Accessibility & Scripting → Scripting.
Continued on next page
Task 3: Creating a System Data Container
Create a system data container. One entry in the container should refer to the PARTNERRFC destination.
1. Use transaction SECATT to create a system data container with the name ZECATT_SDC_## whereby ## designates your group number. Give the system data container a self-explanatory title.
a) Start transaction SECATT (Extended Computer Aided Test Tool:
Initial screen, menu path Tools → ABAP Workbench → Test → Test Workbench → Test Tools → Extended CATT). Select the System Data selection button, enter the name of the system data container (specified in the task step description) in the associated entry field and choose Create Object.
b) On the Attribs tab page, enter a descriptive title in the Title field of the Header Data area.
2. In your system data container, add a further target system on the System Data tab page. Name the target system REMOTESYSTEM, assign the name of the RFC destination PARTNER (checked above) to the target system, and enter a suitable product version. Save your settings.
a) Go to the System Data tab page and choose Add Target System. In the Target System field, enter the value REMOTESYSTEM. In the RFC Destination field, select the name of your RFC destination PARTNER checked above. In the Product Version field, enter the relevant version of your target system, such as Solution Manager 7.0.
b) Save your settings, and choose the package $TMP when doing so (or choose Local Object). Information about the selected target system should now be displayed in the Instance Description field.
Task 4: Optional: Importing a System Data Container
Start the SAP GUI at operating-system level of your SAP system and import a system data container that has been stored locally.
1. Log on at operating-system level of your SAP system and create an entry for your SAP system in the SAP Logon box (if it does not already exist). Log on to your SAP system with your user.
a) For the solution, see the task description.
2. In the initial screen for transaction SECATT, load a system data container from the operating-system level to your SAP system. Your instructor will provide you with the name and the storage location of the related XML file.
a) Call transaction SECATT. On the initial screen for this transaction, choose eCATT Object → Other Features → Upload. Go to the subfolder specified by your instructor and import the file
ECSD_ZADM102_SDC_TEMPLATE.xmlin this folder by selecting it and choosing Open. On the following screen Change eCATT objects to be uploaded, select the row with the system data container and choose Continue. A green traffic light should now be displayed in the Status column.
Hint: If one of the RFC destinations specified in the system data container to be uploaded does not yet exist in the system, a yellow traffic light is displayed. However, this does not prevent the container from being uploaded.
Choose Continue again. By choosing Display Object, you can then display the definition of the uploaded system data container ZADM102_SDC_TEMPLATE.
Result
You have learned about a number of system settings for using eCATT and created a system data container.
Lesson Summary
You should now be able to:
• List security issues related to using eCATT
• Make system and client settings related to eCATT
• Create a system data container Related Information
For more information about configuring SAP systems for using eCATT, see:
• SAP Note 519858(Set up SAP systems for using eCATT)
• SAP Note 496286 (Security concept for CATT and eCATT)
• SAP Note 480149 and 692245 (SAP GUI scripting)
• In the eCATT Security Guide on SAP Service Marketplace, Quick Link /securityguide in the Other area.