Architectural design for service request and order management application software

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing service request and order management. 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 Outbound Delivery process component, a Site Logistics Processing process component, a Confirmation and Inventory process component, a Customer Requirement Processing process component, a Supply and Demand Matching process component, a Logistics Execution Control process component, a Service Request Processing process component, a Customer Quote Processing process component, a Service Order Processing process component, a Service Contract process component, and a Service Confirmation Processing process component.

BACKGROUND

The subject matter of this patent application relates to computer software architecture, and more particularly to the architecture of application software for service request and order management.

Enterprise software systems are generally large and complex. Such systems can require many different components, distributed across many different hardware platforms, possibly in several different geographical locations. Thus, the architecture of a large software application, i.e., what its components are and how they fit together, is an important aspect of its design for a successful implementation.

SUMMARY

This specification presents a software architecture design for a software application.

Methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing service request and order management. 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 Outbound Delivery process component, a Site Logistics Processing process component, a Confirmation and Inventory process component, a Customer Requirement Processing process component, a Supply and Demand Matching process component, a Logistics Execution Control process component, a Service Request Processing process component, a Customer Quote Processing process component, a Service Order Processing process component, a Service Contract process component, and a Service Confirmation Processing process component.

The invention can further be implemented as methods, systems, and apparatus, including computer program products, implementing a software architecture design for a software application that is adapted to interact with external software systems through the service operations described in reference to external process components, or a subcombination of them.

The subject matter described in this specification can be implemented to realize one or more of the following advantages. Effective use is made of process components as units of software reuse, to provide a design that can be implemented reliably in a cost effective way. Effective use is made of deployment units, each of which is deployable on a separate computer hardware platform independent of every other deployment unit, to provide a scalable design. Service interfaces of the process components define a pair-wise interaction between pairs of process components that are in different deployment units in a scalable way.

DETAILED DESCRIPTION

FIG. 1shows the software architectural design for a Service Request and Order Management software application. The Service Request and Order Management application is software that implements Describes operational processes in a customer service and support center based on Service Requests, Service Orders and Service Confirmations including their integration into related applications such as invoicing, financial accounting and logistics.

As shown inFIG. 1, the Service Request and Order Management design includes seven deployment units: a Financial Accounting deployment unit102, a Logistics Execution deployment unit104, a Supply Chain Control deployment unit106, a Due Item Management deployment unit108, a Payment deployment unit110, a Customer Invoicing deployment unit112, and a Customer Relationship Management deployment unit114.

The Financial Accounting deployment unit contains an Accounting process component103that records all relevant business transactions.

The Logistics Execution deployment unit104includes three process components: an Outbound Delivery process component116, a Site Logistics Processing process component118, and a Confirmation and Inventory process component120.

The Outbound Delivery process component116combines tasks concerning outbound delivery processes and enables communication with a vendor and a process component within the Invoice deployment unit. For example, the Outbound Delivery process component116may prepare and trigger execution of physical operations associated with an invoice.

The Site Logistics Processing process component118supports all preparation and execution tasks concerning internal inventory movement in a warehouse type environment.

The Site Logistics Processing process component118may provide stock information such as special stock items. Exception and alert information may also be provided by the Site Logistics Processing process component118.

The Confirmation and Inventory process component120combines all tasks required to confirm inventory changes and provided activities. The Confirmation and Inventory process component120may provide services to maintain current stock, handling unit content, logistics operating unit content and allocation content.

The Supply Chain Control deployment unit106includes three process components: a Customer Requirement Processing process component122, a Supply and Demand Matching process component124, and a Logistics Execution Control process component126.

The Customer Requirement Processing process component122combines the tasks required for processing customer requirements and provides an interface to presales, sales and services. The Customer Requirement Processing process component122receives the customer requirements, prepares them and passes them on to the Supply and Demand Matching process component124as supply planning requirements.

The Supply and Demand Matching process component124combines all the tasks necessary to ensure that sufficient material receipt elements exist to cover material demand while taking available capacity into account. For example, the supply and demand matching process component124may collect all the various material demands from customer requirement processing, the in-house requirement processing, the demand forecast processing, and the sales scheduling agreement processing and attempt to assign all the existing material receipts. The matching component may also plan the internal or external procurement of further material receipts where necessary.

The Logistics Execution Control process component126controls and monitors the supply chain execution activities necessary for the fulfillment of an order. For example, sales order activities or purchase order activities may be controlled and monitored by the logistics execution control process component. The Logistics Execution Control process component126sends information to the logistics execution to trigger the necessary supply chain execution activities, receives information about the supply chain execution progress, and updates data relevant for both fulfillment and supply and demand planning.

The Due Item Management deployment unit108includes a Due Item Processing process component128. The Due Item Processing process component128is used to manage all payables, receivables from service and supply and corresponding sales including a withholding tax.

The Payment deployment unit110includes a Payment Processing process component130. The Payment Processing process component130is used to handle all incoming and outgoing payments as well as represent the main database for a liquidity status.

The Customer Invoice deployment unit112includes a Customer Invoice Processing process component132used to charge a customer for the delivery of goods or services.

The Customer Relationship Management deployment unit114includes five process components: a Service Request Processing process component134, a Customer Quote Processing process component136, a Service Order Processing process component138, a Service Contract process component140, and a Service Confirmation Processing process component142.

The Service Request Processing process component134covers requests from a customer to a service provider to answer a question or solve a problem about a product that the customer possesses. The goal is to solve this problem as quickly as possible, for example, solving the problem on the phone by a service desk agent with the help of a knowledge base.

The Customer Quote Processing process component136is used to offer to a customer for the delivery of goods or services according to fixed terms. The offer legally binds the company for a certain period of time.

The Service Order Processing process component138deals with short-term agreements between a customer and a service provider, in which the customer orders one-off services. For example, an order could be to maintain or repair some equipment making it necessary to send a technician along with spare parts. Typically, these services are billed services. The service order is also used to schedule resources and plan availability of spare parts, and can include extra expenses required to execute service jobs (for example, travel expenses).

The Service Contract Processing process component140deals with long-term agreements between a customer and a service provider, specifying the scope of services and general conditions (for example, service levels and prices) used for processing service requests and service orders.

The Service Confirmation Processing process component142is used to deal with services rendered for a service order. This includes reporting back working times, materials used, as well as any expenses incurred during the service activities. These particulars are used as a basis for keeping track of working times, updating stock levels for spare parts, processing invoices, and cost accounting.

A number of external process components, described below, will be used to describe the architectural design. These include a Service Request Processing in External Requester System process component144, a Service Request Processing in External Provider System process component146, a Supplier Invoice Processing at Customer process component148, a Payment Processing at Business Partner process component150, a Bank statement creation at bank process component152, and a Payment order processing at house bank process component154.

FIG. 2illustrates the elements of the architecture as they are drawn in the figures of this patent application. The elements of the architecture include the business object (drawn as icon202), the process component (drawn as icon204), the operation (drawn as icon206), the process agent (drawn as icon208), the service interface or interface (drawn as icon210), the message (drawn as icon212), and the deployment unit (drawn as icon214).

Not explicitly represented in the figures is a foundation layer that contains all fundamental entities that are used in multiple deployment units. These entities can be process components, business objects and reuse service components. A reuse service component is a piece of software that is reused in different transactions. A reuse service component is used by its defined interfaces, which can be, e.g., local APIs (Application Programming Interfaces) or service interfaces.

In contrast to a deployment unit, the foundation layer does not define a limit for application-defined transactions. Deployment units communicate directly with entities in the foundation layer, which communication is typically not message based. The foundation layer is active in every system instance on which the application is deployed. Business objects in the foundation layer will generally be master data objects. In addition, the foundation layer will include some business process objects that are used by multiple deployment units. Master data objects and business process objects that should be specific to a deployment unit are assigned to their respective deployment unit.

A process component of an external system is drawn as a dashed-line process component (drawn as icon216). Such a process component may be referred to as an external process component, and it is used to represent the external system in describing interactions with the external system; however, this should be understood to require no more of the external system that it be able to produce and receive messages as required by the process component that interacts with the external system.

The connector icon218is used to simplify the drawing of interactions between process components.

