Abstract: Techniques and solutions are provided for organizing and controlling access/operations with respect to computing objects, such as a definition of a computing object or data associated with an instance of a defined computing object. A collection of computing objects is associated with a namespace, the namespace having a namespace identifier. At least a first set of access rights is associated with the namespace, such as access rights of a first tenant, representing a computing environment to which the computing objects of the namespace may be deployed. The access rights specify permitted/prohibited operations with respect to the computing objects, such as whether the computing objects are available on a read-only basis or whether create, update, or delete operations are also allowed. A namespace can have multiple tenant accessors, where different tenants can have different access rights for a given namespace.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: Implementations of the present disclosure include receiving a query, the query including an expression macro (EM), processing the query to provide a raw parse tree, the raw parse tree including an initial node representative of the EM, retrieving metadata corresponding to the EM, the metadata including a definition string, replacing the initial node with a node based on the definition string to provide a consumable parse tree, and executing the query within the database system using the consumable parse tree to provide a query result.

Abstract: The present disclosure pertains to systems and methods for providing search results. A database server may include both a database and a search engine. The database server can receive a search request from an application of a remote computer. The search request can include one or more search terms and permission information. The database server can determine adapting information using the permission information. The database server can provide a search call based on the search request and the adapting information to the search engine. The search engine can determine one or more search statements for the search call. The search engine can execute the one or more search statements on one or more stored search models to obtain database results reflecting the permission information. The database server can provide search results based on the database results to the application of the remote computer.

Abstract: Methods, systems, and computer-readable storage media for retrieving metadata associated with data stored within a database system of an enterprise, the metadata being provided in a first format and being used by the first system to store and access the data, providing a document including the metadata provided in an interoperable format, processing, by a deployer, the document to provide analytics engine metadata in a second format, the analytics metadata being stored in the second system and being consumable by the DB-based analytics engine to access the data from the database system of the enterprise, and retrieving, by the DB-based analytics engine, the data from the database system of the enterprise based on the analytics metadata to provide analytics data based on the data.

Abstract: Methods, systems, and computer-readable storage media for retrieving metadata associated with data stored within a database system of an enterprise, the metadata being provided in a first format and being used by the first system to store and access the data, providing a document including the metadata provided in an interoperable format, processing, by a deployer, the document to provide analytics engine metadata in a second format, the analytics metadata being stored in the second system and being consumable by the DB-based analytics engine to access the data from the database system of the enterprise, and retrieving, by the DB-based analytics engine, the data from the database system of the enterprise based on the analytics metadata to provide analytics data based on the data.

Abstract: Techniques and solutions are described for transferring metadata between software applications. A translation framework stores metadata models in a standard format. Source applications can cause metadata models to be stored in the translation framework in the standard format. A target application can receive metadata models, or elements thereof, from the translation framework, which metadata models can be optionally converted from the standard format to a target format used by the target application. The translation framework can store annotations to a metadata model in the form of custom metadata types. The custom metadata types can be used by one or both of the target application and a source application. Source applications can cause values to be stored for annotations they support. Target applications can read values for annotations they support. Source applications and target applications do not write or read, respectively, unsupported annotations.

Abstract: The present disclosure pertains to systems and methods for providing search results. A database server may include both a database and a search engine. The database server can receive a search request from an application of a remote computer. The search request can include one or more search terms and permission information. The database server can determine adapting information using the permission information. The database server can provide a search call based on the search request and the adapting information to the search engine. The search engine can determine one or more search statements for the search call. The search engine can execute the one or more search statements on one or more stored search models to obtain database results reflecting the permission information. The database server can provide search results based on the database results to the application of the remote computer.

Abstract: Implementations of the present disclosure include receiving a query, the query including an expression macro (EM), processing the query to provide a raw parse tree, the raw parse tree including an initial node representative of the EM, retrieving metadata corresponding to the EM, the metadata including a definition string, replacing the initial node with a node based on the definition string to provide a consumable parse tree, and executing the query within the database system using the consumable parse tree to provide a query result.

