Redwood Documentation

Product Documentation

 

›SAP Monitoring

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
← Active XMB MonitoringConnect to an ABAP System via SAProuter →

Active IDoc Monitoring

You monitor IDocs for specific errors by creating a set of registry entries; if an IDoc reports a specified error, the corresponding event will be raised. The raiser comment of the event contains specific IDoc information such as the DocId and MessageId.

You specify the registry entries for IDoc Monitoring as follows:

/configuration/sap/<sap_system>/idoc/monitoring/MessageType/<message_type>/Event/<event>

Where

  • <sap_system> is the name of your SAP system, such as PR1 for example
  • <message_type> is the message type, or message ID, of the IDoc, such as MATMAS for example
  • <event> is the name of your Redwood Server event to raise

You specify the IDoc statuses in the Value field of the <event> registry entry; multiple values are specified comma-separated. The Event registry entry can have more than one <event> child key.

The raiser comment contains the following information:

IDoc: <DocId>/<MessageType>/<status>/<direction>/<receiver_type>/<receiver_port>/<sender_type>/<sender_port>

SAP Tables

  • TEDS1 - IDoc status table
  • EDMSG - Message type table

Example

You specified the following registry entry:

/configuration/sap/PR1/idoc/monitoring/MessageType/MATAMS/Event/IdocEvent = 45, 46, 56, 58

The IDoc 207019 reached status 56, which matches the value of the registry entry. The event IdocEvent is raised with the following raiser comment:

IDoc: 207019/MATMAS/56/I/LS/TSTCLNT200/LS/JCOCLNT200

Prerequisites

  • ProcessServerService.SAP.iDoc license key set to true
  • IDoc transport files

Procedure

Downloading the IDoc Transport Files

  1. Navigate to "Configuration > Software".
  2. Locate the IDoc Transport files, choose Download from the context-menu.
← Active XMB MonitoringConnect to an ABAP System via SAProuter →
  • SAP Tables
  • Example
  • Prerequisites
  • 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 |