Abstract: Tools and techniques are described for selecting member sets for generating asymmetric queries. User interfaces provided by this description may include representations of different dimensions that include respective members. These dimensions define hierarchical data structures against which queries are run to generate requested reports. The user interfaces may include representations of members associated with different dimensions, with members from different dimensions arranged in selected orders. The user interfaces may also provide selection tools that activate symmetrical or asymmetrical rendering modes for constructing the query. In the symmetrical rendering mode, the query cross-joins all of the members selected from one dimension with all of the members selected from the other dimension.

Abstract: Technologies are described herein for defining the scope of a sub-cube based upon a database query. A request is received to perform a query of a multi-dimensional database, such as a cube, stored at a server computer. In response to the request, the scope for a sub-portion, called a sub-cube, of the multi-dimensional database is determined based upon the query. The scope of the sub-cube may be determined by identifying the minimum sub-portion of the cube necessary to perform the query. Once the scope has been determined, the sub-cube is generated at the server computer and transmitted to a client computer. The client computer stores the sub-cube locally and performs the requested database query on the sub-cube stored at the client computer. A user interface may be provided through which a user can modify the scope of the sub-cube determined based upon the query.

Abstract: A parsing and indexing mechanism for dynamically generated reports is provided. Upon detection of a dynamically generated report, a data source for the dynamically generated report may be identified based on metadata or other information associated with the report. Crawleable or machine readable metadata and data may be generated using the data source such that data represented in the report and/or other relevant data from the data source can be indexed and searched.

Abstract: Relationships between linked and/or embedded documents as well as documents sharing data source(s) are captured and rendered through virtual documents. Virtual documents are created representing linked/embedded documents and data sources associated with a relevant document. Relationships between real and virtual documents are preserved and rendered along with search results providing a user a comprehensive picture of search results.

Abstract: An object oriented search mechanism extracts structural metadata and data based on type of document contents and data sources connected to the documents. Relationships between textual and non-textual elements within documents as well as metadata associated with the elements and data sources are utilized to generate a unified object model with the addition of semantic information derived from metadata and taxonomy, which are used to enhance search indexing, ranking of search results, and dynamic adjustment of result rendering user interface with fine tuned relevancy. Additional data from data sources connected to the documents may also be used to unlock hidden data such as data that has been filtered out in an original document.

Abstract: User role based customizable searches, where crawled documents may be evaluated against user roles or attributes during crawl time, are provided. Metadata retrieved from searched documents may also be evaluated against the user roles and/or attributes such that customized search results ranking documents based on their content beyond textual content may be provided.

Abstract: Architecture for operating an industrial solution on top of a performance management platform using a custom business type library. The platform can plug/unplug the custom business type library, interacts with the type library to ensure data integrity and enforce business rules, and simplifies localizations of the industrial solution. The custom type library extends the capability to define specific behavior for models and dimensions, and create and define content specific to any industry, reuse, and packaging. The custom type library inherits from a generic type library of the platform. The customized type library defines business object types and associates business rules therewith. Through a common interface, the performance management platform can iterate through the business rule chains and enforce/apply the business rules during the operations.

Abstract: Data processing architecture where submitters can write data and/or metadata changes to a destination through an asynchronous interface. The architecture includes a ticketing system that issues a ticket (a unique identifier) to the submitter in response to receiving a changelist from the submitter. When the changes are successfully completed at the destination, the cached destination data can be re-downloaded to the submitter, and the changes cached in the submitter, discarded. Absent this capability, a user has to manually manage the cached changes and cached data. The architecture can be distributed in that multiple submitters can submit changelists. The destination provides data integrity by managing submissions to assist in ensuring data integrity across multiple submissions. Automatic changelist cleanup is provided on the submitter so that changelists do not impact performance, memory, and storage.

Abstract: Architecture that employs a journal assignment that can be created on demand when journal is created, and operates outside the business cycle. The assignment is routed to reviewers and approvers based on predefined company policy that users define. The assignment encloses a changelist of data changes created by the journal. The changelist is used for rendition and calculation for reviewers and approvers (in addition to the journal contributor) to view/verify and modify the data as if the data is already written into the model. At the time that other users access this model, the data is not present. At the end of the successful workflow chain the changelist is written into the model. If failed, the changelist will be used as that basis for correction or the user can discard the changelist.

Abstract: A user interface displays a group of related documents such that bulk operations may be performed on them without requiring the user to individually access each document to perform an action. Properties, such as a status, contributor information, submission date and submission deadline and the like are also displayed with the documents. From this information, a user may decide to open a specific document and/or version of the document for review while bulk approving the other displayed documents. A user may perform an action on all or part of the displayed documents and their versions from the user interface. In this way, the efficiency of the workflow may be increased since the user doesn't have to individually access each document to perform the action.

Abstract: Tools and techniques are described for selecting member sets for generating asymmetric queries. User interfaces provided by this description may include representations of different dimensions that include respective members. These dimensions define hierarchical data structures against which queries are run to generate requested reports. The user interfaces may include representations of members associated with different dimensions, with members from different dimensions arranged in selected orders. The user interfaces may also provide selection tools that activate symmetrical or asymmetrical rendering modes for constructing the query. In the symmetrical rendering mode, the query cross-joins all of the members selected from one dimension with all of the members selected from the other dimension.

Abstract: A computer-implemented method includes selecting a first member of a first dimension of a database to be included at a first location in a report. The first member includes first data to be retrieved from the database. A blank space to be added at a second location relative to the first member is also selected. A database query is generated that includes a first instruction to retrieve first data included in the first member. The first instruction is located at a first position in the query and the first data will appear in the report at the first location. The database query also includes a second instruction to retrieve a null set of data. The second instruction is located at a second position in the query and the null set of data will appear in the report at the second location.

Abstract: Technologies are described herein for defining the scope of a sub-cube based upon a database query. A request is received to perform a query of a multi-dimensional database, such as a cube, stored at a server computer. In response to the request, the scope for a sub-portion, called a sub-cube, of the multi-dimensional database is determined based upon the query. The scope of the sub-cube may be determined by identifying the minimum sub-portion of the cube necessary to perform the query. Once the scope has been determined, the sub-cube is generated at the server computer and transmitted to a client computer. The client computer stores the sub-cube locally and performs the requested database query on the sub-cube stored at the client computer. A user interface may be provided through which a user can modify the scope of the sub-cube determined based upon the query.

Abstract: An interface for designing a report is provided, with elements of the report being disposed at intersections of report positions and configured to present information derived from data in a database. A formula is associated with one or more selected elements in the report to generate a result for the one or more selected elements. A tuple identifying the report positions of the one or more selected elements is associated and stored with the formula in a formula list associated with the report. The report is configured so that, when the report is generated, it is determined whether identifying report positions corresponding to an identified element in the report correspond with the tuple in the formula list. Upon determining the tuple corresponds with the identifying report positions for the identified element, the formula associated with the tuple is applied to generate the result.

Abstract: Techniques to manage information for dynamic reports are described. An apparatus may comprise a business planning application module to update a current period reference to a time member of a time dimension, generate a rolling data entry form with actual data members and forecast data members based on the current period reference, and set a data locking mode for the actual data members and a data access mode for the forecast data members. Other embodiments are described and claimed.

Abstract: A computer-implemented method includes selecting a first member of a first dimension of a database to be included at a first location in a report. The first member includes first data to be retrieved from the database. A blank space to be added at a second location relative to the first member is also selected. A database query is generated that includes a first instruction to retrieve first data included in the first member. The first instruction is located at a first position in the query and the first data will appear in the report at the first location. The database query also includes a second instruction to retrieve a null set of data.