Architectural design for self-service procurement application software

Description

BACKGROUND

The subject matter of this patent application relates to computer software architecture, and, more particularly, to the architecture of application software for self-service procurement.

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 implementing self-service procurement.

In its various aspects, the software architecture design can be implemented as methods, systems, and apparatus, including computer program products, for implementing a software architecture design for a software application implementing self-service procurement used to procure goods and services using internal requests created by employees. The software application is structured as multiple process components interacting with each other through service operations, each implemented for a respective process component. The process components include an Accounting process component, an Internal Request Processing process component, a Purchase Request Processing process component, a Purchase Order Processing process component, a Goods and Service Acknowledgement process component, a Supplier Invoice Processing process component, a Payment Processing process component, an RFQ Processing process component, a Project Processing process component, a Source of Supply Determination process component, a Due Item Processing process component, and a Balance of Foreign Payment Management process component.

In its various aspects, the software architecture design 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.

Details of one or more implementations of the subject matter described in this specification are set forth in the accompanying drawings and in the description below. Further features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a software architectural design for a self-service procurement software application;

FIG. 2 illustrates the elements of the architecture as they are drawn in the figures;

FIG. 3 is a block diagram showing interactions between a Customer Invoice Processing at Supplier process component and a Supplier Invoice Processing process component;

FIG. 4 is a block diagram showing interactions between a Payment Processing process component and an Accounting process component;

FIG. 5 is a block diagram showing interactions between a Supplier Invoice Processing process component and a Customer Invoice Processing at Supplier process component;

FIG. 6 is a block diagram showing interactions between a Payment Processing process component and a Payment Order Processing at House Bank process component;

FIG. 7 is a block diagram showing interactions between a Purchase Order Processing process component and a Sales Order Processing at Supplier process component;

FIG. 8 is a block diagram showing interactions between a Supplier Invoice Processing process component and Due Item Processing process component;

FIG. 9 is a block diagram showing interactions between a Purchase Order Processing process component and an Accounting process component;

FIG. 10 is a block diagram showing interactions between an RFQ Processing process component and an Opportunity/Customer Quote Processing at Supplier process component;

FIG. 11 is a block diagram showing interactions between a Purchase Order Processing process component and a Supplier Invoice Processing process component;

FIG. 12 is a block diagram showing interactions between a Goods and Service Acknowledgement process component and an Accounting process component;

FIG. 13 is a block diagram showing interactions between a Supplier Invoice Processing process component and a Balance of Foreign Payment Management process component;

FIGS. 14A and 14B are block diagrams collectively showing interactions between the Due Item Processing process component and the Payment Processing process component;

FIG. 15 is a block diagram showing interactions between an RFQ Processing process component and a Purchase Order Processing process component;

FIG. 16 is a block diagram showing interactions between a Bank Statement Creation at Bank process component and a Payment Processing process component;

FIG. 17 is a block diagram showing interactions between a Purchase Request Processing process component and an RFQ Processing process component;

FIG. 18 is a block diagram showing interactions between a Supplier Invoice Processing process component and an Accounting process component;

FIG. 19 is a block diagram showing interactions between an Internal Request Processing process component and a Purchase Request Processing process component;

FIG. 20 is a block diagram showing interactions between an Internal Request Processing process component and a Goods and Service Acknowledgement process component;

FIG. 21 is a block diagram showing interactions between a Due Item Processing process component and an Accounting process component;

FIG. 22 is a block diagram showing interactions between a Goods and Service Acknowledgement process component and a Supplier Invoice Processing process component;

FIG. 23 is a block diagram showing interactions between a Payment Processing process component and a Payment Processing at Business Partner process component;

FIG. 24 is a block diagram showing interactions between a Payment Processing process component and a Payment Processing at Business Partner process component related to an outgoing check;

FIG. 25 is a block diagram showing interactions between a Pricing Engine process component and an External Tax Calculation process component;

FIG. 26 is a block diagram showing interactions between a Supplier Invoice Processing process component and a Supplier Invoice Verification Exception Resolution at Processor process component;

FIG. 27 is a block diagram showing interactions between an Accounting Coding Block Distribution Processing process component and a Project Processing process component;

FIG. 28 is a block diagram showing interactions between a Goods and Service Confirmation at Supplier process component and a Goods and Service Acknowledgement process component;

FIG. 29 is a block diagram showing interactions between a Purchase Order Processing process component and an Internal Request Processing process component;

FIG. 30 is a block diagram showing interactions between a Payment Processing process component and a Payment Processing at Business Partner process component related to a bill of exchange payable; and

FIG. 31 is a block diagram showing interactions between an Internal Request Processing process component and a Supplier Invoice Processing process component.

DETAILED DESCRIPTION

FIG. 1 shows the software architectural design for a self-service procurement software application. The self-service procurement application is software that implements an operative procurement of goods and services using internal requests created by employees.

As shown in FIG. 1, the self-service procurement design includes a Financial Accounting deployment unit 102, a Project Management deployment unit 104, a Purchasing deployment unit 106, a Supplier Invoicing deployment unit 108, a Payment deployment unit 110, a Strategic Sourcing deployment unit 112, a Due Item Management deployment unit 114, and a Requisitioning deployment unit 116.

The Financial Accounting deployment unit 102 includes an Accounting process component 103 that represents relevant business transactions for valuation and profitability analysis.

The Project Management deployment unit 104 includes a Project Processing process component 120 that is responsible for structuring, planning, and executing measures or projects (e.g., short-term measures, complex projects, etc).

The Purchasing deployment unit 106 includes a Purchase Request Processing process component 128, a Purchase Order Processing process component 130 and a Goods and Service Acknowledgement process component 133. The Purchase Request Processing process component 128 handles the creation, change, or processing of purchase request to locate appropriate external sources of supply. The Purchase Order Processing process component 130 handles the creation and maintenance of purchase orders and purchase order confirmations. The Goods and Service Acknowledgement process component 133 represents a confirmation by an employee of goods received or services rendered. The Supplier Invoicing deployment unit 108 includes a Supplier Invoice Processing process component 136 that represents management and volume processing of supplier invoices, including exception handling and approval. The Supplier Invoice Processing process component 136 includes a supplier invoice business object and a supplier invoice request business object. The supplier invoice is a document that states the recipient's obligation to pay the supplier for goods received or services rendered. The invoice may be created after the goods and service acknowledgment has been confirmed. The supplier invoice request is a document that is sent to invoice verification, advising that an invoice for specified quantities and prices is expected and may be created through evaluation settlement. The system uses the invoice request as a basis for invoice verification, as well as for the automatic creation of the invoice.

The Payment deployment unit 110 includes a Payment Processing process component 138. The Payment Processing process component 138 is used to handle the processing and management of all payments and is also responsible for the associated communication with financial institutions such as banks, and provides the primary input for liquidity management.

The Strategic Sourcing deployment unit 112 includes an RFQ Processing process component 140. The RFQ Processing process component 140 handles requests for quotes and supplier quotes for strategic as well as operational negotiation purposes. In general, a request for quotation (RFQ) is a description of materials and services that purchasers use to request responses from potential suppliers. Requests for Quotation can be one of a number of types, including: a request for price information, a request for quote that may run over a certain period of time, a request for proposal in complex purchasing situation or live auctions that may be performed over a short time frame. A quote is a response to a request for quotation in which a supplier offers to sell goods and services at a certain price. The quote can be subject to complex pricing and conditions.

The Due Item Management deployment unit 114 includes a Due Item Processing process component 142, and a Balance of Foreign Payment Management process component 156. The Due Item Processing process component 142 is used to collect, manage, and monitor trade receivables or payables and corresponding taxes, e.g., sales tax or withholding tax. The Balance of Foreign Payment Management process component 156 is used to collect, process, and report receivables and payables to foreign trade regulations that are used by the central banks to create the balance of payments of a country. The Requisitioning deployment unit 116 includes an Internal Request Processing process component 144. The Internal Request Processing process component 144 handles the management and processing of internal requests from employees. Employees of a company may make an internal request for the procurement of goods or services for the company. For example, the employees may order stationary, computer hardware, or removal services by creating an internal request. The internal request can be fulfilled by an issue of a purchase request to the purchasing department, a reservation of goods from stock, or a production request.

The foundation layer, described below, includes a Source of Supply Determination process component 134, an Accounting Coding Block Distribution Processing process component 158, and a Pricing Engine processing component 162. The Pricing Engine process component 162 handles the processing of price and tax calculations. The Accounting Coding Block Distribution Processing process component 158 handles the registration and checking of all accounting objects that can be assigned in a source document for a business transaction, such as cost center or project. The process component 158 can dispatch a check request to the Financial Accounting deployment unit 102.

The Source of Supply Determination process component 134 uses two business objects to determine a source of supply: a supply quota arrangement business object, and a source of supply business object. A supply quota arrangement business object represents a distribution of material requirements or goods to different sources of supply, business partners, or organizational units within a company. An example of the use of supply quota arrangements is the distribution of material requirements between in-house production and different sources for external procurement. A supply quota arrangement can also define the distribution of goods to customers in case of excess production or shortages. A source of supply is an object that describes a logical link between a possible source of products and a possible target.

A number of external process components, described below, will be used to describe the architectural design. These include a Customer Invoice Processing at Supplier process component 137, a Supplier Invoice Verification Exception Resolution at Processor process component 139, an Opportunity/Customer Quote Processing at Supplier process component 141, a Sales Order Processing at Supplier process component 146, a Payment Processing at Business Partner process component 150, a Bank Statement Creation at Bank process component 152, a Payment Order Processing at House Bank process component 154, an External Tax Collection process component 164, and a Goods and Service Confirmation at Supplier processing component 168.

The Pricing Engine process component 162 requests a tax calculation from the External Tax Collection process component 164.

The Supplier Invoice Processing process component 136 receives messages from the Customer Invoice Processing at Supplier processing component 137, which is used, at a supplier, to charge a customer for the delivery of goods or services. The Supplier Invoice Processing process component 136 may also send messages to the Customer Invoice Processing at Supplier processing component 137. The Supplier Invoice Processing process component 136 may send messages to the Supplier Invoice Verification Exception Resolution at Processor process component 139.

The RFQ Processing process component 140 requests the creation or update of a supplier quote from the Opportunity/Customer Quote Processing at Supplier process component 141.

The Sales Order Processing at Supplier process component 146 receives messages from the Purchase Order Processing process component 130. The Sales Order Processing at Supplier process component 146 handles customers' requests to a company for delivery of goods or services at a certain time. The requests can be received by a sales area, which is then responsible for fulfilling the contract. The Payment Processing at Business Partner process component 150, the Bank Statement Creation at Bank process component 152, and the Payment Order Processing at House Bank process component 154 can interact with the Payment Processing process component 138. The Payment Processing process component 138 sends updates to a Payment Processing at Business Partner processing component 150, which is used to handle, at the business partner, all incoming and outgoing payments and represent the main data base for the liquidity status. The Payment Processing process component 138 also receives messages from the Bank Statement Creation at Bank process component 152. The messages can include a bank statement for a bank account. The Payment Processing process component 138 sends messages to the Payment Order Processing at House Bank process component 154. The messages can include a bank payment order that is a payment order, which may be sent to a house bank. The bank payment order can include bank transfers as well direct debits.

FIG. 2 illustrates 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 202, the process component 204, the operation 206, the outbound process agent 208, the synchronous outbound process agent 210, the synchronous inbound process agent 212, the inbound process agent 214, the service interface or interface 216, the message 218, the form message 220, the mapping entity 222, the communication channel template 224, and the deployment unit 226.

Not explicitly represented in the figures is a foundation layer that contains all fundamental entities that are used in multiple deployment units 226. 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.

A process component of an external system is drawn as a dashed-line process component 228. Such a process component 228 represents the external system in describing interactions with the external system; however, the process component 228 need not represent more of the external system than is needed to produce and receive messages as required by the process component that interacts with the external system.

The connector icon 230 is used to simplify the drawing of interactions between process components 204. Interactions between process component pairs 204 involving their respective business objects 202, process agents (at 208, 210, 212, and 214), operations 206, interfaces 216, and messages (at 218 and 22) 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 226 to another deployment unit 226. Interactions between process components 204 are indicated in FIG. 1 by 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 204, but interfaces 216, process agents (at 208, 210, 212, and 214), and business objects 202 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 204 is described as being contained in a deployment unit 226. 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 202. A business object 202 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. This example 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 204, 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 202 are implemented free of redundancies.

The architectural elements also include the process component 204. A process component 204 is a software package that realizes a business process and generally exposes its functionality as services. The functionality includes the ability to perform all or parts of particular kinds of business transactions. A process component 204 contains one or more semantically related business objects 202. Any business object belongs to no more than one process component. Process components can be categorized as a standard process component, a process component at a business partner, a third party process component, or a user centric process component. The standard process component (named simply process component) is a software package that realizes a business process and exposes its functionality as services. The process component at a business partner is a placeholder for a process component (or other technology that performs the essential functions of the process component) used at a business partner. The third party process component is a process component (or other technology that performs the essential functions of the process component) provided by a third party. The user-centric process component is a process component containing user interface parts.

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

The architectural elements also include the operation 206. An operation 206 belongs to exactly one process component 204. A process component 204 generally is able to perform multiple operations 206. Operations 206 can be synchronous or asynchronous, corresponding to synchronous or asynchronous process agents (e.g. at 208, 210, 212, and 214), which will be described below. Operation 206 may be 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 216, referred to simply as the interface. An interface 216 is a named group of operations 206. Interface 216 typically specifies inbound service interface functionality or outbound service interface functionality. Each operation 206 belongs to exactly one interface 216. An interface 216 belongs to exactly one process component 204. A process component 204 might contain multiple interfaces 216. In some implementations, 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 206 directed to the same other process component 204 are in one interface 216.

The architectural elements also include the message 218. Operations 206 transmit and receive messages 218. 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. In some implementations, the message is a form based message 220 that can be translated into a recognized format for an external process component 228. The form message type 220 is a message type used for documents structured in forms. The form message type 220 can be used for printing, faxing, emailing, or other events using documents structured in forms. In some implementations, the form message type 220 provides an extended signature relative to the normal message type. For example, the form message type 220 can include text information in addition to identification information to improve human reading.

The architectural elements also include the process agent (e.g. at 208, 210, 212, and 214). Process agents do business processing that involves the sending or receiving of messages 218. Each operation 206 will generally have at least one associated process agent. The process agent can be associated with one or more operations 206. Process agents (at 208, 210, 212, and 214) can be either inbound or outbound, and either synchronous or asynchronous.

Asynchronous outbound process agents 208 are called after a business object 202 changes, e.g., after a create, update, or delete of a business object instance. Synchronous outbound process agents 210 are generally triggered directly by a business object 202.

