WO2007112959A2 - Providing supplier relationship management software application as enterprise - Google Patents

Providing supplier relationship management software application as enterprise Download PDF

Info

Publication number
WO2007112959A2
WO2007112959A2 PCT/EP2007/002845 EP2007002845W WO2007112959A2 WO 2007112959 A2 WO2007112959 A2 WO 2007112959A2 EP 2007002845 W EP2007002845 W EP 2007002845W WO 2007112959 A2 WO2007112959 A2 WO 2007112959A2
Authority
WO
WIPO (PCT)
Prior art keywords
request
quote
invoice
notify
notification
Prior art date
Application number
PCT/EP2007/002845
Other languages
French (fr)
Inventor
Karina Herrmann
Andreas Brossler
Peter J. Neumayer
Torsten Reichardt
Markus Biehler
Hueseyin Haybat
Christoph Jungkind
Pascal Hochwarth
Shyam Mukundan
Amrish Singh
Karin Brecht-Tillinger
Zeno Rummler
Peter Fitz
Ralf Sievers
Antonia Gross
Brit Panzer
Tobias Hoppe-Boeken
Paola Sala
Andre Wagner
Giovanni Deledda
Robert Reiner
Benjamin Klehr
Original Assignee
Sap Ag
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sap Ag filed Critical Sap Ag
Publication of WO2007112959A2 publication Critical patent/WO2007112959A2/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0603Catalogue ordering
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087Inventory or stock management, e.g. order filling, procurement or balancing against orders
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]

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.
  • This specification describes a services architecture design that provides enterprise services having supplier relationship management functionality at the level of an enterprise application.
  • 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 supplier 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 and IB collectively illustrate a high-level view of a software architectural design and implementation of a suite of enterprise software services having supplier relationship management functionality.
  • FIGS. 2A, 2B and 2C are block diagrams collectively showing a purchase order processing process component.
  • FIGS. 3A . and 3B are block diagrams collectively showing a purchase request processing process component.
  • FIGS. 4A and 4B are block diagrams collectively showing a purchasing contract processing process component.
  • FIGS. 5 A and 5 B are block diagrams collectively showing a goods and service acknowledgement process component.
  • FIGS. 6A, 6B and 6C are block diagrams collectively showing a supplier invoice processing process component.
  • FIGS. 7A, 7B and 7C are block diagrams collectively showing a request for quote (RFQ) processing process component.
  • RFQ request for quote
  • FIGS. 8A and 8B are block diagrams collectively showing an internal request processing process component.
  • FIGS. IA and IB 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 supplier relationship management application functionality.
  • 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 and, 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 term business object will be used generically to refer to a business process object and a master data object, unless the context requires otherwise. Properly implemented, business objects are implemented free of redundancies.
  • the architectural elements also include the process component.
  • a process component is a software package that realizes a business process and generally exposes its functionality as services. The functionality contains business transactions.
  • a process component contains one or more semantically related business objects. Any business object belongs to no more than one process component.
  • Process components are modular and context-independent. That they are context-independent means that a process component is not specific to any specific application and is reusable.
  • the process component is the smallest (most granular) element of reuse in the architecture.
  • the architectural elements also include the operation.
  • An operation belongs to exactly one process component.
  • a process component generally has multiple operations. Operations can be synchronous or asynchronous, corresponding to synchronous or asynchronous process agents, which will be described below.
  • An operation is the smallest, separately-callable function, described by a set of data types used as input, output, and fault parameters, or some combination of them, serving as a signature.
  • 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.
  • 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.
  • 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.
  • 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 ACK) properties of atomicity, consistency, isolation, and durability.
  • an application-defined transaction i.e., a set of actions that have the ACK) 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. 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.
  • 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. 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.
  • 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 and IB collectively illustrate a high-level view of a software architectural design and implementation of a suite of enterprise software services having supplier relationship management functionality.
  • a Purchasing deployment unit 102 includes: a Purchase Order Processing process component 104 that includes a Purchase Order business object 106 and a Purchase Order Confirmation business object 108, a Purchase Request Processing process component 110 that includes a Purchase Request business object 112, a Purchasing Contract Processing process component 114 that includes a Purchasing Contract business object 116, and a Goods and Service Acknowledgement process component 118 that includes a Goods and Service Acknowledgement business object 120.
  • a Supplier Invoicing deployment unit 122 includes: a Supplier Invoice Processing process component 124, a Supplier Invoice Request business object 126, an Evaluated Receipt Settlement Run business object 127, a Supplier Invoice business object 128, and a Supplier Invoice Verification Exception business object 129.
  • an RFQ Processing deployment unit 130 includes: an RFQ Processing process component 132, a Request for Quote business object 134, and a Supplier Quote business object 136.
  • a Requisitioning deployment unit 138 includes: an Internal Request Processing process component 140 and an Internal Request business object 142.
  • FIGS. 2 A, 2B and 2C are block diagrams collectively showing the Purchase Order
  • Processing process component 104 (FIG. IA).
  • FIG. IA 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 RFQ Processing process component 132, an External Procurement Trigger and Response process component 202, the Supplier Invoice Processing process component 124, a Sales Order Processing at Supplier process component 206, a Project Processing process component 208, and an Accounting process component 210. 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 Create Purchase Order based on Winning Quote operation 212 sends a purchase order request using a Maintain Purchase Order based on Winning Quote asynchronous inbound process agent 214 to update the Purchase Order business object 106.
  • the operation 212 can send a purchase order request to update the Purchase Order business object 106 if input is received from the RFQ Processing process component 132.
  • a Change Purchase Order based on Delivery Values operation 216 sends a purchase order change request using a Change Purchase Order based on Delivery Values asynchronous inbound process agent 218 to update the Purchase Order business object 106.
  • the operation 216 can send a purchase order change request to update the Purchase Order business object 106 if input is received from the External Procurement Trigger and Response process component 202.
  • the Create Purchase Order based on Winning Quote operation 212 and the Change Purchase Order based on Delivery Values operation 216 are included in a Purchasing In interface 220.
  • a Change Purchase Order based on Invoiced Values operation 222 sends a purchase order change request using a Change Purchase Order based on Invoiced Values asynchronous inbound process agent 224 to update the Purchase Order business object 106.
  • the operation 222 can send a purchase order change request to update the Purchase Order business object 106 if input is received from the Supplier Invoice Processing process component 124.
  • the Change Purchase Order based on Invoiced Values operation 222 is included in an Invoice Verification In interface 226.
  • a Create Purchase Order Confirmation operation 234 sends a purchase order confirmation using a Purchase Order Confirmation asynchronous inbound process agent 236 to update the Purchase Order Confirmation business object 108.
  • the operation 234 can send a purchase order confirmation to update the Purchase Order Confirmation business object 108 if input is received from the Sales Order Processing at Supplier process component 206.
  • the Create Purchase Order Confirmation operation 234 is included in an Ordering In interface 238.
  • the Purchase Order business object 106 can receive updated information and send the update into other components to perform further operations. As shown in FIGS. 2B and 2C, multiple outbound process agents can receive information from the Purchase Order business object 106.
  • a Notify of Invoicing Due from Purchase Order to Supplier Invoice Processing can invoke a Notify of Invoicing Due operation 242.
  • the outbound process agent 240 can send a notification that an invoice is due to a specific supplier.
  • the notification can be sent to the Supplier Invoice Processing process component 124.
  • the Notify of Invoicing Due operation 242 is included in an Invoice Verification Out interface 244.
  • a Request Purchase Order to Supplier asynchronous outbound process agent 252 can invoke a Request Purchase Order Change operation 254.
  • the outbound process agent 252 can send a request to change an existing purchase order.
  • the notification can be sent to the Sales Order Processing at Supplier process component 206.
  • the Request Purchase Order to Supplier asynchronous outbound process agent 252 can also invoke a Request Purchase Order Cancellation operation 256.
  • the outbound process agent 252 can send a request to cancel an existing purchase order.
  • the notification can be sent to the Sales Order Processing at Supplier process component 206.
  • the Request Purchase Order to Supplier asynchronous outbound process agent 252 can also invoke a Request Purchase Order Creation operation 258.
  • the outbound process agent 252 can send a request to create a new purchase order.
  • the notification can be sent to the Sales Order Processing at Supplier process component 206.
  • the Request Purchase Order Change operation 254, the Request Purchase Order Cancellation operation 256, and the Request Purchase Order Creation operation 258 are included in an Ordering Out interface 260.
  • a Notify of Purchase Order to External Procurement Trigger and Response asynchronous outbound process agent 262 can invoke a Notify of Purchase Order operation 264.
  • the outbound process agent 262 can send a notification of the purchase order to the External Procurement Trigger and Response process component 202.
  • the Notify of Purchase Order operation 264 is included in a Purchasing Out interface 266.
  • a Notify of Purchase Order to Project Processing asynchronous outbound process agent 268 can also invoke the Notify of Purchase Order operation 264.
  • the outbound process agent 268 can send a notification of the purchase order to the Project Processing process component 208.
  • a Notify of Purchase Order to Time and Labor Management asynchronous outbound process agent 269 can also invoke the Notify of Purchase Order operation 264.
  • the outbound process agent 269 can send a notification of the purchase order to the Time and Labor Management process component 209.
  • a Notify of Purchase Order to Accounting asynchronous outbound process agent 270 can invoke a Notify of Purchase Order operation 272.
  • the outbound process agent 270 can send a notification of the purchase order to the Accounting process component 210.
  • the Notify of Purchase Order operation 272 is included in an Order Accounting Out interface 274.
  • FIGS. 3 A and 3B are block diagrams collectively showing the Purchase Request Processing process component 110 (FIG. IA).
  • FIGS. 3 A and 3B are block diagrams collectively showing the Purchase Request Processing process component 110 (FIG. IA).
  • FIGS. 3 A and 3B are block diagrams collectively showing the Purchase Request Processing process component 110 (FIG. IA).
  • FIGS. 3 A and 3B are block diagrams collectively showing the Purchase Request Processing process component 110 (FIG. IA).
  • FIGS. 3 A and 3B are block diagrams collectively showing the Purchase Request Processing process component 110 (FIG. IA).
  • FIGS. 3 A and 3B are block diagrams collectively showing the Purchase Request Processing process component 110 (FIG. IA).
  • FIGS. 3 A and 3B are block diagrams collectively showing the Purchase Request Processing process component 110 (FIG. IA).
  • FIGS. 3 A and 3B are block diagrams collectively showing the Purchase Request Processing process component 110 (FIG. IA).
  • a Change Purchase Request operation 302 can send a request to a Change Purchase Request based on Request for Quote asynchronous inbound process agent 306 to update the Purchase Request business object 112. For example, the operation 302 can send a request to update the Purchase Request business object 112 if input is received from the RFQ Processing process component 132.
  • the Change Purchase Request operation 302 is included in a Request for Quote In interface 308.
  • a Maintain Purchase Request operation 310 can send a request to a Maintain Purchase Request asynchronous inbound process agent 314 to update the Purchase Request business object 112. For example, the operation 310 can send the request to update the Purchase Request business object 112 if input is received from the Internal Request Processing process component 140, the External Procurement Trigger and Response process component 202, or the Project Processing process component 208.
  • the Maintain Purchase Request operation 310 is included in a Purchasing In interface 316.
  • the Purchase Request business object 112 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 3B, multiple outbound process agents can receive information from the Purchase Request business object 112.
  • a Request Request for Quote Execution from Purchase Request to RFQ Processing asynchronous outbound process agent 318 can invoke a Request Request for Quote Execution operation 320.
  • the outbound process agent 318 can invoke the operation 320 to update the RFQ Processing process component 132.
  • the Request Request for Quote Execution operation 320 is included in a Request for Quote Out interface 324.
  • a Confirm Purchase Request asynchronous outbound process agent 326 can invoke a Confirm Purchase Request operation 328 .
  • the outbound process agent 326 can invoke the operation 328 to update the Internal Request Processing process component 140, the External Procurement Trigger and Response process component 202, or the Project Processing process component 208.
  • the Confirm Purchase Request operation 328 is included in a Purchasing Out interface 332.
  • FIGS. 4A and 4B are block diagrams collectively showing the Purchasing Contract Processing process component 114 (FIG. IA). 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 RFQ Processing process component 132, the Supplier Invoice Processing process component 124, and a Product Catalog Authoring process component 404 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 Purchasing Contract operation 406 can send a message to a Maintain Purchasing Contract asynchronous inbound process agent 410 to update the Purchasing
  • Contract business object 116 For example, the operation 406 can send a message to update the Purchasing Contract business object 116 if input is received from the RFQ Processing process component 132.
  • the Maintain Purchasing Contract operation 406 is included in a Contract Maintenance In interface 412.
  • a Confirm Request for Quote operation 414 can send a message to a Maintain
  • Purchasing Contract Relations asynchronous inbound process agent 418 to update the Purchasing Contract business object 116.
  • the operation 414 can send a message to update the Purchasing Contract business object 116 if input is received from the RFQ Processing process component 132.
  • the Confirm Request for Quote operation 414 is included in a Request for Quote In interface 420.
  • a Maintain Purchasing Contract Release operation 422 can send a message to a Maintain Purchasing Contract Release asynchronous inbound process agent 426 to update the Purchasing Contract business object 116.
  • the operation 422 can send a message to update the Purchasing Contract business object 116 if input is received from the Supplier Invoice Processing process component 124.
  • the Maintain Purchasing Contract Release operation 422 is included in a Contract Release In interface 428.
  • the Purchasing Contract business object 116 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 4B, multiple outbound process agents can receive information from the Purchasing Contract business object 116.
  • a Request Request for Quote Execution from Purchasing Contract to RFQ Processing asynchronous outbound process agent 436 can invoke a Request Request for Quote Execution operation 438.
  • the outbound process agent 436 can invoke the operation 438 to send a message to the RFQ Processing process component 132.
  • the outbound process agent 436 can also invoke a Request Request for Quote Cancellation operation 442.
  • the outbound process agent 436 can invoke the operation 442 to send a message to the RFQ Processing process component 132.
  • the Request Request for Quote Execution operation 438 and the Request Request for Quote Cancellation operation 442 are included in a Request for Quote Out interface 446.
  • a Notify of Product from Purchasing Contract to Product Catalog Authoring asynchronous outbound process agent 448 can invoke a Notify of Product Catalog operation 450.
  • the outbound process agent 448 can invoke the operation 450 to send a message to the Product Catalog Authoring process component 404.
  • the Notify of Product Catalog operation 450 is included in a Product Catalog Authoring Out interface 454.
  • a Notify of Invoicing Due from Purchasing Contract to Supplier Invoice Processing asynchronous outbound process agent 456 can invoke a Notify of Invoicing Due operation 458.
  • the outbound process agent 456 can invoke the operation 458 to send a message to the Supplier Invoice Processing process component 124.
  • the Notify of Invoicing Due operation 458 is included in an Invoice Verification Out interface 462.
  • a Confirm Purchasing Contract to RFQ Processing asynchronous outbound process agent 464 can invoke a Confirm Purchasing Contract operation 466.
  • the outbound process agent 464 can invoke the operation 466 to send a message to the RFQ Processing process component 132.
  • the Confirm Purchasing Contract operation 466 is included in a Purchasing Contract Out interface 470.
  • FIGS. 5A and 5B are block diagrams collectively showing the Goods and Service
  • Acknowledgement process component 118 (FIG. IA).
  • FIG. IA Acknowledgement process component 118
  • 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 Time and Labor Management process component 209, the Internal Request Processing process component 140, the Supplier Invoice Processing process component 124, and the Accounting process component 210.
  • 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 Cancel Goods and Service Acknowledgement operation 506 can send an acknowledgement using a Maintain Goods and Service Acknowledgement (GSA) based on Internal Acknowledgement asynchronous inbound process agent 508 to update the Goods and Service Acknowledgement business object 120.
  • GSA Maintain Goods and Service Acknowledgement
  • the operation 506 can send an acknowledgement to update the Goods and Service Acknowledgement business object 120 if input is received from the Time and Labor Management process component 209.
  • a Create Goods and Service Acknowledgement operation 510 can also send an acknowledgement using the Maintain GSA based on Internal Acknowledgement asynchronous inbound process agent 508 to update the Goods and Service Acknowledgement business object 120.
  • the operation 506 can send an acknowledgement to update the Goods and Service Acknowledgement business object 120 if input is received from the Time and Labor Management process component 209 or the Internal Request Processing process component 140.
  • the Cancel Goods and Service Acknowledgement operation 506 and the Create Goods and Service Acknowledgement operation 510 are included in an Internal Acknowledgement In interface 512.
  • the Goods and Service Acknowledgement business object 120 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 5B, multiple outbound process agents can receive information from the Goods and Service Acknowledgement business object 120.
  • a Notify of Invoicing Due from GSA to Supplier Invoice Processing asynchronous outbound process agent 520 can invoke a Notify of Invoicing Due operation 522.
  • the outbound process agent 520 can send a notification of an invoice due for items in a purchase order. The notification can be sent to the Supplier Invoice Processing process component 124.
  • the Notify of Invoicing Due operation 522 is included in an Invoice Verification Out interface 524.
  • a Notify of Goods and Service Acknowledgement to Accounting asynchronous outbound process agent 526 can invoke a Notify of Goods and Service Acknowledgement operation 528.
  • the outbound process agent 526 can send a notification that goods or services were received. The notification can be sent to the Accounting process component 210.
  • the Notify of Goods and Service Acknowledgement to Accounting asynchronous outbound process agent 526 can also invoke a Notify of Goods and Service Acknowledgement Cancellation operation 530.
  • the outbound process agent can cancel a notification that goods or services were received.
  • the notification can be sent to the Accounting process component 210.
  • the Notify of Goods and Service Acknowledgement operation 528 and the Notify of Goods and Service Acknowledgement Cancellation operation 530 are included in a Goods and Service Accounting Out interface 532.
  • FIGS. 6A, 6B and 6C are block diagrams collectively showing the Supplier Invoice Processing process component 124 (FIG. IB).
  • FIGS. 6A, 6B and 6C are block diagrams collectively showing the Supplier Invoice Processing process component 124 (FIG. IB).
  • FIGS. 6A, 6B and 6C are block diagrams collectively showing the Supplier Invoice Processing process component 124 (FIG. IB).
  • FIGS. 6A, 6B and 6C are block diagrams collectively showing the Supplier Invoice Processing process component 124 (FIG. IB).
  • FIGS. 6A, 6B and 6C are block diagrams collectively showing the Supplier Invoice Processing process component 124 (FIG. IB).
  • FIGS. 6A, 6B and 6C are block diagrams collectively showing the Supplier Invoice Processing process component 124 (FIG. IB).
  • a Maintain Invoice Request operation 608 can send a request using a Maintain
  • the Supplier Invoice Request asynchronous inbound process agent 610 to update the Supplier Invoice Request business object 126.
  • the operation 608 can send a request to update the Supplier Invoice Request business object 126 if input is received from the Purchase Order Processing process component 104, the Inbound Delivery Processing process component 601 , the Goods and Service Acknowledgement process component 118, or the Purchasing Contract Processing process component 1 14.
  • the Maintain Invoice Request operation 608 is included in an Invoice Verification In interface 612.
  • a Create Invoice operation 614 can send a request using a Create Supplier Invoice based on Supplier Invoice Request asynchronous inbound process agent 616 to update the Supplier Invoice business object 128.
  • the operation 614 can send a supplier invoice request to update the Supplier Invoice business object 128 if input is received from the Internal Request Processing process component 140.
  • the Create Invoice operation 614 is included in an Internal Invoicing In interface 618.
  • a Create Invoice operation 620 can send a request using a Create Supplier Invoice based on Invoice Request asynchronous inbound process agent 622 to update the Supplier Invoice business object 128.
  • the operation 620 can send a supplier invoice request to update the Supplier Invoice business object 128 if input is received from the Customer Invoice Processing at Supplier process component 602.
  • the Create Invoice operation 620 is included in an Invoicing hi interface 624.
  • the Supplier Invoice Request business object 126 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 6B, multiple outbound process agents can receive information from the Supplier Invoice Request business object 126.
  • the outbound process agent 626 can send a notification of a released contract. The notification can be sent to the Purchasing Contract Processing process component 114.
  • the Notify of Contract Release operation 628 is included in a Contract Release Out interface 630.
  • a Notify of Invoiced Values from SIR to Purchase Order Processing asynchronous outbound process agent 632 can invoke a Notify of Invoiced Values operation 634.
  • the outbound process agent 632 can send a notification of invoiced values for a purchase order.
  • the notification can be sent to the Purchase Order Processing process component 104.
  • the Notify of Invoiced Values operation 634 is included in an Invoice Verification Out interface 636.
  • the Supplier Invoice business object 128 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 6C, multiple outbound process agents can receive information from the Supplier Invoice business object 128.
  • a Notify of Supplier Invoice to Accounting asynchronous outbound process agent 644 can invoke a Notify of Invoice operation 646.
  • the outbound process agent 644 can send a notification of an invoice that was created for a particular supplier. The notification can be sent to the Accounting process component 210.
  • the Notify of Supplier Invoice to Accounting asynchronous outbound process agent 644 can also invoke a Notify of Invoice Cancellation operation 648.
  • the outbound process agent 644 can send a notification of the cancellation of an invoice for a supplier.
  • the notification can be sent to the Accounting process component 210.
  • the Notify of Invoice operation 646 and the Notify of Invoice Cancellation operation 648 are included in an Invoice Accounting Out interface 650.
  • a Notify of Supplier Invoice to Due Item Processing asynchronous outbound process agent 652 can invoke a Notify of Invoice operation 654.
  • the outbound process agent 652 can send a notification of an invoice that was created for a particular supplier. The notification can be sent to the Due Item Processing process component 606.
  • the Notify of Supplier Invoice to Due Item Processing asynchronous outbound process agent 652 can also invoke a Notify of Invoice Cancellation operation 656.
  • the outbound process agent 652 can send a notification of the cancellation of an invoice for a supplier.
  • the notification can be sent to the Due Item Processing process component 606.
  • the Notify of Invoice operation 654 and the Notify of Invoice Cancellation operation 656 are included in a Receivables Payables Out interface 658.
  • a Confirm Invoice to Supplier asynchronous outbound process agent 660 can invoke a Confirm Invoice operation 662.
  • the outbound process agent 660 can send a notification to confirm an invoice to a supplier.
  • the notification can be sent to the Customer Invoice Processing at Supplier process component 602.
  • the Confirm Invoice operation 662 is included in an Invoicing Out interface 664.
  • a Request Evaluated Receipt Settlement (ERS) Invoice to Supplier asynchronous outbound process agent 666 can invoke a Request ERS Invoice operation 668.
  • the outbound process agent 666 can send a notification of an ERS invoice.
  • the notification can be sent to the Customer Invoice Processing at Supplier process component 602.
  • the Request ERS Invoice operation 668 is included in an ERS Invoicing Out interface 670.
  • FIGS. 7A, 7B and 7C are block diagrams collectively showing the RFQ Processing process component 132 (FIG. IB). 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 Purchase Request Processing process component 110, the Purchasing Contract Processing process component 114, an Opportunity/Customer Quote Processing at Supplier process component 702, and the Purchase Order Processing process component 104. 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 Request for Quote operation 704 can send a request for quote using a Maintain Request for Quote asynchronous inbound process agent 706 to update the Request for Quote business object 134.
  • the operation 704 can send a request for quote to update the Request for Quote business object 134 if input is received from the Purchase Request Processing process component 110.
  • a Cancel Request for Quote operation 708 can send a cancellation request using the Maintain Request for Quote asynchronous inbound process agent 706 to update the Request for Quote business object 134.
  • the operation 708 can send a cancellation request to update the Request for Quote business object 134 if input is received from the Purchase Request Processing process component 110 or the Purchasing Contract Processing process component 114.
  • the Maintain Request for Quote operation 704 and the Cancel Request for Quote operation 708 are included in a Request for Quote In interface 710.
  • a Maintain Supplier Quote Relations operation 712 can send a supplier quote using a Maintain Supplier Quote Relations based on Purchasing Contract asynchronous inbound process agent 714 to update the Supplier Quote business object 136. For example, the operation 712 can send a supplier quote to update the Supplier Quote business object 136 if input is received from the Purchasing Contract Processing process component 114.
  • the Maintain Supplier Quote Relations operation 712 is included in a Purchasing Contract In interface 716.
  • a Maintain Supplier Quote operation 718 can send a supplier quote using a Maintain Supplier Quote asynchronous inbound process agent 720 to update the Supplier Quote business object 136. For example, the operation 718 can send a supplier quote to update the Supplier Quote business object 136 if input is received from the Opportunity/Customer Quote Processing at Supplier process component 702.
  • the Maintain Supplier Quote operation 718 is included in a Supplier Quote Processing In interface 722.
  • the Request for Quote business object 134 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 7B, multiple outbound process agents can receive information from the Request for Quote business object 134.
  • a Confirm Request for Quote asynchronous outbound process agent 724 can invoke a Confirm Request for Quote operation 726.
  • the outbound process agent 724 can send a notification to confirm a request for quote.
  • the notification can be sent to the Purchase Request Processing process component 110 or the Purchasing Contract Processing process component 114.
  • the Confirm Request for Quote operation 726 is included in a Request for Quote Out interface 728.
  • a Request Quote Maintenance from Request for Quote to Supplier asynchronous outbound process agent 730 can invoke a Request Quote Creation operation 732.
  • the outbound process agent 730 can send a notification of a request to create a quote.
  • the notification can be sent to the Opportunity/Customer Quote Processing at
  • the Request Quote Maintenance from Request for Quote to Supplier asynchronous outbound process agent 730 can also invoke a Notify of Request for Quote Cancellation operation 734.
  • the outbound process agent 730 can send a notification of a quote cancellation.
  • the notification can be sent to the Opportunity/Customer Quote Processing at Supplier process component 702.
  • the Request Quote Maintenance from Request for Quote to Supplier asynchronous outbound process agent 730 can also invoke a Notify of Request for Quote Change operation 736.
  • the outbound process agent 730 can send a notification of a quote change.
  • the notification can be sent to the Opportunity/Customer Quote Processing at Supplier process component 702.
  • the Request Quote Creation operation 732, the Notify of Request for Quote Cancellation operation 734, and the Notify of Request for Quote Change operation 736 are included in a Request Quote Processing Out interface 738.
  • the Supplier Quote business object .136 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 7C, multiple outbound process agents can receive information from the Supplier Quote business object 136.
  • a Request Purchase Order from Supplier Quote to Purchase Order Processing asynchronous outbound process agent 740 can invoke a Request Purchase Order from Winning Quote operation 742.
  • the outbound process agent 740 can send a notification of purchase order based on a winning quote. The notification can be sent to the Purchase Order Processing process component 104.
  • the Request Purchase Order from Winning Quote operation 742 is included in a Purchasing Out interface 744.
  • a Request Contract from Supplier Quote to Purchasing Contract Processing asynchronous outbound process agent 746 can invoke a Request Contract from Winning Quote operation 748.
  • the outbound process agent 746 can send a contract maintenance request based on a winning quote associated with the contract.
  • the notification can be sent to the Purchasing Contract Processing process component 114.
  • the Request Contract from Winning Quote operation 748 is included in a Purchasing Contract Out interface 750.
  • a Request Quote Maintenance from Supplier Quote to Supplier asynchronous outbound process agent 752 can invoke a Request Quote Change operation 754.
  • the outbound process agent 752 can send a notification of a quote change request.
  • the notification can be sent to the Opportunity/Customer Quote Processing at Supplier process component 702.
  • the Request Quote Change operation 754 is included in a Supplier Quote Processing Out interface 756.
  • a Notify of Quote Award from Supplier Quote to Supplier asynchronous outbound process agent 758 can invoke a Notify of Quote Award operation 760.
  • the outbound process agent 758 can send a notification of the quote award.
  • the notification can be sent to the Opportunity/Customer Quote Processing at Supplier process component 702.
  • the Notify of Quote Award operation 760 is included in the Supplier Quote Processing Out interface 756.
  • FIGS. 8 A and 8B are block diagrams collectively showing the Internal Request Processing process component 140 (FIG. IB).
  • FIGS. 8 A and 8B are block diagrams collectively showing the Internal Request Processing process component 140 (FIG. IB).
  • FIGS. 8 A and 8B are block diagrams collectively showing the Internal Request Processing process component 140 (FIG. IB).
  • FIGS. 8 A and 8B are block diagrams collectively showing the Internal Request Processing process component 140 (FIG. IB).
  • FIGS. 8 A and 8B are block diagrams collectively showing the Internal Request Processing process component 140 (FIG. IB).
  • FIGS. 8 A and 8B are block diagrams collectively showing the Internal Request Processing process component 140 (FIG. IB).
  • FIGS. 8 A and 8B are block diagrams collectively showing the Internal Request Processing process component 140 (FIG. IB).
  • FIGS. 8 A and 8B are block diagrams collectively showing the Internal Request Processing process component 140 (FIG. IB).
  • a Change Internal Request based on Procurement Progress operation 804 can send a request using a Change Internal Request based on Procurement Progress asynchronous inbound process agent 806 to update the Internal Request business object 142.
  • the operation 804 can send a request to update the Internal Request business object 142 if input is received from the Purchase Request Processing process component 110.
  • the Change Internal Request based on Procurement Progress operation 804 is included in a Purchasing In interface 808.
  • the Internal Request business object 142 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 8B, multiple outbound process agents can receive information from the Internal Request business object 142.
  • a Request Purchasing from Internal Request to Purchase Request Processing asynchronous outbound process agent 836 can invoke a Request Purchasing operation 838.
  • the outbound process agent 836 can send a request purchasing notification.
  • the notification can be sent to the Purchase Request Processing process component 110.
  • the Request Purchasing operation 838 is included in a Purchasing Out interface 840.
  • a Request GSA from Internal Request to Goods and Service Acknowledgement asynchronous outbound process agent 842 can invoke a Request GSA based on Delivery Confirmation operation 844.
  • the outbound process agent 842 can send a notification of a request for a goods and service acknowledgement once the delivery of goods has occurred. The notification can be sent to the Goods and Service Acknowledgement process component 118.
  • the Request GSA based on Delivery Confirmation operation 844 is included in an Internal Acknowledgement Out interface 846.
  • a Request Invoicing from Internal Request to Supplier Invoice Processing asynchronous outbound process agent 848 can invoke a Request Invoicing based on Invoice Acceptance operation 850.
  • the outbound process agent 848 can send a notification of a request for an invoice after acceptance of the invoice.
  • the notification can be sent to the Supplier Invoice Processing process component 124.
  • the Request Invoicing based on Invoice Acceptance operation 850 is included in an Internal Invoicing Out interface 852.
  • 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.

