Redwood Documentation

Product Documentation

 

›Configuration

RunMyJobsSAP Connector

Introduction

  • The SAP Connector
  • HANA Platforms

Configuration

  • Configuring the Central and Satellite Systems
  • Installing SAP JCo
  • Configuring an SAP System for Process Automation
  • SAP RFC User Privileges
  • Assigning SAP Authorizations to the RFC User
  • Connecting to SAP Systems
  • Connecting to SAP Systems with the Wizard
  • Connection Details for the ABAP Stack
  • Intercepting SAP Jobs
  • SAP Job Interception Configuration
  • Interacting with SAP Events
  • Configuration Details on Interacting with SAP Events
  • Parsing Log Files to set Status of SAP Jobs
  • Understanding the Different XBP Interface Releases

Importing SAP Objects

  • Importing Objects from SAP Systems
  • Importing ABAP Programs
  • Importing ABAP Program Parameter Definitions
  • Importing Archive Objects
  • Importing Batch Events
  • Importing SAP BusinessObjects Processes
  • Importing SAP Calendars
  • Importing SAP CCMS Jobs
  • Importing Communication Channels via PI/XI
  • Importing External Commands
  • Importing and Running Mass Activities
  • Importing Output Devices
  • Importing Process Chains
  • Importing Process Chain Definitions
  • Importing Recipients
  • Importing Variants
  • Importing Variant Definitions

SAP ABAP

  • Handling ABAP Programs
  • Controlling Batch Input Sessions
  • Handling Variants
  • Creating and Modifying Variants in Redwood Server
  • Maintaining Variants Manually
  • Maintaining Variants Automatically
  • Maintaining Variants Automatically (Advanced)
  • Using Temporary Variants
  • Default SAP Process Definitions

Business Objects

  • Main
  • Interface Configuration
  • Crystal Reports
  • Web Intelligence
  • Data Services
  • Triggering Events
  • Crystal Reports REST
  • Web Intelligence REST

Process Chains

  • Handling Process Chains
  • Running Process Chains
  • Monitoring Process Chains
  • Restarting Process Chains

SAP PI/XI

  • SAP Communication Channels with PI/XI
  • Controlling Communication Channels with Redwood Server via PI/XI

Adaptive Computing

  • SAP Adaptive Computing
  • Controlling SAP Adaptive Computing

SAP Monitoring

  • Integrating SAP Monitors
  • Configuration Details for Integrating SAP Monitors
  • Sending Monitoring Data to SAP Systems
  • Configuration Details for Sending Monitoring Data to SAP Systems
  • Monitoring Redwood Server Availability in CEN
  • Active XMB Monitoring
  • Active IDoc Monitoring

Advanced Configuration

  • Connect to an ABAP System via SAProuter
  • SNC connection to an SAP System
  • The SAP Cryptographic Library
  • Tuning Redwood Server

Legacy Systems Support

  • Enable XBP 2.0 or 3.0 Functionality
  • Enhanced SAP Interfaces with Redwood Transports
← Intercepting SAP JobsInteracting with SAP Events →

SAP 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.

tip

You can check all job control rules that use a specific default queue across all SAP systems in the Related Objects list of the queue in question.

note

When you want to retrieve spool files, you should ensure that you have not disabled or restricted spool retrieval with the process server parameter SAP_MaxSpoolSize.

Setting up connection information

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.

Setting up the job handling information