An outbound process agent (208 and 210) 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 (212 and 214) 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 (210 and 212) 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 by using other conventional techniques to perform the functions described in this specification.

The architectural elements also include the communication channel template. The communication channel template is a modeling entity that represents a set of technical settings used for communication. The technical settings can include details for inbound or outbound processing of a message. The details can be defined in the communication channel template. In particular, the communication channel template defines an adapter type, a transport protocol, and a message protocol. In some implementations, various other parameters may be defined based on a selected adapter type. For example, the communication channel template can define a security level, conversion parameters, default exchange infrastructure parameters, processing parameters, download URI parameters, and specific message properties.

The communication channel template 224 can interact with internal or external process components (at 204 and 228). To interact with an internal process component, the communication channel template is received and uploaded to be used with an operation and interface pair. To interact with an external process component, the communication channel template is received and uploaded to be used with an external entity, such as an external bank, business partner, or supplier.

The architectural elements also include the deployment unit 226. A deployment unit 226 includes one or more process components 204 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 boundary of a deployment unit 226 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 204 of one instance of one deployment unit 226.

The process components 204 of one deployment unit 226 interact with those of another deployment unit 226 using messages 218 passed through one or more data communication networks or other suitable communication channels. Thus, a deployment unit 226 deployed on a platform belonging to 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 226 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 204 that interact with other process components 204 or external systems only through messages 218, e.g., as sent and received by operations 206, can also be replaced as long as the replacement supports the operations 206 of the original 204.

In contrast to a deployment unit 226, the foundation layer does not define a limit for application-defined transactions. Deployment units 226 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 202 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 226. Master data objects and business process objects that should be specific to a deployment unit 226 are assigned to their respective deployment unit 226.

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

FIG. 3 is a block diagram showing interactions between the Customer Invoice Processing at Supplier process component 137 and the Supplier Invoice Processing process component 136 in the architectural design of FIG. 1.

As shown in FIG. 3, the Supplier Invoice Processing process component 136 receives a Business Transaction Document Image Recognition Request message 306. A Create Invoice based on Attachment operation 310 receives the message 306 and creates an empty supplier invoice with an attachment of an invoice image according to legally binding claims or liabilities for delivered goods and rendered services. The Create Invoice based on Attachment operation 310 is included in an Image Recognition Invoicing In interface 308. The operation 310 uses a Create Supplier Invoice based on Attachment inbound process agent 312 to update the Supplier Invoice business object 314. The Supplier Invoice business object 314 represents a company's obligation to pay the supplier for delivered goods and services. For example, if the company returns goods or complains about services, the supplier can issue a credit memo for an amount equal to or lower than the original invoice, and can refund the money to the company. For example, for invoiced goods that require a duty, a customs duty invoice can be submitted by the customs authority, stating a company's obligation to pay tax on the import or export of goods.

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

FIG. 4 is a block diagram showing interactions between the Payment Processing process component 138 and the Accounting process component 103 in the architectural design of FIG. 1. The interaction may begin when a payment is ordered, received, allocated or cancelled. The Payment Processing process component 138 can notify the Accounting process component 103 about the creation or cancellation of a payment ordered, received or allocated.

As shown in FIG. 4, the Payment Processing process component 138 includes an Incoming Check business object 402, a Check Deposit business object 404, the Payment Order business object 448, the House Bank Statement business object 450, a Payment Allocation business object 406, a Bill of Exchange Receivable business object 442, a Bill of Exchange Deposit business object 444, and a Cash Transfer business object 446. The Incoming Check business object 402 represents a check issued by a business partner payable to the company. The Check Deposit business object 404 represents a deposit of checks at a house bank for credit to a house bank account. The Payment Allocation business object 406 represents an assignment of a payment item to the payment reasons from which the payment item originated. The Payment Order business object 448 represents an order within a company to make a payment to a business partner at a specified time. For example, a payment order can be a collective order that includes several individual orders. The House Bank Statement business object 450 represents a legally binding notification from the house bank about the revenues (items) within a specific time period at a house bank account with a defined starting and closing balance. The Bill of Exchange Receivable business object 442 represents a bill of exchange issued either by the company or by a business partner for the benefit of the company. The Bill of Exchange Deposit business object 444 represents a deposit of bills of exchange receivable at a house bank for credit to a house bank account. The Cash Transfer business object 446 represents a company-internal money transfer that can include the following payments: from one house bank account to another (house bank account transfer); from one cash storage to another (cash transfer); from a cash storage to a house bank account (cash deposit); from a house bank account to a cash storage (cash withdrawal).

The Incoming check business object 402 uses a Notify of Payment from Incoming Check to Accounting outbound process agent 408 to invoke a Notify of Payment operation 410 or a Notify of Payment Cancellation operation 412. The operations 410 and 412 are included in a Payment Accounting Out interface 414.

The Check Deposit business object 404 uses a Notify of Payment from Check Deposit to Accounting outbound process agent 428 to invoke the Notify of Payment operation 410 or the Notify of Payment Cancellation operation 412.

The Payment Order business object 448 uses a Notify of Payment from Payment Order to Accounting outbound process agent 430 to invoke the Notify of Payment operation 410 or the Notify of Payment Cancellation operation 412.

The House Bank Statement business object 450 uses a Notify of Payment from Bank Statement to Accounting outbound process agent 432 to invoke the Notify of Payment operation 410 or the Notify of Payment Cancellation operation 412.

The Payment Allocation business object 406 uses a Notify of Payment from Payment Allocation to Accounting outbound process agent 434 to invoke the Notify of Payment operation 410 or the Notify of Payment Cancellation operation 412.

The Bill of Exchange Receivable business object 442 uses a Notify of Payment from Bill of Exchange Receivable to Accounting outbound process agent 436 to invoke the Notify of Payment operation 410 or the Notify of Payment Cancellation operation 412.

The Bill of Exchange Deposit business object 444 uses a Notify of Payment from Bill of Exchange Deposit to Accounting outbound process agent 438 to invoke the Notify of Payment operation 410 or the Notify of Payment Cancellation operation 412.

The Cash Transfer business object 446 uses a Notify of Payment Cash Transfer to Accounting outbound process agent 440 to invoke the Notify of Payment operation 410 or the Notify of Payment Cancellation operation 412.

If the Notify of Payment operation 410 is invoked, the operation 410 generates a Payment Accounting Notification message 416. If the Notify of Payment Cancellation operation 412 is invoked, the operation 412 generates a Payment Cancellation Accounting Notification message 418.

A Create Accounting Document operation 422 receives the Payment Accounting Notification message 416. A Cancel Accounting Document operation 424 receives the Payment Cancellation Accounting Notification message 418. The operations 422 and 424 are included in a Payment Accounting Out interface 420. The operations 422 and 424 use a Maintain Accounting Document based on Payment inbound process agent 426 to update the Accounting Notification business object 452. The Accounting Notification business object 452 represents a notification sent to the Accounting process component 103 by an operational component regarding a business transaction. For example, the Accounting Notification business object 452 can represent the operational business transaction in a standardized form for all business transaction documents, and can include the data used to valuate the business transaction.

If the Notify of Payment operation 410 is invoked, then the Payment Accounting Notification message 416 is sent to the Accounting process component 103 to update the Accounting Notification business object 452. If the Notify of Payment Cancellation operation 412 is invoked, then the Payment Cancellation Accounting Notification message 418 is sent to the Accounting process component 103 to update the Accounting Notification business object 452.

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

FIG. 5 is a block diagram showing interactions between the Supplier Invoice Processing process component 136 and the Customer Invoice Processing at Supplier process component 137 in the architectural design of FIG. 1. The interaction may begin when a supplier invoice based on goods received or services rendered is created. The Supplier Invoice Processing process component 136 requests the creation of an invoice from the Customer Invoice Processing at Supplier process component 137.

As shown in FIG. 5, the Supplier Invoice Processing process component 136 includes the Supplier Invoice business object 314. The Supplier Invoice business object 314 represents a company's obligation to pay a supplier for delivered goods and services. For example, if the company returns goods or complains about services, the supplier can issue a credit memo for an amount equal to or lower than the original invoice, and can refund the money to the company. For example, for invoiced goods that require a duty, a customs duty invoice can be submitted by the customs authority, stating a company's obligation to pay tax on the import or export of goods.

The Supplier Invoice business object 314 uses a Request Evaluated Receipt Settlement (ERS) Invoice to Supplier outbound process agent 502 to invoke a Request ERS Invoice operation 504. The operation 504 can inform the seller party about a supplier invoice created by the buyer party using a credit memo procedure (e.g., Evaluated Receipt Settlement (ERS)). The process may start when an invoice which has been created from a business-to-business interface is posted (accepted) or deleted (rejected) and an answer is expected. The Request Evaluated Receipt Settlement Invoice operation 504 is included in an Evaluated Receipt Settlement Invoicing Out interface 506. The operation 504 generates an Invoice Request message 508 or a Form Invoice Request message 510 which can both be sent to the Customer Invoice Processing at Supplier process component 137. The Evaluated Receipt Settlement Invoicing Out interface 506 receives information from a Processing At Tenant Out Web Services Reliable Messaging (WSRM) communication channel template 512. The communication channel template 512 can define protocols and parameters used for communication with an external party

Interactions Between Process Components “Payment Processing” and “Payment Order Processing at House bank”

FIG. 6 is a block diagram showing interactions between the Payment Processing process component 138 and the Payment Order Processing at House Bank process component 154 in the architectural design of FIG. 1.

As shown in FIG. 6, the Payment Processing process component 138 includes a Bank Payment Order business object 610. The Bank Payment Order business object 610 represents an order to a house bank to make a transfer or direct debit from a specified house bank account to fulfill a payment order. For example, the house bank can be a bank located in France.

The Bank Payment Order business object 610 uses a Request File Based Payment Order from Bank Payment Order to House Bank outbound process agent 616 to invoke a Request File based Payment Order operation 618. The Request File based Payment Order operation 618 instructs a house bank, using a file, to make a bank transfer or a direct debit. The operation 618 is included in a Payment Ordering Out interface 620. The Request File based Payment Order operation 618 generates a File based Collective Payment Order Request message 622. The File based Collective Payment Order Request message 622 uses Mapping Entity 624 to transform the file-based message type to a Collective Payment Order Request message 626 that can be received by the Payment Order Processing at House Bank process component 154. The Collective Payment Order Request message 626 may be in a format that the house bank (a bank located in France) can understand. A collective payment order can be an instruction based on a file transfer to a credit institution to carry out one or more payment transactions (e.g. bank transfers or direct debits).

The Payment Order Processing at House Bank process component 154 receives information from a Payment Order Request communication channel template 628. The communication channel template 628 can provide information from a third party about a payment order request.

Interactions Between Process Components “Purchase Order Processing” and “Sales Order Processing at Supplier”

FIG. 7 is a block diagram showing interactions between the Purchase Order Processing process component 130 and the Sales Order Processing at Supplier process component 146 in the architectural design of FIG. 1.

As shown in FIG. 7, the Purchase Order Processing process component 130 includes the Purchase Order business object 744 and a Purchase Order Confirmation business object 702. The Purchase Order Confirmation business object 702 represents a confirmation from a seller to deliver a specified quantity of goods, or perform a specified service, at a specified price within a specified time. The Purchase Order business object 744 represents a request from a buyer to a seller to deliver a specified quantity of material, or perform a specified service, at a specified price within a specified time.

The Purchase Order business object 744 uses a Request Purchase Order to Supplier outbound process agent 704 to request a purchase order at a supplier. The outbound process agent 704 invokes either a Request Purchase Order Creation operation 706, or a Request Purchase Order Change operation 710. The operations 706 and 710 are included in an Ordering Out interface 725.

The Request Purchase Order Creation operation 706 requests a purchase order from a supplier. The operation 706 generates an Interactive Form Purchase Order Request message 718. The Request Purchase Order Change operation 710 requests a change of a purchase order that was formerly ordered at a supplier. The operation 710 can also generate an Interactive Form Purchase Order Request message 718.

The Interactive Form Purchase Order Request message 718 is received at the external Sales Order Processing at Supplier process component 146. The external process component 146 can confirm the purchase order request by generating an Interactive Form Purchase Order Request Message 740. The Interactive Form Purchase Order Request message 740 uses Mapping Entity 738 to transform the interactive form-based message type to a Purchase Order Confirmation message 734 that can be received by the Create Purchase Order Confirmation operation 732.

The operation 732 creates a purchase order confirmation according to the confirmation, partial confirmation, or proposed changes sent from the seller to the buyer concerning the requested delivery of the product to trigger the creation of a purchase order confirmation. The Create Purchase Order Confirmation operation 732 is included in an Ordering In interface 730. The operation 732 uses a Create Purchase Order Confirmation inbound process component 736 to update the Purchase Order Confirmation business object 702. The Ordering In interface 730 receives information from a Processing At Tenant In Web Services Reliable Messaging (WSRM) communication channel template 742. The communication channel template 742 can provide information from an external party about a purchase order confirmation.

Interactions Between Process Components “Supplier Invoice Processing” and “Due Item Processing”

FIG. 8 is a block diagram showing interactions between the Supplier Invoice Processing process component 136 and the Due Item Processing process component 142 in the architectural design of FIG. 1. The interaction may begin when a supplier invoice is created or cancelled. The Supplier Invoice Processing process component 136 notifies the Due Item Processing process component 142 about the creation or cancellation of a supplier invoice.

As shown in FIG. 8, the Supplier Invoice Processing process component 136 includes a Supplier Invoice business object 314. The Supplier Invoice business object 314 represents a company's obligation to pay a supplier for delivered goods and services. For example, if the company returns goods or complains about services, the supplier can issue a credit memo for an amount equal to or lower than the original invoice, and can refund the money to the company. In some implementations, for invoiced goods that require a duty, a customs duty invoice can be submitted by the customs authority, stating a company's obligation to pay tax on the import or export of goods.

The Supplier Invoice business object 314 uses a Notify Supplier of Invoice to a Due Item Processing outbound process agent 808 to invoke a Notify of Invoice operation 810. The operation 810 sends a Receivables Payables Notification message 816 to the Due Item Processing process component 142. The message 816 is a notification about the receivables/payables due for an invoice that has been paid. Alternatively, the Notify Supplier of Invoice to a Due Item Processing outbound process agent 808 invokes a Notify of Invoice Cancellation operation 812 to cancel a previously sent notification for receivables/payables due. Both operations 810 and 812 are included in a Receivables Payables Out interface 814. If the Notify of Invoice operation 810 is invoked, then the Receivables Payables Notification message 816 is sent to the Due Item Processing process component 142. If the Notify of Invoice Cancellation operation 812 is invoked, a Receivables Payables Cancellation Notification message 818 is sent to the Due Item Processing process component 142.