Description

PROVIDING SUPPLIER RELATIONSHIP MANAGEMENT SOFTWARE 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 supplier relationship management 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 supplier 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 and IB collectively illustrate a high-level view of a software architectural design and implementation of a suite of enterprise software services having supplier relationship management functionality.
FIGS. 2A, 2B and 2C are block diagrams collectively showing a purchase order processing process component.
FIGS. 3A.and 3B are block diagrams collectively showing a purchase request processing process component.
FIGS. 4A and 4B are block diagrams collectively showing a purchasing contract processing process component. FIGS. 5 A and 5 B are block diagrams collectively showing a goods and service acknowledgement process component.
FIGS. 6A, 6B and 6C are block diagrams collectively showing a supplier invoice processing process component.
FIGS. 7A, 7B and 7C are block diagrams collectively showing a request for quote (RFQ) processing process component.
FIGS. 8A and 8B are block diagrams collectively showing an internal request processing process component.
Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION
FIGS. IA and IB 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 supplier relationship management application functionality.
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 and, 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 term business object will be used generically to refer to a business process object and a master data object, unless the context requires otherwise. Properly implemented, business objects are implemented free of redundancies.
The architectural elements also include the process component. A process component is a software package that realizes a business process and generally exposes its functionality as services. The functionality contains business transactions. A process component contains one or more semantically related business objects. Any business object belongs to no more than one process component.
Process components are modular and context-independent. That they are context-independent means that a process component is not specific to any specific application and is reusable. The process component is the smallest (most granular) element of reuse in the architecture. The architectural elements also include the operation. An operation belongs to exactly one process component. A process component generally has multiple operations. Operations can be synchronous or asynchronous, corresponding to synchronous or asynchronous process agents, which will be described below. An operation is the smallest, separately-callable function, described by a set of data types used as input, output, and fault parameters, 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 ACK) 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 and IB collectively illustrate a high-level view of a software architectural design and implementation of a suite of enterprise software services having supplier relationship management functionality.
As shown in FIG. IA, a Purchasing deployment unit 102 includes: a Purchase Order Processing process component 104 that includes a Purchase Order business object 106 and a Purchase Order Confirmation business object 108, a Purchase Request Processing process component 110 that includes a Purchase Request business object 112, a Purchasing Contract Processing process component 114 that includes a Purchasing Contract business object 116, and a Goods and Service Acknowledgement process component 118 that includes a Goods and Service Acknowledgement business object 120.
As shown in FIG. IB, a Supplier Invoicing deployment unit 122 includes: a Supplier Invoice Processing process component 124, a Supplier Invoice Request business object 126, an Evaluated Receipt Settlement Run business object 127, a Supplier Invoice business object 128, and a Supplier Invoice Verification Exception business object 129. Additionally, an RFQ Processing deployment unit 130 includes: an RFQ Processing process component 132, a Request for Quote business object 134, and a Supplier Quote business object 136.
Additionally, a Requisitioning deployment unit 138 includes: an Internal Request Processing process component 140 and an Internal Request business object 142. FIGS. 2 A, 2B and 2C are block diagrams collectively showing the Purchase Order
Processing process component 104 (FIG. IA). 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 RFQ Processing process component 132, an External Procurement Trigger and Response process component 202, the Supplier Invoice Processing process component 124, a Sales Order Processing at Supplier process component 206, a Project Processing process component 208, and an Accounting process component 210. 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 Create Purchase Order based on Winning Quote operation 212 sends a purchase order request using a Maintain Purchase Order based on Winning Quote asynchronous inbound process agent 214 to update the Purchase Order business object 106. For example, the operation 212 can send a purchase order request to update the Purchase Order business object 106 if input is received from the RFQ Processing process component 132.
A Change Purchase Order based on Delivery Values operation 216 sends a purchase order change request using a Change Purchase Order based on Delivery Values asynchronous inbound process agent 218 to update the Purchase Order business object 106. For example, the operation 216 can send a purchase order change request to update the Purchase Order business object 106 if input is received from the External Procurement Trigger and Response process component 202.
The Create Purchase Order based on Winning Quote operation 212 and the Change Purchase Order based on Delivery Values operation 216 are included in a Purchasing In interface 220. A Change Purchase Order based on Invoiced Values operation 222 sends a purchase order change request using a Change Purchase Order based on Invoiced Values asynchronous inbound process agent 224 to update the Purchase Order business object 106. For example, the operation 222 can send a purchase order change request to update the Purchase Order business object 106 if input is received from the Supplier Invoice Processing process component 124. The Change Purchase Order based on Invoiced Values operation 222 is included in an Invoice Verification In interface 226.
A Create Purchase Order Confirmation operation 234 sends a purchase order confirmation using a Purchase Order Confirmation asynchronous inbound process agent 236 to update the Purchase Order Confirmation business object 108. For example, the operation 234 can send a purchase order confirmation to update the Purchase Order Confirmation business object 108 if input is received from the Sales Order Processing at Supplier process component 206. The Create Purchase Order Confirmation operation 234 is included in an Ordering In interface 238.
The Purchase Order business object 106 can receive updated information and send the update into other components to perform further operations. As shown in FIGS. 2B and 2C, multiple outbound process agents can receive information from the Purchase Order business object 106.
A Notify of Invoicing Due from Purchase Order to Supplier Invoice Processing asynchronous outbound process agent 240 can invoke a Notify of Invoicing Due operation 242. For example, the outbound process agent 240 can send a notification that an invoice is due to a specific supplier. The notification can be sent to the Supplier Invoice Processing process component 124. The Notify of Invoicing Due operation 242 is included in an Invoice Verification Out interface 244.
A Request Purchase Order to Supplier asynchronous outbound process agent 252 can invoke a Request Purchase Order Change operation 254. For example, the outbound process agent 252 can send a request to change an existing purchase order. The notification can be sent to the Sales Order Processing at Supplier process component 206. The Request Purchase Order to Supplier asynchronous outbound process agent 252 can also invoke a Request Purchase Order Cancellation operation 256. For example, the outbound process agent 252 can send a request to cancel an existing purchase order. The notification can be sent to the Sales Order Processing at Supplier process component 206. The Request Purchase Order to Supplier asynchronous outbound process agent 252 can also invoke a Request Purchase Order Creation operation 258. For example, the outbound process agent 252 can send a request to create a new purchase order. The notification can be sent to the Sales Order Processing at Supplier process component 206. The Request Purchase Order Change operation 254, the Request Purchase Order Cancellation operation 256, and the Request Purchase Order Creation operation 258 are included in an Ordering Out interface 260.
A Notify of Purchase Order to External Procurement Trigger and Response asynchronous outbound process agent 262 can invoke a Notify of Purchase Order operation 264. For example, the outbound process agent 262 can send a notification of the purchase order to the External Procurement Trigger and Response process component 202. The Notify of Purchase Order operation 264 is included in a Purchasing Out interface 266.
A Notify of Purchase Order to Project Processing asynchronous outbound process agent 268 can also invoke the Notify of Purchase Order operation 264. For example, the outbound process agent 268 can send a notification of the purchase order to the Project Processing process component 208.
A Notify of Purchase Order to Time and Labor Management asynchronous outbound process agent 269 can also invoke the Notify of Purchase Order operation 264. For example, the outbound process agent 269 can send a notification of the purchase order to the Time and Labor Management process component 209.
A Notify of Purchase Order to Accounting asynchronous outbound process agent 270 can invoke a Notify of Purchase Order operation 272. For example, the outbound process agent 270 can send a notification of the purchase order to the Accounting process component 210. The Notify of Purchase Order operation 272 is included in an Order Accounting Out interface 274.
FIGS. 3 A and 3B are block diagrams collectively showing the Purchase Request Processing process component 110 (FIG. IA). 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 RFQ Processing process component 132, the Internal Request Processing process component 140, the External Procurement Trigger and Response process component 202, and the Project Processing process component 208. 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 Change Purchase Request operation 302 can send a request to a Change Purchase Request based on Request for Quote asynchronous inbound process agent 306 to update the Purchase Request business object 112. For example, the operation 302 can send a request to update the Purchase Request business object 112 if input is received from the RFQ Processing process component 132. The Change Purchase Request operation 302 is included in a Request for Quote In interface 308.
A Maintain Purchase Request operation 310 can send a request to a Maintain Purchase Request asynchronous inbound process agent 314 to update the Purchase Request business object 112. For example, the operation 310 can send the request to update the Purchase Request business object 112 if input is received from the Internal Request Processing process component 140, the External Procurement Trigger and Response process component 202, or the Project Processing process component 208. The Maintain Purchase Request operation 310 is included in a Purchasing In interface 316.
The Purchase Request business object 112 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 3B, multiple outbound process agents can receive information from the Purchase Request business object 112.
A Request Request for Quote Execution from Purchase Request to RFQ Processing asynchronous outbound process agent 318 can invoke a Request Request for Quote Execution operation 320. For example, the outbound process agent 318 can invoke the operation 320 to update the RFQ Processing process component 132. The Request Request for Quote Execution operation 320 is included in a Request for Quote Out interface 324.
A Confirm Purchase Request asynchronous outbound process agent 326 can invoke a Confirm Purchase Request operation 328 . For example, the outbound process agent 326 can invoke the operation 328 to update the Internal Request Processing process component 140, the External Procurement Trigger and Response process component 202, or the Project Processing process component 208. The Confirm Purchase Request operation 328 is included in a Purchasing Out interface 332.
FIGS. 4A and 4B are block diagrams collectively showing the Purchasing Contract Processing process component 114 (FIG. IA). 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 RFQ Processing process component 132, the Supplier Invoice Processing process component 124, and a Product Catalog Authoring process component 404 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 Purchasing Contract operation 406 can send a message to a Maintain Purchasing Contract asynchronous inbound process agent 410 to update the Purchasing
Contract business object 116. For example, the operation 406 can send a message to update the Purchasing Contract business object 116 if input is received from the RFQ Processing process component 132. The Maintain Purchasing Contract operation 406 is included in a Contract Maintenance In interface 412. A Confirm Request for Quote operation 414 can send a message to a Maintain
Purchasing Contract Relations asynchronous inbound process agent 418 to update the Purchasing Contract business object 116. For example, the operation 414 can send a message to update the Purchasing Contract business object 116 if input is received from the RFQ Processing process component 132. The Confirm Request for Quote operation 414 is included in a Request for Quote In interface 420.
A Maintain Purchasing Contract Release operation 422 can send a message to a Maintain Purchasing Contract Release asynchronous inbound process agent 426 to update the Purchasing Contract business object 116. For example, the operation 422 can send a message to update the Purchasing Contract business object 116 if input is received from the Supplier Invoice Processing process component 124. The Maintain Purchasing Contract Release operation 422 is included in a Contract Release In interface 428.
The Purchasing Contract business object 116 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 4B, multiple outbound process agents can receive information from the Purchasing Contract business object 116.
A Request Request for Quote Execution from Purchasing Contract to RFQ Processing asynchronous outbound process agent 436 can invoke a Request Request for Quote Execution operation 438. For example, the outbound process agent 436 can invoke the operation 438 to send a message to the RFQ Processing process component 132. The outbound process agent 436 can also invoke a Request Request for Quote Cancellation operation 442. For example, the outbound process agent 436 can invoke the operation 442 to send a message to the RFQ Processing process component 132. The Request Request for Quote Execution operation 438 and the Request Request for Quote Cancellation operation 442 are included in a Request for Quote Out interface 446. A Notify of Product from Purchasing Contract to Product Catalog Authoring asynchronous outbound process agent 448 can invoke a Notify of Product Catalog operation 450. For example, the outbound process agent 448 can invoke the operation 450 to send a message to the Product Catalog Authoring process component 404. The Notify of Product Catalog operation 450 is included in a Product Catalog Authoring Out interface 454. A Notify of Invoicing Due from Purchasing Contract to Supplier Invoice Processing asynchronous outbound process agent 456 can invoke a Notify of Invoicing Due operation 458. For example, the outbound process agent 456 can invoke the operation 458 to send a message to the Supplier Invoice Processing process component 124. The Notify of Invoicing Due operation 458 is included in an Invoice Verification Out interface 462. A Confirm Purchasing Contract to RFQ Processing asynchronous outbound process agent 464 can invoke a Confirm Purchasing Contract operation 466. For example, the outbound process agent 464 can invoke the operation 466 to send a message to the RFQ Processing process component 132. The Confirm Purchasing Contract operation 466 is included in a Purchasing Contract Out interface 470. FIGS. 5A and 5B are block diagrams collectively showing the Goods and Service
Acknowledgement process component 118 (FIG. IA). 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 Time and Labor Management process component 209, the Internal Request Processing process component 140, the Supplier Invoice Processing process component 124, and the Accounting process component 210. 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 Cancel Goods and Service Acknowledgement operation 506 can send an acknowledgement using a Maintain Goods and Service Acknowledgement (GSA) based on Internal Acknowledgement asynchronous inbound process agent 508 to update the Goods and Service Acknowledgement business object 120. For example, the operation 506 can send an acknowledgement to update the Goods and Service Acknowledgement business object 120 if input is received from the Time and Labor Management process component 209. A Create Goods and Service Acknowledgement operation 510 can also send an acknowledgement using the Maintain GSA based on Internal Acknowledgement asynchronous inbound process agent 508 to update the Goods and Service Acknowledgement business object 120. For example, the operation 506 can send an acknowledgement to update the Goods and Service Acknowledgement business object 120 if input is received from the Time and Labor Management process component 209 or the Internal Request Processing process component 140. The Cancel Goods and Service Acknowledgement operation 506 and the Create Goods and Service Acknowledgement operation 510 are included in an Internal Acknowledgement In interface 512.
The Goods and Service Acknowledgement business object 120 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 5B, multiple outbound process agents can receive information from the Goods and Service Acknowledgement business object 120. A Notify of Invoicing Due from GSA to Supplier Invoice Processing asynchronous outbound process agent 520 can invoke a Notify of Invoicing Due operation 522. For example, the outbound process agent 520 can send a notification of an invoice due for items in a purchase order. The notification can be sent to the Supplier Invoice Processing process component 124. The Notify of Invoicing Due operation 522 is included in an Invoice Verification Out interface 524.
A Notify of Goods and Service Acknowledgement to Accounting asynchronous outbound process agent 526 can invoke a Notify of Goods and Service Acknowledgement operation 528. For example, the outbound process agent 526 can send a notification that goods or services were received. The notification can be sent to the Accounting process component 210. The Notify of Goods and Service Acknowledgement to Accounting asynchronous outbound process agent 526 can also invoke a Notify of Goods and Service Acknowledgement Cancellation operation 530. For example, the outbound process agent can cancel a notification that goods or services were received. The notification can be sent to the Accounting process component 210. The Notify of Goods and Service Acknowledgement operation 528 and the Notify of Goods and Service Acknowledgement Cancellation operation 530 are included in a Goods and Service Accounting Out interface 532.
FIGS. 6A, 6B and 6C are block diagrams collectively showing the Supplier Invoice Processing process component 124 (FIG. IB). 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 Purchase Order Processing process component 104, an Inbound Delivery Processing process component 601, the Goods and Service Acknowledgement process component 118, the Purchasing Contract Processing process component 114, the Internal Request Processing process component 140, a Customer Invoice Processing at Supplier process component 602, the Accounting process component 210, and a Due Item Processing process component 606. 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 Invoice Request operation 608 can send a request using a Maintain
Supplier Invoice Request asynchronous inbound process agent 610 to update the Supplier Invoice Request business object 126. For example, the operation 608 can send a request to update the Supplier Invoice Request business object 126 if input is received from the Purchase Order Processing process component 104, the Inbound Delivery Processing process component 601 , the Goods and Service Acknowledgement process component 118, or the Purchasing Contract Processing process component 1 14. The Maintain Invoice Request operation 608 is included in an Invoice Verification In interface 612.
A Create Invoice operation 614 can send a request using a Create Supplier Invoice based on Supplier Invoice Request asynchronous inbound process agent 616 to update the Supplier Invoice business object 128. For example, the operation 614 can send a supplier invoice request to update the Supplier Invoice business object 128 if input is received from the Internal Request Processing process component 140. The Create Invoice operation 614 is included in an Internal Invoicing In interface 618.
A Create Invoice operation 620 can send a request using a Create Supplier Invoice based on Invoice Request asynchronous inbound process agent 622 to update the Supplier Invoice business object 128. For example, the operation 620 can send a supplier invoice request to update the Supplier Invoice business object 128 if input is received from the Customer Invoice Processing at Supplier process component 602. The Create Invoice operation 620 is included in an Invoicing hi interface 624. The Supplier Invoice Request business object 126 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 6B, multiple outbound process agents can receive information from the Supplier Invoice Request business object 126.
A Notify of Contract Release from Supplier Invoice Request (SIR) to Purchasing Contract Processing asynchronous outbound process agent 626 can invoke a Notify of
Contract Release operation 628. For example, the outbound process agent 626 can send a notification of a released contract. The notification can be sent to the Purchasing Contract Processing process component 114. The Notify of Contract Release operation 628 is included in a Contract Release Out interface 630. A Notify of Invoiced Values from SIR to Purchase Order Processing asynchronous outbound process agent 632 can invoke a Notify of Invoiced Values operation 634. For example, the outbound process agent 632 can send a notification of invoiced values for a purchase order. The notification can be sent to the Purchase Order Processing process component 104. The Notify of Invoiced Values operation 634 is included in an Invoice Verification Out interface 636.
The Supplier Invoice business object 128 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 6C, multiple outbound process agents can receive information from the Supplier Invoice business object 128. A Notify of Supplier Invoice to Accounting asynchronous outbound process agent 644 can invoke a Notify of Invoice operation 646. For example, the outbound process agent 644 can send a notification of an invoice that was created for a particular supplier. The notification can be sent to the Accounting process component 210. The Notify of Supplier Invoice to Accounting asynchronous outbound process agent 644 can also invoke a Notify of Invoice Cancellation operation 648. For example, the outbound process agent 644 can send a notification of the cancellation of an invoice for a supplier. The notification can be sent to the Accounting process component 210. The Notify of Invoice operation 646 and the Notify of Invoice Cancellation operation 648 are included in an Invoice Accounting Out interface 650.
A Notify of Supplier Invoice to Due Item Processing asynchronous outbound process agent 652 can invoke a Notify of Invoice operation 654. For example, the outbound process agent 652 can send a notification of an invoice that was created for a particular supplier. The notification can be sent to the Due Item Processing process component 606. The Notify of Supplier Invoice to Due Item Processing asynchronous outbound process agent 652 can also invoke a Notify of Invoice Cancellation operation 656. For example, the outbound process agent 652 can send a notification of the cancellation of an invoice for a supplier. The notification can be sent to the Due Item Processing process component 606. The Notify of Invoice operation 654 and the Notify of Invoice Cancellation operation 656 are included in a Receivables Payables Out interface 658.
A Confirm Invoice to Supplier asynchronous outbound process agent 660 can invoke a Confirm Invoice operation 662. For example, the outbound process agent 660 can send a notification to confirm an invoice to a supplier. The notification can be sent to the Customer Invoice Processing at Supplier process component 602. The Confirm Invoice operation 662 is included in an Invoicing Out interface 664.
A Request Evaluated Receipt Settlement (ERS) Invoice to Supplier asynchronous outbound process agent 666 can invoke a Request ERS Invoice operation 668. For example, the outbound process agent 666 can send a notification of an ERS invoice. The notification can be sent to the Customer Invoice Processing at Supplier process component 602. The Request ERS Invoice operation 668 is included in an ERS Invoicing Out interface 670. FIGS. 7A, 7B and 7C are block diagrams collectively showing the RFQ Processing process component 132 (FIG. IB). 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 Purchase Request Processing process component 110, the Purchasing Contract Processing process component 114, an Opportunity/Customer Quote Processing at Supplier process component 702, and the Purchase Order Processing process component 104. 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 Request for Quote operation 704 can send a request for quote using a Maintain Request for Quote asynchronous inbound process agent 706 to update the Request for Quote business object 134. For example, the operation 704 can send a request for quote to update the Request for Quote business object 134 if input is received from the Purchase Request Processing process component 110. A Cancel Request for Quote operation 708 can send a cancellation request using the Maintain Request for Quote asynchronous inbound process agent 706 to update the Request for Quote business object 134. For example, the operation 708 can send a cancellation request to update the Request for Quote business object 134 if input is received from the Purchase Request Processing process component 110 or the Purchasing Contract Processing process component 114. The Maintain Request for Quote operation 704 and the Cancel Request for Quote operation 708 are included in a Request for Quote In interface 710.
A Maintain Supplier Quote Relations operation 712 can send a supplier quote using a Maintain Supplier Quote Relations based on Purchasing Contract asynchronous inbound process agent 714 to update the Supplier Quote business object 136. For example, the operation 712 can send a supplier quote to update the Supplier Quote business object 136 if input is received from the Purchasing Contract Processing process component 114. The Maintain Supplier Quote Relations operation 712 is included in a Purchasing Contract In interface 716. A Maintain Supplier Quote operation 718 can send a supplier quote using a Maintain Supplier Quote asynchronous inbound process agent 720 to update the Supplier Quote business object 136. For example, the operation 718 can send a supplier quote to update the Supplier Quote business object 136 if input is received from the Opportunity/Customer Quote Processing at Supplier process component 702. The Maintain Supplier Quote operation 718 is included in a Supplier Quote Processing In interface 722.
The Request for Quote business object 134 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 7B, multiple outbound process agents can receive information from the Request for Quote business object 134.
A Confirm Request for Quote asynchronous outbound process agent 724 can invoke a Confirm Request for Quote operation 726. For example, the outbound process agent 724 can send a notification to confirm a request for quote. The notification can be sent to the Purchase Request Processing process component 110 or the Purchasing Contract Processing process component 114. The Confirm Request for Quote operation 726 is included in a Request for Quote Out interface 728.
A Request Quote Maintenance from Request for Quote to Supplier asynchronous outbound process agent 730 can invoke a Request Quote Creation operation 732. For example, the outbound process agent 730 can send a notification of a request to create a quote. The notification can be sent to the Opportunity/Customer Quote Processing at
Supplier process component 702. The Request Quote Maintenance from Request for Quote to Supplier asynchronous outbound process agent 730 can also invoke a Notify of Request for Quote Cancellation operation 734. For example, the outbound process agent 730 can send a notification of a quote cancellation. The notification can be sent to the Opportunity/Customer Quote Processing at Supplier process component 702. The Request Quote Maintenance from Request for Quote to Supplier asynchronous outbound process agent 730 can also invoke a Notify of Request for Quote Change operation 736. For example, the outbound process agent 730 can send a notification of a quote change. The notification can be sent to the Opportunity/Customer Quote Processing at Supplier process component 702. The Request Quote Creation operation 732, the Notify of Request for Quote Cancellation operation 734, and the Notify of Request for Quote Change operation 736 are included in a Request Quote Processing Out interface 738.
The Supplier Quote business object .136 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 7C, multiple outbound process agents can receive information from the Supplier Quote business object 136.
A Request Purchase Order from Supplier Quote to Purchase Order Processing asynchronous outbound process agent 740 can invoke a Request Purchase Order from Winning Quote operation 742. For example, the outbound process agent 740 can send a notification of purchase order based on a winning quote. The notification can be sent to the Purchase Order Processing process component 104. The Request Purchase Order from Winning Quote operation 742 is included in a Purchasing Out interface 744.
A Request Contract from Supplier Quote to Purchasing Contract Processing asynchronous outbound process agent 746 can invoke a Request Contract from Winning Quote operation 748. For example, the outbound process agent 746 can send a contract maintenance request based on a winning quote associated with the contract. The notification can be sent to the Purchasing Contract Processing process component 114. The Request Contract from Winning Quote operation 748 is included in a Purchasing Contract Out interface 750. A Request Quote Maintenance from Supplier Quote to Supplier asynchronous outbound process agent 752 can invoke a Request Quote Change operation 754. For example, the outbound process agent 752 can send a notification of a quote change request. The notification can be sent to the Opportunity/Customer Quote Processing at Supplier process component 702. The Request Quote Change operation 754 is included in a Supplier Quote Processing Out interface 756.
A Notify of Quote Award from Supplier Quote to Supplier asynchronous outbound process agent 758 can invoke a Notify of Quote Award operation 760. For example, the outbound process agent 758 can send a notification of the quote award. The notification can be sent to the Opportunity/Customer Quote Processing at Supplier process component 702. The Notify of Quote Award operation 760 is included in the Supplier Quote Processing Out interface 756.
FIGS. 8 A and 8B are block diagrams collectively showing the Internal Request Processing process component 140 (FIG. IB). 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 Purchase Request Processing process component 110, the Goods and Service Acknowledgement process component 118, and the Supplier Invoice Processing process component 124. 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 Change Internal Request based on Procurement Progress operation 804 can send a request using a Change Internal Request based on Procurement Progress asynchronous inbound process agent 806 to update the Internal Request business object 142. For example, the operation 804 can send a request to update the Internal Request business object 142 if input is received from the Purchase Request Processing process component 110. The Change Internal Request based on Procurement Progress operation 804 is included in a Purchasing In interface 808. The Internal Request business object 142 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 8B, multiple outbound process agents can receive information from the Internal Request business object 142.
A Request Purchasing from Internal Request to Purchase Request Processing asynchronous outbound process agent 836 can invoke a Request Purchasing operation 838.
For example, the outbound process agent 836 can send a request purchasing notification. The notification can be sent to the Purchase Request Processing process component 110. The Request Purchasing operation 838 is included in a Purchasing Out interface 840.
A Request GSA from Internal Request to Goods and Service Acknowledgement asynchronous outbound process agent 842 can invoke a Request GSA based on Delivery Confirmation operation 844. For example, the outbound process agent 842 can send a notification of a request for a goods and service acknowledgement once the delivery of goods has occurred. The notification can be sent to the Goods and Service Acknowledgement process component 118. The Request GSA based on Delivery Confirmation operation 844 is included in an Internal Acknowledgement Out interface 846.
A Request Invoicing from Internal Request to Supplier Invoice Processing asynchronous outbound process agent 848 can invoke a Request Invoicing based on Invoice Acceptance operation 850. For example, the outbound process agent 848 can send a notification of a request for an invoice after acceptance of the invoice. The notification can be sent to the Supplier Invoice Processing process component 124. The Request Invoicing based on Invoice Acceptance operation 850 is included in an Internal Invoicing Out interface 852.
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 subcofnbination. 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; and computer software deployed on the computer system, the computer software implementing a plurality of service operations, the service operations comprising: a create purchase order confirmation operation operable to send a notification to create a confirmation of a purchase order; a change purchase order based on delivery values operation operable to send a notification to change the delivered quantity of a purchase order; a request purchase order change operation operable to request a change in a purchase order; a request purchase order cancellation operation operable to request to cancel a purchase order; a request purchase order creation operation operable to request to create a purchase order; . . a notify of purchase order operation operable to send a notification about a new purchase order to accounting; a notify of purchase order operation operable to send a notification about a new purchase order to external procurement trigger and response and to project processing; a maintain purchase request operation operable to send a notification to update an existing purchase order; a confirm purchase request operation operable to send a notification to confirm a new purchase order; a maintain purchasing contract release operation operable to send a notification to create or update purchasing contract releases; a notify of product catalog operation operable to send a notification about a new product catalog; a cancel goods and service acknowledgement operation operable to send a notification to cancel a goods and service acknowledgement; a create goods and service acknowledgement operation operable to send a notification to create a goods and service acknowledgement based on service from a supplier; a notify of invoicing due operation operable to send a notification about invoicing due based on a goods and service acknowledgement; a notify of goods and service acknowledgement operation operable to send a notification about a goods and service acknowledgement; a notify of invoice operation operable to send a notification to accounting about an invoice; a notify of invoice cancellation operation operable to send a notification about the cancellation of an invoice; a notify of invoice operation operable to send a notification to due item processing about an invoice; a notify of invoice cancellation operation operable to request to cancel an existing invoice; a confirm invoice operation operable to send a notification to confirm an invoice; a request ERS invoice operation operable to request an ERS invoice; a maintain supplier quote operation operable to send a notification to update a supplier quote; a request quote creation operation operable to request to create a supplier quote; a notify of request for quote cancellation operation operable to send a notification about the request to cancel a supplier quote; a notify of request for quote change operation operable to send a notification about the request to change a supplier quote; a request quote change operation operable to request to change a supplier quote; and a notify of quote award operation operable to send a notification about a quote award.
2. The system of claim 1, wherein the service operations further comprise: a create purchase order based on winning quote operation operable to send a notification to create a purchase order from an accepted supplier quote; a change purchase order based on invoiced values operation operable to send a notification to change a purchase order based on values in an invoice; a notify of invoicing due operation operable to send a notification about invoice an invoice due based on a purchase order that has been created, changed or cancelled; a change purchase request operation operable to send a notification to update an existing purchase request; a request RFQ (request for quote) execution operation operable to request a request for a quote execution; a maintain purchasing contract operation operable to send a notification to update a purchasing contract; a confirm request for quote operation operable to send a notification to confirm a request for quote for updating a purchasing contract; a request RFQ execution operation operable to request a request for a quote execution; a request RFQ cancellation operation operable to request a request for a quote cancellation; a notify of invoicing due operation operable to send a notification about an invoice due based on a purchasing contract that has been created, changed or cancelled; a confirm purchasing contract operation operable to send a notification to confirm a purchasing contract; a notify of goods and service acknowledgement cancellation operation operable to send a notification about the cancellation of a goods and service acknowledgement; a maintain invoice request operation operable to send a notification to update an invoice request; a create invoice operation operable to send a notification to create an invoice based on a customer request; a create invoice operation operable to send a notification to create an invoice based on a supplier request; a notify of contract release operation operable to send a notification about a released contract; a notify of invoiced values operation operable to send a notification about invoiced values; a maintain request for quote operation operable to send a notification to update a request for quote; a cancel request for quote operation operable to send a notification to cancel a request for quote; a maintain supplier quote relations operation operable to send a notification to update supplier quote relations; a confirm request for quote operation operable to send a notification to confirm a request for quote for updating purchase request processing and purchasing contract processing; a request purchase order from winning quote operation operable to request to create a purchase order based on a winning quote; a request contract from winning quote operation operable to request to create a contract based on a winning quote; a change internal request based on procurement progress operation operable to change an internal request based on progress in procurement; a request purchasing operation operable to request purchasing be made based on an internal request; a request GSA based on delivery confirmation operation operable to request a goods and service acknowledgement be created based on the confirmation of a delivery; and a request invoicing based on invoice acceptance operation operable to request an invoice be created for the complete open amount of requested goods or services.
3. The system of claim 1 or 2, wherein the service operations are grouped into service interfaces, the service interfaces comprising: a purchasing in interface that includes the create purchase order based on winning quote and the change purchase order based on delivery values service operations; an invoice verification in interface that includes the change purchase order based on invoiced values service operation; an ordering in interface that includes the create purchase order confirmation service operation; an invoice verification out interface that includes the notify of invoicing due service operation; an ordering out interface that includes the request purchase order change, the request purchase order cancellation, and the request purchase order creation service operations; a purchasing out interface that includes the notify of purchase order service operation; an order accounting out interface that includes the notify of purchase order service operation; a request for quote in interface that includes the change purchase request service operation; a purchasing in interface that includes the maintain purchase request service operation; a request for quote out interface that includes the request RFQ execution service operation; a purchasing out interface that includes the confirm purchase request service operation; a contract maintenance in interface that includes the maintain purchasing contract service operation; a request for quote in interface that includes the confirm request for quote service operation; a contract release in interface that includes the maintain purchasing contract release service operation; a request for quote out interface that includes the request RFQ execution and the request RFQ cancellation service operations; a product catalog authoring out interface that includes the notify of product catalog service operation; an invoice verification out interface that includes the notify of invoicing due service operation; a purchasing contract out interface that includes the confirm purchasing contract service operation; an internal acknowledgement in interface that includes the cancel goods and service acknowledgement and the create goods and service acknowledgement service operations; an invoice verification out interface that includes the notify of invoicing due service operation; a goods and service accounting out interface that includes the notify of goods and service acknowledgement and the notify of goods and service acknowledgement cancellation service operations; an invoice verification in interface that includes the maintain invoice request service operation; an internal invoicing in interface that includes the create invoice service operation; an invoicing in interface that includes the create invoice service operation; a contract release out interface that includes the notify of contract release service operation; an invoice verification out interface that includes the notify of invoiced values service operation; an invoice accounting out interface that includes the notify of invoice and the notify of invoice cancellation service operations; a receivables payables out interface that includes the notify of invoice and the notify of invoice cancellation service operations; an invoicing out interface that includes the confirm invoice service operation; an ERS invoicing out interface that includes the request ERS invoice service operation; a request for quote in interface that includes the maintain request for quote and the cancel request for quote service operations; a purchasing contract in interface that includes the maintain supplier quote relations service operation; a supplier quote processing in interface that includes the maintain supplier quote service operation; a request for quote out interface that includes the confirm request for quote service operation; a request quote processing out interface that includes the request quote creation, the notify of request for quote cancellation, and the notify of request for quote change service operations; a purchasing out interface that includes the request purchase order from winning quote service operation; a purchasing contract out interface that includes the request contract from winning quote service operation; a supplier quote processing out interface that includes the request quote change service operation; a supplier quote processing out interface that includes the notify of quote award service operation; a purchasing in interface that includes the change internal request based on procurement progress service operation; a purchasing out interface that includes the request purchasing service operation; an internal acknowledgement out interface that includes the request GSA based on delivery confirmation service operation; and an internal invoicing out interface that includes the request invoicing based on invoice acceptance service operation.
4. The system of any one of claims 1 to 3, wherein: the computer software implementing the create purchase order based on winning quote operation, the change purchase order based on delivery values operation, the change purchase order based on invoiced values operation, the create purchase order confirmation operation, the notify of invoicing due operation, the request purchase order change operation, the request purchase order cancellation operation, the request purchase order creation operation, the notify of purchase order operation, the notify of purchase order operation, the change purchase request operation, the maintain purchase request operation, the request RFQ execution operation, the confirm purchase request operation, the maintain purchasing contract operation, the confirm request for quote operation, the maintain purchasing contract release operation, the request RPQ execution operation, the request RFQ cancellation operation, the notify of product catalog operation, the notify of invoicing due operation, the confirm purchasing contract operation, the cancel goods and service acknowledgement operation, the create goods and service acknowledgement operation, the notify of invoicing due operation, the notify of goods and service acknowledgement operation, and the notify of goods and service acknowledgement cancellation operation is deployed on a first hardware platform; the computer software implementing the maintain invoice request operation, the create invoice operation, the create invoice operation, the notify of contract release operation, the notify of invoiced values operation, the notify of invoice operation, the notify of invoice cancellation operation, the notify of invoice operation, the notify of invoice cancellation operation, the confirm invoice operation, and the request ERS invoice operation is deployed on a second hardware platform; the computer software implementing the maintain request for quote operation, the cancel request for quote operation, the maintain supplier quote relations operation, the maintain supplier quote operation, the confirm request for quote operation, the request quote creation operation, the notify of request for quote cancellation operation, the notify of request for quote change operation, the request purchase order from winning quote operation, the request contract from winning quote operation, the request quote change operation, and the notify of quote award operation is deployed on a third hardware platform; and the computer software implementing the change internal request based on procurement progress operation, the request purchasing operation, the request GSA based on delivery confirmation operation, and the request invoicing based on invoice acceptance operation is deployed on a fourth hardware platform.
5. The system of claim 4, wherein each of the first through the fourth hardware platforms are distinct and separate from each other.
6. The system of any one of claims 1 to 3, wherein: the computer software implementing the create purchase order based on winning quote operation, the change purchase order based on delivery values operation, the change purchase order based on invoiced values operation, the create purchase order confirmation operation, the notify of invoicing due operation, the request purchase order change operation, the request purchase order cancellation operation, the request purchase order creation operation, the notify of purchase order operation, the notify of purchase order operation, the change purchase request operation, the maintain purchase request operation, the request RFQ execution operation, the confirm purchase request operation, the maintain purchasing contract operation, the confirm request for quote operation, the maintain purchasing contract release operation, the request RPQ execution operation, the request RFQ cancellation operation, the notify of product catalog operation, the notify of invoicing due operation, the confirm purchasing contract operation, the cancel goods and service acknowledgement operation, the create goods and service acknowledgement operation, the notify of invoicing due operation, the notify of goods and service acknowledgement operation, and the notify of goods and service acknowledgement cancellation operation is deployable on a first hardware platform; the computer software implementing the maintain invoice request operation, the create invoice operation, the create invoice operation, the notify of contract release operation, the notify of invoiced values operation, the notify of invoice operation, the notify of invoice cancellation operation, the notify of invoice operation, the notify of invoice cancellation operation, the confirm invoice operation, and the request ERS invoice operation is deployable on a second hardware platform; the computer software implementing the maintain request for quote operation, the cancel request for quote operation, the maintain supplier quote relations operation, the maintain supplier quote operation, the confirm request for quote operation, the request quote creation operation, the notify of request for quote cancellation operation, the notify of request for quote change operation, the request purchase order from winning quote operation, the request contract from winning quote operation, the request quote change operation, and the notify of quote award operation is deployable on a third hardware platform; and the computer software implementing the change internal request based on procurement progress operation, the request purchasing operation, the request GSA based on delivery confirmation operation, and the request invoicing based on invoice acceptance operation is deployable on a fourth hardware platform; and wherein: the first through the fourth hardware platforms are distinct and separate from each other.
7. The system of any one of claims 1 to 6, 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 purchase order processing process component handling purchase orders from purchasers to external suppliers requesting to deliver a specified quantity of goods, or to perform a specified service, within a specified time; a purchase request processing process component handling requests or instructions to the purchasing department to purchase specified goods or services in specified quantities within a specified time; a purchasing contract processing process component handling agreements between a purchaser and a supplier that cover the supply of goods or the performance of services at agreed conditions; a goods and service acknowledgement process component used by purchasers to report the receipt of goods and services, and by suppliers to report that they have delivered the requested goods or have rendered the requested services; a supplier invoice processing process component handling invoice documents that state the recipients' obligation to pay the suppliers for goods received or services rendered; a request for quote processing process component handling the description of materials and services that purchasers use to request responses from potential suppliers, and the resulting quotes from the suppliers offering to sell goods and services at a certain price; and an internal request processing process component handling requests made by employees of a company for the procurement of goods for their own use, or services for company use; and wherein: the purchase order processing process component implements the create purchase order based on winning quote, the change purchase order based on delivery values, the change purchase order based on invoiced values, the create purchase order confirmation, the notify of invoicing due, the request purchase order change, the request purchase order cancellation, the request purchase order creation, the notify of purchase order, and the notify of purchase order service operations; the purchase request processing process component implements the change purchase request, the maintain purchase request, the request RFQ execution, and the confirm purchase request service operations; the purchasing contract processing process component implements the maintain purchasing contract, the confirm request for quote, the maintain purchasing contract release, the request RFQ execution, the request RFQ cancellation, the notify of product catalog, the notify of invoicing due, and the confirm purchasing contract service operations; the goods and service acknowledgement process component implements the cancel goods and service acknowledgement, the create goods and service acknowledgement, the notify of invoicing due, the notify of goods and service acknowledgement, and the notify of goods and service acknowledgement cancellation service operations; the supplier invoice processing process component implements the maintain invoice request, the create invoice, the create invoice, the notify of contract release, the notify of invoiced values, the notify of invoice, the notify of invoice cancellation, the notify of invoice, the notify of invoice cancellation, the confirm invoice, and the request ERS invoice service operations; the request for quote processing process component implements the maintain request for quote, the cancel request for quote, the maintain supplier quote relations, the maintain supplier quote, the confirm request for quote, the request quote creation, the notify of request for quote cancellation, the notify of request for quote change, the request purchase order from winning quote, the request contract from winning quote, the request quote change, and the notify of quote award service operations; and the internal request processing process component implements the change internal request based on procurement progress, the request purchasing, the request GSA based on delivery confirmation, and the request invoicing based on invoice acceptance service operations.
8. The system of any one of claims 1 to 7, 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 purchasing deployment unit handling aspects of purchasing goods and services including purchase order processing, purchase request processing, purchasing contract processing, and goods and service acknowledgement; a supplier invoicing deployment unit handling invoice documents that state the recipients' obligation to pay the suppliers for goods received or services rendered; a request for quote processing deployment unit handling the description of materials and services that purchasers use to request responses from potential suppliers, and the resulting quotes from the suppliers offering to sell goods and services at a certain price; and a requisitioning deployment unit handling requests made by employees of a company for the procurement of goods for their own use, or services for company use; and wherein: the purchasing deployment unit implements the create purchase order based on winning quote, the change purchase order based on delivery values, the change purchase order based on invoiced values, the create purchase order confirmation, the notify of invoicing due, the request purchase order change, the request purchase order cancellation, the request purchase order creation, the notify of purchase order, the notify of purchase order, the change purchase request, the maintain purchase request, the request RFQ execution, the confirm purchase request, the maintain purchasing contract, the confirm request for quote, the maintain purchasing contract release, the request RFQ execution, the request RFQ cancellation, the notify of product catalog, the notify of invoicing due, the confirm purchasing contract, the cancel goods and service acknowledgement, the create goods and service acknowledgement, the notify of invoicing due, the notify of goods and service acknowledgement, and the notify of goods and service acknowledgement cancellation service operations; the supplier invoicing deployment unit implements the maintain invoice request, the create invoice, the create invoice, the notify of contract release, the notify of invoiced values, the notify of invoice, the notify of invoice cancellation, the notify of invoice, the notify of invoice cancellation, the confirm invoice, and the request ERS invoice service operations; the request for quote processing deployment unit implements the maintain request for quote, the cancel request for quote, the maintain supplier quote relations, the maintain supplier quote, the confirm request for quote, the request quote creation, the notify of request for quote cancellation, the notify of request for quote change, the request purchase order from winning quote, the request contract from winning quote, the request quote change, and the notify of quote award service operations; and the requisitioning deployment unit implements the change internal request based on procurement progress, the request purchasing, the request GSA based on delivery confirmation, and the request invoicing based on invoice acceptance service operations.
9. The system of any one of claims 1 to 8, further comprising: a repository of service descriptions, the repository including a standards-based description of each of the plurality of service operations.
10. 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 create purchase order confirmation operation operable to send a notification to create a confirmation of a purchase order; a change purchase order based on delivery values operation operable to send a notification to change the delivered quantity of a purchase order; a request purchase order change operation operable to request a change in a purchase order; a request purchase order cancellation operation operable to request to cancel a purchase order; a request purchase order creation operation operable to request to create a purchase order; . . . a notify of purchase order operation operable to send a notification about a new purchase order to accounting; a notify of purchase order operation operable to send a notification about a new purchase order to external procurement trigger and response and to project processing; a maintain purchase request operation operable to send a notification to update an existing purchase order; a confirm purchase request operation operable to send a notification to confirm a new purchase order; a maintain purchasing contract release operation operable to send a notification to create or update purchasing contract releases; a notify of product catalog operation operable to send a notification about a new product catalog; a cancel goods and service acknowledgement operation operable to send a notification to cancel a goods and service acknowledgement; a create goods and service acknowledgement operation operable to send a notification to create a goods and service acknowledgement based on service from a supplier; a notify of invoicing due operation operable to send a notification about invoicing due based on a goods and service acknowledgement; a notify of goods and service acknowledgement operation operable to send a notification about a goods and service acknowledgement; a notify of invoice operation operable to send a notification to accounting about an invoice; a notify of invoice cancellation operation operable to send a notification about the cancellation of an invoice; a notify of invoice operation operable to send a notification to due item processing about an invoice; a notify of invoice cancellation operation operable to request to cancel an existing invoice; a confirm invoice operation operable to send a notification to confirm an invoice; a request ERS invoice operation operable to request an ERS invoice; a maintain supplier quote operation operable to send a notification to update a supplier quote; a request quote creation operation operable to request to create a supplier quote; a notify of request for quote cancellation operation operable to send a notification about the request to cancel a supplier quote; a notify of request for quote change operation operable to send a notification about the request to change a supplier quote; a request quote change operation operable to request to change a supplier quote; and a notify of quote award operation operable to send a notification about a quote award.
11. The product of claim 10, wherein the service operations further comprise: a create purchase order based on winning quote operation operable to send a notification to create a purchase order from an accepted supplier quote; a change purchase order based on invoiced values operation operable to send a notification to change a purchase order based on values in an invoice; a notify of invoicing due operation operable to send a notification about invoice an invoice due based on a purchase order that has been created, changed or cancelled; a change purchase request operation operable to send a notification to update an existing purchase request; a request RFQ (request for quote) execution operation operable to request a request for a quote execution; a maintain purchasing contract operation operable to send a notification to update a purchasing contract; a confirm request for quote operation operable to send a notification to confirm a request for quote for updating a purchasing contract; a request RFQ execution operation operable to request a request for a quote execution; a request RFQ cancellation operation operable to request a request for a quote cancellation; a notify of invoicing due operation operable to send a notification about an invoice due based on a purchasing contract that has been created, changed or cancelled; a confirm purchasing contract operation operable to send a notification to confirm a purchasing contract; a notify of goods and service acknowledgement cancellation operation operable to send a notification about the cancellation of a goods and service acknowledgement; a maintain invoice request operation operable to send a notification to update an invoice request; a create invoice operation operable to send a notification to create an invoice based on a customer request; a create invoice operation operable to send a notification to create an invoice based on a supplier request; a notify of contract release operation operable to send a notification about a released contract; a notify of invoiced values operation operable to send a notification about invoiced values; a maintain request for quote operation operable to send a notification to update a request for quote; a cancel request for quote operation operable to send a notification to cancel a request for quote; a maintain supplier quote relations operation operable to send a notification to update supplier quote relations; a confirm request for quote operation operable to send a notification to confirm a request for quote for updating purchase request processing and purchasing contract processing; a request purchase order from winning quote operation operable to request to create a purchase order based on a winning quote; a request contract from winning quote operation operable to request to create a contract based on a winning quote; a change internal request based on procurement progress operation operable to change an internal request based on progress in procurement; a request purchasing operation operable to request purchasing be made based on an internal request; a request GSA based on delivery confirmation operation operable to request a goods and service acknowledgement be created based on the confirmation of a delivery; and a request invoicing based on invoice acceptance operation operable to request an invoice be created for the complete open amount of requested goods or services.
12. The product of claim 10 or 11, 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 purchase order processing process component handling purchase orders from purchasers to external suppliers requesting to deliver a specified quantity of goods, or to perform a specified service, within a specified time; a purchase request processing process component handling requests or instructions to the purchasing department to purchase specified goods or services in specified quantities within a specified time; a purchasing contract processing process component handling agreements between a purchaser and a supplier that cover the supply of goods or the performance of services at agreed conditions; a goods and service acknowledgement process component used by purchasers to report the receipt of goods and services, and by suppliers to report that they have delivered the requested goods or have rendered the requested services; a supplier invoice processing process component handling invoice documents that state the recipients' obligation to pay the suppliers for goods received or services rendered; a request for quote processing process component handling the description of materials and services that purchasers use to request responses from potential suppliers, and the resulting quotes from the suppliers offering to sell goods and services at a certain price; and an internal request processing process component handling requests made by employees of a company for the procurement of goods for their own use, or services for company use; and wherein: the purchase order processing process component implements the create purchase order based on winning quote, the change purchase order based on delivery values, the change purchase order based on invoiced values, the create purchase order confirmation, the notify of invoicing due, the request purchase order change, the request purchase order cancellation, the request purchase order creation, the notify of purchase order, and the notify of purchase order service operations; the purchase request processing process component implements the change purchase request, the maintain purchase request, the request RFQ execution, and the confirm purchase request service operations; the purchasing contract processing process component implements the maintain purchasing contract, the confirm request for quote, the maintain purchasing contract release, the request RFQ execution, the request RFQ cancellation, the notify of product catalog, the notify of invoicing due, and the confirm purchasing contract service operations; the goods and service acknowledgement process component implements the cancel goods and service acknowledgement, the create goods and service acknowledgement, the notify of invoicing due, the notify of goods and service acknowledgement, and the notify of goods and service acknowledgement cancellation service operations; the supplier invoice processing process component implements the maintain invoice request, the create invoice, the create invoice, the notify of contract release, the notify of invoiced values, the notify of invoice, the notify of invoice cancellation, the notify of invoice, the notify of invoice cancellation, the confirm invoice, and the request ERS invoice service operations; the request for quote processing process component implements the maintain request for quote, the cancel request for quote, the maintain supplier quote relations, the maintain supplier quote, the confirm request for quote, the request quote creation, the notify of request for quote cancellation, the notify of request for quote change, the request purchase order from winning quote, the request contract from winning quote, the request quote change, and the notify of quote award service operations; and the internal request processing process component implements the change internal request based on procurement progress, the request purchasing, the request GSA based on delivery confirmation, and the request invoicing based on invoice acceptance service operations.
13. The product of any one of claims 10 to 12, 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 purchasing deployment unit that includes a purchase order, a purchase order confirmation, a purchase request, a purchasing contract and a goods and service acknowledgement business object, wherein the purchase order business object represents a request from a purchaser to an external supplier to deliver a specified quantity of goods (or perform a specified service) within a specified time, the purchase order confirmation business object represents a confirmation from an external supplier to the request of a purchaser to deliver a specified quantity of material (or perform a specified service) at a specified price within a specified time, the purchase request business object represents a request or instruction to the purchasing department to purchase specified goods or services in specified quantities within a specified time, the purchasing contract business object represents an agreement between a purchaser and a supplier that covers the supply of goods or the performance of services at agreed conditions, and the goods and service acknowledgement business object represents a document reporting the receipt of goods and services; a supplier invoicing deployment unit that includes a supplier invoice request, an evaluated receipt settlement run, a supplier invoice and a supplier invoice verification exception business object, wherein the supplier invoice request business object represents a document that is sent to invoice verification advising that an invoice for specified quantities and prices is expected, the evaluated receipt settlement run business object represents supplier invoices of type credit memo, the supplier invoice business object represents a document that states the recipient's (usually the purchaser's) obligation to pay the supplier for goods received or services rendered, and the supplier invoice verification exception business object represents a group of related issues arising during a supplier invoice verification process; a request for quote processing deployment unit that includes a request for quote and a supplier quote business object, wherein the request for quote business object represents a request from a buyer to a bidder to submit a quote for a material or a service according to specified criteria, and the supplier quote business object represents a response to a request for quote, in which a supplier offers to sell materials and services according to the requested criteria; and a requisitioning deployment unit that includes an internal request business object, wherein the internal request business object represents a request for the procurement of goods or services.
14. The product of claim 12, 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.
15. The product of claim 14, wherein the deployment units comprise: a purchasing deployment unit that includes the purchase order processing, the purchase request processing, the purchasing contract processing, and the goods and service acknowledgement process components; wherein: a supplier invoicing deployment unit that includes the supplier invoice processing process component; a request for quote processing deployment unit that includes the request for quote processing process component; and a requisitioning deployment unit that includes the internal request processing process component.
16. The product of any one of claims 10 to 15, further comprising: a purchasing deployment unit that implements the create purchase order based on winning quote, the change purchase order based on delivery values, the change purchase order based on invoiced values, the create purchase order confirmation, the notify of invoicing due, the request purchase order change, the request purchase order cancellation, the request purchase order creation, the notify of purchase order, the notify of purchase order, the change purchase request, the maintain purchase request, the request RFQ execution, the confirm purchase request, the maintain purchasing contract, the confirm request for quote, the maintain purchasing contract release, the request RFQ execution, the request RFQ cancellation, the notify of product catalog, the notify of invoicing due, the confirm purchasing contract, the cancel goods and service acknowledgement, the create goods and service acknowledgement, the notify of invoicing due, the notify of goods and service acknowledgement, and the notify of goods and service acknowledgement cancellation service operations; a supplier invoicing deployment unit that implements the maintain invoice request, the create invoice, the create invoice, the notify of contract release, the notify of invoiced values, the notify of invoice, the notify of invoice cancellation, the notify of invoice, the notify of invoice cancellation, the confirm invoice, and the request ERS invoice service operations; a request for quote processing deployment unit that implements the maintain request for quote, the cancel request for quote, the maintain supplier quote relations, the maintain supplier quote, the confirm request for quote, the request quote creation, the notify of request for quote cancellation, the notify of request for quote change, the request purchase order from winning quote, the request contract from winning quote, the request quote change, and the notify of quote award service operations; and a requisitioning deployment unit that implements the change internal request based on procurement progress, the request purchasing, the request GSA based on delivery confirmation, and the request invoicing based on invoice acceptance service operations.
17. The product of claim 12, wherein: the purchase order processing process component includes a purchase order business object and a purchase order confirmation business object, wherein the purchase order business object is responsible for the request from a purchaser to an external supplier to deliver a specified quantity of goods (or perform a specified service) within a specified time, and the purchase order confirmation business object is responsible for the confirmation from an external supplier to the request of a purchaser to deliver a specified quantity of material (or perform a specified service) at a specified price within a specified time; the purchase request processing process component includes a purchase request business object, wherein the purchase request business object is responsible for the request or instruction to the purchasing department to purchase specified goods or services in specified quantities within a specified time; the purchasing contract processing process component includes a purchasing contract business object, wherein the purchasing contract business object is responsible for the agreement between a purchaser and a supplier that covers the supply of goods or the performance of services at agreed conditions; the goods and service acknowledgement process component includes a goods and service acknowledgement business object, wherein the goods and service acknowledgement business object is responsible for the document reporting the receipt of goods and services; the supplier invoice processing process component includes a supplier invoice request business object, a evaluated receipt settlement run business object, a supplier invoice business object, and a supplier invoice verification exception business object, wherein the supplier invoice request business object is responsible for the document that is sent to invoice verification advising that an invoice for specified quantities and prices is expected, the evaluated receipt settlement run business object is responsible for supplier invoices of type credit memo, the supplier invoice business object is responsible for the document that states the recipient's (usually the purchaser's) obligation to pay the supplier for goods received or services rendered, and the supplier invoice verification exception business object is responsible for a group of related issues arising during a supplier invoice verification process; the request for quote processing process component includes a request for quote business object and a supplier quote business object, wherein the business object is responsible for the request from a buyer to a bidder to submit a quote for a material or a service according to specified criteria, and the business object is responsible for the response to a request for quote, in which a supplier offers to sell materials and services according to the requested criteria; and the internal request processing process component includes a internal request business object, wherein the business object is responsible for the request for the procurement of goods or services.
18. The product of claim 12, 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.
19. The product of claim 18, wherein the business objects comprise a business process object.
20. The product of claim 18 or 19, wherein: none of the business objects included in any one of the process components is included in any of the other process components.
21. The product of any one of claims 10 to 20, 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 the 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.
22. A method for providing services from a computer system having supplier relationship management functionality, the method comprising: providing services through the sending of messages, the messages including: a notification to create a purchase order from an accepted supplier quote; a notification to change the delivered quantity of a purchase order; a notification to change a purchase order based on values in an invoice; a notification to create a confirmation of a purchase order; a notification about an invoice due based on a purchase order that has been created, changed or cancelled; a notification requesting a change in a purchase order; a notification requesting to cancel a purchase order; a notification requesting to create a purchase order; a notification about a new purchase order to external procurement trigger and response and to project processing; a notification about a new purchase order to accounting; a notification to update an existing purchase request; a notification to update an existing purchase order; a notification requesting a request for a quote execution; a notification to confirm a new purchase order; a notification to update a purchasing contract; a notification to confirm a request for quote for updating a purchasing contract; a notification to create or update purchasing contract releases; a notification requesting a request for a quote execution; a notification requesting a request for a quote cancellation; a notification about a new product catalog; a notification about an invoice due based on a purchasing contract that has been created, changed or cancelled; a notification to confirm a purchasing contract; a notification to cancel a goods and service acknowledgement; a notification to create a goods and service acknowledgement based on an internal request; a notification about an invoicing due based on a goods and service acknowledgement; a notification about a goods and service acknowledgement; a notification about the cancellation of a goods and service acknowledgement; a notification to update an invoice request; a notification to create an invoice based on a customer request; a notification to create an invoice based on a supplier request; a notification about a released contract; a notification about invoiced values; a notification to accounting about an invoice; a notification about the cancellation of an invoice; a notification to due item processing about an invoice; a notification requesting to cancel an existing invoice; a notification to confirm an invoice; a notification requesting an ERS invoice; a notification to update a request for quote; a notification to cancel a request for quote; a notification to update supplier quote relations; a notification to update a supplier quote; a notification to confirm a request for quote for updating purchase request processing and purchasing contract processing; a notification requesting to create a supplier quote; a notification about the request to cancel a supplier quote; a notification about the request to change a supplier quote; a notification requesting to create a purchase order based on a winning quote; a notification requesting to create a contract based on a winning quote; a notification requesting to change a supplier quote; a notification about a quote award; a notification to change an internal request based on progress in procurement; a notification requesting purchasing be made based on an internal request; a notification requesting a goods and service acknowledgement be created based on the confirmation of a delivery; and a notification requesting an invoice be created for the complete open amount of requested goods or services.
PCT/EP2007/002845 2006-03-30 2007-03-29 Providing supplier relationship management software application as enterprise WO2007112959A2 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/396,258 2006-03-30
US11/396,258 US8326702B2 (en) 2006-03-30 2006-03-30 Providing supplier relationship management software application as enterprise services

