Abstract: Embodiments extend the relational model and query language to recognize features of tables and higher level entity-relationship models (ERMs). Extension language is implemented in the data design language (DDL) to incorporate tables, entities (and views) having custom-defined/semantic structure, rather than being limited to primitive types (e.g. flat tables as in standard SQL). The extension language includes an indication that a query is to include all active elements for each table extension or entity extension that is active. The extension language can be chained to extend a table or entity that has been extended.

Abstract: Embodiments extend the relational model and language of standard SQL, to recognize features of higher level entity-relationship models (ERMs). SQL extensions implemented in the data design language (DDL) incorporate Entities (and Views) having custom-defined/semantic structure, rather than being limited to primitive types (e.g. flat tables as in standard SQL). Entities are defined similar to structured types with an underlying persistency, but with a uniquely identifying leading key. In DDL, these entities are combined with associations in the data model. The associations of the extended SQL reflect relationships between entities in the ERM. Associations are specified by adding an element to a source entity, with an association type pointing to a target entity. This may be complemented by providing optional information (e.g., cardinality, keys, filter conditions), up to a complete JOIN condition. In the query language (QL), JOINs may be replaced by the use of simple path expressions.

Abstract: A method includes processing a transaction on an in memory database where data being processed has a validity time, updating a time dependent data view responsive to the transaction being processed to capture time validity information regarding the data, and storing the time validity information in a historization table to provide historical access to past time dependent data following expiration of the validity time.

Abstract: Embodiments extend the relational model and language of standard SQL, to recognize features of higher level entity-relationship models (ERMs). Annotation language is implemented in the data design language (DDL) to incorporate tables and entities Using DDL, annotations are typed structures of metadata. Annotations may be used for types, entities and elements. In the query language (QL), annotations may be added to the standard QL. A reflection program may use the metadata of the annotation language for reflection on the tables or entities.

