Abstract: A bulk service interface can be instantiated for each of at least one service provider providing a plurality of business objects using a stored definition of a plurality of metadata properties relating to generation of a user interface that incorporates content of a plurality of business objects. The bulk service interface can query the stored definition and access, in a bulk metadata access process, dynamic metadata required for instantiation of the plurality of business objects. If the stored definition has not previously been received, a default bulk services access process that queries an existing dynamic metadata access interface of each of the plurality of business objects can be initiated to retrieve the dynamic metadata from each of the plurality of business objects. An instance of the user interface can be generated using dynamic metadata accessed by the bulk service interface and/or the retrieved by the default bulk services access process.

Abstract: Techniques are described in which indication of a computer application to be configured for use in a particular business enterprise is received. A mass data run object is identified. The mass data run object defines a computer operation to be performed by the computer application to transform business transaction data as part of a business process. The mass data run object identifies i) selection parameters to select business transaction data to be transformed by the computer operation defined by the mass data run object and ii) instructions, that when executed, perform the computer operation to transform the selected business transaction data. A mass data run object instance corresponding to the identified mass data run object is generated and scheduled for execution.

Abstract: A computerized method for accessing business object data stored in a data buffer of a server computer includes providing an application program interface (API) having a function for specifying a set of paths through a business object stored as a data structure in a data buffer of a server computer. Each of the paths included in the set of paths specifies a plurality of nodes of the business object for accessing hosted data at the plurality of nodes. The method further includes receiving a set of parameters for the function of the API. The set of parameters specify the set of paths. The method further includes issuing the set of parameters to the server computer, retrieving hosted data from the plurality of nodes for each path in the set of paths; and transmitting to a client the hosted data retrieved from the plurality of nodes.

Abstract: A computer system includes instructions recorded on a computer-readable storage medium and executable by at least one processor. The computer system includes a process component of a first deployment unit and a component module. The process component has a handling module and an object module. The handling module is operatively coupled to the object module. The handling module is operatively coupled to the component module. The handling module is configured to receive a message from a second deployment unit.

Abstract: Methods and apparatus, including computer program products, are provided for providing a query language based on a model. In one aspect, there is provided a computer-implemented method. The method may include receiving a first query; generating, based on a model including metadata representing a data structure, a second query specific to the data structure stored in a database; and sending the second query to the database. Related apparatus, systems, methods, and articles are also described.

Abstract: A bulk service interface can be instantiated for each of at least one service provider providing a plurality of business objects using a stored definition of a plurality of metadata properties relating to generation of a user interface that incorporates content of a plurality of business objects. The bulk service interface can query the stored definition and access, in a bulk metadata access process, dynamic metadata required for instantiation of the plurality of business objects. If the stored definition has not previously been received, a default bulk services access process that queries an existing dynamic metadata access interface of each of the plurality of business objects can be initiated to retrieve the dynamic metadata from each of the plurality of business objects. An instance of the user interface can be generated using dynamic metadata accessed by the bulk service interface and/or the retrieved by the default bulk services access process.

Abstract: Embodiments of the present invention may provide a system and method for providing real time analytics and reporting across networked applications. The real time analytics and reporting across networked applications may be provided by extending the reporting metadata and the corresponding design- and runtime-tools. Based on a cross NWAs MDAV-Definition, the corresponding metadata (subview and subquery definitions) may be generated and assigned to the corresponding NWA-Layer (NWA software component). At deployment and configuration time, the relevant views may be activated depending availability of underlying data. At runtime, an MDAV executer (e.g., a MDAV runtime engine) may run a distributed and optimized provisioning of reporting and analytics data. The data provisioning scheme may depend on selection parameters, filters, join conditions between parts in different NWAs, analytical functions defined in the report, and the locality of the data (local or remote).

Abstract: Methods and apparatus, including computer program products, are provided for providing value help. In one aspect, there is provided a computer-implemented method. The method may include receiving at least one field of a row of a list presented at a user interface; transforming, at a service component rather than the user interface, the at least one field into a query; and sending the transformed query to a database. Related apparatus, systems, methods, and articles are also described.

Abstract: Embodiments of the invention relate to computing, and in particular, to a systems and methods for a querying a database. Certain embodiments implement a model-driven database query (“the SADL query”) facilitating a design-time tool that allows a developer to create the query based upon existing Business Objects (BOs) and their associations. This SADL query leverages mapping between business-layer entities and database-layer entities, such mapping being derived from association metadata already extant in the business model used to create the Business Objects. In certain embodiments, query views may be based upon associations present within the business layer, rather than upon database-level entities (such as joins or restriction rules) that are typically relied upon in conventional query creation. Embodiments of the present invention may thus align query creation more closely with the structure of the business layer, and may also render query design agnostic relative to the identity of the underlying database.

Abstract: Aspects of the current subject matter can provide a background job repository that stores a background job template specifying a background job comprising a maintenance task that affects a customized software platform. The background job template can also include metadata defining a purpose of the background job, triggering information indicating when the background job should be executed, and a prerequisite feature of the customized software platform that indicates a need for the background job in the customized software platform. A previous set of background jobs that run in the customized software platform can be updated to a current set by comparing the previous set with the background job template and including the background job in the current set of background jobs when the customized software platform includes the prerequisite feature.

Abstract: Methods and systems are described that involve holistic and flexible operational reporting that does not require transformation of the underlying model or data harmonization since all business data and business logic of standard business processes are modeled and exposed in a standardized way using domain specific language and the operational reports are modeled with the same meta-model as the business data. A user can simply create a given operational report by selecting needed reporting elements of one or more business objects, run the report, and see the results.

Abstract: The addition of a datastore to an application system using process agents for communication allows for maintaining a persistent state by storing records of messages sent between process agents. These records may be retrievable by process agents in order to determine the state of the system. This allows process agents to update previous transactions without storing a copy of messages within each process agent or communicating with every potentially involved process agent to determine its current state.

Abstract: Techniques are described in which indication of a computer application to be configured for use in a particular business enterprise is received. A mass data run object is identified. The mass data run object defines a computer operation to be performed by the computer application to transform business transaction data as part of a business process. The mass data run object identifies i) selection parameters to select business transaction data to be transformed by the computer operation defined by the mass data run object and ii) instructions, that when executed, perform the computer operation to transform the selected business transaction data. A mass data run object instance corresponding to the identified mass data run object is generated and scheduled for execution.

Abstract: It is determined whether at least one request to replicate at least one business object is valid. The business object comprising a plurality of hierarchically arranged nodes, with a root node on a first end, at least one leaf node on a second end, and at least one intermediate node disposed between the root node and the at least one leaf node. Thereafter, a valid path from the root node to replication nodes within each business object specified in the at least one request is determined if it was determined that corresponding request is valid. A replication tree is then generated based on the determined valid path. The replication tree is then traversed and an association is returned when stopping on a leaf node and a replication node is returned when traversing a node to be replicated. A retrieve by association service is executed when an association is returned, otherwise, a retrieve service is executed.

Abstract: System and methods are described for automatically determining the responsible agent for a given task. Using a task grammar, a task constructor constructs a request description. A responsibility request, including the request description, is formulated. A rules engine queries a database and determines, given the request description, the responsible agent for the given task by matching the request description with a task description in the database and returning the responsible agent associated with the task description.

Abstract: The addition of a datastore to an application system using process agents for communication allows for maintaining a persistent state by storing records of messages sent between process agents. These records may be retrievable by process agents in order to determine the state of the system. This allows process agents to update previous transactions without storing a copy of messages within each process agent or communicating with every potentially involved process agent to determine its current state.