Abstract:
A system includes reception of a request conforming to a modeled query and join filter criteria, the request comprising a first subrequest associated with a search attribute view and a second subrequest associated with an analytical view, definition of a join between the search attribute view and the analytical view based on one or more view attributes of the search attribute view, and filtering of a result set associated with the first subrequest based on the join and on the join filter criteria.
Abstract:
Example systems and methods of integrating data tags with their associated object data are presented. In one implementation, a data object employed in a first computer application is accessed. Examples of the data object include, but are not limited to, structured data and unstructured data. Tagging data that is descriptive of the first data object is also accessed. The tagging data is stored in at least one of the first data object and a separate data object linked with the first data object. The tagging data and the first data object are processed using a second computer application.
Abstract:
A system includes reception of a query comprising one or more search terms, determination that one of the one or more search terms corresponds to a table column comprising Boolean operators, determination of a value of the table column corresponding to TRUE, and addition of a condition to the query, the condition specifying the value of the table column.
Abstract:
A system and method for modeling cross system content between a hub and one or more backend systems is disclosed. Model content of one or more data models is stored in a model stack defined in a storage. The model content of each data model includes model metadata representing a model of a backend system. Cross model content is stored in a cross model stack. The cross model content includes reference metadata representing one or more references associated with a data model of one backend system and that reference a data model of another backend system. Central cross model content is stored in a central cross model stack. The central cross model content includes one or more cross elements that do not belong to the model content of any of the data models, and that establish a connection between two data models of different backend systems.
Abstract:
Systems and techniques for providing a master data framework. The framework receives user input and automatically generates, in accordance with the input, a persistent definition of a business object type. The input can be simple declarations and need not be provided in any particular programming language. Definitions generated by the framework adhere to a same data model, regardless of the business object type they are defining. The framework allows the user to create a definition of a business object type by associating two or more definitions of other business object types. The framework provides services that can be applied, without further customization, to any definition of business object types generated by the framework. These services, for example, can be used by a calling application to instantiate business objects or to change a state of a business object instance.
Abstract:
A directory includes information about various systems (e.g., applications, processes, tasks, objects, services) and data, and may include data ownership information. The directory may define existing systems, corresponding locations by address, and corresponding semantic names. The directory may also specify the role of each system, e.g., a consumer or provider role. The directory may also define a scope of data a provider system can provide. As such, the directory may also include information about whether and how such data is being replicated. When a user requests data, a service may, based on the directory, determine and select an appropriate provider system for the data. The service may further create a subscription process to provide the user a local cache of the requested data. With such directory information, a service can provide data access services that integrate subscription processes.
Abstract:
A directory includes information about various systems (e.g., applications, processes, tasks, objects, services) and data, and may include data ownership information (e.g., data scope, read-write access, master-copy, etc.) and system role information (e.g., consumer or provider role). The directory may define existing systems, corresponding locations by address, and corresponding semantic names. With such information, a service may create routing rules that may provide the requested data via a semantic-based request. The routing rule may be selected to optimize communications and/or response time.
Abstract:
A directory includes information about various systems (e.g., applications, processes, tasks, objects, services) and data, and may include data ownership information. The directory may define existing systems, corresponding locations by address, and corresponding semantic names. The directory may also specify the role of each system, e.g., a consumer or provider role. The directory may also define a scope of data a provider system can provide. As such, the directory may also include information about whether and how such data is being replicated. When a user requests data, a service may, based on the directory, determine and select an appropriate provider system for the data. The service may further create a subscription process to provide the user a local cache of the requested data. With such directory information, a service can provide data access services that integrate subscription processes.
Abstract:
Systems and techniques for providing a master data framework. The framework receives user input and automatically generates, in accordance with the input, a persistent definition of a business object type. The input can be simple declarations and need not be provided in any particular programming language. Definitions generated by the framework adhere to a same data model, regardless of the business object type they are defining. The framework allows the user to create a definition of a business object type by associating two or more definitions of other business object types. The framework provides services that can be applied, without further customization, to any definition of business object types generated by the framework. These services, for example, can be used by a calling application to instantiate business objects or to change a state of a business object instance.
Abstract:
Methods and systems consistent with the present invention provide a data processing system having a business object model reflecting the data used during a business transaction. Consistent interfaces are generated from the business object model. These interfaces are suitable for use across industries, across businesses, and across different departments within a business during a business transaction.