Job Interception Configuration 
When a job is found in the SAP System it is checked against the XBP interception rules defining the action to take on the job. The pattern matching is case sensitive.
See the Connection Details for the ABAP Stack section of the documentation for details on how to set up a connection to the ABAP stack.
Tab |
Field |
Description |
XBP Job Control Rules |
Job Handling |
Reports the setting of the Job Handling field on the SAP System tab. |
XBP Job Control Rules |
Enabled |
Allows you to diable rules, preserving the settings for future use. |
XBP Job Control Rules |
Description |
the description to use for this rule. If the description is not set, the rules are named <Action>/<Client Number Mask>/<Username Mask>/<Job Name Mask>, Please see the list below for available actions. |
XBP Job Control Rules |
Processing order |
Order in which to process this rule. |
XBP Job Control Rules |
Action |
Defines how to handle the job. Please see the list below for available actions. |
XBP Job Control Rules |
Client Number Mask |
SAP client pattern that is used to match jobs. |
XBP Job Control Rules |
Job Name Mask |
Job name pattern that is used to match jobs. |
XBP Job Control Rules |
Username Mask |
User name pattern that is used to match jobs. |
XBP Job Control Rules |
Job class (A, B, C) |
The SAP job class |
XBP Job Control Rules |
Default Queue |
Queue the job should be put on (currently not used). |
XBP Job Control Rules |
Priority |
Priority of the job (currently not used). |
XBP Job Control Rules |
Retrieve Joblog |
Should the log of the job be retrieved? |
XBP Job Control Rules |
Retrieve Spool |
Should the output file of the job be retrieved? |
XBP Job Control Rules |
Applies to jobs in SAP status |
You may restrict this rule to jobs with a specific status in SAP, see the details below. |
The following wildcards are supported in masks:
* to match any string, for example BI_PROCESS_* would match BI_PROCESS_ABAP and BI_PROCESS_OR.
? to match a single character, for example RSUSR?00 would match RSUSR200 and RSUSR400.
The following actions are available:
Monitor: A reference to the job is created in SAP CPS. The status of the SAP job can be monitored in the job monitor of the SAP CPS.
Hold: The same as Monitor with the difference that if the SAP job is found to be in a Released state in SAP (which means waiting to start at a certain point in time), it is dereleased (put back in status Scheduled in SAP) and submitted on hold in SAP CPS.
Ignore: Jobs that match this rule are confirmed in SAP, so they are not checked again
Schedule: The same as Hold with the difference that the job is scheduled to start at the time it was intended to be in SAP.
Start Immediately: The same as Schedule with the difference that SAP CPS attempts to start the job as soon as possible.
Note
Jobs that do not match any of the defined rules are skipped, but not confirmed in SAP, so they are checked at the next synchronization round.
You can restrict job control rules to SAP jobs with the following statuses:
Scheduled (P)
Released (S)
Ready (Y)
Active (R)
Finished (F)
Canceled / Error (A)