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
← Maintaining Variants AutomaticallyUsing Temporary Variants →

Maintaining Variants Automatically (Advanced)

You can create a RedwoodScript process definition to change one or more values of a variant directly, without the need to manually edit the variant. In the script you modify the values for the variants with legal values and then submit process definition SAP_StoreVariant to save the variant in the SAP System. This is especially useful when you want to have dynamic variants, for instance, a parameter that would contain the current date. With Redwood Server, this is easily implemented, as you could schedule a process daily which changes the parameter value of the variant and fills it with the current date.

note

XBP 3.0 requires a logical system for the client, see Setting Up Logical Systems for more information on creating logical systems for clients.

See Creating and Modifying Variants for step-by-step instructions on how to modify variants using the Redwood Server user interface and the syntax to specify parameters and select options.

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.

Additionally, the SAP System must have one of the following:

  • XBP 3.0 support
  • The Redwood transport files must have been installed

Example

The below example shows how to change the FLDATE select option of the KL variant of ABAP program BALVEX01 in SAP System D00.

note

The below example does not include the submit of process definition SAP_StoreVariant, which can be done in RedwoodScript or in a following step of the chain.

{
// get the SAP System D00
SAPSystem sapSystem = jcsSession.getSAPSystemByName("D00");

// ABAP program BALVEX01
SAPAbapProgram abap = sapSystem.getSAPAbapProgramByName("BALVEX01");

// variant KL in client 200
SAPAbapProgramVariant variant = abap.getSAPAbapVariantByNameClientNumber("KL", "200");

// values of the select option FLDATE
Iterator<String> it = variant.getSAPAbapVariantSeloptByName("FLDATE").getSAPAbapVariantSeloptValues();
if(it.hasNext())
{
  // set the value of the first one to the current date
  String fldate = it.next();
  fldate.setLow(Time.now().toyyyyMMDDString());

  // persist our change
  jcsSession.persist();
}
}

See Also

  • Importing Variants
  • Importing Variant Definitions
  • Maintaining Variants Manually
  • Maintaining Variants Automatically
← Maintaining Variants AutomaticallyUsing Temporary Variants →
  • Prerequisites
  • Example
  • 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 |