Interactions between process component pairs involving their respective business objects, process agents, operations, interfaces, and messages are described as process component interactions, which determine the interactions of a pair of process components across a deployment unit boundary, i.e., from one deployment unit to another deployment unit. Interactions between process components are indicated inFIG. 1by directed lines (arrows). Interactions between process components within a deployment unit need not be described except to note that they exist, as these interactions are not constrained by the architectural design and can be implemented in any convenient fashion. Interactions between process components that cross a deployment unit boundary will be illustrated by the figures of this patent application; these figures will show the relevant elements associated with potential interaction between two process components, but interfaces, process agents, and business objects that are not relevant to the potential interaction will not be shown.

The architectural design is a specification of a computer software application, and elements of the architectural design can be implemented to realize a software application that implements the end-to-end process mentioned earlier. The elements of the architecture are at times described in this specification as being contained or included in other elements; for example, a process component is described as being contained in a deployment unit. It should be understood, however, that such operational inclusion can be realized in a variety of ways and is not limited to a physical inclusion of the entirety of one element in another.

The architectural elements include the business object. A business object is a representation of a type of a uniquely identifiable business entity (an object instance) described by a structural model. Processes operate on business objects.

A business object represents a specific view on some well-defined business content. A business object represents content, which a typical business user would expect and understand with little explanation. Business objects are further categorized as business process objects and master data objects. A master data object is an object that encapsulates master data (i.e., data that is valid for a period of time). A business process object, which is the kind of business object generally found in a process component, is an object that encapsulates transactional data (i.e., data that is valid for a point in time). The term business object will be used generically to refer to a business process object and a master data object, unless the context requires otherwise. Properly implemented, business objects are implemented free of redundancies.

The architectural elements also include the process component. A process component is a software package that realizes a business process and generally exposes its functionality as services. The functionality contains business transactions. A process component contains one or more semantically related business objects. Any business object belongs to no more than one process component.

Process components are modular and context-independent. That they are context-independent means that a process component is not specific to any specific application and is reusable. The process component is the smallest (most granular) element of reuse in the architecture.

The architectural elements also include the operation. An operation belongs to exactly one process component. A process component generally has multiple operations. Operations can be synchronous or asynchronous, corresponding to synchronous or asynchronous process agents, which will be described below. An operation is the smallest, separately-callable function, described by a set of data types used as input, output, and fault parameters serving as a signature.

The architectural elements also include the service interface, referred to simply as the interface. An interface is a named group of operations. Each operation belongs to exactly one interface. An interface belongs to exactly one process component. A process component might contain multiple interfaces. In one implementation, an interface contains only inbound or outbound operations, but not a mixture of both. One interface can contain both synchronous and asynchronous operations. All operations of the same type (either inbound or outbound) which belong to the same message choreography will belong to the same interface. Thus, generally, all outbound operations to the same other process component are in one interface.

The architectural elements also include the message. Operations transmit and receive messages. Any convenient messaging infrastructure can be used. A message is information conveyed from one process component instance to another, with the expectation that activity will ensue. An operation can use multiple message types for inbound, outbound, or error messages. When two process components are in different deployment units, invocation of an operation of one process component by the other process component is accomplished by an operation on the other process component sending a message to the first process component.

The architectural elements also include the process agent. Process agents do business processing that involves the sending or receiving of messages. Each operation will generally have at least one associated process agent. A process agent can be associated with one or more operations. Process agents can be either inbound or outbound, and either synchronous or asynchronous.

Asynchronous outbound process agents are called after a business object changes, e.g., after a create, update, or delete of a business object instance.

Synchronous outbound process agents are generally triggered directly by a business object.

An output process agent will generally perform some processing of the data of the business object instance whose change triggered the event. An outbound agent triggers subsequent business process steps by sending messages using well-defined outbound services to another process component, which generally will be in another deployment unit, or to an external system. An outbound process agent is linked to the one business object that triggers the agent, but it is sent not to another business object but rather to another process component. Thus, the outbound process agent can be implemented without knowledge of the exact business object design of the recipient process component.

Inbound process agents are called after a message has been received. Inbound process agents are used for the inbound part of a message-based communication. An inbound process agent starts the execution of the business process step requested in a message by creating or updating one or multiple business object instances. An inbound process agent is not the agent of a business object but of its process component. An inbound process agent can act on multiple business objects in a process component.

Synchronous agents are used when a process component requires a more or less immediate response from another process component, and is waiting for that response to continue its work.

Operations and process components are described in this specification in terms of process agents. However, in alternative implementations, process components and operations can be implemented without use of agents using other conventional techniques to perform the functions described in this specification.

The architectural elements also include the deployment unit. A deployment unit includes one or more process components that are deployed together on a single computer system platform. Conversely, separate deployment units can be deployed on separate physical computing systems. For this reason, a deployment unit boundary defines the limits of an application-defined transaction, i.e., a set of actions that have the ACID properties of atomicity, consistency, isolation, and durability. To make use of database manager facilities, the architecture requires that all operations of such a transaction be performed on one physical database; as a consequence, the processes of such a transaction must be performed by the process components of one instance of one deployment unit.

The process components of one deployment unit interact with those of another deployment unit using messages passed through one or more data communication networks or other suitable communication channels. Thus, a deployment unit deployed on a platform belonging one business can interact with a deployment unit software entity deployed on a separate platform belonging to a different and unrelated business, allowing for business-to-business communication. More than one instance of a given deployment unit can execute at the same time, on the same computing system or on separate physical computing systems. This arrangement allows the functionality offered by a deployment unit to be scaled to meet demand by creating as many instances as needed.

Since interaction between deployment units is through service operations, a deployment unit can be replaced by other another deployment unit as long as the new deployment unit supports the operations depended upon by other deployment units. Thus, while deployment units can depend on the external interfaces of process components in other deployment units, deployment units are not dependent on process component interaction within other deployment units. Similarly, process components that interact with other process components or external systems only through messages, e.g., as sent and received by operations, can also be replaced as long as the replacement supports the operations of the original.

Interactions between Process Components “Customer Quote Processing” and “Customer Requirement Processing”

FIG. 3is a block diagram showing interactions between a Customer Quote Processing process component302and a Customer Requirement Processing process component304in the architectural design ofFIG. 1.

The Customer Quote Processing process component302includes a Customer Quote business object306. The Customer Quote business object306is a document containing an offer by a vendor to a customer for the delivery of goods or services according to fixed terms. The offer is legally binding for a specific period of time. The Customer Quote business object306uses a Synchronous Request Availability Information from the Customer Quote to Customer Requirements outbound process agent308to send update information into a Fulfillment Out interface310.

The Fulfillment Out interface310may invoke one or more of three operations depending on the received data instructions: a synchronous Request Product Availability Information operation312to request availability information for customer quote items, a Request Product Availability Information and provisional Reservation operation314that requests availability information, including the creation of a provisional reservation for customer quote items, or a Register Customer Requirement Deletion Notification operation316that registers provisional requirement reservation for deletion and triggers deletion in case of failure or cancellation of transaction processing,

In addition, a second outbound process agent318(Request Reservation from Customer Quote to Customer Requirement) may send update information to the Fulfillment Out interface310, which may invoke a Request Customer Requirement Reservation operation320that requests fulfillment planning for customer quote items. A Customer Requirement Fulfillment Request message322may be sent to a Maintain Customer Requirement operation324in the Customer Requirement Processing process component304.

If the Request Product Availability Information operation312is performed, then an Availability Information Query message326is generated and sent to the Customer Requirement Processing process component304where the update is sent on to a Customer Requirement business object328using a Check Availability outbound process agent330. This update may be performed by a synchronous Check Availability operation332. The Customer Requirement business object328is a requirement document that is derived from a sales order or quotation and to which details on the anticipated availability date are added. It may contain the quantities of required products at specific dates, and information about which products and quantities will be available or delivered at which dates. In addition to forwarding information to the Customer Requirement business object328, the Check Availability operation332may send an Availability Information Response message333back to the Customer Quote Processing process component304.

Upon receiving the update, the Customer Requirement business object328sends the update to a Fulfillment Out interface334using a Confirm Customer Requirement outbound process agent336. The Fulfillment Out interface334invokes a Notify of availability update operation338that notifies the creator of a customer requirement about an updated availability situation for the products requested within the customer requirement. An Availability Update Notification message340is generated and sent into the Fulfillment In interface342in the Customer Quote process agent302.