Abstract: Techniques and solutions are described for transferring metadata between software applications. A translation framework stores metadata models in a standard format. Source applications can cause metadata models to be stored in the translation framework in the standard format. A target application can receive metadata models, or elements thereof, from the translation framework, which metadata models can be optionally converted from the standard format to a target format used by the target application. The translation framework can store annotations to a metadata model in the form of custom metadata types. The custom metadata types can be used by one or both of the target application and a source application. Source applications can cause values to be stored for annotations they support. Target applications can read values for annotations they support. Source applications and target applications do not write or read, respectively, unsupported annotations.

Abstract: A system for visually enhancing a chart of one or more data sets with semantic information, the data points in the data sets being values of one or more measures. The system includes a data model that specifies the one or more measures and includes measure annotations for the one or more measures. The measure annotations include semantic information of the measures. The system further includes a processor that executes instructions stored in the memory to implement a chart component. The chart component renders data points of the one or more data sets in a chart, and visually enhances the chart with semantic information of the one or more measures retrieved from the data model.

Abstract: A system for visually enhancing a chart of one or more data sets with semantic information, the data points in the data sets being values of one or more measures. The system includes a data model that specifies the one or more measures and includes measure annotations for the one or more measures. The measure annotations include semantic information of the measures. The system further includes a processor that executes instructions stored in the memory to implement a chart component. The chart component renders data points of the one or more data sets in a chart, and visually enhances the chart with semantic information of the one or more measures retrieved from the data model.

Abstract: Disclosed herein are system, method, and computer program product embodiments for an embedded analytics and transactional data processing system. An embodiment operates by receiving selection of a filter that indicates a subset of transactional data from a database to be displayed via an interface. Analytical data associated with the subset of transactional data is determined. Via the interface, the filter selection, the analytical data, and the subset of transactional data are all provided.

Abstract: Conventional approaches to transactional processing and analytics in database management systems have typically maintained a strict separation between these tasks, often resulting duplicate modeling, replication of data, usage of different infrastructure stacks, the need to integrate transactions and analytics on a layer that is very close to the end user, etc. Described herein are systems, methods, articles of manufacture, and the like relating to a central integration component that provides access to a core metamodel. Via the metamodel, metadata specify a data part of a business object and one or more information providers (e.g., an analytical view, an attribute view, etc.) that directly consume data from database tables underlying the business object. The central integration component responds to data access requests using the core metmodel.

Abstract: A computer program product is tangibly embodied in a computer readable storage medium and comprises instructions that when executed by a processor perform a method including: presenting business category identifiers to a user in a computer system, each business category identifier representing one of multiple reporting content bundles for configuring a transactional application and an analytical application; receiving, in the computer system, a selection by the user of at least one of the business category identifiers; and installing in the computer system, from the selected reporting content bundle, at least one transactional content object in the transactional application, and at least one analytical content object in the analytical application.

Abstract: A computer program product is tangibly embodied in a computer readable storage medium and comprises instructions that when executed by a processor perform a method including: presenting business category identifiers to a user in a computer system, each business category identifier representing one of multiple reporting content bundles for configuring a transactional application and an analytical application; receiving, in the computer system, a selection by the user of at least one of the business category identifiers; and installing in the computer system, from the selected reporting content bundle, at least one transactional content object in the transactional application, and at least one analytical content object in the analytical application.

Abstract: Systems and methods are provided for data processing. As disclosed herein, such systems and methods may include providing a data model with a set of entity types and set of attributes for each entity type, providing customizing data for the data model, the customizing data indicating data sources for the attributes and describing data structures being provided by the data sources, querying the attribute data for at least a first attribute of the set of attributes of one of the entity types, determining from the customizing data, if a single data source for the first attribute data of the one of the entity types is available, if such a single data source is not available, determining at least first and second ones of the data sources which in combination comprise the first attribute data of the one of the entity types, generating a sub-query for each one of the at least first and second data sources, and combining the results of the sub-queries to provide a query result.

Abstract: Systems and methods are disclosed for providing validity logic. The disclosed systems and methods may include receiving at least one data value, determining validity data corresponding to the received at least one data value, and providing the validity data corresponding to the received at least one data value. Furthermore, the disclosed systems and methods may include receiving at least one data value, receiving validity data corresponding to the received at least one data value, and determining, based on the received validity data, a validity value, the validity value indicating the validity of the received at least one data value.