TabFieldDescription
XBP Job Control RulesJob HandlingReports the setting of the Job Handling field on the SAP System tab.
XBP Job Control RulesEnabledAllows you to disable rules, preserving the settings for future use.
XBP Job Control RulesDescriptionThe description to use for this rule. Limited to 255 characters, any printable UTF-8 character combination is allowed, your browser might not be able to render all characters. 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 RulesProcessing orderOrder in which to process this rule. Rules are processed in ascending order according to the integer you specify here, the first rule that matches wins. The rule with the lowest processing order is processed first.
XBP Job Control RulesActionDefines how to handle the job. Please see the list below for available actions.
XBP Job Control RulesClient Number MaskSAP client pattern that is used to match jobs. Limited to 3 characters, accepts ? and * wildcards, see below.
XBP Job Control RulesJob Name MaskJob name pattern that is used to match jobs. Limited to 255 characters, accepts ? and * wildcards, see below.
XBP Job Control RulesUsername MaskUser name pattern that is used to match jobs. Limited to 255 characters, accepts ? and * wildcards, see below.
XBP Job Control RulesJob class (A, B, C)The SAP job class.
XBP Job Control RulesDefault QueueQueue the job should be put on. This field allows you to choose a queue from the list of queues.
XBP Job Control RulesCcms Process DefinitionThe process definition to use as SAP_CcmsJob alternative.
XBP Job Control RulesTarget ServerForce the SAP job to run on a specific SAP application server. This field allows you to select an application server from the list of application servers.
XBP Job Control RulesTarget Server GroupForce the SAP job to run in a specific. This filed allows you to select a target server group from all target server groups on the SAP system.
XBP Job Control RulesPriorityPriority of the process in Redwood Server.
XBP Job Control RulesRetrieve Job logShould the log of the job be retrieved?
XBP Job Control RulesRetrieve SpoolShould the output file of the job be retrieved?
XBP Job Control RulesRetrieve Application LogShould the application log file be retrieved?
XBP Job Control RulesIgnore Application Return CodeIgnore the return code as returned by the SAP system.
XBP Job Control RulesApplies to jobs in SAP statusYou 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 PROCESS_* would match PROCESS_ABAP and PROCESS_OR but not BI_PROCESS_TRIGGER.
  • ? to match a single character, for example RSUSR?00 would match RSUSR200 and RSUSR400.
note

Due to limitations in SAP BI, you should not intercept processes starting with BI_PROCESS, the only exception is BI_PROCESS_TRIGGER.

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.

Actions

The following actions are available:

ActionDescriptionInterception
MonitorA reference to the job is created in Redwood Server. The status of the SAP job can be monitored in the job monitor of Redwood Server.N/A
HoldA reference to the job is created in Redwood Server. 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 Redwood Server.Redwood Interception
IgnoreJobs that match this rule are confirmed in SAP, so they are not checked again, and ignored (no reference to the job is created in Redwood Server).N/A
ScheduleA reference to the job is created in Redwood Server. 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). The job is scheduled to start in Redwood Server at the time it was intended to be in SAP.Redwood Interception
Start ImmediatelyA reference to the job is created in Redwood Server. 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 Redwood Server attempts to start the job as soon as possible.Redwood Interception
Schedule InterceptedJobs that have been intercepted by the SAP system are scheduled in Redwood Server.SAP Interception

Status

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)

Custom CCMS Definition

You duplicate the SAP_CcmsJob process definition and customize the new definition to suit your needs. Note that you should not delete the SAP Job Name and SAP Job Count parameters, these are required.

You add additional parameters, control how the process files are retrieved and in which format, and/or add RedwoodScript actions to the definition.

Retrieving Spool Output, Logs, and Application Logs in Other Formats

The FL_SHOWSPOOL, FL_SHOWLOG, and FL_SHOWAPPLLOG parameters override the standard SHOWSPOOL, SHOWLOG, and SHOWAPPLLOG parameters, respectively. The EnableFLParameters registry entry allows you to enable or disable these parameters (defaults to true, enabled ). The available formats depend on the version of the target AS ABAP; see Spool Output for more information.

See Also

SAP Systems

← Intercepting SAP JobsInteracting with SAP Events →
  • Setting up connection information
  • Setting up the job handling information
    • Actions
    • Status
    • Custom CCMS Definition
  • Retrieving Spool Output, Logs, and Application Logs in Other Formats
  • See Also
Docs
Getting StartedInstallationFinance InstallationConcepts
TroubleshootingArchiving
Learn and Connect
Support Portal
BlogEventsResources
ISO/ IEC 27001 Information Security Management
Automate to be human

2023 All Rights Reserved |

Terms of Service | Policies | Cookies | Glossary | Third-party Software | Contact | Copyright | Impressum |