WO2007112954A2 - Providing customer relationship management application as enterprise services - Google Patents
Providing customer relationship management application as enterprise services Download PDFInfo
- Publication number
- WO2007112954A2 WO2007112954A2 PCT/EP2007/002840 EP2007002840W WO2007112954A2 WO 2007112954 A2 WO2007112954 A2 WO 2007112954A2 EP 2007002840 W EP2007002840 W EP 2007002840W WO 2007112954 A2 WO2007112954 A2 WO 2007112954A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- customer
- service
- request
- notify
- change
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
- G06Q30/0635—Processing of requisition or of purchase orders
Definitions
- This specification relates to data processing systems implemented on computers, and more particular to data processing systems providing services in the nature of web 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.
- 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.
- Web services are one technology for making the functionality of software applications available to other software, including other applications.
- a web service is a standards-based way of encapsulating the functionality of an application that other applications can locate and access.
- a service-oriented architecture is a distributed software model within which functionality is defined as independent web services. Within a service-oriented architecture, web services can be used in defined sequences according to business logic to form applications that enable business processes.
- Enterprise services are web services that have an enterprise-level business value.
- a system in one embodiment implements a services architecture design that provides enterprise services having customer relationship management functionality at the level of an enterprise application.
- the design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.
- 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.
- FIGS. IA, IB and 1C collectively illustrate a high-level view of a software architectural design and implementation of a suite enterprise software services having customer relationship management functionality.
- FIGS. 2 A, 2B, 2C and 2D are block diagrams collectively showing a customer invoice processing process component.
- FIG. 3 is a block diagram showing an opportunity processing process component.
- FIGS. 4A and 4B are block diagrams collectively showing a service confirmation processing process component.
- FIGS. 5A and 5B are block diagrams collectively showing a service order processing process component.
- FIGS. 6A and 6B are block diagrams collectively showing a service request processing process component.
- FIG. 7 is a block diagram of a customer return processing process component.
- FIG. 8 is a block diagram of an activity management process component.
- FIGS. 9A, 9B and 9C are block diagrams collectively showing a sales order processing process component.
- FIG. 10 is a block diagram of a customer quote processing process component. Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION
- FIGS. IA, IB and 1C collectively illustrate a high-level view of a software architectural design, and of application software implementations of the design, that provides a suite of enterprise service operations, which can be organized into interfaces, having customer relationship management application functionality.
- the software corresponding to FIGS. IA and IB in one implementation is for deployment in an application layer of an application server, while the software corresponding to FIG. 1C is for deployment in a foundation layer, which will be described below.
- the elements of the architecture include the business object, the process component, the service operation (or simply, the operation), the service interface, the message, and the deployment unit.
- the elements can also include process agents and reuse service components. These will be generally described below.
- the software is implemented to be deployed on an application platform that includes a foundation layer that contains all fundamental entities that can used from multiple deployment units. These entities can be process components, business objects or 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.
- 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 enterprise application service interfaces.
- the elements of the architecture are at times described in this specification as being contained or included in other elements; for example, a process component is described as being contained in a deployment unit. It should be understood, however, that such operational inclusion can be realized in a variety of ways and is not limited to a physical inclusion of the entirety of one element in another.
- the architectural elements include the business object.
- a business object is a representation of a type of a uniquely identifiable business entity (an object instance) described by a structural model. Processes operate on business objects.
- a business object represents a specific view on some well-defined business content.
- a business object represents content, and instances of business objects include content, which a typical business user would expect and understand with little explanation. Whether an object as a type or an instance of an object is intended by the term is generally clear from the context, so the distinction will be made explicitly only when necessary. Properly implemented, business objects are implemented free of redundancies.
- Business objects are further categorized as business process objects, master data objects, mass data run objects, dependent objects, and transformed objects.
- a master data object is an object that encapsulates master data (i.e., data that is valid for a period of time).
- a business process object which is the kind of business object generally found in a process component, is an object that encapsulates transactional data (i.e., data that is valid for a point in time).
- a mass data run object is an application object that executes an algorithm for a particular mass data run.
- An instance of a mass data run object contains a particular set of selections and parameters.
- a mass data run object implements an algorithm that modifies, manages, and/or processes a large amount of data in multiple transactions, possibly but not necessarily with parallel processing.
- a dependent object is a business object used as a reuse part in another business object.
- a dependent object represents a concept that cannot stand by itself from a business point of view. Instances of dependent objects only occur in the context of a non-dependent business object.
- a transformed object is a transformation of multiple business objects for a well-defined purpose. It transforms the structure of multiple business objects into a common structure. A transformed object does not have its own persistency.
- the architectural elements also include the process component.
- a process component is a software package that realizes a business process and generally exposes its functionality as services. The functionality contains business transactions.
- a process component contains one or more semantically related business objects. Any business object belongs to no more than one process component.
- Process components are modular and context-independent. That they are context- independent means that a process component is not specific to any specific application and is reusable. The process component is the smallest (most granular) element of reuse in the architecture.
- the architectural elements also include the operation.
- An operation belongs to exactly one process component.
- a process component generally has multiple operations. Operations can be synchronous or asynchronous, corresponding to synchronous or asynchronous process agents, which will be described below.
- An operation is the smallest, separately-callable function, described by a set of data types used as input, output, and fault parameters, or some combination of them, serving as a signature.
- a repository of service descriptions that includes a standards-based description of each of the supported service operations.
- the architectural elements also include the service interface, which may be referred to simply as an interface.
- An interface is a named group of operations. Each operation belongs to exactly one interface.
- An interface belongs to exactly one process component.
- a process component might contain multiple interfaces.
- 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 preferably belong to the same interface. Thus, generally, all outbound operations to the same other process component are in one interface.
- the architectural elements also include the message.
- Operations transmit and receive messages. Any convenient messaging infrastructure can be used.
- a message is information conveyed from one process component instance to another, with the expectation that activity will ensue.
- An operation can use multiple message types for inbound, outbound, or error messages.
- invocation of an operation of one process component by the other process component is accomplished by an operation on the other process component sending a message to the first process component.
- the architectural elements also include the process agent.
- Process agents do business processing that involves the sending or receiving of messages. Each operation will generally have at least one associated process agent.
- a process agent can be associated with one or more operations.
- Process agents can be either inbound or outbound, and either synchronous or asynchronous.
- Asynchronous outbound process agents are called after a business object changes, e.g., after a create, update, or delete of a business object instance.
- Synchronous outbound process agents are generally triggered directly by a business object.
- An output process agent will generally perform some processing of the data of the business object instance whose change triggered the event.
- An outbound agent triggers subsequent business process steps by sending messages using well-defined outbound services to another process component, which generally will be in another deployment unit, or to an external system.
- An outbound process agent is linked to the one business object that triggers the agent, but it is sent not to another business object but rather to another process component. Thus, the outbound process agent can be implemented without knowledge of the exact business object design of the recipient process component.
- Inbound process agents are called after a message has been received. Inbound process agents are used for the inbound part of a message-based communication. An inbound process agent starts the execution of the business process step requested in a message by creating or updating one or multiple business object instances. An inbound process agent is not the agent of a business object but of its process component. An inbound process agent can act on multiple business objects in a process component.
- Synchronous agents are used when a process component requires a more or less immediate response from another process component, and is waiting for that response to continue its work.
- Operations and process components are described in this specification in terms of process agents. However, in alternative implementations, process components and operations can be implemented without use of agents using other conventional techniques to perform the functions described in this specification.
- the architectural elements also include the deployment unit.
- a deployment unit includes one or more process components and, optionally, one or more business objects, that are deployed together on a single computer system platform.
- separate deployment units can be deployed on separate physical computing systems.
- a deployment unit boundary defines the limits of an application-defined transaction, i.e., a set of actions that have the ACID properties of atomicity, consistency, isolation, and durability.
- the architecture requires that all operations of such a transaction be performed on one physical database; as a consequence, the processes of such a transaction must be performed by the process components of one instance of one deployment unit.
- the process components of one deployment unit interact with those of another deployment unit using messages passed through one or more data communication networks or other suitable communication channels.
- a deployment unit deployed on a platform belonging one business can interact with a deployment unit software entity deployed on a separate platform belonging to a different and unrelated business, allowing for business-to- business communication.
- More than one instance of a given deployment unit can execute at the same time, on the same computing system or on separate physical computing systems. This arrangement allows the functionality offered by a deployment unit to be scaled to meet demand by creating as many instances as needed.
- deployment units can be replaced by other another deployment unit as long as the new deployment unit supports the operations depended upon by other deployment units.
- deployment units can depend on the external interfaces of process components in other deployment units, deployment units are not dependent on process component interactions (i.e., interactions between process components involving their respective business objects, operations, interfaces, and messages) within other deployment units.
- process components that interact with other process components or external systems only through messages e.g., as sent and received by operations, can also be replaced as long as the replacement supports the operations of the original.
- the foundation layer does not define a limit for application-defined transactions.
- Deployment units communicate directly with entities in the foundation layer, which communication is typically not message based.
- the foundation layer is active in every system instance on which the application is deployed.
- Business objects in the foundation layer will generally be master data objects.
- the foundation layer will include some business process objects that are used by multiple deployment units. Master data objects and business process objects that should be specific to a deployment unit are preferably assigned to their respective deployment unit.
- FIGS. IA, IB and 1C collectively illustrate a high-level view of a software architectural design and implementation of a suite enterprise software services having customer relationship management functionality.
- a Customer Invoicing deployment unit 102 includes a Customer Invoicing process component 104, a Customer Invoice Request business object 106 and a Customer Invoice business object 108.
- a Customer Relationship Management deployment unit 110 includes an Opportunity Processing process component 114, a Customer Quote Processing process component 116, a Sales Order Processing process component 120 a Customer Return Processing process component 124, a Service Order Processing process component 126, a Direct Mail Processing process component 127, a Service Request Processing process component 128, and a Service Confirmation Processing process component 130.
- Customer Invoice deployment unit 110 also includes a Direct Mail Template business object 132 and a Customer Problem and Solution master data object 134.
- the Opportunity Processing process component 114 includes an Opportunity business object 138.
- the Customer Quote Processing process component 116 includes a Customer Quote business object 140.
- the Sales Order Processing process component 120 includes a Sales Order business object 144.
- the Customer Return Processing process component 124 includes a Customer Return business object 148.
- the Service Order Processing process component 126 includes a Service Order business object 150.
- the Direct Mail Processing process component 127 includes a Direct Mail Template business object 129 used to automatically generate personalized mail in order to contact customers and prospects and a Direct Mail Run business object 131 that is a specification of a serial letter sent as personalized mail to selected customers and/or prospects by means of multiple communication channels.
- the Service Request Processing process component 128 includes a Support Services business object 152 and a Service Request business object 154.
- the Service Confirmation Processing process component 130 includes a Service Confirmation business object 156.
- an Activity Management process component 160 may also be used.
- the Activity Management process component 160 may be used to record public interactions, that is, activities undertaken on behalf of a particular company.
- the Activity Management process component 160 includes a Phone Call Activity business object 162, an Appointment Activity business object 164, a Letter Activity business object 166, a Fax Activity business object 168, an Email Activity business object 170 and a Task master data object 172.
- the Phone Call Activity business object 162 is the type of activity that records telephone interactions that are undertaken by employees on behalf of their company.
- the Appointment Activity business object 164 includes different types of planned activities that are maintained in an employee's calendar, including external appointments and scheduled meetings with other business parties.
- the Letter Activity business object 166 is the type of activity that records messages written on paper by employees on behalf of their company.
- the Fax Activity business object 168 is the type of activity that records documents or graphics transmitted over a telecommunications facility by employees on behalf of their company.
- the Email Activity business object 170 is the type of activity that records communication between employees on behalf of their company via the Internet.
- the Task master data object 172 is a piece of daily business work or a notification about a business event.
- the Price Master Data management process component 180 includes a Sales Price Specification business object 182, a Sale Price List business object 183, and a Procurement Price Specification business object 184.
- the Sales Price Specification business object 182 is a specification of a price, a discount, or a surcharge that is used indirectly using pricing in sales and service documents. The specification is defined for a combination of properties and is valid for a specific period.
- the Sales Price List business object is a list of price specifications with respect to common identifying criteria.
- the Procurement Price Specification business object 184 is the specification of a price, discount or surcharge to be used in procurement documents. The specification is defined for a combination of properties and is valid for a specific period of time.
- the Business Document Flow Processing process component 181 includes a Business Document Flow transformed business object 185.
- the Business Document Flow transformed business objects 185 is a view on the flow of business transaction documents.
- the Business Document Flow transformed business object 185 may use a synchronous Request Business Document Flow outbound message agent to invoke a Query Related Business Document operation.
- the Query Related Business Document may update the Business Document Flow Processing process component 181.
- the Business Document Flow transformed business object may receive an update from a Find Related business Document operation.
- FIGS. 2A, 2B, 2C and 2D are block diagrams collectively showing the Customer Invoicing Processing process component 104 (FIG. 1). For convenience in describing this process component, a number of other process components are shown in the figures; these other process components are not part of the process component being described. These other process components are the Sales Order Processing process component 120, the
- a Maintain Customer Invoice Request operation 222 is included in a Request Invoicing hi interface 223.
- the Maintain Customer Invoice Request operation 222 sends an update of a customer invoice request using a Maintain Customer Invoice Request asynchronous outbound process agent 224 to update the Customer Invoice Request business object 106.
- the operation 222 can create, delete or cancel a customer invoice request.
- a Customer Invoice business object 108 can use a Confirm Customer Invoice asynchronous outbound process agent 226 to invoke a Confirm Invoicing operation 228.
- the Confirm Invoicing operation 228 is included in a Request Invoicing Out interface 229.
- the Confirm Invoicing operation 228 may update multiple process components about an invoice confirmation. These include a Sales Order Processing process component 120, a Customer Return Processing process component 124, a Service Order Processing process component 126, a Service Request Processing process component 128, a Service Confirmation Processing process component 130, and a Sales Contract Processing process component 207.
- the Customer Invoice business object 108 may also invoke several operations (depicted by the letter A) that will be discussed in the description for FIG. 2C and FIG. 2D.
- the Customer Invoice business object 108 may use a Notify of Customer Invoice to Accounting asynchronous outbound process agent 230 to invoke a Notify of Invoice operation 232 or a Notify of Invoice Cancellation operation 234.
- the Notify of Invoice operation 232 and the Notify of Invoice Cancellation operation 234 are included in an Invoice Accounting Out interface 236 and may send an update to the Accounting process agent 209.
- the Customer Invoice business object 108 may also use a Notify of Customer Invoice to Due Item Processing asynchronous outbound process agent 238 to invoke the Notify of Invoice operation 232 or the Notify of Invoice Cancellation operation 234.
- the operations 232 and 234 may update the Due Item Processing process component 21 1.
- the Customer Invoice business object 108 may use a Customer Invoice to Credit Management Processing asynchronous outbound process agent 240 to invoke the
- the Notify of Credit Commitment operation 241 is included in a Credit Usage Out interface 243 and may update the Credit Management process component 213.
- the Customer Invoice business object may use a Notify Customer of Customer Invoice asynchronous outbound process agent 242 to invoke a Notify Customer of Invoice operation 244.
- the Notify Customer of Invoice operation 244 is included in an Invoicing Out interface 245 and may update a Supplier Invoice Processing at Customer process component 215.
- the Customer Invoice business object may also use a Notify of Cash Payment from Customer Invoice to Payment Processing asynchronous outbound process agent 246 to invoke a Notify of Cash Payment operation 248, or a Request Cash Payment Cancellation operation 250. Both operations are included in a Cash Payment Out interface 251 and may be used to update the Payment Processing process component 218.
- the Customer Invoice business object can additionally use a Notify of Customer Invoice to Confirmation and Inventory asynchronous outbound process agent 252 to invoke a Notify of Inventory Change operation 254, or a Request Inventory Change and Activity Provision Cancellation operation 256. Both operations (254, 256) are included in an Inventory Change and Activity Confirmation Accounting Out interface 257 and may be used to update the Confirmation and Inventory process agent 220.
- FIG. 3 is a block diagram showing an Opportunity processing process component 114.
- the opportunity processing process component 114 includes an Opportunity business object 138 that may represent a recognized possibility for sales of products or services. An opportunity can result from a trade fair, a sales deal, or a bid invitation.
- the Opportunity business object 138 summarizes a variety of business information, such as the expected sales revenue or expected net value.
- FIGS. 4A and 4B are block diagrams collectively showing a Service Confirmation
- the Customer Invoice Processing process component 104 may invoke a Change Service Confirmation based on Customer Invoice operation 402.
- the Change Service Confirmation based on Customer Invoice operation 402 is included in a Request Invoicing In interface 403.
- the change Service Confirmation based on Customer Invoice operation 402 may send an update to the Service Confirmation business object 156 using a Change Service Confirmation based on Customer Invoice asynchronous inbound process agent 404.
- the Service Confirmation business object 156 may update several process components through various interfaces and operations.
- a Notify of Service Confirmation to Accounting asynchronous outbound process agent 406 may invoke a Notify of Service Confirmation operation 408 to update the Accounting process component 209.
- the Notify of Service Confirmation operation 408 is included in an Order Accounting Out interface 409.
- the Accounting process component 209 may also receive an update using a Notify of Service Provision from Service Confirmation to Accounting asynchronous outbound process agent 410.
- the process agent 410 may invoke a Notify of Service
- Provision operation 412 or a Notify of Service Provision Cancellation operation 414 Both operations (412, 414) are included in a Service Provision Accounting Out interface 415.
- the Service Confirmation business object 156 may use a Request Invoicing from Service Confirmation to Customer Invoice asynchronous outbound process agent 416 to invoke a Request Invoicing operation 418.
- the Request Invoicing operation 418 is included in a Request Invoicing Out interface 419 and may update the Customer Invoice Processing process component 104.
- the Service Confirmation business object 156 may also use a Notify of Inventory Change from Service Confirmation to Confirmation and Inventory asynchronous outbound process agent 420 to invoke a Notify of Inventory Change operation 422.
- the Notify of Inventory Change operation 422 is included in an Inventory Change Out interface 423 and may update the Confirmation and Inventory process component 220.
- the Service Confirmation business object 156 may also use an Expense Item asynchronous outbound process agent 424 to invoke a Financial Expense Notification Out operation 426, which may update an Expense Processing process component 428.
- FIGS. 5A and 5B are block diagrams collectively showing a Service Order Processing process component 126.
- the Service Order Processing process component 126 may handle customer requests to a company for delivery of goods or services at a specific time. The request may be received by a sales area that is then responsible for fulfilling the contract.
- a Customer Requirement Processing process component 502 may invoke a Change Service Order based on Spare Part Availability Update operation 504 or a Change Service Order based on Spare Part Fulfillment Confirmation operation 506. Both operations (504, 506) are included in a Fulfillment In interface 507.
- a Change Service Order based on customer Requirement asynchronous inbound process agent 508 may send an update to the Service Order business object 150.
- the Customer Invoice Processing process component 104 may invoke a Change Service Order based on Customer Invoice operation 510.
- the Change Service Order based on Customer Invoice operation 510 is included in a Request Invoicing In interface 511.
- a Change Service Order based on Customer Invoice asynchronous inbound process agent 512 may send an update to the Service Order business object 150.
- the Service Order business object 150 may use a Synchronous Request Availability Information and Reservation from Service Order to Customer Requirement process agent 514 to invoke a Synchronous Request Spare Part Availability Information and Provisional Reservation operation 516 or to invoke a Register Spare Part Requirement Deletion Notification operation 518. Bother operations (516, 518) are included in a Fulfillment Out interface 519 and may update the Customer Requirement Processing process component 502.
- the Service Order business object 150 may also use a Synchronous Request Credit Limit Check from Service Order to Credit Management process agent 520 to invoke a Request Credit Limit Check operation 522. The operation 522 may update the Credit Management process component 213.
- the Service Order business object 150 may use a Request Requirement Reservation and Fulfillment from Service Order to Customer Requirement asynchronous outbound process agent 528 to invoke a Request Spare Part Requirement Reservation and Fulfillment operation 530.
- the Request Spare Part Requirement Reservation and Fulfillment operation 530 is included in a Fulfillment Out interface 532 and may send an update to the Customer Requirement Processing process component 502.
- the Service Order business object 150 may use a Notify of Service Order to Accounting asynchronous outbound process agent 534 to invoke a Notify of Service Order operation 536.
- the Notify of Service Order operation 536 is included in an Order Accounting Out interface 538 and may update the Accounting process component 209.
- the Service Order business object 150 may use a Request Invoicing from Service Order to Customer Invoice Processing asynchronous outbound process agent 540 to invoke a Request Invoicing operation 542.
- the Request Invoicing operation 542 is part of a Request Invoicing Out interface 544 and may update the Customer Invoice Processing process component 104.
- the Service Order business object 150 may use a Notify of Service Order Credit Commitment from Service Order to Credit Management asynchronous outbound process agent 546 to invoke a Notify of Service Order Credit Commitment operation 548.
- the Notify of Service Order Credit Commitment operation 548 may update the Credit Management process component 213.
- FIGS. 6A and 6B are block diagrams collectively showing a Service Request Processing process component 128.
- the Service Request Processing process component 128 covers requests from a customer to a service provider to answer a question or solve a problem about a product.
- a Service Request Processing in External Request System external process component 602 may invoke a Maintain Service Request operation 604.
- the Maintain Service Request operation 604 is included in an External Providing In interface 606 and may use a Maintain Service Request asynchronous outbound process agent 608 to update the Service Request business object 154.
- a Service Request Processing in External Provider System external process component 610 may invoke a Change Service Request based on Provider's Confirmation operation 612.
- the Change Service Request based on Provider's Confirmation operation 612 is included in an External Requesting In interface 614 and may use a Change Service Request based on External Provider's Request Confirmation asynchronous outbound process agent 616 to update the Service Request business object 154.
- the Customer Invoice Processing process component 104 may invoke a Change
- the Change Service Request based on Customer Invoice operation 618 is included in a Request Invoicing In interface 620 and may use a Change Service Request based on Customer Invoice 622 to update the Service Request business object 154. As shown in FIG. 6B, the Service Request business object 154 may use a Confirm
- the Service Request business object 154 may use a Notify of Service Request to Accounting asynchronous outbound process agent 630 to invoke a Notify of Service Request operation 632.
- the Notify of Service Request operation 632 is included in an Order Accounting Out interface 634 and may update the Accounting process component 209.
- the Service Request business object 154 may use a Notify of Service Provision from Service Request to External Requester asynchronous outbound process agent 624 to invoke a Confirm Service Request operation 626.
- the Confirm Service Request operation 626 is included in an External Providing Out interface 628 and may update the Service Request Processing in External Requester System external process component 602.
- the Service Request business object 154 may use a Notify of Service Request to Accounting asynchronous outbound process agent 630 to invoke a Notify of Service Request operation 632.
- the Notify of Service Request operation 632 is included in an Order Accounting Out interface 634 and may update the Accounting process component 209.
- the Service Request business object 154 may use a Notify of Service Provision from
- Service Request to Accounting asynchronous outbound process agent 636 to invoke a Notify of Service Provision 638 or a Notify of Service Provision Cancellation operation 640.
- the Notify of Service Provision 638 and the Notify of Service Provision Cancellation operation 640 are included in a Service Provision Accounting Out interface 642 and may update the Accounting process component 209.
- the Service Request business object 154 may use a Request Service from Service Request to External Provider asynchronous outbound process agent 644 to invoke a Request Service operation 646.
- the Request Service operation 646 is included in an External Requesting Out interface 648 and may update the Service Request Processing in External Provider System external process component 610.
- the Service Request business object 154 may also use a Request Invoicing from Service Request to Customer Invoice Processing asynchronous outbound process agent 650 to invoke a Request Invoicing operation 652.
- the Request Invoicing operation 652 is included in a Request Invoicing Out interface 654 and may update the Customer Invoice Processing process component 104.
- FIG. 7 is a block diagram showing a Customer Return Processing process component 124.
- the Customer Return Processing process component 124 represents a document initiating the return of a product from a customer back to a seller.
- the Customer Invoice Processing process component 104 may include details about the return and invoke a Change Customer Return based on Customer Invoice operation 702.
- the Change Customer Return based on Customer Invoice operation 702 is included in a Request Invoicing In interface 704 and may use a Customer Return Customer Invoice In asynchronous outbound process agent 706 to update the Customer Return business object 148.
- the Customer Return business object 148 may use a Customer Return to Customer Invoice Out asynchronous outbound process agent 708 to invoke a Request Invoicing operation 710.
- the Request Invoicing operation 710 is included in a Request Invoicing Out interface 712 and may update the Customer Invoice Processing process component 104.
- the Customer Return business object 148 may also use an Incoming Goods asynchronous outbound process agent 714 to invoke a Delivery Execution Request Out operation 716.
- the Delivery Execution Request Out operation 716 is included in a Delivery Execution Request Out interface 718 and may update an Inbound Delivery Processing process component 720.
- the Customer Return business object 148 may also use a Notify of Customer Return to Accounting asynchronous outbound process agent 722 to invoke a Notify of Customer Return operation 724.
- the Notify of Customer Return operation 724 is included in an Order Accounting Out interface 726 and may update the Accounting process component 209.
- the Customer Return business object 148 may also use a Communication Method at Customer asynchronous outbound process agent 728 to invoke a Confirm Customer Return operation 730 to update a Purchase Order Processing at Customer process component 732.
- FIG. 8 is a block diagram showing an Activity Management process component 160.
- the Activity Management process component 160 may be used to record public interactions, that is, activities undertaken on behalf of a particular company.
- the process component 160 contains information about the business partner involved in the activity and the date on which it takes place.
- a specific business activity may be a telephone call, a letter, or a customer visit.
- the Activity Management process may being with receiving information from a Groupware process component 802.
- the Groupware process component 802 is included in the foundation layer and is not part of a specific deployment unit.
- a Task master data object 172 may be used in the operations for the Activity Management process component 160.
- the Task master data object 172 is a piece of daily business work or a notification about a business event. It is created by an application and assigned to a user or a group of users. There are different categories of tasks, such as, business tasks, alerts, or notifications and each task carries a certain set of attributes and functions.
- the Groupware process component 802 may invoke a Maintain Phone Call Activity operation 804, a Maintain Appointment Activity operation 806, a Maintain Letter Activity operation 808, a Maintain Fax Activity operation 810, or a Maintain Email Activity operation 812.
- the Maintain Phone Call Activity operation 804, the Maintain Appointment Activity operation 806, the Maintain Letter Activity operation 808, the Maintain Fax Activity operation 810, and the Maintain Email Activity operation 812 are included in an Activity Transmission Receiving In interface 814 and may use a Maintain Activity from Groupware asynchronous inbound process agent 816 to update several business objects. If the Phone Call Activity business object 162 receives an update, then a Notify of Phone Call Activity to Groupware asynchronous outbound process agent 820 may invoke a Notify of Phone Call Activity operation 822.
- a Notify of Appointment Activity to Groupware asynchronous outbound process agent 826 may invoke a Notify of Appointment Activity operation 828.
- a Notify of Letter Activity to Groupware asynchronous outbound process agent 832 may invoke a Notify of Letter Activity operation 834.
- a Notify of Fax Activity to Groupware asynchronous outbound process agent 838 may invoke a Notify of Fax Activity operation 840.
- the Email Activity business object 170 receives an update, then a Notify of Email Activity to Groupware asynchronous outbound process agent 844 may invoke a Notify of Email Activity operation 846.
- the Notify of Phone Call Activity 822, the Notify of Appointment Activity 828, the Notify of Letter Activity 834, the Notify of Fax Activity 840, and the Notify of Email Activity 846 are included in an Activity Transmission Sending Out interface 850 and may update the Groupware process component 802.
- FIGS. 9A, 9B and 9C are block diagrams collectively showing a Sales Order Processing process component 120.
- the Sales Order Processing process component 120 handles customers' requests to a company for delivery of goods or services.
- a Purchase Order Processing at Customer external process component 902 may invoke a Create Sales Order operation 904, a Change Sales Order operation 906, or a Cancel Sales Order operation 908.
- the Create Sales Order operation 904, the Change Sales Order operation 906, and the Cancel Sales Order operation 908 are included in an Ordering In interface 910.
- the operations 906, 908, and 910 may use a Maintain Sales Order asynchronous outbound process agent 912 may update the Sales Order business object 144.
- a Customer Requirement Processing process component 914 may invoke a Change Sales Order based on Customer Requirement Fulfillment Confirmation operation 916 or a Change Sales Order based on Product Available to Promise Update operation 918.
- the Change Sales Order based on Customer Requirement Fulfillment Confirmation operation 916 and the Change Sales Order based on Product Available to Promise Update operation 918 are included in a Fulfillment In interface 920 and may use a Change Sales Order based on Customer Requirement asynchronous outbound process agent 922 to update the Sales Order business object 144.
- the Customer Invoice Processing process component 104 may invoke a Change Sales Order based on Customer Invoice operation 924.
- Customer Invoice operation 924 is included in a Request Invoicing In interface 926 and may use a Change Sales Order based on Customer Invoice asynchronous outbound process agent 928 to update the Sales Order business object 144.
- the Sales Order business object 144 may use a Synchronous Request Credit Worthiness from Sales Order to Credit Management inbound process agent 930 to invoke a Request Credit Worthiness operation 932.
- the Request Credit Worthiness operation 932 is included in a Credit Usage Out Interface 934 and may update the Credit Management process component 213.
- the Request Credit Worthiness operation 932 may use a Synchronous Request Product Availability Information from Sales Order to Customer Requirement outbound process agent 936 may invoke a Request Product Availability Information and Provision Reservation of Customer Requirement operation 938 or a Register Customer Requirement Deletion Notification operation 940.
- the Request Product Availability Information and Provision Reservation of Customer Requirement operation 938 and the Register Customer Requirement Deletion Notification operation 940 are included in a Fulfillment Out interface 942 and may update a Customer Requirement Processing process component 502.
- the Request Credit Worthiness operation 932 may use a Request Product Valuation from Sales Order to Accounting synchronous outbound process agent 944 to invoke a Request Product Valuation operation 946.
- the Request Product Valuation operation 946 is included in a Product and Resource Valuation Out interface 948 and may update the Accounting process component 209.
- the Sales Order business object 144 may use a Notify of Credit Commitment from Sales Order to Credit Management asynchronous outbound process agent 930 to invoke a Notify of Credit Commitment operation 932.
- Commitment operation 932 is included in a Credit Usage Out interface 934 and may update the Credit Management process component 213.
- the Sales Order business object 144 may also use a Request Invoicing from Sales Order to Customer Invoice Processing asynchronous outbound process agent 936 to invoke a Request Invoicing operation 938.
- the Request Invoicing operation 938 is included in a Request Invoicing Out interface 940 and may update the Customer Invoice Processing process component 104.
- the Sales Order business object 144 may also use a Request Reservation and Fulfillment from Sales Order to Customer Requirement asynchronous outbound process agent 942 to invoke a Request Customer Requirement Reservation and Fulfillment operation 944.
- the Request Customer Requirement Reservation and Fulfillment operation 944 is included in a Fulfillment Out interface 946 and may update the Customer Requirement Processing process component 502.
- the Sales Order business object 144 may also use a Notify of Sales Order to Accounting asynchronous outbound process agent 948 to invoke a Notify of Sales Order operation 950.
- the Notify of Sales Order operation 950 is included in an Order Accounting Out interface 952 and may update the Accounting process component 209.
- the Sales Order business object 144 may also use a Confirm Sales Order to Customer asynchronous outbound process agent 954 to invoke a Confirm Sales Order operation 956.
- the Confirm Sales Order operation 956 is included in an Ordering Out interface 958 and may update the Purchase Order Processing at Customer external process component 902.
- FIG. 10 is a block diagram showing a Customer Quote Processing process component 116.
- the Customer Quote Processing process component 116 may be used to offer a customer delivery of goods or services according to a fixed term.
- the Customer Requirement Processing process component 914 may invoke a Change Customer Quote based on Product Available to Promise Update operation 1002.
- the Change Customer Quote based on Product Available to Promise Update operation 1002 is included in a Fulfillment In interface 1004 and may use a Change Customer Quote based on Product Available to Promise Update asynchronous outbound process agent 1006 to update the Customer Quote business object 140.
- the Customer Quote business object 914 may use a Synchronous Request Credit Worthiness from Customer Quote to Credit Management inbound process agent 1008 to invoke a Request Credit Worthiness operation 1010.
- the Request Credit Worthiness operation 1010 is included in a Credit Usage Out interface 1012 and may send an update to the Credit Management process component 213.
- the Customer Quote business object 914 may also use a Synchronous Request Product Availability Information from Customer Quote to Customer Requirement inbound process agent 1014 to invoke a Request Product Availability Information operation 1016, a Request Product Availability Information and Provisional Reservation of Customer Requirement operation 1018, or a Register Customer Requirement Deletion Notification operation 1020.
- the operations 1016, 1018, and 1020 are included in a Fulfillment Out interface 1022 and may send an update to the Customer Requirement Processing process component 914.
- the Customer Quote business object 914 may also use a Notify Customer of Customer Quote asynchronous inbound process agent 1024 to invoke a Notify of Customer Quote operation 1026 and update a Request for Quote (RFQ) Processing at Customer process component 1028.
- RFQ Request for Quote
- the Customer Quote business object 914 may also use a Request Requirement Reservation from Customer Quote to Customer Requirement asynchronous inbound process agent 1030 to invoke a Request Customer Requirement Reservation operation 1032.
- Request Customer Requirement Reservation operation 1032 is included in a Fulfillment Out interface 1034 and may update the Customer Requirement Processing process component 914.
- the Customer Quote business object 914 may also use a Notify of Credit Commitment from Customer Quote to Credit Management asynchronous inbound process agent 1036 to invoke a Notify of Credit Commitment operation 1038.
- the Notify of Credit Commitment operation 1038 is included in a Credit Usage Out interface 1040 and may update the Credit Management process component 213.
- 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.
- 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.
- 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.
- semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
- magnetic disks e.g. , internal hard disks or removable disks
- magneto-optical disks e.g., CD-ROM and DVD-ROM disks.
- the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
- 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.
- a display device e.g. , a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
- a keyboard and a pointing device e.g. , a mouse or a trackball
- 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.
- LAN local area network
- WAN wide area network
- 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.
Abstract
Methods and apparatus, including systems and computer program products, for a services architecture design that provides enterprise services having customer relationship management functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.
Description
PROVIDING CUSTOMER RELATIONSHIP MANAGEMENT APPLICATION AS
ENTERPRISE SERVICES
BACKGROUND
This specification relates to data processing systems implemented on computers, and more particular to data processing systems providing services in the nature of web 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.
Web services are one technology for making the functionality of software applications available to other software, including other applications. A web service is a standards-based way of encapsulating the functionality of an application that other applications can locate and access. A service-oriented architecture is a distributed software model within which functionality is defined as independent web services. Within a service-oriented architecture, web services can be used in defined sequences according to business logic to form applications that enable business processes.
SUMMARY
This specification describes a services architecture design that provides enterprise services having accounting functionality at the level of an enterprise application. Enterprise services are web services that have an enterprise-level business value.
In its various aspects, the invention can be embodied in systems, methods, and computer program products. For example, a system in one embodiment implements a services architecture design that provides enterprise services having customer relationship management functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.
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
FIGS. IA, IB and 1C collectively illustrate a high-level view of a software architectural design and implementation of a suite enterprise software services having customer relationship management functionality.
FIGS. 2 A, 2B, 2C and 2D are block diagrams collectively showing a customer invoice processing process component.
FIG. 3 is a block diagram showing an opportunity processing process component. FIGS. 4A and 4B are block diagrams collectively showing a service confirmation processing process component.
FIGS. 5A and 5B are block diagrams collectively showing a service order processing process component.
FIGS. 6A and 6B are block diagrams collectively showing a service request processing process component.
FIG. 7 is a block diagram of a customer return processing process component. FIG. 8 is a block diagram of an activity management process component. FIGS. 9A, 9B and 9C are block diagrams collectively showing a sales order processing process component.
FIG. 10 is a block diagram of a customer quote processing process component. Like reference numbers and designations in the various drawings indicate like elements.
DETAILED DESCRIPTION
FIGS. IA, IB and 1C collectively illustrate a high-level view of a software architectural design, and of application software implementations of the design, that provides a suite of enterprise service operations, which can be organized into interfaces, having customer relationship management application functionality. The software corresponding to FIGS. IA and IB in one implementation is for deployment in an application layer of an application server, while the software corresponding to FIG. 1C is for deployment in a foundation layer, which will be described below.
The elements of the architecture include the business object, the process component, the service operation (or simply, the operation), the service interface, the message, and the deployment unit. The elements can also include process agents and reuse service components. These will be generally described below.
In one implementation, the software is implemented to be deployed on an application platform that includes a foundation layer that contains all fundamental entities that can used from multiple deployment units. These entities can be process components, business objects or 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.
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 enterprise application service interfaces. The elements of the architecture are at times described in this specification as being contained or included in other elements; for example, a process component is described as being contained in a deployment unit. It should be understood, however, that such operational inclusion can be realized in a variety of ways and is not limited to a physical inclusion of the entirety of one element in another.
The architectural elements include the business object. A business object is a representation of a type of a uniquely identifiable business entity (an object instance) described by a structural model. Processes operate on business objects.
A business object represents a specific view on some well-defined business content. A business object represents content, and instances of business objects include content, which
a typical business user would expect and understand with little explanation. Whether an object as a type or an instance of an object is intended by the term is generally clear from the context, so the distinction will be made explicitly only when necessary. Properly implemented, business objects are implemented free of redundancies. Business objects are further categorized as business process objects, master data objects, mass data run objects, dependent objects, and transformed objects. A master data object is an object that encapsulates master data (i.e., data that is valid for a period of time). A business process object, which is the kind of business object generally found in a process component, is an object that encapsulates transactional data (i.e., data that is valid for a point in time). A mass data run object is an application object that executes an algorithm for a particular mass data run. An instance of a mass data run object contains a particular set of selections and parameters. A mass data run object implements an algorithm that modifies, manages, and/or processes a large amount of data in multiple transactions, possibly but not necessarily with parallel processing. A dependent object is a business object used as a reuse part in another business object. A dependent object represents a concept that cannot stand by itself from a business point of view. Instances of dependent objects only occur in the context of a non-dependent business object. A transformed object is a transformation of multiple business objects for a well-defined purpose. It transforms the structure of multiple business objects into a common structure. A transformed object does not have its own persistency. The architectural elements also include the process component. A process component is a software package that realizes a business process and generally exposes its functionality as services. The functionality contains business transactions. A process component contains one or more semantically related business objects. Any business object belongs to no more than one process component. Process components are modular and context-independent. That they are context- independent means that a process component is not specific to any specific application and is reusable. The process component is the smallest (most granular) element of reuse in the architecture.
The architectural elements also include the operation. An operation belongs to exactly one process component. A process component generally has multiple operations.
Operations can be synchronous or asynchronous, corresponding to synchronous or asynchronous process agents, which will be described below. An operation is the smallest, separately-callable function, described by a set of data types used as input, output, and fault parameters, or some combination of them, serving as a signature. For convenience in supporting use of the operations supported by a system implementing elements of the design, such a system can optionally include a repository of service descriptions that includes a standards-based description of each of the supported service operations.
The architectural elements also include the service interface, which may be referred to simply as an interface. An interface is a named group of operations. Each operation belongs to exactly one interface. An interface belongs to exactly one process component. A process component might contain multiple interfaces. In one implementation, an interface contains only inbound or outbound operations, but not a mixture of both. One interface can contain both synchronous and asynchronous operations. All operations of the same type (either inbound or outbound) which belong to the same message choreography will preferably belong to the same interface. Thus, generally, all outbound operations to the same other process component are in one interface.
The architectural elements also include the message. Operations transmit and receive messages. Any convenient messaging infrastructure can be used. A message is information conveyed from one process component instance to another, with the expectation that activity will ensue. An operation can use multiple message types for inbound, outbound, or error messages. When two process components are in different deployment units, invocation of an operation of one process component by the other process component is accomplished by an operation on the other process component sending a message to the first process component. The architectural elements also include the process agent. Process agents do business processing that involves the sending or receiving of messages. Each operation will generally have at least one associated process agent. A process agent can be associated with one or more operations. Process agents can be either inbound or outbound, and either synchronous or asynchronous.
Asynchronous outbound process agents are called after a business object changes, e.g., after a create, update, or delete of a business object instance.
Synchronous outbound process agents are generally triggered directly by a business object.
An output process agent will generally perform some processing of the data of the business object instance whose change triggered the event. An outbound agent triggers subsequent business process steps by sending messages using well-defined outbound services to another process component, which generally will be in another deployment unit, or to an external system. An outbound process agent is linked to the one business object that triggers the agent, but it is sent not to another business object but rather to another process component. Thus, the outbound process agent can be implemented without knowledge of the exact business object design of the recipient process component.
Inbound process agents are called after a message has been received. Inbound process agents are used for the inbound part of a message-based communication. An inbound process agent starts the execution of the business process step requested in a message by creating or updating one or multiple business object instances. An inbound process agent is not the agent of a business object but of its process component. An inbound process agent can act on multiple business objects in a process component.
Synchronous agents are used when a process component requires a more or less immediate response from another process component, and is waiting for that response to continue its work. Operations and process components are described in this specification in terms of process agents. However, in alternative implementations, process components and operations can be implemented without use of agents using other conventional techniques to perform the functions described in this specification.
The architectural elements also include the deployment unit. A deployment unit includes one or more process components and, optionally, one or more business objects, that are deployed together on a single computer system platform. Conversely, separate deployment units can be deployed on separate physical computing systems. For this reason, a deployment unit boundary defines the limits of an application-defined transaction, i.e., a set of actions that have the ACID properties of atomicity, consistency, isolation, and durability. To make use of database manager facilities, the architecture requires that all operations of
such a transaction be performed on one physical database; as a consequence, the processes of such a transaction must be performed by the process components of one instance of one deployment unit.
The process components of one deployment unit interact with those of another deployment unit using messages passed through one or more data communication networks or other suitable communication channels. Thus, a deployment unit deployed on a platform belonging one business can interact with a deployment unit software entity deployed on a separate platform belonging to a different and unrelated business, allowing for business-to- business communication. More than one instance of a given deployment unit can execute at the same time, on the same computing system or on separate physical computing systems. This arrangement allows the functionality offered by a deployment unit to be scaled to meet demand by creating as many instances as needed.
Since interaction between deployment units is through service operations, a deployment unit can be replaced by other another deployment unit as long as the new deployment unit supports the operations depended upon by other deployment units. Thus, while deployment units can depend on the external interfaces of process components in other deployment units, deployment units are not dependent on process component interactions (i.e., interactions between process components involving their respective business objects, operations, interfaces, and messages) within other deployment units. Similarly, process components that interact with other process components or external systems only through messages, e.g., as sent and received by operations, can also be replaced as long as the replacement supports the operations of the original.
Interactions between process components that occur only within a deployment unit are not constrained to using service operations. These can be implemented in any convenient fashion.
In contrast to a deployment unit, the foundation layer does not define a limit for application-defined transactions. Deployment units communicate directly with entities in the foundation layer, which communication is typically not message based. The foundation layer is active in every system instance on which the application is deployed. Business objects in the foundation layer will generally be master data objects. In addition, the foundation layer
will include some business process objects that are used by multiple deployment units. Master data objects and business process objects that should be specific to a deployment unit are preferably assigned to their respective deployment unit.
FIGS. IA, IB and 1C collectively illustrate a high-level view of a software architectural design and implementation of a suite enterprise software services having customer relationship management functionality.
As shown in FIG. IA, a Customer Invoicing deployment unit 102 includes a Customer Invoicing process component 104, a Customer Invoice Request business object 106 and a Customer Invoice business object 108. As shown in FIG. IB, a Customer Relationship Management deployment unit 110 includes an Opportunity Processing process component 114, a Customer Quote Processing process component 116, a Sales Order Processing process component 120 a Customer Return Processing process component 124, a Service Order Processing process component 126, a Direct Mail Processing process component 127, a Service Request Processing process component 128, and a Service Confirmation Processing process component 130. The
Customer Invoice deployment unit 110 also includes a Direct Mail Template business object 132 and a Customer Problem and Solution master data object 134.
The Opportunity Processing process component 114 includes an Opportunity business object 138. The Customer Quote Processing process component 116 includes a Customer Quote business object 140. The Sales Order Processing process component 120 includes a Sales Order business object 144. The Customer Return Processing process component 124 includes a Customer Return business object 148. The Service Order Processing process component 126 includes a Service Order business object 150. The Direct Mail Processing process component 127 includes a Direct Mail Template business object 129 used to automatically generate personalized mail in order to contact customers and prospects and a Direct Mail Run business object 131 that is a specification of a serial letter sent as personalized mail to selected customers and/or prospects by means of multiple communication channels. The Service Request Processing process component 128 includes a Support Services business object 152 and a Service Request business object 154. The
Service Confirmation Processing process component 130 includes a Service Confirmation business object 156.
As shown in FIG. 1C, an Activity Management process component 160, a Price Master Data management process component 180, and a Business Document Flow Processing process component 181 in the foundation layer may also be used. The Activity Management process component 160 may be used to record public interactions, that is, activities undertaken on behalf of a particular company. The Activity Management process component 160 includes a Phone Call Activity business object 162, an Appointment Activity business object 164, a Letter Activity business object 166, a Fax Activity business object 168, an Email Activity business object 170 and a Task master data object 172.
The Phone Call Activity business object 162 is the type of activity that records telephone interactions that are undertaken by employees on behalf of their company. The Appointment Activity business object 164 includes different types of planned activities that are maintained in an employee's calendar, including external appointments and scheduled meetings with other business parties. The Letter Activity business object 166 is the type of activity that records messages written on paper by employees on behalf of their company. The Fax Activity business object 168 is the type of activity that records documents or graphics transmitted over a telecommunications facility by employees on behalf of their company. The Email Activity business object 170 is the type of activity that records communication between employees on behalf of their company via the Internet. The Task master data object 172 is a piece of daily business work or a notification about a business event.
The Price Master Data management process component 180 includes a Sales Price Specification business object 182, a Sale Price List business object 183, and a Procurement Price Specification business object 184. The Sales Price Specification business object 182 is a specification of a price, a discount, or a surcharge that is used indirectly using pricing in sales and service documents. The specification is defined for a combination of properties and is valid for a specific period. The Sales Price List business object is a list of price specifications with respect to common identifying criteria. The Procurement Price Specification business object 184 is the specification of a price, discount or surcharge to be
used in procurement documents. The specification is defined for a combination of properties and is valid for a specific period of time.
The Business Document Flow Processing process component 181 includes a Business Document Flow transformed business object 185. The Business Document Flow transformed business objects 185 is a view on the flow of business transaction documents. The Business Document Flow transformed business object 185 may use a synchronous Request Business Document Flow outbound message agent to invoke a Query Related Business Document operation. The Query Related Business Document may update the Business Document Flow Processing process component 181. Additionally, the Business Document Flow transformed business object may receive an update from a Find Related business Document operation. FIGS. 2A, 2B, 2C and 2D are block diagrams collectively showing the Customer Invoicing Processing process component 104 (FIG. 1). For convenience in describing this process component, a number of other process components are shown in the figures; these other process components are not part of the process component being described. These other process components are the Sales Order Processing process component 120, the
Customer Return Processing process component 124, the Service Order Processing process component 126, the Service Request Processing process component 128, the Service Confirmation Processing process component 130, a Supplier Invoice process component 203, an Outbound Delivery Processing process component 205, a Sales Contract Processing process component 207, an Accounting process component 209, a Due Item Processing process component 211, a Credit Management process component 213, a Supplier Invoice Processing at Customer processing component 215, a Payment Processing process component 218, and a Confirmation and Inventory process component 220. These other process components are used to represent software external to the process component in describing its interactions with the external software; however, while the external software can be implemented as such process components, this is not required.
A Maintain Customer Invoice Request operation 222 is included in a Request Invoicing hi interface 223. The Maintain Customer Invoice Request operation 222 sends an update of a customer invoice request using a Maintain Customer Invoice Request asynchronous outbound process agent 224 to update the Customer Invoice Request business
object 106. For example, the operation 222 can create, delete or cancel a customer invoice request.
As shown in FIG. 2B, a Customer Invoice business object 108 can use a Confirm Customer Invoice asynchronous outbound process agent 226 to invoke a Confirm Invoicing operation 228. The Confirm Invoicing operation 228 is included in a Request Invoicing Out interface 229. The Confirm Invoicing operation 228 may update multiple process components about an invoice confirmation. These include a Sales Order Processing process component 120, a Customer Return Processing process component 124, a Service Order Processing process component 126, a Service Request Processing process component 128, a Service Confirmation Processing process component 130, and a Sales Contract Processing process component 207.
The Customer Invoice business object 108 may also invoke several operations (depicted by the letter A) that will be discussed in the description for FIG. 2C and FIG. 2D.
As shown in FIG. 2C, the Customer Invoice business object 108 may use a Notify of Customer Invoice to Accounting asynchronous outbound process agent 230 to invoke a Notify of Invoice operation 232 or a Notify of Invoice Cancellation operation 234. The Notify of Invoice operation 232 and the Notify of Invoice Cancellation operation 234 are included in an Invoice Accounting Out interface 236 and may send an update to the Accounting process agent 209. The Customer Invoice business object 108 may also use a Notify of Customer Invoice to Due Item Processing asynchronous outbound process agent 238 to invoke the Notify of Invoice operation 232 or the Notify of Invoice Cancellation operation 234. The operations 232 and 234 may update the Due Item Processing process component 21 1.
In addition, the Customer Invoice business object 108 may use a Customer Invoice to Credit Management Processing asynchronous outbound process agent 240 to invoke the
Notify of Credit Commitment operation 241. The Notify of Credit Commitment operation 241 is included in a Credit Usage Out interface 243 and may update the Credit Management process component 213.
As shown in FIG. 2D, the Customer Invoice business object may use a Notify Customer of Customer Invoice asynchronous outbound process agent 242 to invoke a Notify
Customer of Invoice operation 244. The Notify Customer of Invoice operation 244 is included in an Invoicing Out interface 245 and may update a Supplier Invoice Processing at Customer process component 215. The Customer Invoice business object may also use a Notify of Cash Payment from Customer Invoice to Payment Processing asynchronous outbound process agent 246 to invoke a Notify of Cash Payment operation 248, or a Request Cash Payment Cancellation operation 250. Both operations are included in a Cash Payment Out interface 251 and may be used to update the Payment Processing process component 218. The Customer Invoice business object can additionally use a Notify of Customer Invoice to Confirmation and Inventory asynchronous outbound process agent 252 to invoke a Notify of Inventory Change operation 254, or a Request Inventory Change and Activity Provision Cancellation operation 256. Both operations (254, 256) are included in an Inventory Change and Activity Confirmation Accounting Out interface 257 and may be used to update the Confirmation and Inventory process agent 220.
FIG. 3 is a block diagram showing an Opportunity processing process component 114. The opportunity processing process component 114 includes an Opportunity business object 138 that may represent a recognized possibility for sales of products or services. An opportunity can result from a trade fair, a sales deal, or a bid invitation. The Opportunity business object 138 summarizes a variety of business information, such as the expected sales revenue or expected net value. FIGS. 4A and 4B are block diagrams collectively showing a Service Confirmation
Processing process component 130. As shown in FIG. 4A, the Customer Invoice Processing process component 104 may invoke a Change Service Confirmation based on Customer Invoice operation 402. The Change Service Confirmation based on Customer Invoice operation 402 is included in a Request Invoicing In interface 403. The change Service Confirmation based on Customer Invoice operation 402 may send an update to the Service Confirmation business object 156 using a Change Service Confirmation based on Customer Invoice asynchronous inbound process agent 404.
As shown in FIG. 4B, the Service Confirmation business object 156 may update several process components through various interfaces and operations. A Notify of Service Confirmation to Accounting asynchronous outbound process agent 406 may invoke a Notify
of Service Confirmation operation 408 to update the Accounting process component 209. The Notify of Service Confirmation operation 408 is included in an Order Accounting Out interface 409. The Accounting process component 209 may also receive an update using a Notify of Service Provision from Service Confirmation to Accounting asynchronous outbound process agent 410. The process agent 410 may invoke a Notify of Service
Provision operation 412 or a Notify of Service Provision Cancellation operation 414. Both operations (412, 414) are included in a Service Provision Accounting Out interface 415. The Service Confirmation business object 156 may use a Request Invoicing from Service Confirmation to Customer Invoice asynchronous outbound process agent 416 to invoke a Request Invoicing operation 418. The Request Invoicing operation 418 is included in a Request Invoicing Out interface 419 and may update the Customer Invoice Processing process component 104.
The Service Confirmation business object 156 may also use a Notify of Inventory Change from Service Confirmation to Confirmation and Inventory asynchronous outbound process agent 420 to invoke a Notify of Inventory Change operation 422. The Notify of Inventory Change operation 422 is included in an Inventory Change Out interface 423 and may update the Confirmation and Inventory process component 220.
The Service Confirmation business object 156 may also use an Expense Item asynchronous outbound process agent 424 to invoke a Financial Expense Notification Out operation 426, which may update an Expense Processing process component 428.
FIGS. 5A and 5B are block diagrams collectively showing a Service Order Processing process component 126. The Service Order Processing process component 126 may handle customer requests to a company for delivery of goods or services at a specific time. The request may be received by a sales area that is then responsible for fulfilling the contract. As shown in FIG. 5A, a Customer Requirement Processing process component 502 may invoke a Change Service Order based on Spare Part Availability Update operation 504 or a Change Service Order based on Spare Part Fulfillment Confirmation operation 506. Both operations (504, 506) are included in a Fulfillment In interface 507. A Change Service Order based on customer Requirement asynchronous inbound process agent 508 may send an update to the Service Order business object 150.
The Customer Invoice Processing process component 104 may invoke a Change Service Order based on Customer Invoice operation 510. The Change Service Order based on Customer Invoice operation 510 is included in a Request Invoicing In interface 511. A Change Service Order based on Customer Invoice asynchronous inbound process agent 512 may send an update to the Service Order business object 150.
The Service Order business object 150 may use a Synchronous Request Availability Information and Reservation from Service Order to Customer Requirement process agent 514 to invoke a Synchronous Request Spare Part Availability Information and Provisional Reservation operation 516 or to invoke a Register Spare Part Requirement Deletion Notification operation 518. Bother operations (516, 518) are included in a Fulfillment Out interface 519 and may update the Customer Requirement Processing process component 502. The Service Order business object 150 may also use a Synchronous Request Credit Limit Check from Service Order to Credit Management process agent 520 to invoke a Request Credit Limit Check operation 522. The operation 522 may update the Credit Management process component 213.
As shown in FIG. 5B, the Service Order business object 150 may use a Request Requirement Reservation and Fulfillment from Service Order to Customer Requirement asynchronous outbound process agent 528 to invoke a Request Spare Part Requirement Reservation and Fulfillment operation 530. The Request Spare Part Requirement Reservation and Fulfillment operation 530 is included in a Fulfillment Out interface 532 and may send an update to the Customer Requirement Processing process component 502.
The Service Order business object 150 may use a Notify of Service Order to Accounting asynchronous outbound process agent 534 to invoke a Notify of Service Order operation 536. The Notify of Service Order operation 536 is included in an Order Accounting Out interface 538 and may update the Accounting process component 209.
The Service Order business object 150 may use a Request Invoicing from Service Order to Customer Invoice Processing asynchronous outbound process agent 540 to invoke a Request Invoicing operation 542. The Request Invoicing operation 542 is part of a Request Invoicing Out interface 544 and may update the Customer Invoice Processing process component 104.
The Service Order business object 150 may use a Notify of Service Order Credit Commitment from Service Order to Credit Management asynchronous outbound process agent 546 to invoke a Notify of Service Order Credit Commitment operation 548. The Notify of Service Order Credit Commitment operation 548 may update the Credit Management process component 213.
FIGS. 6A and 6B are block diagrams collectively showing a Service Request Processing process component 128. The Service Request Processing process component 128 covers requests from a customer to a service provider to answer a question or solve a problem about a product. As shown in FIG. 6A, a Service Request Processing in External Request System external process component 602 may invoke a Maintain Service Request operation 604. The Maintain Service Request operation 604 is included in an External Providing In interface 606 and may use a Maintain Service Request asynchronous outbound process agent 608 to update the Service Request business object 154.
A Service Request Processing in External Provider System external process component 610 may invoke a Change Service Request based on Provider's Confirmation operation 612. The Change Service Request based on Provider's Confirmation operation 612 is included in an External Requesting In interface 614 and may use a Change Service Request based on External Provider's Request Confirmation asynchronous outbound process agent 616 to update the Service Request business object 154. The Customer Invoice Processing process component 104 may invoke a Change
Service Request based on Customer Invoice operation 618. The Change Service Request based on Customer Invoice operation 618 is included in a Request Invoicing In interface 620 and may use a Change Service Request based on Customer Invoice 622 to update the Service Request business object 154. As shown in FIG. 6B, the Service Request business object 154 may use a Confirm
Service Request from Service Request to External Requester asynchronous outbound process agent 624 to invoke a Confirm Service Request operation 626. The Confirm Service Request operation 626 is included in an External Providing Out interface 628 and may update the Service Request Processing in External Requester System external process component 602.
The Service Request business object 154 may use a Notify of Service Request to Accounting asynchronous outbound process agent 630 to invoke a Notify of Service Request operation 632. The Notify of Service Request operation 632 is included in an Order Accounting Out interface 634 and may update the Accounting process component 209. The Service Request business object 154 may use a Notify of Service Provision from
Service Request to Accounting asynchronous outbound process agent 636 to invoke a Notify of Service Provision 638 or a Notify of Service Provision Cancellation operation 640. The Notify of Service Provision 638 and the Notify of Service Provision Cancellation operation 640 are included in a Service Provision Accounting Out interface 642 and may update the Accounting process component 209.
The Service Request business object 154 may use a Request Service from Service Request to External Provider asynchronous outbound process agent 644 to invoke a Request Service operation 646. The Request Service operation 646 is included in an External Requesting Out interface 648 and may update the Service Request Processing in External Provider System external process component 610.
The Service Request business object 154 may also use a Request Invoicing from Service Request to Customer Invoice Processing asynchronous outbound process agent 650 to invoke a Request Invoicing operation 652. The Request Invoicing operation 652 is included in a Request Invoicing Out interface 654 and may update the Customer Invoice Processing process component 104.
FIG. 7 is a block diagram showing a Customer Return Processing process component 124. The Customer Return Processing process component 124 represents a document initiating the return of a product from a customer back to a seller. The Customer Invoice Processing process component 104 may include details about the return and invoke a Change Customer Return based on Customer Invoice operation 702. The Change Customer Return based on Customer Invoice operation 702 is included in a Request Invoicing In interface 704 and may use a Customer Return Customer Invoice In asynchronous outbound process agent 706 to update the Customer Return business object 148.
The Customer Return business object 148 may use a Customer Return to Customer Invoice Out asynchronous outbound process agent 708 to invoke a Request Invoicing
operation 710. The Request Invoicing operation 710 is included in a Request Invoicing Out interface 712 and may update the Customer Invoice Processing process component 104.
The Customer Return business object 148 may also use an Incoming Goods asynchronous outbound process agent 714 to invoke a Delivery Execution Request Out operation 716. The Delivery Execution Request Out operation 716 is included in a Delivery Execution Request Out interface 718 and may update an Inbound Delivery Processing process component 720.
The Customer Return business object 148 may also use a Notify of Customer Return to Accounting asynchronous outbound process agent 722 to invoke a Notify of Customer Return operation 724. The Notify of Customer Return operation 724 is included in an Order Accounting Out interface 726 and may update the Accounting process component 209.
The Customer Return business object 148 may also use a Communication Method at Customer asynchronous outbound process agent 728 to invoke a Confirm Customer Return operation 730 to update a Purchase Order Processing at Customer process component 732. FIG. 8 is a block diagram showing an Activity Management process component 160.
The Activity Management process component 160 may be used to record public interactions, that is, activities undertaken on behalf of a particular company. The process component 160 contains information about the business partner involved in the activity and the date on which it takes place. For example, a specific business activity may be a telephone call, a letter, or a customer visit. The Activity Management process may being with receiving information from a Groupware process component 802. The Groupware process component 802 is included in the foundation layer and is not part of a specific deployment unit.
A Task master data object 172 (FIG. 1C) may be used in the operations for the Activity Management process component 160. The Task master data object 172 is a piece of daily business work or a notification about a business event. It is created by an application and assigned to a user or a group of users. There are different categories of tasks, such as, business tasks, alerts, or notifications and each task carries a certain set of attributes and functions.
The Groupware process component 802 may invoke a Maintain Phone Call Activity operation 804, a Maintain Appointment Activity operation 806, a Maintain Letter Activity
operation 808, a Maintain Fax Activity operation 810, or a Maintain Email Activity operation 812. The Maintain Phone Call Activity operation 804, the Maintain Appointment Activity operation 806, the Maintain Letter Activity operation 808, the Maintain Fax Activity operation 810, and the Maintain Email Activity operation 812 are included in an Activity Transmission Receiving In interface 814 and may use a Maintain Activity from Groupware asynchronous inbound process agent 816 to update several business objects. If the Phone Call Activity business object 162 receives an update, then a Notify of Phone Call Activity to Groupware asynchronous outbound process agent 820 may invoke a Notify of Phone Call Activity operation 822. If the Appointment Activity business object 164 receives an update, then a Notify of Appointment Activity to Groupware asynchronous outbound process agent 826 may invoke a Notify of Appointment Activity operation 828. If the Letter Activity business object 166 receives an update, then a Notify of Letter Activity to Groupware asynchronous outbound process agent 832 may invoke a Notify of Letter Activity operation 834. If the Fax Activity business object 168, then a Notify of Fax Activity to Groupware asynchronous outbound process agent 838 may invoke a Notify of Fax Activity operation 840. If the Email Activity business object 170 receives an update, then a Notify of Email Activity to Groupware asynchronous outbound process agent 844 may invoke a Notify of Email Activity operation 846. The Notify of Phone Call Activity 822, the Notify of Appointment Activity 828, the Notify of Letter Activity 834, the Notify of Fax Activity 840, and the Notify of Email Activity 846 are included in an Activity Transmission Sending Out interface 850 and may update the Groupware process component 802.
FIGS. 9A, 9B and 9C are block diagrams collectively showing a Sales Order Processing process component 120. The Sales Order Processing process component 120 handles customers' requests to a company for delivery of goods or services. As shown in FIG. 9A, a Purchase Order Processing at Customer external process component 902 may invoke a Create Sales Order operation 904, a Change Sales Order operation 906, or a Cancel Sales Order operation 908. The Create Sales Order operation 904, the Change Sales Order operation 906, and the Cancel Sales Order operation 908 are included in an Ordering In interface 910. The operations 906, 908, and 910 may use a Maintain Sales Order asynchronous outbound process agent 912 may update the Sales Order business object 144.
A Customer Requirement Processing process component 914 may invoke a Change Sales Order based on Customer Requirement Fulfillment Confirmation operation 916 or a Change Sales Order based on Product Available to Promise Update operation 918. The Change Sales Order based on Customer Requirement Fulfillment Confirmation operation 916 and the Change Sales Order based on Product Available to Promise Update operation 918 are included in a Fulfillment In interface 920 and may use a Change Sales Order based on Customer Requirement asynchronous outbound process agent 922 to update the Sales Order business object 144.
The Customer Invoice Processing process component 104 may invoke a Change Sales Order based on Customer Invoice operation 924. The Change Sales Order based on
Customer Invoice operation 924 is included in a Request Invoicing In interface 926 and may use a Change Sales Order based on Customer Invoice asynchronous outbound process agent 928 to update the Sales Order business object 144.
As shown in FIG. 9B, the Sales Order business object 144 may use a Synchronous Request Credit Worthiness from Sales Order to Credit Management inbound process agent 930 to invoke a Request Credit Worthiness operation 932. The Request Credit Worthiness operation 932 is included in a Credit Usage Out Interface 934 and may update the Credit Management process component 213.
The Request Credit Worthiness operation 932 may use a Synchronous Request Product Availability Information from Sales Order to Customer Requirement outbound process agent 936 may invoke a Request Product Availability Information and Provision Reservation of Customer Requirement operation 938 or a Register Customer Requirement Deletion Notification operation 940. The Request Product Availability Information and Provision Reservation of Customer Requirement operation 938 and the Register Customer Requirement Deletion Notification operation 940 are included in a Fulfillment Out interface 942 and may update a Customer Requirement Processing process component 502.
The Request Credit Worthiness operation 932 may use a Request Product Valuation from Sales Order to Accounting synchronous outbound process agent 944 to invoke a Request Product Valuation operation 946. The Request Product Valuation operation 946 is
included in a Product and Resource Valuation Out interface 948 and may update the Accounting process component 209.
As shown in FIG. 9C, the Sales Order business object 144 may use a Notify of Credit Commitment from Sales Order to Credit Management asynchronous outbound process agent 930 to invoke a Notify of Credit Commitment operation 932. The Notify of Credit
Commitment operation 932 is included in a Credit Usage Out interface 934 and may update the Credit Management process component 213.
The Sales Order business object 144 may also use a Request Invoicing from Sales Order to Customer Invoice Processing asynchronous outbound process agent 936 to invoke a Request Invoicing operation 938. The Request Invoicing operation 938 is included in a Request Invoicing Out interface 940 and may update the Customer Invoice Processing process component 104.
The Sales Order business object 144 may also use a Request Reservation and Fulfillment from Sales Order to Customer Requirement asynchronous outbound process agent 942 to invoke a Request Customer Requirement Reservation and Fulfillment operation 944. The Request Customer Requirement Reservation and Fulfillment operation 944 is included in a Fulfillment Out interface 946 and may update the Customer Requirement Processing process component 502.
The Sales Order business object 144 may also use a Notify of Sales Order to Accounting asynchronous outbound process agent 948 to invoke a Notify of Sales Order operation 950. The Notify of Sales Order operation 950 is included in an Order Accounting Out interface 952 and may update the Accounting process component 209.
The Sales Order business object 144 may also use a Confirm Sales Order to Customer asynchronous outbound process agent 954 to invoke a Confirm Sales Order operation 956. The Confirm Sales Order operation 956 is included in an Ordering Out interface 958 and may update the Purchase Order Processing at Customer external process component 902.
FIG. 10 is a block diagram showing a Customer Quote Processing process component 116. The Customer Quote Processing process component 116 may be used to offer a customer delivery of goods or services according to a fixed term. The Customer Requirement Processing process component 914 may invoke a Change Customer Quote
based on Product Available to Promise Update operation 1002. The Change Customer Quote based on Product Available to Promise Update operation 1002 is included in a Fulfillment In interface 1004 and may use a Change Customer Quote based on Product Available to Promise Update asynchronous outbound process agent 1006 to update the Customer Quote business object 140.
The Customer Quote business object 914 may use a Synchronous Request Credit Worthiness from Customer Quote to Credit Management inbound process agent 1008 to invoke a Request Credit Worthiness operation 1010. The Request Credit Worthiness operation 1010 is included in a Credit Usage Out interface 1012 and may send an update to the Credit Management process component 213.
The Customer Quote business object 914 may also use a Synchronous Request Product Availability Information from Customer Quote to Customer Requirement inbound process agent 1014 to invoke a Request Product Availability Information operation 1016, a Request Product Availability Information and Provisional Reservation of Customer Requirement operation 1018, or a Register Customer Requirement Deletion Notification operation 1020. The operations 1016, 1018, and 1020 are included in a Fulfillment Out interface 1022 and may send an update to the Customer Requirement Processing process component 914.
The Customer Quote business object 914 may also use a Notify Customer of Customer Quote asynchronous inbound process agent 1024 to invoke a Notify of Customer Quote operation 1026 and update a Request for Quote (RFQ) Processing at Customer process component 1028.
The Customer Quote business object 914 may also use a Request Requirement Reservation from Customer Quote to Customer Requirement asynchronous inbound process agent 1030 to invoke a Request Customer Requirement Reservation operation 1032. The
Request Customer Requirement Reservation operation 1032 is included in a Fulfillment Out interface 1034 and may update the Customer Requirement Processing process component 914.
The Customer Quote business object 914 may also use a Notify of Credit Commitment from Customer Quote to Credit Management asynchronous inbound process
agent 1036 to invoke a Notify of Credit Commitment operation 1038. The Notify of Credit Commitment operation 1038 is included in a Credit Usage Out interface 1040 and may update the Credit Management process component 213.
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 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. What is claimed is:
Claims
1. A system comprising: a computer system comprising one or more hardware platforms for executing computer software;
5 computer software deployed on the computer system, the computer software implementing a plurality of service operations, the service operations comprising: a maintain customer invoice request operation operable to create, update, delete or request cancellation of a customer invoice request; a confirm invoicing operation operable to confirm that customer invoice was o created or cancelled to process components which requested invoicing; a notify of invoice operation operable to inform accounting about outgoing invoices or credit memos; a notify of invoice cancellation operation operable to inform accounting about cancellation of invoices or credit memos; 5 a change service confirmation based on customer invoice operation operable to update the service confirmation in order to document the information about issued customer invoices in the service confirmation; a notify of service confirmation operation operable to notify accounting about the creation, change or deletion of a service confirmation; 0 a request invoicing operation operable to send a billing due notification to customer invoice processing; a change service order based on spare part availability update operation operable to update a service order with spare part availability and to update reservation information based on customer requirement fulfillment planning data; 5 a change service order based on spare part fulfillment confirmation operation operable to update a service order with spare part quantity delivered to customer, or picked up by a service technician; a notify of customer return operation operable to notify inbound delivery processing about the creation, change or cancellation of a customer return; 0 a register spare part requirement deletion notification operation operable to register a provisional spare part requirement reservation for deletion and to trigger deletion in case of failure or cancellation of transaction processing; a notify of service order operation operable to notify accounting about the creation, change, or deletion of a service order; a cancel sales order operation operable to notify accounting about the cancellation of a sales order; a change sales order operation operable to change a sales order based on changes in a purchase order from the customer; a create sales order operation operable to create a sales order based on a new purchase order from the customer; a change sales order based on customer requirement fulfillment confirmation operation operable to update a sales order with information from fulfillment confirmation; a change sales order based on product available to promise update operation operable to change a sales order with availability and reservation information based on changes in fulfillment planning; a confirm customer return operation operable to confirm a customer return to a customer; a request product valuation operation operable to request the value of a product; a notify of sales order operation operable to notify accounting about the creation, change, or cancellation of a sales order; a confirm sales order operation operable to confirm a sales order; a maintain service request operation operable to create or update a service request with a message received from external requester system; a change service request based on provider's confirmation operation operable to update a service request based on a confirmation message of a service request creation and update progress received from an external provider system; a request service operation operable to send a service request creation or update to an external provider system; a notify of service provision operation operable to notify accounting of actual service provided and actual time spent on performing the service; a notify of service provision cancellation operation operable to notify accounting that a confirmation of a provided service has been cancelled; a notify of service request operation operable to notify accounting about the creation, change or deletion of a service request; a confirm service request operation operable to send a creation, update or processing confirmation to an external requester system; a change customer return based on customer invoice operation operable to send information about invoiced data and values related to items in a current document; a delivery execution request out operation operable to request a delivery; a change service request based on customer invoice operation operable to update a service request in order to document the information about issued customer invoices in the service request; a request customer requirement reservation operation operable to request a reservation for customer requirement; a request customer requirement reservation and fulfillment operation operable to request reservation and fulfillment for customer requirement; a request product availability information and provisional reservation of customer requirement operation operable to request product availability information including the creation of a provisional reservation for customer requirement; a change customer quote based on product available to promise update operation operable to change a customer quote with availability and reservation information based on changes in fulfillment planning; and a notify of service order credit commitment operation operable to send invoice information necessary to update credit commitment.
2. The system of claim 1, wherein the service operations are grouped into service interfaces, the service interfaces comprising: a request invoicing in interface that includes the maintain customer invoice request, the change service confirmation based on customer invoice, the request invoice, the change service request based on customer invoice, the change customer return based on customer invoice, and the change sales order based on customer invoice operations; a request invoicing out interface that includes the confirm invoicing operation and the request invoicing operation; an invoice accounting out interface that includes the notify of invoice operation and the notify of invoice cancellation operation; a receivables payables out interface that includes the notify of invoice operation and the request invoice cancellation operation; an order accounting out interface that includes the notify of service order, the notify of service confirmation, the notify of sales order, the notify of purchase order, the notify of customer return, and the notify of service request operations; a service provision accounting out interface that includes the notify of service provision operation and the notify of service provision cancellation operation; a fulfillment in interface that includes the change service order based on spare part availability update, the change service order based on spare part fulfillment confirmation, the change sales order based on customer requirement fulfillment confirmation, the change sales order based on product available to promise update, and the change customer quote based on product available to promise update service operations; a fulfillment out interface that includes the register spare part requirement deletion notification, the request spare part requirement reservation and fulfillment, the request product availability information and provisional reservation of customer requirement, and the request customer requirement reservation and fulfillment operations; an external providing in interface that includes the maintain service request operation; an external providing out interface that includes the confirm service request operation; an external requesting in interface that includes the change service request based on provider's confirmation operation; an external requesting out interface that includes the request service operation; a delivery execution request out interface that includes the delivery execution request out operation; an ordering in interface that includes the create sales order, the change sales order and the cancel sales order operations; an ordering out interface that includes the confirm sales order operation; and a product and resource valuation out interface that includes the request product valuation operation.
3. The system of claim 1 or 2, wherein: the computer software implementing the maintain customer invoice request operation, the notify of invoice operation, and the confirm invoicing operation is deployed on a first hardware platform; and the computer software implementing the request credit limit check operation, the notify customer of invoice operation, the notify of credit commitment operation, the notify of invoice cancellation operation, the notify of cash payment operation, the request cash payment cancellation operation, the notify of inventory change operation, the request inventory change and activity provision cancellation operation, the change service confirmation based on customer invoice operation, the notify of service confirmation operation, the request invoicing operation, the change service order based on spare part availability update operation, the change service order based on spare part fulfillment confirmation operation, the notify of customer return operation, the register spare part requirement deletion notification operation, the change service order based on customer invoice operation, the request spare part requirement reservation and fulfillment operation, the notify of service order operation, the cancel sales order operation, the change sales order operation, the create sales order operation, the change sales order based on customer requirement fulfillment confirmation operation, the change sales order based on product available to promise update operation, the confirm customer return operation, the request product valuation operation, the notify of credit commitment operation, the notify of sales order operation, the confirm sales order operation, the maintain service request operation, the change service request based on provider's confirmation operation, the request service operation, the notify of service provision operation, the notify of service provision cancellation operation, the notify of service request operation, the confirm service request operation, the change customer return based on customer invoice operation, the change service request based on customer invoice operation, the request customer requirement reservation operation, the request customer requirement reservation and fulfillment operation, the request product availability information and provisional reservation of customer requirement operation, the request credit worthiness operation, the change customer quote based on product available to promise update operation, the notify of inventory change operation, the notify of service order credit commitment operation, the confirm customer return operation, the financial expense notification operation, the request inbound return delivery operation, and is deployed on a second hardware platform.
4. The system of claim 3, wherein each of the first and the second hardware platforms are distinct and separate from each other.
5. The system of claim 1, wherein: the computer software implementing the maintain customer invoice request operation, the notify of invoice operation, and the confirm invoicing operation is deployable on a first hardware platform; and the computer software implementing the request credit limit check operation, the notify customer of invoice operation, the notify of credit commitment operation, the notify of invoice cancellation operation, the notify of cash payment operation, the request cash payment cancellation operation, the notify of inventory change operation, the request inventory change and activity provision cancellation operation, the change service confirmation based on customer invoice operation, the notify of service confirmation operation, the request invoicing operation, the change service order based on spare part availability update operation, the change service order based on spare part fulfillment confirmation operation, the notify of customer return operation, the register spare part requirement deletion notification operation, the change service order based on customer invoice operation, the request spare part requirement reservation and fulfillment operation, the notify of service order operation, the cancel sales order operation, the change sales order operation, the create sales order operation, the change sales order based on customer requirement fulfillment confirmation operation, the change sales order based on product available to promise update operation, the confirm customer return operation, the request product valuation operation, the notify of credit commitment operation, the notify of sales order operation, the confirm sales order operation, the maintain service request operation, the change service request based on provider's confirmation operation, the request service operation, the notify of service provision operation, the notify of service provision cancellation operation, the notify of service request operation, the confirm service request operation, the change customer return based on customer invoice operation, the change service request based on customer invoice operation, the request customer requirement reservation operation, the request customer requirement reservation and fulfillment operation, the request product availability information and provisional reservation of customer requirement operation, the request credit worthiness operation, the change customer quote based on product available to promise update operation, the notify of inventory change operation, the notify of service order credit commitment operation, the confirm customer return operation, the financial expense notification operation, and the request inbound return delivery operation is deployable on a second hardware platform, the first and the second hardware platforms being distinct and separate from each other.
6. The system of any one of claims 1 to 5, wherein the computer software deployed on the computer system comprises: a plurality of process components, each of the process components being a package of software deployed and executing on the computer system and implementing a respective and distinct business process, the plurality of process components including: a customer invoice processing process component used to charge a customer for the delivery of goods or services; an opportunity processing process component used to process customer relationship opportunities; a service confirmation processing process component used to handle services rendered for a service order; a service order processing process component used to handle short-term agreements between a customer and a service provider; a service request processing process component used to cover requests from a customer to a service provider to answer a question or solve a problem about a product; a customer return processing process component used to initiate the return of a product from the customer back to a provider or seller; a sales order processing process component used to handle customers' requests to a company for delivery of goods or services; and a customer quote processing process component used to offer to a customer for the delivery of goods or services according to fixed terms; and wherein: the customer invoice processing process component implements the maintain customer invoice request, the notify of inventory change, the request inventory change and activity provision cancellation, the notify of invoice, the notify of invoice cancellation, the notify of credit commitment, and the confirm invoicing service operation; the service confirmation processing process component implements the notify of inventory change, the notify of service provision, the notify of service provision cancellation, the change service confirmation based on customer invoice, the notify of service confirmation, and the request invoicing service operations; the service order processing process component implements the notify of service order credit commitment, the request credit limit check, the change service order based on product availability update, the change service order based on product customer requirement fulfillment confirmation, the register product customer requirement deletion notification, the request product availability information and provisional reservation, the request product customer requirement reservation and fulfillment, the notify of service order, the request invoicing, and the change service order based on customer invoice service operations; the service request processing process component implements the change service request based on customer invoice, the request service, the notify of service provision, the notify of service provision cancellation, the notify of service request, the maintain service request, the request invoicing, and the confirm service request service operations; the customer return processing process component implements the confirm customer return, the notify of customer return, the change customer return based on customer invoice, the request invoicing, and the notify of customer return service operations; the sales order processing process component implements the notify of sales order, the register product customer requirement deletion notification, the request product availability information and provisional reservation, the request product customer requirement reservation and fulfillment, the change sales order based on product availability update, the change sales order based on product customer requirement fulfillment confirmation, the confirm sales order, the request product valuation, the cancel sales order, the change sales order, the create sales order, the change sales order based on customer invoice, and the request invoicing service operations; and the customer quote processing process component implements the register product customer requirement deletion notification, the request product availability information and provisional reservation of customer requirement, the request product availability information, the request product customer requirement reservation, the request product valuation, and the change customer quote based on product available to promise update service operations.
7. The system of any one of claims 1 to 6, wherein the computer software deployed on the computer system comprises: a plurality of deployment units, each of the deployment units being a package of software packaged together to be deployed on a single physical hardware platform, the plurality of deployment units including: a customer invoicing deployment unit; and a customer relationship management deployment unit; and wherein: the customer invoicing deployment unit implements the maintain customer invoice request operation, the notify of invoice operation, and the confirm invoicing operation; and the customer relationship management deployment unit implements the request credit limit check operation, the notify customer of invoice operation, the notify of credit commitment operation, the notify of invoice cancellation operation, the notify of cash payment operation, the request cash payment cancellation operation, the notify of inventory change operation, the request inventory change and activity provision cancellation operation, the change service confirmation based on customer invoice operation, the notify of service confirmation operation, the request invoicing operation, the change service order based on spare part availability update operation, the change service order based on spare part fulfillment confirmation operation, the notify of customer return operation, the register spare part requirement deletion notification operation, the change service order based on customer invoice operation, the request spare part requirement reservation and fulfillment operation, the notify of service order operation, the cancel sales order operation, the change sales order operation, the create sales order operation, the change sales order based on customer requirement fulfillment confirmation operation, the change sales order based on product available to promise update operation, the confirm customer return operation, the request product valuation operation, the notify of credit commitment operation, the notify of sales order operation, the confirm sales order operation, the maintain service request operation, the change service request based on provider's confirmation operation, the request service operation, the notify of service provision operation, the notify of service provision cancellation operation, the notify of service request operation, the confirm service request operation, the change customer return based on customer invoice operation, the change service request based on customer invoice operation, the request customer requirement reservation operation, the request customer requirement reservation and fulfillment operation, the request product availability information and provisional reservation of customer requirement operation, the request credit worthiness operation, the change customer quote based on product available to promise update operation, the notify of inventory change operation, the notify of service order credit commitment operation, the confirm customer return operation, the financial expense notification operation, and the request inbound return delivery operation.
8. The system of any one of claims 1 to 7, further comprising: a repository of service descriptions, the repository including a standards-based description of each of the plurality of service operations.
9. A computer program product encoded on a tangible machine-readable information carrier for implementing a plurality of services, the product comprising computer software operable to implement service operations on a computer system, the service operations comprising: a maintain customer invoice request operation operable to create, update, delete or request cancellation of a customer invoice request; a confirm invoicing operation operable to confirm that customer invoice was created or cancelled to process components which requested invoicing; a notify of invoice operation operable to inform accounting about outgoing invoices or credit memos; a notify of invoice cancellation operation operable to inform accounting about cancellation of invoices or credit memos; a change service confirmation based on customer invoice operation operable to update the service confirmation in order to document the information about issued customer invoices in the service confirmation; a notify of service confirmation operation operable to notify accounting about the creation, change or deletion of a service confirmation; a request invoicing operation operable to send a billing due notification to customer invoice processing; a change service order based on spare part availability update operation operable to update a service order with spare part availability and to update reservation information based on customer requirement fulfillment planning data; a change service order based on spare part fulfillment confirmation operation operable to update a service order with spare part quantity delivered to customer, or picked up by a service technician; a notify of customer return operation operable to notify inbound delivery processing about the creation, change or cancellation of a customer return; a register spare part requirement deletion notification operation operable to register a provisional spare part requirement reservation for deletion and to trigger deletion in case of failure or cancellation of transaction processing; a notify of service order operation operable to notify accounting about the creation, change, or deletion of a service order; a cancel sales order operation operable to notify accounting about the cancellation of a sales order; a change sales order operation operable to change a sales order based on changes in a purchase order from the customer; a create sales order operation operable to create a sales order based on a new purchase order from the customer; a change sales order based on customer requirement fulfillment confirmation operation operable to update a sales order with information from fulfillment confirmation; a change sales order based on product available to promise update operation operable to change a sales order with availability and reservation information based on changes in fulfillment planning; a confirm customer return operation operable to confirm a customer return to a customer; a request product valuation operation operable to request the value of a product; a notify of sales order operation operable to notify accounting about the creation, change, or cancellation of a sales order; a confirm sales order operation operable to confirm a sales order; a maintain service request operation operable to create or update a service request with a message received from external requester system; a change service request based on provider's confirmation operation operable to update a service request based on a confirmation message of a service request creation and update progress received from an external provider system; a request service operation operable to send a service request creation or update to an external provider system; a notify of service provision operation operable to notify accounting of actual service provided and actual time spent on performing the service; a notify of service provision cancellation operation operable to notify accounting that a confirmation of a provided service has been cancelled; a notify of service request operation operable to notify accounting about the creation, change or deletion of a service request; a confirm service request operation operable to send a creation, update or processing confirmation to an external requester system; a change customer return based on customer invoice operation operable to send information about invoiced data and values related to items in a current document; a delivery execution request out operation operable to request a delivery; a change service request based on customer invoice operation operable to update a service request in order to document the information about issued customer invoices in the service request; a request customer requirement reservation operation operable to request a reservation for customer requirement; a request customer requirement reservation and fulfillment operation operable to request reservation and fulfillment for customer requirement; a request product availability information and provisional reservation of customer requirement operation operable to request product availability information including the creation of a provisional reservation for customer requirement; a change customer quote based on product available to promise update operation operable to change a customer quote with availability and reservation information based on changes in fulfillment planning; and a notify of service order credit commitment operation operable to send invoice information necessary to update credit commitment.
10. The product of claim 9, wherein the computer software comprises: a plurality of process components, each of the process components being a package of software deployed and executing on the computer system and implementing a respective and distinct business process, the plurality of process components including: a customer invoice processing process component used to charge a customer for the delivery of goods or services; an opportunity processing process component used to process customer relationship opportunities; a service confirmation processing process component used to handle services rendered for a service order; a service order processing process component used to handle short-term agreements between a customer and a service provider; a service request processing process component used to cover requests from a customer to a service provider to answer a question or solve a problem about a product; a customer return processing process component used to initiate the return of a product from the customer back to a provider or seller; a sales order processing process component used to handle customers' requests to a company for delivery of goods or services; and a customer quote processing process component used to offer to a customer for the delivery of goods or services according to fixed terms; and wherein: the customer invoice processing process component implements the maintain customer invoice request, the notify of inventory change, the request inventory change and activity provision cancellation, the notify of invoice, the notify of invoice cancellation, the notify of credit commitment, and the confirm invoicing service operation; the service confirmation processing process component implements the notify of inventory change, the notify of service provision, the notify of service provision cancellation, the change service confirmation based on customer invoice, the notify of service confirmation, and the request invoicing service operations; the service order processing process component implements the notify of service order credit commitment, the request credit limit check, the change service order based on product availability update, the change service order based on product customer requirement fulfillment confirmation, the register product customer requirement deletion notification, the request product availability information and provisional reservation, the request product customer requirement reservation and fulfillment, the notify of service order, the request invoicing, and the change service order based on customer invoice service operations; the service request processing process component implements the change service request based on customer invoice, the request service, the notify of service provision, the notify of service provision cancellation, the notify of service request, the maintain service request, the request invoicing, and the confirm service request service operations; the customer return processing process component implements the confirm customer return, the notify of customer return, the change customer return based on customer invoice, the request invoicing, and the notify of customer return service operations; the sales order processing process component implements the notify of sales order, the register product customer requirement deletion notification, the request product availability information and provisional reservation, the request product customer requirement reservation and fulfillment, the change sales order based on product availability update, the change sales order based on product customer requirement fulfillment confirmation, the confirm sales order, the request product valuation, the cancel sales order, the change sales order, the create sales order, the change sales order based on customer invoice, and the request invoicing service operations; and the customer quote processing process component implements the register product customer requirement deletion notification, the request product availability information and provisional reservation of customer requirement, the request product availability information, the request product customer requirement reservation, the request product valuation, and the change customer quote based on product available to promise update service operations.
11. The product of claim 9 or 10, wherein the computer software comprises: a plurality of deployment units, each of the deployment units being a package of software packaged together to be deployed on a single physical hardware platform, the plurality of deployment units including: a customer invoice deployment unit that includes a customer invoice request and a customer invoice business object, wherein the customer invoice request business object maintains a customer invoice request and the customer invoice business object charges a customer for delivery of goods or services; and a customer relationship management deployment unit that includes a customer problem and solution, a direct mail template, an opportunity, a service confirmation, a service order, a service request, a customer return, a sales order, a customer quote, and a direct mail run business object, wherein the customer problem and solution business object is a collection of information consisting of a problem that is reported by a customer, the direct mail template business object is a template which is used to automatically generate personalized mail in order to contact customers and prospects, the opportunity business object represents a recognized possibility for sales of products or services, the service confirmation business object stores the actual resource consumption of performed service operations including working time and the parts and expenses related to service fulfillment, the service order business object represents customer orders to service providers for the delivery of services, the service request business object reflects the initial inquiry of a customer when contacting a customer service and support center, the customer return business object initiates the return of a product from a customer back to a provider or seller, the direct mail run business object is a specification of a serial letter sent as personalized mail to selected customers and prospects by means of multiple communication channels, the sales order business object is a customer request to the company for delivery of goods or services at a certain time, and the customer quote business object is an offer by a vendor to a customer for the delivery of goods or services according to fixed terms.
12. The product of claim 10, wherein: each of the plurality of process components is assigned to no more than 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; and all 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 operations of the two process components.
13. The product of claim 12, wherein the deployment units comprise: a customer invoice deployment unit that includes the customer invoice processing process component; and a customer relationship management deployment unit that includes the customer quote processing, the sales order processing, the customer return processing, the service request processing, the opportunity processing, the service order processing, the direct mail processing, and the service confirmation processing process components.
14. The product of any one of claims 9 to 13, further comprising: a customer invoicing deployment unit that implements the maintain customer invoice request operation, the notify of invoice operation, and the confirm invoicing operation; and a customer relationship management deployment unit that implements the request credit limit check operation, the notify customer of invoice operation, the notify of credit commitment operation, the notify of invoice cancellation operation, the notify of cash payment operation, the request cash payment cancellation operation, the notify of inventory change operation, the request inventory change and activity provision cancellation operation, the change service confirmation based on customer invoice operation, the notify of service confirmation operation, the request invoicing operation, the change service order based on spare part availability update operation, the change service order based on spare part fulfillment confirmation operation, the notify of customer return operation, the register spare part requirement deletion notification operation, the change service order based on customer invoice operation, the request spare part requirement reservation and fulfillment operation, the notify of service order operation, the cancel sales order operation, the change sales order operation, the create sales order operation, the change sales order based on customer requirement fulfillment confirmation operation, the change sales order based on product available to promise update operation, the confirm customer return operation, the request product valuation operation, the notify of credit commitment operation, the notify of sales order operation, the confirm sales order operation, the maintain service request operation, the change service request based on provider's confirmation operation, the request service operation, the notify of service provision operation, the notify of service provision cancellation operation, the notify of service request operation, the confirm service request operation, the change customer return based on customer invoice operation, the change service request based on customer invoice operation, the request customer requirement reservation operation, the request customer requirement reservation and fulfillment operation, the request product availability information and provisional reservation of customer requirement operation, the request credit worthiness operation, the change customer quote based on product available to promise update operation, the notify of inventory change operation, the notify of service order credit commitment operation, the confirm customer return operation, the financial expense notification operation, and the request inbound return delivery operation.
15. The product of any one of claims 10 to 14, wherein: the customer invoice processing process component includes a customer invoice request and a customer invoice business object wherein the customer invoice request business object maintains a customer invoice request and the customer invoice business object charges a customer for delivery of goods or services; the customer quote processing process component includes a customer quote business object wherein the customer quote business object represents an offer by a vendor to a customer for the delivery of goods or services according to fixed terms; the sales order processing process component includes a sales order business object wherein the sales order business object represents a customer request to the company for delivery of goods or services at a certain time; the customer return processing process component includes a customer return business object wherein the customer return business object initiates the return of a product from a customer back to a provider or seller; the service request processing process component includes a support request and a service request business object, wherein the support request is used to resolve an incident in the operations of an IT solution, and the service request business object reflects the initial inquiry of a customer when contacting a customer service and support center; the opportunity processing process component includes an opportunity business object wherein the opportunity business object represents a recognized possibility for sales of products or services; the direct mail processing process component includes a direct mail template business object and a direct mail run business object, wherein the direct mail template business object is a template which is used to automatically generate personalized mail and the direct mail run business object is a specification of a serial letter sent as personalized mail to selected customers; the service order processing process component includes a service order business object wherein the service order business object represents customer orders to service providers for the delivery of services; and the service confirmation processing process component includes a service confirmation business object wherein the service confirmation business object stores the actual resource consumption of performed service operations including working time and the parts and expenses related to service fulfillment.
16. The product of any one of claims 10 to 15, wherein: each of the process components includes one or more business objects; and none 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.
17. The product of claim 16, wherein the business objects comprise a business process object.
18. The product of claim 16 or 17, wherein: none of the business objects included in any one of the process components is included in any of the other process components.
19. The product of any one of claims 9 to 18, further comprising: a plurality of process agents, each process agent being either an inbound process agent or an outbound process agent, an inbound process agent being operable to receive a message from an inbound operation, an outbound process agent being operable to cause an outbound operation to send a message, each process agent being associated with exactly one process component; wherein: the inbound process agents comprise a first inbound process agent operable to start the execution of step requested in a first inbound message by creating or updating one or more business object instances; and 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.
20. A method providing services from a computer system having customer relationship management functionality, the method comprising: providing services through the sending of message, the message including: a notification about a maintain customer invoice request; a notification to confirm an invoicing operation; a notification of invoice; a notification of an invoice cancellation; a notification to change service confirmation based on a customer invoice; a notification of service confirmation; a notification requesting an invoice; a notification about a change service order based on spare part availability update; a notification to change service order based on spare part fulfillment confirmation operation; a notification to maintain a customer invoice request; a notification to confirm invoicing; a notification about an invoice; a notification about an invoice cancellation; a notification about a change service confirmation based on a customer invoice; a notification of a service confirmation; a notification to request invoicing; a notification to change a service order based on spare part availability; a notification to confirm a change service order based on spare part fulfillment; a notification of a customer return; a notification about a spare part requirement deletion notification; a notification of a service order; a notification to cancel a sales order; a notification to change a sales order; a notification to a create sales order; a notification to change a sales order based on customer requirement fulfillment confirmation; a notification to change a sales order based on product available to promise update; a notification to confirm a customer return; a notification to request product valuation; a notification of a sales order; a notification to confirm a sales order; a notification to maintain a service request; a notification to change a service request based on provider's confirmation; a notification to request a service operation; a notification of a service provision; a notification of a service provision cancellation; a notification of a service request; a notification to confirm a service request; a notification to change a customer return based on customer invoice; a notification about a change service request based on customer invoice.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/396,259 US8396749B2 (en) | 2006-03-30 | 2006-03-30 | Providing customer relationship management application as enterprise services |
US11/396,259 | 2006-03-30 |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2007112954A2 true WO2007112954A2 (en) | 2007-10-11 |
WO2007112954A8 WO2007112954A8 (en) | 2008-01-31 |
Family
ID=38055580
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2007/002840 WO2007112954A2 (en) | 2006-03-30 | 2007-03-29 | Providing customer relationship management application as enterprise services |
Country Status (2)
Country | Link |
---|---|
US (1) | US8396749B2 (en) |
WO (1) | WO2007112954A2 (en) |
Families Citing this family (77)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8655756B2 (en) | 2004-06-04 | 2014-02-18 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8448137B2 (en) | 2005-12-30 | 2013-05-21 | Sap Ag | Software model integration scenarios |
US8327319B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Software model process interaction |
US8396731B2 (en) | 2005-12-30 | 2013-03-12 | Sap Ag | Architectural design for service procurement application software |
US8402426B2 (en) | 2005-12-30 | 2013-03-19 | Sap Ag | Architectural design for make to stock application software |
US8370794B2 (en) | 2005-12-30 | 2013-02-05 | Sap Ag | Software model process component |
US8676617B2 (en) | 2005-12-30 | 2014-03-18 | Sap Ag | Architectural design for self-service procurement application software |
US8407664B2 (en) | 2005-12-30 | 2013-03-26 | Sap Ag | Software model business objects |
US8380553B2 (en) | 2005-12-30 | 2013-02-19 | Sap Ag | Architectural design for plan-driven procurement application software |
US8316344B2 (en) | 2005-12-30 | 2012-11-20 | Sap Ag | Software model deployment units |
US8326703B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Architectural design for product catalog management application software |
US8522194B2 (en) | 2005-12-30 | 2013-08-27 | Sap Ag | Software modeling |
US8321831B2 (en) | 2005-12-30 | 2012-11-27 | Sap Ag | Architectural design for internal projects application software |
US8538864B2 (en) | 2006-03-30 | 2013-09-17 | Sap Ag | Providing payment software application as enterprise services |
US8326702B2 (en) | 2006-03-30 | 2012-12-04 | Sap Ag | Providing supplier relationship management software application as enterprise services |
US8396749B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing customer relationship management application as enterprise services |
US8442850B2 (en) | 2006-03-30 | 2013-05-14 | Sap Ag | Providing accounting software application as enterprise services |
US8438119B2 (en) | 2006-03-30 | 2013-05-07 | Sap Ag | Foundation layer for services based enterprise software architecture |
US8396761B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing product catalog software application as enterprise services |
US8321832B2 (en) | 2006-03-31 | 2012-11-27 | Sap Ag | Composite application modeling |
US8312416B2 (en) | 2006-04-13 | 2012-11-13 | Sap Ag | Software model business process variant types |
EP2076874A4 (en) * | 2006-05-13 | 2011-03-09 | Sap Ag | Consistent set of interfaces derived from a business object model |
US8447657B2 (en) | 2007-12-31 | 2013-05-21 | Sap Ag | Architectural design for service procurement application software |
US8671034B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Providing human capital management software application as enterprise services |
US8401936B2 (en) | 2007-12-31 | 2013-03-19 | Sap Ag | Architectural design for expense reimbursement application software |
US8671033B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Architectural design for personnel events application software |
US8315900B2 (en) | 2007-12-31 | 2012-11-20 | Sap Ag | Architectural design for self-service procurement application software |
US8510143B2 (en) | 2007-12-31 | 2013-08-13 | Sap Ag | Architectural design for ad-hoc goods movement software |
US8417593B2 (en) | 2008-02-28 | 2013-04-09 | Sap Ag | System and computer-readable medium for managing consistent interfaces for business objects across heterogeneous systems |
US8589263B2 (en) * | 2008-03-31 | 2013-11-19 | Sap Ag | Managing consistent interfaces for retail business objects across heterogeneous systems |
US20090249358A1 (en) * | 2008-03-31 | 2009-10-01 | Sap Ag | Managing Consistent Interfaces for Kanban Business Objects Across Heterogeneous Systems |
US20090248429A1 (en) * | 2008-03-31 | 2009-10-01 | Sap Ag | Managing Consistent Interfaces for Sales Price Business Objects Across Heterogeneous Systems |
US20090248463A1 (en) * | 2008-03-31 | 2009-10-01 | Emmanuel Piochon | Managing Consistent Interfaces For Trading Business Objects Across Heterogeneous Systems |
CA2663371A1 (en) * | 2008-04-18 | 2009-10-18 | Eaton Steel Bar | Method for electronic database manipulation |
US8818884B2 (en) | 2008-09-18 | 2014-08-26 | Sap Ag | Architectural design for customer returns handling application software |
US8595077B2 (en) | 2008-09-18 | 2013-11-26 | Sap Ag | Architectural design for service request and order management application software |
US8386325B2 (en) | 2008-09-18 | 2013-02-26 | Sap Ag | Architectural design for plan-driven procurement application software |
US8359218B2 (en) | 2008-09-18 | 2013-01-22 | Sap Ag | Computer readable medium for implementing supply chain control using service-oriented methodology |
US8374896B2 (en) | 2008-09-18 | 2013-02-12 | Sap Ag | Architectural design for opportunity management application software |
US20100070556A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Architectural Design for Data Migration Application Software |
US8401928B2 (en) | 2008-09-18 | 2013-03-19 | Sap Ag | Providing supplier relationship management software application as enterprise services |
US8315926B2 (en) | 2008-09-18 | 2012-11-20 | Sap Ag | Architectural design for tax declaration application software |
US8352338B2 (en) | 2008-09-18 | 2013-01-08 | Sap Ag | Architectural design for time recording application software |
US8380549B2 (en) * | 2008-09-18 | 2013-02-19 | Sap Ag | Architectural design for embedded support application software |
US8321250B2 (en) * | 2008-09-18 | 2012-11-27 | Sap Ag | Architectural design for sell from stock application software |
US8311904B2 (en) * | 2008-12-03 | 2012-11-13 | Sap Ag | Architectural design for intra-company stock transfer application software |
US8401908B2 (en) | 2008-12-03 | 2013-03-19 | Sap Ag | Architectural design for make-to-specification application software |
US8738476B2 (en) | 2008-12-03 | 2014-05-27 | Sap Ag | Architectural design for selling standardized services application software |
US8321308B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for manual invoicing application software |
US8321306B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for selling project-based services application software |
US8671035B2 (en) | 2008-12-11 | 2014-03-11 | Sap Ag | Providing payroll software application as enterprise services |
US20100153297A1 (en) | 2008-12-12 | 2010-06-17 | Sap Ag | Managing Consistent Interfaces for Credit Portfolio Business Objects Across Heterogeneous Systems |
US9135585B2 (en) | 2010-06-15 | 2015-09-15 | Sap Se | Managing consistent interfaces for property library, property list template, quantity conversion virtual object, and supplier property specification business objects across heterogeneous systems |
US10614493B2 (en) * | 2011-07-27 | 2020-04-07 | Softlayer Technologies, Inc. | System and method for customer discount management |
US8725654B2 (en) | 2011-07-28 | 2014-05-13 | Sap Ag | Managing consistent interfaces for employee data replication business objects across heterogeneous systems |
US8775280B2 (en) | 2011-07-28 | 2014-07-08 | Sap Ag | Managing consistent interfaces for financial business objects across heterogeneous systems |
US20130124244A1 (en) * | 2011-11-15 | 2013-05-16 | I3Solutions | System and method for managing a proposal lifecycle |
US8984050B2 (en) | 2012-02-16 | 2015-03-17 | Sap Se | Consistent interface for sales territory message type set 2 |
US8756274B2 (en) | 2012-02-16 | 2014-06-17 | Sap Ag | Consistent interface for sales territory message type set 1 |
US9232368B2 (en) | 2012-02-16 | 2016-01-05 | Sap Se | Consistent interface for user feed administrator, user feed event link and user feed settings |
US8762454B2 (en) | 2012-02-16 | 2014-06-24 | Sap Ag | Consistent interface for flag and tag |
US8762453B2 (en) | 2012-02-16 | 2014-06-24 | Sap Ag | Consistent interface for feed collaboration group and feed event subscription |
US9237425B2 (en) | 2012-02-16 | 2016-01-12 | Sap Se | Consistent interface for feed event, feed event document and feed event type |
US8954602B2 (en) | 2012-05-31 | 2015-02-10 | Sap Se | Facilitating communication between enterprise software applications |
US9348665B2 (en) | 2012-05-31 | 2016-05-24 | Sap Se | Mapping messages between web services |
US8756135B2 (en) | 2012-06-28 | 2014-06-17 | Sap Ag | Consistent interface for product valuation data and product valuation level |
US8949855B2 (en) | 2012-06-28 | 2015-02-03 | Sap Se | Consistent interface for address snapshot and approval process definition |
US9367826B2 (en) | 2012-06-28 | 2016-06-14 | Sap Se | Consistent interface for entitlement product |
US9246869B2 (en) | 2012-06-28 | 2016-01-26 | Sap Se | Consistent interface for opportunity |
US9400998B2 (en) | 2012-06-28 | 2016-07-26 | Sap Se | Consistent interface for message-based communication arrangement, organisational centre replication request, and payment schedule |
WO2014000200A1 (en) | 2012-06-28 | 2014-01-03 | Sap Ag | Consistent interface for document output request |
US9076112B2 (en) | 2012-08-22 | 2015-07-07 | Sap Se | Consistent interface for financial instrument impairment expected cash flow analytical result |
US9043236B2 (en) | 2012-08-22 | 2015-05-26 | Sap Se | Consistent interface for financial instrument impairment attribute values analytical result |
US9547833B2 (en) | 2012-08-22 | 2017-01-17 | Sap Se | Consistent interface for financial instrument impairment calculation |
US9191343B2 (en) | 2013-03-15 | 2015-11-17 | Sap Se | Consistent interface for appointment activity business object |
US9191357B2 (en) | 2013-03-15 | 2015-11-17 | Sap Se | Consistent interface for email activity business object |
US10552423B2 (en) | 2016-07-15 | 2020-02-04 | Sap Se | Semantic tagging of nodes |
Family Cites Families (357)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4947321A (en) | 1988-04-04 | 1990-08-07 | Stanford Technologies, Inc. | MICR rejects analysis and management information system |
US5632022A (en) | 1991-11-13 | 1997-05-20 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Encyclopedia of software components |
US5361198A (en) | 1992-04-03 | 1994-11-01 | Combustion Engineering, Inc. | Compact work station control room |
US5566097A (en) | 1993-03-05 | 1996-10-15 | International Business Machines Corporation | System for optimal electronic debugging and verification employing scheduled cutover of alternative logic simulations |
WO1995008148A1 (en) | 1993-09-13 | 1995-03-23 | Taligent, Inc. | Multimedia data routing system |
US5550734A (en) | 1993-12-23 | 1996-08-27 | The Pharmacy Fund, Inc. | Computerized healthcare accounts receivable purchasing collections securitization and management system |
US5560005A (en) | 1994-02-25 | 1996-09-24 | Actamed Corp. | Methods and systems for object-based relational distributed databases |
US5590277A (en) | 1994-06-22 | 1996-12-31 | Lucent Technologies Inc. | Progressive retry method and apparatus for software failure recovery in multi-process message-passing applications |
US5586312A (en) | 1994-10-11 | 1996-12-17 | Unisys Corporation | Method and apparatus for using an independent transaction processing application as a service routine |
US5634127A (en) | 1994-11-30 | 1997-05-27 | International Business Machines Corporation | Methods and apparatus for implementing a message driven processor in a client-server environment |
US5918219A (en) | 1994-12-14 | 1999-06-29 | Isherwood; John Philip | System and method for estimating construction project costs and schedules based on historical data |
JPH08286962A (en) | 1994-12-16 | 1996-11-01 | Internatl Business Mach Corp <Ibm> | Processing system and method for scheduling of object activation |
US5822585A (en) | 1995-02-21 | 1998-10-13 | Compuware Corporation | System and method for cooperative processing using object-oriented framework |
US5680619A (en) | 1995-04-03 | 1997-10-21 | Mfactory, Inc. | Hierarchical encapsulation of instantiated objects in a multimedia authoring system |
US5710917A (en) | 1995-06-07 | 1998-01-20 | International Business Machines Corporation | Method for deriving data mappings and data aliases |
US6272672B1 (en) | 1995-09-06 | 2001-08-07 | Melvin E. Conway | Dataflow processing with events |
US5870588A (en) | 1995-10-23 | 1999-02-09 | Interuniversitair Micro-Elektronica Centrum(Imec Vzw) | Design environment and a design method for hardware/software co-design |
EP0770967A3 (en) | 1995-10-26 | 1998-12-30 | Koninklijke Philips Electronics N.V. | Decision support system for the management of an agile supply chain |
US6067525A (en) | 1995-10-30 | 2000-05-23 | Clear With Computers | Integrated computerized sales force automation system |
US5832218A (en) | 1995-12-14 | 1998-11-03 | International Business Machines Corporation | Client/server electronic mail system for providng off-line client utilization and seamless server resynchronization |
US5768119A (en) | 1996-04-12 | 1998-06-16 | Fisher-Rosemount Systems, Inc. | Process control system including alarm priority adjustment |
DE19712946A1 (en) | 1996-05-30 | 1997-12-04 | Ibm | Computerised method of automatically expanding specifications of process model in workflow process environment |
US5881230A (en) | 1996-06-24 | 1999-03-09 | Microsoft Corporation | Method and system for remote automation of object oriented applications |
US6049838A (en) | 1996-07-01 | 2000-04-11 | Sun Microsystems, Inc. | Persistent distributed capabilities |
US6424991B1 (en) | 1996-07-01 | 2002-07-23 | Sun Microsystems, Inc. | Object-oriented system, method and article of manufacture for a client-server communication framework |
US6112024A (en) | 1996-10-02 | 2000-08-29 | Sybase, Inc. | Development system providing methods for managing different versions of objects with a meta model |
US6446092B1 (en) | 1996-11-01 | 2002-09-03 | Peerdirect Company | Independent distributed database system |
US5991536A (en) | 1996-11-12 | 1999-11-23 | International Business Machines Corporation | Object-oriented tool for registering objects for observation and causing notifications to be made in the event changes are made to an object which is being observed |
US5867495A (en) | 1996-11-18 | 1999-02-02 | Mci Communications Corporations | System, method and article of manufacture for communications utilizing calling, plans in a hybrid network |
US6445782B1 (en) | 1996-11-19 | 2002-09-03 | British Telecommunications Public Limited Company | Service management system for use in communications |
US6311170B1 (en) | 1996-12-04 | 2001-10-30 | Mark C. Embrey | Method and apparatus for making payments and delivering payment information |
US6609100B2 (en) | 1997-03-07 | 2003-08-19 | Lockhead Martin Corporation | Program planning management system |
US6604124B1 (en) | 1997-03-13 | 2003-08-05 | A:\Scribes Corporation | Systems and methods for automatically managing work flow based on tracking job step completion status |
US5987247A (en) | 1997-05-09 | 1999-11-16 | International Business Machines Corporation | Systems, methods and computer program products for building frameworks in an object oriented environment |
USH1830H (en) | 1997-06-17 | 2000-01-04 | The Dow Chemical Company | System for use-tax determination |
US5893106A (en) | 1997-07-11 | 1999-04-06 | International Business Machines Corporation | Object oriented server process framework with interdependent-object creation |
DE19732011A1 (en) | 1997-07-25 | 1999-01-28 | Abb Patent Gmbh | Process for the location-transparent exchange of process data |
US5898872A (en) | 1997-09-19 | 1999-04-27 | Tominy, Inc. | Software reconfiguration engine |
US6038393A (en) | 1997-09-22 | 2000-03-14 | Unisys Corp. | Software development tool to accept object modeling data from a wide variety of other vendors and filter the format into a format that is able to be stored in OMG compliant UML representation |
US6128602A (en) | 1997-10-27 | 2000-10-03 | Bank Of America Corporation | Open-architecture system for real-time consolidation of information from multiple financial systems |
US6237136B1 (en) | 1997-12-02 | 2001-05-22 | National Instruments Corporation | System and method for automatically creating source code example files for an application program in a plurality of programming languages |
US6182133B1 (en) | 1998-02-06 | 2001-01-30 | Microsoft Corporation | Method and apparatus for display of information prefetching and cache status having variable visual indication based on a period of time since prefetching |
US6208345B1 (en) | 1998-04-15 | 2001-03-27 | Adc Telecommunications, Inc. | Visual data integration system and method |
US6067559A (en) | 1998-04-23 | 2000-05-23 | Microsoft Corporation | Server architecture for segregation of dynamic content generation applications into separate process spaces |
JP3925584B2 (en) | 1998-06-09 | 2007-06-06 | ソニー株式会社 | Replication generation management method and recording / reproducing system |
US6338097B1 (en) | 1998-06-19 | 2002-01-08 | Sap Aktiengesellschaft | Cross application time sheet for communicating with one or more enterprise management applications during time data entry |
US7216091B1 (en) | 1998-06-26 | 2007-05-08 | American Express Travel Related Services Company, Inc. | Stored value transaction system including an integrated database server |
US6434740B1 (en) | 1998-07-15 | 2002-08-13 | International Business Machines Corporation | Apparatus and method for visual construction simplification |
US6177932B1 (en) | 1998-08-21 | 2001-01-23 | Kana Communications, Inc. | Method and apparatus for network based customer service |
CA2341871A1 (en) | 1998-08-27 | 2000-03-09 | Upshot Corporation | A method and apparatus for network-based sales force management |
US6167564A (en) | 1998-09-17 | 2000-12-26 | Unisys Corp. | Software system development framework |
US6167563A (en) | 1998-09-17 | 2000-12-26 | Unisys Corporation | Method and system for building components in a framework useful in developing integrated business-centric applications |
US7283973B1 (en) | 1998-10-07 | 2007-10-16 | Logic Tree Corporation | Multi-modal voice-enabled content access and delivery system |
US7131069B1 (en) | 1998-10-22 | 2006-10-31 | Made2 Manage Systems, Inc. | Navigational interface for ERP system |
US7236950B2 (en) | 1998-10-29 | 2007-06-26 | Universal Card Services Corp. | Method and system of combined billing of multiple accounts on a single statement |
FR2787902B1 (en) | 1998-12-23 | 2004-07-30 | France Telecom | MODEL AND METHOD FOR IMPLEMENTING A RATIONAL DIALOGUE AGENT, SERVER AND MULTI-AGENT SYSTEM FOR IMPLEMENTATION |
US6851115B1 (en) | 1999-01-05 | 2005-02-01 | Sri International | Software-based architecture for communication and cooperation among distributed electronic agents |
US6594535B1 (en) | 1999-01-11 | 2003-07-15 | Demand Flow Institute, Llc | Material and inventory control system for a demand flow process |
US7155409B1 (en) | 1999-03-05 | 2006-12-26 | Trade Finance Service Corporation | Trade financing method, instruments and systems |
US6738964B1 (en) | 1999-03-11 | 2004-05-18 | Texas Instruments Incorporated | Graphical development system and method |
US6789252B1 (en) | 1999-04-15 | 2004-09-07 | Miles D. Burke | Building business objects and business software applications using dynamic object definitions of ingrediential objects |
US6473794B1 (en) | 1999-05-27 | 2002-10-29 | Accenture Llp | System for establishing plan to test components of web based framework by displaying pictorial representation and conveying indicia coded components of existing network framework |
US6533168B1 (en) | 1999-05-27 | 2003-03-18 | Peter N. Ching | Method and apparatus for computer-readable purchase receipts using multi-dimensional bar codes |
US6782536B2 (en) | 1999-06-08 | 2004-08-24 | Unisys Corporation | System and method for discovering host-based application assets for the development of business-centric software components |
US6678882B1 (en) | 1999-06-30 | 2004-01-13 | Qwest Communications International Inc. | Collaborative model for software systems with synchronization submodel with merge feature, automatic conflict resolution and isolation of potential changes for reuse |
US7152228B2 (en) | 1999-07-08 | 2006-12-19 | Science Applications International Corporation | Automatically generated objects within extensible object frameworks and links to enterprise resources |
US6601233B1 (en) | 1999-07-30 | 2003-07-29 | Accenture Llp | Business components framework |
US7100195B1 (en) | 1999-07-30 | 2006-08-29 | Accenture Llp | Managing user information on an e-commerce system |
US7139999B2 (en) | 1999-08-31 | 2006-11-21 | Accenture Llp | Development architecture framework |
US6442748B1 (en) | 1999-08-31 | 2002-08-27 | Accenture Llp | System, method and article of manufacture for a persistent state and persistent object separator in an information services patterns environment |
US6640238B1 (en) | 1999-08-31 | 2003-10-28 | Accenture Llp | Activity component in a presentation services patterns environment |
AU7111800A (en) | 1999-08-31 | 2001-03-26 | Accenture Llp | A system, method and article of manufacture for organizing and managing transaction-related tax information |
US6636242B2 (en) | 1999-08-31 | 2003-10-21 | Accenture Llp | View configurer in a presentation services patterns environment |
US6601234B1 (en) | 1999-08-31 | 2003-07-29 | Accenture Llp | Attribute dictionary in a business logic services environment |
US7797195B2 (en) | 1999-09-17 | 2010-09-14 | Michael Jay Langhammer | Merchant-affiliated direct wholesale marketing and fulfillment system |
US7047219B1 (en) | 1999-10-04 | 2006-05-16 | Trade Finance Systems, Inc. | Trade finance automation system |
US20110191750A1 (en) | 1999-10-05 | 2011-08-04 | Borland Software Corporation | Methods and systems for displaying distributed computing components using symbols |
US7051316B2 (en) | 1999-10-05 | 2006-05-23 | Borland Software Corporation | Distributed computing component system with diagrammatic graphical representation of code with separate delineated display area by type |
US6757837B1 (en) | 1999-10-19 | 2004-06-29 | Tivo, Inc. | Method and apparatus for software failure diagnosis and repair |
US20020133368A1 (en) | 1999-10-28 | 2002-09-19 | David Strutt | Data warehouse model and methodology |
US6606744B1 (en) | 1999-11-22 | 2003-08-12 | Accenture, Llp | Providing collaborative installation management in a network-based supply chain environment |
US6721783B1 (en) | 1999-11-24 | 2004-04-13 | Parish National Bank | E-mailer controller for privately and securely delivering bank notices, advices and monthly statements |
US7103605B1 (en) | 1999-12-10 | 2006-09-05 | A21, Inc. | Timeshared electronic catalog system and method |
CA2362812A1 (en) | 1999-12-10 | 2001-06-14 | Mtw Corp. | A method of component-based system development |
US7798417B2 (en) | 2000-01-03 | 2010-09-21 | Snyder David M | Method for data interchange |
US6764009B2 (en) | 2001-05-30 | 2004-07-20 | Lightwaves Systems, Inc. | Method for tagged bar code data interchange |
US7003720B1 (en) | 2000-01-07 | 2006-02-21 | Abf Freight Sysems. Inc. | Electronic shipment planner |
US6446045B1 (en) | 2000-01-10 | 2002-09-03 | Lucinda Stone | Method for using computers to facilitate and control the creating of a plurality of functions |
US6889197B2 (en) | 2000-01-12 | 2005-05-03 | Isuppli Inc. | Supply chain architecture |
US6493716B1 (en) | 2000-01-19 | 2002-12-10 | International Business Machines Corporation | Group communication system with flexible member model |
EP1269362A4 (en) | 2000-01-21 | 2007-10-17 | Amcor Ltd | System for specifying design of a product or process |
US7376599B1 (en) * | 2000-01-28 | 2008-05-20 | General Electric Company | Virtual warehouse parts distribution system and process |
US6750885B1 (en) | 2000-01-31 | 2004-06-15 | Journyx, Inc. | Time keeping and expense tracking server that interfaces with a user based upon a user's atomic abilities |
US6747679B1 (en) | 2000-01-31 | 2004-06-08 | Journyx, Inc. | Time keeping and expense tracking server that interfaces with a user based upon a user's atomic abilities |
WO2001059569A2 (en) | 2000-02-09 | 2001-08-16 | Apriva, Inc. | Communication systems, components, and methods with programmable wireless devices |
US7437408B2 (en) | 2000-02-14 | 2008-10-14 | Lockheed Martin Corporation | Information aggregation, processing and distribution system |
US7283977B1 (en) | 2000-02-25 | 2007-10-16 | Kathleen Tyson-Quah | System for reducing risk payment-based transactions wherein a risk filter routine returns instructions authorizing payment to a payment queue for later re-evaluation |
JP2001356934A (en) | 2000-03-02 | 2001-12-26 | Texas Instr Inc <Ti> | Constituting method of software system to interact with hardware system and digital system |
US20070239569A1 (en) * | 2000-03-07 | 2007-10-11 | Michael Lucas | Systems and methods for managing assets |
US6687734B1 (en) | 2000-03-21 | 2004-02-03 | America Online, Incorporated | System and method for determining if one web site has the same information as another web site |
US6671673B1 (en) | 2000-03-24 | 2003-12-30 | International Business Machines Corporation | Method for integrated supply chain and financial management |
US7353180B1 (en) | 2000-04-17 | 2008-04-01 | Accenture Llp | Supply chain/workflow services in a contract manufacturing framework |
US20020049622A1 (en) | 2000-04-27 | 2002-04-25 | Lettich Anthony R. | Vertical systems and methods for providing shipping and logistics services, operations and products to an industry |
US7194431B1 (en) | 2000-05-02 | 2007-03-20 | Ge Corporate Financial Services, Inc. | Method and apparatus for managing remittance processing within account receivables |
US6772216B1 (en) | 2000-05-19 | 2004-08-03 | Sun Microsystems, Inc. | Interaction protocol for managing cross company processes among network-distributed applications |
US7225240B1 (en) | 2000-05-20 | 2007-05-29 | Ciena Corporation | Decoupling processes from hardware with logical identifiers |
US7072855B1 (en) * | 2000-07-24 | 2006-07-04 | Omnicell, Inc. | Systems and methods for purchasing, invoicing and distributing items |
US7469233B2 (en) | 2000-07-24 | 2008-12-23 | American Express Travel Related Services Company, Inc. | Method and system for facilitating the anonymous purchase of goods and services from an e-commerce website |
US6898783B1 (en) | 2000-08-03 | 2005-05-24 | International Business Machines Corporation | Object oriented based methodology for modeling business functionality for enabling implementation in a web based environment |
WO2002013002A2 (en) | 2000-08-04 | 2002-02-14 | Intrinsic Graphics, Inc. | Development of graphics hardware and software |
US6990466B1 (en) | 2000-08-08 | 2006-01-24 | International Business Machines Corporation | Method and system for integrating core banking business processes |
US7315830B1 (en) * | 2000-08-11 | 2008-01-01 | Nexus Company, Ltd. | Method, system and computer program product for ordering merchandise in a global computer network environment |
US7206768B1 (en) | 2000-08-14 | 2007-04-17 | Jpmorgan Chase Bank, N.A. | Electronic multiparty accounts receivable and accounts payable system |
US7136857B2 (en) | 2000-09-01 | 2006-11-14 | Op40, Inc. | Server system and method for distributing and scheduling modules to be executed on different tiers of a network |
US6895438B1 (en) | 2000-09-06 | 2005-05-17 | Paul C. Ulrich | Telecommunication-based time-management system and method |
US7155403B2 (en) | 2001-03-22 | 2006-12-26 | International Business Machines Corporation | System and method for leveraging procurement across companies and company groups |
US7047518B2 (en) | 2000-10-04 | 2006-05-16 | Bea Systems, Inc. | System for software application development and modeling |
US7249044B2 (en) | 2000-10-05 | 2007-07-24 | I2 Technologies Us, Inc. | Fulfillment management system for managing ATP data in a distributed supply chain environment |
US6907395B1 (en) | 2000-10-24 | 2005-06-14 | Microsoft Corporation | System and method for designing a logical model of a distributed computer system and deploying physical resources according to the logical model |
AU2002214663A1 (en) | 2000-10-27 | 2002-05-06 | Manugistics, Inc. | System and method for ensuring order fulfillment |
AU2002237718A1 (en) | 2000-10-30 | 2002-05-21 | Tririga, Inc. | Method for associating graphical objects with non-graphical data |
NZ526323A (en) * | 2000-11-15 | 2005-04-29 | Spc Holdings Pty Ltd | Collaborative commerce hub |
US6889375B1 (en) | 2000-11-17 | 2005-05-03 | Cisco Technology, Inc. | Method and system for application development |
US7370315B1 (en) | 2000-11-21 | 2008-05-06 | Microsoft Corporation | Visual programming environment providing synchronization between source code and graphical component objects |
WO2002044891A2 (en) | 2000-11-30 | 2002-06-06 | Videlity A/S | A generic transaction server |
US7020869B2 (en) | 2000-12-01 | 2006-03-28 | Corticon Technologies, Inc. | Business rules user interface for development of adaptable enterprise applications |
KR100695563B1 (en) | 2000-12-22 | 2007-03-15 | 에이덴티티 매트릭스 메디컬 인코포레이티드 | Multi-agent collaborative architecture for problem solving and tutoring |
US7120597B1 (en) | 2000-12-27 | 2006-10-10 | Kermit Knudtzon | Computerized accounting systems and methods |
TW591456B (en) | 2001-01-08 | 2004-06-11 | Wu-Jie Wang | Supply chain computer management system applying the constant value-quantity principle for single-cell/cell-group/boundary of supply chain |
WO2002057889A2 (en) | 2001-01-19 | 2002-07-25 | Globalserve Computer Services, Ltd. | Electronic procurement ('e-procurement') |
US7212976B2 (en) | 2001-01-22 | 2007-05-01 | W.W. Grainger, Inc. | Method for selecting a fulfillment plan for moving an item within an integrated supply chain |
US7313534B2 (en) | 2001-01-22 | 2007-12-25 | W.W. Grainger, Inc. | System and method for predictive maintenance and service parts fulfillment in a supply chain |
US7324966B2 (en) | 2001-01-22 | 2008-01-29 | W.W. Grainger | Method for fulfilling an order in an integrated supply chain management system |
US7058587B1 (en) | 2001-01-29 | 2006-06-06 | Manugistics, Inc. | System and method for allocating the supply of critical material components and manufacturing capacity |
US6845499B2 (en) | 2001-01-31 | 2005-01-18 | I2 Technologies Us, Inc. | System and method for developing software applications using an extended XML-based framework |
US7299202B2 (en) | 2001-02-07 | 2007-11-20 | Exalt Solutions, Inc. | Intelligent multimedia e-catalog |
US7899721B2 (en) | 2001-02-27 | 2011-03-01 | Accenture Global Services Gmbh | E-commerce system, method and computer program product |
US20030069774A1 (en) | 2001-04-13 | 2003-04-10 | Hoffman George Harry | System, method and computer program product for distributor/supplier selection in a supply chain management framework |
US6954736B2 (en) | 2001-03-23 | 2005-10-11 | Restaurant Services, Inc. | System, method and computer program product for order confirmation in a supply chain management framework |
US7120896B2 (en) | 2001-10-31 | 2006-10-10 | Vitria Technology, Inc. | Integrated business process modeling environment and models created thereby |
US20020198798A1 (en) | 2001-04-03 | 2002-12-26 | Bottomline Technologies, Inc. | Modular business transactions platform |
US20020198828A1 (en) | 2001-04-03 | 2002-12-26 | Bottomline Technologies, Inc. | Modular business transactions platform |
US7376600B1 (en) | 2001-04-11 | 2008-05-20 | I2 Technologies Us, Inc. | Intelligent fulfillment agents |
EP1390844A4 (en) | 2001-04-24 | 2006-01-18 | Breed Automotive Tech | Simplified modeling software interface and method |
US20020161907A1 (en) | 2001-04-25 | 2002-10-31 | Avery Moon | Adaptive multi-protocol communications system |
US7213232B1 (en) | 2001-06-07 | 2007-05-01 | 12 Technologies, Inc. | System and method for configuring software using a business modeling tool |
US7761319B2 (en) | 2001-06-08 | 2010-07-20 | Click Acqusitions, Inc. | Supply chain management |
US7117447B2 (en) | 2001-06-08 | 2006-10-03 | Mci, Llc | Graphical user interface (GUI) based call application system |
EP1410228B1 (en) | 2001-06-22 | 2016-03-23 | Wonderware Corporation | Remotely monitoring / diagnosing distributed components of a supervisory process control and manufacturing information application from a central location |
EP1410196B1 (en) | 2001-06-22 | 2019-08-07 | AVEVA Software, LLC | Installing supervisory process control and manufacturing software from a remote location and maintaining configuration data links in a run-time environment |
US7069536B2 (en) | 2001-06-28 | 2006-06-27 | International Business Machines Corporation | Method, system, and program for executing a workflow |
US7322024B2 (en) | 2002-03-18 | 2008-01-22 | Logiclibrary, Inc. | Generating reusable software assets from distributed artifacts |
US7904350B2 (en) | 2001-07-20 | 2011-03-08 | International Business Machines Corporation | Network-based supply chain management method |
US6847854B2 (en) | 2001-08-10 | 2005-01-25 | Rockwell Automation Technologies, Inc. | System and method for dynamic multi-objective optimization of machine selection, integration and utilization |
US6985939B2 (en) | 2001-09-19 | 2006-01-10 | International Business Machines Corporation | Building distributed software services as aggregations of other services |
US7415697B1 (en) | 2001-10-04 | 2008-08-19 | Perot Systems Corporation | Method and system for providing visualization of underlying architecture of a software system |
US7337132B2 (en) | 2001-10-17 | 2008-02-26 | Sun Microsystems, Inc. | Customizable two step mapping of extensible markup language data in an e-procurement system and method |
JP3730900B2 (en) * | 2001-11-02 | 2006-01-05 | 本田技研工業株式会社 | Internal combustion engine |
US7222786B2 (en) | 2001-11-14 | 2007-05-29 | Sap Ag | Inventory early warning agent with correction by error correlation calculation |
US7200569B2 (en) | 2001-11-26 | 2007-04-03 | Hewlett-Packard Development Company, L.P. | Intelligent apparatus, system and method for financial data computation and analysis |
AU2002351195A1 (en) | 2001-11-28 | 2003-06-10 | Isuppli Corporation | Supply chain network |
US7383201B2 (en) | 2001-12-05 | 2008-06-03 | Canon Kabushiki Kaisha | Demand forecast device, method, and program product |
US7376604B1 (en) | 2001-12-27 | 2008-05-20 | Goldman Sachs & Co. | Method for investing yield restricted monies |
US7460654B1 (en) | 2001-12-28 | 2008-12-02 | Vocada, Inc. | Processing of enterprise messages integrating voice messaging and data systems |
US6914374B2 (en) | 2002-01-09 | 2005-07-05 | Hewlett-Packard Development Company, L.P. | Planar electron emitter apparatus with improved emission area and method of manufacture |
US7281235B2 (en) | 2002-01-09 | 2007-10-09 | International Business Machines Corporation | Computer controlled system for modularizing the information technology structure of a business enterprise into a structure of holonic self-contained modules |
WO2003069442A2 (en) | 2002-02-12 | 2003-08-21 | Sandpiper Software, Inc. | Ontology frame-based knowledge representation in the unified modeling language (uml) |
US20030182206A1 (en) | 2002-03-07 | 2003-09-25 | Hendrix Thomas R. | Accounts payable electronic processing |
US20060248504A1 (en) | 2002-04-08 | 2006-11-02 | Hughes John M | Systems and methods for software development |
US20030212602A1 (en) | 2002-05-13 | 2003-11-13 | Kurt Schaller | Order and inventory management system |
US7657445B1 (en) | 2002-05-20 | 2010-02-02 | Rise Above Technologies, LLC | Method and system for managing healthcare facility resources |
US7801976B2 (en) | 2002-05-28 | 2010-09-21 | At&T Intellectual Property I, L.P. | Service-oriented architecture systems and methods |
US7181694B2 (en) | 2002-05-31 | 2007-02-20 | Sap Aktiengesellschaft | Software customization objects for programming extensions associated with a computer system |
US7076766B2 (en) | 2002-06-03 | 2006-07-11 | Steve Wirts | Software application development methods and framework |
US20030233290A1 (en) | 2002-06-14 | 2003-12-18 | Yang Lou Ping | Buyer, multi-supplier, multi-stage supply chain management system with lot tracking |
AUPS322202A0 (en) | 2002-06-27 | 2002-07-18 | Pn & Aj Murray Pty Ltd | An accounting system |
US8121908B2 (en) * | 2002-08-16 | 2012-02-21 | Schlumberger Technology Corporation | Data collection method and report generation apparatus including an automatch function for generating a report illustrating a field order and associated invoice |
US7765521B2 (en) | 2002-08-29 | 2010-07-27 | Jeffrey F Bryant | Configuration engine |
AU2003268373A1 (en) | 2002-09-04 | 2004-03-29 | Mentor Graphics (Holdings) Ltd. | Polymorphic computational system and method |
US20040054564A1 (en) | 2002-09-17 | 2004-03-18 | Fonseca Adolfo M. | Systems and methods for the optimization of resources in energy markets |
EP1403793A1 (en) | 2002-09-27 | 2004-03-31 | Sap Ag | Method for automatic integrated document filing in the logging of business transactions |
CA2406105A1 (en) | 2002-09-30 | 2004-03-30 | Canadian National Railway Company | Method and system for generating account reconciliation data |
US8600804B2 (en) | 2002-11-07 | 2013-12-03 | Novitaz, Inc. | Customer relationship management system for physical locations |
US7725354B2 (en) | 2002-11-18 | 2010-05-25 | Sap Aktiengesellschaft | Interface for generating business partners |
US20040111304A1 (en) | 2002-12-04 | 2004-06-10 | International Business Machines Corporation | System and method for supply chain aggregation and web services |
US7412418B2 (en) | 2002-12-06 | 2008-08-12 | Ocwen Financial Corporation | Expense tracking, electronic ordering, invoice presentment, and payment system and method |
US7640291B2 (en) | 2002-12-16 | 2009-12-29 | Rockwell Automation Technologies, Inc. | Agent-equipped controller having data table interface between agent-type programming and non-agent-type programming |
US7050056B2 (en) | 2002-12-20 | 2006-05-23 | Sap Aktiengesellschaft | Interactive and web-based Gantt Chart |
US7634737B2 (en) | 2002-12-23 | 2009-12-15 | Sap Ag | Defining a resource template for locating relevant resources |
US20040128180A1 (en) | 2002-12-27 | 2004-07-01 | Claus-Dieter Abel | Integrating logistic and financial control of projects |
US20040153359A1 (en) | 2003-01-31 | 2004-08-05 | Mein-Kai Ho | Integrated supply chain management |
AT501256A2 (en) * | 2003-02-06 | 2006-07-15 | Mobilkom Austria Ag & Co Kg | SYSTEM FOR THE MANAGEMENT OF PRODUCTS AND PRODUCT PARTS OR ASSOCIATED SERIAL NUMBERS AND DATA PROCESSING SYSTEM |
JP4387116B2 (en) | 2003-02-28 | 2009-12-16 | 株式会社日立製作所 | Storage system control method and storage system |
US8122106B2 (en) | 2003-03-06 | 2012-02-21 | Microsoft Corporation | Integrating design, deployment, and management phases for systems |
EP1455291A1 (en) | 2003-03-06 | 2004-09-08 | Comptel OYJ | Method, means and computer program product for setting rating |
US20040181470A1 (en) | 2003-03-11 | 2004-09-16 | Electronic Data Systems Corporation | System, method, and computer program product for taxation of online transactions |
US7313561B2 (en) | 2003-03-12 | 2007-12-25 | Microsoft Corporation | Model definition schema |
US8510179B2 (en) | 2003-03-24 | 2013-08-13 | Siebel Systems, Inc. | Inventory transaction common object |
US7028175B2 (en) | 2003-04-09 | 2006-04-11 | Microsoft Corporation | System and method for computer hardware identification |
CN1551026A (en) | 2003-04-18 | 2004-12-01 | 松下电器产业株式会社 | System supporting consolidated accounting |
US20050209732A1 (en) | 2003-04-28 | 2005-09-22 | Srinivasaragavan Audimoolam | Decision support system for supply chain management |
US20070150855A1 (en) | 2003-05-12 | 2007-06-28 | Jeong An M | Method and system of developing a software with utilizing extended metadata of component under component-based development environment |
WO2004102438A2 (en) | 2003-05-16 | 2004-11-25 | Sap Aktiengesellschaft | Business process management for a message-based exchange infrastructure |
US20040236639A1 (en) | 2003-05-20 | 2004-11-25 | Arun Candadai | Dynamic data collaboration |
US20040243489A1 (en) | 2003-05-27 | 2004-12-02 | International Business Machines Corporation | Expense accounting data management based on electronic expense document |
US7546575B1 (en) | 2003-06-09 | 2009-06-09 | Dillman Frederick J | System and method for using blueprints to provide a software solution for an enterprise |
US7406716B2 (en) | 2003-06-10 | 2008-07-29 | Kabushiki Kaisha Toshiba | Software IP providing system and method, software IP obtaining method, and IP core designing and manufacturing method |
US8036962B2 (en) | 2003-06-13 | 2011-10-11 | Sap Ag | Systems and methods for determining payers in a billing environment |
US7742985B1 (en) | 2003-06-26 | 2010-06-22 | Paypal Inc. | Multicurrency exchanges between participants of a network-based transaction facility |
US20050010501A1 (en) | 2003-07-10 | 2005-01-13 | Ward Lycurgus B. | Internet-based back office payroll service and method thereof |
US7257254B2 (en) | 2003-07-24 | 2007-08-14 | Sap Ag | Method and system for recognizing time |
US20050033588A1 (en) | 2003-08-04 | 2005-02-10 | Mario Ruiz | Information system comprised of synchronized software application moduless with individual databases for implementing and changing business requirements to be automated |
US8121913B2 (en) | 2003-08-19 | 2012-02-21 | Swiss Reinsurance Company Ltd. | Architecture for account reconciliation |
US8060553B2 (en) | 2003-08-27 | 2011-11-15 | International Business Machines Corporation | Service oriented architecture for a transformation function in a data integration platform |
US20050240592A1 (en) | 2003-08-27 | 2005-10-27 | Ascential Software Corporation | Real time data integration for supply chain management |
US7814142B2 (en) | 2003-08-27 | 2010-10-12 | International Business Machines Corporation | User interface service for a services oriented architecture in a data integration platform |
US7197740B2 (en) | 2003-09-05 | 2007-03-27 | Sap Aktiengesellschaft | Pattern-based software design |
US7293254B2 (en) | 2003-09-18 | 2007-11-06 | Microsoft Corporation | Extensibility application programming interface and framework for meta-model objects |
US20050222896A1 (en) | 2003-09-19 | 2005-10-06 | Rhyne Joseph C | Systems, methods, and software for leveraging informational assets across multiple business units |
US7711602B2 (en) | 2003-09-23 | 2010-05-04 | Ryder Integrated Logistics | Systems and methods for supply chain management |
US7418409B1 (en) * | 2003-10-24 | 2008-08-26 | Sachin Goel | System for concurrent optimization of business economics and customer value satisfaction |
US20050114829A1 (en) | 2003-10-30 | 2005-05-26 | Microsoft Corporation | Facilitating the process of designing and developing a project |
US20050144226A1 (en) | 2003-11-10 | 2005-06-30 | Churchill Software Services | Systems and methods for modeling and generating reusable application component frameworks, and automated assembly of service-oriented applications from existing applications |
US7756751B2 (en) | 2003-11-17 | 2010-07-13 | International Business Machines Corporation | Architecture for business process integration |
US7093034B2 (en) | 2003-11-18 | 2006-08-15 | Microsoft Corporation | Method and apparatus for input management having a plurality of input provider types wherein staging area holds and allows access by external components |
US7835971B2 (en) | 2003-12-12 | 2010-11-16 | Michael Stockton | Method and system configured for facilitating management of international trade receivables transactions |
US7765156B2 (en) | 2003-12-31 | 2010-07-27 | American Express Travel Related Services Company, Inc. | Method and apparatus for automatically processing invoiced payments with selectable payment terms |
CN1914630A (en) | 2004-01-05 | 2007-02-14 | 迪迪尔·蒂加德 | Behavior based multi-agent systems as data types. |
US20050198121A1 (en) | 2004-01-07 | 2005-09-08 | Daniels Robert W. | Vertical enterprise system |
US8782616B2 (en) | 2004-01-12 | 2014-07-15 | Hewlett-Packard Development Company, L.P. | Templates for configuring digital sending devices to achieve an automated business process |
US20050160104A1 (en) | 2004-01-20 | 2005-07-21 | Datasource, Inc. | System and method for generating and deploying a software application |
US8615487B2 (en) | 2004-01-23 | 2013-12-24 | Garrison Gomez | System and method to store and retrieve identifier associated information content |
US7448022B1 (en) | 2004-02-10 | 2008-11-04 | Prasad Ram | Dynamic software composition in a component-based software system |
US7899725B2 (en) | 2004-03-02 | 2011-03-01 | Accenture Global Services Limited | Enhanced business reporting methodology |
US8046273B2 (en) | 2004-03-08 | 2011-10-25 | Sap Ag | System and method for purchase order creation, procurement, and controlling |
US8050956B2 (en) | 2004-03-08 | 2011-11-01 | Sap Ag | Computer-readable medium, program product, and system for providing a schedule bar with event dates to monitor procurement of a product |
US7793258B2 (en) | 2004-03-15 | 2010-09-07 | Ramco Systems Limited | Software development using visual interfaces |
US20050203760A1 (en) | 2004-03-15 | 2005-09-15 | Microsoft Corporation | Project time and expense |
US7367011B2 (en) | 2004-04-13 | 2008-04-29 | International Business Machines Corporation | Method, system and program product for developing a data model in a data mining system |
US7962386B2 (en) | 2004-04-14 | 2011-06-14 | Sap Ag | Enterprise service architecture platform architecture for multi-application computer system |
US7689477B2 (en) | 2004-04-16 | 2010-03-30 | Sap Aktiengesellschaft | Apparatus and program product for generating an allocation table in a computerized procurement system |
US8655697B2 (en) | 2004-04-16 | 2014-02-18 | Sap Aktiengesellschaft | Allocation table generation from assortment planning |
US8352423B2 (en) | 2004-05-07 | 2013-01-08 | Inceptia Llc | Apparatus and method for providing streaming data |
US20050257197A1 (en) | 2004-05-11 | 2005-11-17 | Klaus Herter | Role-based object models |
US7665064B2 (en) | 2004-05-14 | 2010-02-16 | Gt Software, Inc. | Systems and methods for web service function, definition, implementation, and/or execution |
US9026455B2 (en) | 2004-05-14 | 2015-05-05 | Sap Ag | Methods and systems for processing stock in a storage facility |
US8554805B2 (en) | 2004-05-17 | 2013-10-08 | Sap Ag | Methods and systems for importing source data |
US20050289079A1 (en) | 2004-05-17 | 2005-12-29 | Shimon Systems, Inc. | Systems and methods for biometric identification |
US20050262453A1 (en) | 2004-05-21 | 2005-11-24 | Luca Massasso | Modular data management system |
US8655756B2 (en) | 2004-06-04 | 2014-02-18 | Sap Ag | Consistent set of interfaces derived from a business object model |
US20050289264A1 (en) | 2004-06-08 | 2005-12-29 | Daniel Illowsky | Device and method for interoperability instruction set |
US20080162382A1 (en) | 2004-06-14 | 2008-07-03 | Symphonyrpm,Inc. | Decision object for associating a plurality of business plans |
WO2006038924A2 (en) | 2004-06-18 | 2006-04-13 | Sap Ag | Consistent set of interfaces derived from a business object model |
US7770792B2 (en) * | 2004-06-23 | 2010-08-10 | Sap Ag | Methods and systems for managing stock transportation |
US7669763B2 (en) | 2004-06-23 | 2010-03-02 | Sap Ag | Methods and system for managing stock |
WO2006012123A2 (en) * | 2004-06-25 | 2006-02-02 | Nature Bright Company | Programmable multifunction table lamp for light therapy |
US20050288987A1 (en) | 2004-06-29 | 2005-12-29 | Sap Aktiengesellschaft | Vacation planning and approval |
US20080288379A1 (en) | 2004-06-29 | 2008-11-20 | Allin Patrick J | Construction payment management system and method with automated electronic document generation features |
US7665083B2 (en) | 2004-07-16 | 2010-02-16 | Sap Ag | Method and apparatus for supporting context links for application program text |
US7376601B1 (en) | 2004-08-18 | 2008-05-20 | Teradata Us, Inc. | System and method for determining sell-through time and inventory aging for retail products |
US7664684B2 (en) | 2004-08-27 | 2010-02-16 | Sap Ag | Method and system for catch-weight management |
US7831463B2 (en) | 2004-09-07 | 2010-11-09 | Sap Ag | Computer-implemented method and system for allocating customer demand to suppliers |
US20060085243A1 (en) | 2004-09-24 | 2006-04-20 | Workscape, Inc. | Business process management method and system |
US7574694B2 (en) | 2004-09-28 | 2009-08-11 | Electronic Data Systems Corporation | Method for application and infrastructure rationalization |
US7805324B2 (en) | 2004-10-01 | 2010-09-28 | Microsoft Corporation | Unified model for authoring and executing flow-based and constraint-based workflows |
US20060074704A1 (en) | 2004-10-01 | 2006-04-06 | Microsoft Corporation | Framework to model cross-cutting behavioral concerns in the workflow domain |
US7451432B2 (en) | 2004-10-01 | 2008-11-11 | Microsoft Corporation | Transformation of componentized and extensible workflow to a declarative format |
US7565640B2 (en) | 2004-10-01 | 2009-07-21 | Microsoft Corporation | Framework for seamlessly authoring and editing workflows at design and runtime |
US7631291B2 (en) | 2004-10-01 | 2009-12-08 | Microsoft Corporation | Declarative representation for an extensible workflow model |
US20060089886A1 (en) | 2004-10-27 | 2006-04-27 | Anthony Wong | E-commerce business methodologies for supply and demand chain management |
US8352478B2 (en) | 2004-10-29 | 2013-01-08 | Sap Ag | Master data framework |
WO2006053027A2 (en) | 2004-11-09 | 2006-05-18 | Nexthop Technologies, Inc. | Systems and methods for multicast routing on packet switched networks |
US7797698B2 (en) | 2004-11-17 | 2010-09-14 | International Business Machines Corporation | Method and apparatus for dynamic middleware assembly |
US7739160B1 (en) | 2004-12-22 | 2010-06-15 | Ryan, Inc. | Dynamic, rule-based, tax-decision system |
US7974855B2 (en) | 2004-12-27 | 2011-07-05 | General Electric Company | System and method for identifying, representing and evaluating information and decision flow requirements and processes in a transactional business system |
US8489407B2 (en) | 2005-01-04 | 2013-07-16 | International Business Machines Corporation | Method of evaluating business components in an enterprise |
US8744937B2 (en) | 2005-02-25 | 2014-06-03 | Sap Ag | Consistent set of interfaces derived from a business object model |
US7681176B2 (en) | 2005-03-04 | 2010-03-16 | Microsoft Corporation | Generating a graphical designer application for developing graphical models |
US20060206352A1 (en) | 2005-03-14 | 2006-09-14 | Pulianda Arunkumar G | System for seamless enablement of compound enterprise-processes |
US7890389B2 (en) | 2005-05-17 | 2011-02-15 | Sap Ag | Methods and systems for grouping and managing stock requests |
WO2006133157A2 (en) | 2005-06-07 | 2006-12-14 | Kyube Sal | Computer method and apparatus for developing web pages and applications |
US7822682B2 (en) | 2005-06-08 | 2010-10-26 | Jpmorgan Chase Bank, N.A. | System and method for enhancing supply chain transactions |
WO2006135756A1 (en) | 2005-06-09 | 2006-12-21 | Intepoint, Llc | Multi-infrastructure modeling system |
US7827554B2 (en) | 2005-06-20 | 2010-11-02 | Microsoft Corporation | Multi-thread multimedia processing |
US20080065437A1 (en) | 2005-07-06 | 2008-03-13 | Dybvig Alan J | System and Method for Budgeting, Planning, and Supply Chain Management |
US20070022410A1 (en) | 2005-07-22 | 2007-01-25 | Ban Linda B | Method and system for using a component business model to transform warranty claims processing in the automotive industry |
US7925985B2 (en) | 2005-07-29 | 2011-04-12 | Sap Ag | Methods and apparatus for process thumbnail view |
CA2620993A1 (en) | 2005-09-02 | 2007-03-08 | Ecmarket Inc. | Method and system for exchanging business documents |
US7693586B2 (en) | 2005-09-02 | 2010-04-06 | Sap Ag | Process model transformation for event-based coordination of composite applications |
US7912755B2 (en) | 2005-09-23 | 2011-03-22 | Pronto, Inc. | Method and system for identifying product-related information on a web page |
US8782539B2 (en) | 2005-10-05 | 2014-07-15 | Invensys Systems, Inc. | Generic utility supporting on-demand creation of customizable graphical user interfaces for viewing and specifying field device parameters |
US9152941B2 (en) | 2005-10-11 | 2015-10-06 | Sap Se | Systems and methods for automated parallelization of back-order processing |
US8001019B2 (en) | 2005-10-24 | 2011-08-16 | The Boeing Company | Managing access to and updating warehouse data |
US20070143164A1 (en) | 2005-12-01 | 2007-06-21 | Sanjeev Kaila | Business practice management system |
EP1798675A1 (en) | 2005-12-05 | 2007-06-20 | Sap Ag | Consolidation of third party order processing items |
EP1806686A1 (en) | 2005-12-05 | 2007-07-11 | Sap Ag | Restriction of the number of locations |
EP1798676A1 (en) | 2005-12-05 | 2007-06-20 | Sap Ag | Third party order processing within ATP check |
US20070150332A1 (en) | 2005-12-22 | 2007-06-28 | Caterpillar Inc. | Heuristic supply chain modeling method and system |
US20070156731A1 (en) | 2005-12-23 | 2007-07-05 | Sap Ag | Automatic project management application |
US20070156482A1 (en) | 2005-12-29 | 2007-07-05 | Sap Ag | System and method for generating and providing priority information |
US8396731B2 (en) | 2005-12-30 | 2013-03-12 | Sap Ag | Architectural design for service procurement application software |
US8327319B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Software model process interaction |
US8510183B2 (en) | 2005-12-30 | 2013-08-13 | Sap Ag | System and method for distributed and integrated asset management |
US8326703B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Architectural design for product catalog management application software |
US8688495B2 (en) | 2005-12-30 | 2014-04-01 | Sap Ag | Architectural design for time recording application software |
US8407664B2 (en) | 2005-12-30 | 2013-03-26 | Sap Ag | Software model business objects |
US20070156550A1 (en) | 2005-12-30 | 2007-07-05 | Der Emde Martin V | Architectural design for cash and liquidity management application software |
US20070156500A1 (en) | 2005-12-30 | 2007-07-05 | Wilfried Merkel | Architectural design for sell from stock application software |
US20080275713A9 (en) * | 2005-12-30 | 2008-11-06 | Shai Alfandary | Architectural design for physical inventory application software |
US8380553B2 (en) | 2005-12-30 | 2013-02-19 | Sap Ag | Architectural design for plan-driven procurement application software |
US8660904B2 (en) | 2005-12-30 | 2014-02-25 | Sap Ag | Architectural design for service request and order management application software |
US8676617B2 (en) | 2005-12-30 | 2014-03-18 | Sap Ag | Architectural design for self-service procurement application software |
US20070174145A1 (en) | 2005-12-30 | 2007-07-26 | Stephan Hetzer | Controlling logistics execution in a computer application |
US8316344B2 (en) | 2005-12-30 | 2012-11-20 | Sap Ag | Software model deployment units |
US8370794B2 (en) | 2005-12-30 | 2013-02-05 | Sap Ag | Software model process component |
US20070156428A1 (en) | 2005-12-30 | 2007-07-05 | Brecht-Tillinger Karin K | System and method for internally ordering goods and services |
US20070164849A1 (en) | 2005-12-30 | 2007-07-19 | Tilmann Haeberle | Enterprise software with contextual support |
US8522194B2 (en) | 2005-12-30 | 2013-08-27 | Sap Ag | Software modeling |
US8448137B2 (en) | 2005-12-30 | 2013-05-21 | Sap Ag | Software model integration scenarios |
US20070198391A1 (en) | 2006-02-21 | 2007-08-23 | Deutsche Boerse Ag | Method and system for conducting a block auction |
US20070220143A1 (en) | 2006-03-20 | 2007-09-20 | Postini, Inc. | Synchronous message management system |
US8326702B2 (en) | 2006-03-30 | 2012-12-04 | Sap Ag | Providing supplier relationship management software application as enterprise services |
US20070233539A1 (en) | 2006-03-30 | 2007-10-04 | Philipp Suenderhauf | Providing human capital management software application as enterprise services |
US8396761B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing product catalog software application as enterprise services |
US20070233575A1 (en) | 2006-03-30 | 2007-10-04 | Arthur Berger | Architectural design for strategic sourcing application software |
US8538864B2 (en) | 2006-03-30 | 2013-09-17 | Sap Ag | Providing payment software application as enterprise services |
US8442850B2 (en) | 2006-03-30 | 2013-05-14 | Sap Ag | Providing accounting software application as enterprise services |
US8396749B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing customer relationship management application as enterprise services |
US8321832B2 (en) | 2006-03-31 | 2012-11-27 | Sap Ag | Composite application modeling |
US8407072B2 (en) | 2006-04-04 | 2013-03-26 | International Business Machines Corporation | Process for management of complex projects |
CA2542524A1 (en) | 2006-04-07 | 2007-10-07 | Cognos Incorporated | Report management system |
US8312416B2 (en) | 2006-04-13 | 2012-11-13 | Sap Ag | Software model business process variant types |
EP2076874A4 (en) | 2006-05-13 | 2011-03-09 | Sap Ag | Consistent set of interfaces derived from a business object model |
US7917889B2 (en) | 2006-06-19 | 2011-03-29 | International Business Machines Corporation | Data locations template based application-data association and its use for policy based management |
WO2008021433A2 (en) | 2006-08-14 | 2008-02-21 | Payman Khodabandehloo | Design tool and methodology for enterprise software applications |
US20100100464A1 (en) | 2006-10-10 | 2010-04-22 | Estar Inc. | A multi-tasked human resources and payroll accounting system |
US7624371B2 (en) | 2006-10-16 | 2009-11-24 | Invensys Systems, Inc. | Extensible automation development environment |
US8010938B2 (en) | 2006-11-27 | 2011-08-30 | International Business Machines Corporation | Computer method and system for pattern specification using meta-model of a target domain |
US20080300959A1 (en) | 2007-05-30 | 2008-12-04 | Genpact Global Holdings, S.A.R.L., Sicar | Enterprise application procurement system |
US8001519B2 (en) | 2007-06-27 | 2011-08-16 | International Business Machines Corporation | Model driven development including aspect integration tool |
US20090037492A1 (en) | 2007-07-31 | 2009-02-05 | Ahmad Baitalmal | Framework for Synchronizing Applications |
US20090037287A1 (en) | 2007-07-31 | 2009-02-05 | Ahmad Baitalmal | Software Marketplace and Distribution System |
US8014994B2 (en) | 2007-08-31 | 2011-09-06 | Sap Ag | Simulation business object for service oriented architecture |
US8091065B2 (en) | 2007-09-25 | 2012-01-03 | Microsoft Corporation | Threat analysis and modeling during a software development lifecycle of a software application |
US8112738B2 (en) | 2007-09-26 | 2012-02-07 | Sap Ag | Apparatus and method of customizable model import and export to and from XML schema formats |
US8401936B2 (en) | 2007-12-31 | 2013-03-19 | Sap Ag | Architectural design for expense reimbursement application software |
US8671033B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Architectural design for personnel events application software |
US8447657B2 (en) | 2007-12-31 | 2013-05-21 | Sap Ag | Architectural design for service procurement application software |
US20090189743A1 (en) | 2008-01-24 | 2009-07-30 | Alcatel-Lucent | Radio-Frequency Identification Enabled Inventory Management and Network Operations System and Method |
US20090192858A1 (en) | 2008-01-28 | 2009-07-30 | Blake Johnson | Coordination And Management Of Operational Activities Subject to Uncertainty |
US8051332B2 (en) | 2008-07-15 | 2011-11-01 | Avicode Inc. | Exposing application performance counters for .NET applications through code instrumentation |
US20100070395A1 (en) | 2008-09-18 | 2010-03-18 | Andreas Elkeles | Architectural design for payroll processing application software |
US8352338B2 (en) | 2008-09-18 | 2013-01-08 | Sap Ag | Architectural design for time recording application software |
US20100070336A1 (en) | 2008-09-18 | 2010-03-18 | Sap Ag | Providing Customer Relationship Management Application as Enterprise Services |
US8595077B2 (en) | 2008-09-18 | 2013-11-26 | Sap Ag | Architectural design for service request and order management application software |
US8386325B2 (en) | 2008-09-18 | 2013-02-26 | Sap Ag | Architectural design for plan-driven procurement application software |
US8321306B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for selling project-based services application software |
-
2006
- 2006-03-30 US US11/396,259 patent/US8396749B2/en active Active
-
2007
- 2007-03-29 WO PCT/EP2007/002840 patent/WO2007112954A2/en active Application Filing
Non-Patent Citations (1)
Title |
---|
No Search * |
Also Published As
Publication number | Publication date |
---|---|
US8396749B2 (en) | 2013-03-12 |
WO2007112954A8 (en) | 2008-01-31 |
US20070233574A1 (en) | 2007-10-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8396749B2 (en) | Providing customer relationship management application as enterprise services | |
US8326702B2 (en) | Providing supplier relationship management software application as enterprise services | |
US8660904B2 (en) | Architectural design for service request and order management application software | |
US8396731B2 (en) | Architectural design for service procurement application software | |
US20100070336A1 (en) | Providing Customer Relationship Management Application as Enterprise Services | |
US8595077B2 (en) | Architectural design for service request and order management application software | |
US8380553B2 (en) | Architectural design for plan-driven procurement application software | |
US8401928B2 (en) | Providing supplier relationship management software application as enterprise services | |
US20070156500A1 (en) | Architectural design for sell from stock application software | |
US8676617B2 (en) | Architectural design for self-service procurement application software | |
US8538864B2 (en) | Providing payment software application as enterprise services | |
US8442850B2 (en) | Providing accounting software application as enterprise services | |
US8386325B2 (en) | Architectural design for plan-driven procurement application software | |
US8447657B2 (en) | Architectural design for service procurement application software | |
US8312416B2 (en) | Software model business process variant types | |
US8359218B2 (en) | Computer readable medium for implementing supply chain control using service-oriented methodology | |
US8321250B2 (en) | Architectural design for sell from stock application software | |
US20070233575A1 (en) | Architectural design for strategic sourcing application software | |
US20100138276A1 (en) | Architectural design for make-to-specification application software | |
US8818884B2 (en) | Architectural design for customer returns handling application software | |
US20090171758A1 (en) | Architectural design for physical inventory application software | |
US8374896B2 (en) | Architectural design for opportunity management application software | |
WO2007112947A2 (en) | Providing logistics execution application as enterprise services |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07723782 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 07723782 Country of ref document: EP Kind code of ref document: A1 |