The Fulfillment In interface302may invoke a Change Customer Quote based on Availability Update operation344that changes customer quote with availability and reservation information based on changes in fulfillment planning. An inbound process agent346(Change Customer Quote based on Availability Update) may send update information to the Customer Quote business object306.

If the Request Product Availability Information and Provisional Reservation operation314is performed, an Availability Check Request message348may be generated and sent to a Check availability and Reserve operation350that checks the availability of specific amounts of certain materials and confirms this availability to the caller in the Customer Requirement Processing process component304. The message348may be sent on to the Customer Requirement business object328and an Availability Check Confirmation message352may be sent back to the Customer Quote Processing process component302.

If the Register Customer Requirement Deletion Notification operation316is performed, a Customer Requirement Deletion Notification message354is generated and sent to a Delete Provisional Customer Requirement operation356that deletes provisional customer requirements that have been created by a sync check availability and reserve operation. The message354may be sent on to the Customer Requirement business object328using a Maintain Customer Requirement inbound process agent358.

Interactions between Process Components “Service Request Processing” and “Customer Invoice Processing”

FIG. 4is a block diagram showing interactions between a Service Request Processing process component402and a Customer Invoice Processing process component404in the architectural design ofFIG. 1.

The Purchase Request Processing process component302includes a Service Request business object406. The Service Request business object406contains a service notification reflecting the initial inquiry of a customer when contacting a customer service and support center.

In the Service Request Processing process component402, a Request Invoicing from Service Request to Customer Invoice Processing outbound process agent408requests the execution of a service request. The outbound process agent408uses a Request Invoicing operation410to send a Customer Invoice Request Request message412to the Customer Invoice Processing process component404. The Request Invoicing operation410is part of a Request Invoicing Out interface414.

The Customer Invoice Request Request message412is received by a Maintain Customer Invoice Request operation416, which creates, updates, deletes or requests cancellation of customer invoice requests in a Request Invoicing In interface418. The operation416initiates a Maintain Customer Invoice Request inbound process agent420.

The Customer Invoice Processing process component404includes a Customer Invoice Request business object422. The Customer Invoice Request business object422is used to charge a customer for delivery of goods or services.

The customer Invoice Processing process component404also includes a Customer Invoice business object423. A Confirm Customer Invoice outbound process agent424requests the execution of a Confirm Invoicing operation426that confirms that a customer invoice was created (or cancelled) to process components which requested the invoicing. The outbound process agent428uses a Confirm Invoicing operation426to send a Customer Invoice Issued Confirmation message430to the Service Request Processing process component402. The Confirm Invoicing operation426is part of a Request Invoicing Out interface428.

The Customer Invoice Issued Confirmation message430is received by a Change Service Request based on Customer Invoice operation432that documents information about issued customer invoice in the service request in a Request Invoicing In interface434. The operation432initiates a Change Service Request based on Customer Invoice inbound process agent434. The inbound process agent434updates the Service Request business object406.

Interactions between Process Components “Service Confirmation Processing” and “Customer Invoice Processing”

FIG. 5is a block diagram showing interactions between a Service Confirmation Processing process component502and a Customer Invoice Processing process component504in the architectural design ofFIG. 1. The Service Confirmation Processing process component502includes a Service Confirmation business object506that sends a request to a Request Invoice Out interface508using a Request Invoicing from Service Confirmation to Customer Invoice outbound process agent510. The Request Invoicing Out interface508invokes a Request Invoicing operation512that Requests invoicing of services provided and spare parts consumed as reported back in the service confirmation as actual values. Next, a Customer Invoice Request Request message514is generated and sent to the Customer Invoice Processing process component504where it is received in a Request Invoicing In interface516. A Maintain Customer Invoice Request517may then be invoked to create, update, delete or request a cancellation of customer invoice request. An update may be sent to a Customer Invoice Request business object518using a Maintain Customer Invoice Request inbound process agent520. The Customer Invoice Processing process component504may include a Customer Invoice business object519is used to charge a customer for delivery of goods or services.

The Customer Invoice Processing process component504may send a confirmation into a Request Invoicing Out interface522using a Confirmation Customer Invoice outbound process agent524. The Request Invoicing Out interface522may invoke a Confirm Invoicing operation526that confirms that customer invoice was created (or cancelled) to process components which requested invoicing. A Customer Invoice Issued Confirmation message528may then be generated and sent to the Request Invoicing In interface530in the Service Confirmation Processing process component502. Next, a Change Service Confirmation based on Customer Invoice operation532is invoked to document information about issued customer invoice in the service confirmation. A Change Service Confirmation based on Customer Invoice inbound process agent534updates the Service Confirmation business object506.

Interactions between Process Components “Service Request Processing” and “Service Request Processing in External Provider System”

FIG. 6is a block diagram showing interactions between a Service Request Processing process component602and a Service Request Processing in External Provider System process component604in the architectural design ofFIG. 1.

The Service Request Processing process component602includes a Service Request business object606. The Service Request business object606is a service notification reflecting the initial inquiry of a customer when contacting a Customer Service and Support Center. The Service Request business object606includes customer data, the nature of the request and the customer's product in question. In addition, text notes describing the issue and attributes that classify the request, the problem, reason, severity, and so on can be maintained. Service requests might also include immediate validation of existing service entitlements, such as agreed service levels and existing service contracts or product warranties. To ensure an appropriate reaction, prioritization and scheduling of request processing is set accordingly.

The Service Request business object606sends a request to an External Requesting Out interface608using a Request Service from Service Request to External Provider outbound process agent610. The External Request Out interface608invokes a Request Service operation612that sends Service Request Creation/Update data to an external provider system, thereby generating a Service Request message614to update the Service Request Processing in External Provider System process component604.

The Service Request Processing process component602may receive an incoming Service Request Confirmation message616from the Service Request Processing in External Provider System process component604. An External Requesting In interface618receives the message616and invokes a Change Service Request based on Provider's Confirmation operation620that updates a service request based on a confirmation message of a service request creation, update or processing progress received from an external provider system. A Change service Request based on External Provider's Request Confirmation inbound process agent622updates the Service Request business object606.

Interactions between Process Components “Logistics Execution Control” and “Site Logistics Processing”

FIG. 7is a block diagram showing interactions between a Logistics Execution Control process component702and a Site Logistics Processing process component704in the architectural design ofFIG. 1

Four business objects from the Demand Matching process component706are used in the Logistics execution Demand process component702: Planning View on Inventory708, which is a planning view on Inventory is an object that represents the inventory object from logistics execution, Supply Planning Requirement710, which is a requirement object that is used as the target for the supply planning run and the availability check, Procurement Planning Order712, which defines the requested or expected material receipt in a specific quantity and at a specific availability date, Planned Material Flow714, which is an object that defines the relationship between material receipt elements (stock, planned order, and a production order, purchase requisition, purchase order etc.) and material requirements elements (sales order, forecast demand, dependent demand, transfer demand) of a material within a location.

The business object716uses a Request Site Logistics Processing from Site Log Req to Site Logistics Processing outbound process agent718to send an update to the Request Site Logistics Processing process component704.

The Site Logistics Processing Out interface720includes a Request Site Logistics operation722to send a request in order to maintain the site logistics request. The Site Logistics Request message724may then be generated and sent to the Site Logistics Processing process component704.

The Site Logistics Processing In interface728includes a Maintain Site Logistics Request operation730that creates or updates a Site Logistics Processing Request. A Maintain Site Logistics Request inbound process agent732may send an update into a Site Logistics Request business object734. The Site Logistics Request business object734performs Site Logistics operations supporting outbound, inbound and site internal logistics activities at a certain time. A Confirm Site Logistics Request to Logistic Execution Control outbound process agent736may send updated information into a Site Logistics Processing Out interface738which includes a Confirm Site Logistics Request operation740that confirms receipt of request and acknowledges quantities and delivery dates. This operation740generates a Site Logistics Request Confirmation message742which will be sent to update the Logistics Execution Control process component702.

A Site Logistics Confirmation business object744may also send updated information into the Logistics Execution Control process component702using a Notify of Site Logistics Confirmation to Logistic Execution Control outbound process agent745. The Site Logistics Confirmation business object744is a document that collects actual data posted with reference to a site logistics order or site logistics request. The site logistics confirmation updates inventory, finance and planning. A Notify of Site Logistics Request Progress operation746may be invoked that informs logistics execution control about inventory changes and fulfillment of Site Logistics Processing. A Site Logistics Request Progress Notification message748may be generated to update the Logistics Execution Control process component702.

