ABAP Event Consumption via Automatic RAP Event Generation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Manually creating event providers and consumers for high-level business programming languages like ABAP is a time-consuming and error-prone task, especially when dealing with a substantial number of events or applications.

Innovation Solution

A framework automatically transforms behavior definitions of a Representational State Transfer (RAP) model into producer events using a cloud event standardized format and parses event specifications into high-level programming language structures, facilitating efficient event processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If event providers and consumers are manually created for high-level business programming languages, then system flexibility and customizability are improved, but development time and error rate increase significantly

Engineering Contradiction:
Improvesystem flexibilityVSAvoiddevelopment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The system enables self-service by allowing the event framework to automatically generate event providers and consumers from behavior definitions without requiring manual programming. The framework introspects the RAP model behavior definitions and autonomously creates the necessary event handling code, eliminating the need for developers to manually write event provider and consumer implementations while maintaining system flexibility.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The framework performs preliminary action by pre-configuring event bindings between behavior definitions and event handlers during system initialization or model definition phase. This allows the event architecture to be prepared in advance, so that when events occur, the providers and consumers are already in place and configured, eliminating the need for manual setup during deployment or operation.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If event providers and consumers are manually created, then event handling precision is improved, but reliability decreases due to human errors

Engineering Contradiction:
Improveevent handling precisionVSAvoidsystem reliability
Core Design Contradiction:
Measurement precisionVSReliability

Solution Approach 1:

The system eliminates human error by using the framework to automatically generate event handling code from behavior definitions. The automated generation ensures consistency between the defined behavior and the implemented event handling logic, removing variability and errors introduced by manual programming while maintaining precise event handling through the structured RAP model definitions.

Inventive Principle:
Principle #25Self-service

3Productivity

If automatic transformation of behavior definitions into producer events is implemented, then productivity is improved, but system complexity increases

Engineering Contradiction:
Improveevent processing efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The framework acts as an intermediary layer between the RAP model behavior definitions and the event-driven architecture. This mediator automatically transforms behavior definitions into producer events, handling the complexity of event generation, binding, and dispatch internally. The intermediary absorbs the system complexity, presenting a simple interface to developers while managing the intricate transformations and coordination required for efficient event processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS12367014B2Event consumption for high-level programing language platform
Publication Date: 2025.07.22 SAP SE
  • US12367014B2 patent drawing
  • US12367014B2 patent drawing
  • US12367014B2 patent drawing

AI summary

Embodiments may facilitate event processing for an ABAP platform. A business object data store may include a RAP model, including a behavior definition, for a business object. A framework may automatically transform the behavior definition of the RAP model into a producer event via an event binding and a cloud event standardized format. Information about the producer event may then be passed to an ABAP application associated with a pre-configured destination at an enterprise business technology platform. In some embodiments, a standalone API enterprise hub data store may contain an event specification. An ABAP development tenant of a business technology platform may automatically parse the event specification and translate the parsed information into high-level programming language structures that reflect an event type at runtime. An event consumption model may then be generated based on the event type.