Business Eventing Toolkit for SAP overview

The Business Eventing Toolkit for SAP provides event-driven integration between SAP and Google Cloud, enabling you publish your SAP events to Google Cloud. By publishing your SAP events to Google Cloud, you can maximize the value of your SAP events, such as:

The Business Eventing Toolkit for SAP facilitates the integration of business systems by offering flexible event publishing:

  • Publish events as CloudEvents: To ensure consistent event handling and integration across different systems, the toolkit supports the CloudEvents 1.0 specification, an open standard for event data. Google Cloud services such as Cloud Run functions, Pub/Sub, and Firebase Cloud Messaging use the CloudEvents 1.0 specification. This enables efficient communication between SAP systems and Google Cloud services. The toolkit supports publishing your events in both structured encoding and binary encoding.

  • Publish events as regular JSON: To enable data exchange and integration between systems where CloudEvents compliance is not required, the toolkit supports publishing events in standard JSON format.

The Business Eventing Toolkit for SAP is shipped as a subpackage of the on-premises or any cloud edition of ABAP SDK for Google Cloud. To use the toolkit, you need to install the latest version of the SDK in your SAP environment. For information about the installation steps, see Install and configure the on-premises or any cloud edition of ABAP SDK for Google Cloud.

The Business Eventing Toolkit for SAP is only available with the on-premises or any cloud edition of ABAP SDK for Google Cloud.

This document is intended for ABAP developers, SAP solution architects, and cloud architects. It assumes that you're familiar with the ABAP SDK for Google Cloud and CloudEvents Notations and Terminology.

Key capabilities

The following list highlights the key capabilities of the Business Eventing Toolkit for SAP:

  • Publish SAP events to Google Cloud: Capture SAP standard events such as BOR events, change documents, and IDOCs, and publish them to Google Cloud with minimal configuration.

  • CloudEvents 1.0 encoding and decoding: Encode and decode API requests according to the CloudEvents 1.0 specification.

  • Configure multiple Google Cloud services as targets: Configure to publish events to multiple target Google Cloud services, including Cloud Run functions, Pub/Sub, Firebase Cloud Messaging (FCM), and Integration Connectors.

  • Extend event-driven integration: Extend event-driven integration to other Google Cloud targets and third-party systems.

Key components

The toolkit has the following main components:

CloudEvents module

The CloudEvents module handles the encoding and decoding of CloudEvents using both structured and binary encodings. In structured encoding, the module serializes CloudEvent attributes and data into a single JSON-formatted payload. In binary encoding, CloudEvent attributes are mapped to transport-specific headers, and the data payload is transmitted directly.

The CloudEvents module lets you configure default values for CloudEvent attributes to standardize how your event messages are encoded and decoded. By predefining attribute values, you can streamline event processing and integration with downstream systems, regardless of whether you're using structured or binary encoding.

The CloudEvent attribute values are stored against a unique CloudEvent Default Attribute Key in the CloudEvents module. As an ABAP developer, for sending a business event to Google Cloud, you use the ENCODE_AS_CLOUD_EVENT method within the Google Cloud API stub to pass the CloudEvent Default Attribute Key and optionally supply extension attribute values. This method retrieves CloudEvent attributes from the configuration and publishes the event as a CloudEvent with those attributes.

To override the default values defined in the configuration, when you publish an event as a CloudEvent, you can pass specific values for CloudEvent attributes in your code.

Publisher module

The Publisher module contains routing rules and an event publisher that reads the routing rules and sends event data to the target endpoint.

The Publisher module includes prebuilt targets for the following Google Cloud services:

  • Pub/Sub: Enables publishing SAP events to Pub/Sub topics for asynchronous processing.
  • Cloud Run functions: Enables triggering serverless functions in response to SAP events.
  • Firebase Cloud Messaging (FCM): Enables sending push notifications to mobile devices based on SAP events.
  • Integration Connectors: Enables sending events to the Integration Connectors API.

SAP event listeners

The SAP event listeners capture any SAP events within your SAP system, such as changes to business objects or incoming data. You can integrate these listeners directly into your standard SAP transactions, including enhancement points for custom logic. This lets you send these SAP events to Google Cloud, enabling real-time integration.

The Business Eventing Toolkit for SAP supports capturing various SAP events, including the following::

  • BOR events: Events triggered by changes to SAP business objects. For example, a "customer created" or "sales order changed" event.
  • RAP events: Events raised within modern SAP cloud applications built with the RESTful ABAP programming model.
  • Change documents: Records of data changes within SAP, providing an audit trail. Whenever a field in a database table is modified, a change document is created, capturing the old and new values.
  • IDOC events: Events triggered when SAP receives data from external systems or sends data to external systems through IDOCs.

Pricing

The Business Eventing Toolkit for SAP is offered at no cost. However, you're responsible for the charges incurred from your use of Google Cloud services. To get a cost estimate, see the Pricing calculator.

What's next