Cisco Cisco Intelligent Automation for SAP System Refresh Guida Utente
1-14
Cisco TEO—Process Automation Guide for Task Automation for SAP
OL-24786-01
Chapter 1 Importing Automation Packs
Importing the Cisco Add-On Into SAP Systems
Error Handling, Logging and Tracing for ABAP Add-on
The ABAP Add-On contains API enabled ABAP function modules (RFC's) that are called by the Cisco
TEO application. This is performed in TEO by defining an ABAP adapter step and specifying a method
for the SAP Target system in a process. Cisco TEO ABAP custom methods perform individual tasks
such as updating RFC Destinations, configuring printers, and so on.
TEO application. This is performed in TEO by defining an ABAP adapter step and specifying a method
for the SAP Target system in a process. Cisco TEO ABAP custom methods perform individual tasks
such as updating RFC Destinations, configuring printers, and so on.
In the event the method encounters an error, such as attempting to modify an RFC destination that does
not exist, an error result is returned to the TEO process. This can then be modeled as an outcome to the
activity, and then subsequent actions based on the error returned may be performed.
not exist, an error result is returned to the TEO process. This can then be modeled as an outcome to the
activity, and then subsequent actions based on the error returned may be performed.
All RFC activity performed by TEO may be traced through SAP Standard RFC tracing functionality.
Refer to SAP online help for enabling the trace level for RFC communication on the SAP target system
using SAP transaction SM59. The SAP methods that are called may either write log entries to the SAP
System Log (SAP Transaction SM21) or to the Application log (SAP Transaction SLG1) depending on
the SAP standard application functionality. For instance, the SAP Application log is updated during the
BDLS process scenario as this part of the SAP standard application functionality.
Refer to SAP online help for enabling the trace level for RFC communication on the SAP target system
using SAP transaction SM59. The SAP methods that are called may either write log entries to the SAP
System Log (SAP Transaction SM21) or to the Application log (SAP Transaction SLG1) depending on
the SAP standard application functionality. For instance, the SAP Application log is updated during the
BDLS process scenario as this part of the SAP standard application functionality.
Support desk management for ABAP Add-on
SAP Root Cause Analysis ABAP tools can be used to review the performance and execution of the RFC
calls performed by the TEO system. A read-only SAP Administrator user is used to review the
functionality performed by the ABAP methods. The following roles are to be the basis for a composite
role that can be adapted to the customer environment:
calls performed by the TEO system. A read-only SAP Administrator user is used to review the
functionality performed by the ABAP methods. The following roles are to be the basis for a composite
role that can be adapted to the customer environment:
•
SAP_BC_BASIS_MONITORING,
•
SAP_BC_SEC_USER_DISPLAY,
•
SAP_BC_BTC_DISPLAY,
•
SAP_BC_MID_ALE_DISPLAY