Cisco Cisco Process Orchestrator 3.0
1-6
Process Automation Guide for System Copy for SAP
OL-24606-02
Chapter 1 Importing the Automation Pack
Importing ABAP Transport or Cisco Add-On
Importing the Cisco Add-On On SAP Systems
Perform the following procedure to import the Cisco add-on file on all SAP System targets where the
RFCs will be used.
RFCs will be used.
Step 1
Navigate to the location where the ABAP Transport data was extracted for the SAP version of the
systems in your environment. The default location is:
systems in your environment. The default location is:
C:\user\[username]\Documents\Cisco\Cisco Process Orchestrator\Extracted Data\ABAP
Transports\SAP System Copy\Add-on\
Transports\SAP System Copy\Add-on\
7.0
7.1
Step 2
Copy the SAP Add-On Package file(s) to the following location on the SAP server:
usr\sap\trans\EPS\in
Step 3
Log onto client 000 of the SAP system using an administrator account (DDIC or SAP* are not valid
accounts) and run the SAP transaction code SAINT.
accounts) and run the SAP transaction code SAINT.
Step 4
Follow the standard SAP procedures for performing an add-on product installation using SAINT.
Note
To verify whether the add-on is on the SAP system, use the SAP menu path System > Status and review
the software component versions for the Cisco software component add-on.
the software component versions for the Cisco software component add-on.
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
Process Orchestrator application. This is performed in Cisco Process Orchestrator by defining an ABAP
adapter step and specifying a method for the SAP Target system in a process. Cisco Process Orchestrator
ABAP custom methods perform individual tasks such as updating RFC Destinations, configuring
printers, and so on.
Process Orchestrator application. This is performed in Cisco Process Orchestrator by defining an ABAP
adapter step and specifying a method for the SAP Target system in a process. Cisco Process Orchestrator
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 Cisco Process Orchestrator 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 Cisco Process Orchestrator 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 Cisco Process Orchestrator 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.
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.