Consistent interface for sales territory message type set 1

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

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Hanumolu, Usha, He, Yingjiong, Nagapandi, Sivakumar, Pachineelam, Manikanta, Zhou, Yufeng
• Primary Examiner(s): ALGIBHAH, HAMZA N
• Application Number:
  US13/398,191
• Publication Number:
  US 20130218944A1
• Time in Patent Office: 852 Days
• Field of Search: 709/203
• US Class Current: 709/203
• CPC Class Codes: G06Q 10/067 Enterprise or organisation modelling

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 sales territory business object.

Claims

1. A non-transitory computer readable medium including program code for providing a message-based interface for exchanging information about relations between sales territories and accounts, 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 maintenance of one or more relations between sales territories and accounts, the first message including a first message package hierarchically organized in memory based on and derived from the common business object model, the first message package including;

at a first hierarchical level in the first message package, a sales territory account bundle check maintain request message entity;

at the first hierarchical level in the first message package, a message header package including, at a second hierarchical level in the first message package, a basic message header entity; and

at the first hierarchical level in the first message package, a sales territory package including, at the second hierarchical level in the first message package, a sales territory account maintain request bundle entity, where the sales territory account maintain request bundle entity includes, at a third hierarchical level in the first message package, a sales territory identifier (ID);

program code for 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 hierarchical organization of the first message package and the first message package'"'"'s deriviation from the common business object model, wherein the particular hierarchical organization 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.

2. The computer readable medium of claim 1, wherein the sales territory account maintain request bundle entity includes, in the third hierarchical level in the first message package, at least one account request bundle entity.

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

an object node sender technical ID and a change state ID.

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 tangible, non-transitory media, for requesting maintenance of one or more relations between sales territories and accounts 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 and derived from the common business object model, the hierarchical organization of the message package including;

at a first hierarchical level in the first message package, a sales territory account bundle check maintain request message entity;

at the first hierarchical level in the first message package, a message header package including, at a second hierarchical level in the first message package, a basic message header entity; and

at the first hierarchical level in the first message package, a sales territory package including, at the second hierarchical level in the first message package, a sales territory account maintain request bundle entity, where the sales territory account maintain request bundle entity includes, at a third hierarchical level in the first message package, a sales territory identifier (ID); 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 message-based service interfaces is operable to process the message based on the hierarchical organization of the first message package, where processing the message includes unpacking the first message package based on the hierarchical organization of the first message package and the first 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. 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.

7. A non-transitory computer readable medium including program code for providing a message-based interface for exchanging information about relations between sales territories and accounts, 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 maintenance of one or more relations between sales territories and accounts, the first message including a first message package hierarchically organized in memory based on and derived from the common business object model, the first message package including;

at a first hierarchical level in the first message package, a sales territory account bundle maintain request message entity;

at the first hierarchical level in the first message package, a message header package including, at a second hierarchical level in the first message package, a basic message header entity; and

at the first hierarchical level in the first message package, a sales territory package including, at the second hierarchical level in the first message package, a sales territory account maintain request bundle entity, where the sales territory account maintain request bundle entity includes, at a third hierarchical level in the first message package, a sales territory identifier (ID);

program code for 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 hierarchical organization of the first message package and the first message package'"'"'s deriviation from the common business object model, wherein the particular hierarchical organization 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.

8. The computer readable medium of claim 7, wherein the sales territory account maintain request bundle entity includes, at the third hierarchical level in the first message package, at least one account request bundle entity.

9. The computer readable medium of claim 7, wherein the sales territory account maintain request bundle entity further includes, at the third hierarchical level in the first message package, at least one of the following:

an object node sender technical ID and a change state ID.

10. 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 tangible, non-transitory media, for requesting maintenance of one or more relations between sales territories and accounts 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 and derived from the common business object model, the hierarchical organization of the message package including;

at a first hierarchical level in the first message package, a sales territory account bundle maintain request message entity;

at the first hierarchical level in the first message package, a message header package including, at a second hierarchical level in the first message package, a basic message header entity; and

at the first hierarchical level in the first message package, a sales territory package including, at the second hierarchical level in the first message package, a sales territory account maintain request bundle entity, where the sales territory account maintain request bundle entity includes, at a third hierarchical level in the first message package, a sales territory identifier (ID); 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 message-based service interfaces is operable to process the message based on the hierarchical organization of the first message package, where processing the message includes unpacking the first message package based on the hierarchical organization of the first message package and the first 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.

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

12. The distributed system of claim 10, wherein the first memory is remote from the second memory.