Patent Application
20100138257
The subject matter of this patent application relates to computer software architecture, and, more particularly, to the architecture of application software for selling standardized services.
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.
This specification presents a software architecture design for a software application implementing selling standardized services.
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 selling standardized services. The software application is structured as multiple process components interacting with each other through service interfaces, and multiple service operations, each being implemented for a respective process component. The process components include a Customer Quote Processing process component; a Sales Order Processing process component; a Service Confirmation Processing process component; a Financial Accounting Master Data Management processing component; a Customer Invoice Processing process component; an Accounting process component; a Balance of Foreign Payment Management process component; a Due Item Processing process component; an Expense and Reimbursement Management process component; and a Payment Processing 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.
As shown in
The Financials deployment unit 102 includes an Accounting process component 110, a Financial Accounting Master Data Management process component 112, a Balance of Foreign Payment Management process component 114, a Due Item Processing process component 116, and a Payment Processing process component 118. The Accounting process component 110 handles the representation of relevant business transactions for valuation and profitability analysis. The Financial Accounting Master Data Management process component 112 handles the management of financial accounting master data that is used both for accounting and costing purposes.
The Balance of Foreign Payment Management process component 114 handles the collection, processing, and reporting of receivables and payables according to foreign trade regulations that are used by the financial authority of a country, such as the central bank.
The Due Item Processing process component 116 handles the collection, management, and monitoring of trade receivables or payables and corresponding sales tax or withholding tax.
The Payment Processing process component 118 handles the processing and management of all payments. The Payment Processing process component is also responsible for the associated communication with financial institutions such as banks, and provides the primary input for liquidity management.
The Customer Relationship Management deployment unit 106 includes a Customer Quote Processing process component 120, a Sales Order Processing process component 122, and a Service Confirmation Processing process component 124. The Customer Quote Processing process component 120 handles the processing of quotes to customers offering the delivery of goods according to specific terms. The Sales Order Processing process component 122 handles the processing of customers' requests to a seller for the delivery of goods, on a specific date, for a specific quantity, and for a specific price. The Service Confirmation Processing process component 124 handles the reporting back of actual times and quantities for services provided, and spare parts consumed related to the execution of a service order.
The Customer Invoicing deployment unit 108 includes a Customer Invoicing Processing process component 126 which invoices customers for the delivery of goods or the provision of services.
The Expense and Reimbursement deployment unit 104 includes an Expense and Reimbursement Management process component 128. The Expense and Reimbursement Management process component 128 handles the management and monitoring of expenses incurred by employees, and the reimbursement of such expenses to employees. It includes the process of verifying the validity of expenses submitted by internal or external employees, settling the expenses in conformance with legal requirements and company policy, reimbursing the expenses to the employees, transferring the expenses to financial accounting, and transferring taxable amounts to payroll for internal employees.
The foundation layer, described below, includes a Pricing Engine processing component 130 and a Payment Authorization process component 132. The Pricing Engine process component 130 processes price and tax calculation. The Payment Authorization process component 132 provides a reusable service that is used to process an authorization request for a payment made using a payment card at a clearing house. For example, the Payment Authorization process component 132 can authorize a payment for goods or services purchased from an online store using a credit card.
A number of external process components, described below, will be used to describe the architectural design. These include a Supplier Invoice Processing at Customer process component 134, a Due Item Processing at Business Partner process component 136, a Payment Processing at Business Partner process component 138, a Bank Statement Creation at Bank process component 140, a Payment Order Processing at House Bank process component 142, an External Tax Calculation process component 144, and a Settlement Processing at Clearing House process component 146.
The Supplier Invoice Processing at Customer process component 134 receives messages from the Customer Invoice Processing process component 126. The Due Item Processing at Business Partner process component 136 receives messages from the Due Item Processing process component 116. The Payment Processing at Business Partner process component 138 sends and receives messages from the Payment Processing process component 118. The Bank Statement Creation at Bank process component 140 sends messages to the Payment Processing process component 118. The Payment Order Processing at House Bank process component 142 receives messages from the Payment Processing process component 118. The External Tax Calculation process component 144 receives messages from the Pricing Engine process component 130. The Settlement Processing at Clearing House process component 146 receives messages from the Payment Authorization process component 132.
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
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 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 “Sales Order Processing” and “Financial Accounting Master Data Management”
As shown in
The Sales Order business object 302 uses a Synchronous Request Product Valuation from Sales Order to Financial Accounting Master Data outbound process agent 304 to invoke a Request Product Valuation operation 306. The Request Product Valuation operation 306 is included in a Product and Resource Valuation Out interface 308. The operation 306 requests a product valuation. The Request Product Valuation operation 306 sends a Product and Resource Valuation Query message 310 to the Financial Accounting Master Data Management process component 140.
A Synchronous Valuate Product and Resource operation 314 receives the Product and Resource Valuation Query message 310. The operation 314 is included in a Product and Resource Valuation In interface 316, and can synchronize access to product pricing information. The Synchronous Valuate Product and Resource operation 314 valuates one or more products or resources with internal valuation prices or internal cost rates. For example, the product or resource can be valuated as an individual object or in the context of a business transaction. For example, the result of the valuation for a product or resources can be a price and an amount (optional) provided that a quantity was entered for the valuation. The operation 314 uses a Synchronous Valuate Product and Resource synchronous inbound process agent 318 to update either a Material Valuation Data business object 320, a Service Product Valuation Data business object 322, or a Resource Valuation Data business object 324. The Material Valuation Data business object 320 represents data that references a material or material group for valuating business transactions, for cost estimates, and for value-based management of material inventories. For example, business object 320 contains internal valuation prices for a material or material group. The Service Product Valuation Data business object 322 represents data that references a service product or service product group for the valuation of business transactions and for cost estimates and cost accounting. For example, business object 322 contains the internal cost rates for a service product or service product group. The Resource Valuation Data business object 324 represents data that references a resource or resource group for the valuation of business transactions and for cost estimates and cost accounting. For example, business object 324 contains the internal cost rates for a resource or resource group.
The Financial Accounting Master Data Management process component 140 sends a Product and Resource Valuation Response message 312 to the Sales Order Processing process component 122.
Interactions between Process Components “Payment Processing” and “Due Item Processing”
The Payment Processing process component 118 includes a Payment Allocation business object 402. The Payment Allocation business object 402 represents an assignment of a payment item to a payment reasons from which the payment item originated. The Payment Allocation business object 402 uses a Request Clearing Maintenance from Payment Allocation to Due Item Processing outbound process agent 404 to invoke a Request Clearing operation 408 or a Request Clearing Cancellation operation 410. The operations 408 and 410 are included in a Clearing Out interface 412. The Request Clearing operation 408 requests the clearing of payments within Due Item Processing process component 116. The Request Clearing Cancellation operation 410 cancels a previously sent clearing request from Due Item Processing process component 116 by reference. If the Request Clearing operation 408 is invoked, a Clearing Request message 418 is sent. If the Request Clearing Cancellation operation 410 is invoked, a Clearing Cancellation Request message 420 is sent.
A Create Clearing operation 424 receives the Clearing Request message 418. The Create Clearing operation 424 creates a clearing for business partner-initiated payments. The operation 424 uses a Maintain Clearing inbound process agent 434 to update either a Tax Due Payment business object 440 or a Due Payment business object 442. The Tax Due Payment business object 440 represents a payment request or payment confirmation with regard to tax payables and receivables. The Due Payment business object 442 represents a payment request or payment confirmation with regard to trade receivables and payables.
A Cancel Clearing operation 426 receives the Clearing Cancellation Request message 420. The Cancel Clearing operation 426 cancels a previously sent clearing request by reference. The operation 426 uses the Maintain Clearing inbound process agent 434 to update either the Tax Due Payment business object 440 or the Due Payment business object 442. The operations 424 and 426 are included in a Clearing In interface 428.
The Tax Due Payment business object 440 uses a Confirm Clearing from Tax Due Payment to Payment Processing outbound process agent 436 to invoke a Confirm Clearing operation 430. The Due Payment business object 442 uses a Confirm Clearing from Due Payment to Payment Processing outbound process agent 438 to invoke the Confirm Clearing operation 430. The operation 430 sends a confirmation to the Payment Processing process component 118 for a clearing request. The operation 430 is included in a Clearing Out interface 432. The Confirm Clearing operation 430 sends a Clearing Confirmation message 422.
The Clearing Confirmation message 422 is received by a Change Payment Allocation based on Clearing Request Confirmation operation 414. The operation 414 confirms the execution or rejection of a sent clearing request. The operation 414 is included in a Clearing In interface 416. The Change Payment Allocation based on Clearing Request Confirmation operation 414 uses a Change Payment Allocation based on Clearing Request Confirmation inbound process agent 406 to update the Payment Allocation business object 402.
Interactions between Process Components “Customer Invoice Processing” and “Balance of Foreign Payment Management”
As shown in
The Customer Invoice business object 502 uses a Notify of Customer Invoice to Balance of Foreign Payments Management outbound process agent 508 to invoke a Notify of Invoice operation 510. The operation 510 informs the Balance Of Foreign Payment Management process component 114 about an invoice in order to track a receivable from or a payable to a non-resident business partner. Alternatively, the Customer Invoice business object 502 uses the outbound process agent 508 to invoke a Notify of Invoice Cancellation operation 512. The operation 512 informs the Balance Of Foreign Payment Management process component 114 about the cancellation of an invoice in order to also cancel information about a receivable from or a payable to a non-resident business partner. Operations 510 and 512 are included in a Foreign Receivable Payable Notification Out interface 514. The Notify of Invoice operation 510 sends a Foreign Receivable Payable Notification message 516 to the Balance Of Foreign Payment Management process component 114. The Notify of Invoice Cancellation operation 512 sends a Foreign Receivable Payable Cancellation Notification message 518 to the Balance Of Foreign Payment Management process component 114.
The messages 516 and 518 are received by a Create Foreign Receivable Payable operation 522 and a Cancel Foreign Receivable Payable operation 524, respectively. The Create Foreign Receivable Payable operation 522 creates a foreign receivable or payable from foreign trade. The Cancel Foreign Receivable Payable operation 524 cancels a foreign receivable or payable. The Create Foreign Receivable Payable operation 522 and the Cancel Foreign Receivable Payable operation 524 are both included in a Foreign Receivable Payable Notification In interface 520.
The operations 522 and 524 use a Maintain Foreign Receivable Payable inbound process agent 526 to create, change, or cancel a foreign receivable or payable in a Foreign Receivable Payable business object 530. The Foreign Receivable Payable business object 530 represents a receivable from or payable to a non-resident business partner.
Interactions between Process Components “Service Confirmation Processing” and “Accounting”
As shown in
The Sales and Purchasing Accounting Notification message 610 is received by a Create Accounting Notification operation 612. The Create Accounting Notification operation 612 is included in a Sales and Order Purchasing Accounting In interface 614. The Create Accounting Notification operation 612 creates an accounting notification based on production order data received from production. The Create Accounting Notification operation 612 uses a Maintain Subledger Account based on Sales and Purchasing inbound process agent 616 to update an Accounting Notification business object 618. The Accounting Notification business object 618 represents a notification sent to the Financials deployment unit 102 by an operational component regarding a business transaction. For example, the Accounting Notification business object 618 can represent the operational business transaction in a standardized form for all business transaction documents and contains the data needed to valuate the business transaction.
Interactions between Process Components “Sales Order Processing” and “Due Item Processing”
As shown in
The Sales Order business object 302 uses a Synchronous Request Creditworthiness from Sales Order to Due Item Processing synchronous outbound process agent 704 to invoke a Request Creditworthiness operation 706. The operation 706 checks whether a particular sales order is covered by the current credit limit of the customer. The Request Creditworthiness operation 706 is included in a Credit Usage Out interface 708. The Request Creditworthiness operation 706 sends a Request Creditworthiness Query message 710 to the Due Item Processing process component 116.
The Request Creditworthiness Query message 710 is received by a Check Creditworthiness operation 712. The operation 712 is included in a Credit Usage In interface 714. The Check Creditworthiness operation 712 is used to initiate the execution of a credit check. The operation 712 uses a Check Creditworthiness Based on Trade Receivables Payables Register synchronous inbound process agent 716 to update a Trade Receivables Payables Register business object 718. The Trade Receivables Payables Register business object 718 represents the register of all trade receivables and payables of a company from or to its business partners. The Check Creditworthiness operation 712 sends a Request Creditworthiness Response message 720 to update the Sales Order Processing process component 122 about the creditworthiness of a party.
Interactions between Process Components “Customer Invoice Processing” and “Accounting”
As shown in
The Customer Invoice business object 502 uses a Notify of Customer Invoice to Accounting outbound process agent 804 to invoke a Notify of Invoice operation 806 or a Notify of Invoice Cancellation operation 808. The Notify of Invoice operation 806 and the Notify of Invoice Cancellation operation 808 are included in an Invoice Accounting Out interface 810. The Notify of Invoice Cancellation operation 806 informs the Accounting process component 110 about the cancellation of invoices or credit memos. The Notify of Invoice operation 806 informs the Accounting process component 110 about the creation of invoices or credit memos. The Notify of Invoice operation 806 sends an Invoice Accounting Notification message 812. The message 812 is a notification about the creation of a new supplier invoice or a change to an existing supplier invoice. The Notify of Invoice Cancellation operation 808 sends an Invoice Cancellation Accounting Notification message 814. The message 814 is a notification about the cancellation of a an incoming or outgoing invoice or credit memo, or of an item in such a business transaction.
A Create Accounting Document operation 816 receives the Invoice Accounting Notification message 812. The operation 816 creates an accounting document based on invoice data received from the Customer Invoice Processing process component 126. In some implementations, the received data can first be converted into an accounting notification from which one or more accounting documents are created according to the relevant sets of books. The Create Accounting Document operation 816 is included in an Invoice Accounting In interface 820.
A Cancel Accounting Document operation 818 receives the Invoice Cancellation Accounting Notification message 814. The operation 818 cancels an existing accounting document based on cancellation data received from the Customer Invoice Processing process component 126. In some implementations, the received data can be converted into an accounting notification from which one or more reversal accounting documents are created according to the relevant sets of books. The Cancel Accounting Document operation 818 is included in the Invoice Accounting In interface 820.
The Create Accounting Document operation 816 and the Cancel Accounting Document operation 818 both use a Maintain Accounting Document based on Invoice inbound process agent 822 to update the Accounting Notification business object 618. The Accounting Notification business object 618 represents a notification sent to the Financials deployment unit 102 by an operational component regarding a business transaction. For example, the Accounting Notification business object 618 can represent the operational business transaction in a standardized form for all business transaction documents and contains the data for valuating the business transaction.
Interactions between Process Components “Sales Order Processing” and “Customer Invoice Processing”
As shown in
The Customer Invoice Request Request message 916 is received in a Maintain Customer Invoice Request operation 920. The Maintain Customer Invoice Request operation 920 creates, updates, or cancels a customer invoice request. The operation 920 is included in a Request Invoicing In interface 922. The Maintain Customer Invoice Request operation 920 uses a Maintain Customer Invoice Request inbound process agent 928 to update a Customer Invoice Request business object 932. The Customer Invoice Request business object 932 represents a request to create one or several customer invoices, or to take account of the data for the underlying business document when creating a customer invoice.
The Customer Invoice business object 502 uses a Confirm Customer Invoice to Sales Order Processing outbound process agent 930 to invoke a Confirm Invoicing operation 924. The operation 924 confirms that invoicing has taken place. The Confirm Invoicing operation 924 is included in a Request Invoicing Out interface 926. The operation 924 generates a Customer Invoice Issued Confirmation message 918.
A Change Sales Order based on Customer Invoice operation 912 receives the Customer Invoice Issued Confirmation message 918. The Change Sales Order based on Customer Invoice operation 912 is included in a Request Invoicing In interface 914. The Change Sales Order based on Customer Invoice operation 912 updates a sales order based on changes from the customer invoice. The operation 912 uses a Change Sales Order based on Customer Invoice inbound process agent 906 to update the Sales Order business object 302.
Interactions between Process Components “Service Confirmation Processing” and “Customer Invoice Processing”
As shown in
The Service Confirmation business object 602 uses a Request Invoicing from Service Confirmation to Customer Invoice Processing outbound process agent 1004 to invoke a Request Invoicing operation 1008. The operation 1008 requests invoicing of services provided and spare parts consumed based on information in the service confirmation. The Request Invoicing operation 1008 is included in a Request Invoicing Out interface 1010. The Request Invoicing operation 1008 sends a Customer Invoice Request Request message 1016 to the Customer Invoice Processing process component 126.
A Maintain Customer Invoice Request operation 1020 receives the message 1016. The Maintain Customer Invoice Request operation 1020 creates, updates, or cancels a customer invoice request. The operation 1020 is included in a Request Invoicing In interface 1022. The Maintain Customer Invoice Request operation 1020 uses a Maintain Customer Invoice Request inbound process agent 1028 to update a Customer Invoice Request business object 932. The Customer Invoice Request business object 932 represents a request to create one or several customer invoices, or to take account of the data for the underlying business document when creating a customer invoice.
The Customer Invoice Processing process component 126 includes the Customer Invoice business object 502. The Customer Invoice business object 502 represents a binding statement of amounts receivable resulting, for example, from deliveries to a customer, services performed for a customer, adjustments to these receivables, or credit memos to a customer.
The Customer Invoice business object 502 uses a Confirm Customer Invoice to Service Confirmation Processing outbound process agent 1030 to invoke a Confirm Invoicing operation 1024. The operation 1024 confirms that invoicing has taken place. The Confirm Invoicing operation 1024 is included in a Request Invoicing Out interface 1026. The operation 1024 sends a Customer Invoice Issued Confirmation message 1018 to the Service Confirmation Processing process component 124.
A Change Service Confirmation based on Customer Invoice operation 1012 receives the Customer Invoice Issued Confirmation message 1018. The Change Service Confirmation based on Customer Invoice operation 1012 is included in a Request Invoicing In interface 1014. The Change Service Confirmation based on Customer Invoice operation 1012 updates a service confirmation based on information from related customer invoices. The operation 1012 uses a Change Service Confirmation based on Customer Invoice inbound process agent 1006 to update the Service Confirmation business object 602.
Interactions between Process Components “Payment Authorization” and “Settlement Processing at Clearing House”
As shown in
The Payment Card Payment Authorization business object 1102 uses a Request Payment Card Payment Authorization synchronous outbound process agent 1104 to invoke a Request Payment Authorization operation 1106. The Request Payment Authorization operation 1106 is included in a Payment Authorization Requesting Out interface 1108. The Payment Authorization process component 132 receives information from a Processing at Tenant Out Web Services Reliable Messaging (WSRM) communication channel template 1114. The communication channel template 1114 can define protocols and parameters used for communication with an external party. The Request Payment Authorization operation 1106 sends to a clearing house a request for authorization of a payment made by a payment card. The Request Payment Authorization operation 1106 sends a Payment Card Payment Authorization Request message 1110 to the Settlement Processing at Clearing House processing component 146. The Request Payment Authorization operation 1106 receives a Payment Card Payment Authorization Confirmation message 1112 from the Settlement Processing at Clearing House processing component 146.
The Settlement Processing at Clearing House process component 146 receives information from a Processing at Business Partner In Exchange Infrastructure (XI) communication channel template 1116. The communication channel template 1116 can define protocols and parameters used for communication with an external party. The Settlement Processing at Clearing House process component 146 sends information to the Payment Authorization process component 132 using a Processing at Business Partner in SOAP communication channel template 1118. The communication channel template 1118 can define protocols and parameters used for communication with an external party.
Interactions between Process Components “Pricing Engine” and “External Tax Calculation”
As shown in
The Price and Tax Calculation business object 1202 uses a Synchronous Request Product Tax Calculation from Price and Tax Calculation to External Tax Calculation synchronous outbound process agent 1204 to invoke a Request Product Tax Calculation operation 1206. The Tax Calculation business object 1203 uses a Synchronous Request Product Tax Calculation from Tax Calculation to External Tax Calculation synchronous outbound process agent 1205 to invoke the Request Product Tax Calculation operation 1206. The operation 1206 requests a product tax calculation from the External Tax Calculation process component 144. The Request Product Tax Calculation operation 1206 is included in an External Tax Calculation Out interface 1208. The Pricing Engine process component 130 sends information to the External Tax Calculation process component 144 using a Processing at Tenant In Web Services Reliable Messaging (WSRM) communication channel template 1214. The communication channel template 1214 can define protocols and parameters used for communication with an external party.
The Request Product Tax Calculation operation 1206 sends an External Product Tax Calculation Request message 1210 to the External Tax Calculation process component 144. The Request Product Tax Calculation operation 1206 receives an External Product Tax Calculation Confirmation message 1212 from the External Tax Calculation process component 144.
Interactions between Process Components “Customer Quote Processing” and “Due Item Processing”
As shown in
The Customer Quote business object 1302 uses a Synchronous Request Creditworthiness from Customer Quote to Due Item Processing synchronous outbound process agent 1304 to invoke a Request Creditworthiness operation 1306. The operation 1306 verifies the data or value of a current document against an actual credit standing of customer. The Request Creditworthiness operation 1306 is included in a Credit Usage Out interface 1308. The Request Creditworthiness operation 1306 sends a Request Credit Worthiness Query message 1310 to the Due Item Processing process component 116.
The Request Credit Worthiness Query message 1310 is received by a Check Creditworthiness operation 1312. The operation 1312 is included in a Credit Usage In interface 1314. The Check Creditworthiness operation 1312 is used to initiate the execution of a credit check. The operation 1312 uses a Check Creditworthiness Based on Trade Receivables Payables Register synchronous inbound process agent 1316 to update the Trade Receivables Payables Register business object 1318. The Trade Receivables Payables Register business object 1318 represents the register of all trade receivables and payables of a company from or to its business partners. The Check Creditworthiness operation 1312 sends a Request Credit Worthiness Response message 1320 to update the Customer Quote Processing process component 120 about the creditworthiness of a party.
Interactions between Process Components “Payment Processing at Business Partner” and “Payment Processing”
As shown in
The Create Payment Advice operation 1418 uses a Maintain Payment Advice inbound process agent 1422 to update a Payment Advice business object 1424. The Payment Advice business object 1424 represents an announcement of a payment transaction by a business partner to the company, specifying payment reasons.
The Payment Processing at Business Partner process component 138 sends information to the Payment Processing process component 118 using a Processing at Business Partner Out Exchange Infrastructure (XI) communication channel template 1426. The communication channel template 1426 can define protocols and parameters used for communication with an external party.
Interactions between Process Components “Sales Order Processing” and “Accounting”
As shown in
The Sales Order business object 302 uses a Notify of Sales Order to Accounting outbound process agent 1504 to invoke a Notify of Sales Order operation 1506. The Notify of Sales Order operation 1506 informs the Accounting process component 110 when a sales order is created, updated, or changed. Also, when a sales order contains a service provision, accounting can be notified when the service provision is created or cancelled. The operation 1506 is included in a Sales and Purchasing Accounting Out interface 1508. The operation 1506 sends a Sales and Purchasing Accounting Notification message 1510.
A Create Accounting Notification operation 1512 receives the Sales and Purchasing Accounting Notification message 1510. The operation 1512 creates an accounting notification based on order data received from the Sales Order Processing process component 112. The operation 1512 is included in a Sales and Order Purchasing Accounting In interface 1514. The Create Accounting Notification operation 1512 uses a Maintain Subledger Account based on Sales and Purchasing inbound process agent 1516 to update the Accounting Notification business object 618. The Accounting Notification business object 618 represents a notification sent to the Financial Accounting deployment unit 102 by an operational component regarding a business transaction. The Accounting Notification business object 618 also represents the business transaction in a standardized form for all business transaction documents and contains the data needed to valuate the business transaction.
Interactions between Process Components “Payment Processing” and “Payment Order Processing at House Bank”
As shown in
The Bank Payment Order business object 1610 uses a Request File Based Payment Order from Bank Payment Order to House Bank outbound process agent 1616 to invoke a Request File based Payment Order operation 1618. The Request File based Payment Order operation 1618 instructs a house bank, using a file, to make a bank transfer, a direct debit, an outgoing check, or a bill of exchange payable. The operation 1618 is included in a Payment Ordering Out interface 1620. The Request File based Payment Order operation 1618 sends a File Based Collective Payment Order Request message 1622. The File Based Collective Payment Order Request message 1622 uses Mapping Entity 1624 to transform the file-based message type to a Collective Payment Order Request message 1626 that is received by the Payment Order Processing at House Bank process component 142. The Collective Payment Order Request message 1626 is in a format that the house bank (e.g., a bank located in Germany) can understand. The Payment Order Processing at House Bank process component 142 receives information from a Payment Order Request communication channel template 1628. The communication channel template 1628 can define protocols and parameters used for communication with an external party.
Interactions between Process Components “Customer Quote Processing” and “Financial Accounting Master Data Management”
The Customer Quote business object 1302 uses a Synchronous Request Product Valuation from Customer Quote to Financial Accounting Master Data synchronous outbound process agent 1704 to invoke a Request Product Valuation operation 1706. The Request Product Valuation operation 1706 is included in a Product and Resource Valuation Out interface 1708. The operation 1706 requests a product valuation. The operation 1706 sends a Product and Resource Valuation Query message 1710 to the Financial Accounting Master Data Management process component 112.
A Synchronous Valuate Product and Resource operation 1714 receives the Product and Resource Valuation Query message 1710. The operation 1714 is included in a Product and Resource Valuation In interface 1716. The operation 1714 valuates one or more products or resources with internal valuation prices or internal cost rates. In some implementations, the product or resource can be valuated as an individual object or in the context of a business transaction. The result of the valuation for a product or resources can be a price and an amount, that can be optional, provided that a quantity was entered for the valuation. The operation 1714 uses a Synchronous Valuate Product and Resource synchronous inbound process agent 1718 to update either the Material Valuation Data business object 320, the Service Product Valuation Data business object 322, or the Resource Valuation Data business object 324. The Material Valuation Data business object 320 represents data that references a material or material group for valuating business transactions, for cost estimates, and for value-based management of material inventories. In particular, business object 320 contains internal valuation prices for a material or material group. The Service Product Valuation Data business object 322 represents data that references a service product or service product group for the valuation of business transactions and for cost estimates and cost accounting. For example, business object 322 contains the internal cost rates for a service product or service product group. The Resource Valuation Data business object 324 represents data that references a resource or resource group for the valuation of business transactions and for cost estimates and cost accounting. For example, business object 324 contains the internal cost rates for a resource or resource group.
The Financial Accounting Master Data Management process component 112 sends a Product and Resource Valuation Response message 1720 to the Customer Quote Processing process component 120.
Interactions between Process Components “Bank Statement Creation at Bank” and “Payment Processing”
The Bank Statement Creation at Bank process component 124 receives information from the Payment Processing process component 118 using a Notify Of Bank Account Statement Attachment communication channel template 1820. The communication channel template 1820 can define protocols and parameters used for communication with an external party.
Interactions between Process Components “Payment Processing” and “Payment Processing at Business Partner”
As shown in
Interactions between Process Components “Due Item Processing” and “Due Item Processing at Business Partner”
As shown in
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 software architecture design or of what may be claimed, but rather as an exemplification of preferred embodiments of the software architecture design. Certain features that are described in this specification in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be provided in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
The subject matter has been described in terms of particular variations, but other variations can be implemented and are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous. Other variations are within the scope of the following claims.
