WO2007112956A2 - Providing product catalog software application as enterprise services - Google Patents
Providing product catalog software application as enterprise services Download PDFInfo
- Publication number
- WO2007112956A2 WO2007112956A2 PCT/EP2007/002842 EP2007002842W WO2007112956A2 WO 2007112956 A2 WO2007112956 A2 WO 2007112956A2 EP 2007002842 W EP2007002842 W EP 2007002842W WO 2007112956 A2 WO2007112956 A2 WO 2007112956A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- catalog
- publication
- product
- change
- product catalog
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0641—Shopping interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0641—Shopping interfaces
- G06Q30/0643—Graphical representation of items or shoppers
Definitions
- This specification relates to data processing systems implemented on computers, and more particular to data processing systems providing services in the nature of web services.
- Enterprise software systems are generally large and complex. Such systems can require many different components, distributed across many different hardware platforms, possibly in several different geographical locations.
- the architecture of a large software application i.e., what its components are and how they fit together, is an important aspect of its design for a successful implementation.
- Web services are one technology for making the functionality of software applications available to other software, including other applications.
- a web service is a standards-based way of encapsulating the functionality of an application that other applications can locate and access.
- a service-oriented architecture is a distributed software model within which functionality is defined as independent web services. Within a service-oriented architecture, web services can be used in defined sequences according to business logic to form applications that enable business processes.
- This specification describes a services architecture design that provides enterprise services having product catalog functionality at the level of an enterprise application.
- Enterprise services are web services that have an enterprise-level business value.
- a system in one embodiment implements a services architecture design that provides enterprise services having product catalog functionality at the level of an enterprise application.
- the design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.
- Effective use is made of process components as units of software reuse, to provide a design that can be implemented reliably in a cost effective way.
- Effective use is made of deployment units, each of which is deployable on a separate computer hardware platform independent of every other deployment unit, to provide a scalable design.
- Service interfaces of the process components define a pair- wise interaction between pairs of process components that are in different deployment units in a scalable way.
- FIG. 1 illustrates a high-level view of a software architectural design and implementation of a suite of enterprise software services having product catalog functionality.
- FIGS. 2A and 2B are block diagrams collectively showing a product catalog authoring process component.
- FIGS. 3A and 3B are block diagrams collectively showing a product catalog publishing process component.
- FIG. 1 illustrates a high-level view of a software architectural design, and of application software implementations of the design, that provides a suite of enterprise service operations, which can be organized into interfaces, having product catalog application functionality.
- the elements of the architecture include the business object, the process component, the service operation (or simply, the operation), the service interface, the message, and the deployment unit.
- the elements can also include process agents and reuse service components. These will be generally described below.
- the software is implemented to be deployed on an application platform that includes a foundation layer that contains all fundamental entities that can used from multiple deployment units. These entities can be process components, business objects or reuse service components.
- a reuse service component is a piece of software that is reused in different transactions.
- a reuse service component is used by its defined interfaces, which can be, e.g., local APIs (Application Programming Interfaces) or service interfaces.
- the architectural design is a specification of a computer software application, and elements of the architectural design can be implemented to realize a software application that implements enterprise application service interfaces.
- the elements of the architecture are at times described in this specification as being contained or included in other elements; for example, a process component is described as being contained in a deployment unit. It should be understood, however, that such operational inclusion can be realized in a variety of ways and is not limited to a physical inclusion of the entirety of one element in another.
- the architectural elements include the business object.
- a business object is a representation of a type of a uniquely identifiable business entity (an object instance) described by a structural model. Processes operate on business objects.
- a business object represents a specific view on some well-defined business content.
- a business object represents content, and instances of business objects include content, which a typical business user would expect and understand with little explanation. Whether an object as a type or an instance of an object is intended by the term is generally clear from the context, so the distinction will be made explicitly only when necessary. Properly implemented, business objects are implemented free of redundancies.
- Business objects are further categorized as business process objects and, master data objects, mass data run objects, dependent objects, and transformed objects.
- a master data object is an object that encapsulates master data (i.e., data that is valid for a period of time).
- a business process object which is the kind of business object generally found in a process component, is an object that encapsulates transactional data (i.e., data that is valid for a point in time).
- a mass data run object is an application object that executes an algorithm for a particular mass data run. An instance of a mass data run object contains a particular set of selections and parameters.
- a mass data run object implements an algorithm that modifies, manages, and/or processes a large amount of data in multiple transactions, possibly but not necessarily with parallel processing.
- a dependent object is a business object used as a reuse part in another business object.
- a dependent object represents a concept that cannot stand by itself from a business point of view. Instances of dependent objects only occur in the context of a non-dependent business object.
- a transformed object is a transformation of multiple business objects for a well-defined purpose. It transforms the structure of multiple business objects into a common structure. A transformed object does not have its own persistency.
- the term business object will be used generically to refer to a business process object and a master data object, unless the context requires otherwise. Properly implemented, business objects are implemented free of redundancies.
- the architectural elements also include the process component.
- a process component is a software package that realizes a business process and generally exposes its functionality as services. The functionality contains business transactions.
- a process component contains one or more semantically related business objects. Any business object belongs to no more than one process component.
- Process components are modular and context-independent. That they are context- independent means that a process component is not specific to any specific application and is reusable. The process component is the smallest (most granular) element of reuse in the architecture.
- the architectural elements also include the operation.
- An operation belongs to exactly one process component.
- a process component generally has multiple operations. Operations can be synchronous or asynchronous, corresponding to synchronous or asynchronous process agents, which will be described below.
- An operation is the smallest, separately-callable function, described by a set of data types used as input, output, and fault parameters, or some combination of them, serving as a signature.
- a repository of service descriptions that includes a standards-based description of each of the supported service operations.
- the architectural elements also include the service interface, which may be referred to simply as an interface.
- An interface is a named group of operations. Each operation belongs to exactly one interface.
- An interface belongs to exactly one process component.
- a process component might contain multiple interfaces.
- an interface contains only inbound or outbound operations, but not a mixture of both.
- One interface can contain both synchronous and asynchronous operations.
- AU operations of the same type (either inbound or outbound) which belong to the same message choreography will preferably belong to the same interface. Thus, generally, all outbound operations to the same other process component are in one interface.
- the architectural elements also include the message.
- Operations transmit and receive messages. Any convenient messaging infrastructure can be used.
- a message is information conveyed from one process component instance to another, with the expectation that activity will ensue.
- An operation can use multiple message types for inbound, outbound, or error messages.
- invocation of an operation of one process component by the other process component is accomplished by an operation on the other process component sending a message to the first process component.
- the architectural elements also include the process agent.
- Process agents do business processing that involves the sending or receiving of messages. Each operation will generally have at least one associated process agent.
- a process agent can be associated with one or more operations.
- Process agents can be either inbound or outbound, and either synchronous or asynchronous.
- Asynchronous outbound process agents are called after a business object changes, e.g., after a create, update, or delete of a business object instance.
- Synchronous outbound process agents are generally triggered directly by a business object.
- An output process agent will generally perform some processing of the data of the business object instance whose change triggered the event.
- An outbound agent triggers subsequent business process steps by sending messages using well-defined outbound services to another process component, which generally will be in another deployment unit, or to an external system.
- An outbound process agent is linked to the one business object that triggers the agent, but it is sent not to another business object but rather to another process component. Thus, the outbound process agent can be implemented without knowledge of the exact business object design of the recipient process component.
- Inbound process agents are called after a message has been received.
- Inbound process agents are used for the inbound part of a message-based communication.
- An inbound process agent starts the execution of the business process step requested in a message by creating or updating one or multiple business object instances.
- An inbound process agent is not the agent of a business object but of its process component.
- An inbound process agent can act on multiple business objects in a process component.
- Synchronous agents are used when a process component requires a more or less immediate response from another process component, and is waiting for that response to continue its work.
- Operations and process components are described in this specification in terms of process agents. However, in alternative implementations, process components and operations can be implemented without use of agents using other conventional techniques to perform the functions described in this specification.
- the architectural elements also include the deployment unit.
- a deployment unit includes one or more process components and, optionally, one or more business objects, that are deployed together on a single computer system platform.
- separate deployment units can be deployed on separate physical computing systems.
- a deployment unit boundary defines the limits of an application-defined transaction, i.e., a set of actions that have the ACID properties of atomicity, consistency, isolation, and durability.
- the architecture requires that all operations of such a transaction be performed on one physical database; as a consequence, the processes of such a transaction must be performed by the process components of one instance of one deployment unit.
- the process components of one deployment unit interact with those of another deployment unit using messages passed through one or more data communication networks or other suitable communication channels.
- a deployment unit deployed on a platform belonging one business can interact with a deployment unit software entity deployed on a separate platform belonging to a different and unrelated business, allowing for business-to- business communication.
- More than one instance of a given deployment unit can execute at the same time, on the same computing system or on separate physical computing systems. This arrangement allows the functionality offered by a deployment unit to be scaled to meet demand by creating as many instances as needed.
- deployment units can be replaced by other another deployment unit as long as the new deployment unit supports the operations depended upon by other deployment units.
- deployment units can depend on the external interfaces of process components in other deployment units, deployment units are not dependent on process component interactions (i.e., interactions between process components involving their respective business objects, operations, interfaces, and messages) within other deployment units.
- process components that interact with other process components or external systems only through messages e.g., as sent and received by operations, can also be replaced as long as the replacement supports the operations of the original.
- the foundation layer does not define a limit for application-defined transactions.
- Deployment units communicate directly with entities in the foundation layer, which communication is typically not message based.
- the foundation layer is active in every system instance on which the application is deployed.
- Business objects in the foundation layer will generally be master data objects.
- the foundation layer will include some business process objects that are used by multiple deployment units. Master data objects and business process objects that should be specific to a deployment unit are preferably assigned to their respective deployment unit.
- FIG. 1 illustrates a high-level view of a software architectural design and implementation of a suite of enterprise software services having product catalog functionality.
- a Catalog Authoring deployment unit 102 includes a Product Catalog Authoring process component 104, a Product Catalog master data object 106, a Product Catalog Update Run business object 108, a Product Catalog File Upload Run business object 110, a Product Catalog Duplication Run business object 112, a Product Catalog Change List business object 114, a Product Catalog Update Method master data object 116, and a Product Catalog Publishing Sending Run business object 120.
- a Catalog Publishing deployment unit 122 includes: a Product Catalog Publishing process component 124, a Published Product Catalog master data object 126, and a Published Product Catalog Update Run business object 128.
- FIGS. 2 A and 2B are block diagrams collectively showing the Product Catalog Authoring process component 104 (FIG. 1).
- FIGS. 2 A and 2B are block diagrams collectively showing the Product Catalog Authoring process component 104 (FIG. 1).
- FIGS. 2 A and 2B are block diagrams collectively showing the Product Catalog Authoring process component 104 (FIG. 1).
- FIGS. 2 A and 2B are block diagrams collectively showing the Product Catalog Authoring process component 104 (FIG. 1).
- FIGS. 2 A and 2B are block diagrams collectively showing the Product Catalog Authoring process component 104 (FIG. 1).
- FIGS. 2 A and 2B are block diagrams collectively showing the Product Catalog Authoring process component 104 (FIG. 1).
- FIGS. 2 A and 2B are block diagrams collectively showing the Product Catalog Authoring process component 104 (FIG. 1).
- FIGS. 2 A and 2B are block diagrams collectively showing the Product Catalog Authoring process component 104 (FIG. 1).
- a Maintain Catalog operation 210 sends a catalog maintenance request using a Maintain Product Catalog asynchronous inbound process agent 212 to update the Product Catalog master data object 106.
- the operation 210 can send a request to update the Product Catalog master data object 106 if input is received from the Purchasing Contract Processing process component 202 or the Product Catalog Authoring at Supplier process component 204.
- the request can be to create a new product catalog, or to change or update an existing product catalog.
- the Maintain Catalog operation 210 is included in a Product Catalog Transmission Receiving In interface 214.
- a Change Transmission Status operation 216 sends a product catalog transmission status change notification using a Change Product Catalog based on Published Product
- a Change Publication Status operation 220 sends a product catalog publication status change using the Change Product Catalog based on Published Product Catalog asynchronous inbound process agent 218 to update the Product Catalog master data object 106.
- the operation 220 can send a change notification to update the Product Catalog 5 master data object 106 if input is received from the Product Catalog Publishing process component 124.
- the change notification can be to set the result status of an ongoing catalog publication transmission.
- a Change Catalog based on Publication Cancellation operation 222 sends a product catalog change notification using the Change Product Catalog based on Published Product o Catalog asynchronous inbound process agent 218 to update the Product Catalog master data object 106.
- the operation 222 can send a change notification to update the Product Catalog master data object 106 if input is received from the Product Catalog Publishing process component 124.
- the change notification can be to update a catalog based on the cancellation of publication.
- a Change Catalog based on Item Lock Status operation 224 sends a product catalog change notification using the Change Product Catalog based on Published Product Catalog asynchronous inbound process agent 218 to update the Product Catalog master data object 106.
- the operation 224 can send a change notification to update the Product Catalog master data object 106 if input is received from the Product Catalog Publishing 0 process component 124.
- the change notification can be to change a product catalog based on the change of status of a locked item within the catalog.
- a Change Catalog based on Content Change Publication Status operation 226 sends a product catalog change notification using the Change Product Catalog based on Published Product Catalog asynchronous inbound process agent 218 to update the Product Catalog 5 master data object 106.
- the operation 226 can send a change notification to update the Product Catalog master data object 106 if input is received from the Product Catalog Publishing process component 124.
- the change notification can be to change a catalog based on a change of status of a catalog publication.
- the Change Transmission Status operation 216, the Change Publication Status 0 operation 220, the Change Catalog based on Publication Cancellation operation 222, the Change Catalog based on Item Lock Status operation 224, and the Change Catalog based on Content Change Publication Status operation 226 are included in a Publishing In interface 228.
- the Product Catalog master data object 106 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 2B, multiple message agents can receive information from the Product Catalog master data object 106.
- a Request Publication from Product Catalog to Product Catalog Publishing asynchronous outbound process agent 230 can invoke a Request Catalog Publication operation 232.
- the outbound process agent 230 can send a request to publish a product catalog.
- the Request Publication from Product Catalog to Product Catalog Publishing asynchronous outbound process agent 230 can also invoke a Request Catalog Publication Cancellation operation 234.
- the outbound process agent 230 can send a request to cancel publication of a product catalog.
- the Request Publication from Product Catalog to Product Catalog Publishing asynchronous outbound process agent 230 can also invoke a Request Catalog Item Lock operation 236.
- the outbound process agent 230 can send a request to lock an item a product catalog.
- the Request Publication from Product Catalog to Product Catalog Publishing asynchronous outbound process agent 230 can also invoke a Request Catalog Publication Content Change operation 238.
- the outbound process agent 230 can send a request to change the information for an item in a product catalog.
- the Request Catalog Publication operation 232, the Request Catalog Publication Cancellation operation 234, the Request Catalog Item Lock operation 236, and the Request Catalog Publication Content Change operation 238 are included in a Publishing Out interface 240.
- a Notify of Publication from Product Catalog to Customer asynchronous outbound process agent 242 invokes a Notify of Catalog Update operation 244, which notifies another party (e.g., a customer) about a catalog publication. This can be a new catalog or an update to a previously published catalog.
- FIGS. 3A and 3B are block diagrams collectively showing the Product Catalog Publishing process component 124 (FIG. 1).
- FIG. 1 For convenience in describing this process component, another process component is shown in the figures; this other process component is not part of the process component being described.
- This other process component is a Product Catalog Authoring process component 104.
- This other process component is used to represent software external to the process component in describing its interactions with the external software; however, while the external software can be implemented as such process components, this is not required.
- a Maintain Published Product Catalog operation 304 can send a product catalog maintenance request using a Maintain Published Product Catalog asynchronous inbound process agent 306 to update the Published Product Catalog master data object 126.
- the operation 304 can send a product catalog maintenance notification to update the Published Product Catalog master data object 126 if input is received from the Product Catalog Authoring process component 104.
- the maintenance notification can be to update the contents of a published catalog.
- a Cancel Catalog Publication operation 308 can send a product catalog publication cancellation request using the Maintain Published Product Catalog asynchronous inbound process agent 306 to update the Published Product Catalog master data object 126.
- the operation 308 can send a product catalog publication cancellation notification to update the Published Product Catalog master data object 126 if input is received from the
- the maintenance notification can be to cancel the publication of a catalog.
- a Lock Published Catalog Items operation 310 can send a product catalog item lock request using the Maintain Published Product Catalog asynchronous inbound process agent 306 to update the Published Product Catalog master data object 126.
- the operation 310 can send a product catalog item lock notification to update the Published Product Catalog master data object 126 if input is received from the Product Catalog Authoring process component 104.
- the maintenance notification can be to place a lock on items within a published catalog.
- a Change Published Catalog Content operation 312 can send a product catalog content change request using the Maintain Published Product Catalog asynchronous inbound process agent 306 to update the Published Product Catalog master data object 126.
- the operation 312 can send a product catalog content change notification to update the Published Product Catalog master data object 126 if input is received from the Product Catalog Authoring process component 104.
- the maintenance notification can be to change the content of a published catalog.
- the Maintain Published Product Catalog operation 304, the Cancel Catalog Publication operation 308, the Lock Published Catalog Items operation 310, and the Change Published Catalog Content operation 312 are included in a Publishing In interface 314.
- the Published Product Catalog master data object 126 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 3B, multiple process agents can receive information from the Published Product Catalog master data object 126.
- a Notify of Product Catalog Publication Status asynchronous outbound process agent
- the outbound process agent 316 can invoke a Notify of Publication Transmission Package Check operation 318.
- the outbound process agent 316 can send a notification of a publication transmission package check.
- the Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can also invoke a Confirm Catalog Publication operation 320.
- the outbound process agent 316 can send a confirmation that a product catalog has been published.
- the Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can also invoke a Confirm Catalog Publication Cancellation operation 322.
- the outbound process agent 316 can send a confirmation that a product catalog publication has been cancelled.
- the Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can also invoke a Confirm Catalog Item Lock operation 324.
- the outbound process agent 316 can send a request to lock an item in a product catalog.
- the Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can also invoke a Confirm Catalog Publication Content Change operation 326.
- the outbound process agent 316 can send a request to change the information for an item in a product catalog.
- the Notify of Publication Transmission Package Check operation 318, the Confirm Catalog Publication operation 320, the Confirm Catalog Publication Cancellation operation 322, the Confirm Catalog Item Lock operation 324, and the Confirm Catalog Publication Content Change operation 326 are included in a Publishing Out interface 328.
- the subject matter described in this specification and all of the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structural means disclosed in this specification and structural equivalents thereof, or in combinations of them.
- the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more computer programs tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
- a computer program (also known as a program, software, software application, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
- a computer program does not necessarily correspond to a file.
- a program can be stored in a portion of a file that holds other programs or data, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).
- a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
- the processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output.
- the processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
- processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer.
- a processor will receive instructions and data from a read-only memory or a random access memory or both.
- the essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data.
- a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
- Information carriers suitable for embodying computer program instructions and data include all forms of non- volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
- semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
- magnetic disks e.g., internal hard disks or removable disks
- magneto-optical disks e.g., CD-ROM and DVD-ROM disks.
- the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
- the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g. , a mouse or a trackball, by which the user can provide input to the computer.
- a display device e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor
- a keyboard and a pointing device e.g. , a mouse or a trackball
- Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g. , visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
- the subject matter described in this specification can be implemented in a computing system that includes a back-end component (e.g., a data server), a middleware component (e.g., an application server), or a front-end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described herein), or any combination of such back-end, middleware, and front-end components.
- the components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network ("LAN”) and a wide area network (“WAN”), e.g., the Internet.
- LAN local area network
- WAN wide area network
- the computing system can include clients and servers.
- a client and server are generally remote from each other and typically interact through a communication network.
- the relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
Description
PROVIDING PRODUCT CATALOG SOFTWARE APPLICATION AS
ENTERPRISE SERVICES
BACKGROUND
This specification relates to data processing systems implemented on computers, and more particular to data processing systems providing services in the nature of web services.
Enterprise software systems are generally large and complex. Such systems can require many different components, distributed across many different hardware platforms, possibly in several different geographical locations. Thus, the architecture of a large software application, i.e., what its components are and how they fit together, is an important aspect of its design for a successful implementation.
Web services are one technology for making the functionality of software applications available to other software, including other applications. A web service is a standards-based way of encapsulating the functionality of an application that other applications can locate and access. A service-oriented architecture is a distributed software model within which functionality is defined as independent web services. Within a service-oriented architecture, web services can be used in defined sequences according to business logic to form applications that enable business processes.
SUMMARY
This specification describes a services architecture design that provides enterprise services having product catalog functionality at the level of an enterprise application. Enterprise services are web services that have an enterprise-level business value.
In its various aspects, the invention can be embodied in systems, methods, and computer program products. For example, a system in one embodiment implements a services architecture design that provides enterprise services having product catalog functionality at the level of an enterprise application. The design includes a set of service operations, process components, and optionally deployment units. Suitable business objects are also described.
The subject matter described in this specification can be implemented to realize one or more of the following advantages. Effective use is made of process components as units of
software reuse, to provide a design that can be implemented reliably in a cost effective way. Effective use is made of deployment units, each of which is deployable on a separate computer hardware platform independent of every other deployment unit, to provide a scalable design. Service interfaces of the process components define a pair- wise interaction between pairs of process components that are in different deployment units in a scalable way.
Details of one or more implementations of the subject matter described in this specification are set forth in the accompanying drawings and in the description below. Further features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 illustrates a high-level view of a software architectural design and implementation of a suite of enterprise software services having product catalog functionality. FIGS. 2A and 2B are block diagrams collectively showing a product catalog authoring process component. FIGS. 3A and 3B are block diagrams collectively showing a product catalog publishing process component.
Like reference numbers and designations in the various drawings indicate like elements.
DETAILED DESCRIPTION FIG. 1 illustrates a high-level view of a software architectural design, and of application software implementations of the design, that provides a suite of enterprise service operations, which can be organized into interfaces, having product catalog application functionality.
The elements of the architecture include the business object, the process component, the service operation (or simply, the operation), the service interface, the message, and the deployment unit. The elements can also include process agents and reuse service components. These will be generally described below.
In one implementation, the software is implemented to be deployed on an application platform that includes a foundation layer that contains all fundamental entities that can used
from multiple deployment units. These entities can be process components, business objects or reuse service components. A reuse service component is a piece of software that is reused in different transactions. A reuse service component is used by its defined interfaces, which can be, e.g., local APIs (Application Programming Interfaces) or service interfaces. The architectural design is a specification of a computer software application, and elements of the architectural design can be implemented to realize a software application that implements enterprise application service interfaces. The elements of the architecture are at times described in this specification as being contained or included in other elements; for example, a process component is described as being contained in a deployment unit. It should be understood, however, that such operational inclusion can be realized in a variety of ways and is not limited to a physical inclusion of the entirety of one element in another.
The architectural elements include the business object. A business object is a representation of a type of a uniquely identifiable business entity (an object instance) described by a structural model. Processes operate on business objects. A business object represents a specific view on some well-defined business content. A business object represents content, and instances of business objects include content, which a typical business user would expect and understand with little explanation. Whether an object as a type or an instance of an object is intended by the term is generally clear from the context, so the distinction will be made explicitly only when necessary. Properly implemented, business objects are implemented free of redundancies.
Business objects are further categorized as business process objects and, master data objects, mass data run objects, dependent objects, and transformed objects. A master data object is an object that encapsulates master data (i.e., data that is valid for a period of time). A business process object, which is the kind of business object generally found in a process component, is an object that encapsulates transactional data (i.e., data that is valid for a point in time). A mass data run object is an application object that executes an algorithm for a particular mass data run. An instance of a mass data run object contains a particular set of selections and parameters. A mass data run object implements an algorithm that modifies, manages, and/or processes a large amount of data in multiple transactions, possibly but not necessarily with parallel processing. A dependent object is a business object used as a reuse
part in another business object. A dependent object represents a concept that cannot stand by itself from a business point of view. Instances of dependent objects only occur in the context of a non-dependent business object. A transformed object is a transformation of multiple business objects for a well-defined purpose. It transforms the structure of multiple business objects into a common structure. A transformed object does not have its own persistency. The term business object will be used generically to refer to a business process object and a master data object, unless the context requires otherwise. Properly implemented, business objects are implemented free of redundancies.
The architectural elements also include the process component. A process component is a software package that realizes a business process and generally exposes its functionality as services. The functionality contains business transactions. A process component contains one or more semantically related business objects. Any business object belongs to no more than one process component.
Process components are modular and context-independent. That they are context- independent means that a process component is not specific to any specific application and is reusable. The process component is the smallest (most granular) element of reuse in the architecture.
The architectural elements also include the operation. An operation belongs to exactly one process component. A process component generally has multiple operations. Operations can be synchronous or asynchronous, corresponding to synchronous or asynchronous process agents, which will be described below. An operation is the smallest, separately-callable function, described by a set of data types used as input, output, and fault parameters, or some combination of them, serving as a signature. For convenience in supporting use of the operations supported by a system implementing elements of the design, such a system can optionally include a repository of service descriptions that includes a standards-based description of each of the supported service operations.
The architectural elements also include the service interface, which may be referred to simply as an interface. An interface is a named group of operations. Each operation belongs to exactly one interface. An interface belongs to exactly one process component. A process component might contain multiple interfaces. In one implementation, an interface contains
only inbound or outbound operations, but not a mixture of both. One interface can contain both synchronous and asynchronous operations. AU operations of the same type (either inbound or outbound) which belong to the same message choreography will preferably belong to the same interface. Thus, generally, all outbound operations to the same other process component are in one interface.
The architectural elements also include the message. Operations transmit and receive messages. Any convenient messaging infrastructure can be used. A message is information conveyed from one process component instance to another, with the expectation that activity will ensue. An operation can use multiple message types for inbound, outbound, or error messages. When two process components are in different deployment units, invocation of an operation of one process component by the other process component is accomplished by an operation on the other process component sending a message to the first process component. The architectural elements also include the process agent. Process agents do business processing that involves the sending or receiving of messages. Each operation will generally have at least one associated process agent. A process agent can be associated with one or more operations. Process agents can be either inbound or outbound, and either synchronous or asynchronous.
Asynchronous outbound process agents are called after a business object changes, e.g., after a create, update, or delete of a business object instance. Synchronous outbound process agents are generally triggered directly by a business object.
An output process agent will generally perform some processing of the data of the business object instance whose change triggered the event. An outbound agent triggers subsequent business process steps by sending messages using well-defined outbound services to another process component, which generally will be in another deployment unit, or to an external system. An outbound process agent is linked to the one business object that triggers the agent, but it is sent not to another business object but rather to another process component. Thus, the outbound process agent can be implemented without knowledge of the exact business object design of the recipient process component.
Inbound process agents are called after a message has been received. Inbound process agents are used for the inbound part of a message-based communication. An inbound process agent starts the execution of the business process step requested in a message by creating or updating one or multiple business object instances. An inbound process agent is not the agent of a business object but of its process component. An inbound process agent can act on multiple business objects in a process component.
Synchronous agents are used when a process component requires a more or less immediate response from another process component, and is waiting for that response to continue its work. Operations and process components are described in this specification in terms of process agents. However, in alternative implementations, process components and operations can be implemented without use of agents using other conventional techniques to perform the functions described in this specification.
The architectural elements also include the deployment unit. A deployment unit includes one or more process components and, optionally, one or more business objects, that are deployed together on a single computer system platform. Conversely, separate deployment units can be deployed on separate physical computing systems. For this reason, a deployment unit boundary defines the limits of an application-defined transaction, i.e., a set of actions that have the ACID properties of atomicity, consistency, isolation, and durability. To make use of database manager facilities, the architecture requires that all operations of such a transaction be performed on one physical database; as a consequence, the processes of such a transaction must be performed by the process components of one instance of one deployment unit.
The process components of one deployment unit interact with those of another deployment unit using messages passed through one or more data communication networks or other suitable communication channels. Thus, a deployment unit deployed on a platform belonging one business can interact with a deployment unit software entity deployed on a separate platform belonging to a different and unrelated business, allowing for business-to- business communication. More than one instance of a given deployment unit can execute at the same time, on the same computing system or on separate physical computing systems.
This arrangement allows the functionality offered by a deployment unit to be scaled to meet demand by creating as many instances as needed.
Since interaction between deployment units is through service operations, a deployment unit can be replaced by other another deployment unit as long as the new deployment unit supports the operations depended upon by other deployment units. Thus, while deployment units can depend on the external interfaces of process components in other deployment units, deployment units are not dependent on process component interactions (i.e., interactions between process components involving their respective business objects, operations, interfaces, and messages) within other deployment units. Similarly, process components that interact with other process components or external systems only through messages, e.g., as sent and received by operations, can also be replaced as long as the replacement supports the operations of the original.
Interactions between process components that occur only within a deployment unit are not constrained to using service operations. These can be implemented in any convenient fashion.
In contrast to a deployment unit, the foundation layer does not define a limit for application-defined transactions. Deployment units communicate directly with entities in the foundation layer, which communication is typically not message based. The foundation layer is active in every system instance on which the application is deployed. Business objects in the foundation layer will generally be master data objects. In addition, the foundation layer will include some business process objects that are used by multiple deployment units. Master data objects and business process objects that should be specific to a deployment unit are preferably assigned to their respective deployment unit.
FIG. 1 illustrates a high-level view of a software architectural design and implementation of a suite of enterprise software services having product catalog functionality.
As shown in FIG. 1, a Catalog Authoring deployment unit 102 includes a Product Catalog Authoring process component 104, a Product Catalog master data object 106, a Product Catalog Update Run business object 108, a Product Catalog File Upload Run business object 110, a Product Catalog Duplication Run business object 112, a Product
Catalog Change List business object 114, a Product Catalog Update Method master data object 116, and a Product Catalog Publishing Sending Run business object 120.
Additionally, as shown in FIG. 1, a Catalog Publishing deployment unit 122 includes: a Product Catalog Publishing process component 124, a Published Product Catalog master data object 126, and a Published Product Catalog Update Run business object 128.
FIGS. 2 A and 2B are block diagrams collectively showing the Product Catalog Authoring process component 104 (FIG. 1). For convenience in describing this process component, a number of other process components are shown in the figures; these other process components are not part of the process component being described. These other process components are a Purchasing Contract Processing process component 202, a Product Catalog Authoring at Supplier process component 204, a Product Catalog Publishing process component 124, and a Product Catalog Authoring at Customer process component 208. These other process components are used to represent software external to the process component in describing its interactions with the external software; however, while the external software can be implemented as such process components, this is not required. A Maintain Catalog operation 210 sends a catalog maintenance request using a Maintain Product Catalog asynchronous inbound process agent 212 to update the Product Catalog master data object 106. For example, the operation 210 can send a request to update the Product Catalog master data object 106 if input is received from the Purchasing Contract Processing process component 202 or the Product Catalog Authoring at Supplier process component 204. The request can be to create a new product catalog, or to change or update an existing product catalog. The Maintain Catalog operation 210 is included in a Product Catalog Transmission Receiving In interface 214.
A Change Transmission Status operation 216 sends a product catalog transmission status change notification using a Change Product Catalog based on Published Product
Catalog asynchronous inbound process agent 218 to update the Product Catalog master data object 106. For example, the operation 216 can send a change notification to update the Product Catalog master data object 106 if input is received from the Product Catalog Publishing process component 124. The change notification can be to update the status of a catalog publication transmission package sent out earlier.
A Change Publication Status operation 220 sends a product catalog publication status change using the Change Product Catalog based on Published Product Catalog asynchronous inbound process agent 218 to update the Product Catalog master data object 106. For example, the operation 220 can send a change notification to update the Product Catalog 5 master data object 106 if input is received from the Product Catalog Publishing process component 124. The change notification can be to set the result status of an ongoing catalog publication transmission.
A Change Catalog based on Publication Cancellation operation 222 sends a product catalog change notification using the Change Product Catalog based on Published Product o Catalog asynchronous inbound process agent 218 to update the Product Catalog master data object 106. For example, the operation 222 can send a change notification to update the Product Catalog master data object 106 if input is received from the Product Catalog Publishing process component 124. The change notification can be to update a catalog based on the cancellation of publication. 5 A Change Catalog based on Item Lock Status operation 224 sends a product catalog change notification using the Change Product Catalog based on Published Product Catalog asynchronous inbound process agent 218 to update the Product Catalog master data object 106. For example, the operation 224 can send a change notification to update the Product Catalog master data object 106 if input is received from the Product Catalog Publishing 0 process component 124. The change notification can be to change a product catalog based on the change of status of a locked item within the catalog.
A Change Catalog based on Content Change Publication Status operation 226 sends a product catalog change notification using the Change Product Catalog based on Published Product Catalog asynchronous inbound process agent 218 to update the Product Catalog 5 master data object 106. For example, the operation 226 can send a change notification to update the Product Catalog master data object 106 if input is received from the Product Catalog Publishing process component 124. The change notification can be to change a catalog based on a change of status of a catalog publication.
The Change Transmission Status operation 216, the Change Publication Status 0 operation 220, the Change Catalog based on Publication Cancellation operation 222, the
Change Catalog based on Item Lock Status operation 224, and the Change Catalog based on Content Change Publication Status operation 226 are included in a Publishing In interface 228.
The Product Catalog master data object 106 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 2B, multiple message agents can receive information from the Product Catalog master data object 106.
A Request Publication from Product Catalog to Product Catalog Publishing asynchronous outbound process agent 230 can invoke a Request Catalog Publication operation 232. For example, the outbound process agent 230 can send a request to publish a product catalog. The Request Publication from Product Catalog to Product Catalog Publishing asynchronous outbound process agent 230 can also invoke a Request Catalog Publication Cancellation operation 234. For example, the outbound process agent 230 can send a request to cancel publication of a product catalog. The Request Publication from Product Catalog to Product Catalog Publishing asynchronous outbound process agent 230 can also invoke a Request Catalog Item Lock operation 236. For example, the outbound process agent 230 can send a request to lock an item a product catalog. The Request Publication from Product Catalog to Product Catalog Publishing asynchronous outbound process agent 230 can also invoke a Request Catalog Publication Content Change operation 238. For example, the outbound process agent 230 can send a request to change the information for an item in a product catalog. The Request Catalog Publication operation 232, the Request Catalog Publication Cancellation operation 234, the Request Catalog Item Lock operation 236, and the Request Catalog Publication Content Change operation 238 are included in a Publishing Out interface 240. A Notify of Publication from Product Catalog to Customer asynchronous outbound process agent 242 invokes a Notify of Catalog Update operation 244, which notifies another party (e.g., a customer) about a catalog publication. This can be a new catalog or an update to a previously published catalog. The Notify of Catalog Update operation 244 is included in a Transmission Sending Out interface 246. As an example, the operation 244 can then send a notification to the Product Catalog Authoring at Customer process component 208.
FIGS. 3A and 3B are block diagrams collectively showing the Product Catalog Publishing process component 124 (FIG. 1). For convenience in describing this process component, another process component is shown in the figures; this other process component is not part of the process component being described. This other process component is a Product Catalog Authoring process component 104. This other process component is used to represent software external to the process component in describing its interactions with the external software; however, while the external software can be implemented as such process components, this is not required.
A Maintain Published Product Catalog operation 304 can send a product catalog maintenance request using a Maintain Published Product Catalog asynchronous inbound process agent 306 to update the Published Product Catalog master data object 126. For example, the operation 304 can send a product catalog maintenance notification to update the Published Product Catalog master data object 126 if input is received from the Product Catalog Authoring process component 104. The maintenance notification can be to update the contents of a published catalog.
A Cancel Catalog Publication operation 308 can send a product catalog publication cancellation request using the Maintain Published Product Catalog asynchronous inbound process agent 306 to update the Published Product Catalog master data object 126. For example, the operation 308 can send a product catalog publication cancellation notification to update the Published Product Catalog master data object 126 if input is received from the
Product Catalog Authoring process component 104. The maintenance notification can be to cancel the publication of a catalog.
A Lock Published Catalog Items operation 310 can send a product catalog item lock request using the Maintain Published Product Catalog asynchronous inbound process agent 306 to update the Published Product Catalog master data object 126. For example, the operation 310 can send a product catalog item lock notification to update the Published Product Catalog master data object 126 if input is received from the Product Catalog Authoring process component 104. The maintenance notification can be to place a lock on items within a published catalog.
A Change Published Catalog Content operation 312 can send a product catalog content change request using the Maintain Published Product Catalog asynchronous inbound process agent 306 to update the Published Product Catalog master data object 126. For example, the operation 312 can send a product catalog content change notification to update the Published Product Catalog master data object 126 if input is received from the Product Catalog Authoring process component 104. The maintenance notification can be to change the content of a published catalog.
The Maintain Published Product Catalog operation 304, the Cancel Catalog Publication operation 308, the Lock Published Catalog Items operation 310, and the Change Published Catalog Content operation 312 are included in a Publishing In interface 314.
The Published Product Catalog master data object 126 can receive updated information and send the update into other components to perform further operations. As shown in FIG. 3B, multiple process agents can receive information from the Published Product Catalog master data object 126. A Notify of Product Catalog Publication Status asynchronous outbound process agent
316 can invoke a Notify of Publication Transmission Package Check operation 318. For example, the outbound process agent 316 can send a notification of a publication transmission package check. The Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can also invoke a Confirm Catalog Publication operation 320. For example, the outbound process agent 316 can send a confirmation that a product catalog has been published. The Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can also invoke a Confirm Catalog Publication Cancellation operation 322. For example, the outbound process agent 316 can send a confirmation that a product catalog publication has been cancelled. The Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can also invoke a Confirm Catalog Item Lock operation 324. For example, the outbound process agent 316 can send a request to lock an item in a product catalog. The Notify of Product Catalog Publication Status asynchronous outbound process agent 316 can also invoke a Confirm Catalog Publication Content Change operation 326. For example, the outbound process agent 316 can send a request to change the information for an item in a product catalog. The Notify of Publication Transmission
Package Check operation 318, the Confirm Catalog Publication operation 320, the Confirm Catalog Publication Cancellation operation 322, the Confirm Catalog Item Lock operation 324, and the Confirm Catalog Publication Content Change operation 326 are included in a Publishing Out interface 328.
The subject matter described in this specification and all of the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structural means disclosed in this specification and structural equivalents thereof, or in combinations of them. The subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more computer programs tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program (also known as a program, software, software application, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file. A program can be stored in a portion of a file that holds other programs or data, in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors
of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non- volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
To provide for interaction with a user, the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g. , a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g. , visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. The subject matter described in this specification can be implemented in a computing system that includes a back-end component (e.g., a data server), a middleware component (e.g., an application server), or a front-end component (e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described herein), or any combination of such back-end, middleware, and front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network ("LAN") and a wide area network ("WAN"), e.g., the Internet.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network.
The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
While this specification contains many specifics, these should not be construed as limitations on the scope of the invention or of what may be claimed, but rather as an exemplification of preferred embodiments of the invention. Certain features that are described in this specification in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be provided in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.
The subject matter has been described in terms of particular variations, but other variations can be implemented and are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous. Other variations are within the scope of the following claims. What is claimed is:
Claims
1. A system comprising: a computer system comprising one or more hardware platforms for executing computer software; and
5 computer software deployed on the computer system, the computer software implementing a plurality of service operations, the service operations comprising: a maintain catalog operation, the operation operable to send a notification to update a product catalog; a change transmission status operation, the operation operable to send a o notification to change the transmission status of a product catalog; a change publication status operation, the operation operable to send a notification to change the publication status of a product catalog; a change catalog based on publication cancellation operation, the operation operable to send a notification to update a product catalog based on a publication 5 cancellation; a change catalog based on item lock status operation, the operation operable to send a notification to update a product catalog based on a locked item; a change catalog based on content change publication status operation, the operation operable to send a notification to update a product catalog based on a catalog 0 change content publication status; a request catalog publication operation, the operation requesting that a product catalog be published; a request catalog publication cancellation operation, the operation requesting a product catalog publication be cancelled; 5 a request catalog item lock operation, the operation requesting an item in a product catalog to be locked; a request catalog publication content change operation, the operation requesting a content change in a product catalog publication; a notify of catalog update operation, the operation operable to send a 0 notification about an update to a product catalog; a maintain published product catalog operation, the operation operable to send a notification to update a published product catalog; a cancel catalog publication operation, the operation operable to send a notification to cancel the publication of a product catalog; a lock published catalog items operation, the operation operable to send a notification to lock items contained in a published product catalog; a change published catalog content operation, the operation operable to send a notification to change the content in a published product catalog; a notify of publication transmission package check operation, the operation operable to send a notification about a catalog publication transmission package check; a confirm catalog publication operation, the operation operable to send a notification to confirm the publication of a product catalog; a confirm catalog publication cancellation operation, the operation operable to send a notification to confirm the cancellation of a product catalog publication; a confirm catalog item lock operation, the operation operable to send a notification to confirm the lock of an item in a product catalog; and a confirm catalog publication content change operation, the operation operable to send a notification to confirm the content change of a product catalog publication.
02842
2. The system of claim 1, wherein the service operations are grouped into service interfaces, the service interfaces comprising: a product catalog transmission receiving in interface that includes the maintain catalog service operation; a publishing in interface that includes the change transmission status, the change publication status, the change catalog based on publication cancellation, the change catalog based on item lock status, and the change catalog based on content change publication status service operations; a publishing out interface that includes the request catalog publication, the request catalog publication cancellation, the request catalog item lock, and the request catalog publication content change service operations; a transmission sending out interface that includes the notify of catalog update service operation; a publishing in interface that includes the maintain published product catalog, the cancel catalog publication, the lock published catalog items, and the change published catalog content service operations; and a publishing out interface that includes the notify of publication transmission package check, the confirm catalog publication, the confirm catalog publication cancellation, the confirm catalog item lock, and the confirm catalog publication content change service operations. or 2 .
3. The system of claim 1* wherein: the computer software implementing the maintain catalog, the change transmission status, the change publication status, the change catalog based on publication cancellation, the change catalog based on item lock status, the change catalog based on content change publication status, the request catalog publication, the request catalog publication cancellation, the request catalog item lock, the request catalog publication content change, and the notify of catalog update operation is deployed on a first hardware platform; and the computer software implementing the maintain published product catalog, the cancel catalog publication, the lock published catalog items, the change published catalog content, the notify of publication transmission package check, the confirm catalog publication, 02842
the confirm catalog publication cancellation, the confirm catalog item lock, and the confirm catalog publication content change operation is deployed on a second hardware platform.
4. The system of claim 3, wherein each of the first and second hardware platforms are distinct and separate from each other.
5. The system of claim 1 , wherein: the computer software implementing the maintain catalog, the change transmission status, the change publication status, the change catalog based on publication cancellation, the change catalog based on item lock status, the change catalog based on content change publication status, the request catalog publication, the request catalog publication cancellation, the request catalog item lock, the request catalog publication content change, and the notify of catalog update operation is deployable on a first hardware platform; and the computer software implementing the maintain published product catalog, the cancel catalog publication, the lock published catalog items, the change published catalog content, the notify of publication transmission package check, the confirm catalog publication, the confirm catalog publication cancellation, the confirm catalog item lock, and the confirm catalog publication content change operation is deployable on a second hardware platform; and wherein: the first and second hardware platforms are distinct and separate from each other.
. a ny one of cla ims 1 to 5 r ι
6. The system of "^" wherein the computer software deployed on the computer system comprises: a plurality of process components, each of the process components being a package of software deployed and executing on the computer system and implementing a respective and 5 distinct business process, the plurality of process components including: a product catalog authoring process component used to create and edit product catalogs, to control the quality of their contents, and to control their readiness for publication; and a product catalog publishing process component used to make published o product catalogs available electronically, and to provide a means to interactively search for and select products for use by other business processes; and wherein: the product catalog authoring process component implements the maintain catalog, the change transmission status, the change publication status, the change catalog 5 based on publication cancellation, the change catalog based on item lock status, the change catalog based on content change publication status, the request catalog publication, the request catalog publication cancellation, the request catalog item lock, the request catalog publication content change, and the notify of catalog update service operations; and the product catalog publishing process component implements the maintain 0 published product catalog, the cancel catalog publication, the lock published catalog items, the change published catalog content, the notify of publication transmission package check, the confirm catalog publication, the confirm catalog publication cancellation, the confirm catalog item lock, and the confirm catalog publication content change service operations.
a ny on e of c la ims 1 to 6 , ,
7. The system of wherein the computer software deployed on the computer system comprises: a plurality of deployment units, each of the deployment units being a package of software packaged together to be deployed on a single physical hardware platform, the plurality of deployment units including: a catalog authoring deployment unit that defines, edits and releases product catalogs; and a catalog publishing deployment unit that provides released product catalogs for use in business processes; and wherein: the catalog authoring deployment unit implements the maintain catalog, the change transmission status, the change publication status, the change catalog based on publication cancellation, the change catalog based on item lock status, the change catalog based on content change publication status, the request catalog publication, the request catalog publication cancellation, the request catalog item lock, the request catalog publication content change, and the notify of catalog update service operations; and the catalog publishing deployment unit implements the product catalog publishing process component implements the maintain published product catalog, the cancel catalog publication, the lock published catalog items, the change published catalog content, the notify of publication transmission package check, the confirm catalog publication, the confirm catalog publication cancellation, the confirm catalog item lock, and the confirm catalog publication content change service operations.
^ a n y one of cla ims 1 to l . \
8. The system of ^ further compπsing: a repository of service descriptions, the repository including a standards-based description of each of the plurality of service operations.
9. A computer program product encoded on a tangible machine-readable information carrier for implementing a plurality of services, the product comprising computer software operable to implement service operations on a computer system, the service operations comprising: a maintain catalog operation, the operation operable to send a notification to update a product catalog; a change transmission status operation, the operation operable to send a notification to change the transmission status of a product catalog; a change publication status operation, the operation operable to send a notification to change the publication status of a product catalog; a change catalog based on publication cancellation operation, the operation operable to send a notification to update a product catalog based on a publication cancellation; a change catalog based on item lock status operation, the operation operable to send a notification to update a product catalog based on a locked item; a change catalog based on content change publication status operation, the operation operable to send a notification to update a product catalog based on a catalog change content publication status; a request catalog publication operation, the operation requesting that a product catalog be published; a request catalog publication cancellation operation, the operation requesting a product catalog publication be cancelled; a request catalog item lock operation, the operation requesting an item in a product catalog to be locked; a request catalog publication content change operation, the operation requesting a content change in a product catalog publication; a notify of catalog update operation, the operation operable to send a notification about an update to a product catalog; a maintain published product catalog operation, the operation operable to send a notification to update a published product catalog; a cancel catalog publication operation, the operation operable to send a notification to cancel the publication of a product catalog; a lock published catalog items operation, the operation operable to send a notification to lock items contained in a published product catalog; a change published catalog content operation, the operation operable to send a notification to change the content in a published product catalog; a notify of publication transmission package check operation, the operation operable to send a notification about a catalog publication transmission package check; a confirm catalog publication operation, the operation operable to send a notification to confirm the publication of a product catalog; a confirm catalog publication cancellation operation, the operation operable to send a notification to confirm the cancellation of a product catalog publication; a confirm catalog item lock operation, the operation operable to send a notification to confirm the lock of an item in a product catalog; and a confirm catalog publication content change operation, the operation operable to send a notification to confirm the content change of a product catalog publication.
10. The product of claim 9, wherein the computer software comprises: a plurality of process components, each of the process components being a package of software deployed and executing on the computer system and implementing a respective and distinct business process, the plurality of process components including: a product catalog authoring process component used to create and edit product catalogs, to control the quality of their contents, and to control their readiness for publication; and a product catalog publishing process component used to make published product catalogs available electronically, and to provide a means to interactively search for and select products for use by other business processes; and wherein: the product catalog authoring process component implements the maintain catalog, the change transmission status, the change publication status, the change catalog based on publication cancellation, the change catalog based on item lock status, the change catalog based on content change publication status, the request catalog publication, the request catalog publication cancellation, the request catalog item lock, the request catalog publication content change, and the notify of catalog update service operations; and the product catalog publishing process component implements the maintain published product catalog, the cancel catalog publication, the lock published catalog items, the change published catalog content, the notify of publication transmission package check, the confirm catalog publication, the confirm catalog publication cancellation, the confirm catalog item lock, and the confirm catalog publication content change service operations.
, o r ' 10 j
11. The product of claim 9f wherein the computer software comprises: a catalog authoring deployment unit that includes a product catalog, a product catalog update run, a product catalog file upload run, a product catalog duplication run, a product catalog change list, a product catalog update method, and a product catalog publishing sending run business object, wherein the product catalog business object is a master data object representing a structured directory of catalog items where each catalog item represents a product and provides information about it, the product catalog update run business object represents a run to update product catalogs based on product catalog update methods, the product catalog file upload run business object represents a run to update a product catalog based on an uploaded file, the product catalog duplication run business object represents a run to copy a product catalog in total or in parts, the product catalog change list business object represents a list of changes to a product catalog, the product catalog update method business object represents a master data object representing a set of rules controlling how products are cataloged in a product catalog and how to update the product catalog when cataloged products are changed, and the product catalog publishing sending run business object represents a run to trigger sending a product catalog for publication; and a catalog publishing deployment unit that includes a published product catalog and a published product catalog update run business object, wherein the published product catalog business object is a master data object representing a version of a product catalog that has been released for access by or exchange with the target group of people for whom the product catalog has been tailored; and the published product catalog update run business object represents a run to update a product catalog based on an uploaded file.
12. The product of claim 10, wherein: each of the plurality of process components is assigned to no more than one deployment unit among multiple deployment units, and each deployment unit is deployable on a separate computer hardware platform independent of every other deployment unit; and all interaction between a process component in one deployment unit and any other process component in any other deployment unit takes place through the respective service operations of the two process components.
13. The product of claim 12, wherein the deployment units comprise: a catalog authoring deployment unit that includes the product catalog authoring process component; and a catalog publishing deployment unit that includes the product catalog publishing process component.
, any one of claims 9 to 13, t
14. The product of ^ further comprising: a catalog authoring deployment unit that implements the maintain catalog, the change transmission status, the change publication status, the change catalog based on publication cancellation, the change catalog based on item lock status, the change catalog based on content change publication status, the request catalog publication, the request catalog publication cancellation, the request catalog item lock, the request catalog publication content change, and the notify of catalog update service operations; and a catalog publishing deployment unit that implements the maintain published product catalog, the cancel catalog publication, the lock published catalog items, the change published catalog content, the notify of publication transmission package check, the confirm catalog publication, the confirm catalog publication cancellation, the confirm catalog item lock, and the confirm catalog publication content change service operations.
a n y o n e o f c l a ims IU t o 14 ,
15. The product of V wherein: the product catalog authoring process component includes a product catalog master data object, a product catalog update run business object, a product catalog file upload run business object, a product catalog duplication run business object, a product catalog change 5 list business object, a product catalog update method business object, and a product catalog publishing sending run business object, wherein: the product catalog master data object is the business object responsible for the structured directory of catalog items where each catalog item represents a product and provides information about it; o the product catalog update run business object is the business object responsible for the run to update product catalogs based on product catalog update methods; the product catalog file upload run business object is the business object responsible for the run to update a product catalog based on an uploaded file; the product catalog duplication run business object is the business object 5 responsible for the run to copy a product catalog in total or in parts; the product catalog change list business object is the business object responsible for the list of changes to a product catalog; the product catalog update method master data object is the business object responsible for the set of rules controlling how products are cataloged in a product catalog 0 and how to update the product catalog when cataloged products are changed; and the product catalog publishing sending run is the business object responsible for the run to trigger sending a product catalog for publication; and the product catalog publishing process component includes a published product catalog master data object and a published product catalog update run business object, 5 wherein: the published product catalog master data object is the business object responsible for the version of a product catalog that has been released for access by or exchange with the target group of people for whom the product catalog has been tailored; and the published product catalog update run business object is the business object 0 responsible for the run to update a product catalog based on an uploaded file. , any one of claims 10 to 15 , /
16. The product of ^ wherein: each of the process components includes one or more business objects; and none of the business objects of any one of the process components interacts directly with any of the business objects included in any of the other process components.
17. The product of claim 16, wherein the business objects comprise a business process object. or 17
18. The product of claim 16/wherein: none of the business objects included in any one of the process components is included in any of the other process components.
^ a n y o n e o.f c l a ims 9 t o 18 , y
19. The product ol v further comprising: a plurality of process agents, each process agent being either an inbound process agent or an outbound process agent, an inbound process agent being operable to receive a message from an inbound operation, an outbound process agent being operable to cause an outbound operation to send a message, each process agent being associated with exactly one process component; wherein: the inbound process agents comprise a first inbound process agent operable to start the execution of the step requested in a first inbound message by creating or updating one or more business object instances; and the outbound process agents comprise a first asynchronous outbound process agent that is called after a business object that is associated with the first outbound process agent changes.
20. A method for providing services from a computer system having product catalog functionality, the method comprising: providing services through the sending of messages, the messages including: a notification to update a product catalog; a notification to change the transmission status of a product catalog; a notification to change the publication status of a product catalog; a notification to update a product catalog based on a publication cancellation; a notification to update a product catalog based on a locked item; a notification to update a product catalog based on a catalog change content publication status; a notification requesting that a product catalog be published; a notification requesting a product catalog publication be cancelled; a notification requesting an item in a product catalog to be locked; a notification requesting a content change in a product catalog publication; a notification about an update to a product catalog; a notification to update a published product catalog; a notification to cancel the publication of a product catalog; a notification to lock items contained in a published product catalog; a notification to change the content in a published product catalog; a notification about a catalog publication transmission package check; a notification to confirm the publication of a product catalog; a notification to confirm the cancellation of a product catalog publication; a notification to confirm the lock of an item in a product catalog; and a notification to confirm the content change of a product catalog publication.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/396,250 | 2006-03-30 | ||
US11/396,250 US8396761B2 (en) | 2006-03-30 | 2006-03-30 | Providing product catalog software application as enterprise services |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2007112956A2 true WO2007112956A2 (en) | 2007-10-11 |
Family
ID=38198222
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/EP2007/002842 WO2007112956A2 (en) | 2006-03-30 | 2007-03-29 | Providing product catalog software application as enterprise services |
Country Status (2)
Country | Link |
---|---|
US (1) | US8396761B2 (en) |
WO (1) | WO2007112956A2 (en) |
Families Citing this family (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
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 |
US8370794B2 (en) | 2005-12-30 | 2013-02-05 | Sap Ag | Software model process component |
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 |
US8321831B2 (en) | 2005-12-30 | 2012-11-27 | Sap Ag | Architectural design for internal projects application software |
US8676617B2 (en) | 2005-12-30 | 2014-03-18 | Sap Ag | Architectural design for self-service procurement application software |
US8326703B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Architectural design for product catalog management application software |
US8448137B2 (en) | 2005-12-30 | 2013-05-21 | Sap Ag | Software model integration scenarios |
US8402426B2 (en) | 2005-12-30 | 2013-03-19 | Sap Ag | Architectural design for make to stock application software |
US8438119B2 (en) | 2006-03-30 | 2013-05-07 | Sap Ag | Foundation layer for services based enterprise software architecture |
US8326702B2 (en) | 2006-03-30 | 2012-12-04 | Sap Ag | Providing supplier relationship management software application as enterprise services |
US8442850B2 (en) | 2006-03-30 | 2013-05-14 | Sap Ag | Providing accounting software application as enterprise services |
US8538864B2 (en) | 2006-03-30 | 2013-09-17 | Sap Ag | Providing payment software application as enterprise services |
US8396749B2 (en) | 2006-03-30 | 2013-03-12 | Sap Ag | Providing customer relationship management application as enterprise services |
US8321832B2 (en) | 2006-03-31 | 2012-11-27 | Sap Ag | Composite application modeling |
US7877433B2 (en) * | 2006-10-16 | 2011-01-25 | Hewlett-Packard Development Company, L.P. | Infrastructure by contract |
US8332851B2 (en) * | 2006-12-28 | 2012-12-11 | Sap Ag | Configuration and execution of mass data run objects |
US20080162344A1 (en) * | 2006-12-29 | 2008-07-03 | Sap Ag | Method and system for enterprise software having direct debit mandates |
US8447657B2 (en) | 2007-12-31 | 2013-05-21 | Sap Ag | Architectural design for service procurement application software |
US8380549B2 (en) | 2008-09-18 | 2013-02-19 | Sap Ag | Architectural design for embedded support application software |
US8374896B2 (en) | 2008-09-18 | 2013-02-12 | Sap Ag | Architectural design for opportunity management 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 |
US8352338B2 (en) | 2008-09-18 | 2013-01-08 | Sap Ag | Architectural design for time recording application software |
US8818884B2 (en) | 2008-09-18 | 2014-08-26 | Sap Ag | Architectural design for customer returns handling application software |
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 |
US8738476B2 (en) | 2008-12-03 | 2014-05-27 | Sap Ag | Architectural design for selling standardized services application software |
US8311904B2 (en) * | 2008-12-03 | 2012-11-13 | Sap Ag | Architectural design for intra-company stock transfer application software |
US8401908B2 (en) | 2008-12-03 | 2013-03-19 | Sap Ag | Architectural design for make-to-specification application software |
US8671035B2 (en) | 2008-12-11 | 2014-03-11 | Sap Ag | Providing payroll software application as enterprise services |
US20100153150A1 (en) * | 2008-12-12 | 2010-06-17 | Sap Ag | Software for business adaptation catalog modeling |
US20100153149A1 (en) * | 2008-12-12 | 2010-06-17 | Sap Ag | Software for model-based configuration constraint generation |
US9626700B1 (en) | 2011-09-29 | 2017-04-18 | Amazon Technologies, Inc. | Aggregation of operational data for merchandizing of network accessible services |
US8776043B1 (en) * | 2011-09-29 | 2014-07-08 | Amazon Technologies, Inc. | Service image notifications |
US10147123B2 (en) | 2011-09-29 | 2018-12-04 | Amazon Technologies, Inc. | Electronic marketplace for hosted service images |
US9530156B2 (en) | 2011-09-29 | 2016-12-27 | Amazon Technologies, Inc. | Customizable uniform control user interface for hosted service images |
US9477944B2 (en) * | 2012-04-30 | 2016-10-25 | International Business Machines Corporation | Asynchronous serialization for aggregating process results |
US11367133B2 (en) | 2016-03-01 | 2022-06-21 | Finx Software Technolgy Inc. | System and method for determining interest rates and interest rate buy down for indirect financing transactions |
US10664907B2 (en) | 2016-03-01 | 2020-05-26 | Finx Software Technology Inc. | System and method for determining interest rates and interest rate buy down for indirect financing transactions |
Family Cites Families (317)
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 |
AU6019994A (en) | 1993-09-13 | 1995-04-03 | Taligent, Inc. | Multimedia data routing system |
US5550734A (en) | 1993-12-23 | 1996-08-27 | The Pharmacy Fund, Inc. | Computerized healthcare accounts receivable purchasing collections securitization and management system |
US5560005A (en) | 1994-02-25 | 1996-09-24 | Actamed Corp. | Methods and systems for object-based relational distributed databases |
US5586312A (en) | 1994-10-11 | 1996-12-17 | Unisys Corporation | Method and apparatus for using an independent transaction processing application as a service routine |
US5634127A (en) * | 1994-11-30 | 1997-05-27 | International Business Machines Corporation | Methods and apparatus for implementing a message driven processor in a client-server environment |
US5918219A (en) | 1994-12-14 | 1999-06-29 | Isherwood; John Philip | System and method for estimating construction project costs and schedules based on historical data |
JPH08286962A (en) * | 1994-12-16 | 1996-11-01 | Internatl Business Mach Corp <Ibm> | Processing system and method for scheduling of object activation |
US5822585A (en) | 1995-02-21 | 1998-10-13 | Compuware Corporation | System and method for cooperative processing using object-oriented framework |
US5680619A (en) | 1995-04-03 | 1997-10-21 | Mfactory, Inc. | Hierarchical encapsulation of instantiated objects in a multimedia authoring system |
US5710917A (en) * | 1995-06-07 | 1998-01-20 | International Business Machines Corporation | Method for deriving data mappings and data aliases |
US6272672B1 (en) | 1995-09-06 | 2001-08-07 | Melvin E. Conway | Dataflow processing with events |
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 |
US6038393A (en) * | 1997-09-22 | 2000-03-14 | Unisys Corp. | Software development tool to accept object modeling data from a wide variety of other vendors and filter the format into a format that is able to be stored in OMG compliant UML representation |
US6128602A (en) | 1997-10-27 | 2000-10-03 | Bank Of America Corporation | Open-architecture system for real-time consolidation of information from multiple financial systems |
US6237136B1 (en) * | 1997-12-02 | 2001-05-22 | National Instruments Corporation | System and method for automatically creating source code example files for an application program in a plurality of programming languages |
US6182133B1 (en) * | 1998-02-06 | 2001-01-30 | Microsoft Corporation | Method and apparatus for display of information prefetching and cache status having variable visual indication based on a period of time since prefetching |
US6208345B1 (en) * | 1998-04-15 | 2001-03-27 | Adc Telecommunications, Inc. | Visual data integration system and method |
JP3925584B2 (en) | 1998-06-09 | 2007-06-06 | ソニー株式会社 | Replication generation management method and recording / reproducing system |
US6338097B1 (en) * | 1998-06-19 | 2002-01-08 | Sap Aktiengesellschaft | Cross application time sheet for communicating with one or more enterprise management applications during time data entry |
US7216091B1 (en) | 1998-06-26 | 2007-05-08 | American Express Travel Related Services Company, Inc. | Stored value transaction system including an integrated database server |
US6434740B1 (en) | 1998-07-15 | 2002-08-13 | International Business Machines Corporation | Apparatus and method for visual construction simplification |
US6177932B1 (en) * | 1998-08-21 | 2001-01-23 | Kana Communications, Inc. | Method and apparatus for network based customer service |
EP1105826A1 (en) * | 1998-08-27 | 2001-06-13 | Upshot Corporation | A method and apparatus for network-based sales force management |
US6167564A (en) | 1998-09-17 | 2000-12-26 | Unisys Corp. | Software system development framework |
US6167563A (en) | 1998-09-17 | 2000-12-26 | Unisys Corporation | Method and system for building components in a framework useful in developing integrated business-centric applications |
US7283973B1 (en) | 1998-10-07 | 2007-10-16 | Logic Tree Corporation | Multi-modal voice-enabled content access and delivery system |
US7131069B1 (en) | 1998-10-22 | 2006-10-31 | Made2 Manage Systems, Inc. | Navigational interface for ERP system |
US7236950B2 (en) * | 1998-10-29 | 2007-06-26 | Universal Card Services Corp. | Method and system of combined billing of multiple accounts on a single statement |
FR2787902B1 (en) | 1998-12-23 | 2004-07-30 | France Telecom | MODEL AND METHOD FOR IMPLEMENTING A RATIONAL DIALOGUE AGENT, SERVER AND MULTI-AGENT SYSTEM FOR IMPLEMENTATION |
US6851115B1 (en) * | 1999-01-05 | 2005-02-01 | Sri International | Software-based architecture for communication and cooperation among distributed electronic agents |
US6594535B1 (en) | 1999-01-11 | 2003-07-15 | Demand Flow Institute, Llc | Material and inventory control system for a demand flow process |
US7155409B1 (en) | 1999-03-05 | 2006-12-26 | Trade Finance Service Corporation | Trade financing method, instruments and systems |
US6738964B1 (en) | 1999-03-11 | 2004-05-18 | Texas Instruments Incorporated | Graphical development system and method |
US6789252B1 (en) | 1999-04-15 | 2004-09-07 | Miles D. Burke | Building business objects and business software applications using dynamic object definitions of ingrediential objects |
US6473794B1 (en) | 1999-05-27 | 2002-10-29 | Accenture Llp | System for establishing plan to test components of web based framework by displaying pictorial representation and conveying indicia coded components of existing network framework |
US6533168B1 (en) | 1999-05-27 | 2003-03-18 | Peter N. Ching | Method and apparatus for computer-readable purchase receipts using multi-dimensional bar codes |
US6678882B1 (en) * | 1999-06-30 | 2004-01-13 | Qwest Communications International Inc. | Collaborative model for software systems with synchronization submodel with merge feature, automatic conflict resolution and isolation of potential changes for reuse |
US7152228B2 (en) * | 1999-07-08 | 2006-12-19 | Science Applications International Corporation | Automatically generated objects within extensible object frameworks and links to enterprise resources |
US6601233B1 (en) | 1999-07-30 | 2003-07-29 | Accenture Llp | Business components framework |
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 |
US7139999B2 (en) | 1999-08-31 | 2006-11-21 | Accenture Llp | Development architecture framework |
US6601234B1 (en) | 1999-08-31 | 2003-07-29 | Accenture Llp | Attribute dictionary in a business logic services environment |
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 |
US7797195B2 (en) | 1999-09-17 | 2010-09-14 | Michael Jay Langhammer | Merchant-affiliated direct wholesale marketing and fulfillment system |
US7047219B1 (en) | 1999-10-04 | 2006-05-16 | Trade Finance Systems, Inc. | Trade finance automation system |
US20110191747A1 (en) | 1999-10-05 | 2011-08-04 | Borland Software Corporation | Supporting and deploying distributed computing components |
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 |
EP1269362A4 (en) | 2000-01-21 | 2007-10-17 | Amcor Ltd | System for specifying design of a product or process |
US7376599B1 (en) * | 2000-01-28 | 2008-05-20 | General Electric Company | Virtual warehouse parts distribution system and process |
US6747679B1 (en) | 2000-01-31 | 2004-06-08 | Journyx, Inc. | Time keeping and expense tracking server that interfaces with a user based upon a user's atomic abilities |
US6750885B1 (en) | 2000-01-31 | 2004-06-15 | Journyx, Inc. | Time keeping and expense tracking server that interfaces with a user based upon a user's atomic abilities |
US6934532B2 (en) | 2000-02-09 | 2005-08-23 | Apriva, Inc. | Communication systems, components, and methods operative with programmable wireless devices |
US7437408B2 (en) | 2000-02-14 | 2008-10-14 | Lockheed Martin Corporation | Information aggregation, processing and distribution system |
US7283977B1 (en) | 2000-02-25 | 2007-10-16 | Kathleen Tyson-Quah | System for reducing risk payment-based transactions wherein a risk filter routine returns instructions authorizing payment to a payment queue for later re-evaluation |
US20010034880A1 (en) | 2000-03-02 | 2001-10-25 | Jonathan Dzoba | Configurable debug system using source and data objects |
US20070239569A1 (en) | 2000-03-07 | 2007-10-11 | Michael Lucas | Systems and methods for managing assets |
US6687734B1 (en) * | 2000-03-21 | 2004-02-03 | America Online, Incorporated | System and method for determining if one web site has the same information as another web site |
US6671673B1 (en) | 2000-03-24 | 2003-12-30 | International Business Machines Corporation | Method for integrated supply chain and financial management |
US7353180B1 (en) * | 2000-04-17 | 2008-04-01 | Accenture Llp | Supply chain/workflow services in a contract manufacturing framework |
WO2001082071A1 (en) | 2000-04-21 | 2001-11-01 | Togethersoft Corporation | Methods and systems for supporting and deploying distributed computing components |
US20020049622A1 (en) * | 2000-04-27 | 2002-04-25 | Lettich Anthony R. | Vertical systems and methods for providing shipping and logistics services, operations and products to an industry |
US7194431B1 (en) * | 2000-05-02 | 2007-03-20 | Ge Corporate Financial Services, Inc. | Method and apparatus for managing remittance processing within account receivables |
US6772216B1 (en) | 2000-05-19 | 2004-08-03 | Sun Microsystems, Inc. | Interaction protocol for managing cross company processes among network-distributed applications |
US7225240B1 (en) | 2000-05-20 | 2007-05-29 | Ciena Corporation | Decoupling processes from hardware with logical identifiers |
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 |
US6898783B1 (en) | 2000-08-03 | 2005-05-24 | International Business Machines Corporation | Object oriented based methodology for modeling business functionality for enabling implementation in a web based environment |
US6990466B1 (en) * | 2000-08-08 | 2006-01-24 | International Business Machines Corporation | Method and system for integrating core banking business processes |
US7315830B1 (en) * | 2000-08-11 | 2008-01-01 | Nexus Company, Ltd. | Method, system and computer program product for ordering merchandise in a global computer network environment |
US7206768B1 (en) | 2000-08-14 | 2007-04-17 | Jpmorgan Chase Bank, N.A. | Electronic multiparty accounts receivable and accounts payable system |
US7136857B2 (en) * | 2000-09-01 | 2006-11-14 | Op40, Inc. | Server system and method for distributing and scheduling modules to be executed on different tiers of a network |
US6895438B1 (en) | 2000-09-06 | 2005-05-17 | Paul C. Ulrich | Telecommunication-based time-management system and method |
US7155403B2 (en) | 2001-03-22 | 2006-12-26 | International Business Machines Corporation | System and method for leveraging procurement across companies and company groups |
US7047518B2 (en) | 2000-10-04 | 2006-05-16 | Bea Systems, Inc. | System for software application development and modeling |
US7249044B2 (en) * | 2000-10-05 | 2007-07-24 | I2 Technologies Us, Inc. | Fulfillment management system for managing ATP data in a distributed supply chain environment |
US6907395B1 (en) | 2000-10-24 | 2005-06-14 | Microsoft Corporation | System and method for designing a logical model of a distributed computer system and deploying physical resources according to the logical model |
TW541483B (en) * | 2000-10-27 | 2003-07-11 | Manugistics Inc | System and method for ensuring order fulfillment |
WO2002037394A2 (en) | 2000-10-30 | 2002-05-10 | Tririga, Inc. | sUSINESS ASSET MANAGEMENT SYSTEM |
WO2002041197A1 (en) * | 2000-11-15 | 2002-05-23 | Virtual Supply Logic Pty Limited | Collaborative commerce hub |
US6889375B1 (en) | 2000-11-17 | 2005-05-03 | Cisco Technology, Inc. | Method and system for application development |
US7370315B1 (en) | 2000-11-21 | 2008-05-06 | Microsoft Corporation | Visual programming environment providing synchronization between source code and graphical component objects |
US20020103660A1 (en) | 2000-11-30 | 2002-08-01 | Kurt Cramon | Generic transaction server |
US7020869B2 (en) | 2000-12-01 | 2006-03-28 | Corticon Technologies, Inc. | Business rules user interface for development of adaptable enterprise applications |
WO2002096008A2 (en) | 2000-12-22 | 2002-11-28 | Aidentity Matrix Medical, Inc. | Multi-agent collaborative architecture for problem solving and tutoring |
US7120597B1 (en) | 2000-12-27 | 2006-10-10 | Kermit Knudtzon | Computerized accounting systems and methods |
TW591456B (en) * | 2001-01-08 | 2004-06-11 | Wu-Jie Wang | Supply chain computer management system applying the constant value-quantity principle for single-cell/cell-group/boundary of supply chain |
WO2002057889A2 (en) | 2001-01-19 | 2002-07-25 | Globalserve Computer Services, Ltd. | Electronic procurement ('e-procurement') |
US7212976B2 (en) | 2001-01-22 | 2007-05-01 | W.W. Grainger, Inc. | Method for selecting a fulfillment plan for moving an item within an integrated supply chain |
US7313534B2 (en) | 2001-01-22 | 2007-12-25 | W.W. Grainger, Inc. | System and method for predictive maintenance and service parts fulfillment in a supply chain |
US7324966B2 (en) * | 2001-01-22 | 2008-01-29 | W.W. Grainger | Method for fulfilling an order in an integrated supply chain management system |
US7058587B1 (en) | 2001-01-29 | 2006-06-06 | Manugistics, Inc. | System and method for allocating the supply of critical material components and manufacturing capacity |
US6845499B2 (en) * | 2001-01-31 | 2005-01-18 | I2 Technologies Us, Inc. | System and method for developing software applications using an extended XML-based framework |
US7299202B2 (en) | 2001-02-07 | 2007-11-20 | Exalt Solutions, Inc. | Intelligent multimedia e-catalog |
US7899721B2 (en) | 2001-02-27 | 2011-03-01 | Accenture Global Services Gmbh | E-commerce system, method and computer program product |
US6954736B2 (en) | 2001-03-23 | 2005-10-11 | Restaurant Services, Inc. | System, method and computer program product for order confirmation in a supply chain management framework |
US20030069774A1 (en) * | 2001-04-13 | 2003-04-10 | Hoffman George Harry | System, method and computer program product for distributor/supplier selection in a supply chain management framework |
US7120896B2 (en) | 2001-10-31 | 2006-10-10 | Vitria Technology, Inc. | Integrated business process modeling environment and models created thereby |
US20020198798A1 (en) | 2001-04-03 | 2002-12-26 | Bottomline Technologies, Inc. | Modular business transactions platform |
US20020198828A1 (en) | 2001-04-03 | 2002-12-26 | Bottomline Technologies, Inc. | Modular business transactions platform |
US7376600B1 (en) | 2001-04-11 | 2008-05-20 | I2 Technologies Us, Inc. | Intelligent fulfillment agents |
EP1390844A4 (en) | 2001-04-24 | 2006-01-18 | Breed Automotive Tech | Simplified modeling software interface and method |
US20020161907A1 (en) | 2001-04-25 | 2002-10-31 | Avery Moon | Adaptive multi-protocol communications system |
US7761319B2 (en) | 2001-06-08 | 2010-07-20 | Click Acqusitions, Inc. | Supply chain management |
US7117447B2 (en) | 2001-06-08 | 2006-10-03 | Mci, Llc | Graphical user interface (GUI) based call application system |
EP1410196B1 (en) * | 2001-06-22 | 2019-08-07 | AVEVA Software, LLC | Installing supervisory process control and manufacturing software from a remote location and maintaining configuration data links in a run-time environment |
EP1410228B1 (en) * | 2001-06-22 | 2016-03-23 | Wonderware Corporation | Remotely monitoring / diagnosing distributed components of a supervisory process control and manufacturing information application from a central location |
US7069536B2 (en) | 2001-06-28 | 2006-06-27 | International Business Machines Corporation | Method, system, and program for executing a workflow |
US7322024B2 (en) * | 2002-03-18 | 2008-01-22 | Logiclibrary, Inc. | Generating reusable software assets from distributed artifacts |
US7904350B2 (en) * | 2001-07-20 | 2011-03-08 | International Business Machines Corporation | Network-based supply chain management method |
US6847854B2 (en) | 2001-08-10 | 2005-01-25 | Rockwell Automation Technologies, Inc. | System and method for dynamic multi-objective optimization of machine selection, integration and utilization |
US6985939B2 (en) * | 2001-09-19 | 2006-01-10 | International Business Machines Corporation | Building distributed software services as aggregations of other services |
US7415697B1 (en) | 2001-10-04 | 2008-08-19 | Perot Systems Corporation | Method and system for providing visualization of underlying architecture of a software system |
US7337132B2 (en) * | 2001-10-17 | 2008-02-26 | Sun Microsystems, Inc. | Customizable two step mapping of extensible markup language data in an e-procurement system and method |
JP3730900B2 (en) * | 2001-11-02 | 2006-01-05 | 本田技研工業株式会社 | Internal combustion engine |
US7222786B2 (en) | 2001-11-14 | 2007-05-29 | Sap Ag | Inventory early warning agent with correction by error correlation calculation |
US7200569B2 (en) * | 2001-11-26 | 2007-04-03 | Hewlett-Packard Development Company, L.P. | Intelligent apparatus, system and method for financial data computation and analysis |
AU2002351195A1 (en) | 2001-11-28 | 2003-06-10 | Isuppli Corporation | Supply chain network |
US7383201B2 (en) | 2001-12-05 | 2008-06-03 | Canon Kabushiki Kaisha | Demand forecast device, method, and program product |
US7376604B1 (en) | 2001-12-27 | 2008-05-20 | Goldman Sachs & Co. | Method for investing yield restricted monies |
US7460654B1 (en) | 2001-12-28 | 2008-12-02 | Vocada, Inc. | Processing of enterprise messages integrating voice messaging and data systems |
US7281235B2 (en) | 2002-01-09 | 2007-10-09 | International Business Machines Corporation | Computer controlled system for modularizing the information technology structure of a business enterprise into a structure of holonic self-contained modules |
US6914374B2 (en) | 2002-01-09 | 2005-07-05 | Hewlett-Packard Development Company, L.P. | Planar electron emitter apparatus with improved emission area and method of manufacture |
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 |
US7386833B2 (en) | 2002-09-04 | 2008-06-10 | Mentor Graphics Corp. | Polymorphic computational system and method in signals intelligence analysis |
EP1403793A1 (en) | 2002-09-27 | 2004-03-31 | Sap Ag | Method for automatic integrated document filing in the logging of business transactions |
CA2406105A1 (en) | 2002-09-30 | 2004-03-30 | Canadian National Railway Company | Method and system for generating account reconciliation data |
US8600804B2 (en) | 2002-11-07 | 2013-12-03 | Novitaz, Inc. | Customer relationship management system for physical locations |
US7725354B2 (en) | 2002-11-18 | 2010-05-25 | Sap Aktiengesellschaft | Interface for generating business partners |
US20040111304A1 (en) | 2002-12-04 | 2004-06-10 | International Business Machines Corporation | System and method for supply chain aggregation and web services |
US7412418B2 (en) | 2002-12-06 | 2008-08-12 | Ocwen Financial Corporation | Expense tracking, electronic ordering, invoice presentment, and payment system and method |
US7640291B2 (en) | 2002-12-16 | 2009-12-29 | Rockwell Automation Technologies, Inc. | Agent-equipped controller having data table interface between agent-type programming and non-agent-type programming |
US7050056B2 (en) | 2002-12-20 | 2006-05-23 | Sap Aktiengesellschaft | Interactive and web-based Gantt Chart |
US7219107B2 (en) | 2002-12-23 | 2007-05-15 | Sap Ag | Collaborative information spaces |
US20040128180A1 (en) | 2002-12-27 | 2004-07-01 | Claus-Dieter Abel | Integrating logistic and financial control of projects |
US20040153359A1 (en) | 2003-01-31 | 2004-08-05 | Mein-Kai Ho | Integrated supply chain management |
AT501256A2 (en) | 2003-02-06 | 2006-07-15 | Mobilkom Austria Ag & Co Kg | SYSTEM FOR THE MANAGEMENT OF PRODUCTS AND PRODUCT PARTS OR ASSOCIATED SERIAL NUMBERS AND DATA PROCESSING SYSTEM |
JP4387116B2 (en) | 2003-02-28 | 2009-12-16 | 株式会社日立製作所 | Storage system control method and storage system |
US8122106B2 (en) * | 2003-03-06 | 2012-02-21 | Microsoft Corporation | Integrating design, deployment, and management phases for systems |
US20040181470A1 (en) | 2003-03-11 | 2004-09-16 | Electronic Data Systems Corporation | System, method, and computer program product for taxation of online transactions |
US7313561B2 (en) | 2003-03-12 | 2007-12-25 | Microsoft Corporation | Model definition schema |
US8510179B2 (en) | 2003-03-24 | 2013-08-13 | Siebel Systems, Inc. | Inventory transaction common object |
EP1469411A1 (en) | 2003-04-18 | 2004-10-20 | Matsushita Electric Industrial Co., Ltd. | System supporting consolidated accounting |
US20050209732A1 (en) | 2003-04-28 | 2005-09-22 | Srinivasaragavan Audimoolam | Decision support system for supply chain management |
US20070150855A1 (en) | 2003-05-12 | 2007-06-28 | Jeong An M | Method and system of developing a software with utilizing extended metadata of component under component-based development environment |
CN1791861A (en) | 2003-05-16 | 2006-06-21 | Sap股份公司 | Business process management for a message-based exchange infrastructure |
US20040236639A1 (en) | 2003-05-20 | 2004-11-25 | Arun Candadai | Dynamic data collaboration |
US20040243489A1 (en) | 2003-05-27 | 2004-12-02 | International Business Machines Corporation | Expense accounting data management based on electronic expense document |
US7546575B1 (en) | 2003-06-09 | 2009-06-09 | Dillman Frederick J | System and method for using blueprints to provide a software solution for an enterprise |
US7406716B2 (en) | 2003-06-10 | 2008-07-29 | Kabushiki Kaisha Toshiba | Software IP providing system and method, software IP obtaining method, and IP core designing and manufacturing method |
US8036962B2 (en) | 2003-06-13 | 2011-10-11 | Sap Ag | Systems and methods for determining payers in a billing environment |
US7742985B1 (en) | 2003-06-26 | 2010-06-22 | Paypal Inc. | Multicurrency exchanges between participants of a network-based transaction facility |
US20050010501A1 (en) * | 2003-07-10 | 2005-01-13 | Ward Lycurgus B. | Internet-based back office payroll service and method thereof |
US7257254B2 (en) | 2003-07-24 | 2007-08-14 | Sap Ag | Method and system for recognizing time |
US20050033588A1 (en) * | 2003-08-04 | 2005-02-10 | Mario Ruiz | Information system comprised of synchronized software application moduless with individual databases for implementing and changing business requirements to be automated |
US8121913B2 (en) * | 2003-08-19 | 2012-02-21 | Swiss Reinsurance Company Ltd. | Architecture for account reconciliation |
US20050240592A1 (en) | 2003-08-27 | 2005-10-27 | Ascential Software Corporation | Real time data integration for supply chain management |
US8060553B2 (en) | 2003-08-27 | 2011-11-15 | International Business Machines Corporation | Service oriented architecture for a transformation function in a data integration platform |
US7814142B2 (en) | 2003-08-27 | 2010-10-12 | International Business Machines Corporation | User interface service for a services oriented architecture in a data integration platform |
US7197740B2 (en) * | 2003-09-05 | 2007-03-27 | Sap Aktiengesellschaft | Pattern-based software design |
US7293254B2 (en) | 2003-09-18 | 2007-11-06 | Microsoft Corporation | Extensibility application programming interface and framework for meta-model objects |
US20050222896A1 (en) | 2003-09-19 | 2005-10-06 | Rhyne Joseph C | Systems, methods, and software for leveraging informational assets across multiple business units |
US7711602B2 (en) * | 2003-09-23 | 2010-05-04 | Ryder Integrated Logistics | Systems and methods for supply chain management |
US7418409B1 (en) | 2003-10-24 | 2008-08-26 | Sachin Goel | System for concurrent optimization of business economics and customer value satisfaction |
US20050114829A1 (en) | 2003-10-30 | 2005-05-26 | Microsoft Corporation | Facilitating the process of designing and developing a project |
US20050144226A1 (en) | 2003-11-10 | 2005-06-30 | Churchill Software Services | Systems and methods for modeling and generating reusable application component frameworks, and automated assembly of service-oriented applications from existing applications |
US7756751B2 (en) | 2003-11-17 | 2010-07-13 | International Business Machines Corporation | Architecture for business process integration |
US7835971B2 (en) | 2003-12-12 | 2010-11-16 | Michael Stockton | Method and system configured for facilitating management of international trade receivables transactions |
US7765156B2 (en) | 2003-12-31 | 2010-07-27 | American Express Travel Related Services Company, Inc. | Method and apparatus for automatically processing invoiced payments with selectable payment terms |
US20070197877A1 (en) | 2004-01-05 | 2007-08-23 | Stefaan Decorte | Behavior Based Multi-Agent Systems As Data Types |
US20050160104A1 (en) | 2004-01-20 | 2005-07-21 | Datasource, Inc. | System and method for generating and deploying a software application |
US8615487B2 (en) | 2004-01-23 | 2013-12-24 | Garrison Gomez | System and method to store and retrieve identifier associated information content |
US7448022B1 (en) | 2004-02-10 | 2008-11-04 | Prasad Ram | Dynamic software composition in a component-based software system |
US7899725B2 (en) | 2004-03-02 | 2011-03-01 | Accenture Global Services Limited | Enhanced business reporting methodology |
US8046273B2 (en) | 2004-03-08 | 2011-10-25 | Sap Ag | System and method for purchase order creation, procurement, and controlling |
US8050956B2 (en) | 2004-03-08 | 2011-11-01 | Sap Ag | Computer-readable medium, program product, and system for providing a schedule bar with event dates to monitor procurement of a product |
US20050203760A1 (en) | 2004-03-15 | 2005-09-15 | Microsoft Corporation | Project time and expense |
US7793258B2 (en) | 2004-03-15 | 2010-09-07 | Ramco Systems Limited | Software development using visual interfaces |
US7367011B2 (en) * | 2004-04-13 | 2008-04-29 | International Business Machines Corporation | Method, system and program product for developing a data model in a data mining system |
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 |
US20050257197A1 (en) | 2004-05-11 | 2005-11-17 | Klaus Herter | Role-based object models |
US9026455B2 (en) | 2004-05-14 | 2015-05-05 | Sap Ag | Methods and systems for processing stock in a storage facility |
US7665064B2 (en) | 2004-05-14 | 2010-02-16 | Gt Software, Inc. | Systems and methods for web service function, definition, implementation, and/or execution |
US8554805B2 (en) | 2004-05-17 | 2013-10-08 | Sap Ag | Methods and systems for importing source data |
US20050289079A1 (en) | 2004-05-17 | 2005-12-29 | Shimon Systems, Inc. | Systems and methods for biometric identification |
WO2005122078A2 (en) * | 2004-06-04 | 2005-12-22 | Sap Ag | Consistent set of interfaces derived from a business object model |
CN101031882B (en) * | 2004-06-08 | 2010-09-08 | 达尔特设备互操作有限公司 | Architecture, apparatus and method for device team recruitment and content renditioning for universal device interoperability platform |
US20080167916A1 (en) | 2004-06-14 | 2008-07-10 | Symphonyrpm, Inc. | Decision object for associating a plurality of business plans |
WO2006038924A2 (en) * | 2004-06-18 | 2006-04-13 | Sap Ag | Consistent set of interfaces derived from a business object model |
US7770792B2 (en) | 2004-06-23 | 2010-08-10 | Sap Ag | Methods and systems for managing stock transportation |
US7669763B2 (en) | 2004-06-23 | 2010-03-02 | Sap Ag | Methods and system for managing stock |
US20050288987A1 (en) | 2004-06-29 | 2005-12-29 | Sap Aktiengesellschaft | Vacation planning and approval |
US20080288379A1 (en) * | 2004-06-29 | 2008-11-20 | Allin Patrick J | Construction payment management system and method with automated electronic document generation features |
US7665083B2 (en) * | 2004-07-16 | 2010-02-16 | Sap Ag | Method and apparatus for supporting context links for application program text |
US7376601B1 (en) | 2004-08-18 | 2008-05-20 | Teradata Us, Inc. | System and method for determining sell-through time and inventory aging for retail products |
US7664684B2 (en) * | 2004-08-27 | 2010-02-16 | Sap Ag | Method and system for catch-weight management |
US7831463B2 (en) * | 2004-09-07 | 2010-11-09 | Sap Ag | Computer-implemented method and system for allocating customer demand to suppliers |
US20060085243A1 (en) * | 2004-09-24 | 2006-04-20 | Workscape, Inc. | Business process management method and system |
US7805324B2 (en) * | 2004-10-01 | 2010-09-28 | Microsoft Corporation | Unified model for authoring and executing flow-based and constraint-based workflows |
US20060074704A1 (en) * | 2004-10-01 | 2006-04-06 | Microsoft Corporation | Framework to model cross-cutting behavioral concerns in the workflow domain |
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 |
US7451432B2 (en) | 2004-10-01 | 2008-11-11 | Microsoft Corporation | Transformation of componentized and extensible workflow to a declarative format |
US20060089886A1 (en) * | 2004-10-27 | 2006-04-27 | Anthony Wong | E-commerce business methodologies for supply and demand chain management |
US8352478B2 (en) | 2004-10-29 | 2013-01-08 | Sap Ag | Master data framework |
US20060274720A1 (en) | 2004-11-09 | 2006-12-07 | Andrew Adams | Systems and methods for multicast routing on packet switched networks |
US7797698B2 (en) | 2004-11-17 | 2010-09-14 | International Business Machines Corporation | Method and apparatus for dynamic middleware assembly |
US7739160B1 (en) | 2004-12-22 | 2010-06-15 | Ryan, Inc. | Dynamic, rule-based, tax-decision system |
US7974855B2 (en) | 2004-12-27 | 2011-07-05 | General Electric Company | System and method for identifying, representing and evaluating information and decision flow requirements and processes in a transactional business system |
US8744937B2 (en) | 2005-02-25 | 2014-06-03 | Sap Ag | Consistent set of interfaces derived from a business object model |
US7681176B2 (en) * | 2005-03-04 | 2010-03-16 | Microsoft Corporation | Generating a graphical designer application for developing graphical models |
US20060206352A1 (en) | 2005-03-14 | 2006-09-14 | Pulianda Arunkumar G | System for seamless enablement of compound enterprise-processes |
US7890389B2 (en) | 2005-05-17 | 2011-02-15 | Sap Ag | Methods and systems for grouping and managing stock requests |
WO2006133157A2 (en) * | 2005-06-07 | 2006-12-14 | Kyube Sal | Computer method and apparatus for developing web pages and applications |
US7822682B2 (en) | 2005-06-08 | 2010-10-26 | Jpmorgan Chase Bank, N.A. | System and method for enhancing supply chain transactions |
US7657406B2 (en) * | 2005-06-09 | 2010-02-02 | Intepoint, Llc | Multi-infrastructure modeling system |
US7827554B2 (en) | 2005-06-20 | 2010-11-02 | Microsoft Corporation | Multi-thread multimedia processing |
US20080065437A1 (en) * | 2005-07-06 | 2008-03-13 | Dybvig Alan J | System and Method for Budgeting, Planning, and Supply Chain Management |
US7925985B2 (en) * | 2005-07-29 | 2011-04-12 | Sap Ag | Methods and apparatus for process thumbnail view |
US7693586B2 (en) * | 2005-09-02 | 2010-04-06 | Sap Ag | Process model transformation for event-based coordination of composite applications |
EP1934905A4 (en) | 2005-09-02 | 2010-08-25 | Ecmarket Inc | Method and system for exchanging business documents |
US7912755B2 (en) * | 2005-09-23 | 2011-03-22 | Pronto, Inc. | Method and system for identifying product-related information on a web page |
US8782539B2 (en) * | 2005-10-05 | 2014-07-15 | Invensys Systems, Inc. | Generic utility supporting on-demand creation of customizable graphical user interfaces for viewing and specifying field device parameters |
US9152941B2 (en) * | 2005-10-11 | 2015-10-06 | Sap Se | Systems and methods for automated parallelization of back-order processing |
US8001019B2 (en) * | 2005-10-24 | 2011-08-16 | The Boeing Company | Managing access to and updating warehouse data |
US20070143164A1 (en) | 2005-12-01 | 2007-06-21 | Sanjeev Kaila | Business practice management system |
EP1798675A1 (en) | 2005-12-05 | 2007-06-20 | Sap Ag | Consolidation of third party order processing items |
EP1806686A1 (en) | 2005-12-05 | 2007-07-11 | Sap Ag | Restriction of the number of locations |
EP1798676A1 (en) | 2005-12-05 | 2007-06-20 | Sap Ag | Third party order processing within ATP check |
US20070150332A1 (en) | 2005-12-22 | 2007-06-28 | Caterpillar Inc. | Heuristic supply chain modeling method and system |
US20070156731A1 (en) | 2005-12-23 | 2007-07-05 | Sap Ag | Automatic project management application |
US20070156482A1 (en) | 2005-12-29 | 2007-07-05 | Sap Ag | System and method for generating and providing priority information |
US8316344B2 (en) | 2005-12-30 | 2012-11-20 | Sap Ag | Software model deployment units |
US20070174145A1 (en) | 2005-12-30 | 2007-07-26 | Stephan Hetzer | Controlling logistics execution in a computer application |
US8327319B2 (en) | 2005-12-30 | 2012-12-04 | Sap Ag | Software model process interaction |
US8676617B2 (en) | 2005-12-30 | 2014-03-18 | Sap Ag | Architectural design for self-service procurement application software |
US20070156500A1 (en) | 2005-12-30 | 2007-07-05 | Wilfried Merkel | Architectural design for sell from stock application software |
US8407664B2 (en) | 2005-12-30 | 2013-03-26 | Sap Ag | Software model business objects |
US8396731B2 (en) | 2005-12-30 | 2013-03-12 | Sap Ag | Architectural design for service procurement application software |
US8370794B2 (en) | 2005-12-30 | 2013-02-05 | Sap Ag | Software model process component |
US8448137B2 (en) | 2005-12-30 | 2013-05-21 | Sap Ag | Software model integration scenarios |
US8660904B2 (en) | 2005-12-30 | 2014-02-25 | Sap Ag | Architectural design for service request and order management application software |
US20080275713A9 (en) | 2005-12-30 | 2008-11-06 | Shai Alfandary | Architectural design for physical inventory application software |
US20070156550A1 (en) | 2005-12-30 | 2007-07-05 | Der Emde Martin V | Architectural design for cash and liquidity management application software |
US8522194B2 (en) | 2005-12-30 | 2013-08-27 | Sap Ag | Software modeling |
US8510183B2 (en) | 2005-12-30 | 2013-08-13 | Sap Ag | System and method for distributed and integrated asset management |
US8380553B2 (en) | 2005-12-30 | 2013-02-19 | Sap Ag | Architectural design for plan-driven procurement application software |
US8688495B2 (en) | 2005-12-30 | 2014-04-01 | Sap Ag | Architectural design for time recording application software |
US8326703B2 (en) * | 2005-12-30 | 2012-12-04 | Sap Ag | Architectural design for product catalog management application software |
US20070198391A1 (en) | 2006-02-21 | 2007-08-23 | Deutsche Boerse Ag | Method and system for conducting a block auction |
US20070220143A1 (en) | 2006-03-20 | 2007-09-20 | Postini, Inc. | Synchronous message management system |
US8538864B2 (en) | 2006-03-30 | 2013-09-17 | Sap Ag | Providing payment software application as enterprise services |
US20070233575A1 (en) | 2006-03-30 | 2007-10-04 | Arthur Berger | Architectural design for strategic sourcing application software |
US20070233539A1 (en) | 2006-03-30 | 2007-10-04 | Philipp Suenderhauf | Providing human capital management software application as enterprise services |
US8442850B2 (en) | 2006-03-30 | 2013-05-14 | Sap Ag | Providing accounting software application as enterprise services |
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 |
US8924269B2 (en) | 2006-05-13 | 2014-12-30 | Sap Ag | Consistent set of interfaces derived from a business object model |
US7917889B2 (en) * | 2006-06-19 | 2011-03-29 | International Business Machines Corporation | Data locations template based application-data association and its use for policy based management |
US7644390B2 (en) * | 2006-08-14 | 2010-01-05 | Payman Khodabandehloo | Design tool and methodology for enterprise software applications |
WO2008045941A1 (en) * | 2006-10-10 | 2008-04-17 | Estar, Inc. | A multi-tasked human resources and payroll accounting system |
US7624371B2 (en) | 2006-10-16 | 2009-11-24 | Invensys Systems, Inc. | Extensible automation development environment |
US8001519B2 (en) | 2007-06-27 | 2011-08-16 | International Business Machines Corporation | Model driven development including aspect integration tool |
US20090037287A1 (en) * | 2007-07-31 | 2009-02-05 | Ahmad Baitalmal | Software Marketplace and Distribution System |
US20090037492A1 (en) * | 2007-07-31 | 2009-02-05 | Ahmad Baitalmal | Framework for Synchronizing Applications |
US8014994B2 (en) * | 2007-08-31 | 2011-09-06 | Sap Ag | Simulation business object for service oriented architecture |
US8401936B2 (en) | 2007-12-31 | 2013-03-19 | Sap Ag | Architectural design for expense reimbursement application software |
US8671033B2 (en) | 2007-12-31 | 2014-03-11 | Sap Ag | Architectural design for personnel events application software |
US8447657B2 (en) | 2007-12-31 | 2013-05-21 | Sap Ag | Architectural design for service procurement application software |
US20090189743A1 (en) | 2008-01-24 | 2009-07-30 | Alcatel-Lucent | Radio-Frequency Identification Enabled Inventory Management and Network Operations System and Method |
US20090192858A1 (en) | 2008-01-28 | 2009-07-30 | Blake Johnson | Coordination And Management Of Operational Activities Subject to Uncertainty |
US20100070395A1 (en) * | 2008-09-18 | 2010-03-18 | Andreas Elkeles | Architectural design for payroll processing application software |
US8352338B2 (en) * | 2008-09-18 | 2013-01-08 | Sap Ag | Architectural design for time recording application software |
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 |
US8595077B2 (en) * | 2008-09-18 | 2013-11-26 | Sap Ag | Architectural design for service request and order management application software |
US8321306B2 (en) | 2008-12-03 | 2012-11-27 | Sap Ag | Architectural design for selling project-based services application software |
-
2006
- 2006-03-30 US US11/396,250 patent/US8396761B2/en active Active
-
2007
- 2007-03-29 WO PCT/EP2007/002842 patent/WO2007112956A2/en active Application Filing
Also Published As
Publication number | Publication date |
---|---|
US20070233581A1 (en) | 2007-10-04 |
US8396761B2 (en) | 2013-03-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8396761B2 (en) | Providing product catalog software application as enterprise services | |
US8326703B2 (en) | Architectural design for product catalog management application software | |
US8688495B2 (en) | Architectural design for time recording application software | |
US8326702B2 (en) | Providing supplier relationship management software application as enterprise services | |
US20080275713A9 (en) | Architectural design for physical inventory application software | |
US8402426B2 (en) | Architectural design for make to stock application software | |
US8538864B2 (en) | Providing payment software application as enterprise services | |
US8396749B2 (en) | Providing customer relationship management application as enterprise services | |
US8401928B2 (en) | Providing supplier relationship management software application as enterprise services | |
US20070233575A1 (en) | Architectural design for strategic sourcing application software | |
US8359218B2 (en) | Computer readable medium for implementing supply chain control using service-oriented methodology | |
US20100153158A1 (en) | Providing project management software application as enterprise services | |
US20100070555A1 (en) | Architectural design for time recording application software | |
US20140164572A1 (en) | Transport of customer flexibility changes in a multi-tenant environment | |
US8326706B2 (en) | Providing logistics execution application as enterprise services | |
US8321831B2 (en) | Architectural design for internal projects application software | |
US20090171811A1 (en) | Architectural Design For Product Catalog Management Application Software | |
US20090171758A1 (en) | Architectural design for physical inventory application software | |
US8671035B2 (en) | Providing payroll software application as enterprise services | |
US8311904B2 (en) | Architectural design for intra-company stock transfer application software | |
US20100070289A1 (en) | Architectural Design for Embedded Support Application Software | |
US10680983B2 (en) | Message payload editor | |
US20100070329A1 (en) | Architectural Design for Opportunity Management Application Software | |
US8510143B2 (en) | Architectural design for ad-hoc goods movement software | |
WO2007112955A1 (en) | Architectural design for personnel events application software |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07723784 Country of ref document: EP Kind code of ref document: A2 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 07723784 Country of ref document: EP Kind code of ref document: A2 |