Back to results
US 2014/0006305 A1Published application
Consistent Interface for Confirmed Inbound Delivery
AssigneeSap SE
InventorsStephan Hetzer, Amit Yaniv, Zoya Pronyakova, Alexander Krasinskiy
Life of this patent
Estimating the term…
Abstract
A business object model, which reflects data that is used during a given business transaction, is utilized to generate interfaces. This business object model facilitates commercial transactions by providing consistent interfaces that are suitable for use across industries, across businesses, and across different departments within a business during a business transaction. In some operations, software creates, updates, or otherwise processes information related to a confirmed inbound delivery business object.
Claims6
A computer readable medium including program code for providing a message-based interface for exchanging information about confirmation of goods received, 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 providing a confirmation by a warehouse provider of goods received, 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:
- an inbound delivery execution confirmation message entity;
- and
- an inbound delivery execution package including an inbound delivery execution entity, a party package, an arrival period package, and an item package, wherein the inbound delivery execution entity includes an identifier (ID), a vendor ID, a type code, and a sender last change date time, wherein the party package includes a vendor party entity and a product recipient party entity, wherein the arrival period package includes an arrival date time period entity, wherein the item package includes at least one item entity and a product information package, wherein each item entity includes an item entity ID, an item entity vendor ID, an item entity delivery quantity, and an item entity delivery quantity type code, and wherein the product information package includes a product 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.
4 more elements
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 providing a confirmation by a warehouse provider of goods received, 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 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 message package hierarchically organized based on the common business object model, the hierarchical organization of the message package including:
- an inbound delivery execution confirmation message entity;
- and
- an inbound delivery execution package including an inbound delivery execution entity, a party package, an arrival period package, and an item package, wherein the inbound delivery execution entity includes an identifier (ID), a vendor ID, a type code, and a sender last change date time, wherein the party package includes a vendor party entity and a product recipient party entity, wherein the arrival period package includes an arrival date time period entity, wherein the item package includes at least one item entity and a product information package, wherein each item entity includes an item entity ID, an item entity vendor ID, an item entity delivery quantity, and an item entity delivery quantity type code, and wherein the product information package includes a product 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 message package, where processing the message includes unpacking the first message package based on the message package's structure and the message package's derivation from the common business object model, wherein the particular structure of the message package is used at least in part to identify the purpose of the message.
5 more elements
Dependencies are inferred from the claim text.