Managing consistent interfaces for maintenance order business objects across heterogeneous systems

• US 8,413,165 B2
• Filed: 03/31/2008
• Issued: 04/02/2013
• Est. Priority Date: 03/31/2008
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Lindemann, Thiemo, Singh, Abhinava Pratap
• Primary Examiner(s): Truong, Lechi
• Application Number:
  US12/060,155
• Publication Number:
  US 20090249362A1
• Time in Patent Office: 1,828 Days
• Field of Search: 719/310, 719/313, 717/100, 717/106
• US Class Current: 719/313
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

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 maintenance order business object.

Claims

1. A computer readable storage medium including program code for providing a message-based interface for performing a maintenance order service, the service exposing at least one service as defined in a service registry, wherein upon execution the program code executes in an environment of computer systems providing message-based services and comprises:

program code for receiving, from a service consumer, a first message for providing the interfaces that include the service operations used for communication between client and maintenance order applications;

program code for invoking a maintenance order business object, wherein the maintenance order business object is a logically centralized, semantically disjointed object for describing work to be done in a maintenance work order cycle, and comprises data logically organized as;

a maintenance order root node;

a cost settlement rule subordinate node;

a party subordinate node; and

an operation subordinate node; and

program code for initiating transmission of a message to a heterogeneous second application, executing in the environment of computer systems providing message-based services, based on the data in the maintenance order business object, the message comprising a maintenance order message entity, a message header package, a maintenance order package, and a log package.

2. A computer readable storage medium including program code for providing a message-based interface for performing a maintenance order service, the service exposing at least one service as defined in a service registry, wherein upon execution the program code executes in an environment of computer systems providing message-based services and comprises:

program code for initiating transmission of a first message to a heterogeneous second application, executing in the environment of computer systems providing message-based services, based on data in a maintenance order business object invoked by the second application, wherein the maintenance order business object is a logically centralized, semantically disjointed object for describing the work to be done in a maintenance work order cycle and comprises data logically organized as;

a maintenance order root node;

a cost settlement rule subordinate node;

a party subordinate node; and

an operation subordinate node;

and the first message comprising a maintenance order message entity, a message header package, a maintenance order package, and a log package; and

program code for receiving a second message from the second application, the second message associated with the invoked maintenance order business object and in response to the first message.

3. A computer readable storage medium including program code for providing a message-based interface for performing a maintenance order service, 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 sent from a service consumer to an enterprise asset management system for requesting creation of a new maintenance order, where the maintenance order is a requirement to execute a maintenance task on a technical object for a specific deadline, the first message including a first message package derived from the common business object model and hierarchically organized as;

a maintenance order create request message entity; and

a message header package and a maintenance order package, where the message header package includes a message header entity, where the message header entity includes an ID and a creation date time, and where the maintenance order package includes a maintenance order entity, where the maintenance order entity includes a type code; and

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;

wherein the maintenance order package includes one or more of the following;

an operation package, one or more party packages, and one or more cost settlement rule packages.

4. The medium of claim 3, wherein the maintenance order entity further includes one or more of the following:

a maintenance planning plant ID, an accounting business area code, a work centre ID, a work centre plant ID, a maintenance planner group code, an installation point ID, an individual material ID, a material ID, a serial ID, an importance code, a description, a text collection, a maintenance request ID, a requested execution period, and an estimated total amount.

5. 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 requesting creation of a new maintenance order, where the maintenance order is a requirement to execute a maintenance task on a technical object for a specific deadline, 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;

a maintenance order create request message entity; and

a message header package and a maintenance order package, where the message header package includes a message header entity, where the message header entity includes an ID and a creation date time, and where the maintenance order package includes a maintenance order entity, where the maintenance order entity includes a type code; and

; and

a second memory, remote from the graphical user interface, storing a plurality of message-based service interfaces derived from the common business object model to provide consistent semantics with messages derived from the common business object model, where one of the message-based 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 common business object model;

wherein the first memory is remote from the graphical user interface.

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