Publications (1)

Publication Number Publication Date
WO2007112959A2 true WO2007112959A2 (en) 2007-10-11

Family

ID=38255117

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2007/002845 WO2007112959A2 (en) 2006-03-30 2007-03-29 Providing supplier relationship management software application as enterprise

Country Status (2)

Country Link
US (1) US8326702B2 (en)
WO (1) WO2007112959A2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111612556A (en) * 2019-02-22 2020-09-01 北京致医健康信息技术有限公司 Method and device for purchasing medicine

Families Citing this family (95)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2005122078A2 (en) 2004-06-04 2005-12-22 Sap Ag Consistent set of interfaces derived from a business object model
US8606723B2 (en) 2004-06-04 2013-12-10 Sap Ag Consistent set of interfaces derived from a business object model
WO2006038924A2 (en) 2004-06-18 2006-04-13 Sap Ag Consistent set of interfaces derived from a business object model
US8744937B2 (en) 2005-02-25 2014-06-03 Sap Ag Consistent set of interfaces derived from a business object model
US8380553B2 (en) 2005-12-30 2013-02-19 Sap Ag Architectural design for plan-driven procurement application software
US8321831B2 (en) 2005-12-30 2012-11-27 Sap Ag Architectural design for internal projects application software
US8676617B2 (en) 2005-12-30 2014-03-18 Sap Ag Architectural design for self-service procurement application software
US8370794B2 (en) 2005-12-30 2013-02-05 Sap Ag Software model process component
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
US8448137B2 (en) 2005-12-30 2013-05-21 Sap Ag Software model integration scenarios
US8402426B2 (en) 2005-12-30 2013-03-19 Sap Ag Architectural design for make to stock application software
US8396731B2 (en) 2005-12-30 2013-03-12 Sap Ag Architectural design for service procurement application software
US8316344B2 (en) 2005-12-30 2012-11-20 Sap Ag Software model deployment units
US8396749B2 (en) 2006-03-30 2013-03-12 Sap Ag Providing customer relationship management application as enterprise services
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
US8326702B2 (en) 2006-03-30 2012-12-04 Sap Ag Providing supplier relationship management software application as enterprise services
US8438119B2 (en) 2006-03-30 2013-05-07 Sap Ag Foundation layer for services based enterprise software architecture
US8374931B2 (en) 2006-03-31 2013-02-12 Sap Ag Consistent set of interfaces derived from a business object model
US8321832B2 (en) 2006-03-31 2012-11-27 Sap Ag Composite application modeling
US8924269B2 (en) 2006-05-13 2014-12-30 Sap Ag Consistent set of interfaces derived from a business object model
US8392364B2 (en) 2006-07-10 2013-03-05 Sap Ag Consistent set of interfaces derived from a business object model
US8566193B2 (en) 2006-08-11 2013-10-22 Sap Ag Consistent set of interfaces derived from a business object model
US8571961B1 (en) 2006-09-28 2013-10-29 Sap Ag Managing consistent interfaces for financial business objects across heterogeneous systems
US9679318B1 (en) * 2007-05-24 2017-06-13 Amdocs Software Systems Limited System, method, and computer program product for updating billing parameters utilizing a bill replica
US8447657B2 (en) 2007-12-31 2013-05-21 Sap Ag Architectural design for service procurement application 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
US8413165B2 (en) 2008-03-31 2013-04-02 Sap Ag Managing consistent interfaces for maintenance order business objects across heterogeneous systems
US8577991B2 (en) 2008-03-31 2013-11-05 Sap Ag Managing consistent interfaces for internal service request business objects across heterogeneous systems
US8433585B2 (en) 2008-03-31 2013-04-30 Sap Ag 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
US8423418B2 (en) 2008-03-31 2013-04-16 Sap Ag Managing consistent interfaces for business objects across heterogeneous systems
US8930248B2 (en) 2008-03-31 2015-01-06 Sap Se Managing consistent interfaces for supply network business objects across heterogeneous systems
US8473317B2 (en) 2008-03-31 2013-06-25 Sap Ag Managing consistent interfaces for service part business objects across heterogeneous systems
US8364715B2 (en) 2008-03-31 2013-01-29 Sap Ag Managing consistent interfaces for automatic identification label business objects across heterogeneous systems
US8370233B2 (en) 2008-03-31 2013-02-05 Sap Ag Managing consistent interfaces for business objects across heterogeneous systems
US20090326988A1 (en) 2008-06-26 2009-12-31 Robert Barth Managing consistent interfaces for business objects across heterogeneous systems
US8566185B2 (en) 2008-06-26 2013-10-22 Sap Ag Managing consistent interfaces for financial instrument business objects across heterogeneous systems
US8671064B2 (en) 2008-06-26 2014-03-11 Sap Ag Managing consistent interfaces for supply chain management business objects across heterogeneous systems
US8645228B2 (en) 2008-06-26 2014-02-04 Sap Ag Managing consistent interfaces for business objects across heterogeneous systems
US8374896B2 (en) 2008-09-18 2013-02-12 Sap Ag Architectural design for opportunity management application software
US8352338B2 (en) 2008-09-18 2013-01-08 Sap Ag Architectural design for time recording application software
US8818884B2 (en) 2008-09-18 2014-08-26 Sap Ag Architectural design for customer returns handling application software
US8401928B2 (en) 2008-09-18 2013-03-19 Sap Ag Providing supplier relationship management software application as enterprise services
US8380549B2 (en) * 2008-09-18 2013-02-19 Sap Ag Architectural design for embedded support application software
US8386325B2 (en) 2008-09-18 2013-02-26 Sap Ag Architectural design for plan-driven procurement application software
US8595077B2 (en) 2008-09-18 2013-11-26 Sap Ag Architectural design for service request and order management application software
US8463666B2 (en) 2008-11-25 2013-06-11 Sap Ag Managing consistent interfaces for merchandise and assortment planning business objects across heterogeneous systems
US8577760B2 (en) 2008-11-25 2013-11-05 Sap Ag Managing consistent interfaces for tax authority business objects across heterogeneous systems
US8738476B2 (en) 2008-12-03 2014-05-27 Sap Ag Architectural design for selling standardized services 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
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
US20100250445A1 (en) * 2009-03-25 2010-09-30 Solheim Robert J Commitment tracking system
US20110077999A1 (en) * 2009-09-30 2011-03-31 Sap Ag Managing consistent interfaces for retail event business objects across heterogeneous systems
US8396751B2 (en) 2009-09-30 2013-03-12 Sap Ag Managing consistent interfaces for merchandising business objects across heterogeneous systems
US20110276443A1 (en) * 2010-05-05 2011-11-10 Oracle International Corporation Multi-resource services
US8412603B2 (en) 2010-06-15 2013-04-02 Sap Ag Managing consistent interfaces for currency conversion and date and time business objects across heterogeneous systems
US8732083B2 (en) 2010-06-15 2014-05-20 Sap Ag Managing consistent interfaces for number range, number range profile, payment card payment authorisation, and product template template business objects across heterogeneous systems
US8370272B2 (en) 2010-06-15 2013-02-05 Sap Ag Managing consistent interfaces for business document message monitoring view, customs arrangement, and freight list 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
US8364608B2 (en) 2010-06-15 2013-01-29 Sap Ag Managing consistent interfaces for export declaration and export declaration request business objects across heterogeneous systems
US8515794B2 (en) 2010-06-15 2013-08-20 Sap Ag Managing consistent interfaces for employee time event and human capital management view of payroll process business objects across heterogeneous systems
US8417588B2 (en) 2010-06-15 2013-04-09 Sap Ag Managing consistent interfaces for goods tag, production bill of material hierarchy, and release order template business objects across heterogeneous systems
US8666845B2 (en) 2011-07-28 2014-03-04 Sap Ag Managing consistent interfaces for a customer requirement business object across heterogeneous systems
US8725654B2 (en) 2011-07-28 2014-05-13 Sap Ag Managing consistent interfaces for employee data replication business objects across heterogeneous systems
US8521838B2 (en) 2011-07-28 2013-08-27 Sap Ag Managing consistent interfaces for communication system and object identifier mapping 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
US8601490B2 (en) 2011-07-28 2013-12-03 Sap Ag Managing consistent interfaces for business rule business object across heterogeneous systems
US8560392B2 (en) 2011-07-28 2013-10-15 Sap Ag Managing consistent interfaces for a point of sale transaction business object across heterogeneous systems
US20140012706A1 (en) * 2011-12-22 2014-01-09 Zuora, Inc. Methods and systems for processing orders in a subscription based billing system
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
US8984050B2 (en) 2012-02-16 2015-03-17 Sap Se Consistent interface for sales territory message type set 2
US9232368B2 (en) 2012-02-16 2016-01-05 Sap Se Consistent interface for user feed administrator, user feed event link and user feed settings
US8756274B2 (en) 2012-02-16 2014-06-17 Sap Ag Consistent interface for sales territory message type set 1
US9237425B2 (en) 2012-02-16 2016-01-12 Sap Se Consistent interface for feed event, feed event document and feed event type
US8756135B2 (en) 2012-06-28 2014-06-17 Sap Ag Consistent interface for product valuation data and product valuation level
US9246869B2 (en) 2012-06-28 2016-01-26 Sap Se Consistent interface for opportunity
US8949855B2 (en) 2012-06-28 2015-02-03 Sap Se Consistent interface for address snapshot and approval process definition
US8521621B1 (en) 2012-06-28 2013-08-27 Sap Ag Consistent interface for inbound delivery request
WO2014000200A1 (en) 2012-06-28 2014-01-03 Sap Ag Consistent interface for document output request
US9367826B2 (en) 2012-06-28 2016-06-14 Sap Se Consistent interface for entitlement product
US8615451B1 (en) 2012-06-28 2013-12-24 Sap Ag Consistent interface for goods and activity confirmation
US9400998B2 (en) 2012-06-28 2016-07-26 Sap Se Consistent interface for message-based communication arrangement, organisational centre replication request, and payment schedule
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
IN2013MU03241A (en) * 2013-11-15 2015-08-21 Tata Consultancy Services Ltd
US10963952B2 (en) 2018-12-03 2021-03-30 Sap Se Augmented reality-based real estate property analysis
US11232113B2 (en) 2019-03-12 2022-01-25 Sap Se Metadata-driven data maintenance