Upon receiving messages740and742, the Logistics Execution Control process component702may perform the following operations: 1. The Site Logistics Processing In interface750contains a Change Site Log Request Progress Notification operation752, which notifies Logistics execution control of inventory changes and confirmation of Site Logistics Processing. 2. The Site Logistics Processing In interface750also contains a Change Site Logistics Requisition based on Site Logistics Request Confirmation operation754that receives confirmation data from Site Logistics Request. A Maintain Site Logistics Requisition Based on Site Logistics inbound process agent756may then update the Site Logistics Requisition business object716.

Interactions between Process Components “Payment Processing at Business Partner” and “Payment Processing”

FIG. 8is a block diagram showing interactions between a Payment Processing at Business Partner process component802and a Payment Processing process component804in the architectural design ofFIG. 1.

A payment advice is created at a business partner and a Payment Advice Notification message806is generated. The Payment Processing process component804receives the Payment Advice Notification message806into the Incoming Payment Advicing In interface808, where a Create Payment Advice operation810creates a Payment Advice concerning future payment transactions. A Maintain Payment Advice inbound process agent812updates a Payment Advice business object814with a new or modified payment advice. The payment advice may be sent to the Due Item Processing deployment unit for post processing.

Interactions between Process Components “Service Order Processing” and “Customer Invoice Processing”

FIG. 9is a block diagram showing interactions between a Service Order Processing process component902and a Customer Invoice Processing process component904in the architectural design ofFIG. 1.

The Service Order Processing process component902includes a Service Order business object906that represents customer orders to service providers for the delivery of services which can possibly include the exchange of spare parts in an after sales situation.

In the Service Order Processing process component902, a Request Invoicing from Service Order to Customer Invoice Processing outbound process agent908uses a Request Invoicing operation910to send a Customer Invoice Request Request message912to the Customer Invoice Processing process component904. The Request Invoicing operation910is part of a Request for Quote Out interface914.

The Customer Invoice Request Request message912is received by a Maintain Customer Invoice Request operation916that creates, updates, deletes or requests cancellation of a customer invoice request in an Invoice Verification In interface918. The Maintain Customer Invoice Request operation916initiates a Maintain Customer Invoice Request inbound process agent920, which creates or updates a Customer Invoice Request business object922to take over the billing relevant data from the initiator of the billing process.

Next, the Confirm Customer Invoice outbound process agent924receives the Customer Invoice business object information925and initiates a Confirm Invoicing operation926in a Request Invoicing Out Interface928. A Customer Invoice Issued Confirmation message930is generated and sent to the Service Order Processing process component902.

The message930is received in the Request Invoicing In interface932. The interface932includes a Change Service Order based on Customer Invoice operation934that documents information about issued customer invoices in the service order. The update is sent to the Service Order business object906using a Change Service Order based on Customer Invoice inbound process agent936.

Interactions between Process Components “Confirmation and Inventory” and “Accounting”

FIG. 10is a block diagram showing interactions between a Confirmation and Inventory process component1002and an Accounting process component1004in the architectural design ofFIG. 1.

The Confirmation and Inventory process component1002includes a Goods and Activity Confirmation business object1006that contains all actual data reflecting an ‘ad-hoc’ executed work. For example, actual data may include a notification of scrap material, a goods issue for account assignment or a change of stock category update. In particular, the execution was not pre-planned based on a production or site logistics order.

The Notify of Inventory Change From Goods and Activity Confirmation to Accounting outbound process agent1008can invoke a Notify of Inventory Change and Activity Confirmation operation1010to update an inventory change or to update an action consumption posting. Alternatively, a Request Inventory Change and Activity Confirmation Cancellation operation1012may be invoked to send Inventory Change Accounting Cancellation updates to Accounting. Both operations may be used in an Inventory and Activity Accounting Out interface1014. If the Notify of Inventory Change and Activity Confirmation operation1010is invoked, then an Inventory Change and Activity Confirmation Accounting Notification message1016is sent to the Accounting process component1004. If the Request Inventory Change and Activity Confirmation Cancellation operation1012is invoked, the Inventory Change and Activity Confirmation Accounting Cancellation Notification message1018is sent to the Accounting process component1004.

The messages1016and1018are received by an Inventory and Activity Accounting In interface1020where operations may be performed. If a notification message1016is received, then a Create Accounting Document operation1022is performed to receive Inventory Change Accounting Notifications from Confirmation and Inventory, Site Logistics Processing or Production. If a cancellation message1018is received, then a Cancel Accounting Document operation1024is performed to Receive Inventory Change Accounting Cancellation Request from Confirmation and Inventory, Site Logistics Processing or Production. Cancellations and updates may be sent by a Maintain Accounting Document based on Inventory and Activity inbound process agent1026to an Accounting Notification business object1028.

Interactions between Process Components “Payment Processing” and “Payment Order Processing at House Bank”

FIG. 11is a block diagram showing interactions between a Payment Processing process component1102and a Payment Order processing at house bank process component1104in the architectural design ofFIG. 1.

The Payment Processing process component1102includes four business objects: a Bill of Exchange Receivable business object1106that represents a Bill of Exchange received from or a Bill of Exchange Request sent to a business partner, an Outgoing Check business object1108that represents a check sent to a business partner that is created via payment order, a Bill of Exchange Payable business object1110that represents a Bill of Exchange sent to a business partner that is created only via payment order, and a Bank Payment Order business object1112which is a Payment Order that will be sent to a house bank and may contain bank transfers as well direct debits.

The Request Payment Order from Bill of Exchange Receivable to House Bank1114creates an electronic Bill of Exchange Receivable (Request). The Request Payment Order from Outgoing Check to House Bank1116creates an outgoing check to be printed externally. The Request Payment Order from Bill of Exchange Payable to House Bank1118creates an electronic Bill of Exchange Payable. The Request Payment Order from Bank Payment Order to House Bank1120creates a Payment order to House Bank.

The Payment Ordering out interface1122receives the updates from the outbound process agents1114,1116,1118,1120. A Request Payment Order operation1124collects Bank Transfers or Direct Debits for payment submission to the business partner. A Collective Payment Order Request message1126is generated and processed by the Payment order processing at house bank process component1104. Upon completion of processing, a Collective Payment Order Confirmation message1128is sent to the Payment Ordering In interface1130that includes a Maintain Payment Order Confirmation operation1132to confirm the status updates from processing a payment order. After completing the operation1132, an update is sent to the Bank Payment Order business object1112using the Maintain Payment Order Confirmation from House Bank inbound process agent1134.

Interactions between Process Components “Service Confirmation Processing” and “Accounting”

FIG. 12is a block diagram showing interactions between a Service Confirmation Processing process component1202and an Accounting process component1204in the architectural design ofFIG. 1.

The Service Confirmation Processing process component1202includes a Service Confirmation business object1206that stores the actual resource consumption of performed service operations including working time, parts and expenses related to service fulfillment. The Service Confirmation business object1206may use a Notify of Service Confirmation to Accounting inbound process agent1208to update an Order Accounting Out interface1210. The Order Accounting Out interface1210includes a Notify of Service Confirmation operation1212that notifies Accounting about the creation, change, or deletion of a service confirmation. An Order Accounting Notification message1214is generated and sent to the Accounting process component1204. The Accounting process component1204receives the notification message1214in an Order Accounting In interface1216, which includes a Maintain Subledger Account operation1218that receives order accounting notifications from the following process components: Service Confirmation Processing, Service Contract Processing, Service Request Processing, Service Order Processing, Purchase Order Processing and Sales Order Processing. The notification is to inform the Accounting process component1204about creation, change or deletion of any kind of order business objects. A Maintain Subledger Account based on Order inbound process agent1220may then update an Accounting Notification business object1222. The Accounting Notification business object1222is a common input channel for all kinds of operational business transactions into Financial Accounting that is called by operational components in order to record the business transactions in Financial Accounting.

