Redwood Documentation

Product Documentation

 

›Process Chains

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
← Handling Process ChainsMonitoring Process Chains →

Running Process Chains

A process chain defines a sequence of processes that are scheduled to wait in the background for an event. These processes can trigger a separate event that can, in turn, start other processes. When you monitor a process chain in Redwood Server, the process chain is displayed like a chain.

When a process of a process chain reaches the status Error, you have the possibility to start just the erroneous process, its parent or the parents' parent, see the Restarting Process Chains section for more information.

note

It is not possible to use Redwood Server to balance the load of process chains across SAP application servers. As far as scheduling is concerned, you can only influence the parent job. You can, however, restart certain child jobs.

Sending Spool Files to Financial Closing Cockpit

You can make all output of the process chain available in Financial Closing Cockpit (FCc) by specifying the parameter SAP_APPSAPI_CHAIN_GET_OUTPUT.

This parameter accepts two values:

  • A - to be set on the parent process definition of the process chain; will force all output to be available in FCc.
  • M - to be set on the parent process definition and the child process definition of which you want the output.

Monitoring Process Chains

note

Monitoring Process Chains requires the ProcessServerService.SAP.XBPVariant license key.

You can configure Redwood Server to monitor process chains started from within SAP, they are displayed like chains and allow you to restart them if you meet the prerequisites for restarting process chains.

See Monitoring Process Chains for more information.

Importing Process Chains

You use the following definitions to import process chains:

Process DefinitionUse
SAP_BW_ImportProcessChainsUsed to import process chains, optionally with its definition.
SAP_BW_ImportProcessChainDefinitionUsed to import the definition of an already imported process chain; you run this to update the definition in Redwood Server when the process chain in SAP has been modified.SAP_BW_ImportProcessChains ParametersSAP_BW_ImportProcessChainDefinition Parameters

SAP_BW_ImportProcessChains Parameters

TabParameterDescriptionDirectionData TypeDefault ExpressionValues
ParametersSAP_SYSTEMSSAP SystemInOutString

ParametersPCHAIN_NAMETechnical Name of SAP BW Process ChainInString

ParametersPCHAIN_TEXTDescription of SAP BW Process ChainInString

ParametersMAX_COUNTMaximum CountInNumber

ParametersIMPORT_CHAIN_DEFINITIONImport Process Chain Definition?InStringNY, N
ParametersCREATE_JOBDEFSCreate a Job Definition?InStringNY, N
ParametersDROP_OLD_SELECTIONDrop Old Matching Values?InStringYY, N
ParametersTEST_RUNTest run?InStringNY, N
ParametersCCMS_JOB_DEFINITIONCCMS process definitionInString

ParametersCLIENTTarget Client; the client the process will use.InString

Generation SettingsNAMEName of Generated Job DefinitionInString

Generation SettingsJOBNAME_GENERATIONUse name asInString

Generation SettingsAPPLICATIONApplicationInString

Generation SettingsPARTITIONPartitionInString

Generation SettingsOVERWRITEOverwrite Existing Job Definitions?InStringYY, N
Generation SettingsCHAIN_RESTARTABLEMake Processes Restartable If Errors Occur?InStringFF (Failed) A (All) N (Not restartable)
Generation SettingsSYNCHRONOUSSynchronous Run?InStringNY, N
Generation SettingsSIMULATESimulate Run?InStringNY, N
Generation SettingsNOPLANNo Plan?InStringNY, N
Job Output ParametersSHOWLOGRetrieve Job Log?InStringYY, N
Job Output ParametersSHOWSPOOLRetrieve Spool Lists?InStringYY, N
Job Output ParametersSHOWAPPLLOGRetrieve Application Logs?InStringNY, N
Job Output ParametersIGNORE_APPL_RCIgnore Application Return Code?InStringYY - Ignore return code N - Use system default U - Use return code

SAP_BW_ImportProcessChainDefinition Parameters

ParameterDescriptionDirectionData TypeDefault ExpressionValues
SAP_SYSTEMSSAP SystemInString

PCHAIN_NAMETechnical name of the SAP BW Process ChainInString

DROP_OLD_SELECTIONDrop old selection?InStringYY, N

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.

Example

You wish to retrieve the spool in PDF, XLSX, and Text. You set the FL_SHOWSPOOL parameter to PDF;XLSX;Text.

You wish to retrieve the application log in PDF and Text. You set the FL_SHOWAPPLOG to PDF;Text.

You wish to retrieve the application log entries in PDF and XLS format for External ID``12345678910, Object set to ZBO, Program set to ZBO_VALPO, furthermore, you want the entire application log in text. You set FL_SHOWAPPLOG to PDF:ZBO,,12345678910,ZBO_VALPO;XLS:ZBO,,12345678910,ZBO_VALPO;Text.

Restarting Process Chains

note

Monitoring Process Chains requires the ProcessServerService.SAP.XBPVariant license key.

The following process definitions allow you to start, represent and restart process chains in your BI or BW system.

Process DefinitionUse
SAP_BW_ProcessRepresents a process chain
SAP_BW_ProcessChainRunUsed to start a process chain
SAP_CcmsJobRepresents a process chain process

