Consistent interface for product valuation data and product valuation level

• US 8,756,135 B2
• Filed: 06/28/2012
• Issued: 06/17/2014
• Est. Priority Date: 06/28/2012
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Klein, Markus, Barheine, Wolfgang, Bedke, Johannes, Dinkel, Ralf, Richert, Jan, Ringl, Benjamin, Weber, Sascha, Zhang, Guimei
• Primary Examiner(s): Hammond, III, Thomas M
• Application Number:
  US13/535,419
• Publication Number:
  US 20140006238A1
• Time in Patent Office: 719 Days
• Field of Search: 705 35- 45
• US Class Current: 705/35
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management

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 product valuation data and a product valuation level business object.

Claims

1. A non-transitory computer readable medium storing instructions executable by at least one processor to perform operations, where the instructions provide a message-based interface for exchanging information about material valuation data, the operations comprising:

receiving, at first application, 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 second application different from the first application, the second application executing in an environment of computer systems providing message-based services, a first message for requesting maintenance of a bundle of material valuation data, the first message including a first message package hierarchically organized in memory, the first message package including;

at a first hierarchical level in the first message package, a material valuation data bundle maintain request sync message entity; and

at the first hierarchical level in the first message package, a material valuation data bundle maintain request sync package including, at a second hierarchical level in the first message package, a material valuation data bundle maintain request sync entity, wherein the material valuation data bundle maintain request sync entity includes, at a third hierarchical level in the first message package, at least one material valuation data entity from a material valuation data package;

processing the first message based on 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

sending a second message to the second application responsive to the first message, where the second message includes a second message package derived from the common business object model to correspond to the semantics of the first message package.

2. The computer readable medium of claim 1, wherein the material valuation data bundle maintain request sync entity includes, at the third hierarchical level in the first message package, at least one valuation price entity from a valuation price package.

3. The computer readable medium of claim 1, wherein the material valuation data bundle maintain request sync entity further includes, at the third hierarchical level in the first message package, at least one of the following:

an object node sender technical identifier (ID), a change state ID, a material internal ID, a material universally unique identifier (UUID), a company ID, and a company UUID.

4. 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 maintenance of a bundle of material valuation data, 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, the hierarchical organization of the first message package including;

at a first hierarchical level in the first message package, a material valuation data bundle maintain request sync message entity; and

at the first hierarchical level in the first message package, a material valuation data bundle maintain request sync package including, at a second hierarchical level in the first message package, a material valuation data bundle maintain request sync entity, wherein the material valuation data bundle maintain request sync entity includes, at a third hierarchical level in the first message package, at least one material valuation data entity from a material valuation data package; 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 correspond to the semantics of messages derived from the common business object model, where one of the service interfaces is operable to process the message via the service interface based on 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.

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.