Abstract:
Transactional data associated with a specific instance of a business scenario that includes an intersecting process feature requiring prerequisite action by a prerequisite process feature that is part of another business scenario can be linked to a scenario model providing a linearized representation in which other process features of the business scenario, the intersecting process feature, and the prerequisite process feature are arranged in a linear sequence. A navigation pane including a linear progression of user interface elements representing the linear sequence can be concurrently displayed with a work pane including other user interface elements corresponding to functionality provided by business software architecture features related to a currently selected process feature. The navigation pane display can expand at a selected user interface element to display additional user interface elements corresponding to process features involved in completion of the process feature corresponding to the selected first user interface element.
Abstract:
Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing an internal projects application useful for planning and executing internal projects and measures, including network scheduling, resource staffing, cost estimation and management, time confirmation, and progress monitoring. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service interface operations, each being implemented for a respective process component. The process components include a Costing process component that maintains project cost estimates; an Accounting process component that records relevant business transactions; a Project Management process component that structures, plans and executes simple, short-term measures and complex projects; and a Time and Labor Management process component that supports the definition of employees' planned working times as well as the recording of the actual working times and absences and their evaluation.
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 interface operations, each being implemented for a respective process component. The process components include an Inbound Delivery Processing process component, a Material Inspection Processing process component, a Site Logistics Processing process component, a Confirmation and Inventory 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 view object is generated in a target deployment unit in a design time environment of a metadata repository. The view object is modeled on a business object of a source deployment unit. The source deployment unit includes process components of a business application that is physically decoupled from the target deployment unit. A subset of attributes of the business object of the source deployment unit is selected. The subset of attributes includes at least an outbound agent and an inbound agent implemented by a generic messaging framework. The view object is modeled in the target deployment unit with the subset of attributes of the business object. The inbound agent of the view object is configured for receiving a replication message from the outbound agent of the business object, and the replication message includes replication data for configuring the view object only with data from the business object.
Abstract:
Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing strategic sourcing. 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 a Purchasing Contract Processing process component, a Supplier Invoicing process component, a Product Catalog Authoring process component, and a Source of Supply Determination process component.
Abstract:
A current transactional context of a user of a business software architecture can be detected, optionally in response to a guidance request received from the user. At least one matching business process feature related to the current transactional context can be determined by comparing the current transactional context with process metadata in a process repository, and the matching business process feature can be compared to scenario metadata defining a set of business process features that are part of each of a plurality of business scenarios within the business configuration to identify at least one matching business scenario containing the matching business process feature. In a user interface, the at least one matching business process feature and the identified matching business scenario that contains the at least one matching business process feature can be highlighted.
Abstract:
Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having accounting 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 self-service procurement used to procure goods and services “ad hoc” by requests from within an organization. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service interface operations, each being implemented for a respective process component. The process components include an Accounting process component, an Internal Request Processing process component, a Purchase Request Processing process component, a Purchase Order Processing process component, a Goods and Service Acknowledgement process component, a Supplier Invoice Processing process component, a Payment Processing process component, an RFQ Processing process component, and a Due Item Processing process component.
Abstract:
Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing time recording. The application is structured as multiple process components interacting with each other through service interfaces, and multiple service interface operations, each being implemented for a respective process component. The process components include a Project Processing component that is responsible for structuring, planning, and executing measures or projects, a Time and Labor Management process component that supports the definition of employees' planned working time as well as the recording or the actual working times and absences, an Accounting process component that records relevant business transactions, and a Goods and Service Acknowledgement process component that includes the Goods and Service Acknowledgement business object, which is a document that states the recipient's obligation to pay the supplier for goods received or services rendered.
Abstract:
A view object is generated in a target deployment unit in a design time environment of a metadata repository. The view object is modeled on a business object of a source deployment unit. The source deployment unit includes process components of a business application that is physically decoupled from the target deployment unit. A subset of attributes of the business object of the source deployment unit is selected. The subset of attributes includes at least an outbound agent and an inbound agent implemented by a generic messaging framework. The view object is modeled in the target deployment unit with the subset of attributes of the business object. The inbound agent of the view object is configured for receiving a replication message from the outbound agent of the business object, and the replication message includes replication data for configuring the view object only with data from the business object.