Redwood Documentation

Product Documentation

 

›Legacy Systems Support

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
← Enable XBP 2.0 or 3.0 Functionality

Enhanced SAP Interfaces with Redwood Transports

Redwood Server takes advantage of transport files that are installed on the remote SAP System and that enhance the XBP and Industry Solutions (IS) functionality offered by that system. The transport files contain a number of functions that are stored in the Redwood name-space, thus they do not interfere with other functions in the SAP instance. They are used exclusively by Redwood Server.

The following illustrates the enhancements that transport files offer.

  • Faster monitoring (all XBP releases)
  • The standard SAP calls only allow Redwood Server to monitor jobs by doing a full table scan on the SAP job table. In larger systems, this can be quite time consuming. To improve performance, an optimized call is included that allows scanning for jobs changed since the previous scan.
  • Extra print parameters (2.0)
  • Older XBP releases did not allow access to all job print parameters. This extends the functionality found in XBP 2.0 with two new print parameters.
  • Dereleasing jobs (XBP 1.0)
    • Older XBP releases did not allow de-releasing jobs. This closely emulates the functionality found in XBP 2.0.
  • Variant handling (XBP 1.0-2.0)
    • Variant handling has been improved with additional calls in the transport files.
  • Recipients (XBP 1.0 - 2.0)
    • It was not possible to get a list of recipients from an SAP System. Calls have been added to retrieve the list of recipients. Recipients retrieval functionality has been added to XBP 3.0.

When should a transport file be loaded

If one or more of the following conditions are applicable:

  • You want to monitor other SAP jobs in Redwood Server, loading the XBP+ transport file is recommended.
  • You want to intercept SAP jobs, and are running XBP 2.0, loading the XBP+ transport file is recommended.
  • You want to intercept SAP jobs, and are running XBP 1.0, loading the XBP+ transport file is required.
  • You want to start and control mass activity runs on systems prior to ERP 2005S, loading the IS transport file is required.
  • You want Variant handling, and you are running XBP 2.0 or lower, loading the XBP+ transport file is required.
  • You want to work with Recipients, and are running XBP 2.0 or lower, loading the XBP+ transport file is required.
  • You want more flexibility when you switch operation modes

The XBP+ transport files

The XBP+ ("XBP Plus") transport file is delivered by Redwood to supply missing functionality in BC-XBP. Several different versions are available for different SAP releases:

SAP Basis/WAS releaseXBP+Transport files
4.6c-710K000245.DEV, R000245.DEV

The IS transport files

For Industry Solutions (IS) Mass activities, there are currently only two sets of transport files for releases 4.6.4 and 4.7.2:

  • R001520.EC6 and K001520.EC6 - to be used if you are upgrading from a previous version and would like to use mass activities.
  • R000244.DEV and R000244.DEV - for all other cases.
note

These are the names of the transports at the time of this writing, the names change frequently as the transport files are updated.

note

If you have a higher SAP basis version you must contact Redwood Support Services for more information.

Procedure

Loading the transport files

  1. Copy the K**. file to /usr/sap/trans/cofiles directory.
  2. Copy the R**. file to /usr/sap/trans/data directory.
  3. Open Transaction STMS in SAPGUI.
  4. Choose Import Overview and choose the correct Import queue.
  5. Add the request via menu item Extra > Other Requests > Add.
  6. The name of the request is the extension of the K**. file followed by the name. For example, if the transport to be loaded consists of the files R900099.I46 and K900099.I46, the transport request to specify is I46K900090.

Inspecting XBP Settings

  1. Navigate to "Definitions > Processes".
  2. Choose Submit from the context-menu of the process definition SAP_MaintainXbpOptions.
  3. Select the target SAP System, select Show for Interception action and Parent/Child action.
  4. Choose Submit and inspect the output of the corresponding process.

Enabling XBP 2.0 Features

  1. Navigate to "Definitions > Processes".
  2. Choose Submit from the context-menu of the process definition SAP_MaintainXbpOptions.
  3. Select the target SAP System, select Enable for Interception action and Parent/Child action.
  4. Choose Submit and inspect the output of the corresponding process, to verify if the settings were applied.

Enabling XBP 3.0 Features

  1. Navigate to "Definitions > Processes".
  2. Choose Submit from the context-menu of the process definition SAP_MaintainXbpOptions.
  3. Select the target SAP System, select Enable with XBP 3.0 features for Interception action.
  4. Choose Submit and inspect the output of the corresponding process,to verify if the settings were applied.
← Enable XBP 2.0 or 3.0 Functionality
  • Procedure
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 |