Abstract: A system and method including receiving a request to map a first service accessible on a first application stack; determining, based on a combination of metadata of the first service and other services in the first application stack that are related to the first service, metadata associated with entities in the first application stack, and trace data associated with data flows between the entities, a complete mapping of the first service, the other services, and the entities comprising business object representations of the first service and business object representations of other services in the first application stack; deriving, based on the determined complete mapping, service mapping information for the first application stack; and persisting the generated service mapping information and the determined complete mapping in a persistency.

Abstract: Some embodiments provide a non-transitory machine-readable medium that stores a program. The program receives a metadata model definition comprising a set of entity definitions specifying a set of entities, a set of semantic key definitions specifying a set of semantic keys associated with the set of entities, and a set of relationship definitions specifying a set of relationships between the set of entities. The set of semantic keys are configured to be used by an application to refer to the set of entities. The program further determines a set of technical keys for the set of entities. The set of technical keys are configured to be used by the device to refer to the set of entities. The program also stores the metadata model definition and the set of technical keys in a set of records.

Abstract: Techniques and solutions are described for storing and processing metadata models using a metadata hub that can be accessed by a plurality of computing systems. The metadata hub can receive requests to retrieve or store metadata models. The metadata models can be converted between first and second formats. In some cases, the second format can be a relational format, such as a representation of a metadata model as one or more records in one or more database tables. The metadata hub can be used to compare metadata models, including comparing a metadata model provided by a client system with one or more metadata models stored in a repository maintained by the metadata hub. In at least some cases, the metadata model provided by the client system is not stored. The repository can be queried to find related metadata models, or to find metadata models meeting specified search criteria.

Abstract: The present disclosure involves computer-implemented method, medium, and system for automatically correlating semantically connected data and metadata. One example method includes identifying a document that is to be analyzed using a semantics based mapping (SBM) infrastructure. A matching process is performed for the identified document using the SBM infrastructure, where the matching process identifies a plurality of matching terms within the document, the plurality of matching terms are assigned to a plurality of semantics identifiers (IDs), and each semantics ID corresponds to one or more terms in the plurality of matching terms. Each of the plurality of matching terms is replaced with a respective term ID to generate an updated document. A request to search for a target term in the document is received. The target term is translated to a target term ID based on the SBM infrastructure. The updated document is searched for one or more matching terms.

Abstract: Some embodiments provide a non-transitory machine-readable medium that stores a program. The program receives a metadata model definition comprising a set of entity definitions specifying a set of entities, a set of semantic key definitions specifying a set of semantic keys associated with the set of entities, and a set of relationship definitions specifying a set of relationships between the set of entities. The set of semantic keys are configured to be used by an application to refer to the set of entities. The program further determines a set of technical keys for the set of entities. The set of technical keys are configured to be used by the device to refer to the set of entities. The program also stores the metadata model definition and the set of technical keys in a set of records.

Abstract: Techniques and solutions are described for storing and processing metadata models using a metadata hub that can be accessed by a plurality of computing systems. The metadata hub can receive requests to retrieve or store metadata models. The metadata models can be converted between first and second formats. In some cases, the second format can be a relational format, such as a representation of a metadata model as one or more records in one or more database tables. The metadata hub can be used to compare metadata models, including comparing a metadata model provided by a client system with one or more metadata models stored in a repository maintained by the metadata hub. In at least some cases, the metadata model provided by the client system is not stored. The repository can be queried to find related metadata models, or to find metadata models meeting specified search criteria.

Abstract: Techniques and solutions are described for defining metadata artefacts and, using a framework, which can be referred to as a decorator framework, updating data artefacts. The data artefacts can be artefacts in a virtual data model, such as data artefacts representing views that can correspond to a view, or one or more tables, of a relational database system. A metadata artefact can include semantic elements, such as annotations, that are processable by the decorator framework in updating data artefacts. Annotations can specify an operation type, such as to include, remove, replace, or synchronize, for content a metadata artefact, where the operation will be carried out on data artefacts to which the metadata artefact is applied and which contain specified content. Multiple metadata artefacts can be applied to a given data artefact, and a given metadata artefact can be applied to multiple data artefacts.

Abstract: Techniques and solutions are described for storing and processing metadata models using a metadata hub that can be accessed by a plurality of computing systems. The metadata hub can receive requests to retrieve or store metadata models. The metadata models can be converted between first and second formats. In some cases, the second format can be a relational format, such as a representation of a metadata model as one or more records in one or more database tables. The metadata hub can be used to compare metadata models, including comparing a metadata model provided by a client system with one or more metadata models stored in a repository maintained by the metadata hub. In at least some cases, the metadata model provided by the client system is not stored. The repository can be queried to find related metadata models, or to find metadata models meeting specified search criteria.

Abstract: Techniques and solutions are described for defining metadata artefacts and, using a framework, which can be referred to as a decorator framework, updating data artefacts. The data artefacts can be artefacts in a virtual data model, such as data artefacts representing views that can correspond to a view, or one or more tables, of a relational database system. A metadata artefact can include semantic elements, such as annotations, that are processable by the decorator framework in updating data artefacts. Annotations can specify an operation type, such as to include, remove, replace, or synchronize, for content a metadata artefact, where the operation will be carried out on data artefacts to which the metadata artefact is applied and which contain specified content. Multiple metadata artefacts can be applied to a given data artefact, and a given metadata artefact can be applied to multiple data artefacts.

