Redwood Documentation

Product Documentation

 

›SAP ABAP

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 VariantsMaintaining Variants Manually →

Creating and Modifying Variants in Redwood Server

Variants are sets of parameter values used for quickly setting ABAP program parameters. You can create and modify variants from within Redwood Server in the SAP System Maintain Objects editor screen.

Creating Variants

First you import the ABAP program, then you can create variants. You create variants on the ABAP program and set a number of parameters. You should import at least one variant and its variant definition, so that the available parameters are displayed in drop-down menus. This is done with the SAP_ImportVariants process definition, not that it will by default import the variant definition as well. Variant definitions are the set of parameters and their respective values as defined in the variant.

Editing Variants

To be able to edit variants that were created in SAPGui, you will have to import the variants and variant definitions first. When you use SAP_ImportVariants to import variants, the process will import the variant and its variant definition by default. Variant definitions are the set of parameters and their respective values as defined in the variant.

Saving a Variant in the SAP System for use with SAPGui

You can use the SAP_StoreVariant process definition to store variants in you SAP system, see Handling Variants for more information.

Variant Parameter Syntax

Variant parameters should be string parameters, with PAR_, SEL_, or FSL_ prefixes, for parameter, select options, and free selections (freie Abgrenzungen in German), respectively. Their names should contain the name of the parameter/select option in SAP for parameters and selection options; free selections must be specified as FSL_<table>/<field>, where <table> and <field> are the technical names of the table and field, respectively. When you want to specify a range, you should enclose it in square brackets [], as in [a-m,!d,!f,!g]. These parameter names must be all upper case.

The following operators are available for select options, the mathematical syntax can only be used in RedwoodScript and is displayed here for clarity:

SyntaxMeaningMathematical Syntax
NOTNot!
EQEquals=
BTBetween-
CPContains Pattern, use + for one character and * for zero or more characters

NENot Equals!=
NENot Equals<>
NPNot Pattern

GEGreater than or equals>=
GTGreater than>
LELess than or equals<=
LTLess than<
note

When you specify date-ranges, make sure you put spaces between the dates and the hyphen (-), the range 21.02.2010 - 31.12.2010 is valid and this one is not valid:21.02.2010-31.12.2010.

tip

If you want to specify two or more exact values, you can create a parameter for each select option.

Example

You have a process definition with the following parameters:

  • PAR_NOEX - Without Extract, set to X
  • SEL_FLDATE - Flight Date, set to BT and 21.02.2010 - 31.12.2010

Another example of a process definition with parameters:

  • PAR_NOEX - Without Extract, set to X
  • SEL_CAR - Airline, set to BT and [AA-ZZ, !BC, !AF]

Alternate example of process definition with parameters:

  • PAR_NOEX - Without Extract, set to X
  • SEL_CAR - Airline, set to CP and L+
  • SEL_FLDATE_01 - Flight Date, set to GE and 01.02.2010
  • SEL_FLDATE_02 - Flight Date, set to LE and 18.02.2010

Free selections example:

  • FSL_BSID/MANSP - set to BT and [AA-CA, !BC, !AF]

Handling Empty/Missing Variant Parameters

You use the PASSNULLVALUES parameter to specify how you want empty/missing parameters to be interpreted. The parameter accepts the following values:

  • N - missing parameters are ignored, the SAP variant parameter/selopt default values will be used; empty parameters are passed on as is, variant parameter/selopt is empty (but set).
  • Y - missing parameters cause the corresponding SAP variant parameters/selopts to be unset; empty parameters are passed on as is, variant parameter/selopt is empty (but set).

To unset an existing parameter, specify >!<; Parameters with this value are not forwarded to the SAP system.

Prerequisites

  • You have imported the ABAP program, a variant and its variant definition, as outlined in Importing ABAP Programs and Importing Variants.

Procedure

Create a variant

  1. Navigate to "Environment > SAP".
  2. Choose Maintain Objects from the context-menu of the SAP System that represents the SAP Instance where the ABAP program is used.
  3. Expand ABAP Programs and choose New Variant from the context-menu of the ABAP program.
  4. Fill in a name and optional description, choose Save.
  5. For each simple parameter/value combination, choose New Parameter.
  6. Select the name of the parameter from the drop-down, enter an optional description and value.
  7. For each select option, choose New Select Option.
  8. Select the name of the parameter from the drop-down, enter an optional description.
  9. On the Values tab, select to include or exclude the rows in the Sign field, select and operator in the Option field, and enter a lower and higher value (depending on the operator in Option, only a lower value is required).
  10. Choose Save & Close.

Modify a variant

  1. Navigate to "Environment > SAP".
  2. Choose Maintain Objects from the context-menu of the SAP System that represents the SAP Instance where the ABAP program is used.
  3. Expand ABAP Programs, the ABAP program, client and variant.
  4. Select the parameter you want to change.
  5. For each simple parameter/value combination".
  6. Select the name of the parameter and enter a value into the Value field.
  7. For each select option:
  8. Select the name of the parameter.
  9. On the Values tab, select to include or exclude the rows in the Sign field, select and operator in the Option field, and enter a lower and higher value (depending on the operator in Option, only a lower value is required).
  10. Choose Save & Close.

See Also

  • Handling Variants
  • Creating and Modifying Variants
  • Maintaining Variants Manually
  • Maintaining Variants Automatically
  • Maintaining Variants Automatically (Advanced)
← Handling VariantsMaintaining Variants Manually →
  • Creating Variants
  • Editing Variants
  • Saving a Variant in the SAP System for use with SAPGui
  • Variant Parameter Syntax
  • Example
  • Handling Empty/Missing Variant Parameters
  • Prerequisites
  • Procedure
  • 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 |