The Receivables Payables Notification message 816 is received in a Create Receivables Payables operation 822. The Receivables Payables Cancellation Notification message 818 is received in a Cancel Receivables Payables operation 824. The operation 822 and 824 are included in a Receivables Payables In interface 820. If the Receivables Payables Notification message 816 is received, then the Create Receivables Payables operation 822 is performed to create a trade and/or tax receivable or payable. If the Receivables Payables Cancellation Notification message 818 is received, then the Cancel Receivables Payables operation 824 is performed to cancel a trade and/or tax receivable or payable. The operations 822 and 824 use a Maintain Trade and Tax Receivables Payables inbound process agent 826 to update one or more of three business objects including a Trade Receivables Payables Register business object 828, a Tax Receivables Payables Register business object 830, and a Due Clearing business object 832. The Trade Receivables Payables Register business object 828 represents the register of trade receivables and payables of a company to or from its business partners. The Tax Receivables Payables Register business object 830 represents the register of tax receivables and payables of a company for the delivered goods and rendered services between buyers and sellers, the consumption of goods, the transfer of goods, and amounts withheld from payments to sellers. The Due Clearing business object 832 represents a group of receivables and payables for clearing. “Clearing” can refer to the amounts of the receivables and payables of a group balance to zero, taking cash discounts and other deductions into account. The “group” can be payments and invoices that belong together, but it can also be credit memos and invoices, or customer and vendor invoices. A group can result from the invoice reference information of a payment.

Interactions Between Process Components “Purchase Order Processing” and “Accounting”

FIG. 9 is a block diagram showing interactions between the Purchase Order Processing process component 130 and the Accounting process component 103 in the architectural design of FIG. 1. The interaction may begin when a purchase order is created or updated. The Purchase Order Processing process component 130 requests the creation or update of subledger account (based on purchasing) from the Accounting process component 103.

As shown in FIG. 9, the Purchase Order Processing component 130 includes the Purchase Order business object 744. The Purchase Order business object 744 represents a request from a buyer to a seller to deliver a specified quantity of material, or perform a specified service, at a specified price within a specified time.

The Purchase Order business object 744 uses the Notify of Purchase Order to Accounting outbound process agent 908 to invoke a Notify of Purchase Order operation 912. The Notify of Purchase Order operation 912 notifies about a created, changed, or cancelled purchase order. The operation 912 is included in an Order Accounting Out interface 910. The operation 912 generates a Sales and Purchasing Accounting Notification message 914.

A Create Accounting Notification operation 918 receives the Sales and Purchasing Accounting Notification message 914. The operation 918 receives order accounting notification from the Purchase Order Processing process component 130. The notification can inform the Accounting Processing process component 103 about the creation, change or deletion of any kind of order business objects. The operation 918 is included in a Sales and Order Purchasing Accounting In interface 916. The Create Accounting Notification operation 918 uses a Maintain Subledger Account based Sales and Purchasing inbound process agent 920 to update the Accounting Notification business object 452. The Accounting Notification business object 452 represents a notification sent to the Accounting process component 103 by an operational component regarding a business transaction. For example, the Accounting Notification business object 452 can represent the operational business transaction in a standardized form for all business transaction documents, and can include the data used to valuate the business transaction.

Interactions Between Process Components “RFQ Processing” and “Opportunity/Customer Quote Processing at Supplier”

FIG. 10 is a block diagram showing interactions between the RFQ Processing process component 140 and the Opportunity/Customer Quote Processing at Supplier process component 141 in the architectural design of FIG. 1. The interaction may begin when a request for quote is created, changed, or cancelled. The RFQ Processing process component 140 can request the creation or update of a supplier quote from the Opportunity/Customer Quote Processing at Supplier process component 141. The RFQ Processing process component 140 can inform the supplier of the awarding result.

As shown in FIG. 10, the RFQ Processing process component 140 includes a Request for Quote business object 1004 and the Supplier Quote business object 1064. The Request for Quote business object 1004 represents a request from a buyer to a bidder to submit a quote for goods or services according to a set of specified criteria. The Supplier Quote business object 1064 represents a response to a quote request in which a bidder offers to sell goods and services to a buyer according to requested criteria.

The RFQ Processing process component 140 also includes a Request Quote Processing Out interface 1010, a Quote Processing In interface 1012, and a Quote Processing Out interface 1014. The Request Quote Processing Out interface 1010 includes a Request Quote Creation operation 1016, a Notify of Request for Quote Change operation 1018, and a Notify of Request for Quote Cancellation operation 1020. The Request Quote Creation operation 1016 requests the participation of the supplier in a bidding process. The Notify of Request for Quote Change operation 1018 notifies the supplier about changes to the request for quote. The Notify of Request for Quote Cancellation operation 1020 notifies the supplier about the cancellation of a request for quote. The Request Quote Processing Out interface 1010 receives information from a Processing At Tenant Out Web Services Reliable Messaging (WSRM) communication channel template 1062. The communication channel template 1062 can provide information from an external party about a purchase order confirmation.

The Quote Processing In interface 1012 includes a Maintain Supplier Quote operation 1022 that creates or updates a supplier quote on the basis of the received customer quote which was sent in response to the invitation from the buyer to submit a quotation.

The Quote Processing Out interface 1014 includes a Request Quote Change operation 1024 and a Notify of Quote Award operation 1026. The Request Quote Change operation 1024 requests the change of the customer quote. The Notify of Quote Award operation 1026 notifies the bidder about supplier quote items for which the quotation from the bidder has been awarded, including extending the award, or about a rejection if the quotation from the bidder is not successful. The Quote Processing Out interface 1014 receives information from a Processing At Tenant In Web Services Reliable Messaging (WSRM) communication channel template 1060. The communication channel template 1060 can provide information from an external party about a purchase order confirmation.

The Request for Quote business object 1004 uses a Request Quote Maintenance from Request for Quote to Supplier outbound process agent 1028 when the Request for Quote business object 1004 is published, re-published or cancelled. The Request Quote Maintenance from Request for Quote to Supplier outbound process agent 1028 invokes the Request Quote Creation operation 1016 to send a Form RFQ Request message 1032, or an RFQ Request message 1034 to the Opportunity/Customer Quote Processing at Supplier process component 141. The Request Quote Maintenance from Request for Quote to Supplier outbound process agent 1028 can also invoke the Notify of Request for Quote Change operation 1018 to send a Form RFQ Change Request message 1038, or an RFQ Change Request message 1040 to the Opportunity/Customer Quote Processing at Supplier process component 141. The Request Quote Maintenance from Request for Quote to Supplier outbound process agent 1028 can also invoke the Notify of Request for Quote Cancellation operation 1020 to send an RFQ Cancellation Request message 1042 or a Form RFQ Cancellation Request message 1044 to the Opportunity/Customer Quote Processing at Supplier process component 141.

A Quote Notification message 1048 is received by a Maintain Supplier Quote operation 1022 that uses a Maintain Supplier Quote inbound process agent 1046 to create or update the Supplier Quote business object 1064.

The Supplier Quote business object 1064 uses a Notify of Supplier Quote to Supplier outbound process agent 1052 to invoke the Request Quote Change operation 1024 when a supplier quote is submitted. The Request Quote Change operation 1024 sends a RFQ Change Request message 1054 to the Opportunity/Customer Quote Processing at Supplier process component 141. The Notify of Supplier Quote to Supplier outbound process agent 1052 invokes the Notify of Quote Award operation 1026 when a supplier quote is submitted. The Notify of Quote Award operation 1026 sends an RFQ Result Notification message 1056 or a Form RFQ Result Notification message 1058 to the Opportunity/Customer Quote Processing at Supplier process component 141.

Interactions Between Process Components “Purchase Order Processing” and “Supplier Invoice Processing”

FIG. 11 is a block diagram showing interactions between the Purchase Order Processing process component 130 and the Supplier Invoice Processing process component 136 in the architectural design of FIG. 1. The interaction may begin when a purchase order is requested. The Purchase Order Processing process component 130 notifies the Supplier Invoice Processing process component 136 about the invoicing-relevant data contained in the purchase order.

As shown in FIG. 11, the Purchase Order Processing process component 130 includes the Purchase Order business object 744. The Purchase Order business object 744 represents a request from a buyer to a seller to deliver a specified quantity of material, or to perform a specified service, at a specified price within a specified time.

The Purchase Order business object 744 uses a Notify of Invoicing Due from Purchase Order to Supplier Invoice Processing outbound process agent 1108 to invoke a Notify of Invoicing Due operation 1110. The Notify of Invoicing Due operation 1110 notifies a supplier invoice about an invoice due, or when a purchase order has been created, changed or cancelled. The Notify of Invoicing Due operation 1110 is included in an Invoice Verification Out interface 1112. The operation 1110 generates an Invoicing Due Notification message 1114.

A Maintain Invoice Request operation 1118 receives the Invoicing Due Notification message 1114. The operation 1118 creates or updates a reference object in the Supplier Invoice Processing process component 136 in order to perform invoice verification with reference to a purchase order without having to access other deployment units. The reference object is used for checks against the preceding documents and to make proposals for invoice entry. The Maintain Invoice Request operation 1118 is included in an Invoice Verification In interface 1116.

A Maintain Supplier Invoice Request inbound process agent 1120 updates invoice data into a Supplier Invoice Request business object 1122. The Supplier Invoice Request business object 1122 represents a request that is sent to invoice verification, advising that a supplier invoice for specified quantities and prices is expected, or is to be created through evaluation settlement.

The business object 1122 uses a Notify of Invoiced Values from Supplier Invoice Request to Purchase Order Processing outbound process agent 1124 to invoke a Notify of Invoice Values operation 1126. The Notify of Invoice Values operation 1126 notifies the Purchase Order Processing process component 130 that at least parts of the purchase order have been invoiced. The operation 1126 is included in an Invoice Verification Out interface 1128. The Notify of Invoice Values operation 1126 generates a Purchase Order Invoice Values Notification message 1130.

The message 1130 is received in a Change Purchase Order based on Invoice Values operation 1134. The Change Purchase Order based on Invoice Values operation 1134 changes a purchase order based on invoice values by adding the quantity and amount of a supplier invoice to the cumulated invoiced quantity and amount in a purchase order. The operation can also add the reference to the supplier invoice document to the purchase order. The operation 1134 is included in an Invoice Verification In interface 1132. The Change Purchase Order based on Invoice Values operation 1134 uses a Change Purchase Order based on Invoice Values inbound process agent 1136 to update the Purchase Order business object 744.

Interactions Between Process Components “Goods and Service Acknowledgement” and “Accounting”

FIG. 12 is a block diagram showing interactions between the Goods and Service Acknowledgement process component 133 and the Accounting process component 103 in the architectural design of FIG. 1. The interaction may begin when a goods and service acknowledgment is created or cancelled. The Goods and Service Acknowledgement Processing process component 133 requests the creation or cancellation of accounting documents from the Accounting process component 103.

As shown in FIG. 12, the Goods and Service Acknowledgement process component 133 includes a Goods and Service Acknowledgement business object 1206. The Goods and Service Acknowledgement business object 1206 represents a notification sent to the Accounting process component 103 by an operational component regarding a business transaction. For example, the Goods and Service Acknowledgement business object 1206 can represent the operational business transaction in a standardized form for all business transaction documents, and can include the data used to valuate the business transaction.

The Goods and Service Acknowledgement business object 1206 uses a Notify of Goods and Service Acknowledgement to Accounting outbound process agent 1208 to invoke a Notify of Goods and Service Acknowledgement operation 1210 or a Notify of Goods and Service Acknowledgement Cancellation operation 1212. The Notify of Goods and Service Acknowledgement operation 1210 notifies the Accounting process component 103 about delivered goods and rendered services of a goods and service acknowledgement. The Notify of Goods and Service Acknowledgement Cancellation operation 1212 notifies the Accounting process component 103 about goods and service acknowledgement cancellation. The operations 1210 and 1212 are included in a Goods and Service Accounting Out interface 1214. The Notify of Goods and Service Acknowledgement operation 1210 generates a Goods and Service Acknowledgement Accounting Notification message 1216.

A Create Accounting Document operation 1220 receives the message 1216. The Create Accounting Document operation 1220 receives goods movement resource consumption notification from the Goods and Service Acknowledgement process component 133. The Create Accounting Document operation 1220 is included in a Goods and Service Accounting In interface 1218. The operation 1220 uses a Maintain Accounting Document based on a Goods and Service Acknowledgement Description inbound process agent 1222 to update the Accounting Notification business object 452. The Accounting Notification business object 452 represents a notification sent to the Accounting process component 103 by an operational component regarding a business transaction. For example, the Accounting Notification business object 452 can represent the operational business transaction in a standardized form for all business transaction documents, and can include the data used to valuate the business transaction.

The Notify of Goods and Service Acknowledgement Cancellation operation 1212 generates a Goods and Service Acknowledgement Cancellation Accounting Notification message 1217. A Cancel Accounting Document operation 1228, in the Goods and Service Accounting In interface 1218, receives the Goods and Service Acknowledgement Cancellation Request message 1217 from the Goods and Service Acknowledgement process component 133. The Cancel Accounting Document operation 1228 receives a goods movement resource consumption cancellation request from the Goods and Service Acknowledgement process component 133. The operation 1228 uses a Maintain Accounting Document based on the Goods and Service Acknowledgement Description inbound process agent 1222 to update the Accounting Notification business object 452.

Interactions Between Process Components “Supplier Invoice Processing” and “Balance Of Foreign Payment Management”

FIG. 13 is a block diagram showing interactions between a Supplier Invoice Processing process component 136 and a Balance Of Foreign Payment Management process component 156. The interaction may begin when a supplier invoice, such when as a supplier invoice related to a non-resident seller is created or cancelled. The Supplier Invoice Processing process component 136 can notify the Balance of Foreign Payments Management process component 156 about the creation or cancellation of a payable related to a non-resident seller.

As shown in FIG. 13, the Supplier Invoice Processing process component 136 includes a Supplier Invoice business object 314. The Supplier Invoice business object 314 represents a company's obligation to pay a supplier for delivered goods and services. For example, if the company returns goods or complains about services, the supplier can issue a credit memo for an amount equal to or lower than the original invoice, and can refund the money to the company. For example, for invoiced goods that require a duty, a customs duty invoice can be submitted by the customs authority, stating a company's obligation to pay tax on the import or export of goods.

The Supplier Invoice business object 314 uses a Notify Supplier of Invoice to Balance of Foreign Payments Management outbound process agent 1408 to invoke a Notify of Invoice operation 1310. The operation 1310 notifies the Balance Of Foreign Payment Management process component 156 about the foreign receivables/payables of the supplier invoice. Alternatively, a Notify of Invoice Cancellation operation 1312 can be used to notify the process component 156 about the cancellation of a previously sent notification for foreign receivables/payables of the supplier invoice. Both operations are included in a Foreign Receivable Payable Notification Out interface 1314. The Notify of Invoice operation 710 generates a Foreign Receivable Payable Notification message 1316. The Notify of Invoice Cancellation operation 1312 generates a Foreign Receivable Payable Cancellation Notification message 1318.