Alternatively, the Service Confirmation business object1206may use a Notify of Resource Consumption from Service Confirmation to Accounting outbound process agent1224to send a Resource Consumption Notification message1226or a Resource Consumption Cancellation Request message1228. The Service Confirmation Processing process component1202passes information into a Resource Consumption Accounting Out interface1230which includes a Notify of Resource Consumption operation1232or a Request Resource Consumption Cancellation operation1234. The Notify of Resource Consumption operation informs Accounting Processing about service provisions such as activity consumption or resource consumption and generates the Resource consumption Notification message1226. The Request Resource Consumption Cancellation operation1234cancels a service provision and generates a Resource Consumption Cancellation Request message1228.

The Resource Consumption Notification message1226may be received by a Resource Consumption Accounting In interface1236, which includes a Create Accounting Document operation1238that receives resource consumption notifications from Production, Service Request Processing, Service Confirmation Processing, Time and Labor Management and Project Processing. A Cancel Accounting Document operation1240may also be invoked if a Resource Consumption Cancellation Request message1228is received. A Maintain Accounting Document based on Resource Consumption inbound process agent1242may then update the Accounting Notification business object1222.

Interactions between Process Components “Site Logistics Processing” and “Accounting”

FIG. 13is a block diagram showing interactions between a Site Logistics Processing process component1302and an Accounting process component1304in the architectural design ofFIG. 1. The Site Logistics Processing process component1302includes a Site Logistics Confirmation business object1306, which is a document that collects actual data posted with reference to a site logistics order, or site logistics request. The site logistics confirmation updates inventory, finance and planning.

The Notify of Inventory Change From Site Logistics Confirmation to Accounting outbound process agent1308includes a Notify of Inventory Change and Activity Provision operation1310to send an Inventory Change Accounting Notification to Accounting message1316to the Accounting process component1304. Alternatively, a Request Inventory Change and Activity Provision Cancellation operation1312may be invoked to request inventory change and activity provision cancellation. Both operations may be used in an Inventory and Activity Accounting Out interface1314. If the Request Inventory Change and Activity Provision Cancellation operation1312is invoked, the Inventory Change and Activity Confirmation Accounting Cancellation Request message1318is sent to the Accounting process component1304.

The messages1316and1318are received by an Inventory and activity Accounting In interface1320where operations may be performed. If a notification message1316is received, then a Create Receivables/Payables operation1322is performed to Receive Inventory Change Accounting Notification from Confirmation and Inventory or Site Logistics Processing or Production. If a cancellation message1318is received, then a Cancel Accounting Document operation1324is performed to Receive Inventory Change Accounting Cancellation Request from Confirmation and Inventory or Site Logistics Processing or Production. Cancellations and updates may be sent by a Maintain Accounting Document based on Inventory and Activity inbound process agent1326to an Accounting Notification business object.

Interactions between Process Components “Customer Invoice Processing” and “Accounting”

FIG. 14is a block diagram showing interactions between a Customer Invoice Processing process component1402and an Accounting process component1404in the architectural design ofFIG. 1.

The Customer Invoice Processing process component1402includes a Customer Invoice business object1406. The Customer Invoice business object1406is used to charge a customer for delivery of goods or services. A customer invoice is then sent into a Notify of Customer Invoice to Accounting outbound process agent1408, which notifies accounting of the existence of the customer invoice.

The processing agent provides an Invoice Accounting Out interface1410with the notification and additional data such as invoice billing numbers or a credit memo. Here, the interface1410includes a Notify of Invoice operation1412and a Request Invoice Cancellation operation1414. The Notify of Invoice operation1412may be invoked if the invoice accounting out interface receives a notification to post an invoice. Upon performing the Notify of Invoice operation1412, the outbound process agent transmits an Invoice Accounting Notification message1416with the invoice accounting notification. Alternatively, the Request Invoice Cancellation operation1414may be invoked if the Invoice Accounting Out interface1410receives information requesting a cancellation. For example, the Request Invoice Cancellation operation1414may be invoked in order to cancel an invoice. Upon performing the Request Invoice Cancellation operation1414, the Notify of Customer Invoice Accounting outbound process agent1408transmits an Invoice Accounting Cancellation message1418with the invoice accounting cancellation request.

The Accounting process component1404may receive messages sent by the Supplier Invoice Processing process component1404. Here, an Invoice Accounting interface1420includes a Create Accounting Document operation1422that creates an accounting document for a customer invoice or supplier invoice if accounting receives the Invoice Accounting Notification message1416. The Invoice Accounting interface1420also includes a Cancel Accounting Document operation1424that cancels a customer or supplier invoice.

The Accounting process component1404includes a Maintain Accounting Document based on Invoice inbound process agent1426that can maintain accounting documents. For example, the inbound process agent1426may update the accounting document if a creation or cancellation operation is received. After updating the accounting document, the inbound process agent1426may forward information about the updated document into an Accounting Notification business object1428. The Accounting Notification business object1428may receive input from operational business transactions, such as the invoice notification above, and record the business transactions in the Financial Accounting deployment unit.

Interactions between Process Components “Service Order Processing” and “Accounting”

FIG. 15is a block diagram showing interactions between a Service Order Processing process component1502and an Accounting process component1504in the architectural design ofFIG. 1.

The Service Order Processing process component1502includes the Service Order business object1506, which passes information into a Notify of Service Order to Accounting outbound process agent1508. The information may contain notifications about created, changed or cancelled purchase orders.

The outbound process agent1508sends notification into an Order Accounting Out interface1510which includes a Notify of Service Order operation1512. The Notify of Service Order operation1512may be called when a service order has been created, changed or cancelled. An Order Accounting Notification message1514may then be sent to the Accounting process component1504.

The Accounting process component1504receives the Order Accounting Notification message1514in the interface1516which includes a Maintain Subledger Account operation1518that receives order accounting notifications from the Service Order Processing process component1502. The notification message1514informs the Accounting Processing process component1504about the creation, the change, or the deletion of any kind of order business objects. The notification may then be sent to the Accounting Notification business object1519using an inbound process agent1520. The Accounting Notification business object1519is a common input channel for all kinds of operational business transactions into Financial Accounting that is called by operational components in order to record the business transactions in Financial Accounting.

Interactions between Process Components “Service Request Processing External Requester System” and “Service Request Processing”

FIG. 16is a block diagram showing interactions between a Service Request Processing External Requester System process component1602and a Service Request Processing process component1604in the architectural design ofFIG. 1.

The Service Request Processing process component1604receives a Service Request message1606into an External Providing In interface1608which includes a Maintain Service Request operation1610. The Maintain Service Request operation1610creates or updates service requests using messages received from external requester systems. A Maintain Service Request inbound process agent1612updates a Service Request business object1614. The Service Request business object1614is a service notification reflecting the initial inquiry of a customer when contacting a Customer Service and Support Center.

After the update occurs, a Confirm Service Request from Service Request to External Requestor outbound process agent1616sends an update to a Confirm Service Request operation1618that creates, updates, or processes confirmations to the external requester systems. The operation1618is part of an External Providing out interface1619. A Service Request Confirmation message1620is generated and transmitted to the Service Request Processing External Requester System process component1602.

Interactions between Process Components “Due Item Processing” and “Payment Processing”

FIG. 17is a block diagram showing interactions between a Due Item Processing process component1702and a Payment Processing process component1704in the architectural design ofFIG. 1. The Due Item Processing process component1702may be used to manage all payables and receivables from service and supply and corresponding sales including a withholding tax. The Payment Processing process component1704is used to handle all incoming and outgoing payments and represent the main database for a liquidity status.

The process components include business objects to create and update data by passing messages between the Payment Request process component1704and the Due Item Processing process component1702. Multiple operations can be carried out within the interfaces. Both inbound and outbound process agents carry the business object data to and from the interfaces.

A due payment business object1706may create payment requests manually or automatically for payment processing. The due payment business object1706is responsible for the payment and clearing of payables and receivables for goods and services. A product tax declaration business object1708is a declaration of the product tax liabilities/receivables of a company to the responsible tax authority according to the tax declaration arrangement and country specific legal requirements that triggers the payment to the tax authority.

A Synchronous Request Payment Reservation interface from Due Payment to Payment Processing outbound process component1710may create a payment reservation request from Due Payment. The Payment Request Out interface1712includes several operations which go on to create messages and updates to business objects in the Payment Processing process component1704. The operations, messaging and business objects are discussed in the following paragraphs.

