Sap Se

Arne Rantzen

Tatjana Pfeifer

Raphael Dibbern

Jens Roessler

Jonas Braun

Silvana Straus

Andre Pany

Martin Mueller

Roland Trapp

Thomas Ehret

Nadine Baumgaertel

Vanessa Rau

Ihlas Basha

Jes Sie Cheah

Roman Belosludtsev

In an example embodiment, multiple different categories of events from an Enterprise application are separated and processed by different daemons. This allows events of a first category, such as business events, to be processed separately from events of a second category, such as configuration events. This provides the benefits of stable event processing, additional monitoring functionality, and specialized error handling.

Manage daemon for event reconciliation in a computer system

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.

Event consumption for high-level programing language platform

Event provisioning for high-level programing language platform

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 vian 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.

Growing community of inventors

Ketsch, Germany

Arne Rantzen