The messages 1316 and 1318 are received by a Create Foreign Receivable Payable operation 1322 and a Cancel Foreign Receivable Payable operation 1324, respectively. The Foreign Receivable Payable operation 1322 creates a foreign receivable or payable. The Create Foreign Receivable Payable operation 1322 and the Cancel Foreign Receivable Payable operation 1324 are included in a Foreign Receivable Payable Notification In interface 1320.

Operations 1322 and 1324 use a Maintain Foreign Receivable Payable inbound process agent 1326 to create, change or cancel a foreign receivable or payable in a Foreign Receivable Payable business object 1330. The Foreign Receivable Payable business object 1330 represents a receivable from or payable to a non-resident business partner.

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

FIGS. 14A and 14B are block diagrams collectively showing interactions between the Due Item Processing process component 142 and the Payment Processing process component 138 in the architectural design of FIG. 1. The interaction may begin when a payment for trade or tax receivables or payables is initiated or cancelled. The interaction allows the Due Item Processing process component 142 to request a reservation or change a previously made reservation of cash from the Payment Processing process component 138 within the creation process. The Payment Processing process component 138 confirms the creation or the change of a reservation immediately.

As shown in FIG. 14A, the Due Item Processing process component includes a Due Payment business object 1406, a Product Tax Declaration business object 1408, and a Tax Due Payment business object 1474. The Due Payment business object 1406 represents a payment request or payment confirmation with regard to trade receivables and payables. The Product Tax Declaration business object 1408 represents a declaration of the product tax payables and receivables of a company to the responsible tax authority according to the tax declaration arrangement, and country-specific rules and regulations that trigger the payment to the tax authority. The Tax Due Payment business object 1474 represents a payment request or payment confirmation with regard to tax payables and receivables.

The Due Item business object uses a Synchronous Request Payment Reservation from Due Payment to Payment Processing outbound process agent 1410 to invoke one or more operations including a Request Payment Information and Provisional Payment Reservation operation 1414, a Request Payment Information and Provisional Payment Reservation Change operation 1416, and a Notify of Provisional Payment Reservation Change Cancellation operation 1418. The operations 1414, 1416, and 1418 are included in a Payment Request Out interface 1412. The Request Payment Information and Provisional Payment Reservation operation 1414 can request payment information with a provisional reservation of money in payment processing. The Request Payment Information and Provisional Payment Reservation Change operation 1416 can request payment information with a change of provisional reservation of money in payment processing. The Notify of Provisional Payment Reservation Cancellation operation 1418 can register a change of a provisional payment to the last transactional or saved state.

If the Request Payment Information and Provisional Payment Reservation operation 1414 is invoked, the operation 1414 generates a Payment Order Reservation Request message 1422. If the Request Payment Information and Provisional Payment Reservation Change operation 1416 is invoked, the operation 1416 generates a Payment Order Reservation Change Request message 1432. If the Notify of Provisional Payment Reservation Change Cancellation operation 1418 is invoked, the operation 1418 generates a Payment Order Reservation Change Cancellation Notification message 1438.

The Due Payment business object 1406 also uses a Request Payment from Due Payment to Payment Processing outbound process agent 1444 to invoke a Request Payment operation 1446 or a Request Payment Cancellation operation 1448. The operations 1444 and 1446 are included in the Payment Request Out interface 1412. The Request Payment operation 1446 sends a request for payment to the Payment Processing process component 138. This confirms a previously made provisional payment. The Request Payment Cancellation operation 1448 cancels at least one provisional, requested, or ordered payment. If the Request Payment operation 1446 is invoked, a Payment Order Request message 1450 is generated. If the Request Payment Cancellation operation 1448 is invoked, the operation 1448 generates a Payment Order Cancellation Request message 1454.

The Product Tax Declaration business object 1408 uses a Request Payment from Product Tax Declaration to Payment Processing outbound process agent 1458 to invoke the Request Payment operation 1446 or the Request Payment Cancellation operation 1448. If the Request Payment operation 1446 is invoked, a Payment Order Request message 1450 is generated. If the Request Payment Cancellation operation 1448 is invoked, the operation 1448 generates a Payment Order Cancellation Request message 1454.

The Tax Due Payment business object 1474 uses a Request Payment from Tax Due Payment to Payment Processing outbound process agent 1476 to invoke the Request Payment operation 1446 or the Request Payment Cancellation operation 1448. If the Request Payment operation 1446 is invoked, a Payment Order Request message 1450 is generated. If the Request Payment Cancellation operation 1448 is invoked, the operation 1448 generates a Payment Order Cancellation Request message 1454.

As shown in FIG. 14B, a Create Payment Reservation operation 1424 receives the Payment Order Reservation Request message 1422. The operation 1424 uses a synchronous Request Payment Reservation from Due Payment to Payment Processing inbound process agent 1428 to create, change, or cancel a payment order for a reservation request. The synchronous inbound process agent 1428 updates the Payment Order business object 448. The Payment Order business object 448 represents an order within a company to make a payment to a business partner at a specified time. A payment order can be a collective order that includes several individual orders.

A synchronous Change Payment Reservation operation 1436 receives a Payment Order Reservation Change Request message 1432. The operation 1436 uses the synchronous Request Payment Reservation from Due Payment to Payment Processing inbound process agent 1428 to update the Payment Order business object 448.

A Change Payment Reservation operation 1440 receives the Payment Order Reservation Change Cancellation Notification message 1438. A Create Payment Order operation 1452 receives the Payment Order Request message 1450. A Cancel Payment Order operation 1456 receives the Payment Order Cancellation Request message 1454. The operations 1440, 1452, and 1456 use a Maintain Payment Order inbound process agent 1442 to update the Payment Order business object 448. The Cancel Payment Order operation 1456 cancels a previously sent payment request by reference. The Create Payment Order operation 1452 cancels a request for payment. The operations 1424, 1436, 1440, 1452, and 1456 are included in a Payment Request In interface 1426.

The Payment Order business object 448 uses a Confirm Payment Request from Payment Order to Due Item Processing outbound process agent 1460 to invoke a Confirm Payment Request operation 1462. The operation 1462 confirms a processing status of a payment to a sender. The operation 1462 is included in a Payment Request Out interface 1464. The Confirm Payment Request operation 1462 generates a Payment Order Confirmation message 1466.

As shown in FIG. 14A, the Payment Order Confirmation message 1466 is received in a Change Payment based on Payment Request Confirmation operation 1468. The operation 1468 confirms the execution of a payment request or a payment request cancellation. The operation 1468 is included in a Payment Request In interface 1470. The Change Payment based on Payment Request Confirmation operation 1468 uses a Change Payment based on Payment Request Confirmation inbound process agent 1472 to update the Due Payment business object 1406.

The Create Payment Reservation 1424 operation (shown in FIG. 14B) sends a Payment Order Reservation Confirmation message 1420 to the Due Item Processing process component 140 (shown in FIG. 14A). The message 1420 is a confirmation response received in the Request Payment Information and Provisional Payment Reservation operation 1414.

The Synchronous Change Payment Reservation operation 1436 (shown in FIG. 14B) sends a Payment Order Reservation Change Confirmation message 1434 to the Due Item Processing process component 130 (shown in FIG. 14A). The message 1434 is a confirmation response received in the Request Payment Information and Provisional Payment Reservation Change operation 1416.

Interactions Between Process Components “RFQ Processing” and “Purchase Order Processing”

FIG. 15 is a block diagram showing interactions between the RFQ Processing process component 140 and the Purchase Order Processing process component 130 in the architectural design of FIG. 1. The interaction may begin when a supplier quote is created. The RFQ Processing process component 140 requests the creation of a purchase order from the Purchase Order Processing process component 130.

As shown in FIG. 15, the Request for Quote Processing process component 140 includes a Supplier Quote business object 1064. The Supplier Quote business object 1064 represents a response to a request for quote, in which a bidder offers to sell goods and services to a buyer according to the requested criteria.

The Supplier Quote business object 1064 uses a Request Purchase Order from Supplier Quote to Purchase Order Processing outbound process agent 1508 to invoke a Request Purchase Order from Winning Quote operation 1512. The operation 1512 is included in a Purchasing Out interface 1510. The operation 1512 requests a purchase order based on the awarded respective winning supplier quote. The Request Purchase Order from Winning Quote operation 1512 generates a Supplier Quote Award Notification message 1514.

A Create Purchase Order based on Winning Quote operation 1518 receives the message 1514. The operation 1518 is included in a Quote Award Notification In interface 1516. The operation 1518 creates a purchase order based on data included in a winning supplier quote. For example, if the supplier quote refers to a purchase request, data from the purchase request items are added by the operation to complete the purchase order. The Create Purchase Order based on Winning Quote operation 1518 uses a Maintain Purchase Order based on Winning Quote inbound process agent 1520 to update the Purchase Order business object 744. The Purchase Order business object 744 represents a request from a buyer to a seller to deliver a specified quantity of material, or perform a specified service, at a specified price within a specified time.

Interactions Between Process Components “Bank Statement Creation at Bank” and “Payment Processing”

FIG. 16 is a block diagram showing interactions between the Bank Statement Creation at Bank process component 152 and the Payment Processing process component 138 in the architectural design of FIG. 1. The interaction may begin when a bank statement is created at a bank. The Bank Statement Creation at Bank process component 152 notifies the Payment Processing process component 138 about transactions on a bank account. In some implementations, a bank account statement following the MT940 standard predefined by SWIFT in Canada provides balance and transaction details of an account to a financial institution on behalf of the account holder.

As shown in FIG. 16, a bank statement is created at a bank and a CA_MT940 Bank Account Statement Notification message 1616 with statement information is generated. The CA_MT940 Bank Account Statement Notification message 1616 uses Mapping Entity 1618 to transform the CA_MT940 formatted message to a Bank Account Statement Notification message 1606. The message 1606 is received in the Payment Processing process component 138 where a Create Bank Statement operation 1608 is invoked to create a bank statement. The Create Bank Statement operation 1608 is included in a Bank Statement Processing In interface 1610. A Maintain Bank Statement inbound process agent 1612 updates the House Bank Statement business object 1614 by creating a new bank statement. The House Bank Statement business object 1614 represents a legally binding notification from the house bank about the revenues items within a specific time period at a house bank account with a defined starting and closing balance.

The Bank Statement Creation at Bank process component 152 receives information from a CA_MT940_Notify of Bank Account Statement communication channel template 1620. The communication channel template 1620 can provide information from an external party about a bank statement.

Interactions Between Process Components “Purchase Request Processing” and “RFQ Processing”

FIG. 17 is a block diagram showing interactions between the Purchase Request Processing process component 128 and the RFQ Processing process component 140 in the architectural design of FIG. 1. The interaction may begin when a purchase request is created. The Purchase Request Processing process component 128 requests the creation of a request for quote from the RFQ Processing process component 140. The RFQ Processing process component 140 can confirm the performed action to the Purchase Request Processing process component 128.

As shown in FIG. 17, the Purchase Request Processing process component 128 includes the Purchase Request business object 1706. The Purchase Request business object 1706 uses a Request Request for Quote Execution from Purchase Request to RFQ Processing outbound process agent 1708 to invoke a Request RFQ Execution operation 1712. The Request RFQ Execution operation 1712 sends an RFQ Execution Request message 1714 to the RFQ Processing process component 140. The Request RFQ Execution operation 1712 is included in a Request for Quote Out interface 1710.

The RFQ Execution Request message 1714 is received by a Maintain RFQ Request operation 1718 in a Request for Quote In interface 1716. The Maintain RFQ Request operation 1718 creates an RFQ request from business documents that are involved in the bidding or negotiation process. The operation 1718 initiates a Maintain Request for Quote inbound process agent 1720 to update an RFQ Request business object 1722. The RFQ Request business object 1722 represents a request to the purchasing department to prepare a request for quote. A Confirm Request for Quote Request outbound process agent 1724 receives the request for quote, which is created or updated from purchase request processing or from purchasing contract processing, and invokes a Confirm RFQ Request operation 1728. The Confirm RFQ Request operation 1728 is included in a Request for Quote Out Interface 1726.

The Confirm RFQ Request operation 1728 sends an RFQ Execution Confirmation message 1730 to the Purchase Request Processing process component 128 to confirm an RFQ execution. A Change Purchase Request based on RFQ Execution operation 1734 receives the RFQ Execution Confirmation message 1730. The Change Purchase Request based on RFQ Execution operation 1734 is included in a Request for Quote In interface 1732. The Change Purchase Request based on RFQ Execution operation 1734 uses a Change Purchase Request based on Request for Quote Execution inbound process agent 1736 to update the references of the purchase request in the Purchase Request business object 306. The Purchase Request business object 1706 represents a request or instruction to the purchasing department to purchase specified goods or services in specified quantities at a specified price within a specified time.

Interactions Between Process Components “Supplier Invoice Processing” and “Accounting”

FIG. 18 is a block diagram showing interactions between the Supplier Invoice Processing process component 136 and the Accounting process component 103 in the architectural design of FIG. 1. The interaction may begin when a supplier invoice is created or cancelled. The Supplier Invoice Processing process component 136 requests the creation or cancellation of accounting documents from the Accounting process component 103.

As shown in FIG. 18, the Supplier Invoice Processing process component 136 includes the Supplier Invoice business object 314. The Supplier Invoice business object 314 represents a company's obligation to pay the supplier for delivered goods and services. For example, if the company returns goods or complains about services, the supplier can issue a credit memo for an amount equal to or lower than the original invoice, and can refund the money to the company.

The Supplier Invoice business object 314 uses a Notify of Supplier Invoice to Accounting outbound process agent 1808 to invoke a Notify of Invoice operation 1812 or a Notify of Invoice Cancellation operation 1814. The Notify of Invoice operation 1812 and the Notify of Invoice Cancellation operation 1814 are included in an Invoice Accounting Out interface 1810. The Notify of Invoice operation 1812 forwards accounting relevant information about a billing document (e.g., invoice, credit memo) to the Accounting process component 103 in order to assure posting. The Notify of Invoice operation 1812 generates an Invoice Accounting Notification message 1816.

The Notify of Invoice Cancellation operation 1814 cancels accounting relevant information about a billing document (e.g., invoice, credit memo). The Notify of Invoice Cancellation operation 1814 generates an Invoice Cancellation Accounting Notification message 1818.

A Create Accounting Document operation 1822 receives the Invoice Accounting Notification message 1816. The operation 1822 creates an accounting document for a customer invoice or supplier invoice. For example, the accounting document records payables, receivables, expenses, and revenues for the invoice in the Accounting process component 103. The Create Accounting Document operation 1822 is included in an Invoice Accounting In interface 1820.