The Payment Request Out interface1712includes a synchronous Request payment information and provisional Payment Reservation operation1714that generates a Payment Order Reservation Request message1716to request a payment order reservation. A synchronous Create Payment Reservation operation1717receives the message and uses a Sync Maintain Payment Reservation inbound process agent1722to update a Payment Order business object1724. In addition, a Payment Order Reservation Confirmation synchronous message1720is sent back to the Due Item Processing process component1702.

The Payment Request Out interface1712also includes a Notify of provisional Payment Reservation Deletion operation1715that registers the change of a provisional payment to the last transactional/saved state. A Payment Order Reservation Cancellation Notification message1727may be generated and a Cancel Payment Reservation operation1728may be invoked that cancels a previously sent payment reservation by reference. Next, a maintain Payment Order inbound process agent sends an update to the Payment Order business object1724.

The Payment Request Out interface1712further includes a synchronous Request Payment Information and provisional Payment Reservation Change operation1718that requests payment information with a provisional reservation of money in payment processing. A Payment Order Reservation Change Request synchronous message1730is generated and a synchronous Sync Change Payment Reservation operation1732is invoked that changes a reservation of payment and confirms the change to the caller. Next, a Payment Reservation Confirmation synchronous message1734may be generated and sent back to the Due Item Processing process component1702.

The Payment Request Out interface1712further includes a Notify of provisional Payment Reservation Change Deletion operation1720that registers the change of a provisional payment to the last transactional/saved state. A Payment Order Reservation Change Deletion Cancellation Notification message1736may be generated and a Change Payment Reservation operation1738may be invoked that changes a previously sent payment reservation by reference. Upon completion of the operation1738, the Maintain Payment Order inbound process agent1740updates the Payment Order business object1724.

A Request Payment from Due Payment to Payment Processing outbound process agent1742may send a payment update to the Payment Processing process component1704from a Due Payment business object1706. A Request Payment operation1744is then invoked that sends a request for payment to Payment Processing. Upon completion of the operation, a Payment Order Request message1746is sent the Payment Processing process component1704, where a Create Payment Order operation1748begins. Then, the Maintain Payment Order inbound process agent1740updates the Payment Order business object1724to create or cancel a payment order.

A Request Payment from Product Tax Declaration to Payment Processing outbound process agent1759may send an update from a Product Tax Declaration business object1708. The update is sent into the Payment Request Out interface1712and a Request Payment Cancellation operation1750is invoked to cancel a provisional, requested or ordered payment. A Payment Order Cancellation Request message1752is then generated and sent to the Payment Processing process component where a Cancel Payment Order operation1754is invoked.

The payment order business object may use a Confirm Payment Request from Payment Order to Due Item Processing outbound process agent1764to confirm the processing status of a payment to the sender of a payment request. A Confirm Payment Request operation1762may then be invoked, thereby generating a Payment Order Request Confirmation message1760to send to the Due Item Processing process component1702. The message is received in a Change payment based on Payment Request Confirmation operation1756that uses a Change Due Payment based on Payment Request Confirmation outbound process agent1758to update the processing status of Due Payment based on the confirmation of a payment request.

Interactions between Process Components “Payment Processing” and “Payment Processing at Business Partner”

FIG. 18is a block diagram showing interactions between a Payment Processing process component1802and a Processing at Business Partner process component1804in the architectural design ofFIG. 1. The Payment Processing process component1802is used to handle all incoming and outgoing payments and to represent the main database for a liquidity status. Business partners may be any third party operating an independent system.

The interaction model begins in the Payment Processing process component1802with a Payment Order business object1806. The Payment Order business object1806creates payment media for either a bank, a credit card, a settlement institute, or a business partner on the base of payment requests. After the payment media is created, the Payment Order business object1806sends a notification using a Notify of Payment from the Payment Order to the Business Partner outbound process agent1808. A Payment Order can create different (sub) items within a payment that is sent if the payment medium is subject to amount limitations. The Payment Processing process component1802also contains an Outgoing Payment Advicing Out interface1810that includes a Notify of Payment operation1812. The Notify of Payment operation1812creates a payment advice and sends a Payment Advice Notification message1814to the Payment Processing at Business Partner processing component1804.

Interactions between Process Components “Service Request Processing” and “Accounting”

FIG. 19is a block diagram showing interactions between a Service Request Processing process component1902and an Accounting process component1904in the architectural design ofFIG. 1.

The Service Request Processing process component1902includes a Service Request business object1906. The Service Request business object1906contains a notification reflecting the initial inquiry of a customer when contacting a Customer Service and Support Center. In the Service Request Processing process component1902, a Notify of Service Request to Accounting outbound process agent1908requests the execution of a request for quote. The outbound process agent1908uses a Notify of Service Request operation1910to send an Order Accounting Notification message1912notifying accounting about the creation, change or deletion of a service request. The Notify of Service Request operation1910is part of a Order Accounting Out interface1914.

The Order Accounting Notification message1912is received by a Maintain Subledge Account operation1916in an Order Accounting In interface1918, where the operation1916receives order accounting notification to inform Accounting Processing about creation, change or deletion of any kind of order business objects. Next, the Maintain Subledge Account based on Order outbound process agent1920receives the request for quote and updates the Accounting Notification business object1922. The Accounting Notification business object1922is a common input channel for all kinds of operational business transactions into Financial Accounting that can be called by operational components in order to record the business transactions in Financial Accounting.

Alternatively, the Service Request Processing process component1902may notify the Accounting process component1904of a particular resource consumption.FIG. 19shows a Notify of Resource Consumption from Service Request to Accounting outbound process agent1924using both a Notify of Resource Consumption operation1926and a Request Resource Cancellation operation1928to update the Accounting process component1904. Both operations1926,1928are part of a Resource Consumption Accounting Out interface1930. If the Notify of Resource Consumption Operation1926is invoked, a Resource Consumption Notification message1932is transmitted to the Accounting process component1904. The message1932is received in the Create Accounting Document operation1934. If the Request Resource Consumption Cancellation operation1928is invoked, a Resource Consumption Cancellation Request message1936is transmitted to the Accounting process component1904. The message1936is received in the Cancel Accounting Document operation1938. After completion of the Create Accounting Document operation1934or the Cancel Accounting Document operation1938, a Maintain Accounting Document based on Resource Consumption inbound process agent1940updates the Accounting Notification business object1922.

Interactions between Process Components “Payment Processing” and “Due Item Processing”

FIG. 20is a block diagram showing interactions between a Payment Processing process component2002and a Due Item Processing process component2004in the architectural design ofFIG. 1.

The a Payment Processing process component2002includes a Payment Allocation business object2006. The Payment Allocation business object2006documents a process step by which open payments of different type belonging to one another are indicated as confirmed or sent to other components for post processing. In the Payment Processing process component2002, a Request Clearing Maintenance from Payment Allocation to Due Item Processing outbound process agent2008uses a Request Clearing operation2010to send a Clearing Request message2012to request the clearing of payments within the Due Item Processing process component2004. Alternatively, the outbound process agent2008may invoke a Request Clearing Cancellation operation2014to cancel a payment clearing using a Clearing Cancellation Request message2016. Both operations2010,2014are part of a clearing Out interface2018in the Payment Processing process component2002.

The messages2012,2016are received in the Due Item Processing process component2004in a Create Clearing operation2020and a Cancel Clearing operation2022respectively. The Create Clearing operation2020and the Cancel Clearing operation2022are both part of a Clearing In interface2024. Upon creating or canceling clearing, a Maintain Clearing inbound process agent2026may update a Due Payment business object2028or a Product Declaration business object2030, or both.

The Due Payment business object2028creates payment requests for payment processing. A Confirm Clearing from Due Payment to Payment Processing outbound process agent2032may invoke a Confirm Clearing operation2034that sends a Clearing Confirmation message2036to payment processing for a clearing request. The operation2034is part of a Clearing Out interface2035The message2036is received by a Change Payment Allocation based On Clearing request Confirmation operation2038that confirms the execution or rejection of a sent Clearing Request. The operation2038is part of a Clearing In interface2040. An update may be sent to the Payment Allocation business object2006using a Change Payment Allocation Based on Clearing Request Confirmation inbound process agent2042.

