Event consumption for high-level programing language platform

Patent metadata

Field	Value
Publication number	US-12367014-B2
Application number	US-202418615272-A
Country	US
Kind code	B2
Filing date	Mar 25, 2024
Priority date	Jul 26, 2022
Publication date	Jul 22, 2025
Grant date	Jul 22, 2025

Abstract

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.

First claim

The invention claimed is:

1. A system to facilitate event processing for a high-level programing language platform, comprising:
an Application Programming Interface (“API”) enterprise hub data store containing electronic records that include an event specification; and
a high-level programming language development tenant of a business technology platform, coupled to the API enterprise hub data store, including:
a computer processor, and
a memory storage device, coupled to the computer processor, including instructions that, when executed by the computer processor, enable the high-level programming language development tenant to:
(i) access, from the API enterprise hub data store, the event specification, wherein the event specification comprises a JavaScript Object Notation (“JSON”) file,
(ii) automatically parse the JSON file,
(iii) translate the parsed information into high-level programming language structures that reflect an event type at runtime, and
(iv) generate an event consumption model based on the event type.

2. The system of claim 1 , wherein the high-level programming language comprises an Advanced Enterprise application Programming (“ABAP”) language.

3. The system of claim 2 , wherein the JSON file comprises an AsyncAPI specification.

4. The system of claim 3 , wherein a simple transformation is performed on the JSON file to create an ABAP readable representation associated with elements of an abstract entity.

5. The system of claim 4 , wherein at least one of the elements of the abstract entity is a primitive element or a primitive element collection.

6. The system of claim 4 , wherein at least one of the elements of the abstract entity is a complex element or a complex element collection.

7. The system of claim 4 , wherein a new behavior definition contains names of all connected abstract entities and hierarchical information.

8. The system of claim 4 , wherein an extension component standard library is utilized to generate abstract entities.

9. The system of claim 4 , wherein the AsyncAPI specification defines channels and components, a payload, and message traits associated with an event.

10. The system of claim 9 , wherein the AsyncAPI specification further defines a payload and message traits associated with the event.

11. A computer-implemented method to facilitate event processing for a high-level programing language platform, comprising:
accessing, by a high-level programming language development tenant of a business technology platform from an Application Programming Interface (“API”) enterprise hub data store, an event specification, wherein the API enterprise hub data store contains electronic records that include the event specification, and the event specification comprises a JavaScript Object Notation (“JSON”) file;
automatically parsing the JSON file;
translating the parsed information into high-level programming language structures that reflect an event type at runtime; and
generating an event consumption model based on the event type.

12. The method of claim 11 , wherein the high-level programming language comprises an Advanced Enterprise application Programming (“ABAP”) language.

13. The method of claim 12 , wherein the JSON file comprises an AsyncAPI specification.

14. The method of claim 13 , wherein a simple transformation is performed on the JSON file to create an ABAP readable representation associated with elements of an abstract entity.

15. The method of claim 14 , wherein at least one of the elements of the abstract entity is a primitive element or a primitive element collection.

16. The method of claim 14 , wherein at least one of the elements of the abstract entity is a complex element or a complex element collection.

17. A non-transitory, computer readable medium having executable instructions stored therein to perform a method to facilitate event processing for a high-level programing language platform, the method comprising:
accessing, by a high-level programming language development tenant of a business technology platform from an Application Programming Interface (“API”) enterprise hub data store, an event specification, wherein the API enterprise hub data store contains electronic records that include the event specification, and the event specification comprises a JavaScript Object Notation (“JSON”) file;
automatically parsing the JSON file;
translating the parsed information into high-level programming language structures that reflect an event type at runtime; and
generating an event consumption model based on the event type.

18. The medium of claim 17 , wherein the high-level programming language comprises an Advanced Enterprise application Programming (“ABAP”) language, the JSON file comprises an AsyncAPI specification, and a simple transformation is performed on the JSON file to create an ABAP readable representation associated with elements of an abstract entity.

19. The medium of claim 18 , wherein a new behavior definition contains names of all connected abstract entities and hierarchical information.

20. The medium of claim 18 , wherein an extension component standard library is utilized to generate abstract entities.

21. The medium of claim 18 , wherein the AsyncAPI specification defines channels and components, a payload, and message traits associated with an event.

22. The medium of claim 21 , wherein the AsyncAPI specification further defines a payload and message traits associated with the event.

Assignees

• Sap Se

Inventors

• Pfeifer Tatjana
• Dibbern Raphael
• Braun Jonas
• Roessler Jens
• Rantzen Arne
• Straus Silvana

Classifications

• G06F8/31

  Programming languages or programming paradigms · CPC title

• G06F9/542

  Event management; Broadcasting; Multicasting; Notifications · CPC title

• G06F9/547

  Remote procedure calls [RPC]; Web services · CPC title

• G06F8/51

  Source to source · CPC title

• G06F8/36

  Software reuse · CPC title