Consistent interface for inbound delivery request

• US 8,521,621 B1
• Filed: 06/28/2012
• Issued: 08/27/2013
• Est. Priority Date: 06/28/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Hetzer, Stephan, Krasinskiy, Alexander, Yaniv, Amit, Pronyakova, Zoya, Baruch, Amir
• Primary Examiner(s): Frenel, Vanel
• Application Number:
  US13/535,881
• Time in Patent Office: 425 Days
• Field of Search: 705/28, 705/304, 705/334, 705/8, 709/203
• US Class Current: 705/28
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/083 Shipping

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 an inbound delivery request business object.

Claims

1. A non-transitory computer readable medium including program code for providing a message-based interface for exchanging information about inbound delivery execution requests, 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 a warehouse provider to execute a receipt of goods, the first message including a first message package derived from the common business object model and the first message hierarchically organized in memory as;

an inbound delivery execution request message entity; and

an inbound delivery execution request package including an inbound delivery execution request entity, wherein the inbound delivery execution request entity includes an identifier, a type code and a sender last change date time, wherein the inbound delivery execution request entity further includes at least one item entity from an item package, and wherein each item entity includes an identifier, a type code, a cancelled indicator, a completed indicator, a product and a ship to location;

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 common business object model; 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.

2. The computer readable medium of claim 1, wherein the inbound delivery execution request entity further includes at least one of the following:

a buyer party, a seller party, an employee responsible party, a text collection, and an attachment folder.

3. The computer readable medium of claim 1, wherein each item entity further includes at least one schedule line entity from a schedule line package.

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

a graphical user interface comprising computer readable instructions, embedded on tangible media, for a request to a warehouse provider to execute a receipt of goods, the instructions using a request;

a first memory storing a user interface controller 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 as;

an inbound delivery execution request message entity; and

an inbound delivery execution request package including an inbound delivery execution request entity, wherein the inbound delivery execution request entity includes an identifier, a type code and a sender last change date time, wherein the inbound delivery execution request entity further includes at least one item entity from an item package, and wherein each item entity includes an identifier, a type code, a cancelled indicator, a completed indicator, a product and a ship to location; and

a second memory, remote from the graphical user interface, storing a plurality of service interfaces, wherein one of the service interfaces is operable to process the message via the service interface, where processing the message includes unpacking the first message package based on the common business object model.

5. The distributed system of claim 4, wherein the first memory is remote from the graphical user interface.

6. The distributed system of claim 4, wherein the first memory is remote from the second memory.