Abstract: A tenant separation architecture is provided to adopt tenant separation for remote integration of various OEM systems with a cloud-based analytics application. The tenant separation architecture provided herein allows for tenant separation in a wide range of modules in different OEM integration scenarios through a token-base authentication. Application server tenants and database tenants may be accessed for application of the tenant separation. Moreover, the tenant separation implementations disclosed herein may be applied to different modules for metadata, tenant configuration, authorization concepts, and general data protection regulation (GDPR) adoption.

Abstract: Methods, systems, and computer-readable storage media for receiving, by a QMS executed within a first data center, a query definition provided from a browser of an analytics platform executed within the second data center, the query definition being stored in a query repository, being validated by the QMS based on analytical metadata, and being stored in a mirror query repository of the first data center, providing, after validation of the query definition, a calculation scenario as an object model based on the query definition, executing, by a calculation engine within the first data center, the calculation scenario to provide an analytical artifact including a query-level calculation view on transactional data stored in the first data center, and transmitting, by the first data center, the analytical artifact to the second data center to perform analytics on at least a portion of the transactional data stored in the first data center.

Abstract: The disclosure generally describes methods, software, and systems, including a method for using an object definition from which object documents are instantiated defining real-world variants of a physical object and including a meta-model identifying nodes, fields, and associations with other object definitions. The object definition includes, at instantiation of a given object document marking an existence of the physical object, an object identifier node, including an object identifier, and at least one variant type node, including a variant type identifier identifying the real-world variant of the physical object and including variant extension nodes and fields extending the object definition to a variant object definition.

Abstract: A system, a method, and a computer program product for performing component integration. A first computing system generates a computing component for integration with a second computing system. The first computing system provides the computing component to the second computing system. The second computing system configures the computing component for operation by the first computing system with at least one computing component of the second computing system. The first computing system operates the configured computing component in the second computing system.

Abstract: A data source integration architecture is provided for integrating application systems with an analytics system for user querying and data retrieval. The integration includes flexibly configuring base data sources as defined by an analytical model of an application system, such as an OEM application. In response to a query, metadata is fetched from an application server, where the metadata may contain a description of underlying artifacts of the structural part of the analytical model. During query generation, these specific views are injected into a query view and a parametrization is added for data source modulation. In addition, a flexible configuration of the final shape of the base data source specifically allows for the requirements of the OEM application to be addressed.

Abstract: Methods, systems, and computer-readable storage media for receiving, by a query manager service (QMS) executed within a first data center, a query definition provided from a browser of an analytics platform executed within a second data center, providing, by the QMS, a calculation scenario as an object model based on the query definition, executing, by a calculation engine within the first data center, the calculation scenario to provide an analytical artifact including a query-level calculation view on transactional data stored in the first data center, and transmitting, by the first data center, the analytical artifact to the second data center to perform analytics on at least a portion of the transactional data stored in the first data center.

Abstract: Implementations include actions of receiving, by a QMS executed within a first data center, a query definition provided from a browser of an analytics platform executed within the second data center, providing, by the QMS, a raw calculation scenario as an object model based on the query definition, and one or more filters, processing, by the QMS, the raw calculation scenario to provide an enhanced calculation scenario, the enhanced calculation scenario incorporating one or more relationships based on at least one of the one or more filters, executing, by a calculation engine within the first data center, the enhanced calculation scenario to provide an analytical artifact including a query-level calculation view on transactional data, and transmitting, by the first data center, the analytical artifact to the second data center to perform analytics on at least a portion of the transactional data stored in the first data center.

Abstract: A tenant separation architecture is provided to adopt tenant separation for remote integration of various OEM systems with a cloud-based analytics application. The tenant separation architecture provided herein allows for tenant separation in a wide range of modules in different OEM integration scenarios through a token-base authentication. Application server tenants and database tenants may be accessed for application of the tenant separation. Moreover, the tenant separation implementations disclosed herein may be applied to different modules for metadata, tenant configuration, authorization concepts, and general data protection regulation (GDPR) adoption.

Abstract: A data source integration architecture is provided for integrating application systems with an analytics system for user querying and data retrieval. The integration includes flexibly configuring base data sources as defined by an analytical model of an application system, such as an OEM application. In response to a query, metadata is fetched from an application server, where the metadata may contain a description of underlying artifacts of the structural part of the analytical model. During query generation, these specific views are injected into a query view and a parametrization is added for data source modulation. In addition, a flexible configuration of the final shape of the base data source specifically allows for the requirements of the OEM application to be addressed.

Abstract: A system, a method, and a computer program product for performing component integration. A first computing system generates a computing component for integration with a second computing system. The first computing system provides the computing component to the second computing system. The second computing system configures the computing component for operation by the first computing system with at least one computing component of the second computing system. The first computing system operates the configured computing component in the second computing system.