Abstract: Techniques and solutions are described for storing and processing metadata models using a metadata hub that can be accessed by a plurality of computing systems. The metadata hub can receive requests to retrieve or store metadata models. The metadata models can be converted between first and second formats. In some cases, the second format can be a relational format, such as a representation of a metadata model as one or more records in one or more database tables. The metadata hub can be used to compare metadata models, including comparing a metadata model provided by a client system with one or more metadata models stored in a repository maintained by the metadata hub. In at least some cases, the metadata model provided by the client system is not stored. The repository can be queried to find related metadata models, or to find metadata models meeting specified search criteria.

Abstract: Data characterizing a design time model and an identification of a use case for the design time model is received. The design time model includes logic characterizing a database view. A predefined set of rules associated with the use case is received. A runtime model of the database view is generated using the design time model and according to the predefined set of rules. The generating includes building the runtime model from the design time model and automatically removing logic from the design time model, the removed logic being unused and removed according to the predefined set of rules associated with the use case. The runtime model is provided. Related apparatus, systems, techniques and articles are also described.

Abstract: Methods and apparatus, including computer program products, are provided for editing messages via a message-specific user interface. In some implementations, a method may be provided. The method may include receiving, at a user interface, data content of a message corresponding to a business object; presenting, at the user interface, the data content of the message corresponding to the business object, the user interface generated specifically for a type associated with the message; and initiating, at the user interface, at least one of a change and a save to the data content. Related systems, methods, and articles of manufacture are also disclosed.

Abstract: An interface for accessing adaptive labeling logic for enriching label texts is instantiated. The adaptive labeling logic is provided at an adaptive labeling text processor. At the interface, a request associated with a view of a UI application is received. Data service metadata associated with the UI view is fetched. The data service metadata includes a plurality of fields and association definitions in relation to the UI view. Label texts mapped to the plurality of fields are determined, where one or more of the label texts are mapped to a field from the fields. Adaptive label texts for the plurality of fields are constructed based on evaluation of the association definitions and the determined label texts. A set of adaptive label texts is associated with a field. An adaptive label text uniquely identifies a corresponding field from the plurality of field within the constructed adaptive label texts.

Abstract: An interface for accessing adaptive labeling logic for enriching label texts is instantiated. The adaptive labeling logic is provided at an adaptive labeling text processor. At the interface, a request associated with a view of a UI application is received. Data service metadata associated with the UI view is fetched. The data service metadata includes a plurality of fields and association definitions in relation to the UI view. Label texts mapped to the plurality of fields are determined, where one or more of the label texts are mapped to a field from the fields. Adaptive label texts for the plurality of fields are constructed based on evaluation of the association definitions and the determined label texts. A set of adaptive label texts is associated with a field. An adaptive label text uniquely identifies a corresponding field from the plurality of field within the constructed adaptive label texts.

Abstract: Methods and apparatus, including computer program products, are provided for editing messages via a message-specific user interface. In some implementations, a method may be provided. The method may include receiving, at a user interface, data content of a message corresponding to a business object; presenting, at the user interface, the data content of the message corresponding to the business object, the user interface generated specifically for a type associated with the message; and initiating, at the user interface, at least one of a change and a save to the data content. Related systems, methods, and articles of manufacture are also disclosed.

Abstract: Methods and apparatus, including computer program products, are provided for editing messages via a message-specific user interface. In some implementations, a method may be provided. The method may include receiving, at a user interface, data content of a message corresponding to a business object; presenting, at the user interface, the data content of the message corresponding to the business object, the user interface generated specifically for a type associated with the message; and initiating, at the user interface, at least one of a change and a save to the data content. Related systems, methods, and articles of manufacture are also disclosed.

Abstract: Methods and apparatus, including computer program products, are provided for testing data structures, such as for example business objects. In some implementations, there is provided a method. The method may include generating, at a test system, a test script including a test business object generated based on metadata describing aspects of a deployed business object at a target system; receiving, at the test system, a request to test the target system including the deployed business object; testing, based on the generated test script including the test business object, at least one of a data and an action of the deployed business object; and generating, at the test system, at least a result of the testing. Related systems, methods, and articles of manufacture are also disclosed.

Abstract: Read access logging is performed by tracing data accesses in all domains. The logged data is traced on metadata level with some additions identifying the exposed data records. All data relevant for read access logging is stored at first in a temporary log, which is later processed, structured, and archived.

Abstract: Read access logging is performed by tracing data accesses in all domains. The logged data is traced on metadata level with some additions identifying the exposed data records. All data relevant for read access logging is stored at first in a temporary log, which is later processed, structured, and archived.

Abstract: A search area to search business object instance(s), business object(s), node(s), and/or data types may be displayed. Business object instance(s), business object(s), node(s), and/or data type(s) based on search criteria specified in the search area may be displayed. In response to identification of a business object instance, a business object, a node, or a data type, information pertaining to the identified business object instance, business object, node, or data type may be displayed.