A Cancel Accounting Document operation 1824 receives the Invoice Cancellation Accounting Notification message 1818. The operation 1824 receives an invoice accounting cancellation request from the Customer Invoice Processing process component or the supplier Invoice Processing process component 136. The Cancel Accounting Document operation 1824 is included in the Invoice Accounting In interface 1820.

The Create Accounting Document operation 1822 and the Cancel Accounting Document operation 1824 both use a Maintain Accounting Document based on Invoice inbound process agent 1826 to update the Accounting Notification business object 452. The Accounting Notification business object 452 represents a notification sent to the Accounting process component 103 by an operational component regarding a business transaction. The Accounting Notification business object 452 can represent the operational business transaction in a standardized form for all business transaction documents, and can include the data used to valuate the business transaction.

Interactions Between Process Components “Internal Request Processing” and “Purchase Request Processing”

FIG. 19 is a block diagram showing interactions between the Internal Request Processing process component 144 and the Purchase Request Processing process component 128. The interaction may begin when an internal request is created.

As shown in FIG. 19, the Internal Request Processing process component 144 includes an Internal Request business object 1906. The Internal Request business object 1906 represents a request from an employee of a company for the procurement of goods or services for their own or for company use.

The Internal Request business object 1906 uses a Request Purchasing from Internal Request to Purchase Request Processing outbound process agent 1908 to invoke a Request Purchasing operation 1912. The operation 1912 requests the purchase of materials and/or services. The operation 1912 is included in a Purchasing Out interface 1910. The Request Purchasing operation 1912 generates a Purchase Request Request message 1914.

A Maintain Purchase Request operation 1918 receives the Purchase Request Request message 1914. The operation 1918 creates or updates a request from a requester to a purchaser to externally procure materials and/or services (i.e., it creates or updates a purchase request). The operation 1918 is included in a Purchasing In interface 1916. The operation 1918 uses a Maintain Purchase Request inbound process agent 1920 to update the Purchase Request business object 1706. The Purchase Request business object 1706 represents a request or instruction to the purchasing department to purchase specified goods or services in specified quantities at a specified price within a specified time.

The Purchase Request business object 1706 uses a Confirm Purchase Request outbound process agent 1924 to invoke a Confirm Purchase Request operation 1928. The operation 1928 confirms the creation, change or cancellation of a purchase request to the requestor. The Confirm Purchase Request operation 1928 is included in a Purchasing Out interface 1926. The operation 1928 generates a Purchase Request Confirmation message 1930.

A Change Internal Request based on Purchase Request operation 1934 receives the Purchase Request Confirmation message 1930. The operation 1934 is included in a Purchasing In interface 1932. The operation 1934 confirms the creation, change, or cancellation of a purchase request to the requestor. The operation 1934 uses a Change Internal Request based on Purchase Request inbound process agent 1936 to update the Internal Request business object 1906.

Interactions Between Process Components “Internal Request Processing” and “Goods and Service Acknowledgement”

FIG. 20 is a block diagram showing interactions between the Internal Request Processing process component 144 and the Goods and Service Acknowledgement process component 133 in the architectural design of FIG. 1. The interaction may begin when an internal request asks for the creation of a goods and service acknowledgement. The Internal Request Processing process component 144 requests the creation of a goods and service acknowledgement from the Goods and Service Acknowledgement process component 133.

The Internal Request Processing process component 144 includes an Internal Request business object 1906. The Internal Request business object 1906 represents a request from an employee of a company for the procurement of goods or services for their own or for company use. The Internal Request Processing business object 1906 uses a Request GSA (Goods and Service Acknowledgement) from Internal Request to Goods and Service Acknowledgement outbound process agent 2008 to invoke a Request GSA based on Delivery Confirmation operation 2012. The operation 2012 generates a Goods and Service Acknowledgement Request message 2014 that is sent to the Goods and Service Acknowledgement process component 133. The Request GSA based on Delivery Confirmation operation 2012 requests express confirmation of goods and services from an overview list of internal requests. An Internal Acknowledgement Out interface 2010 includes the Request GSA based on Delivery Confirmation operation 2012.

The Goods and Service Acknowledgement process component 133 includes an Internal Acknowledgement In interface 2016. The interface 2016 includes a Create Goods and Service Acknowledgment operation 2018 to receive goods and service acknowledgement notifications. The operation 2018 receives the Goods and Service Acknowledgement Request message 2014. The Create Goods and Service Acknowledgment operation 2018 creates a goods and service acknowledgement based on a time recording or express confirmation in internal request processing. The operation 2018 uses a Maintain GSA based on Internal Acknowledgement inbound process agent 2020 to update the Goods and Service Acknowledgement business object 1206. The Goods and Service Acknowledgement business object 1206 represents a document reporting the receipt of goods and services.

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

FIG. 21 is a block diagram showing interactions between the Due Item Processing process component 142 and the Accounting process component 103 in the architectural design of FIG. 1. The interaction may begin when a payment or clearing for trade or tax receivables or payables is created or cancelled. The Due Item Processing process component 142 notifies the Accounting process component 103 about the creation or cancellation of the payment or clearing.

As shown in FIG. 21, the Due Item Processing process component 142 includes the Due Clearing business object 832, the Due Payment business object 1406, the Product Tax Declaration business object 1408, a Withholding Tax Declaration business object 2134, and the Tax Due Payment business object 1474. The Due Clearing business object 832 represents a group of receivables and payables for clearing. The Due Payment business object 1406 represents a payment request or payment confirmation with regard to trade receivables and payables. The Product Tax Declaration business object 1408 represents a declaration of the product tax payables or receivables of a company to the responsible tax authority according to the tax declaration arrangement and country-specific rules and regulations that triggers the payment to the tax authority, if applicable. The Withholding Tax Declaration business object 2134 represents a declaration of withholding tax payables of a company to a tax authority according to the tax declaration arrangement and applicable country-specific rules and regulations. The Tax Due Payment business object 1474 represents a payment request or payment confirmation with regard to tax payables and receivables.

The Due Clearing business object 832 uses a Notify of Payment from Due Clearing to Accounting outbound process agent 2112 to invoke a Notify of Payment operation 2120 or a Notify of Payment Cancellation operation 2122. The operations 2120 and 2122 are included in a Payment Accounting Out interface 2118.

The Due Payment business object 1406 uses a Notify of Payment from Due Payment to Accounting outbound process agent 2114 to invoke the Notify of Payment operation 2120 or the Notify of Payment Cancellation operation 2122.

The Product Tax Declaration business object 1408 uses a Notify of Payment from Product Tax Declaration to Accounting outbound process agent 2116 to invoke the Notify of Payment operation 2120 or the Notify of Payment Cancellation operation 2122.

The Withholding Tax Declaration business object 2134 uses a Notify of Payment from to Withholding Tax Declaration to Accounting outbound process agent 2136 to invoke the Notify of Payment operation 2120 or the Notify of Payment Cancellation operation 2122.

The Tax Due Payment business object 1474 uses a Notify of Payment from Tax Due Payment to Accounting outbound process agent 2138 to invoke the Notify of Payment operation 2120 or the Notify of Payment Cancellation operation 2122.

The Notify of Payment operation 2120 is invoked if a VAT (value added tax) declaration is released. The Notify of Payment Cancellation operation 2122 is invoked if the VAT declaration is cancelled.

If the Notify of Payment operation 2120 is invoked, the operation 2120 generates a Payment Accounting Notification message 2121. If the Notify of Payment Cancellation operation 2123 is invoked, the operation 2123 generates a Payment Cancellation Accounting Notification message 2123.

The Payment Accounting Notification message 2121 is received in a Create Accounting Document operation 2126. The Create Accounting Document operation 2126 handles the Payment Accounting Notification message 2121. The Create Accounting Document operation 2126 is included in a Payment Accounting In interface 2124.

The Payment Cancellation Accounting Notification message 2123 is received in a Cancel Accounting Document operation 2128. The Cancel Accounting Document operation 2128 handles the Payment Cancellation Accounting Notification message 2123. The Cancel Accounting Document operation 2128 is included in a Payment Accounting In interface 2124.

The Create Accounting Document operation 2126 and the Cancel Accounting Document operation 2128 both use a Maintain Accounting Document based on Payment inbound process agent 2132 to update the Accounting Notification business object 452. The Accounting Notification business object 452 represents a notification sent to the Accounting process component 103 by an operational component regarding a business transaction. For example, the Accounting Notification business object 452 can represent this operational business transaction in a standardized form for all business transaction documents, and can include the data used to valuate the business transaction.

Interactions Between Process Components “Goods and Service Acknowledgement” and “Supplier Invoice Processing”

FIG. 22 is a block diagram showing interactions between the Goods and Service Acknowledgement process component 133 and the Supplier Invoice Processing process component 136 in the architectural design of FIG. 1. The interaction may begin when a goods and service acknowledgement is posted. The Goods and Service Acknowledgement process component 133 notifies the Supplier Invoice Processing process component 136 of the invoicing-relevant data included in the goods and service acknowledgement.

As shown in FIG. 22, the Goods and Service Acknowledgement process component 133 includes the Goods and Service Acknowledgement business object 1206. The Goods and Service Acknowledgement business object 1206 represents a document that reports the receipt of goods and services.

The Goods and Service Acknowledgement business object 1206 uses a Notify of Invoicing Due from GSA (Goods and Service Acknowledgement) to Supplier Invoice Processing outbound process agent 2208 to invoke a Notify of Invoicing Due operation 2212. The Notify of Invoicing Due operation 2212 notifies the Supplier Invoice Processing process component 136 of a goods and service acknowledgement due for invoicing. The operation 2212 is included in an Invoice Verification Out interface. The Notify of Invoicing Due operation 2212 generates an Invoicing Due Notification message 2214.

A Maintain Invoice Request operation 2218 receives the Invoicing Due Notification message 2214. The operation 2218 is included in an Invoice Verification In interface 2216. The operation 2218 creates or updates a reference object in the Supplier Invoice Processing process component 136 in order to perform invoice verification with reference to a purchase order without having to access other logical deployment units. The reference object can be used for checks against the preceding documents, and to make proposals for invoice entry.

The Maintain Invoice Request operation 2218 uses a Maintain Supplier Invoice Request inbound process agent 2220 to update the Supplier Invoice Request business object 1122. The Supplier Invoice Request business object 1122 represents a request that is sent to invoice verification, advising that a supplier invoice for specified quantities and prices is expected, or is to be created through evaluation settlement.

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

FIG. 23 is a block diagram showing interactions between the Payment Processing process component 138 and the Payment Processing at a Business Partner processing component 150 in the architectural design of FIG. 1. The interaction may begin with the creation of a payment advice from a payment order within the Payment Processing process component 138. The Payment Processing process component 138 notifies the Payment Processing at the Business Partner process component 150 about payments in transfer.

As shown in FIG. 23, the Payment Processing process component 138 includes a Payment Order business object 448. The Payment Order business object 448 represents an order within a company to make a payment to a business partner at a specified time. For example, a payment order can be a collective order that includes several individual orders.

The Payment Order business object 448 uses a Notify of Payment from Payment Order to Business Partner outbound process agent 2308 to invoke a Notify of Payment operation 2312. The Notify of Payment operation 2312 is included in an Outgoing Payment Advicing Out interface 2310. The Notify of Payment operation 2312 generates data to allow an assignment of payments to receivables/payables at the business partner. The Notify of Payment operation 2312 sends a Payment Advice Notification message 2314 or a Form Payment Advice Notification 2316 to the Payment Processing at Business Partner processing component 150.

The Outgoing Payment Advicing Out interface 2310 receives a Processing At Tenant Out Web Services Reliable Messaging (WSRM) communication channel template 2318. The communication channel template 2318 can define protocols and parameters used for communication with an external party. The Payment Processing at Business Partner processing component 150 receives information from a Processing At Business Partner in XI communication channel template 2320. The Processing At Business Partner in Exchange Infrastructure (XI) communication channel template 2320 can define protocols and parameters used for communication with an external party.

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

FIG. 24 is a block diagram showing interactions between a Payment Processing process component and a Payment Processing at Business Partner process component, related to an outgoing check, in the architectural design of FIG. 1. The interaction may begin with the creation of an outgoing check from a payment order within the Payment Processing process component 138. The Payment Processing process component 138 prints an outgoing check that can be sent to the business partner.

As shown in FIG. 24, the Payment Processing process component 138 includes an Outgoing Check business object 2402. The Outgoing Check business object 2402 represents a check issued by a company payable to a business partner to fulfill a payment order. The business object 2402 uses an Issue Check From Outgoing Check to Business Partner outbound process agent 2404 to invoke an Issue Check operation 2406 when the status of an outgoing check changes to “issued” and internal printing of the check is requested. The Issue Check operation 2406 is included in a Check Issue Output Out interface 2408. The Issue Check operation 2406 can request the issuing of a check. The Issue Check operation 2406 generates a Form Check Issue Request message 2410 that is received by the Payment Processing at Business Partner process component 150.

Interactions Between Process Components “Pricing Engine” and “External Tax Calculation”

FIG. 25 is a block diagram showing interactions between the Pricing Engine process component 162 and the External Tax Calculation process component 164 in the architectural design of FIG. 1. The interaction may begin with the Pricing Engine process component 162 requesting a tax calculation from the External Tax Calculation process component 164.

As shown in FIG. 25, the Pricing Engine process component 162 includes a Price and Tax Calculation business object 2502 and a Tax Calculation business object 2504. The Price and Tax Calculation business object 2502 represents a summary of the determined price and tax components for a business case. The Tax Calculation business object 2504 represents a summary of the determined and calculated tax elements of a business case.

The Price and Tax Calculation business object 2502 uses a Synchronous Request Product Tax Calculation from Price and Tax Calculation to External Tax Calculation outbound process agent 2506 to invoke a Request Product Tax Calculation operation 25100. The Tax Calculation business object 2504 uses a Synchronous Request Product Tax Calculation from Tax Calculation to External Tax Calculation outbound process agent 2508 to invoke the Request Product Tax Calculation operation 2510 to calculate the product tax for a current document. The operation 2510 requests a product tax calculation from the External Tax Calculation process component 164. The Request Product Tax Calculation operation 2510 is included in an External Tax Calculation Out interface 2512. The Request Product Tax Calculation operation 2510 generates an External Product Tax Calculation Request message 2514 or an External Product Tax Calculation Confirmation message 2516. The messages 2514, 2516 can be received by the External Tax Calculation process component 164.

Interactions Between Process Components “Supplier Invoice Processing” and “Supplier Invoice Verification Exception Resolution”

FIG. 26 is a block diagram showing interactions between the Supplier Invoice Processing process component 136 and the Supplier Invoice Verification Exception Resolution at Processor process component 139 in the architectural design of FIG. 1.