The Product Tax Declaration business object2030is a declaration of the product tax liabilities/receivables of a company to the responsible tax authority according to the tax declaration arrangement and country specific legal requirements that triggers the payment to the tax authority. The Product Tax Declaration business object2030may invoke the same sequence of events that the Due Payment business object2028above has completed.

Interactions between Process Components “Customer Invoice Processing” and “Supplier Invoice Processing at Customer”

FIG. 21is a block diagram showing interactions between a Customer Invoice Processing process component2102and a Supplier Invoice Processing at Customer process component2104in the architectural design ofFIG. 1.

The Customer Invoice Processing process component2102contains a Customer Invoice business object2106, a Notify Customer of Customer Invoice inbound process agent2108, and a Notify Customer of Invoice operation in an Invoicing Out interface2110. The Customer Invoice business object2106is an object used to charge a customer for delivery of goods or services.

The Customer Invoice business object2106initiates the Notify Customer of Invoice operation2112to fill billing document with data for customer usage. Upon completion of the operation2112, the Notify of Customer Invoice operation2112transmits an Invoice Request message2114requesting that the update be made.

Interactions between Process Components “Bank statement creation at bank” and “Payment Processing”

FIG. 22is a block diagram showing interactions between a Bank Statement Creation at Bank process component2202and a Payment Processing process component2204in the architectural design ofFIG. 1.

As shown inFIG. 22, a bank statement is created at a bank and a Bank Statement Notification message2206is created. The Payment Processing process component2204receives the Bank Statement Notification message2206into the Bank Statement Processing In interface2208where a Create Bank Statement operation2210is invoked to create a bank statement in the Payment Processing process component2204. A Maintain Bank Statement inbound process agent2212updates the Bank Statement business object2214with a new or modified bank statement. For example, the bank statement may be a statement for a house bank account where modifications are made when bills are paid.

Interactions between Process Components “Customer Invoice Processing and Due Item Processing”

FIG. 23is a block diagram showing interactions between a Customer Invoice Processing process component2302and a Due Item Processing process component2304in the architectural design ofFIG. 1.

The Customer Invoice Processing process component2302includes a Customer Invoice business object2306which is a document used to charge a customer for delivery of goods or services.

A Notify of Customer Invoice to Due Item Processing outbound process agent2308invokes a Notify of Invoice operation2310to inform the Due Item Processing process component2304about a customer invoice in order to derive payment due data. Alternatively, a Request Invoice Cancellation operation2312may be invoked to cancel the previously sent notification for receivables/payables due. Both operations2310,2312may be used in a Receivables Payables Out interface2314. If the Notify of Invoice operation2310is invoked, then a Receivables Payables Notification message2316is sent to the Due Item Processing process component2304. If the Request Invoice Cancellation operation2312is invoked, the Receivables/Payables Cancellation Request message2318is sent to the Due Item Processing process component2304.

The Receivables/Payables Messages are received by a Receivables/Payables In interface2320where operations may be performed. If the notification message2316is received, then a Create Receivables/Payables operation2322is performed to create a trade and/or tax receivable or payable. If the cancellation message2318is received, then a Cancel Receivables/Payables operation2324is performed to cancel a trade and/or tax receivable or payable. Cancellations and updates may be sent by a Maintain Trade and Tax Receivables Payables inbound process agent2326to one or more of three business objects: a Trade Receivables Payables business object2328, a Tax Receivables Payables business object2330, and a Due Clearing business object2332. The Trade Receivables Payables business object2328may register for all trade receivables and payables from goods and services of a company from/to its business partners. The Tax Receivables Payables business object2330may register for all tax receivables and payables of a company that are due for delivered goods and rendered services between buyers and sellers, the consumption of goods, and the transfer of goods that are withheld from payments to vendors. The Due Clearing business object2332is group of receivables and payables for clearing. “Clearing” means that the amounts of the receivables and payables of a group balance to zero taking cash discounts and other deductions into account. The “group” is typically payments and invoices that belong together but it can also be credit memos and invoices, or customer and vendor invoices. A group results uniquely from the invoice reference information of a payment.

Interactions between Process Components “Logistics Execution Control” and “Outbound Delivery Processing”

FIG. 24is a block diagram showing interactions between a Logistics Execution Control process component2402and an Outbound Delivery Processing process component2404in the architectural design ofFIG. 1.

The Logistics Execution Control process component2402controls and monitors, on a macro logistics level, the supply chain execution activities necessary for the fulfillment of an order. The Logistics Execution Control process component2402sends information to Logistics Execution to trigger the necessary supply chain execution activities, receives information about the supply chain execution progress, and updates data relevant for both fulfillment and supply and demand planning.

The Logistics Execution Control process component2402includes a Logistics Execution Requisition business object2406that sends data into a Fulfillment Out interface2408using a Request Fulfillment from Logistics Execution Request to Outbound Delivery Processing outbound process agent2410. The Fulfillment Out interface2408includes a Request Delivery Fulfillment operation2412performed to maintain a delivery request The Logistics Execution Requisition business object2406may send instructions to Logistics Execution, which supports the controlling, triggering and monitoring of supply chain execution activities necessary for the fulfillment of an order.

A Delivery Fulfillment Request message2414is then transmitted to a Fulfillment In interface2416located in the Outbound Delivery Processing process component2404. The interface contains a Maintain Outbound Delivery Request operation2418, which receives delivery fulfillment requests from Logistics Execution Control and sends the requests into an Outbound Delivery Request business object2420using a Maintain Outbound Delivery Request inbound delivery process agent2422. The Outbound Delivery Request business object2420is a document in the inbound delivery process containing all the relevant logistics data from the initiator of the inbound delivery process (such as the purchase order, for example). The inbound delivery request is used to validate an inbound delivery and an advanced shipping notification, and to prepare inbound logistics for receiving the goods. Upon receipt of the inbound delivery request, a Confirm Fulfillment of Outbound Delivery Request to Logistics Execution Control outbound delivery agent2424sends the confirmation data into a Fulfillment Out interface2426where a Confirm Fulfillment operation2428may take place. Upon completion of the Confirm Fulfillment operation2428, a Delivery Fulfillment Confirmation message2430is created and transmitted back to the Logistics Execution Control process component2402to receive fulfillment confirmation data. Receiving the Delivery Fulfillment Confirmation message2430in the Logistics Execution Control process component2402may invoke a Change Logistics Execution Requisition based on the Delivery Fulfillment Confirmation operation2434. The operation2434may then send updates or changes by way of a Change Logistics Execution Requisition based on Delivery Fulfillment inbound process agent2436into the Logistics Execution Requisition business object2406.

Interactions between Process Components “Payment Processing” and “Accounting”

FIG. 25is a block diagram showing interactions between a Payment Processing process component2504and an Accounting process component2504in the architectural design ofFIG. 1.

The Payment Processing process component Payment Processing process component2502includes ten business objects: a Bill of Exchange Submission business object2506, an Incoming Check business object2508, a Check Deposit business object2510, a Payment Order business object2512, a Bank Statement business object2514, a Bill of Exchange Receivable business object2516, a Cash Transfer business object2518, a Payment Allocation business object2520, a Clearing House Payment Order business object2522, and a Cash Payment business object2524

The Bill of Exchange Submission business object2506sends incoming bill of exchange receivables to the house bank for cashing. The Incoming Check business object2508represents a check sent by a business partner. The incoming check will be sent to the house bank by a check deposit. The Check Deposit business object2510sends a collection of incoming checks to the house bank for cashing. The Payment Order business object2512creates payment media for either a bank, a credit card a settlement institute, or a business partner on the base of payment requests. The Bank Statement business object2514is a bank statement for a house bank account. The Bill of Exchange Receivable business object2516represents a Bill of Exchange received from a business partner or a Bill of Exchange Request sent to a business partner. The Cash Transfer business object2518is a document that shows an internal money transfer between: a bank account and bank account (bank transfer), a cash account and bank account (cash deposit), a bank account and cash account (cash withdrawal), or a cash account and cash account (cash transfer). The Payment Allocation business object2520documents a process step by which open payments of different types belonging to one another are indicated as confirmed or sent to other components for post processing. For example, an incoming check may confirm a payment advice or a bank statement item may confirm a check deposit. The Clearing House Payment Order business object2522is an order document for clearing a collection of credit card payments to the clearing house. The Cash Payment business object2524is a document showing an incoming or outgoing cash payment from or to a business partner.

