Sap Se

Sap Ag

Daniel Buchmann

Michael Zoeller

Timm Falter

Thomas Mueller

Florian Kresser

Uwe Pyka

Gerd Ritter

Gunther Stuhec

Renzo Colle

Michael Seubert

Paola Sala

Stephan Hetzer

Uwe E Fischer

Werner Gnan

Ralf Dentzer

Andreas Balzar

Joachim Kenntner

Thilo Kraehmer

Johann Kemmer

Gregor Rieken

Markus A Peter

Toralf Grossmann

Tao Yu

Thomas Nitschke

Andreas Bold

Georg Podhajsky

Andre Wagner

Andreas Brossler

Wolfgang Nieswand

Antonia Gross

Matthias Schmitt

Markus Biehler

Thomas Maag

Hans-Martin Ludwig

Ralf Sievers

Rudolf Winkel

Andreas F Morsch

Otto Makris

Frank Michels

Christoph Lehner

Stefan Elfner

Volker Jaeck

Thomas Finke

Jochen A Rasch

Axel Kuehl

Karsten Koetter

Corinne Kuster

Ruediger Radcke

Daniela Schapler

Andreas Schneider

Frank Thome

Dagmar Schultze

Joerg Hendricks

Wolf Hengevoss

Christine Hofmann

Bernhard Kelnberger

Dominic Poetschke

Jens Zachmann

Theo Zimmerman

Gabriel Alvarez

Gerhard Gschwender

Dietmar Nowotny

Daniel Bock

Karl Fuerst

Arnulf Schueler

Robert Doerner

Stefan Adelmann

Stefan Franke

Volker Ripp

Renato Zadro

Adam Kiwon

Werner Liebold

Jochen Hoenig

Oliver Scheerer

Reiner Seyler

Bernhard P Waldscheck

Christof Bornhoevd

Wolfgang Kalthoff

Marcus Paradies

Sebastian Droll

Michael Rudolf

Marco Pesarese

Thomas Seufert

Simon Heimler

Gerd Moser

Ralf Helmut Philipp

Selcuk Imal

Bernd Krannich

Frank Reinemuth

Marieta Koch

Patrick Gross

Armulf Schueler

Wolfgang Wiese

Harald Bender

Jochen Hönig

Uwe Pyke

Waldemar Porscha

Laurent Pommier

Matthias Heitmann

Christian Münkel

The present disclosure relates to techniques for automatically generating new data objects from user input. The system receives user input comprising a plurality of words and executes a first query on a vector store to identify schema elements similar to keywords in the user input. The vector store provides a response with similarity scores for identified elements. A second query is executed on a knowledge graph to identify association paths between data objects that include the identified elements. The knowledge graph response includes association information linking source and target data objects through selected elements. Full association paths are constructed from this information, and a command is generated to instantiate a new data object with elements corresponding to the user input. This approach leverages the strengths of large language models, vector stores, and knowledge graphs to efficiently and accurately create new data objects, ensuring data integrity and relevance.

Automatic generation of data objects from user input

Techniques and solutions are described for storing and retrieving metadata for database artefacts. A client request is received that includes a relevancy identifier. The relevancy identifier is useable to determine a subset of metadata that should be provided in response to the request. Metadata, including in metadata objects or database artefacts, can be reviewed to determine whether it is relevant to the request, such as if the metadata is associated with the relevancy identifier. Different requests from the same client can specify different relevancy identifiers, as, for example, a first set of metadata may be relevant to one client process and another set may be relevant to another client process. While some metadata can be specific to a particular client, at least some of the metadata can be accessed by multiple clients, and at least in some cases different clients can specify the same relevancy identifier.

Centralized metadata repository with relevancy identifiers

Techniques and solutions are described for retaining names for metadata elements, such as when metadata is imported, converted to a different format, or used with a system that may have restrictions on naming different than a system on which the metadata is created. Metadata includes a plurality of metadata elements, including a first metadata element associated with a first name. A second name is received for the first metadata element. The second name is assigned to the first metadata element. An association is created between the renamed first metadata element and the first name.

Metadata elements with persistent identifiers

The present disclosure relates to computer-implemented methods, software, and systems for automatic database configuration. One example method includes receiving, at a database associated with a data warehouse application, a request to generate a configuration to acquire data objects based on executing calls to corresponding programming interfaces provided by a source application, wherein the programming interfaces are identified in the received instructions and are associated with acquiring the data objects associated with metadata entities defined at the database; in response to the received instructions, configuring the database to automatically execute one or more calls to acquire relevant data for a metadata entity defined at the database, wherein the metadata entity is associated with a section of a first programming interface; and invoking the first programming interface at the source application, wherein invoking the first programming interface results in acquiring the relevant data.

Automatic configuration of data invocation from one or more sources based on metadata mappings

A method, a system, and computer program product for managing data are provided. A request to access data from a table including the data and metadata associated with the data is received. The request to determine one or more relevant portions of the data is processed. A file corresponding to the one or more relevant portions of the data is generated by using the metadata. A repository object is generated from the file. A response to the request is transmitted. The response can provide access to update the relevant portions of the data in the repository object.

Handling of lifecycle and delivery for code list values

