Committing SAP background events by an external task
About this task
SAP events
defined as HCL Workload Automation internetwork
dependencies, by default
are not automatically committed after their processing. You can modify
this default by specifying the -commit
parameter.
Otherwise, if you leave the default, you must commit the processed
event by using the external task Put Information (PI).
The PI task commits all the processed events that meet the given criteria. For this reason, it is recommended that you run this task at the end of the working day. By doing so, internetwork dependencies that are already resolved are not reset and the objects depending on them are not blocked until they are resolved again.
- -t PI
- The identifier of the task to be performed, in this case PI (Put Information). This parameter is required.
- -c XA_Unique_ID
- The unique identifier for the extended agent workstation connected to the SAP background processing system where the event is run. This parameter is required. For information about retrieving the unique identifier for the extended agent workstation, see UNIQUE_ID.
- -t CE
- The identifier of the task to be performed, in this case CE (Commit Event). This parameter is required.
- -evtid sap_event_name
- The name of the SAP R/3 event running on the background processing system. If the name contains blanks, enclose it between single quotes. This parameter is required.
- -evtpar sap_event_parm
- The parameter of the SAP event running on the background processing system. If the parameter contains blanks, enclose it between single quotes. This parameter is optional. If you do not specify it, all the SAP events with the name you specified, with or without a parameter, are committed on the target system.
SAP_TEST
, with parameter 1234567
, with extended agent workstation
with unique identifier horse10
connected to the background processing system:
r3batch -t PI -c horse10 -- " -t CE -evtid SAP_TEST -evtpar 1234567"