As shown in FIG. 26, the Supplier Invoice Processing process component 136 includes a Supplier Invoice Verification Exception business object 2606. The Supplier Invoice Verification Exception business object 2606 represents a group of related issues arising during a supplier invoice verification process. In some implementations, the issues causing an exception can be bundled according to certain business criteria. A complex follow-up clarification process may be used to resolve the issues.

The Supplier Invoice Verification Exception business object 2606 uses a Request Resolution from Supplier Verification Exception to Processor outbound process agent 2608. The Request Resolution from Supplier Verification Exception to Processor outbound process agent 2608 invokes a Request Exception Resolution operation 2612 included in an Exception Resolution Out interface 2610. The operation 2612 can request the resolution of a verification exception from an external party. The operation 2612 generates an Interactive Form Supplier Invoice Verification Exception Resolution Request message 2614 that can be received by the Supplier Invoice Verification Exception Resolution at Processor process component 139.

The Supplier Invoice Verification Exception Resolution at Processor process component 139 sends an Interactive Form Supplier Invoice Verification Exception Resolution Confirmation message 2626. The message 2626 uses a Mapping Entity 2624 to transform the interactive form-based message type to a Supplier Invoice Verification Exception Resolution Confirmation message 2620 that can be received by the Supplier Invoice Processing process component 136.

The Supplier Invoice Processing process component 136 includes an Exception Resolution In interface 2616. The interface 2616 includes an Update Supplier Invoice Verification Exception operation 2618. The Exception Resolution In interface 2616 receives information from a Processing At Tenant In Web Services Reliable Messaging (WSRM) communication channel template 2628. The communication channel template 2628 can define protocols and parameters used for communication with an external party.

The Supplier Invoice Verification Exception Resolution Confirmation message 2620 is received by the Update Supplier Invoice Verification Exception operation 2618. The Update Supplier Invoice Verification Exception operation 2618 can update the Supplier Invoice Verification Exception business object 2606 according to changes made by an external party using an Update Supplier Invoice Verification Exception based on Resolution Confirmation inbound process agent 2622.

Interactions Between Process Components “Accounting Coding Block Distribution Processing” and “Project Processing”

FIG. 27 is a block diagram showing interactions between the Accounting Coding Block Distribution Processing process component 158 and the Project Processing process component 120 in the architectural design of FIG. 1.

As shown in FIG. 27, the Accounting Coding Block Distribution Processing process component 158 includes an Accounting Coding Block Distribution business object 2702. The Accounting Coding Block Distribution business object 2702 represents a distribution of coding blocks to enterprise resource changes, such as expenses or material movements. A Coding Block can be a set of accounting objects to which an enterprise resource change is assigned. The resource change can be assigned a value in an accounting process.

A Synchronous Request Project Task Accountability Information from Accounting Coding Block Distribution to Project Processing outbound process agent 2704 uses a Request Project Task Accountability Information operation 2706 to generate either an Accounting Object Check Request message 2710 or an Accounting Object Check Confirmation message 2712. The Request Project Task Accountability Information operation 2706 is included in a Project Task Accountability Out interface 2708. The operation 2706 can check given tasks for existence and availability for expense or resource assignment in financial accounting. The check can take place in the Project Processing process component 120.

A Check Project Task Accountability operation 2714 receives the Accounting Object Check Request message 2710 or the Accounting Object Check Confirmation message 2712. The operation 2714 is included in a Project Task Accountability In interface 2716, and can check whether a task can be posted for accounting. The operation 2714 uses a Synchronous Check Project Task Accountability inbound process agent 2718 to update the Project business object 2720. The Project business object 2720 represents a business undertaking with a defined goal that can be attained in a specified time frame. The business undertaking can be achieved using predefined funds and planned resources, while reaching an agreed quality level. The project can be characterized by the fact that it is unique, and that it involves an element of risk.

Interactions Between Process Components “Goods and Service Confirmation at Supplier” and “Goods and Service Acknowledgement”

FIG. 28 is a block diagram showing interactions between the Goods and Service Confirmation at Supplier process component 168 and the Goods and Service Acknowledgement 133 in the architectural design of FIG. 1. The interaction may begin when a supplier confirms the rendering of services ordered, or the receipt of goods ordered. Goods and Service Acknowledgement at Supplier process component 168 can request acknowledgement for the services rendered or the goods received. The Goods and Service Acknowledgement process component 133 can confirm the rendering of the services or the receipt of the goods.

As shown in FIG. 28, the Goods and Service Acknowledgement process component 133 receives a Service Acknowledgement Request message 2806. A Create Goods and Service Acknowledgement operation 2810 receives the message 2806. The operation 2810 creates a goods and service acknowledgement based on information received from the supplier. The supplier can also create a goods and service acknowledgement using Extensible Markup Language (XML). The Create Goods and Service Acknowledgement operation 2810 is included in an Acknowledgement In interface 2808. The Create Goods and Service Acknowledgement operation 2810 uses a Create Goods and Service Acknowledgement based on Service Acknowledgement Request inbound process agent 2812 to update the Goods and Service Acknowledgement business object 1206. The Goods and Service Acknowledgement business object 1206 represents a document that reports the receipt of goods and services.

The Goods and Service Acknowledgement business object 1206 uses a Confirm Goods and Service Acknowledgement to Supplier outbound process agent 2820 to invoke a Confirm Goods and Service Acknowledgement operation 2816. The goods and service acknowledgement, created from the business-to-business interface, is confirmed (accepted) or deleted (rejected), and an answer is expected. The Confirm Goods and Service Acknowledgement operation 2816 notifies the supplier whether the previously sent service acknowledgement request is accepted or rejected. The Confirm Goods and Service Acknowledgement operation 2816 is included in an Acknowledgement Out interface 2818. The operation 2816 generates a Service Acknowledgement Confirmation message 2814.

Interactions between Process Components “Purchase Order Processing” and “Internal Request Processing”

FIG. 29 is a block diagram showing interactions between the Purchase Order Processing process component 130 and the Internal Request Processing process component 144 in the architectural design of FIG. 1.

As shown in FIG. 29, the Purchase Order Processing process component 130 includes a Purchase Order business object 744. The Purchase Order business object 744 represents a request from a buyer to a seller to deliver a specified quantity of material, or perform a specified service, at a specified price within a specified time. The Purchase Order business object 744 uses a Notify of Purchase Order to Internal Request Processing outbound process agent 2908 to invoke a Notify of Purchase Order operation 2910 when a purchase order has been ordered, changed or cancelled and a purchase request was from internal request processing. The operation 2910 is included in an Ordering Notification Out interface 2912. The Notify of Purchase Order operation 2910 is a notification about a created, changed or cancelled purchase order. The operation 2912 generates a Purchase Order Notification message 2914 that is received by the Internal Request Processing process component 144.

The Internal Request Processing process component 144 includes an Ordering Notification In interface 2916. The interface 2916 includes a Change Internal Request based on Purchase Order operation 2918. The operation 2918 changes an internal request based on the notification of the buyer that informs the requester about the progress of procurement, and the meaning of changes to follow-on documents. For example, the creation of a goods and service acknowledgment can include the amount of received goods as well as the creation of supplier invoices. The operation 2918 uses a Change Internal Request based on Purchase Order inbound process agent 2920 to update the Internal Request business object 1906. The Internal Request business object 1906 represents a request from an employee of a company for the procurement of goods or services for their own or for company use.

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

FIG. 30 is a block diagram showing interactions between a Payment Processing process component 138 and a Payment Processing at Business Partner process component 150, related to a bill of exchange payable, in the architectural design of FIG. 1.

As shown in FIG. 30, the Payment Processing process component 138 includes a Bill Of Exchange Payable business object 3002. The Bill Of Exchange Payable business object 3002 represents a bill of exchange for an outgoing payment. The business object 3002 uses an Issue Bill Of Exchange Payable to Business Partner outbound process agent 3004 to invoke an Issue Bill Of Exchange operation 3006. The Issue Bill Of Exchange operation 3006 is included in a Bill Of Exchange Payable Issuing Output Out interface 3008. The Issue Bill Of Exchange operation 3006 can request the issuing of a bill of exchange. The Issue Bill Of Exchange operation 3006 generates a Form Bill Of Exchange Payable Issue Request message 3010 that is received by the Payment Processing at Business Partner process component 150.

Interactions Between Process Components “Internal Request Processing” and “Supplier Invoice Processing”

FIG. 31 is a block diagram showing interactions between the Internal Request Processing process component 144 and the Supplier Invoice Processing process component 136 in the architectural design of FIG. 1. The interaction may begin when an internal request asks for the creation of a supplier invoice. The Internal Request Processing process component 144 requests the creation of the supplier invoice from the Supplier Invoice Processing process component 136.

As shown in FIG. 31, the Internal Request Processing process component 144 includes an Internal Request business object 1906. The Internal Request business object 1906 represents a request from an employee of a company for the procurement of goods or services for their own or for company use. The Internal Request business object 1906 uses a Request Invoicing from Internal Request to Supplier Invoice Processing outbound process agent 3108 to invoke a Request Invoicing based on Invoice Acceptance operation 3110. The Request Invoicing based on Invoice Acceptance operation 3110 generates a Supplier Invoice Request message 3114 requesting the creation of an invoice for acknowledged goods and services. The operation 3110 is included in an Internal Invoicing Out interface 3112. The message 3114 is sent to a Create Invoice operation 3116 included in the Supplier Invoice Processing process component 136. The Create Invoice operation 3116 handles the creation of a supplier invoice out of delivered goods and rendered services. The Create Invoice operation 3116 can automatically create an invoice for the complete open amount of requested goods or services. The operation 3116 is included in an Internal Invoicing In interface 3118. The Create Invoice operation 3116 uses a Create Supplier Invoice based on Supplier Invoice Request inbound process agent 3120 to update the Supplier Invoice business object 314. The Supplier Invoice business object 314 represents a company's obligation to pay the supplier for delivered goods and services. For example, if the company returns goods or complains about services, the supplier can issue a credit memo for an amount equal to or lower than the original invoice, and can refund the money to the company. For example, for invoiced goods that require a duty, a customs duty invoice can be submitted by the customs authority, stating a company's obligation to pay tax on the import or export of goods.

The subject matter described in this specification and all of the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structural means disclosed in this specification and structural equivalents thereof, or in combinations of them. The subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more computer programs tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program (also known as a program, software, software application, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file. A program can be stored in a portion of a file that holds other programs or data, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.

The subject matter described in this specification can be implemented in a computing system that includes a back-end component (e.g., a data server), a middleware component (e.g., an application server), or a front-end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described herein), or any combination of such back-end, middleware, and front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.

The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

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 may not 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.

Claims