The present disclosure provides techniques and solutions for integrating data from different instances of a data source, such as a data artifact. That is, in some cases data may be disjoint, or it may overlap in whole or part. How data should be integrated can depend on whether data overlaps, or a type or extent of overlap. An artifact that consumes data can be integrated to indicate how data from underlying instances of a data source should be integrated, including when this consuming artifact requests data indirectly from a consolidation artifact. A search against the consuming artifact can be modified based on configuration information in the consuming artifact indicating how or if data from multiple instances of the data source should be integrated.

Techniques for integrating data for multiple instances of a data artifact

Techniques and solutions are described for facilitating the reuse of text translations. For a first instance of text in a human language, a first logical pointer value is assigned to the first instance of the text, pointing to a target having at least a first translation for the text. A second instance of the text is received. If only the first instance is present, the first logical pointer value is assigned to the second instance. If a third instance of the text is present, associated with a second translation and a second logical pointer value, user or process input is received determining whether the first logical pointer value or the second logical pointer value is assigned to the second instance. Context information can be provided to a user to help determine whether the second instance should be associated with the first translation or the second translation.

Logical pointers supporting reuse of text translations

Techniques and solutions are provided for maintaining data separation, such as when consolidating data for two instances of a data artifact. If data separation is not maintained, it may not be possible, or as easy, to determine from which instance particular data came, which can also limit filtering/selectively searching data for a particular instance. The present disclosure addresses this issue by providing a consolidation data artifact. For particular sets of data in the consolidation data artifact, the consolidation artifact maintains the data in association with an identifier of the instance that serves as the source of the data.

Maintaining data separation for data consolidated from multiple data artifact instances

The present disclosure relates to computer-implemented methods, software, and systems for importing metadata between applications. One example method includes obtaining, at a data warehouse application, metadata for relevant entities in response to a query defined for querying metadata from a metadata source associated with a source application. A service at the source application is queried to identify a set of programming interfaces associated with the relevant entities for acquiring data objects corresponding to the obtained metadata from the source application. Instructions are generated that can be used to configure the database associated with the data warehouse application to acquire a data object based on executing a call to a corresponding programming interface. The generated instructions are provided to the database to configure the database to automatically execute the call to acquire the data object from the source application.

Importing data objects metadata based on application interface to service entity mappings

Techniques and solutions are provided for grouping of applications, including application content, or other content useable by a computer-implemented process. In particular, a consolidation space is provided as a lightweight mechanism for this purpose. Identifiers are received for multiple landscape elements, where a landscape element can be an application, application content, or other content. A given landscape element has a type and has one or more artifacts. A consolidation space is generated for at least first and second landscape elements having a first type. A consolidation artifact is generated in the consolidation space, where the consolidation artifact references respective first and second instances of a first artifact in the first and second landscape elements.

Consolidation spaces providing access to multiple instances of application content

The present disclosure relates to computer-implemented methods, software, and systems for exchanging metadata between applications. One example method includes providing a metadata service defining a service metadata model for exposing metadata of data objects defined at one or more applications. A connection to a data source associated with a first application is established from a separate application to acquire the metadata from the data source for one or more data objects related to the first application. In response to establishing the connection, a view of content from the data source is provided that includes a list of entities from the service metadata model. A query defined based on the list of entities is received for acquiring metadata associated with the one or more identified entities. The query is evaluated at a backend of the first application and the metadata for the identified entities from the data source is provided.

Metadata integration

Techniques and solutions are described for propagating extensions to data artifacts, such as data artifacts defining objects in a physical or virtual data model. One or more data artifacts are identified that are related to a first data artifact. One or more extension elements of the first data artifact are analyzed for propagation to at least one data artifact of the one or more data artifacts. Analyzing whether an extension element should be propagated can include analyzing a type of the extension element, a type of operation or context in which the extension element is used, or how the at least one data artifact refers to, uses, or incorporates the first data artifact, including particular elements thereof. The results of the analysis are compared with various rules. Extension elements are propagated automatically, manually upon user approval (e.g., propagation recommendations are provided), or in a semi-automated manner.

Propagation of extensions of data artifacts

Techniques and solutions are described for providing flexible access to data during execution of a data access request. Multiple instances of a data artifact are created, where different instances of the data artifact provide access to different data sources having data associated with the data access request. When a data access request is executed, a particular data artifact instance can be used during execution of the data access request. In some cases, switching logic can be used to determine which data artifact instance is to be used in executing the data access request. Also described are technologies for facilitating creation of data artifact instances corresponding to a modelling artifact.

Data artifact instances faciliating flexible data access

Techniques and solutions are described for defining and deploying application content. Content, such as objects, can be created in a repository defined for a first application. A package can be defined based at least in part on the objects for use in a computing environment only requiring the first application. A second package can be defined based at least in part on the objects for use in a computing environment in which both the first application and a second application are available. Content can be moved between repositories defined for a single application and repositories defined for multiple applications. Content can be added to, or removed from, a client computing system as applications available on a client computing system change.

Flexible provision of multi-application content

Techniques and solutions are described for storing and processing metadata. A target system sends a request to a source system to identify extensions to one or more specified database artefacts. The source system identifies one or more software objects that include metadata extensions to the one or more specified database artefacts and sends at least a portion of such metadata elements to the target system in response to the request. The source system can expose APIs, such as APIs in a standard format, to the target system to assist in requesting and retrieving metadata from the source system.

Identification and import of metadata for extensions to database artefacts

Growing community of inventors

Eggenstein, Germany

Daniel Buchmann