Abstract: A computer-implemented method for defining queries based on agile semantic objects (ASOs) is provided. Data definitions defining data structures are acquired from a plurality of data sources. The data definitions include information for fields, semantics, and data relationships and semantics for use in analytical environments. Using the data definitions, metadata is defined for ASOs representing data objects in the data definitions. The metadata and the ASOs are stored in an ASO repository. A request for creating a query is received. Metadata representing the ASOs is provided in response to the request for use in a query designer interface. A query based on selected ones of the ASOs is received from the query designer interface. The query is stored in a query repository. A runtime object for executing the query is provided.

Abstract: The disclosure generally describes methods, software, and systems, including a method for using an object definition from which object documents are instantiated defining real-world variants of a physical object and including a meta-model identifying nodes, fields, and associations with other object definitions. The object definition includes, at instantiation of a given object document marking an existence of the physical object, an object identifier node, including an object identifier, and at least one variant type node, including a variant type identifier identifying the real-world variant of the physical object and including variant extension nodes and fields extending the object definition to a variant object definition.

Abstract: Methods, systems, and computer-readable storage media for receiving, by a query manager service (QMS) executed within a first data center, a query definition provided from a browser of an analytics platform executed within a second data center, providing, by the QMS, a calculation scenario as an object model based on the query definition, executing, by a calculation engine within the first data center, the calculation scenario to provide an analytical artifact including a query-level calculation view on transactional data stored in the first data center, and transmitting, by the first data center, the analytical artifact to the second data center to perform analytics on at least a portion of the transactional data stored in the first data center.

Abstract: Methods, systems, and computer-readable storage media for receiving, by a QMS executed within a first data center, a query definition provided from a browser of an analytics platform executed within the second data center, the query definition being stored in a query repository, being validated by the QMS based on analytical metadata, and being stored in a mirror query repository of the first data center, providing, after validation of the query definition, a calculation scenario as an object model based on the query definition, executing, by a calculation engine within the first data center, the calculation scenerio to provide an analytical artificat including a query-level calculation view on transactional data stored in the first data center, and transmitting, by the first data center, the analytical artificat to the second data center to perform analytics on at least a portion of the transactional data stored in the first data center.

Abstract: Implementations include actions of receiving, by a QMS executed within a first data center, a query definition provided from a browser of an analytics platform executed within the second data center, providing, by the QMS, a raw calculation scenario as an object model based on the query definition, and one or more filters, processing, by the QMS, the raw calculation scenario to provide an enhanced calculation scenario, the enhanced calculation scenario incorporating one or more relationships based on at least one of the one or more filters, executing, by a calculation engine within the first data center, the enhanced calculation scenario to provide an analytical artifact including a query-level calculation view on transactional data, and transmitting, by the first data center, the analytical artifact to the second data center to perform analytics on at least a portion of the transactional data stored in the first data center.

Abstract: The disclosure generally describes methods, software, and systems, including a method for using an object definition from which object documents are instantiated defining real-world variants of a physical object and including a meta-model identifying nodes, fields, and associations with other object definitions. The object definition includes, at instantiation of a given object document marking an existence of the physical object, an object identifier node, including an object identifier, and at least one variant type node, including a variant type identifier identifying the real-world variant of the physical object and including variant extension nodes and fields extending the object definition to a variant object definition.

Abstract: Methods, systems, and computer program products for transferring business objects and business object data are described. A business object from a first networked service may be obtained. The business object may be stored in a cloud business object broker and may be transferred to a second networked service. The business object may be deleted from the cloud business object broker after a transferal from the cloud business object broker to the second networked service.

Abstract: The disclosure generally describes computer-implemented methods, computer program products, and systems for providing metadata-driven dynamic load balancing in multi-tenant systems. A computer-implemented method includes: identifying a request related to a model-based application executing in a multi-tenant system associated with a plurality of application servers and identifying at least one object in the model-based application associated with the request. At least one application server is identified as associated with a locally-cached version of a runtime version of the identified object, and a determination of a particular one of the identified application servers to send the identified request for processing is based on a combination of the availability of a locally-cached version of the runtime version at the particular application server and the server's processing load. The request is then sent to the determined application server for processing.

Abstract: Systems and methods are disclosed for processing data in an application platform. The method may include receiving at runtime a request for data about contributors to at least one document. Data may be determined for a set of contributors to the at least one document. The data for the set of contributors may be transformed based on at least one transformation rule. The transformed data for the set of contributors may be communicated in response to the request. The request may include context data indicating one or more of a user of a computing device, a user session of the computing device, a currently active application on the computing device, and an active screen of the computing device. The determining the data may include identifying, using at least some of the context data, a document associated with the currently active application.

Abstract: The present disclosure involves systems, products, and methods for modifying elements within a user interface (UI). One method includes operations for identifying an instance of a UI text element for modification within a UI associated with a software application, wherein the UI is displayed to at least one user; retrieving a set of metadata associated with the identified instance of the UI text element, where each instance of the UI text element is associated with the retrieved set of metadata; receiving at least one modification to the retrieved set of metadata associated with the identified instance of the UI text element; and persisting the modified set of metadata associated with the UI text element.