Cisco Cisco Workload Automation 6.3 User Guide

Page of 78
65
Working with SAP Jobs
Defining SAP Events
5.
If you wish to make the action public, select the 
Public
 option. When an action is public, the action will be available 
to all CWA users, within the bounds of their security policy.
6.
Select the desired owner from the 
Owner
 list.
7.
On the 
SAP 
tab, in the 
SAP Instance
 list select the SAP instance to receive notification of the event.
8.
In the 
SAP Event ID
 field, enter the event ID that SAP is expecting to trigger some action.
9.
In the
 Event Parameters 
field, enter parameters for the event, if any. You can use variables available from the 
Variables
 button.
This action can be associated with any defined event in CWA. Refer to the “Events” chapter in the Cisco Workload 
Automation User Guide
 for more information on configuring events. 
SAP Events (XBP 3.0 Interface Only)
Event Profile
Note: 
This feature is only be available for SAP Systems with the XBP 3.0 Interface.
Criteria Hierarchy of the Interception Profiles
A criteria hierarchy is stored in a criteria profile and can be active or inactive.
For the criteria in a profile to take effect, the profile has to be active. You can have many profiles, but only one can be 
active.
Warning: 
With the Use Existing Profile option of the connection in effect, multiple SAP connections or CWA 
implementations that point to the same SAP system must use the same Profile across all! The profile specified for 
connection(s) are activated when deactivated externally. Disabling these connections(s) in CWA prior to any 
external profile modification is highly recommended.

Criteria overlapping must always be avoided!
Note: 
Criteria in the profile can be managed by different Masters. Unlike Interception, for as long as it remains unique / 
no overlapping, it would work for every CWA Master.
Note: 
To get to the Criteria Manger within SAP System run Transaction: SE38 / Program: CRITERIA_MANAGER