The Payment Processing process component2502also contains a number of outbound process agents, each tied to a particular business object. The Notify of Payment from Bill of Exchange Submission to Accounting outbound process agent2526creates an accounting notification from the Bill of Exchange Submission business object2506. The Notify of Payment from Incoming Check to Accounting outbound process agent2528may notify the Accounting process component2504of a bounced or cancelled check. The Notify of Payment from Check Deposit to Accounting outbound process agent2530may notify the Accounting process component2504of a change in status of a check deposit. For example, a notification may be sent stating that a deposit is ready for transfer to another account. The Notify of Payment from Payment Order to Accounting outbound process agent2532may notify the Accounting process component2504of a payment by payment order or a cancellation of payment. The Notify of Payment from Bank Statement to Accounting outbound process agent2534may notify the Accounting process component2504of a payment by bank account or a cancellation of payment. The Notify of Payment from Bill of Exchange Receivable to Accounting outbound process agent2536may notify the Accounting process component2504of a payment made by a bill of exchange or a cancellation of payment. The Notify of Payment from Cash Transfer to Accounting outbound process component2538may notify the Accounting process component2504about a transfer of money between house bank accounts and/or cash accounts or a cancellation of payment. The Notify of Payment from Payment Allocation to Accounting outbound process agent2540may notify the Accounting process component2504of a payment made by a payment allocation or a cancellation of payment. The Notify of Payment from Credit Card Settlement to Accounting outbound process agent2542may notify the Accounting process component2504of a payment made by credit card or a cancellation of payment. The Notify of Payment from Cash Payment to Accounting outbound process agent2544may notify the Accounting process component2504of a payment made by cash or a cancellation of payment.

The outbound process agents above may cause invocation of a Notify of Payment operation2546or a Request Payment Cancellation operation2548to update accounting. The operations2546,2548may be included in a Payment Accounting Out interface2550. The Payment Accounting Out interface2550may send a Payment Accounting Notification message2552or a Payment Accounting Cancellation Request message2554to a Payment Accounting In interface2556in the Accounting process component2504. The Payment Accounting In interface2556includes a Create Accounting Document operation2558or a Cancel Accounting Document operation2560depending on the received message. A Maintain Accounting Document based on Payment inbound processing component2562updates an Accounting Notification business object2564. The Accounting Notification business object2564is a common input channel for all kinds of operational business transactions into Financial Accounting that is called by operational components in order to record the business transactions in Financial Accounting.

Interactions between Process Components “Due Item Processing” and “Accounting”

FIG. 26is a block diagram showing interactions between a Due Item Processing component2602and an Accounting process component2604in the architectural design ofFIG. 1.

The Due Item Processing component2602contains three business objects: a Due Clearing business object2606to clear the amounts of the receivables and payables of a group balance to zero taking cash discounts and other deductions into account, a Due Payment business object2608to create payment requests for payment processing, and a Product Tax Declaration business object2610to declare the product tax liabilities/receivables of a company to the responsible tax authority according to the tax declaration arrangement and country specific legal requirements that triggers the payment to the tax authority.

The business objects send updates into one of three outbound process agents: a Notify of Payment from Due Clearing to Accounting2612, which sends notification for a clearing of trade receivables and/or payables to Accounting, a Notify of Payment from Due Payment to Accounting2614, which sends notification to Accounting for inward or outward trade receivables and/or payables payments, and a Notify of Payment from Product Tax Declaration to Accounting2616, which sends notification for a payment of tax receivables and/or payables to Accounting.

A Payment Accounting Out interface2618includes a Notify of Payment operation2620, which sends a Payment Accounting Notification message2621to the Accounting process component2604notifying Financial Accounting about inward or outward movements of trade or tax receivables or payables. Alternatively, a Request Payment Cancellation operation2622is invoked that sends a Payment Accounting Cancellation Request message2623to the Accounting process component2604to notify a cancelling of an inward or outward movement of trade or tax receivables or payables in Financial Accounting.

The Accounting process component2604receives the messages in a Payment Accounting In interface2624, which includes a Create Accounting Document operation2626to receive Payment Accounting Notification from Payment Processing or Due Item Processing. If the received message was the cancellation message2623, a Cancel Accounting Document operation2628is invoked to cancel the payment processing or due item processing. Updates are sent to the Accounting Notification business object using a Maintain Accounting Document2632based on Payment inbound process agent2630. An Accounting Notification business object2632is a common input channel for all kinds of operational business transactions into Financial Accounting that is called by operational components in order to record the business transactions in Financial Accounting.

Interactions between Process Components “Service Order Processing” and “Customer Requirement Processing”

FIG. 27is a block diagram showing interactions between a Service Order Processing process component2702and a Customer Requirement Processing process component2704in the architectural design ofFIG. 1.

The Service Order Processing process component2702contains a Service Order business object2706, inbound and outbound processing agents and several operations. The Service Order business object2706represents customer orders to service providers for the delivery of services which can possibly include the exchange of spare parts in an after sales scenario. The Service Order business object2706initiates one of four operations to send or request information to the Customer Requirement Processing process component2704.

The Service Order business object2706may send a request to fulfill a service order to the Sync Request Availability Information and Reservation from Service Order to Customer Requirement outbound process agent2708. Here, the process agent2708may invoke a Sync Request Spare Part Availability Information and Provisional Reservation operation2710that requests availability information including the creation of a provisional reservation for service order spare part items operation. Upon completion of the operation2710, the operation2710transmits an Availability Check Request message2712. The Availability Check Request message2712is received by a Check Availability and Reserve operation2714that checks the availability of certain amounts of materials and confirms this availability to the caller. The process agent2716updates the Customer Requirement business object2718to complete the operation2714. In addition, an Availability Check Confirmation message2720may be transmitted back to the Service Order Processing process component2702.

The Service Order business object2706may also send a notification to a Register Spare Part Requirement Deletion Notification operation2722that registers provisional spare part requirement reservation for deletion. The operation2722also triggers deletion in case of failure or cancellation of transaction processing. This operation2722generates a Customer Requirement Deletion Notification message2724and is received in a Delete Provisional Customer Requirement operation2726. The Delete Provisional Customer Requirement operation2726deletes provisional customer requirements that have been created by the “sync check availability and reserve” operation. An update may be sent to the Customer Requirement business object2718using the Check Availability inbound process agent2716.

The Service Order business object2706may also send a request to a Request Spare art Requirement Reservation and Fulfillment operation2728using a Request Requirement Reservation and fulfillment from Service Order to Customer Requirement outbound process agent2730. The Request Spare Part Requirement Reservation and Fulfillment operation2728requests fulfillment planning and fulfillment execution for service order spare part items. A Customer Requirement Fulfillment Request message2732is generated and transmitted to a Maintain Customer Requirement operation2734that creates or changes a customer requirement. An update may be sent to a Customer Requirement business object2718using the Maintain Customer Requirement inbound process agent2736.

The Customer Requirement business object2718is derived from a sales order or quotation for which details on the anticipated availability date are added. The Customer Requirement business object2718sends information or notifications to the Service Order Processing process component2702using a Confirmation Customer Requirement outbound process agent2738. The process agent2738invokes a Notify of availability update operation2740which notifies the creator of a customer requirement about an updated availability situation for the products requested within the customer requirement. The process agent2738may also invoke a Confirm Fulfillment operation2742that confirms the partial or complete fulfillment of a customer requirement to the creator of the requirement. If the Notify of availability update operation2740is invoked, an Availability Update Notification message2744may be generated and transmitted to a Change Service Order based on Spare Part Availability Update operation2746to update a service order with spare part availability and reservation information based on customer requirement fulfillment planning data. If the Confirm Fulfillment operation2742is invoked, a Customer Requirement Fulfillment Confirmation message2748may be generated and transmitted to a Change Service Order based on Spare Part Fulfillment Confirmation operation2750that updates a service order with spare part quantity delivered to customer or picked up by service technician. A change Service Order based on Customer Requirement inbound process agent2752may then update the Service Order business object2706.

While this specification contains many specifics, these should not be construed as limitations on the scope of the invention or of what may be claimed, but rather as an exemplification of preferred embodiments of the invention. Certain features that are described in this specification in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be provided in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

The subject matter has been described in terms of particular variations, but other variations can be implemented and are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous. Other variations are within the scope of the following claims.