Family Cites Families (358)

* Cited by examiner, † Cited by third party
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
US5460371A (en) * 1993-05-19 1995-10-24 Kabushiki Kaisha Endo Seisakusho Golf club wood head
AU6019994A (en) 1993-09-13 1995-04-03 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
EP1105826A1 (en) 1998-08-27 2001-06-13 Upshot Corporation A method and apparatus for network-based sales force management
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
US6167564A (en) 1998-09-17 2000-12-26 Unisys Corp. Software system development framework
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
US7100195B1 (en) 1999-07-30 2006-08-29 Accenture Llp Managing user information on an e-commerce system
US6601233B1 (en) 1999-07-30 2003-07-29 Accenture Llp Business components framework
WO2001016850A2 (en) 1999-08-31 2001-03-08 Accenture Llp A system, method and article of manufacture for organizing and managing transaction-related tax information
US6640238B1 (en) 1999-08-31 2003-10-28 Accenture Llp Activity component in a presentation services patterns environment
US6601234B1 (en) 1999-08-31 2003-07-29 Accenture Llp Attribute dictionary in a business logic services environment
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
US6636242B2 (en) 1999-08-31 2003-10-21 Accenture Llp View configurer in a presentation services patterns environment
US7139999B2 (en) 1999-08-31 2006-11-21 Accenture Llp Development architecture framework
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
US20110191747A1 (en) 1999-10-05 2011-08-04 Borland Software Corporation Supporting and deploying distributed computing components
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
AU780914B2 (en) 1999-12-10 2005-04-28 Innovation Group/Mtw, Inc., The A method of component-based system development
US6764009B2 (en) 2001-05-30 2004-07-20 Lightwaves Systems, Inc. Method for tagged bar code data interchange
US7798417B2 (en) 2000-01-03 2010-09-21 Snyder David M Method for 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
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
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
US6934532B2 (en) 2000-02-09 2005-08-23 Apriva, Inc. Communication systems, components, and methods operative 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
US20010034880A1 (en) 2000-03-02 2001-10-25 Jonathan Dzoba Configurable debug system using source and data objects
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
WO2001082071A1 (en) 2000-04-21 2001-11-01 Togethersoft Corporation Methods and systems for supporting and deploying distributed computing components
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
TW541483B (en) 2000-10-27 2003-07-11 Manugistics Inc System and method for ensuring order fulfillment
WO2002037394A2 (en) 2000-10-30 2002-05-10 Tririga, Inc. sUSINESS ASSET MANAGEMENT SYSTEM
WO2002041197A1 (en) 2000-11-15 2002-05-23 Virtual Supply Logic Pty Limited 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
US20020103660A1 (en) 2000-11-30 2002-08-01 Kurt Cramon Generic transaction server
US7020869B2 (en) 2000-12-01 2006-03-28 Corticon Technologies, Inc. Business rules user interface for development of adaptable enterprise applications
WO2002096008A2 (en) 2000-12-22 2002-11-28 Aidentity Matrix Medical, Inc. 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')
US7324966B2 (en) 2001-01-22 2008-01-29 W.W. Grainger Method for fulfilling an order in an integrated supply chain management system
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
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
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
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
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
US7120896B2 (en) 2001-10-31 2006-10-10 Vitria Technology, Inc. Integrated business process modeling environment and models created thereby
US20020198828A1 (en) 2001-04-03 2002-12-26 Bottomline Technologies, Inc. Modular business transactions platform
US20020198798A1 (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
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
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
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
JP2003167445A (en) * 2001-11-30 2003-06-13 Konica Corp Image forming apparatus
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
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
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
US7424701B2 (en) 2002-02-12 2008-09-09 Sandpiper Software, Inc. Method and apparatus for 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
US7386833B2 (en) 2002-09-04 2008-06-10 Mentor Graphics Corp. Polymorphic computational system and method in signals intelligence analysis
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
US7219107B2 (en) 2002-12-23 2007-05-15 Sap Ag Collaborative information spaces
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
EP1469411A1 (en) 2003-04-18 2004-10-20 Matsushita Electric Industrial Co., Ltd. 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
CN1791861A (en) 2003-05-16 2006-06-21 Sap股份公司 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
US20050240592A1 (en) 2003-08-27 2005-10-27 Ascential Software Corporation Real time data integration for supply chain management
US8060553B2 (en) 2003-08-27 2011-11-15 International Business Machines Corporation Service oriented architecture for a transformation function in a data integration platform
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
US20070197877A1 (en) 2004-01-05 2007-08-23 Stefaan Decorte 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
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
US8046273B2 (en) 2004-03-08 2011-10-25 Sap Ag System and method for purchase order creation, procurement, and controlling
US20050203760A1 (en) 2004-03-15 2005-09-15 Microsoft Corporation Project time and expense
US7793258B2 (en) 2004-03-15 2010-09-07 Ramco Systems Limited Software development using visual interfaces
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
US9026455B2 (en) 2004-05-14 2015-05-05 Sap Ag Methods and systems for processing stock in a storage facility
US7665064B2 (en) 2004-05-14 2010-02-16 Gt Software, Inc. Systems and methods for web service function, definition, implementation, and/or execution
US20050289079A1 (en) 2004-05-17 2005-12-29 Shimon Systems, Inc. Systems and methods for biometric identification
US8554805B2 (en) 2004-05-17 2013-10-08 Sap Ag Methods and systems for importing source data
US20050262453A1 (en) 2004-05-21 2005-11-24 Luca Massasso Modular data management system
WO2005122078A2 (en) 2004-06-04 2005-12-22 Sap Ag Consistent set of interfaces derived from a business object model
CN101031882B (en) 2004-06-08 2010-09-08 达尔特设备互操作有限公司 Architecture, apparatus and method for device team recruitment and content renditioning for universal device interoperability platform
US20080167916A1 (en) 2004-06-14 2008-07-10 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
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
US7565640B2 (en) 2004-10-01 2009-07-21 Microsoft Corporation Framework for seamlessly authoring and editing workflows at design and runtime
US20060074704A1 (en) 2004-10-01 2006-04-06 Microsoft Corporation Framework to model cross-cutting behavioral concerns in the workflow domain
US7631291B2 (en) 2004-10-01 2009-12-08 Microsoft Corporation Declarative representation for an extensible workflow model
US7451432B2 (en) 2004-10-01 2008-11-11 Microsoft Corporation Transformation of componentized and extensible workflow to a declarative format
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
US20060274720A1 (en) 2004-11-09 2006-12-07 Andrew Adams 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
US7657406B2 (en) 2005-06-09 2010-02-02 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
US7693586B2 (en) 2005-09-02 2010-04-06 Sap Ag Process model transformation for event-based coordination of composite applications
EP1934905A4 (en) 2005-09-02 2010-08-25 Ecmarket Inc Method and system for exchanging business documents
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
EP1806686A1 (en) 2005-12-05 2007-07-11 Sap Ag Restriction of the number of locations
EP1798675A1 (en) 2005-12-05 2007-06-20 Sap Ag Consolidation of third party order processing items
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
US8688495B2 (en) 2005-12-30 2014-04-01 Sap Ag Architectural design for time recording application software
US20070156428A1 (en) 2005-12-30 2007-07-05 Brecht-Tillinger Karin K System and method for internally ordering goods and services
US8676617B2 (en) 2005-12-30 2014-03-18 Sap Ag Architectural design for self-service procurement application software
US8327319B2 (en) * 2005-12-30 2012-12-04 Sap Ag Software model process interaction
US20080275713A9 (en) 2005-12-30 2008-11-06 Shai Alfandary Architectural design for physical inventory application software
US8522194B2 (en) 2005-12-30 2013-08-27 Sap Ag Software modeling
US20070164849A1 (en) 2005-12-30 2007-07-19 Tilmann Haeberle Enterprise software with contextual support
US8396731B2 (en) 2005-12-30 2013-03-12 Sap Ag Architectural design for service procurement application software
US8510183B2 (en) 2005-12-30 2013-08-13 Sap Ag System and method for distributed and integrated asset management
US8407664B2 (en) * 2005-12-30 2013-03-26 Sap Ag Software model business objects
US8370794B2 (en) * 2005-12-30 2013-02-05 Sap Ag Software model process component
US8316344B2 (en) 2005-12-30 2012-11-20 Sap Ag Software model deployment units
US20070156550A1 (en) 2005-12-30 2007-07-05 Der Emde Martin V Architectural design for cash and liquidity management application software
US20070174145A1 (en) 2005-12-30 2007-07-26 Stephan Hetzer Controlling logistics execution in a computer application
US8326703B2 (en) 2005-12-30 2012-12-04 Sap Ag Architectural design for product catalog management application software
US8660904B2 (en) 2005-12-30 2014-02-25 Sap Ag Architectural design for service request and order management application software
US20070156500A1 (en) 2005-12-30 2007-07-05 Wilfried Merkel Architectural design for sell from stock application software
US8380553B2 (en) 2005-12-30 2013-02-19 Sap Ag Architectural design for plan-driven procurement application software
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
US8396749B2 (en) 2006-03-30 2013-03-12 Sap Ag Providing customer relationship management 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
US8396761B2 (en) 2006-03-30 2013-03-12 Sap Ag Providing product catalog software application as enterprise services
US20070233539A1 (en) 2006-03-30 2007-10-04 Philipp Suenderhauf Providing human capital management software application as enterprise services
US8442850B2 (en) 2006-03-30 2013-05-14 Sap Ag Providing accounting software application as enterprise services
US8326702B2 (en) 2006-03-30 2012-12-04 Sap Ag Providing supplier relationship management software 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
US8924269B2 (en) 2006-05-13 2014-12-30 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
US7644390B2 (en) 2006-08-14 2010-01-05 Payman Khodabandehloo Design tool and methodology for enterprise software applications
WO2008045941A1 (en) 2006-10-10 2008-04-17 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
US20090037287A1 (en) 2007-07-31 2009-02-05 Ahmad Baitalmal Software Marketplace and Distribution System
US20090037492A1 (en) 2007-07-31 2009-02-05 Ahmad Baitalmal Framework for Synchronizing Applications
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
US8386325B2 (en) 2008-09-18 2013-02-26 Sap Ag Architectural design for plan-driven procurement application software
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
US8321306B2 (en) 2008-12-03 2012-11-27 Sap Ag Architectural design for selling project-based services application software

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111612556A (en) * 2019-02-22 2020-09-01 北京致医健康信息技术有限公司 Method and device for purchasing medicine

Also Published As

Publication number Publication date
US20070265860A1 (en) 2007-11-15
US8326702B2 (en) 2012-12-04

Similar Documents

Publication Publication Date Title
US8326702B2 (en) Providing supplier relationship management software application as enterprise services
US8401928B2 (en) Providing supplier relationship management software application as enterprise services
US8396749B2 (en) Providing customer relationship management application as enterprise services
US8396761B2 (en) Providing product catalog software application as enterprise services
US20070233575A1 (en) Architectural design for strategic sourcing application software
US8396731B2 (en) Architectural design for service procurement application software
US8380553B2 (en) Architectural design for plan-driven procurement application software
US8688495B2 (en) Architectural design for time recording application software
US8359218B2 (en) Computer readable medium for implementing supply chain control using service-oriented methodology
US8442850B2 (en) Providing accounting software application as enterprise services
US8595077B2 (en) Architectural design for service request and order management application software
US8538864B2 (en) Providing payment software application as enterprise services
US8312416B2 (en) Software model business process variant types
US8326703B2 (en) Architectural design for product catalog management application software
US20070156500A1 (en) Architectural design for sell from stock application software
US20100070336A1 (en) Providing Customer Relationship Management Application as Enterprise Services
US20070156499A1 (en) Architectural design for self-service procurement application software
US20070156476A1 (en) Architectural design for service request and order management application software
US20070168240A1 (en) Architectural design for make to stock application software
US20100153158A1 (en) Providing project management software application as enterprise services
US20100070318A1 (en) Providing logistics execution application as enterprise services
US8311904B2 (en) Architectural design for intra-company stock transfer 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: 07723787

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07723787

Country of ref document: EP

Kind code of ref document: A2