See Restarting Process Chains for more information.

Starting Process Chains with Direct Scheduling in SAP

When you want to schedule process chains in Redwood Server which have Direct Scheduling in SAP enabled, make sure the option Immediate start is selected. If the Date/Time is selected and if the time is in the past, the start of the chain will fail. Note that it will also fail if you try to start it from SAPGui. You need to change the process chains to use either the Start Immediate option or change them to Start Using Meta Chain or API.

Transient Errors

By default, Redwood Server will put processes that return an error into status Error; Redwood Server has no means to determine if an error is transient or not.

The IgnoreError registry entry has been introduced to allow you to specify a list of errors that Redwood Server will ignore while the job is active in the SAP system.

Prerequisites

  • An RFC connection has been established between the central Redwood Server and a BI or BW system, as outlined in Connecting to SAP Systems.

Procedure

Import Process Chains from your remote SAP system

  1. Navigate to "Definitions > Processes".
  2. Choose Submit from the context-menu of process definition SAP_BW_ImportProcessChains.
  3. Select the BI or BW SAP system to import the process chains from.
  4. Specify the technical name or description of the process chain to import in the Technical Name of SAP BW Process Chain (PCHAIN_NAME) or Description of SAP BW Process Chain (PCHAIN_TEXT) parameters, respectively; leaving these fields empty will import all process chains.
  5. Specify any other parameters, as required.
tip

If you do not want to import all process chains and do not know the exact technical name or description of a process chain, submit the import with the Technical Name and Description parameters empty and Test Run set to Yes; you will find all process chains in the output of the import process definition. Since you performed a Test Run, no process chains will have been imported.

Start a BW process chain

  1. Navigate to "Definitions > Processes".
  2. Choose Submit from the context-menu of process definition SAP_BW_ProcessChainRun.
  3. Select the SAP System name of the BW system in the SAP System parameter.
  4. Select the process chain to start.
  5. Choose Submit to schedule the job.

Example

The following examples use an SAP BW system named BSP and a process chain named EXAMPLE_PCHAIN to illustrate importing and running a process chain. Note that a process chain must first be imported before it can be run.

Import Process Chain EXAMPLE_PCHAIN, with its definition, from SAP system BSP

  1. Navigate to "Definitions > Processes".
  2. Choose Submit from the context-menu of process definition SAP_BW_ImportProcessChains.
  3. Select BSP from the SAP System.
  4. Fill EXAMPLE_PCHAIN into the Technical Name of SAP BW Process Chain (PCHAIN_NAME) parameter.
  5. Select Yes for parameter Import Process Chain Definition? (IMPORT_CHAIN_DEFINITION).
  6. Select Yes for parameter Test Run? (TEST_RUN).
  7. Choose Submit Summary on the left-hand side, select Monitor process definition 1234 (you will most certainly have a different process definition ID than 1234); choose Submit.
  8. Once the process has reached status Completed, inspect its stdout.log file.
  9. The output file must contain: Importing process chain EXAMPLE_PCHAIN, this indicates that it would have imported the requested process chain.
  10. The output file must contain: Generating job definition EXAMPLE_PCHAIN for process chain EXAMPLE_PCHAIN, this indicates that it would have imported the definition of the requested process chain.
  11. Resubmit the process, set the Test Run? parameter to No this time.

Start BW process chain EXAMPLE_PCHAIN on SAP system BSP

  1. Navigate to "Definitions > Processes".
  2. Choose Submit from the context-menu of process definition SAP_BW_ProcessChainRun.
  3. Select BSP in the SAP System parameter.
  4. Select EXAMPLE_PCHAIN in the Technical Name of SAP BW Process Chain (NAME) parameter.
  5. Choose Submit.
tip

When you set the parameter Create a Definition? (CREATE_JOBDEFS) to Yes on SAP_BW_ImportProcessChains during import, a process definition will be created in Redwood Server for that process chain. You submit this directly instead of using process definition SAP_BW_ProcessChainRun and having to fill in all the parameters.

See Also

  • Importing Process Chains
  • Importing Process Chain Definitions
  • Handling Process Chains
  • Monitoring Process Chains
  • Restarting Process Chains
← Handling Process ChainsMonitoring Process Chains →
  • Sending Spool Files to Financial Closing Cockpit
    • Monitoring Process Chains
  • Importing Process Chains
    • SAP_BW_ImportProcessChains Parameters
    • SAP_BW_ImportProcessChainDefinition Parameters
    • Custom CCMS Definition
  • Retrieving Spool Output, Logs, and Application Logs in Other Formats
    • Example
  • Restarting Process Chains
  • Starting Process Chains with Direct Scheduling in SAP
  • Transient Errors
  • Prerequisites
  • Procedure
    • Import Process Chains from your remote SAP system
    • Start a BW process chain
  • Example
    • Import Process Chain EXAMPLE_PCHAIN, with its definition, from SAP system BSP
    • Start BW process chain EXAMPLE_PCHAIN on SAP system BSP
  • 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 |