1. A computer program product comprising instructions encoded on a non-transitory tangible machine-readable storage medium, the instructions being structured as process components interacting with each other through service interfaces, the instructions operable when executed by at least one processor to: define a plurality of process components, each of the process components comprising a modular and application-independent package of reusable granular software implementing a respective and distinct business process, the business process comprising functionality exposed by the process component via a corresponding service interface, the plurality of process components including: a purchase request processing process component that handles creating, changing, and processing of purchase requests to locate appropriate external sources of supply;an accounting process component that handles representing all relevant business transactions for valuation and profitability analysis;a purchase order processing process component that handles creation and maintenance of purchase orders and purchase order confirmations;a goods and service acknowledgement process component that handles confirmation by an employee of goods received or services rendered;a balance of foreign payment management process component that handles collection, processing, and reporting of receivables and payables according to foreign trade regulations that are required by central banks to create the balance of payments of a country;an internal request processing process component that handles management and processing of internal requests from employees;a supplier invoice processing process component that handles management and volume processing of supplier invoices, including exception handling and approval; andan RFQ processing process component that handles the processing of requests for quotes and supplier quotes for strategic as well as operational negotiation purposes; anddefine a plurality of service interfaces, each service interface associated with exactly one process component and comprising at least one service operation, each service operation being implemented for exactly one process component, the operations comprising inbound and outbound operations, the outbound operation for a first process component being operable to send a message to a second process component of the plurality of process components, the second process component having an inbound operation for receiving the message, the sending and receiving of messages between an inbound and an outbound operation defining a message-based pair-wise interaction between the respective process components of the respective operations, the pair-wise interactions between pairs of the process components including interactions between: the purchase request processing process component and the RFQ processing process component, where the pair-wise interaction between the purchase request processing process component and the RFQ processing process component includes transmission of: an RFQ execution request message from the purchase request processing process component and the RFQ processing process component, the RFQ execution request message comprising a request for a quote, andan RFQ execution confirmation message from the RFQ processing process component to the purchase request processing process component, the RFQ execution confirmation message comprising a request to confirm an RFQ execution;the RFQ processing process component and the purchase order processing process component, where the pair-wise interaction between the RFQ processing process component and the purchase request processing process component includes transmission of: a supplier quote award notification message from the RFQ processing process component to the purchase request processing process component, the supplier quote award notification message comprising a notification of a winning supplier quote;the purchase order processing process component and the internal request processing process component, where the pair-wise interaction between the purchase order processing process component and the internal request processing process component includes transmission of: a purchase order notification message from the purchase order processing process component to the internal request processing process component, the purchase order notification message comprising a notification of a created, changed, or cancelled purchase order;the purchase order processing process component and the accounting process component, where the pair-wise interaction between the purchase order processing process component and the accounting process component includes transmission of: a sales and purchasing accounting notification message from the purchase order processing process component to the accounting process component, the sales and purchasing accounting notification message comprising a notification of a created, changed, or cancelled purchase order;the goods and service acknowledgement process component and the accounting process component, where the pair-wise interaction between the goods and service acknowledgement process component and the accounting process component includes transmission of: a goods and service acknowledgement accounting notification message from the goods and service acknowledgement process component to the accounting process component, the goods and service acknowledgement accounting notification message comprising a notification to accounting of delivered goods or rendered services, anda goods and service acknowledgement cancellation accounting notification message from the goods and services acknowledgement process component to the accounting process component, the goods and service acknowledgement cancellation accounting notification message comprising a notification to accounting of a goods and service acknowledgement cancellation;the goods and service acknowledgement process component and the supplier invoice processing process component, where the pair-wise interaction between the goods and service acknowledgement process component and the supplier invoice processing process component includes transmission of: an invoice due notification message from the goods and service acknowledgement process component to the supplier invoice processing process component, the invoice due notification message comprising a notification of a goods and service acknowledgement due for invoicing;the purchase order processing process component and the supplier invoice processing process component, where the pair-wise interaction between the purchase order processing process component and the supplier invoice processing process component includes transmission of: an invoicing due notification message from the purchase order processing process component to the supplier invoice processing process component, the invoicing due notification comprising a notification to a supplier invoice of an invoice due or when a purchase order has been created, changed, or cancelled, anda purchase order invoice values notification message from the supplier invoice processing process component to the purchase order processing process component, the purchase order invoice values notification comprising a notification that at least parts of the purchase order have been invoiced;the internal request processing process component and the goods and service acknowledgement process component, where the pair-wise interaction between the internal request order processing process component and the goods and service acknowledgement process component includes transmission of: a goods and service acknowledgement request message from the internal request processing process component to the goods and service acknowledgement process component, the goods and service acknowledgement request message comprising a request for confirmation of goods and services from a list of internal requests;the internal request processing process component and the supplier invoice processing process component, where the pair-wise interaction between the internal request order processing process component and the supplier invoice processing process component includes transmission of: a supplier invoice request message from the internal request processing process component to the supplier invoice processing process component, the supplier invoice request message comprising a request for the creation of an invoice for acknowledged goods and services; andthe supplier invoice processing process component and the accounting process component, where the pair-wise interaction between the internal request order processing process component and the supplier invoice processing process component includes transmission of: an invoice accounting notification message from the supplier invoice processing process component to the accounting process component, the invoice accounting notification message comprising a notification to accounting of information about a billing document, andan invoice cancellation accounting notification message from the supplier invoice processing process component to the accounting process component, the invoice cancellation accounting notification message comprising a notification to accounting of a cancellation of information about a billing document.
2. The product of claim 1, wherein: the plurality of process components further includes: a source of supply and determination process component that handles the maintenance of and access to sources of supply and quota arrangements for external and internal procurement processes;a project processing process component that structures, plans, and executes simple short-term measures or complex projects;a pricing engine process component that handles the processing of price and tax calculations;an accounting coding block distribution processing process component that handles the registration and checking of all accounting objects that can be assigned in a source document for a business transaction, such as cost center or project, as well as the dispatching of a check request;a due item processing process component that handles the collection, management, and monitoring of trade receivables or payables and corresponding sales tax or withholding tax;a payment processing process component that handles the processing and management of all payments as well as associated communications with financial institutions and provides input for liquidity management; and wherein:the pair-wise interactions between pairs of the process components further include interactions between: a bank statement creation at bank process component and the payment processing process component;the supplier invoice processing process component and the due item processing process component;the payment processing process component and a payment processing at business partner process component;the due item processing process component and the payment processing process component;the payment processing process component and a payment order processing at house bank process component;a customer invoice processing at supplier process component and the supplier invoice processing process component;the due item processing process component and the accounting process component;the payment processing process component and the accounting process component;the purchase order processing process component and a sales order processing at supplier process component;the RFQ processing process component and an opportunity/customer quote processing at supplier process component;the accounting coding block distribution processing process component and the project processing process component;the supplier invoice processing process component and the balance of foreign payment management process component;the supplier invoice processing process component and a customer invoice processing at supplier process component;the pricing engine process component and an external tax calculation process component;the supplier invoice processing process component and a supplier invoice verification exception resolution process component;a goods and service confirmation at supplier process component and the goods and service acknowledgement process component;the payment processing process component and the payment processing at business partner process component related to a bill of exchange payable; andthe payment processing process component and the payment processing at business partner process component related to the outgoing check.
3. The product of claim 1, wherein: each of the plurality of process components is assigned to exactly one deployment unit among multiple deployment units, and each deployment unit is deployable on a separate computer hardware platform independent of every other deployment unit; andall interaction between a process component in one deployment unit and any other process component in any other deployment unit takes place through the respective service interfaces of the two process components.
4. The product of claim 3, wherein the deployment units comprise: a financial accounting deployment unit that includes the accounting process component;a project management deployment unit that includes the project processing process component;a purchasing deployment unit that includes the purchase request processing process component, the purchase order processing process component, and the goods and service acknowledgement process component;a supplier invoicing deployment unit that includes the supplier invoice processing process component;a payment deployment unit that includes the payment process component;a strategic sourcing processing deployment unit that includes the RFQ processing process component;a due item management deployment unit that includes the due item processing process component, and the balance of foreign payment management processing component; anda requisitioning deployment unit that includes the internal request processing process component.
5. The product of claim 1, wherein: each of the process components includes one or more business objects; andnone of the business objects of any one of the process components interacts directly with any of the business objects included in any of the other process components.
6. The product of claim 5, wherein the business objects comprise a business process object.
7. The product of claim 5, wherein: none of the business objects included in any one of the process components is included in any of the other process components.
8. The product of claim 1, further comprising: a plurality of process agents, each process agent being either an inbound process agent or an outbound process agent, the inbound process agent being operable to receive a message from an inbound operation, the outbound process agent being operable to cause an outbound operation to send a message, each process agent being associated with exactly one process component.
9. The product of claim 8, wherein: the inbound process agents comprise a first inbound process agent operable to start the execution of a business process step requested in a first inbound message by creating or updating one or more business object instances.
10. The product of claim 8, wherein: the outbound process agents comprise a first asynchronous outbound process agent that is called after a business object that is associated with the first outbound process agent changes.
11. The product of claim 1, wherein the operations comprise synchronous and asynchronous operations.
12. A system comprising: a computer system comprising at least one more hardware platform for executing computer instructions, the computer instructions structured as a plurality of process components interacting with each other through service interfaces, each hardware platform including at least one processor for executing the computer instructions;memory storing a plurality of process components executable by the respective processor of the particular hardware platform, each of the process components being a comprising a modular and application-independent package of reusable granular software implementing a respective and distinct business process, the business process comprising functionality exposed by the process component via at least one service interface, the plurality of process components including: a purchase request processing process component that handles creating, changing, and processing of purchase requests to locate appropriate external sources of supply;an accounting process component that handles representing all relevant business transactions for valuation and profitability analysis;a purchase order processing process component that handles creation and maintenance of purchase orders and purchase order confirmations;a goods and service acknowledgement process component that handles confirmation by an employee of goods received or services rendered;a balance of foreign payment management process component that handles collection, processing, and reporting of receivables and payables according to foreign trade regulations that are required by central banks to create the balance of payments of a country;an internal request processing process component that handles management and processing of internal requests from employees;a supplier invoice processing process component that handles management and volume processing of supplier invoices, including exception handling and approval; andan RFQ processing process component that handles the processing of requests for quotes and supplier quotes for strategic as well as operational negotiation purposes; andthe memory further storing a plurality of service interfaces, each service interface associated with exactly one process component and comprising at least one operation, each being implemented for exactly one process component, the operations comprising inbound and outbound operations, the outbound operation for a first process component being operable to send a message to a second process component of the plurality of process components, the second process component having an inbound operation for receiving the message, the sending and receiving of messages between an inbound and an outbound operation defining a message-based pair-wise interaction between the respective process components of the respective operations, the pair-wise interactions between pairs of the process components including interactions between: the purchase request processing process component and the RFQ Processing processing process component, where the pair-wise interaction between the purchase request processing process component and the RFQ processing process component includes transmission of: an RFQ execution request message from the purchase request processing process component and the RFQ processing process component, the RFQ execution request message comprising a request for a quote, andan RFQ execution confirmation message from the RFQ processing process component to the purchase request processing process component, the RFQ execution confirmation message comprising a request to confirm an RFQ execution;the RFQ processing process component and the purchase order processing process component, where the pair-wise interaction between the RFQ processing process component and the purchase request processing process component includes transmission of: a supplier quote award notification message from the RFQ processing process component to the purchase request processing process component, the supplier quote award notification message comprising a notification of a winning supplier quote;the purchase order processing process component and the internal request processing process component, where the pair-wise interaction between the purchase order processing process component and the internal request processing process component includes transmission of: a purchase order notification message from the purchase order processing process component to the internal request processing process component, the purchase order notification message comprising a notification of a created, changed, or cancelled purchase order;the purchase order processing process component and the accounting process component, where the pair-wise interaction between the purchase order processing process component and the accounting process component includes transmission of: a sales and purchasing accounting notification message from the purchase order processing process component to the accounting process component, the sales and purchasing accounting notification message comprising a notification of a created, changed, or cancelled purchase order;the goods and service acknowledgement process component and the accounting process component, where the pair-wise interaction between the goods and service acknowledgement process component and the accounting process component includes transmission of: a goods and service acknowledgement accounting notification message from the goods and service acknowledgement process component to the accounting process component, the goods and service acknowledgement accounting notification message comprising a notification to accounting of delivered goods or rendered services, anda goods and service acknowledgement cancellation accounting notification message from the goods and services acknowledgement process component to the accounting process component, the goods and service acknowledgement cancellation accounting notification message comprising a notification to accounting of a goods and service acknowledgement cancellation;the goods and service acknowledgement process component and the supplier invoice processing process component, where the pair-wise interaction between the goods and service acknowledgement process component and the supplier invoice processing process component includes transmission of: an invoice due notification message from the goods and service acknowledgement process component to the supplier invoice processing process component, the invoice due notification message comprising a notification of a goods and service acknowledgement due for invoicing;the purchase order processing process component and the supplier invoice processing process component, where the pair-wise interaction between the purchase order processing process component and the supplier invoice processing process component includes transmission of: an invoicing due notification message from the purchase order processing process component to the supplier invoice processing process component, the invoicing due notification comprising a notification to a supplier invoice of an invoice due or when a purchase order has been created, changed, or cancelled, anda purchase order invoice values notification message from the supplier invoice processing process component to the purchase order processing process component, the purchase order invoice values notification comprising a notification that at least parts of the purchase order have been invoiced;the internal request processing process component and the goods and service acknowledgement process component, where the pair-wise interaction between the internal request order processing process component and the goods and service acknowledgement process component includes transmission of: a goods and service acknowledgement request message from the internal request processing process component to the goods and service acknowledgement process component, the goods and service acknowledgement request message comprising a request for confirmation of goods and services from a list of internal requests;the internal request processing process component and the supplier invoice processing process component, where the pair-wise interaction between the internal request order processing process component and the supplier invoice processing process component includes transmission of: a supplier invoice request message from the internal request processing process component to the supplier invoice processing process component, the supplier invoice request message comprising a request for the creation of an invoice for acknowledged goods and services; andthe supplier invoice processing process component and the accounting process component, where the pair-wise interaction between the internal request order processing process component and the supplier invoice processing process component includes transmission of: an invoice accounting notification message from the supplier invoice processing process component to the accounting process component, the invoice accounting notification message comprising a notification to accounting of information about a billing document, andan invoice cancellation accounting notification message from the supplier invoice processing process component to the accounting process component, the invoice cancellation accounting notification message comprising a notification to accounting of a cancellation of information about a billing document.
13. The system of claim 12, wherein: the plurality of process components further includes: a source of supply and determination process component that handles the maintenance of and access to sources of supply and quota arrangements for external and internal procurement processes;a project processing process component that structures, plans, and executes simple short-term measures or complex projects;a pricing engine process component that handles the processing of price and tax calculations;an accounting coding block distribution processing process component that handles the registration and checking of all accounting objects that can be assigned in a source document for a business transaction, such as cost center or project, as well as the dispatching of a check request;a due item processing process component that handles the collection, management, and monitoring of trade receivables or payables and corresponding sales tax or withholding tax;a payment processing process component that handles the processing and management of all payments as well as associated communications with financial institutions and provides input for liquidity management; and wherein:the pair-wise interactions between pairs of the process components further include interactions between: a bank statement creation at bank process component and the payment processing process component;the supplier invoice processing process component and the due item processing process component;the payment processing process component and a payment processing at business partner process component;the due item processing process component and the payment processing process component;the payment processing process component and a payment order processing at house bank process component;a customer invoice processing at supplier process component and the supplier invoice processing process component;the due item processing process component and the accounting process component;the payment processing process component and the accounting process component;the purchase order processing process component and a sales order processing at supplier process component;the RFQ processing process component and an opportunity/customer quote processing at supplier process component;the accounting coding block distribution processing process component and the project processing process component;the supplier invoice processing process component and the balance of foreign payment management process component;the supplier invoice processing process component and a customer invoice processing at supplier process component;the pricing engine process component and an external tax calculation process component;the supplier invoice processing process component and a supplier invoice verification exception resolution process component;a goods and service confirmation at supplier process component and the goods and service acknowledgement process component;the payment processing process component and the payment processing at business partner process component related to the bill of exchange payable; andthe payment processing process component and the payment processing at business partner process component related to the outgoing check.
14. The system of claim 12, wherein: each of the process components includes one or more business objects; andnone of the business objects of any one of the process components interacts directly with any of the business objects included in any of the other process components.
15. The system of claim 12, wherein: none of the business objects included in any one of the process components is included in any of the other process components.
16. The system of claim 12, further comprising: a plurality of process agents, each process agent being either an inbound process agent or an outbound process agent, the inbound process agent being operable to receive a message from an inbound operation, the outbound process agent being operable to cause an outbound operation to send a message, each process agent being associated with exactly one process component.
17. The system of claim 12, further comprising multiple hardware platforms, wherein: the project processing process component is deployed on a first hardware platform;the purchase request processing process component, the purchase order processing process component, and the goods and service acknowledgement process component are deployed on a second hardware platform;the supplier invoice processing process component is deployed on a third hardware platform;the RFQ processing process component is deployed on a fourth hardware platform;the internal request processing process component is deployed on a fifth hardware platform;the due item processing process component and the balance of foreign payment management process component are deployed on a sixth hardware platform;the accounting process component is deployed on an seventh hardware platform; andthe payment processing process component is deployed on an eighth hardware platform.
18. The system of claim 17, wherein each of the first through the eighth hardware platforms are distinct and separate from each other.

US Referenced Citations (293)