Abstract: In an example embodiment a market data management system allows users to track information regarding commodities. A representative market data management system comprises physical commodity objects including a plurality of fields that describe a real world commodity, market identifier objects including market identifier codes, and contract specification objects including a plurality of fields that describe a derivative contract specification for a particular commodity traded at a particular commodity market. In the data model, a one to many relationship may exist for a physical commodity object and contract specification objects (e.g., a given commodity may be traded according to different derivative contract specifications). The data model may also allow a many to many relationship between contract specification objects and market identifier objects (e.g.

Abstract: A technique is described for generating error buffer that includes errors from both a program and event handlers called by the program. A program in an event-driven environment triggers an event. In response to the triggered event, the program calls event handlers related to the event. The event handlers are executed and error messages generated during the execution are stored in a local error buffer. Upon completion of the event handlers, the local error buffers are returned to the program and the program merges the local error buffers with an error buffer associated with the program.

Abstract: Disclosed are techniques employed alone or in combination, to further enhance a database language and improve conciseness and comprehensiveness of query statements in application code. Embodiments may build upon an initial extension of database language to accommodate concepts of entity-relationship models (ERMs). That initial extension may include entities with structured types, and named associations. One technique modifies SQL to allow the SELECT command to specify element path expressions based upon a relationship (e.g. named associations between ERM elements). Another technique modifies SQL to introduce filter expressions suffixed to associations within path expressions, thus improving adherence to the principle of locality within query statements. Yet another technique allows a shorthand to “factor out” association path prefixes, thereby avoiding lengthy lists of path expressions in order to read several elements from the same nested structure or a same target entity behind a single association.

Abstract: A database language is extended to define constraints on a data model (e.g., entity-relationship model) rather than the concrete database. The constraints can be declarative (e.g., constraints that are defined using expressions of the database language) or programmatic (e.g., constraints that are defined as a stored procedure implemented in a domain specific language). By storing the constraints at a higher level than the database level, the constraints can be performed without changing the persistency of the database. Also disclosed are techniques for handling of constraints on partially loaded entities.

Abstract: Technologies are disclosed for pruning a dependency graph representing source artifacts compilable by a plurality of compilers. The dependency graph can include strongly connected components represented as a directed acyclic graph. During compilation of the source artifacts, it can be discovered that some source artifacts did not need to be compiled, and associated nodes in the dependency graph can be pruned. Pruning can result in removal of nodes for source artifacts that are yet to be compiled, and compilation for source artifacts associated with such nodes in the dependency graph can be avoided.

Abstract: The method includes generating at least one base object, and generating at least one extendable object associated with the base object, the extendable object defining an insertion point and is configured to enable addition of new functionalities to an application including the at least one base object.

Abstract: A system may include a record generator to receive a plurality of documents associated with a plurality of suppliers and provide supplier-specific data records based thereon. The record generator may include an event classifier configured to execute a supplier-independent, event-based classification of each document, to thereby obtain event-classified documents. The record generator may include a supplier query generator configured to query the plurality of documents to obtain potential supplier matches from the plurality of suppliers, and a supplier match analyzer configured to analyze each potential supplier match of the potential supplier matches, to thereby obtain supplier matches. The record generator may include a supplier relevance analyzer configured to relate, for each event-classified document, any supplier identified therein to at least one event of the event-classified document, to thereby obtain supplier-event relationships.

Abstract: Systems and methods for determining alternative visual analytics for a particular business object in response to user requests to change the dimensions of a previously generated visual analytic are disclosed herein. By analyzing the request to change the dimensions, an alternative visual analytic pattern that includes suitably dimensioned visualizations is determined. The alternative visual analytic pattern includes a description of a particular visualization and defines how to generate a corresponding visual analytic. Based on the alternative visual analytic pattern, a modified report definition can be generated. The Modified report definition, that includes analytical operations with dimensions corresponding to the request, can be executed on the business object to generate modified analytic data. A new modified visual analytic that comprises a visual representation of the modified analytic data is then generated based on the alternative visual analytic pattern.

Abstract: Various embodiments herein each include at least one of systems, methods, and software for table-form presentation of hierarchical data. Some such embodiments include aggregating a hierarchical dataset as it may be stored in several rows of each of one to many tables or other similar data storage structures, grouping data according to the hierarchy, and writing the data in hierarchical groups to a table structure.

Abstract: An event type generator may provide a training set for classifying documents with respect to an event type. The event type generator may include a request handler to receive the event type and at least one example document, a text analyzer to extract first entities from the at least one example document, and a result manager to execute a first search against an indexed corpus of documents, to obtain first search results, and further to receive at least one selected document from the first search results. The request handler may extract second entities from the at least one selected document, and execute a second search against the indexed corpus of documents, to obtain second search results. The event type generator may thus provide the at least one example document, the first search results, and the second search results as the training set.

Abstract: The embodiments provide a system for measuring user productivity in developing a business process using one or more development tools. The system may include a productivity tacking unit configured to provide a user productivity model for measuring user productivity. The user productivity model may identify at least one business function associated with a process to be implemented by one or more development tools, at least one composition pattern, and a plurality of effort drivers associated with the at least one composition pattern. The productivity tracking unit is configured to receive development tracking information based on the user productivity model. The system may also include a report generator unit configured to generate at least one report characterizing the user productivity in developing at least a portion of the process based on the user productivity model and the development tracking information.

Abstract: A method includes recording audit results from an audit being conducted on a computer searchable storage device, recording supporting documentation on the computer searchable storage device, searching the storage device for similar prior audits to reveal fraud patterns utilizing a database search engine, and correlating the fraud patterns with the audit being conducted.

Abstract: A data object can be received at a first time at a first inbound interface of a first software component from a second software component. The first inbound interface can be configured to map a first feature of the data object to at least one first internal data structure of the first software component but not configured to map a second data feature of the data object to any corresponding internal data structure of the first software component. Characteristic information of the second data feature can be stored in a generic data container added to the internal data structure. The characteristic information can include a value of the second data feature and metadata describing an identifier of the second data feature. A reconstructed data object can be formed at a second time subsequent to the first time. Related methods, systems, and articles of manufacture are disclosed.

Abstract: Methods and apparatuses enable generation of an executed workload electronic record. The executed workload record indicates data related to one or more performance metrics by which performance of a work task is evaluated. One such performance metric is an expected time for completion of the task. Performance of the task can be monitored to determine an actual completion time for the task to compare against an expected completion time. The executed workload record can be used for evaluation of workers. Executed workload records provide centralized, aggregatable information for evaluation purposes.

Abstract: The subject matter disclosed herein provides methods and apparatus, including computer program products, for task decomposition of a task of a workflow. In one aspect there is provided a method. The method may include selecting, for decomposition, a task from a workflow including a plurality of tasks; indicating whether one or more portions of information associated with the decomposed task are restricted; and providing, to another user interface, the decomposed task including the one or more restricted portions. The received command is executed at the database. Related systems, apparatus, methods, and/or articles are also described.

Abstract: A method and system includes a bill of materials stored on a computer readable storage device, listing multiple components to be assembled. A mapping table is stored on a computer readable storage device having rows listing attributes of components of the bill of materials and a routing operation attribute identifying work centers or another unique attribute. A plurality of routing templates stored on a computer readable storage device, the routing templates identifying work centers and routing operations between work centers. A route generator utilizes the mapping table to map components from the bill of materials to a routing template and its operations.