Abstract: A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to an appointment activity business object.

Abstract: A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to an email activity business object.

Abstract: A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a task activity business object.

Abstract: A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to an appointment activity business object.

Abstract: A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a phone call business object.

Abstract: A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to an email activity business object.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having customer relationship management functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Abstract: Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing plan-driven procurement. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service operations, each being implemented for a respective process component. The process components include an Inbound Delivery Processing process component, a Site Logistics Processing process component, an Inventory Processing process component, a Purchase Request Processing process component, a Purchase Order Processing process component, a Purchasing Contract process component, a Supplier Invoice Processing process component, a Demand Forecast Processing process component, a Supply and Demand Matching process component, an External Procurement Trigger and Response process component, and a Logistics Execution Control process component.

Abstract: A system may include reception of an instruction to create a next meeting based on a source meeting, the source meeting associated with a first plurality of meeting particulars, and automatically creation, in response to the instruction, of the next meeting in association with a second plurality of meeting particulars, wherein at least one of the second plurality of meeting particulars provides an indication of the source meeting.

Abstract: Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing plan-driven procurement. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service operations, each being implemented for a respective process component. The process components include an Inbound Delivery Processing process component, a Site Logistics Processing process component, an Inventory Processing process component, a Purchase Request Processing process component, a Purchase Order Processing process component, a Purchasing Contract process component, a Supplier Invoice Processing process component, a Demand Forecast Processing process component, a Supply and Demand Matching process component, an External Procurement Trigger and Response process component, and a Logistics Execution Control process component.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having customer relationship management functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Abstract: Systems and methods are described that permit a user to configure an identification strategy at run time to facilitate user input of data. The identification strategy may include a parsing grammar and a search algorithm. The parsing grammar may be used to parse user input, and the search algorithm may be used to search a database for the user input. A configuring user may configure the parsing grammar at run time to accept data in a customized form to suit the user's input style. The search algorithm may be configured accordingly as well.

Abstract: In a computing system, an operation is performed on an instance of a data object. One of several persistence models that are available for the data object is identified for the instance using the performed operation, where each of the several persistence models defines how the data object is to be persisted in a database. The instance is stored in the database according to the identified persistence model. The persistence model may be identified at run time in a manner transparent to a user. A first persistence model may be identified for a first instance of the data object and a second persistence model, different from the first persistence model, may be identified for a second instance of the data object. An object instance may later be stored according to another persistence model.

Abstract: A system may include reception of an instruction to create a next meeting based on a source meeting, the source meeting associated with a first plurality of meeting particulars, and automatically creation, in response to the instruction, of the next meeting in association with a second plurality of meeting particulars, wherein at least one of the second plurality of meeting particulars provides an indication of the source meeting.

Abstract: In a computing system, an indication of a predefined transaction participant role in which a specified participant serves in a specified computer-implemented transaction is received. An association between the indicated predefined transaction participant role and a predefined master code is determined. Previously stored master data that is associated with the specified participant and with the associated predefined master code is retrieved, and the retrieved master data is used during the specified computer-implemented transaction involving the specified participant.

Abstract: Systems and methods are described that permit a user to configure an identification strategy at run time to facilitate user input of data. The identification strategy may include a parsing grammar and a search algorithm. The parsing grammar may be used to parse user input, and the search algorithm may be used to search a database for the user input. A configuring user may configure the parsing grammar at run time to accept data in a customized form to suit the user's input style. The search algorithm may be configured accordingly as well.

Abstract: In a computing system, an operation is performed on an instance of a data object. One of several persistence models that are available for the data object is identified for the instance using the performed operation, where each of the several persistence models defines how the data object is to be persisted in a database. The instance is stored in the database according to the identified persistence model. The persistence model may be identified at run time in a manner transparent to a user. A first persistence model may be identified for a first instance of the data object and a second persistence model, different from the first persistence model, may be identified for a second instance of the data object. An object instance may later be stored according to another persistence model.

Abstract: Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having customer relationship management functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.

Abstract: The present subject matter, in various embodiments, provides systems, software, and methods to automatically determine roles to include, and not include, in documents. Some embodiments further include populating the roles in documents. Determining roles to include and not include, in some embodiments, includes branching decisions, the result of which can be to include one of multiple roles, or not including a role.

Abstract: First data identifying a resource, a calendared appointment associated with the resource, and a participant in the calendared appointment may be received and subsequently associated with second data (e.g., at least one link to information available via a communications network and/or a data file). Thereafter, third data may be transmitted over the communications network to a node associated with the participant to modify the calendared appointment to include the second data. In one variation, data identifying a resource and a calendared appointment associated with the resource may be received via a communications network. Based on such data, a usage statistic may be calculated for the resource based on a length of time of the calendared appointment. Related apparatuses, systems, computer program products are also described.