Number	Name	Date	Kind
4947321	Spence et al.	Aug 1990	A
5550734	Tarter et al.	Aug 1996	A
5560005	Hoover et al.	Sep 1996	A
5586312	Johnson et al.	Dec 1996	A
5632022	Warren et al.	May 1997	A
5634127	Cloud et al.	May 1997	A
5680619	Gudmundson et al.	Oct 1997	A
5704044	Tarter et al.	Dec 1997	A
5768119	Havekost et al.	Jun 1998	A
5822585	Noble et al.	Oct 1998	A
5832218	Gibbs et al.	Nov 1998	A
5848291	Milne et al.	Dec 1998	A
5867495	Elliott et al.	Feb 1999	A
5881230	Christensen et al.	Mar 1999	A
5893106	Brobst et al.	Apr 1999	A
5918219	Isherwood	Jun 1999	A
5987247	Lau	Nov 1999	A
H1830	Petrimoulx et al.	Jan 2000	H
6028997	Leymann et al.	Feb 2000	A
6049838	Miller et al.	Apr 2000	A
6070197	Cobb et al.	May 2000	A
6151582	Huang et al.	Nov 2000	A
6167563	Fontana et al.	Dec 2000	A
6167564	Fontana et al.	Dec 2000	A
6177932	Galdes et al.	Jan 2001	B1
6182133	Horvitz	Jan 2001	B1
6208345	Sheard et al.	Mar 2001	B1
6272672	Conway	Aug 2001	B1
6311170	Embrey	Oct 2001	B1
6338097	Krenzke et al.	Jan 2002	B1
6424991	Gish	Jul 2002	B1
6434740	Monday et al.	Aug 2002	B1
6442748	Bowman-Amuah	Aug 2002	B1
6445782	Elfe et al.	Sep 2002	B1
6446045	Stone et al.	Sep 2002	B1
6446092	Sutter	Sep 2002	B1
6473794	Guheen et al.	Oct 2002	B1
6493716	Azagury et al.	Dec 2002	B1
6571220	Ogino et al.	May 2003	B1
6594535	Costanza	Jul 2003	B1
6601233	Underwood	Jul 2003	B1
6601234	Bowman-Amuah	Jul 2003	B1
6606744	Mikurak	Aug 2003	B1
6609100	Smith et al.	Aug 2003	B2
6671673	Baseman et al.	Dec 2003	B1
6678882	Hurley et al.	Jan 2004	B1
6687734	Sellink et al.	Feb 2004	B1
6691151	Cheyer et al.	Feb 2004	B1
6721783	Blossman et al.	Apr 2004	B1
6738964	Zink et al.	May 2004	B1
6747679	Finch et al.	Jun 2004	B1
6750885	Finch et al.	Jun 2004	B1
6764009	Melick et al.	Jul 2004	B2
6789252	Burke et al.	Sep 2004	B1
6847854	Discenzo	Jan 2005	B2
6859931	Cheyer et al.	Feb 2005	B1
6889197	Lidow	May 2005	B2
6889375	Chan et al.	May 2005	B1
6895438	Ulrich	May 2005	B1
6904399	Cooper et al.	Jun 2005	B2
6907395	Hunt et al.	Jun 2005	B1
6954736	Menninger et al.	Oct 2005	B2
6985939	Fletcher et al.	Jan 2006	B2
6990466	Hu	Jan 2006	B1
7003474	Lidow	Feb 2006	B2
7031998	Archbold	Apr 2006	B2
7043448	Campbell	May 2006	B2
7047518	Little et al.	May 2006	B2
7050056	Meyringer	May 2006	B2
7050873	Discenzo	May 2006	B1
7055136	Dzoba et al.	May 2006	B2
7058587	Horne	Jun 2006	B1
7069536	Yaung	Jun 2006	B2
7072855	Godlewski et al.	Jul 2006	B1
7076766	Wirts et al.	Jul 2006	B2
7117447	Cobb et al.	Oct 2006	B2
7120597	Knudtzon et al.	Oct 2006	B1
7120896	Budhiraja et al.	Oct 2006	B2
7130807	Mikurak	Oct 2006	B1
7131069	Rush et al.	Oct 2006	B1
7155409	Stroh	Dec 2006	B1
7181694	Reiss et al.	Feb 2007	B2
7184964	Wang	Feb 2007	B2
7194431	Land et al.	Mar 2007	B1
7197740	Beringer et al.	Mar 2007	B2
7200569	Gallagher et al.	Apr 2007	B2
7206768	deGroeve et al.	Apr 2007	B1
7216091	Blandina et al.	May 2007	B1
7219107	Beringer	May 2007	B2
7222786	Renz et al.	May 2007	B2
7225240	Fox et al.	May 2007	B1
7249044	Kumar et al.	Jul 2007	B2
7257254	Tunney	Aug 2007	B2
7283973	Loghmani et al.	Oct 2007	B1
7293254	Bloesch et al.	Nov 2007	B2
7299970	Ching	Nov 2007	B1
7315830	Wirtz et al.	Jan 2008	B1
7324966	Scheer	Jan 2008	B2
7353180	Silverstone et al.	Apr 2008	B1
7356492	Hazi et al.	Apr 2008	B2
7367011	Ramsey et al.	Apr 2008	B2
7370315	Lovell et al.	May 2008	B1
7376601	Aldridge	May 2008	B1
7376604	Butcher	May 2008	B1
7376632	Sadek et al.	May 2008	B1
7383201	Matsuzaki et al.	Jun 2008	B2
7386833	Granny et al.	Jun 2008	B2
7406716	Kanamori et al.	Jul 2008	B2
7415697	Houlding	Aug 2008	B1
7418409	Goel	Aug 2008	B1
7418424	Martin et al.	Aug 2008	B2
7448022	Ram et al.	Nov 2008	B1
7451432	Shukla et al.	Nov 2008	B2
7461030	Hibler et al.	Dec 2008	B2
7469233	Shooks et al.	Dec 2008	B2
7523054	Tyson-Quah	Apr 2009	B2
7529699	Fuse et al.	May 2009	B2
7536325	Randell et al.	May 2009	B2
7536354	deGroeve et al.	May 2009	B1
7546520	Davidson et al.	Jun 2009	B2
7546575	Dillman et al.	Jun 2009	B1
7565640	Shukla et al.	Jul 2009	B2
7624371	Kulkarni et al.	Nov 2009	B2
7631291	Shukla et al.	Dec 2009	B2
7640195	Von Zimmermann et al.	Dec 2009	B2
7640291	Maturana et al.	Dec 2009	B2
7644390	Khodabandehloo et al.	Jan 2010	B2
7657406	Tolone et al.	Feb 2010	B2
7657445	Goux	Feb 2010	B1
7665083	Demant et al.	Feb 2010	B2
7668761	Jenkins et al.	Feb 2010	B2
7672888	Allin et al.	Mar 2010	B2
7681176	Wills et al.	Mar 2010	B2
7693586	Dumas et al.	Apr 2010	B2
7703073	Illowsky et al.	Apr 2010	B2
7739160	Ryan et al.	Jun 2010	B1
7742985	Digrigoli et al.	Jun 2010	B1
7747980	Illowsky et al.	Jun 2010	B2
7765156	Staniar et al.	Jul 2010	B2
7765521	Bryant	Jul 2010	B2
7788145	Wadawadigi et al.	Aug 2010	B2
7797698	Diament et al.	Sep 2010	B2
7814142	Mamou et al.	Oct 2010	B2
7822682	Arnold et al.	Oct 2010	B2
7835971	Stockton et al.	Nov 2010	B2
7904350	Ayala et al.	Mar 2011	B2
7925985	Moore	Apr 2011	B2
20020026394	Savage et al.	Feb 2002	A1
20020042756	Kumar et al.	Apr 2002	A1
20020049622	Lettich et al.	Apr 2002	A1
20020073114	Nicastro et al.	Jun 2002	A1
20020078046	Uluakar et al.	Jun 2002	A1
20020082892	Raffel et al.	Jun 2002	A1
20020103660	Cramon et al.	Aug 2002	A1
20020107826	Ramachandran et al.	Aug 2002	A1
20020120553	Bowman-Amuah	Aug 2002	A1
20020133368	Strutt et al.	Sep 2002	A1
20020138281	Cirulli et al.	Sep 2002	A1
20020138358	Scheer	Sep 2002	A1
20020143598	Scheer	Oct 2002	A1
20020156695	Edwards	Oct 2002	A1
20020161907	Moon	Oct 2002	A1
20020184111	Swanson	Dec 2002	A1
20020188486	Gil et al.	Dec 2002	A1
20020198798	Ludwig et al.	Dec 2002	A1
20020198828	Ludwig et al.	Dec 2002	A1
20030009754	Rowley et al.	Jan 2003	A1
20030069774	Hoffman et al.	Apr 2003	A1
20030074271	Viswanath et al.	Apr 2003	A1
20030074360	Chen et al.	Apr 2003	A1
20030083762	Farrah et al.	May 2003	A1
20030084127	Budhiraja et al.	May 2003	A1
20030130860	Datta et al.	Jul 2003	A1
20030182206	Hendrix et al.	Sep 2003	A1
20030212602	Schaller	Nov 2003	A1
20030233290	Yang et al.	Dec 2003	A1
20040034578	Oney et al.	Feb 2004	A1
20040111304	Meka et al.	Jun 2004	A1
20040128180	Abel et al.	Jul 2004	A1
20040153359	Ho et al.	Aug 2004	A1
20040158506	Wille	Aug 2004	A1
20040172510	Nagashima et al.	Sep 2004	A1
20040181470	Grounds	Sep 2004	A1
20040205011	Northington et al.	Oct 2004	A1
20040236639	Candadai et al.	Nov 2004	A1
20040236687	Tyson-Quah	Nov 2004	A1
20040243489	Mitchell et al.	Dec 2004	A1
20040254866	Crumbach et al.	Dec 2004	A1
20040255152	Kanamori et al.	Dec 2004	A1
20050010501	Ward	Jan 2005	A1
20050033588	Ruiz et al.	Feb 2005	A1
20050044015	Bracken et al.	Feb 2005	A1
20050060235	Byrne	Mar 2005	A2
20050060408	McIntyre et al.	Mar 2005	A1
20050065828	Kroswek et al.	Mar 2005	A1
20050108680	Cheng et al.	May 2005	A1
20050113092	Coppinger et al.	May 2005	A1
20050114829	Robin et al.	May 2005	A1
20050125310	Hazi et al.	Jun 2005	A1
20050144125	Erbey et al.	Jun 2005	A1
20050144226	Purewal	Jun 2005	A1
20050160104	Meera et al.	Jul 2005	A1
20050165784	Gomez et al.	Jul 2005	A1
20050177435	Lidow	Aug 2005	A1
20050203760	Gottumukkala et al.	Sep 2005	A1
20050203813	Welter et al.	Sep 2005	A1
20050209732	Audimoolam et al.	Sep 2005	A1
20050209943	Ballow et al.	Sep 2005	A1
20050216325	Ziad et al.	Sep 2005	A1
20050222896	Rhyne et al.	Oct 2005	A1
20050235020	Gabelmann et al.	Oct 2005	A1
20050240592	Mamou et al.	Oct 2005	A1
20050246250	Murray	Nov 2005	A1
20050246482	Gabelmann et al.	Nov 2005	A1
20050256775	Schapler et al.	Nov 2005	A1
20050256882	Able et al.	Nov 2005	A1
20050257125	Roesner et al.	Nov 2005	A1
20050262192	Mamou et al.	Nov 2005	A1
20050284934	Ernesti et al.	Dec 2005	A1
20050288987	Sattler et al.	Dec 2005	A1
20050289020	Bruns et al.	Dec 2005	A1
20050289079	Krishan et al.	Dec 2005	A1
20060004802	Phillips et al.	Jan 2006	A1
20060053063	Nagar	Mar 2006	A1
20060064344	Lidow	Mar 2006	A1
20060074704	Shukla et al.	Apr 2006	A1
20060074731	Green et al.	Apr 2006	A1
20060080338	Seubert et al.	Apr 2006	A1
20060085243	Cooper et al.	Apr 2006	A1
20060085294	Boerner et al.	Apr 2006	A1
20060085336	Seubert et al.	Apr 2006	A1
20060089886	Wong	Apr 2006	A1
20060095439	Buchmann et al.	May 2006	A1
20060129978	Abrari et al.	Jun 2006	A1
20060143029	Akbay et al.	Jun 2006	A1
20060206352	Pulianda	Sep 2006	A1
20060248504	Hughes	Nov 2006	A1
20060274720	Adams et al.	Dec 2006	A1
20060287939	Harel et al.	Dec 2006	A1
20060288350	Grigorovitch et al.	Dec 2006	A1
20070011650	Hage et al.	Jan 2007	A1
20070075916	Bump et al.	Apr 2007	A1
20070094098	Mayer et al.	Apr 2007	A1
20070094261	Phelan et al.	Apr 2007	A1
20070129964	Helmolt et al.	Jun 2007	A1
20070129984	von Helmolt et al.	Jun 2007	A1
20070129985	Helmolt et al.	Jun 2007	A1
20070150332	Grichnik et al.	Jun 2007	A1
20070150387	Seubert et al.	Jun 2007	A1
20070150855	Jeong	Jun 2007	A1
20070156430	Kaetker et al.	Jul 2007	A1
20070156475	Berger et al.	Jul 2007	A1
20070156476	Koegler et al.	Jul 2007	A1
20070156482	Bagheri	Jul 2007	A1
20070156489	Berger et al.	Jul 2007	A1
20070156493	Tebbe et al.	Jul 2007	A1
20070156499	Berger et al.	Jul 2007	A1
20070156500	Merkel et al.	Jul 2007	A1
20070156538	Peter et al.	Jul 2007	A1
20070156550	Der Emde et al.	Jul 2007	A1
20070156731	Ben-Zeev	Jul 2007	A1
20070162893	Moosmann et al.	Jul 2007	A1
20070168303	Moosmann et al.	Jul 2007	A1
20070174068	Alfandary et al.	Jul 2007	A1
20070174145	Hetzer et al.	Jul 2007	A1
20070174811	Kaetker et al.	Jul 2007	A1
20070186209	Kaetker et al.	Aug 2007	A1
20070197877	Decorte et al.	Aug 2007	A1
20070198391	Dreyer et al.	Aug 2007	A1
20070214065	Kahlon et al.	Sep 2007	A1
20070220046	Moosmann et al.	Sep 2007	A1
20070233541	Schorr et al.	Oct 2007	A1
20070233574	Koegler et al.	Oct 2007	A1
20070233575	Berger et al.	Oct 2007	A1
20070234282	Prigge et al.	Oct 2007	A1
20070239508	Fazal et al.	Oct 2007	A1
20070239569	Lucas et al.	Oct 2007	A1
20070265862	Freund et al.	Nov 2007	A1
20080004929	Raffel et al.	Jan 2008	A9
20080017722	Snyder et al.	Jan 2008	A1
20080027831	Gerhardt	Jan 2008	A1
20080065437	Dybvig	Mar 2008	A1
20080120129	Seubert et al.	May 2008	A1
20080147507	Langhammer	Jun 2008	A1
20080162382	Clayton et al.	Jul 2008	A1
20080208707	Erbey et al.	Aug 2008	A1
20080215354	Halverson et al.	Sep 2008	A1
20090037287	Baitalmal et al.	Feb 2009	A1
20090037492	Baitalmal et al.	Feb 2009	A1
20090189743	Abraham et al.	Jul 2009	A1
20090192858	Johnson	Jul 2009	A1
20100070324	Bock et al.	Mar 2010	A1
20100070336	Koegler et al.	Mar 2010	A1

Foreign Referenced Citations (3)

Number	Date	Country
0023874	Apr 2000	WO
WO 2004083984	Sep 2004	WO
WO 2005114381	Dec 2005	WO

Related Publications (1)

	Number	Date	Country
	20090171713 A1	Jul 2009	US

Architectural design for self-service procurement application software

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

US Classifications

Field of Search

US

International Classifications

Term Extension

Abstract

Description

Claims

US Referenced Citations (293)

Foreign Referenced Citations (3)

Related Publications (1)