Consistent interface for service product

A distributed system operating in a landscape of computer systems providing message-based services defined in a service registry, the system comprising:

• at least one processor operable to execute computer readable instructions embodied on non-transitory media;
• a graphical user interface executable by the at least one processor and comprising computer readable instructions, embedded on non-transitory media, for requesting to maintain a bundle of service products, each service product being an intangible product that describes the provision of a service, the service being provided at a time that the service is used, the instructions using a request;
• a first memory storing a user interface controller executable by the at least one processor for processing the request and involving a message including a first message package derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based service interfaces and message packages, the first message package hierarchically organized based on the common business object model, the hierarchical organization of the first message package including:
• a service product bundle maintain request sync message entity;
• and
• a service product package including at least one service product entity description package, a detail package, a quantity conversion package, a purchasing package, a sales package, a customer information package, and a supplier information package, wherein the description package includes at least one description entity, wherein the detail package includes at least one detail entity, wherein the quantity conversion package includes at least one quantity conversion entity, wherein the purchasing package includes a purchasing entity, and wherein the sales package includes at least one sales entity, wherein the customer information package includes at least one customer information entity, and wherein the supplier information package includes at least one supplier information entity;
• and
• a second memory, remote from the graphical user interface, storing a plurality of service interfaces executable by the at least one processor and derived from the common business object model to provide consistent semantics with messages derived from the common business object model, wherein one of the service interfaces is operable to process the message via the service interface according to the hierarchical organization of the first message package, where processing the message includes unpacking the first message package based on the first message package's structure and the first message package's derivation from the common business object model, wherein the particular structure of the first message package is used at least in part to identify the purpose of the message.

A non-transitory computer readable medium including program code for providing a message-based interface for exchanging information about service products, the medium comprising:

• program code for receiving via a message-based interface derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based interfaces and message packages, the message-based interface exposing at least one service as defined in a service registry and from a heterogeneous application executing in an environment of computer systems providing message-based services, a first message for requesting to check whether maintaining a bundle of service products is possible, each service product being an intangible product that describes the provision of a service, the service being provided at a time that the service is used, the first message including a first message package derived from the common business object model, the first message package hierarchically organized in memory based on the common business object model, the first message package including:
• a service product bundle maintenance check request sync message entity;
• and
• a service product package including at least one service product entity, a description package, a detail package, a quantity conversion package, a purchasing package, a sales package, a customer information package, and a supplier information package, wherein the description package includes at least one description entity wherein the detail package includes at least one detail entity, wherein the quantity conversion package includes at least one quantity conversion entity, wherein the purchasing package includes a purchasing entity, and wherein the sales package includes at least one sales entity, wherein the customer information package includes at least one customer information entity, and wherein the supplier information package includes at least one supplier information entity;
• program code for processing the first message according to the hierarchical organization of the first message package, where processing the first message includes unpacking the first message package based on the first message package's structure and the first message package's derivation from the common business object model, wherein the particular structure of the first message package is used at least in part to identify the purpose of the first message;
• and
• program code for sending a second message to the heterogeneous application responsive to the first message, where the second message includes a second message package derived from the common business object model to provide consistent semantics with the first message package.

A distributed system operating in a landscape of computer systems providing message-based services defined in a service registry, the system comprising:

• at least one processor operable to execute computer readable instructions embodied on non-transitory media;
• a graphical user interface executable by the at least one processor and comprising computer readable instructions, embedded on non-transitory media, for requesting to check whether maintaining a bundle of service products is possible, each service product being an intangible product that describes the provision of a service, the service being provided at a time that the service is used, the instructions using a request;
• a first memory storing a user interface controller executable by the at least one processor for processing the request and involving a message including a first message package derived from a common business object model, where the common business object model includes business objects having relationships that enable derivation of message-based service interfaces and message packages, the first message package hierarchically organized based on the common business object model, the hierarchical organization of the first message package including:
• a service product bundle maintenance check request sync message entity;
• and
• a service product package including at least one service product entity description package, a detail package, a quantity conversion package, a purchasing package, a sales package, a customer information package, and a supplier information package, wherein the description package includes at least one description entity, wherein the detail package includes at least one detail entity, wherein the quantity conversion package includes at least one quantity conversion entity, wherein the purchasing package includes a purchasing entity, and wherein the sales package includes at least one sales entity, wherein the customer information package includes at least one customer information entity, and wherein the supplier information package includes at least one supplier information entity;
• and
• a second memory, remote from the graphical user interface, storing a plurality of service interfaces executable by the at least one processor and derived from the common business object model to provide consistent semantics with messages derived from the common business object model, wherein one of the service interfaces is operable to process the message via the service interface according to the hierarchical organization of the first message package, where processing the message includes unpacking the first message package based on the first message package's structure and the first message package's derivation from the common business object model, wherein the particular structure of the first message package is used at least in part to identify the purpose of the message.