WO2007077018A1 - Software model business objects - Google Patents
Software model business objects Download PDFInfo
- Publication number
- WO2007077018A1 WO2007077018A1 PCT/EP2006/012621 EP2006012621W WO2007077018A1 WO 2007077018 A1 WO2007077018 A1 WO 2007077018A1 EP 2006012621 W EP2006012621 W EP 2006012621W WO 2007077018 A1 WO2007077018 A1 WO 2007077018A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- business
- process components
- components
- process component
- component
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/10—Requirements analysis; Specification techniques
Definitions
- the subject matter of this patent applications relates to modeling software systems, and more particularly to modeling the composition and interaction of components in a software system.
- 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. Typical software modeling systems may not be able to reduce this complexity for end users.
- a systems administrator may need a high-level technical understanding of how various software modules are installed on physical hardware, such as a server device or a network, and how those software modules interact with other software modules in the system.
- a person responsible for configuring the software may need a high-level functional understanding of the operations that each functional component provides.
- An application designer may need a low-level technical understanding of the various software interfaces that portions of the application require or implement.
- an application developer may need a detailed understanding of the interfaces and functionality he or she is implementing in relation to the remainder of the system.
- Each business object is operable to encapsulate business data and can be associated with exactly one process component.
- Each of the process components characterizes software implementing a respective and distinct process and defines a respective at least one service interface for communicating and interacting with business objects in other process components. Moreover, all communication and interaction between process components takes place through the respective interfaces of the process components. Additionally, the interactions among business objects in different deployment units occur solely via the process component interfaces.
- the process components can characterize inbound operations and/or outbound operations.
- the inbound operations handle incoming messages associated with a modification of reading of data encapsulated in a business object associated with the process component.
- the outbound operations handle outgoing messages associated with a modification or reading of data encapsulated in at least one business object associated with another process component.
- the process components may also include process agents that characterize operations that enable communications between a business object associated with the process component and a business object associated with any other process component.
- the process agents are operable to enable communication through the service interface of its respective process component.
- An inbound agent can characterize an inbound operation to handle incoming messages.
- Inbound agents can also be operable to receive a message of a first type and convert it into a message of a second type.
- An outbound process agent can characterize an outbound operation to transmit outgoing messages to an external process component.
- An integration scenario can be formed by logically associating a plurality of process components in such a manner as to realize a business scenario.
- a plurality of such integration scenarios may be generated and populated in a catalog.
- Data associated with the catalogs, integration scenarios, deployment units, and process components may be stored in a data repository to allow, for example, reuse of such information.
- the process components can be associated with different deployment units that each characterize independently operable software that can, in some variations, be deployed on separate platforms. Communications between process components in different deployment units can be message based. Communications between process components within the same deployment unit need not be message based, and in some cases, such communications can utilize shared memory, database records, and the like.
- a deployment unit may include a business object that is not associated with a process component.
- a plurality of business objects each business object being operable to encapsulate business data, are defined. Thereafter, each of the business objects are associated with exactly one process component (or with a deployment unit if the business object is not associated with a process component).
- Each of the process components characterizes software implementing a respective and distinct process and defines a respective at least one service interface for communicating and interacting with other business objects in other process components. In addition, all communication and interaction between process components takes place through the respective interfaces of the process components.
- Computer program products which can be tangibly encoded on computer readable- material, are also described. Such computer program products can include executable instructions that cause a computer system to implement one or more of the acts and/or components described herein.
- a model provides modeling entities to represent aspects of a software system. Multiple views of the model are provided in a user interface. The model views offer varying levels of detail, allowing users to focus on the information that is important for their task. Model entities can be reused and correspond to reusable software that implements functionality corresponding to the model entity. The model supports dynamic mapping between incompatible message formats. A model can incorporate external components. The models can be used to generate metadata, which can be stored in a repository and used in various downstream processes and tools.
- the subject matter described herein provides a logical abstraction of how various software modules can interact to effect a business scenario.
- effective use can be made of process components as units of software reuse, to provide a design that can be implemented reliably in a cost effective way.
- Deployment units each of which is deployable on a separate computer hardware platform independent of every other deployment unit, enable a scalable design.
- service interfaces of the process components can define a pair- wise interaction between pairs of process components that are in different deployment units in a scalable manner.
- FIG. 1 is an illustration of a modeling method.
- FIG. 2 is an illustration of a modeling system.
- FIG. 3 is an illustration of process component modeling entities.
- FIGS. 4A-4C are an illustration of a process interaction map.
- FIG. 5 is an illustration of a process component model.
- FIG. 6 is an illustration of a process component interaction model.
- FIGS. 7A-7B are an illustration of a business object map.
- FIG. 8 is an illustration of an integration scenario model entity.
- FIGS. 9-9A are an illustration of an integration scenario catalog.
- FIGS. 10A- 1OB are an illustration of a GUI for presenting one or more graphical depictions of views of a model and modeling entities.
- FIG. 1 1 is an illustration of process component interaction with an external process component.
- FIG. 12 is an illustration of process component interaction through a mapping model element.
- a model is a representation of a software system, part of a software system, or an aspect of a software system.
- a model can be associated with one or more views.
- a view of a model represents a subset of the information in the model.
- the term "model” will be used to refer to both a model or a view of the model.
- a modeling system can be used to create, modify and examine a model.
- a model can be used in a software development process to describe or specify a software application, or parts or aspects of a software application, for developers implementing or modifying the application.
- the model specifies the design to a useful level of detail or granularity.
- a compliant implementation of the modeled functionality will conform to the specification represented by the model.
- FIG. 1 is a process flow diagram illustrating a method 100 in which, at 110, a plurality of business objects are defined. Each business object is operable to encapsulate business data and is associated with exactly one process component. Each of the process components characterizes software implementing a respective and distinct process.
- each of the process components defines a respective at least one process interface for communicating and interacting with business objects in other process components, and all communication and interaction between process components takes place through the respective interfaces of the process components.
- interactions among the plurality of business objects are defined. These interactions among business objects in different deployment units occur solely via the process component interfaces.
- FIG. 2 illustrates a modeling system 200.
- An interactive graphical user interface (GUI) 204 allows a user to create, inspect and modify a model.
- the GUI 204 can present a model in different views offering differing levels of detail. This allows users to focus on information that is appropriate to their role or the task at hand.
- a model design component 206 coupled to the GUI 204 provides one or more tools for modifying and manipulating a model, as will be discussed below.
- a repository 202 is capable of storing one or more models and associated information. By way of illustration and without limitation, the repository can incorporate one or more files, databases, services, combinations of these, or other suitable means for providing persistent storage of model information.
- FIG. 3 is an illustration of process component modeling entities (or "process components") in a model.
- process component will be used to refer both to the modeling entity and to an implementation in a software system of a process represented by that modeling entity. The same dual use will be made of other terms to refer both to the modeling entity and an implementation represented by the entity, where the meaning is clear from the context.
- a process component is a software package that realizes a business process and exposes its functionality as services. The functionality contains business transactions.
- a process component contains one or more semantically related business objects (e.g., 330, 310).
- a business object belongs to no more than one process component.
- Process components are modular and context-independent. Context-independent means that a process component is not specific to a given integration scenario. (Integration scenarios are described later.) Therefore, process components are reusable, that is, they can be used in different integration scenarios.
- a process component has one or more service interface modeling entities (316, 318, 320, 322, 336, 338) (or "interfaces").
- An interface is a named grouping of one or more operations. It specifies offered (inbound service interface) or used (outbound service interface) functionality. While, in general, process components will have service interfaces, it is permissible to define a process component having no service operations. This would be appropriate, for example, for process components that inherently or by design interact only with process components deployed on the same hardware platform, in which circumstances a non-service method of interacting, e.g., through shared memory or database records, might be preferred.
- An operation belongs to exactly one process component.
- a process component generally has multiple operations.
- An operation is the smallest, separately-callable function, described by a set of data types used as input, output, and fault parameters serving as a signature.
- An operation can use multiple message types for inbound, outbound, or error messages.
- An operation is specific to one interface, i.e., the same operation cannot be used in more than one interface.
- a process agent (or "agent") is an optional modeling entity representing software that implements an operation. Operations can be implemented through other conventional techniques. Operations (and hence agents) can be synchronous or asynchronous, and inbound or outbound. Synchronous outbound operations send synchronous request messages and process response messages. Synchronous inbound operations respond to messages from synchronous outbound operations. Synchronous communication is when a message is sent with the expectation that a response will be received promptly. Asynchronous communication comes with the expectation that a response will be provided by a separate operation invoked at a later point in time.
- An asynchronous outbound operation is specific to a sending business object. If the asynchronous outbound operation is triggering a new communication to another process component, it is specific for the triggered process component. However, the same asynchronous outbound process operation can be used for two operations which are part of the same message choreography. If the asynchronous outbound operation is sending only a confirmation (not triggering), it might be re-used for different receiving process components.
- Inbound operations are called after a message has been received. Based on a business object's status, inbound operations may initiate communication across deployment units, may initiate business-to-business (B2B) communication, or both by sending messages using well- defined services.
- B2B business-to-business
- the model can describe the potential invocation by one process component of an operation on another process component. Graphically, this is depicted as an arc (340, 342) in FIG. 3 connecting the two process components 306 and 308. Invocation of an operation on a process component is always accomplished by another process component sending a message to the process component, if the two process components are part of different deployment units, which are described below. Interaction between two process components in the same deployment unit, on the other hand, can be implemented by the passing of messages, as described, or it can be implemented by the use of resources, e.g., data objects, database records, or memory, that are accessible to both process components when they are deployed.
- resources e.g., data objects, database records, or memory
- Messages are described by message modeling entities (or “messages”) in the model.
- An process agent can be associated with a single interface.
- interface 338 is associated with process agent 332
- interface 336 is associated with process agent 334
- interface 316 is associated with process agent 312
- interface 318 is associated with process agent 314.
- each operation is associated with a process agent.
- An output operation generally responds to a change in a business object associated with the operation. The operation will generally perform some processing of the data of the business object instance whose change triggered the event.
- An outbound operation 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 a business partner.
- outbound process agent 324 in process component 306 can invoke an operation of interface 322 to send a message that will be received by the inbound process agent 312 in process component 308.
- the message is routed to a specific operation in interface 316 according to the signature or type of the message, which the inbound process agent 312 handles.
- Inbound process agents when implemented are pieces of software that 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, e.g., for associated business objects (330, 310) in response to receiving a message.
- Outbound process agents when implemented can send messages in response to a business object changing or interaction with a business object.
- the inbound process agent 312 may modify business object 310, thus triggering outbound process agent 314 to send a message to the inbound process agent 328. If two operation invocations are part of the same message choreography, they are associated with the same process agent.
- a business object model entity models a 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 and zero or more service interfaces. Implemented business processes operate on business objects.
- a business object represents a specific view on some well-defined business content.
- a business object represents content, which a typical business user would expect and understand with little explanation.
- Business objects are further categorized as business process objects and master data objects.
- a master data object is an object that encapsulates master data (i.e., data that is valid for a period of time).
- a business process object which is the kind of business object generally found in a process component, is an object that encapsulates transactional data (i.e., data that is valid for a point in time).
- the term business object will be used generically to refer to a business process object and a master data object, unless the context requires otherwise. Properly implemented, business objects are implemented free of redundancies.
- Business process objects are associated with exactly one process component.
- Master data objects are either associated with exactly one process component or exactly one deployment unit.
- FIGS. 4A-4C illustrate a process interaction map 400.
- a process interaction map is a modeling entity that describes interactions between two or more process components. It can be presented in the GUI 204 (FIG. 2) by the model design component 206 as a circuit diagram, for example, with arcs indicating potential interactions between process components.
- process components are represented as icons (e.g., 404, 406, 408). So called “external” process components are indicated with dashed lines (e.g., 406, 408).
- External process components are shown to place the modeled process components in their operational context relative to another system, e.g., a system belonging to another company, such as a customer or other third party.
- the GUI 204 allows a user to connect and disconnect process components (i.e., to indicate potential interactions), move process components, and zoom in a specific portion of the map 400 to see more detail, as indicated by view 414.
- Groups of process components can be organized into scenarios and deployment units.
- An integration scenario modeling entity (or "scenario") describes a group of process components that interact directly or indirectly (i.e., through one or more other process components) with each other.
- a process component belongs to one deployment unit. Scenarios are discussed below.
- a deployment unit modeling entity (e.g., 402, 410, 412) models a deployment unit, which includes one or more process components that can be deployed together on a single computer system platform.
- Separate deployment units can be deployed on separate physical computing systems and include one or more process components.
- a physical system can be a cluster of computers having direct access to a common database.
- the process components of one deployment unit interact with those of another deployment unit only using messages passed through one or more data communication networks or other suitable communication channels.
- a deployment unit software entity deployed on a platform belonging to Company A can interact with a deployment unit software entity deployed on a separate platform belonging to Company B, allowing for business-to-business communication.
- deployment units in different divisions of the same company can interact with each other. More than one instance of a given deployment unit software entity can execute at the same time.
- FIG. 5 is an illustration of a process component model (PCM) 500.
- a PCM is a view of a model that incorporates the model entities associated with a particular process component.
- a PCM can also describe potential interactions between a process component and other process components in the same or in different deployment units.
- the illustrated process component 500 can interact with a Customer Requirement Processing process component 504 and a Customer Invoice Processing process component 525.
- a PCM can describe interaction with external process components that are controlled by third parties (e.g., 528).
- the PCM models operations incorporated in a process component. For example, inbound operation Change Sales Order based on Customer Requirement Fulfillment Confirmation 508, and outbound operations Request Invoicing 520 and Confirm Sales Order 522.
- the arc 530 connecting the process component 504 to the interface 502 represents that the process component 504 can invoke an operation on that interface.
- the arcs 532 and 534 represent that the process component illustrated in 500 can invoke an operation on process components 525 and
- the PCM optionally models process agents (e.g., 510, 516, 518) corresponding to the process component's operations.
- process agents e.g., 510, 516, 5128
- the Change Sales Order based on Customer Requirement inbound process agent 510 models processing or responding to a message routed to inbound operations 508 or 540.
- the inbound process agent 510 will access and modify the Sales Order business object 514 as part of the processing, e.g., change the delivery date of goods or services on the sales order.
- Process component 525 can receive one or more messages by way of outbound operation 520, as denoted by the arc 532 connecting outbound operation 520 to the process component 525. Based on the change associated with the business object 514, the Request Invoicing from Sales Order to Customer Invoice Processing outbound process agent 518 invokes operation 520 in interface 526 to send a message to process component 525. Likewise, external process component 528 can receive one or more messages sent by outbound operation 522, as denoted by the arc 534 connecting operation 522 to the process component 528. Based on the state or a state change associated with the business object 514, outbound process agent 516 can invoke operation 522 to send a message to external process component 528.
- FIG. 6 is an illustration of a process component interaction model (PCEVI) 600.
- PCEVI process component interaction model
- a PCEVI is a view of a model that incorporates relevant model entities associated with potential interaction between two process components (e.g., 602, 604). Interfaces, process agents and business objects that are not relevant to the potential interaction are excluded.
- the PCEVI 600 shows interactions between a Time and Labor Management process component 602 and a Goods and Service Acknowledgement process component 604.
- the Time and Labor Management process component 602 includes an Employee Time Calendar business object 606 that gives a read-only information of a calendar based overview of different time data (e.g., planned working time, an absences and working time confirmation) of employees and their superposition (e.g., illness, vacation, etc.).
- the Employee Time Calendar business object 606 may use a Notify Goods and Services Acknowledgement outbound process agent 608 to invoke a Notify of Goods and Service Acknowledgement Notification operation 610 or a Notify of Goods and Service Acknowledgement Cancellation operation 612, which are both included in the Internal Service Acknowledgement Out interface 614.
- the Notify of Goods and Service Acknowledgement Notification operation 610 notifies the Goods and Service
- the Acknowledgement process component 604 of a service provided by an external employee sends a Goods and Service Acknowledgement Request message 616 when an active employee time with Goods and Service Acknowledgement relevant information is created or changed.
- the Goods and Service Acknowledgement process component 604 receives the
- a Create Goods and Service Acknowledgement operation 620 is invoked to create Goods and Service Acknowledgement by initiating a Maintain GSA based on Internal Acknowledgment inbound process agent 622.
- the Maintain GSA based on Internal Acknowledgment inbound process agent 622 updates or creates a Goods and Service Acknowledgement business object 624 to report the receipt of goods and services.
- the Goods and Service Acknowledgement business object 624 may be used when employees of a company can confirm that they have received the goods and services they ordered through internal requests; purchasers, or designated recipients of goods and services, can confirm that they have received the goods and services they ordered on behalf of the employees for whom they are responsible; or suppliers or service providers can report that they have delivered the requested goods or have rendered the requested services.
- the Notify Goods and Services Acknowledgement outbound process agent 608 may also invoke the Notify of Goods and Service Acknowledgement Cancellation operation 612 to notify the Goods and Service Acknowledgement process component 604 of a cancellation of goods and service.
- the Notify of Goods and Service Acknowledgement Cancellation operation 612 sends a Goods and Service Acknowledgement Cancellation Request message 626 when an active employee time with Goods and Service Acknowledgement relevant information is cancelled.
- a Cancel Goods and Service Acknowledgement operation 628 is invoked to cancel Goods and Service Acknowledgement.
- the Maintain GSA based on Internal Acknowledgment inbound process agent 622 updates the Goods and Service Acknowledgement business object 624 to report the cancellation of goods and services.
- the message format of a message sent by an outbound operation need not match the message format expected by an inbound operation. If the message formats do not match, and the message is transformed, or mapped. Message mapping is indicated by interposition of an intermediary mapping model element between the source and the destination of the message in a PCM or a PCEVI (see below).
- FIGS. 7A-7B illustrate a business object map 700.
- a business object map is a view of a model that incorporates deployment units, process components, and business objects. Interfaces, operations and process agents are excluded from the view. Each model entity is only represented once in the business object map.
- the business object map is a representation of all deployment units, process components, and business objects.
- a Customer Invoice Processing process component 726 in Customer Invoicing deployment unit 704 incorporates two business objects: a customer invoice request 710 and a customer invoice 708.
- a Project Processing process component 724 in a Project Management deployment unit 706 includes five business objects: a Project Request 718, a Project 720, a Project Snapshot 712, a Project Simulation 714, and a Project Template 722.
- FIG. 8 is an illustration of an integration scenario model entity 800 (or "integration scenario").
- An integration scenario is a realization of a given end-to-end business scenario. It consists of the process components and the interactions between them, which are required for its realization. A process component is only represented once in an integration scenario model, even though the actual flow in the software system might invoke the same process component multiple times.
- An integration scenario model entity describes at a high level the potential interaction between process components in one or more deployment units that are relevant to realization of the business scenario.
- an integration scenario can be a set of process components and their interactions working together to realize a business scenario to achieve a business objective, such as selling products to generate revenue. Internal details of process components are not described, nor are details of process component interactions (e.g., interfaces, operations and messages).
- the illustrated integration scenario 800 is for a service procurement software application.
- the service procurement application is software that implements an end-to-end process used to procure services.
- the scenario 800 includes nine deployment units: a Financial Accounting unit 802, a Project Management unit 804, a Purchasing unit 806, a Supplier Invoicing unit 808, a Payment unit 810, a RFQ Processing unit 812, a Due Item Management unit 814, a Requisitioning unit 816, and a Human Capital Management unit 818.
- the Financial Accounting deployment unit 802 includes an Accounting process component 803 that records all relevant business transactions.
- the Project Management deployment unit 804 includes a Project Processing process component 820 that is responsible for structuring, planning, and executing measures or projects (e.g., short-term measures, complex projects, etc.).
- measures or projects e.g., short-term measures, complex projects, etc.
- the Purchasing deployment unit 806 includes four process components: a Purchase Request Processing process component 828, a Purchase Order Processing process component 830, a Purchasing Contract process component 832, and a Goods and Service Acknowledgement process component 833.
- the Purchase Request Processing process component 828 provides a request or instruction to the purchasing department to purchase specified goods or services in specified quantities within a specified time.
- the Purchase Order Processing process component 830 includes a purchase order business object and a purchase order confirmation business object.
- the purchase order is 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 is a communication from a supplier to a purchaser to advise that a purchase order has been received. In particular, a purchase order confirmation may advise the purchaser of the supplier accepting the purchase order, or the supplier proposing changes to the purchase order, or the supplier not accepting the purchase order.
- the Purchasing Contract process component 832 handles an agreement between a purchaser and a supplier that details the supply of goods or the performance of services at agreed conditions.
- the Purchasing Contract process component includes the purchasing contract business object.
- the Goods and Service Acknowledgement 833 includes a Goods and Service
- the Goods and Service Acknowledgement business object is a document that states the recipient's, for example, a purchaser's, obligation to pay the supplier for goods received or services rendered.
- An invoice is normally created after the goods and service acknowledgement has been confirmed.
- the Supplier Invoicing deployment unit 808 includes a Supplier Invoice Processing process component 836.
- the Supplier Invoice Processing process component 836 includes a supplier invoice business object and a supplier invoice request business object.
- the supplier invoice is a document that states the recipient's obligation to pay the supplier for goods received or services rendered.
- the invoice may be created after the goods and service acknowledgment has been confirmed.
- the supplier invoice request is a document that is sent to invoice verification, advising that an invoice for specified quantities and prices is expected and may be created through evaluation settlement.
- the system uses the invoice request as a basis for invoice verification, as well as for the automatic creation of the invoice.
- the Payment deployment unit 810 includes a Payment Processing process component 838.
- the Payment Processing process component 838 is used to handle all incoming and outgoing payments as well as represent the main database for a liquidity status.
- the RFQ deployment unit 812 includes an RFQ Processing process component 840.
- An RFQ Processing deployment unit includes a Request for Response business object and a Quote business object.
- the request for quotation (RFQ) is a description of materials and services that purchasers use to request responses from potential suppliers.
- Requests for quotation can be one of the following types: a request for (price) information, a request for quote that may run over a certain period of time, a request for proposal in complex purchasing situation or live auctions that may be performed over a short time frame.
- the quote is a response to a request for quotation in which a supplier offers to sell goods and services at a certain price.
- the quote can be subject to complex pricing and conditions.
- the Due Item Management deployment unit 814 includes a Due Item Processing process component 842.
- the Due Item Processing process component 842 is used to manage all payables, receivables from service and supply and corresponding sales including a withholding tax.
- the Requisitioning deployment unit 816 includes an Internal Request Processing process component 844.
- the Internal Request Processing deployment unit 816 includes an Internal Request business object.
- Employees of a company may make an internal request for the procurement of goods or services for the company. For example, the employees may order stationery, computer hardware, or removal services by creating an internal request.
- the internal request can be fulfilled by an issue of a purchase request to the purchasing department, a reservation of goods from stock, or a production request.
- the Human Capital Management deployment unit 818 includes a Time and Labor Management process component 848.
- the Time and Labor Management process component 848 supports the definition of employees' planned working time as well as the recording or the actual working times and absences and their evaluation.
- the foundation layer includes a Source of Supply Determination process component 834, a Customer Invoice Processing at Supplier process component 837, a Sales Order Processing at Supplier process component 846, a Payment Processing at Business Partner process component 850, a Bank Statement Creation at Bank process component 852, and a Payment Order Processing at House Bank process component 854.
- the service procurement design includes a Source of Supply Determination process component 834 that uses two business objects to determine a source of supply: a supply quota arrangement business object, and a source of supply business object.
- a supply quota arrangement is a distribution of material requirements or goods to different sources of supply, business partners, or organizational units within a company.
- An example of the use of supply quota arrangements is the distribution of material requirements between in-house production and different sources for external procurement.
- a supply quota arrangement can also define the distribution of goods to customers in case of excess production or shortages.
- a source of supply is an object that describes a logical link between a possible source of products and a possible target.
- a number of external process components, described below, will be used to describe the architectural design. These include a Customer Invoice Processing at Supplier process component 837, a Sales Order Processing at Supplier process component 846, a Payment Processing at Business Partner process component 850, a Bank Statement Creation at Bank process component 852, and a Payment Order Processing at House Bank process component 854.
- the Supplier Invoicing deployment unit 808 receives messages from a Customer Invoice at Supplier process component 837, which is used, at a supplier, to charge a customer for the delivery of goods or services.
- the service procurement design includes a Sales Order Processing at Supplier process component 846 that may receive messages from the RPQ Processing process component 840.
- the Sales Order Processing at Supplier process component 846 handles customers' requests to a company for delivery of goods or services at a certain time. The requests are received by a sales area, which is then responsible for fulfilling the contract.
- the Payment Processing process component 838 may send updates to a Payment Processing at Business Partner process component 850, which is used to handle, at business partner, all incoming and outgoing payments and represent the main data base for the liquidity status.
- the Payment Processing process component 838 also receives messages from the Bank Statement Creation at Bank process component 852.
- the message may include a bank statement for a bank account.
- the Payment Processing process component 838 sends messages to the Payment Order Processing at House Bank process component 854.
- the message may include a Bank Payment Order that is a Payment Order which will be sent to a house bank.
- the bank payment order may contain bank transfers as well as direct debits.
- FIGS. 9-9 A illustrate an integration scenario catalog (or "scenario catalog") 900.
- a scenario catalog presents an organized view of a collection of integration scenarios. The view can be organized in a number of ways, including hierarchically or associatively based on one or more attributes of the integration scenarios.
- the illustrated integration scenario catalog 900 represents a structured directory of integration scenarios. For example, a scenario directory Sell from Stock 902 representing a family of scenarios includes two entries: a reference to a Sell from Stock integration scenario 904, and a reference to a Sell from Stock for Delivery Schedules integration scenario 906.
- FIGS. 10A- 1OB illustrate the GUI 204 (from FIG. 2) for presenting one or more graphical depictions of views of a model and modeling entities. Each view can present a different level of detail or emphasize a different aspect of the model. This allows for different classes of users to focus on the information that is important for carrying out their duties without being distracted by extraneous detail.
- One or more of the following graphical depictions can be presented: a scenario catalog 1002, an integration scenario model 1004, a PCIM 1008, and a PCM 1010.
- the GUI 204 allows a user to "drill down" to increasing levels of model detail. For example, selection of a scenario icon 1006 in the integration scenario catalog 1002 can cause an associated integration scenario model 1004 to be presented.
- Selection of a graphical representation of a process component 1014 in the integration scenario can cause an associated PCM 1010 for the process component to be presented.
- selection of an arc 1012 connecting process components in different deployment units can cause a PCIM 1008 for the process components connected by the arc to be presented.
- the aforementioned graphical depictions can be presented singularly or in combination with each other in the GUI 204.
- a given graphical depiction can present all of its underlying information or a portion thereof, while allowing other portions to be viewed through a navigation mechanism, e.g., user selection of a graphical element, issuance of a command, or other suitable means.
- FIG. 1 1 is an illustration of process component interaction with an external process component, representing an external system.
- a process component can interact with an external process component. This interaction can be modeled even though the interfaces of the external process are unknown, as is the case in this example. (However, if this information is known, it can be incorporated into the model.)
- the Purchase Order Processing process component 1102 includes a Purchase Order business object 1106 which is 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 Request Purchase Order to Supplier outbound process agent 1108 can request invocation of a Request Purchase Order Creation operation 1112, a Request Purchase Order Cancellation operation 1114, or a Request Purchase Order Change operation 1116 in an Ordering Out interface 1110.
- the Request Purchase Order Cancellation operation 1114 requests a Cancellation of a
- the Request Purchase Order Change operation 1116 requests a change of a purchase order that was formerly ordered at the supplier which creates a Purchase Order Change Request message 1120.
- the Request Purchase Order Creation operation 1112 requests a purchase order from a supplier which creates a Purchase Order Request message 1122.
- the Sales Order Processing process component 1104 may create a Purchase Order Confirmation message 1123 to update the Purchase Order Processing process component 1102.
- a Create Purchase Order Confirmation operation 1124 included in an Ordering In interface 1125, may transfer the update to the Purchase Order Confirmation business object 1128 by using a Create Purchase Order inbound process agent 1 126.
- the Purchase Order Confirmation business object 1128 is 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.
- FIG. 12 is an illustration 1200 of process component interaction through a mapping model element 1214 (or "mapper").
- the message can be transformed by a mapper on its way from the outbound process agent to the inbound process agent.
- output process agent 1216 associated with process component 1202 can send a message 1210 to inbound process agent 1217 in process component 1204 by way of operation 1218 in interface 1206.
- a transformation of the message from its original format to a format compatible with operation 1220 can be described by a mapper 1214 interposed between the two process agents.
- the mapper 1214 generates a new message 1212 based on the original message 1210, where the new message has a format that is compatible with operation 1220 in interface 1208.
- the subject matter described in this specification and all of the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structural means disclosed in this specification and structural equivalents thereof, or in combinations of them.
- the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more computer programs tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
- a computer program (also known as a program, software, software application, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
- a computer program does not necessarily correspond to a file.
- a program can be stored in a portion of a file that holds other programs or data, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).
- a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
- the processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output.
- the processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
- processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer.
- a processor will receive instructions and data from a read-only memory or a random access memory or both.
- the essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data.
- a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
- Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
- semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
- magnetic disks e.g., internal hard disks or removable disks
- magneto-optical disks e.g., CD-ROM and DVD-ROM disks.
- the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
- the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.
- a display device e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
- a keyboard and a pointing device e.g., a mouse or a trackball
- Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
- the subject matter described in this specification can be implemented in a computing system that includes a back-end component (e.g., a data server), a middleware component (e.g., an application server), or a front-end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described herein), or any combination of such back-end, middleware, and front-end components.
- the components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network ("LAN”) and a wide area network (“WAN”), e.g., the Internet.
- LAN local area network
- WAN wide area network
- the computing system can include clients and servers.
- a client and server are generally remote from each other and typically interact through a communication network.
- the relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
Abstract
Methods and apparatus, including computer program products, for defining a software model business object are described. A plurality of business objects and interactions between these business objects are defined. Each business object is operable to encapsulate business data and can be associated with exactly one process component. Each of the process components characterizes software implementing a respective and distinct process and defines a respective at least one service interface for communicating and interacting with business objects in other process components. Moreover, all communication and interaction between process components takes place through the respective interfaces of the process components. Additionally, the interactions among business objects in different deployment units occur solely via the process component interfaces.
Description
SOFTWARE MODEL BUSINESS OBJECTS
BACKGROUND
The subject matter of this patent applications relates to modeling software systems, and more particularly to modeling the composition and interaction of components in a software system.
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. Typical software modeling systems may not be able to reduce this complexity for end users. In order to design, configure, update or implement an enterprise software system, one is required to understand details of the system at varying levels, depending on his or her role in designing, managing or implementing the system. For example, a systems administrator may need a high-level technical understanding of how various software modules are installed on physical hardware, such as a server device or a network, and how those software modules interact with other software modules in the system. A person responsible for configuring the software may need a high-level functional understanding of the operations that each functional component provides. An application designer may need a low-level technical understanding of the various software interfaces that portions of the application require or implement. And an application developer may need a detailed understanding of the interfaces and functionality he or she is implementing in relation to the remainder of the system.
SUMMARY
A plurality of business objects and interactions between these business objects are defined. Each business object is operable to encapsulate business data and can be associated with exactly one process component. Each of the process components characterizes software implementing a respective and distinct process and defines a respective at least one service interface for communicating and interacting with business objects in other process components. Moreover, all communication and interaction between process components takes place through the respective interfaces of the process components. Additionally, the interactions among business objects in different deployment units occur solely via the process
component interfaces.
The process components can characterize inbound operations and/or outbound operations. The inbound operations handle incoming messages associated with a modification of reading of data encapsulated in a business object associated with the process component. The outbound operations handle outgoing messages associated with a modification or reading of data encapsulated in at least one business object associated with another process component.
The process components may also include process agents that characterize operations that enable communications between a business object associated with the process component and a business object associated with any other process component. The process agents are operable to enable communication through the service interface of its respective process component. An inbound agent can characterize an inbound operation to handle incoming messages. Inbound agents can also be operable to receive a message of a first type and convert it into a message of a second type. An outbound process agent can characterize an outbound operation to transmit outgoing messages to an external process component.
An integration scenario can be formed by logically associating a plurality of process components in such a manner as to realize a business scenario. A plurality of such integration scenarios may be generated and populated in a catalog. Data associated with the catalogs, integration scenarios, deployment units, and process components may be stored in a data repository to allow, for example, reuse of such information.
The process components can be associated with different deployment units that each characterize independently operable software that can, in some variations, be deployed on separate platforms. Communications between process components in different deployment units can be message based. Communications between process components within the same deployment unit need not be message based, and in some cases, such communications can utilize shared memory, database records, and the like. In addition, in some variations, a deployment unit may include a business object that is not associated with a process component.
In an interrelated aspect, a plurality of business objects, each business object being operable to encapsulate business data, are defined. Thereafter, each of the business objects
are associated with exactly one process component (or with a deployment unit if the business object is not associated with a process component). Each of the process components characterizes software implementing a respective and distinct process and defines a respective at least one service interface for communicating and interacting with other business objects in other process components. In addition, all communication and interaction between process components takes place through the respective interfaces of the process components.
Computer program products, which can be tangibly encoded on computer readable- material, are also described. Such computer program products can include executable instructions that cause a computer system to implement one or more of the acts and/or components described herein.
Similarly, computer systems are also described that can include a processor and a memory coupled to the processor. The memory can encode one or more programs that cause the processor to implement one or more of the acts and/or components described herein. The subject matter described herein provides many advantages. A model provides modeling entities to represent aspects of a software system. Multiple views of the model are provided in a user interface. The model views offer varying levels of detail, allowing users to focus on the information that is important for their task. Model entities can be reused and correspond to reusable software that implements functionality corresponding to the model entity. The model supports dynamic mapping between incompatible message formats. A model can incorporate external components. The models can be used to generate metadata, which can be stored in a repository and used in various downstream processes and tools.
Moreover, the subject matter described herein provides a logical abstraction of how various software modules can interact to effect a business scenario. In particular, effective use can be made of process components as units of software reuse, to provide a design that can be implemented reliably in a cost effective way. Deployment units, each of which is deployable on a separate computer hardware platform independent of every other deployment unit, enable a scalable design. Furthermore, service interfaces of the process components can define a pair- wise interaction between pairs of process components that are in different deployment units in a scalable manner.
One implementation of the subject matter described in this specification provides all of the above advantages.
Details of one or more implementations of the subject matter described in this specification are set forth in the accompanying drawings and in the description below. Further features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.
BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is an illustration of a modeling method. FIG. 2 is an illustration of a modeling system. FIG. 3 is an illustration of process component modeling entities.
FIGS. 4A-4C are an illustration of a process interaction map. FIG. 5 is an illustration of a process component model. FIG. 6 is an illustration of a process component interaction model. FIGS. 7A-7B are an illustration of a business object map. FIG. 8 is an illustration of an integration scenario model entity.
FIGS. 9-9A are an illustration of an integration scenario catalog. FIGS. 10A- 1OB are an illustration of a GUI for presenting one or more graphical depictions of views of a model and modeling entities.
FIG. 1 1 is an illustration of process component interaction with an external process component.
FIG. 12 is an illustration of process component interaction through a mapping model element.
Like reference numbers and designations in the various drawings indicate like elements.
DETAILED DESCRIPTION
In the context of this document, a model is a representation of a software system, part of a software system, or an aspect of a software system. A model can be associated with one or more views. A view of a model represents a subset of the information in the model. For purposes of discussion, the term "model" will be used to refer to both a model or a view of
the model. A modeling system can be used to create, modify and examine a model. A model can be used in a software development process to describe or specify a software application, or parts or aspects of a software application, for developers implementing or modifying the application. The model specifies the design to a useful level of detail or granularity. A compliant implementation of the modeled functionality will conform to the specification represented by the model.
FIG. 1 is a process flow diagram illustrating a method 100 in which, at 110, a plurality of business objects are defined. Each business object is operable to encapsulate business data and is associated with exactly one process component. Each of the process components characterizes software implementing a respective and distinct process.
Moreover, each of the process components defines a respective at least one process interface for communicating and interacting with business objects in other process components, and all communication and interaction between process components takes place through the respective interfaces of the process components. At 120, interactions among the plurality of business objects are defined. These interactions among business objects in different deployment units occur solely via the process component interfaces.
FIG. 2 illustrates a modeling system 200. An interactive graphical user interface (GUI) 204 allows a user to create, inspect and modify a model. The GUI 204 can present a model in different views offering differing levels of detail. This allows users to focus on information that is appropriate to their role or the task at hand. A model design component 206 coupled to the GUI 204 provides one or more tools for modifying and manipulating a model, as will be discussed below. A repository 202 is capable of storing one or more models and associated information. By way of illustration and without limitation, the repository can incorporate one or more files, databases, services, combinations of these, or other suitable means for providing persistent storage of model information.
FIG. 3 is an illustration of process component modeling entities (or "process components") in a model. For brevity, where the sense is clear from the context, the term "process component" will be used to refer both to the modeling entity and to an implementation in a software system of a process represented by that modeling entity. The
same dual use will be made of other terms to refer both to the modeling entity and an implementation represented by the entity, where the meaning is clear from the context. A process component is a software package that realizes a business process and exposes its functionality as services. The functionality contains business transactions. A process component contains one or more semantically related business objects (e.g., 330, 310). A business object belongs to no more than one process component.
Process components are modular and context-independent. Context-independent means that a process component is not specific to a given integration scenario. (Integration scenarios are described later.) Therefore, process components are reusable, that is, they can be used in different integration scenarios.
A process component has one or more service interface modeling entities (316, 318, 320, 322, 336, 338) (or "interfaces"). An interface is a named grouping of one or more operations. It specifies offered (inbound service interface) or used (outbound service interface) functionality. While, in general, process components will have service interfaces, it is permissible to define a process component having no service operations. This would be appropriate, for example, for process components that inherently or by design interact only with process components deployed on the same hardware platform, in which circumstances a non-service method of interacting, e.g., through shared memory or database records, might be preferred. An operation belongs to exactly one process component. A process component generally has multiple operations. An operation is the smallest, separately-callable function, described by a set of data types used as input, output, and fault parameters serving as a signature. An operation can use multiple message types for inbound, outbound, or error messages. An operation is specific to one interface, i.e., the same operation cannot be used in more than one interface.
Operations are described for purposes of exposition in terms of process agents. A process agent (or "agent") is an optional modeling entity representing software that implements an operation. Operations can be implemented through other conventional techniques. Operations (and hence agents) can be synchronous or asynchronous, and inbound or outbound.
Synchronous outbound operations send synchronous request messages and process response messages. Synchronous inbound operations respond to messages from synchronous outbound operations. Synchronous communication is when a message is sent with the expectation that a response will be received promptly. Asynchronous communication comes with the expectation that a response will be provided by a separate operation invoked at a later point in time.
An asynchronous outbound operation is specific to a sending business object. If the asynchronous outbound operation is triggering a new communication to another process component, it is specific for the triggered process component. However, the same asynchronous outbound process operation can be used for two operations which are part of the same message choreography. If the asynchronous outbound operation is sending only a confirmation (not triggering), it might be re-used for different receiving process components.
Inbound operations are called after a message has been received. Based on a business object's status, inbound operations may initiate communication across deployment units, may initiate business-to-business (B2B) communication, or both by sending messages using well- defined services.
The model can describe the potential invocation by one process component of an operation on another process component. Graphically, this is depicted as an arc (340, 342) in FIG. 3 connecting the two process components 306 and 308. Invocation of an operation on a process component is always accomplished by another process component sending a message to the process component, if the two process components are part of different deployment units, which are described below. Interaction between two process components in the same deployment unit, on the other hand, can be implemented by the passing of messages, as described, or it can be implemented by the use of resources, e.g., data objects, database records, or memory, that are accessible to both process components when they are deployed.
Messages are described by message modeling entities (or "messages") in the model.
An process agent can be associated with a single interface. For example, interface 338 is associated with process agent 332, interface 336 is associated with process agent 334, interface 316 is associated with process agent 312, and interface 318 is associated with process agent 314. In one variation, each operation is associated with a process agent.
An output operation generally responds to a change in a business object associated with the operation. The operation will generally perform some processing of the data of the business object instance whose change triggered the event. An outbound operation 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 a business partner. For example, outbound process agent 324 in process component 306 can invoke an operation of interface 322 to send a message that will be received by the inbound process agent 312 in process component 308. The message is routed to a specific operation in interface 316 according to the signature or type of the message, which the inbound process agent 312 handles.
Inbound process agents when implemented are pieces of software that 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, e.g., for associated business objects (330, 310) in response to receiving a message. Outbound process agents when implemented can send messages in response to a business object changing or interaction with a business object. For example, the inbound process agent 312 may modify business object 310, thus triggering outbound process agent 314 to send a message to the inbound process agent 328. If two operation invocations are part of the same message choreography, they are associated with the same process agent.
A business object model entity models a 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 and zero or more service interfaces. Implemented business processes operate on business objects. A business object represents a specific view on some well-defined business content.
A business object represents content, which a typical business user would expect and understand with little explanation. Business objects are further categorized as business process objects and master data objects. A master data object is an object that encapsulates master data (i.e., data that is valid for a period of time). A business process object, which is the kind of business object generally found in a process component, is an object that
encapsulates transactional data (i.e., data that is valid for a point in time). The term business object will be used generically to refer to a business process object and a master data object, unless the context requires otherwise. Properly implemented, business objects are implemented free of redundancies. Business process objects are associated with exactly one process component. Master data objects are either associated with exactly one process component or exactly one deployment unit.
Business objects residing in a foundation layer are called business foundation objects. The foundation layer is deployed on every platform, and its business objects, process components, and reuse services are available to be used by all application scenarios. It is assumed that business objects in the foundation layer will be local in all integration scenarios and can be directly accessed synchronously from business objects within deployment units in an application layer. Business objects in the foundation layer can be associated with more than one process component. FIGS. 4A-4C illustrate a process interaction map 400. A process interaction map is a modeling entity that describes interactions between two or more process components. It can be presented in the GUI 204 (FIG. 2) by the model design component 206 as a circuit diagram, for example, with arcs indicating potential interactions between process components. In a visual rendition of the map 400, process components are represented as icons (e.g., 404, 406, 408). So called "external" process components are indicated with dashed lines (e.g., 406, 408). External process components are shown to place the modeled process components in their operational context relative to another system, e.g., a system belonging to another company, such as a customer or other third party. The GUI 204 allows a user to connect and disconnect process components (i.e., to indicate potential interactions), move process components, and zoom in a specific portion of the map 400 to see more detail, as indicated by view 414.
Groups of process components can be organized into scenarios and deployment units. An integration scenario modeling entity (or "scenario") describes a group of process components that interact directly or indirectly (i.e., through one or more other process
components) with each other. A process component belongs to one deployment unit. Scenarios are discussed below.
A deployment unit modeling entity (e.g., 402, 410, 412) models a deployment unit, which includes one or more process components that can be deployed together on a single computer system platform.
Separate deployment units can be deployed on separate physical computing systems and include one or more process components. For example, a physical system can be a cluster of computers having direct access to a common database. The process components of one deployment unit interact with those of another deployment unit only using messages passed through one or more data communication networks or other suitable communication channels. Thus, a deployment unit software entity deployed on a platform belonging to Company A can interact with a deployment unit software entity deployed on a separate platform belonging to Company B, allowing for business-to-business communication. Or deployment units in different divisions of the same company can interact with each other. More than one instance of a given deployment unit software entity can execute at the same time.
FIG. 5 is an illustration of a process component model (PCM) 500. A PCM is a view of a model that incorporates the model entities associated with a particular process component. A PCM can also describe potential interactions between a process component and other process components in the same or in different deployment units. For example, the illustrated process component 500 can interact with a Customer Requirement Processing process component 504 and a Customer Invoice Processing process component 525. Moreover, a PCM can describe interaction with external process components that are controlled by third parties (e.g., 528). The PCM models operations incorporated in a process component. For example, inbound operation Change Sales Order based on Customer Requirement Fulfillment Confirmation 508, and outbound operations Request Invoicing 520 and Confirm Sales Order 522. The arc 530 connecting the process component 504 to the interface 502 represents that the process component 504 can invoke an operation on that interface. The arcs 532 and 534
represent that the process component illustrated in 500 can invoke an operation on process components 525 and 528, respectively.
The PCM optionally models process agents (e.g., 510, 516, 518) corresponding to the process component's operations. For example, the Change Sales Order based on Customer Requirement inbound process agent 510 models processing or responding to a message routed to inbound operations 508 or 540. The inbound process agent 510, for example, will access and modify the Sales Order business object 514 as part of the processing, e.g., change the delivery date of goods or services on the sales order.
Process component 525 can receive one or more messages by way of outbound operation 520, as denoted by the arc 532 connecting outbound operation 520 to the process component 525. Based on the change associated with the business object 514, the Request Invoicing from Sales Order to Customer Invoice Processing outbound process agent 518 invokes operation 520 in interface 526 to send a message to process component 525. Likewise, external process component 528 can receive one or more messages sent by outbound operation 522, as denoted by the arc 534 connecting operation 522 to the process component 528. Based on the state or a state change associated with the business object 514, outbound process agent 516 can invoke operation 522 to send a message to external process component 528.
FIG. 6 is an illustration of a process component interaction model (PCEVI) 600. PCIMs can be reused in different integration scenarios. A PCEVI is a view of a model that incorporates relevant model entities associated with potential interaction between two process components (e.g., 602, 604). Interfaces, process agents and business objects that are not relevant to the potential interaction are excluded. The PCEVI 600 shows interactions between a Time and Labor Management process component 602 and a Goods and Service Acknowledgement process component 604.
The Time and Labor Management process component 602 includes an Employee Time Calendar business object 606 that gives a read-only information of a calendar based overview of different time data (e.g., planned working time, an absences and working time confirmation) of employees and their superposition (e.g., illness, vacation, etc.). The Employee Time Calendar business object 606 may use a Notify Goods and Services
Acknowledgement outbound process agent 608 to invoke a Notify of Goods and Service Acknowledgement Notification operation 610 or a Notify of Goods and Service Acknowledgement Cancellation operation 612, which are both included in the Internal Service Acknowledgement Out interface 614. The Notify of Goods and Service Acknowledgement Notification operation 610 notifies the Goods and Service
Acknowledgement process component 604 of a service provided by an external employee. The Notify of Goods and Service Acknowledgement Notification operation 610 sends a Goods and Service Acknowledgement Request message 616 when an active employee time with Goods and Service Acknowledgement relevant information is created or changed. The Goods and Service Acknowledgement process component 604 receives the
Goods and Service Acknowledgement Request message 616 via an Internal Acknowledgement In interface 618. Upon receipt of the Goods and Service Acknowledgement Request message 616, a Create Goods and Service Acknowledgement operation 620 is invoked to create Goods and Service Acknowledgement by initiating a Maintain GSA based on Internal Acknowledgment inbound process agent 622. The Maintain GSA based on Internal Acknowledgment inbound process agent 622 updates or creates a Goods and Service Acknowledgement business object 624 to report the receipt of goods and services. The Goods and Service Acknowledgement business object 624 may be used when employees of a company can confirm that they have received the goods and services they ordered through internal requests; purchasers, or designated recipients of goods and services, can confirm that they have received the goods and services they ordered on behalf of the employees for whom they are responsible; or suppliers or service providers can report that they have delivered the requested goods or have rendered the requested services.
The Notify Goods and Services Acknowledgement outbound process agent 608 may also invoke the Notify of Goods and Service Acknowledgement Cancellation operation 612 to notify the Goods and Service Acknowledgement process component 604 of a cancellation of goods and service. The Notify of Goods and Service Acknowledgement Cancellation operation 612 sends a Goods and Service Acknowledgement Cancellation Request message 626 when an active employee time with Goods and Service Acknowledgement relevant information is cancelled. Upon receipt of the Goods and Service Acknowledgement
Cancellation Request message 626, a Cancel Goods and Service Acknowledgement operation 628 is invoked to cancel Goods and Service Acknowledgement. Next, the Maintain GSA based on Internal Acknowledgment inbound process agent 622 updates the Goods and Service Acknowledgement business object 624 to report the cancellation of goods and services.
The message format of a message sent by an outbound operation need not match the message format expected by an inbound operation. If the message formats do not match, and the message is transformed, or mapped. Message mapping is indicated by interposition of an intermediary mapping model element between the source and the destination of the message in a PCM or a PCEVI (see below).
FIGS. 7A-7B illustrate a business object map 700. A business object map is a view of a model that incorporates deployment units, process components, and business objects. Interfaces, operations and process agents are excluded from the view. Each model entity is only represented once in the business object map. Hence, the business object map is a representation of all deployment units, process components, and business objects. In the illustrated business object map 700, and as shown in the highlighted portion 728, a Customer Invoice Processing process component 726 in Customer Invoicing deployment unit 704 incorporates two business objects: a customer invoice request 710 and a customer invoice 708. A Project Processing process component 724 in a Project Management deployment unit 706 includes five business objects: a Project Request 718, a Project 720, a Project Snapshot 712, a Project Simulation 714, and a Project Template 722.
FIG. 8 is an illustration of an integration scenario model entity 800 (or "integration scenario"). An integration scenario is a realization of a given end-to-end business scenario. It consists of the process components and the interactions between them, which are required for its realization. A process component is only represented once in an integration scenario model, even though the actual flow in the software system might invoke the same process component multiple times. An integration scenario model entity describes at a high level the potential interaction between process components in one or more deployment units that are relevant to realization of the business scenario. For example, an integration scenario can be a set of process components and their interactions working together to realize a business
scenario to achieve a business objective, such as selling products to generate revenue. Internal details of process components are not described, nor are details of process component interactions (e.g., interfaces, operations and messages).
The illustrated integration scenario 800 is for a service procurement software application. The service procurement application is software that implements an end-to-end process used to procure services. The scenario 800 includes nine deployment units: a Financial Accounting unit 802, a Project Management unit 804, a Purchasing unit 806, a Supplier Invoicing unit 808, a Payment unit 810, a RFQ Processing unit 812, a Due Item Management unit 814, a Requisitioning unit 816, and a Human Capital Management unit 818.
The Financial Accounting deployment unit 802 includes an Accounting process component 803 that records all relevant business transactions.
The Project Management deployment unit 804 includes a Project Processing process component 820 that is responsible for structuring, planning, and executing measures or projects (e.g., short-term measures, complex projects, etc.).
The Purchasing deployment unit 806 includes four process components: a Purchase Request Processing process component 828, a Purchase Order Processing process component 830, a Purchasing Contract process component 832, and a Goods and Service Acknowledgement process component 833. The Purchase Request Processing process component 828 provides a request or instruction to the purchasing department to purchase specified goods or services in specified quantities within a specified time.
The Purchase Order Processing process component 830 includes a purchase order business object and a purchase order confirmation business object. The purchase order is 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 is a communication from a supplier to a purchaser to advise that a purchase order has been received. In particular, a purchase order confirmation may advise the purchaser of the supplier accepting the purchase order, or the supplier proposing changes to the purchase order, or the supplier not accepting the purchase order.
The Purchasing Contract process component 832 handles an agreement between a purchaser and a supplier that details the supply of goods or the performance of services at agreed conditions. The Purchasing Contract process component includes the purchasing contract business object. The Goods and Service Acknowledgement 833 includes a Goods and Service
Acknowledgement business object. The Goods and Service Acknowledgement business object is a document that states the recipient's, for example, a purchaser's, obligation to pay the supplier for goods received or services rendered. An invoice is normally created after the goods and service acknowledgement has been confirmed. The Supplier Invoicing deployment unit 808 includes a Supplier Invoice Processing process component 836. The Supplier Invoice Processing process component 836 includes a supplier invoice business object and a supplier invoice request business object. The supplier invoice is a document that states the recipient's obligation to pay the supplier for goods received or services rendered. The invoice may be created after the goods and service acknowledgment has been confirmed. The supplier invoice request is a document that is sent to invoice verification, advising that an invoice for specified quantities and prices is expected and may be created through evaluation settlement. The system uses the invoice request as a basis for invoice verification, as well as for the automatic creation of the invoice. The Payment deployment unit 810 includes a Payment Processing process component 838. The Payment Processing process component 838 is used to handle all incoming and outgoing payments as well as represent the main database for a liquidity status.
The RFQ deployment unit 812 includes an RFQ Processing process component 840. An RFQ Processing deployment unit includes a Request for Response business object and a Quote business object. The request for quotation (RFQ) is a description of materials and services that purchasers use to request responses from potential suppliers. Requests for quotation can be one of the following types: a request for (price) information, a request for quote that may run over a certain period of time, a request for proposal in complex purchasing situation or live auctions that may be performed over a short time frame. The quote is a response to a request for quotation in which a supplier offers to sell goods and services at a certain price. The quote can be subject to complex pricing and conditions.
The Due Item Management deployment unit 814 includes a Due Item Processing process component 842. The Due Item Processing process component 842 is used to manage all payables, receivables from service and supply and corresponding sales including a withholding tax. The Requisitioning deployment unit 816 includes an Internal Request Processing process component 844. The Internal Request Processing deployment unit 816 includes an Internal Request business object. Employees of a company may make an internal request for the procurement of goods or services for the company. For example, the employees may order stationery, computer hardware, or removal services by creating an internal request. The internal request can be fulfilled by an issue of a purchase request to the purchasing department, a reservation of goods from stock, or a production request.
The Human Capital Management deployment unit 818 includes a Time and Labor Management process component 848. The Time and Labor Management process component 848 supports the definition of employees' planned working time as well as the recording or the actual working times and absences and their evaluation.
The foundation layer includes a Source of Supply Determination process component 834, a Customer Invoice Processing at Supplier process component 837, a Sales Order Processing at Supplier process component 846, a Payment Processing at Business Partner process component 850, a Bank Statement Creation at Bank process component 852, and a Payment Order Processing at House Bank process component 854.
The service procurement design includes a Source of Supply Determination process component 834 that uses two business objects to determine a source of supply: a supply quota arrangement business object, and a source of supply business object. A supply quota arrangement is a distribution of material requirements or goods to different sources of supply, business partners, or organizational units within a company. An example of the use of supply quota arrangements is the distribution of material requirements between in-house production and different sources for external procurement. A supply quota arrangement can also define the distribution of goods to customers in case of excess production or shortages. A source of supply is an object that describes a logical link between a possible source of products and a possible target.
A number of external process components, described below, will be used to describe the architectural design. These include a Customer Invoice Processing at Supplier process component 837, a Sales Order Processing at Supplier process component 846, a Payment Processing at Business Partner process component 850, a Bank Statement Creation at Bank process component 852, and a Payment Order Processing at House Bank process component 854.
The Supplier Invoicing deployment unit 808 receives messages from a Customer Invoice at Supplier process component 837, which is used, at a supplier, to charge a customer for the delivery of goods or services. The service procurement design includes a Sales Order Processing at Supplier process component 846 that may receive messages from the RPQ Processing process component 840. The Sales Order Processing at Supplier process component 846 handles customers' requests to a company for delivery of goods or services at a certain time. The requests are received by a sales area, which is then responsible for fulfilling the contract. The Payment Processing at Business Partner process component 850, the Bank
Statement Creation at Bank process component 852, and the Payment Order Processing at House Bank process component 854 may interact with the Payment Processing process component 838. The Payment Processing process component 838 may send updates to a Payment Processing at Business Partner process component 850, which is used to handle, at business partner, all incoming and outgoing payments and represent the main data base for the liquidity status. The Payment Processing process component 838 also receives messages from the Bank Statement Creation at Bank process component 852. The message may include a bank statement for a bank account. The Payment Processing process component 838 sends messages to the Payment Order Processing at House Bank process component 854. The message may include a Bank Payment Order that is a Payment Order which will be sent to a house bank. The bank payment order may contain bank transfers as well as direct debits.
The connector 829 symbol is a graphical convention to improve graphical layout for human reading. A connector is a placeholder for another process component. For example, the illustrated connector 829 would be a placeholder for Accounting process component 803.
FIGS. 9-9 A illustrate an integration scenario catalog (or "scenario catalog") 900. A scenario catalog presents an organized view of a collection of integration scenarios. The view can be organized in a number of ways, including hierarchically or associatively based on one or more attributes of the integration scenarios. The illustrated integration scenario catalog 900 represents a structured directory of integration scenarios. For example, a scenario directory Sell from Stock 902 representing a family of scenarios includes two entries: a reference to a Sell from Stock integration scenario 904, and a reference to a Sell from Stock for Delivery Schedules integration scenario 906.
FIGS. 10A- 1OB illustrate the GUI 204 (from FIG. 2) for presenting one or more graphical depictions of views of a model and modeling entities. Each view can present a different level of detail or emphasize a different aspect of the model. This allows for different classes of users to focus on the information that is important for carrying out their duties without being distracted by extraneous detail. One or more of the following graphical depictions can be presented: a scenario catalog 1002, an integration scenario model 1004, a PCIM 1008, and a PCM 1010. hi one variation, the GUI 204 allows a user to "drill down" to increasing levels of model detail. For example, selection of a scenario icon 1006 in the integration scenario catalog 1002 can cause an associated integration scenario model 1004 to be presented. Selection of a graphical representation of a process component 1014 in the integration scenario can cause an associated PCM 1010 for the process component to be presented. Likewise, selection of an arc 1012 connecting process components in different deployment units can cause a PCIM 1008 for the process components connected by the arc to be presented.
In one implementation, the aforementioned graphical depictions can be presented singularly or in combination with each other in the GUI 204. Moreover, a given graphical depiction can present all of its underlying information or a portion thereof, while allowing other portions to be viewed through a navigation mechanism, e.g., user selection of a graphical element, issuance of a command, or other suitable means.
Information can also be represented by colors in the display of model entities. For example, color can be used to distinguish types of business objects, types of process agents and types of interfaces.
FIG. 1 1 is an illustration of process component interaction with an external process component, representing an external system. As discussed earlier, a process component can interact with an external process component. This interaction can be modeled even though the interfaces of the external process are unknown, as is the case in this example. (However, if this information is known, it can be incorporated into the model.)
In this example, potential interactions are shown between a Purchase Order Processing process component 1102 and an external Sales Order Processing at Supplier process component 1104. The Purchase Order Processing process component 1102 includes a Purchase Order business object 1106 which is 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 Request Purchase Order to Supplier outbound process agent 1108 can request invocation of a Request Purchase Order Creation operation 1112, a Request Purchase Order Cancellation operation 1114, or a Request Purchase Order Change operation 1116 in an Ordering Out interface 1110. The Request Purchase Order Cancellation operation 1114 requests a Cancellation of a
Purchase Order that was formerly ordered at a supplier which creates a Purchase Order Cancellation Request message 1118. The Request Purchase Order Change operation 1116 requests a change of a purchase order that was formerly ordered at the supplier which creates a Purchase Order Change Request message 1120. The Request Purchase Order Creation operation 1112 requests a purchase order from a supplier which creates a Purchase Order Request message 1122.
Upon receiving a create, a change, or a cancellation message, the Sales Order Processing process component 1104 may create a Purchase Order Confirmation message 1123 to update the Purchase Order Processing process component 1102. To complete the update, a Create Purchase Order Confirmation operation 1124, included in an Ordering In interface 1125, may transfer the update to the Purchase Order Confirmation business object 1128 by using a Create Purchase Order inbound process agent 1 126. The Purchase Order Confirmation business object 1128 is 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.
FIG. 12 is an illustration 1200 of process component interaction through a mapping model element 1214 (or "mapper"). As discussed above, if message formats between two process component operations do not match, the message can be transformed by a mapper on its way from the outbound process agent to the inbound process agent. For example, output process agent 1216 associated with process component 1202 can send a message 1210 to inbound process agent 1217 in process component 1204 by way of operation 1218 in interface 1206. If the message format associated with operation 1218 does not match that of operation 1220, a transformation of the message from its original format to a format compatible with operation 1220 can be described by a mapper 1214 interposed between the two process agents. The mapper 1214 generates a new message 1212 based on the original message 1210, where the new message has a format that is compatible with operation 1220 in interface 1208.
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.
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 method comprising: defining a plurality of business objects, each business object operable to encapsulate business data and associated with exactly one process component, each of the process components characterizing software implementing a respective and distinct process, and each of the process components defining a respective at least one service interface for communicating and interacting with business objects in other process components, and all communication and interaction between process components taking place through the respective interfaces of the process components; and defining interactions among the plurality of business objects, wherein the interactions among business objects in different deployment units occur solely via the process component interfaces.
2. A method as in claim 1, wherein the process components characterize inbound operations to handle incoming messages associated with a modification of reading of data encapsulated in a business object associated with the process component.
3. A method as in claim 1 or 2, wherein the process components characterize outbound operations to handle outgoing messages associated with a modification or reading of data encapsulated in at least one business object associated with another process component.
4. A method as in anyone of the preceding claims, wherein the defining a plurality of process components comprises: generating, for each process component, at least one process agent, each process agent enabling communications between a business object associated with the process component and a business object associated with any other process component.
5. A method as in claim 4, wherein at least one of the process agents is an inbound process agent characterizing an inbound operation to handle incoming messages.
6. A method as in claim 4 or 5, wherein at least one of the inbound process agents is operable to receive a message of a first type and convert it into a message of a second type.
7. A method as in anyone of claims 4 to 6, wherein at least one of the process agents is an outbound process agent characterizing an outbound operation to transmit outgoing messages to an external process component.
8. A method as in anyone of claims 4 to 7, wherein each process agent is operable to communicate through the service interface of its respective process component.
9. A method as in anyone of the preceding claims, further comprising: logically associating a plurality of process components to realize a business scenario.
10. A method as in anyone of the preceding claims, further comprising: generating a plurality of integration scenarios, each integration scenario comprising a plurality of logically associated process components to realize a business scenario; and populating a catalog with the generated integration scenarios.
1 1. A method as in anyone of the preceding claims, further comprising: polling a data repository to obtain stored data characterizing the plurality of deployment units.
12. A method as in anyone of the preceding claims, wherein at least a portion of communications between process components within a deployment unit is not message based.
13. A method as in anyone of the preceding claims, wherein a first group of one or more process components is associated with a first deployment unit and a second group of one or more process components is associated with a second deployment unit, the deployment units characterizing independently operable software.
14. A method as in claim 13, wherein at least one of the deployment units comprises at least one business object that is not associated with a process component.
15. A method as in claim 14, wherein at least two of the deployment units are deployed on separate hardware platforms.
16. A method comprising: defining a plurality of business objects, each business object operable to encapsulate business data; and associating each of the business objects with exactly one process component, each of the process components characterizing software implementing a respective and distinct process, and each of the process components defining a respective at least one service interface for communicating and interacting with other business objects in other process components, and all communication and interaction between process components taking place through the respective interfaces of the process components.
17. A method as in claim 16, further comprising: grouping process components to form a plurality of deployment units.
18. A method as in claim 17, further comprising: logically associating the deployment units to realize a business scenario.
19. A method comprising: defining a plurality of business objects in a foundation layer, each foundation layer business object operable to encapsulate business data and associated with one or more process components, each of the process components characterizing software implementing a respective and distinct process, and each of the process components defining a respective at least one service interface for communicating and interacting with business objects in other process components, and all communication and interaction between process components taking place through the respective interfaces of the process components; and defining interactions among the plurality of foundation layer business objects, wherein the interactions among business objects in different business objects occur solely via the process component interfaces.
20. A method as in claim 19, further comprising: defining a plurality of business objects external to the foundation layer, each external business object being associated with exactly one process component.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/322,612 | 2005-12-30 | ||
US11/322,612 US8407664B2 (en) | 2005-12-30 | 2005-12-30 | Software model business objects |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2007077018A1 true WO2007077018A1 (en) | 2007-07-12 |
Family
ID=37895832
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2006/012621 WO2007077018A1 (en) | 2005-12-30 | 2006-12-29 | Software model business objects |
Country Status (2)
Country | Link |
---|---|
US (1) | US8407664B2 (en) |
WO (1) | WO2007077018A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8252766B2 (en) | 2002-12-09 | 2012-08-28 | Cbt Development Limited | Use of spongosine for the treatment of pain |
Families Citing this family (90)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8327319B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Software model process interaction |
US8448137B2 (en) | 2005-12-30 | 2013-05-21 | Sap Ag | Software model integration scenarios |
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 |
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 |
US8396731B2 (en) | 2005-12-30 | 2013-03-12 | Sap Ag | Architectural design for service procurement application software |
US8688495B2 (en) * | 2005-12-30 | 2014-04-01 | Sap Ag | Architectural design for time recording application software |
US8402426B2 (en) | 2005-12-30 | 2013-03-19 | Sap Ag | Architectural design for make to stock application software |
US8321831B2 (en) | 2005-12-30 | 2012-11-27 | Sap Ag | Architectural design for internal projects application software |
US8522194B2 (en) | 2005-12-30 | 2013-08-27 | Sap Ag | Software modeling |
US20070156550A1 (en) * | 2005-12-30 | 2007-07-05 | Der Emde Martin V | Architectural design for cash and liquidity management application software |
US8407664B2 (en) | 2005-12-30 | 2013-03-26 | Sap Ag | Software model business objects |
US8380553B2 (en) | 2005-12-30 | 2013-02-19 | Sap Ag | Architectural design for plan-driven procurement application software |
US8676617B2 (en) | 2005-12-30 | 2014-03-18 | Sap Ag | Architectural design for self-service procurement application software |
US20070233539A1 (en) * | 2006-03-30 | 2007-10-04 | Philipp Suenderhauf | Providing human capital management software application as enterprise services |
US20070233575A1 (en) * | 2006-03-30 | 2007-10-04 | Arthur Berger | Architectural design for strategic sourcing application software |
US8438119B2 (en) | 2006-03-30 | 2013-05-07 | Sap Ag | Foundation layer for services based enterprise software architecture |
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 |
US8396749B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing customer relationship management application as enterprise services |
US8396761B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing product catalog software application as enterprise services |
US8538864B2 (en) | 2006-03-30 | 2013-09-17 | Sap Ag | Providing payment software application as enterprise services |
US8321832B2 (en) | 2006-03-31 | 2012-11-27 | Sap Ag | Composite application modeling |
US8312416B2 (en) * | 2006-04-13 | 2012-11-13 | Sap Ag | Software model business process variant types |
US9606772B2 (en) * | 2006-11-21 | 2017-03-28 | International Business Machines Corporation | Business process diagram data collection |
US8041588B2 (en) * | 2006-11-21 | 2011-10-18 | International Business Machines Corporation | Business process diagram visualization using heat maps |
US7957992B2 (en) * | 2006-11-21 | 2011-06-07 | International Business Machines Corporation | Modification of a diagram for business process optimization |
US7953619B2 (en) * | 2006-11-21 | 2011-05-31 | International Business Machines Corporation | Business process diagram visualization using timeline-based heat maps |
US8166465B2 (en) * | 2007-04-02 | 2012-04-24 | International Business Machines Corporation | Method and system for composing stream processing applications according to a semantic description of a processing goal |
US8098248B2 (en) | 2007-04-02 | 2012-01-17 | International Business Machines Corporation | Method for semantic modeling of stream processing components to enable automatic application composition |
US8307372B2 (en) * | 2007-04-02 | 2012-11-06 | International Business Machines Corporation | Method for declarative semantic expression of user intent to enable goal-driven information processing |
US8863102B2 (en) * | 2007-04-02 | 2014-10-14 | International Business Machines Corporation | Method and system for assembling information processing applications based on declarative semantic specifications |
US8370812B2 (en) | 2007-04-02 | 2013-02-05 | International Business Machines Corporation | Method and system for automatically assembling processing graphs in information processing systems |
US7882485B2 (en) * | 2007-04-02 | 2011-02-01 | International Business Machines Corporation | Method for modeling components of an information processing application using semantic graph transformations |
US7899861B2 (en) * | 2007-04-02 | 2011-03-01 | International Business Machines Corporation | Method for declarative semantic expression of user intent to enable goal-driven stream processing |
US8117233B2 (en) * | 2007-05-14 | 2012-02-14 | International Business Machines Corporation | Method and system for message-oriented semantic web service composition based on artificial intelligence planning |
US8671032B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Providing payment software application as enterprise services |
US8315900B2 (en) | 2007-12-31 | 2012-11-20 | Sap Ag | Architectural design for self-service procurement application software |
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 |
US8510143B2 (en) | 2007-12-31 | 2013-08-13 | Sap Ag | Architectural design for ad-hoc goods movement software |
US8671034B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Providing human capital management software application as enterprise services |
US8818884B2 (en) | 2008-09-18 | 2014-08-26 | Sap Ag | Architectural design for customer returns handling application software |
US8380549B2 (en) * | 2008-09-18 | 2013-02-19 | Sap Ag | Architectural design for embedded support application software |
US8315926B2 (en) | 2008-09-18 | 2012-11-20 | Sap Ag | Architectural design for tax declaration application software |
US8595077B2 (en) | 2008-09-18 | 2013-11-26 | Sap Ag | Architectural design for service request and order management application software |
US8401928B2 (en) * | 2008-09-18 | 2013-03-19 | Sap Ag | Providing supplier relationship management software application as enterprise services |
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 |
US8321250B2 (en) | 2008-09-18 | 2012-11-27 | Sap Ag | Architectural design for sell from stock application software |
US20100070556A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Architectural Design for Data Migration Application Software |
US8326706B2 (en) | 2008-09-18 | 2012-12-04 | Sap Ag | Providing logistics execution application as enterprise services |
US8386325B2 (en) | 2008-09-18 | 2013-02-26 | Sap Ag | Architectural design for plan-driven procurement application software |
US8429597B2 (en) * | 2008-11-21 | 2013-04-23 | Sap Ag | Software for integrated modeling of user interfaces with applications |
US20100131916A1 (en) * | 2008-11-21 | 2010-05-27 | Uta Prigge | Software for modeling business tasks |
US8401908B2 (en) | 2008-12-03 | 2013-03-19 | Sap Ag | Architectural design for make-to-specification application software |
US8321306B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for selling project-based services application software |
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 |
US8321308B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for manual invoicing application software |
US8671035B2 (en) | 2008-12-11 | 2014-03-11 | Sap Ag | Providing payroll software application as enterprise services |
US20100153149A1 (en) * | 2008-12-12 | 2010-06-17 | Sap Ag | Software for model-based configuration constraint generation |
US20100153150A1 (en) * | 2008-12-12 | 2010-06-17 | Sap Ag | Software for business adaptation catalog modeling |
US20100169132A1 (en) * | 2008-12-29 | 2010-07-01 | Tobias Hoppe-Boeken | Executing a business transaction in an enterprise system using business data obtained from heterogeneous sources |
US8234308B2 (en) * | 2009-12-22 | 2012-07-31 | Sap Ag | Deliver application services through business object views |
US8826227B2 (en) * | 2011-06-08 | 2014-09-02 | International Business Machines Corporation | Computer aided visualization of a business object model lifecycle |
US20130262189A1 (en) * | 2012-04-02 | 2013-10-03 | International Business Machines Corporation | Analyzing metered cost effects of deployment patterns in a networked computing environment |
CN103377263B (en) * | 2012-04-28 | 2017-03-01 | 阿里巴巴集团控股有限公司 | A kind of screening technique of business object and device |
US20140210838A1 (en) * | 2013-01-29 | 2014-07-31 | Sap Ag | Visual business objects |
US9021432B2 (en) | 2013-03-05 | 2015-04-28 | Sap Se | Enrichment of entity relational model |
US8719217B1 (en) | 2013-03-15 | 2014-05-06 | Decisyon, Inc. | Systems, devices, and methods for generation of contextual objects mapped by dimensional data to data measures |
US10235649B1 (en) | 2014-03-14 | 2019-03-19 | Walmart Apollo, Llc | Customer analytics data model |
US11080734B2 (en) | 2013-03-15 | 2021-08-03 | Cdk Global, Llc | Pricing system for identifying prices for vehicles offered by vehicle dealerships and other entities |
WO2015103308A1 (en) | 2014-01-02 | 2015-07-09 | Decisyon, Inc. | Systems, devices, and methods for exchanging and processing data measures and objects |
US10733555B1 (en) | 2014-03-14 | 2020-08-04 | Walmart Apollo, Llc | Workflow coordinator |
US10346769B1 (en) | 2014-03-14 | 2019-07-09 | Walmart Apollo, Llc | System and method for dynamic attribute table |
US10235687B1 (en) | 2014-03-14 | 2019-03-19 | Walmart Apollo, Llc | Shortest distance to store |
US10565538B1 (en) | 2014-03-14 | 2020-02-18 | Walmart Apollo, Llc | Customer attribute exemption |
EP3265905A4 (en) * | 2015-03-06 | 2018-11-21 | Cisco Technology, Inc. | Systems and methods for generating data visualization applications |
US9800672B2 (en) | 2015-04-09 | 2017-10-24 | Eugene Edwin Nelson | Computer work distribution system and method |
US10853769B2 (en) | 2016-04-21 | 2020-12-01 | Cdk Global Llc | Scheduling an automobile service appointment in a dealer service bay based on diagnostic trouble codes and service bay attributes |
US10867285B2 (en) | 2016-04-21 | 2020-12-15 | Cdk Global, Llc | Automatic automobile repair service scheduling based on diagnostic trouble codes and service center attributes |
US10452774B2 (en) * | 2016-12-13 | 2019-10-22 | Bank Of America Corporation | System architecture framework |
US11190608B2 (en) | 2018-03-21 | 2021-11-30 | Cdk Global Llc | Systems and methods for an automotive commerce exchange |
US11501351B2 (en) * | 2018-03-21 | 2022-11-15 | Cdk Global, Llc | Servers, systems, and methods for single sign-on of an automotive commerce exchange |
US11080105B1 (en) | 2020-11-18 | 2021-08-03 | Cdk Global, Llc | Systems, methods, and apparatuses for routing API calls |
US11514021B2 (en) | 2021-01-22 | 2022-11-29 | Cdk Global, Llc | Systems, methods, and apparatuses for scanning a legacy database |
US11803535B2 (en) | 2021-05-24 | 2023-10-31 | Cdk Global, Llc | Systems, methods, and apparatuses for simultaneously running parallel databases |
Family Cites Families (278)
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 |
WO1995008148A1 (en) | 1993-09-13 | 1995-03-23 | Taligent, Inc. | Multimedia data routing system |
US5550734A (en) | 1993-12-23 | 1996-08-27 | The Pharmacy Fund, Inc. | Computerized healthcare accounts receivable purchasing collections securitization and management system |
US5560005A (en) | 1994-02-25 | 1996-09-24 | Actamed Corp. | Methods and systems for object-based relational distributed databases |
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 |
US6272672B1 (en) | 1995-09-06 | 2001-08-07 | Melvin E. Conway | Dataflow processing with events |
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 |
US6446092B1 (en) | 1996-11-01 | 2002-09-03 | Peerdirect Company | Independent distributed database system |
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 |
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 |
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 |
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 |
AU5791899A (en) | 1998-08-27 | 2000-03-21 | 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 |
US6533168B1 (en) | 1999-05-27 | 2003-03-18 | Peter N. Ching | Method and apparatus for computer-readable purchase receipts using multi-dimensional bar codes |
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 |
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 |
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 |
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 |
US6601234B1 (en) * | 1999-08-31 | 2003-07-29 | Accenture Llp | Attribute dictionary in a business logic services environment |
US7797195B2 (en) | 1999-09-17 | 2010-09-14 | Michael Jay Langhammer | Merchant-affiliated direct wholesale marketing and fulfillment system |
US7047219B1 (en) | 1999-10-04 | 2006-05-16 | Trade Finance Systems, Inc. | Trade finance automation system |
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 |
AU780914B2 (en) * | 1999-12-10 | 2005-04-28 | Innovation Group/Mtw, Inc., The | A method of component-based system development |
US7103605B1 (en) * | 1999-12-10 | 2006-09-05 | A21, Inc. | Timeshared electronic catalog system and method |
US7798417B2 (en) * | 2000-01-03 | 2010-09-21 | Snyder David M | Method for data interchange |
US6764009B2 (en) * | 2001-05-30 | 2004-07-20 | Lightwaves Systems, Inc. | Method for tagged bar code data interchange |
US7003720B1 (en) * | 2000-01-07 | 2006-02-21 | Abf Freight Sysems. Inc. | Electronic shipment planner |
US6446045B1 (en) * | 2000-01-10 | 2002-09-03 | Lucinda Stone | Method for using computers to facilitate and control the creating of a plurality of functions |
US6889197B2 (en) * | 2000-01-12 | 2005-05-03 | Isuppli Inc. | Supply chain architecture |
US6493716B1 (en) | 2000-01-19 | 2002-12-10 | International Business Machines Corporation | Group communication system with flexible member model |
US6882892B2 (en) | 2000-01-21 | 2005-04-19 | Amcor Limited | System and method for specifying elements in a packaging 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 |
WO2001059569A2 (en) | 2000-02-09 | 2001-08-16 | Apriva, Inc. | Communication systems, components, and methods with programmable wireless devices |
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 |
WO2001082200A2 (en) | 2000-04-27 | 2001-11-01 | Eastman Chemical Company | 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 |
US7225240B1 (en) * | 2000-05-20 | 2007-05-29 | Ciena Corporation | Decoupling processes from hardware with logical identifiers |
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 |
US7072855B1 (en) | 2000-07-24 | 2006-07-04 | Omnicell, Inc. | Systems and methods for purchasing, invoicing and distributing items |
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 |
AU2002227376A1 (en) * | 2000-10-30 | 2002-05-15 | Tririga, Inc. | Susiness asset management system |
AU2002223271A1 (en) | 2000-11-15 | 2002-05-27 | Spc Holdings 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 |
JP4301815B2 (en) * | 2000-12-22 | 2009-07-22 | アイデンティティ・マトリックス・メディカル・インコーポレーテッド | Multi-agent joint 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 |
US7720714B2 (en) | 2001-01-19 | 2010-05-18 | Globalserve Computer Services, Ltd. | System and method for facilitating electronic procurement based on negotiated contracts |
US7313534B2 (en) | 2001-01-22 | 2007-12-25 | W.W. Grainger, Inc. | System and method for predictive maintenance and service parts fulfillment in a supply chain |
US7324966B2 (en) * | 2001-01-22 | 2008-01-29 | W.W. Grainger | Method for fulfilling an order in an integrated supply chain management system |
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 |
US7299202B2 (en) | 2001-02-07 | 2007-11-20 | Exalt Solutions, Inc. | Intelligent multimedia e-catalog |
US7899721B2 (en) | 2001-02-27 | 2011-03-01 | Accenture Global Services Gmbh | E-commerce system, method and computer program product |
US20030069774A1 (en) | 2001-04-13 | 2003-04-10 | Hoffman George Harry | System, method and computer program product for distributor/supplier selection in a supply chain management framework |
US6954736B2 (en) | 2001-03-23 | 2005-10-11 | Restaurant Services, Inc. | System, method and computer program product for order confirmation in a supply chain management framework |
US7120896B2 (en) * | 2001-10-31 | 2006-10-10 | Vitria Technology, Inc. | Integrated business process modeling environment and models created thereby |
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 |
US6904399B2 (en) * | 2001-04-24 | 2005-06-07 | Key Safety Systems, Inc. | Simplified modeling software interface and method |
US20020161907A1 (en) | 2001-04-25 | 2002-10-31 | Avery Moon | Adaptive multi-protocol communications system |
US7117447B2 (en) | 2001-06-08 | 2006-10-03 | Mci, Llc | Graphical user interface (GUI) based call application system |
US7761319B2 (en) | 2001-06-08 | 2010-07-20 | Click Acqusitions, Inc. | Supply chain management |
US6813587B2 (en) * | 2001-06-22 | 2004-11-02 | Invensys Systems, Inc. | Remotely monitoring/diagnosing distributed components of a supervisory process control and manufacturing information application from a central location |
WO2003001377A2 (en) * | 2001-06-22 | 2003-01-03 | Wonderware Corporation | Installing supervisory process control and manufacturing software from a remote location and maintaining configuration data links in a run-time environment |
US7069536B2 (en) | 2001-06-28 | 2006-06-27 | International Business Machines Corporation | Method, system, and program for executing a workflow |
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 |
US7222786B2 (en) | 2001-11-14 | 2007-05-29 | Sap Ag | Inventory early warning agent with correction by error correlation calculation |
US7200569B2 (en) | 2001-11-26 | 2007-04-03 | Hewlett-Packard Development Company, L.P. | Intelligent apparatus, system and method for financial data computation and analysis |
AU2002351195A1 (en) * | 2001-11-28 | 2003-06-10 | Isuppli Corporation | Supply chain network |
US7383201B2 (en) * | 2001-12-05 | 2008-06-03 | Canon Kabushiki Kaisha | Demand forecast device, method, and program product |
US7376604B1 (en) * | 2001-12-27 | 2008-05-20 | Goldman Sachs & Co. | Method for investing yield restricted monies |
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 |
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 |
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 |
WO2004023325A1 (en) | 2002-09-04 | 2004-03-18 | Mentor Graphics (Holdings) Ltd. | Polymorphic computational system and method |
EP1403793A1 (en) | 2002-09-27 | 2004-03-31 | Sap Ag | Method for automatic integrated document filing in the logging of business transactions |
US7536325B2 (en) * | 2002-09-30 | 2009-05-19 | Canadian National Railway Company | Method and system for generating account reconciliation data |
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 |
US20040181470A1 (en) * | 2003-03-11 | 2004-09-16 | Electronic Data Systems Corporation | System, method, and computer program product for taxation of online transactions |
US8510179B2 (en) | 2003-03-24 | 2013-08-13 | Siebel Systems, Inc. | Inventory transaction common object |
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 |
WO2004099896A2 (en) * | 2003-05-12 | 2004-11-18 | An Mo Jeong | Method and system of developing a software with utilizing extented metadata of component under component-based development environment |
US20040236639A1 (en) | 2003-05-20 | 2004-11-25 | Arun Candadai | Dynamic data collaboration |
US20040243489A1 (en) | 2003-05-27 | 2004-12-02 | International Business Machines Corporation | Expense accounting data management based on electronic expense document |
US7546575B1 (en) * | 2003-06-09 | 2009-06-09 | Dillman Frederick J | System and method for using blueprints to provide a software solution for an enterprise |
US7406716B2 (en) | 2003-06-10 | 2008-07-29 | Kabushiki Kaisha Toshiba | Software IP providing system and method, software IP obtaining method, and IP core designing and manufacturing method |
US8036962B2 (en) | 2003-06-13 | 2011-10-11 | Sap Ag | Systems and methods for determining payers in a billing environment |
US7742985B1 (en) * | 2003-06-26 | 2010-06-22 | Paypal Inc. | Multicurrency exchanges between participants of a network-based transaction facility |
US20050010501A1 (en) * | 2003-07-10 | 2005-01-13 | Ward Lycurgus B. | Internet-based back office payroll service and method thereof |
US7257254B2 (en) | 2003-07-24 | 2007-08-14 | Sap Ag | Method and system for recognizing time |
US20050033588A1 (en) | 2003-08-04 | 2005-02-10 | Mario Ruiz | Information system comprised of synchronized software application moduless with individual databases for implementing and changing business requirements to be automated |
US8121913B2 (en) | 2003-08-19 | 2012-02-21 | Swiss Reinsurance Company Ltd. | Architecture for account reconciliation |
US8060553B2 (en) | 2003-08-27 | 2011-11-15 | International Business Machines Corporation | Service oriented architecture for a transformation function in a data integration platform |
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 |
US20050240592A1 (en) | 2003-08-27 | 2005-10-27 | Ascential Software Corporation | Real time data integration for supply chain management |
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 |
WO2005029275A2 (en) | 2003-09-19 | 2005-03-31 | Thomson Global Resources Ag | 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 |
WO2005059690A2 (en) | 2003-12-12 | 2005-06-30 | 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 |
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 |
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 |
US8655697B2 (en) | 2004-04-16 | 2014-02-18 | Sap Aktiengesellschaft | Allocation table generation from assortment planning |
US7689477B2 (en) | 2004-04-16 | 2010-03-30 | Sap Aktiengesellschaft | Apparatus and program product for generating an allocation table in a computerized procurement system |
US8352423B2 (en) * | 2004-05-07 | 2013-01-08 | Inceptia Llc | Apparatus and method for providing streaming data |
US9026455B2 (en) | 2004-05-14 | 2015-05-05 | Sap Ag | Methods and systems for processing stock in a storage facility |
WO2005114381A2 (en) * | 2004-05-14 | 2005-12-01 | 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 |
EP1782366A2 (en) | 2004-06-04 | 2007-05-09 | Sap Ag | Consistent set of interfaces derived from a business object |
US20050289531A1 (en) * | 2004-06-08 | 2005-12-29 | Daniel Illowsky | Device interoperability tool set and method for processing interoperability application specifications into interoperable application packages |
US20080162221A1 (en) * | 2004-06-14 | 2008-07-03 | Symphonyrpm, Inc. | Decision object for associating a plurality of business plans |
US8694397B2 (en) | 2004-06-18 | 2014-04-08 | 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 |
US20060074704A1 (en) | 2004-10-01 | 2006-04-06 | Microsoft Corporation | Framework to model cross-cutting behavioral concerns in the workflow domain |
US7451432B2 (en) | 2004-10-01 | 2008-11-11 | Microsoft Corporation | Transformation of componentized and extensible workflow to a declarative format |
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 |
US7631291B2 (en) | 2004-10-01 | 2009-12-08 | Microsoft Corporation | Declarative representation for an extensible workflow model |
US20060089886A1 (en) * | 2004-10-27 | 2006-04-27 | Anthony Wong | E-commerce business methodologies for supply and demand chain management |
US8352478B2 (en) * | 2004-10-29 | 2013-01-08 | Sap Ag | Master data framework |
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 |
US8744937B2 (en) | 2005-02-25 | 2014-06-03 | Sap Ag | Consistent set of interfaces derived from a business object model |
US7681176B2 (en) * | 2005-03-04 | 2010-03-16 | Microsoft Corporation | Generating a graphical designer application for developing graphical models |
US20060206352A1 (en) | 2005-03-14 | 2006-09-14 | Pulianda Arunkumar G | System for seamless enablement of compound enterprise-processes |
US7890389B2 (en) | 2005-05-17 | 2011-02-15 | Sap Ag | Methods and systems for grouping and managing stock requests |
WO2006133157A2 (en) * | 2005-06-07 | 2006-12-14 | Kyube Sal | Computer method and apparatus for developing web pages and applications |
US7822682B2 (en) | 2005-06-08 | 2010-10-26 | Jpmorgan Chase Bank, N.A. | System and method for enhancing supply chain transactions |
WO2006135756A1 (en) * | 2005-06-09 | 2006-12-21 | Intepoint, Llc | Multi-infrastructure modeling system |
US7827554B2 (en) | 2005-06-20 | 2010-11-02 | Microsoft Corporation | Multi-thread multimedia processing |
US20080065437A1 (en) * | 2005-07-06 | 2008-03-13 | Dybvig Alan J | System and Method for Budgeting, Planning, and Supply Chain Management |
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 |
CA2620993A1 (en) | 2005-09-02 | 2007-03-08 | Ecmarket Inc. | Method and system for exchanging business documents |
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 |
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 |
EP1806686A1 (en) | 2005-12-05 | 2007-07-11 | Sap Ag | Restriction of the number of locations |
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 |
US8522194B2 (en) * | 2005-12-30 | 2013-08-27 | Sap Ag | Software modeling |
US8396731B2 (en) | 2005-12-30 | 2013-03-12 | Sap Ag | Architectural design for service procurement application software |
US8448137B2 (en) * | 2005-12-30 | 2013-05-21 | Sap Ag | Software model integration scenarios |
US8407664B2 (en) | 2005-12-30 | 2013-03-26 | Sap Ag | Software model business objects |
US8380553B2 (en) * | 2005-12-30 | 2013-02-19 | Sap Ag | Architectural design for plan-driven procurement application software |
US8316344B2 (en) * | 2005-12-30 | 2012-11-20 | Sap Ag | Software model deployment units |
US8326703B2 (en) * | 2005-12-30 | 2012-12-04 | Sap Ag | Architectural design for product catalog management application software |
US8327319B2 (en) * | 2005-12-30 | 2012-12-04 | Sap Ag | Software model process interaction |
US20070156500A1 (en) * | 2005-12-30 | 2007-07-05 | Wilfried Merkel | Architectural design for sell from stock application software |
US8676617B2 (en) | 2005-12-30 | 2014-03-18 | Sap Ag | Architectural design for self-service procurement application software |
US20070156550A1 (en) * | 2005-12-30 | 2007-07-05 | Der Emde Martin V | Architectural design for cash and liquidity management application software |
US8660904B2 (en) | 2005-12-30 | 2014-02-25 | Sap Ag | Architectural design for service request and order management application software |
US20070174145A1 (en) * | 2005-12-30 | 2007-07-26 | Stephan Hetzer | Controlling logistics execution in a computer application |
US8370794B2 (en) * | 2005-12-30 | 2013-02-05 | Sap Ag | Software model process component |
US8688495B2 (en) * | 2005-12-30 | 2014-04-01 | Sap Ag | Architectural design for time recording application software |
US20080275713A9 (en) | 2005-12-30 | 2008-11-06 | Shai Alfandary | Architectural design for physical inventory application software |
US20070198391A1 (en) | 2006-02-21 | 2007-08-23 | Deutsche Boerse Ag | Method and system for conducting a block auction |
US8442850B2 (en) | 2006-03-30 | 2013-05-14 | Sap Ag | Providing accounting software application as enterprise services |
US20070233575A1 (en) | 2006-03-30 | 2007-10-04 | Arthur Berger | Architectural design for strategic sourcing application software |
US8396749B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing customer relationship management application as enterprise services |
US8321832B2 (en) | 2006-03-31 | 2012-11-27 | Sap Ag | Composite application modeling |
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 |
WO2008005102A2 (en) | 2006-05-13 | 2008-01-10 | Sap Ag | Consistent set of interfaces derived from a business object model |
US7644390B2 (en) * | 2006-08-14 | 2010-01-05 | Payman Khodabandehloo | Design tool and methodology for enterprise software applications |
US7624371B2 (en) | 2006-10-16 | 2009-11-24 | Invensys Systems, Inc. | Extensible automation development environment |
US20090037492A1 (en) | 2007-07-31 | 2009-02-05 | Ahmad Baitalmal | Framework for Synchronizing Applications |
US20090037287A1 (en) | 2007-07-31 | 2009-02-05 | Ahmad Baitalmal | Software Marketplace and Distribution System |
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 |
US8386325B2 (en) * | 2008-09-18 | 2013-02-26 | Sap Ag | Architectural design for plan-driven procurement application software |
US20100070336A1 (en) * | 2008-09-18 | 2010-03-18 | Sap Ag | Providing Customer Relationship Management Application as Enterprise Services |
-
2005
- 2005-12-30 US US11/322,612 patent/US8407664B2/en active Active
-
2006
- 2006-12-29 WO PCT/EP2006/012621 patent/WO2007077018A1/en active Application Filing
Non-Patent Citations (2)
Title |
---|
PILHOFER F: "Writing and Using CORBA Components", INTERNET CITATION, April 2002 (2002-04-01), XP002422781, Retrieved from the Internet <URL:http://www.fpx.de/MicoCCM/download/mico-ccm.pdf> [retrieved on 20070228] * |
SHARIFI M ET AL: "CORBA components collocation optimization enhanced with local ORB-like services support", LECTURE NOTES IN COMPUTER SCIENCE, SPRINGER VERLAG, BERLIN, DE, vol. 3291, 2004, pages 1143 - 1154, XP002422782, ISSN: 0302-9743 * |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8252766B2 (en) | 2002-12-09 | 2012-08-28 | Cbt Development Limited | Use of spongosine for the treatment of pain |
Also Published As
Publication number | Publication date |
---|---|
US20070220046A1 (en) | 2007-09-20 |
US8407664B2 (en) | 2013-03-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8407664B2 (en) | Software model business objects | |
US8316344B2 (en) | Software model deployment units | |
US8448137B2 (en) | Software model integration scenarios | |
US8522194B2 (en) | Software modeling | |
US8327319B2 (en) | Software model process interaction | |
US8370794B2 (en) | Software model process component | |
US8312416B2 (en) | Software model business process variant types | |
US8321832B2 (en) | Composite application modeling | |
US20070233575A1 (en) | Architectural design for strategic sourcing application software | |
US20020111922A1 (en) | Electronic markets business interchange system and method | |
US20110307289A1 (en) | Managing consistent interfaces for customer project invoicing agreement, engineering change case, product design, product design version hierarchy, and project expense view business objects across heterogeneous systems | |
US20110307263A1 (en) | Managing consistent interfaces for property library, property list template, quantity conversion virtual object, and supplier property specification business objects across heterogeneous systems | |
Froehlich et al. | Application framework issues when evolving business applications for electronic commerce | |
WO2011153713A1 (en) | Managing consistent interfaces for indian payroll business objects across heterogeneous systems | |
Apperly | Service-and component-based development using Select Perspective and UML | |
Saleh | Documenting electronic commerce systems and software using the unified modeling language | |
US20130030967A1 (en) | Managing consistent interfaces for foreign trade product classification, supplier invoice business objects across heterogeneous systems | |
US20140006240A1 (en) | Consistent interface for customer contract and customer contract template - message set 2 | |
US20140280545A1 (en) | Consistent Interface for Lead Business Object | |
US20140006303A1 (en) | Consistent Interface for Customer Contract and Customer Contract Template - Message Set 1 | |
US20140006519A1 (en) | Consistent interface for employee master data replication request and employee work calendar | |
Cheng | SC Collaborator: A service oriented framework for construction supply chain collaboration and monitoring | |
Lau | Designing Web Services with Tropos | |
Mehta | Business Process Execution Language Based Software Implementation for Small Trading Firms With Service Oriented Architecture | |
Zografos | A Framework for e-Business Components |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 06847008 Country of ref document: EP Kind code of ref document: A1 |