Self-describing business objects

• US 7,533,103 B2
• Filed: 12/23/2003
• Issued: 05/12/2009
• Est. Priority Date: 07/22/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Remmel, Juergen, Brunswig, Frank, Dietl, Josef, Viegener, Johannes, Brendle, Rainer, Krane, Rolf, Ritter, Stephan
• Primary Examiner(s): Ali; Mohammad
• Assistant Examiner(s): Darno; Patrick A
• Application Number:
  US10/747,020
• Publication Number:
  US 20050021537A1
• Time in Patent Office: 1,967 Days
• Field of Search: 717/104, 705/7
• US Class Current: 1/1
• 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/10 Office automation; Time management
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching

Abstract

Methods and apparatus, including computer program products, that include representing, in a repository, services from a server, the services including interacting with one or more collections of data elements using a set of operations on the data elements in the collections, the repository comprising descriptions of the collections and common attributes for each collection, the repository organized according to a meta model. The method also includes enabling a software entity to request a service represented in the repository, the service representing a first operation on one or more data elements in a first collection from the collections, and executing the first operation on the one or more data elements in the first collection.

Claims

1. A method implemented as instructions for execution by a computer, the method comprising:

representing, in a repository, services from a server, the services comprising a first service for operating on a first collection of data elements and a second service for operating on a second collection of data elements, the repository comprising metadata describing attributes and operations available on the first collection and the second collection, the metadata organized according to a meta model that defines a syntax for requesting the services;

storing the first collection of data elements in a first format and the second collection of data elements in a second format, the first collection and second collection being stored separately from the repository, the second format being different than the first format;

receiving a first request from a software entity to request the first service represented in the repository, the first service representing a first operation on a data element in the first collection;

receiving a second request from the software entity to request the second service represented in the repository, the second service representing a second operation on a data element in the second collection; and

using a processor to execute the first service to perform the first operation on the data element in the first collection, the first operation comprising either reading the data element from the first collection, modifying the data element in the first collection, or locking the data element in the first collection to prevent the data element in the first collection from being read or modified; and

using a processor to execute the second service to perform the second operation on the data element in the second collection;

wherein the first request and the second request both conform with the syntax defined by the meta-model, the first service maps the first request to the first format, and the second service maps the second request to the second format.

2. The method of claim 1 wherein the repository further comprises descriptions of specialized actions available on a subset of the data elements in the first collection.

3. The method of claim 2 wherein a description of a specialized action comprises:

a name of the specialized action;

a name of a data structure for input data for the specialized action;

a name of the collection of data elements.

4. The method of claim 1 wherein the first service is implemented by a service provider class.

5. The method of claim 1, wherein the first service implements a select by relation command for finding, based on an identified data type, data elements in the first collection that have relations with the identified data type, the relations being defined in the repository.

6. The method of claim 5, wherein the select by relation command identifies data elements in the first collection that are related by a foreign key.

7. The method of claim 1 wherein the select by relation command enables the software entity to request the retrieval of data elements of the first collection that are related to a specified data element.

8. The method of claim 1 wherein the repository is a database, a first key for each data element identifies a row in a table, and the row contains a second key identifying a data dictionary entry for the data element.

9. The method of claim 1 wherein the first operation comprises reading the attributes of the first collection of data elements from memory storage and sending the attributes to the software entity.

10. The method of claim 9 wherein a first group of the one or more attributes are maintained in memory storage, and executing the first operation further comprises calculating an attribute from a second group of one or more attributes based on the values of one or more attributes in the first group, and sending the attribute from the second group to the software entity.

11. The method of claim 1 wherein a description of the first collection and common attributes for the first collection comprises:

a name of the first collection; and

a description of a data structure defining the attributes.

12. The method of claim 1 wherein the first operation is a query and executing the first operation further comprises searching for individual data elements within the first collection and returning keys representing the individual data elements.

13. The method of claim 12 wherein the repository comprises a definition of the query comprising:

a search parameter structure of the query; and

an input name defining a key that is used for filtering one or more data from the first collection.

14. A system comprising:

a first computer configured to execute a client program, the client program tangibly embodied on a computer readable storage medium;

a second computer configured to execute a server program, the server program tangibly embodied on a computer readable storage medium;

a network linking the first and second computers such that the server program is configured to execute the following;

represent, in a repository, services from the server program, the services comprising a first service for operating on a first collection of data elements and a second service for operating on a second collection of data elements, the repository comprising metadata describing attributes and operations available on the first collection and the second collection, the metadata organized according to a meta model that defines a syntax for requesting the services;

store the first collection of data elements in a first format and the second collection of data elements in a second format, the first collection and second collection being stored separately from the repository, the second format being different than the first format;

receive, from the client program, a first request to the first service represented in the repository, the first service representing a first operation on a data element in the first collection;

receive, from the client program, a second request to the second service represented in the repository, the second service representing a second operation on a data element in the second collection;

execute the first service to perform the first operation on the data element in the first collection, the first operation comprising either reading the data element from the first collection, modifying the data element in the first collection, or locking the data element in the first collection to prevent the data element in the first collection from being read or modified; and

execute the second service to perform the second operation on the data element in the second collection;

wherein the first request and the second request both conform with the syntax defined by the meta-model, the first service maps the first request to the first format, and the second service maps the second request to the second format.

15. The system of claim 14 wherein the repository further comprises descriptions of specialized actions available on a subset of the data elements in the first collection.

16. The system of claim 15 wherein a description of a specialized action comprises:

a name of the specialized action;

a name of a data structure for input data for the specialized action;

a name of the collection of data elements.

17. The system of claim 14 wherein the first service is implemented by a service provider class.

18. The system of claim 14 wherein first service is implemented by a service provider class.

19. The system of claim 14 wherein the first service implements a select by relation command for finding, based on an identified data type, data elements in the first collection that have relations with the identified data type, the relations being defined in the repository.

20. The system of claim 19 wherein the select by relation command enables the software entity to request the retrieval of data elements of the first collection that are related to a specified data element.

21. The system of claim 14 wherein the repository is a database, a first key for each data element identifies a row in a table, and the row contains a second key identifying a data dictionary entry for the data element.

22. The system of claim 14 wherein the first operation comprises reading the attributes of the first collection of data elements from memory storage and sending the attributes to the software entity.

23. The system of claim 22 wherein a first group of the one or more attributes are maintained in memory storage and executing the first operation further comprises calculating an attribute from a second group of one or more attributes based on the values of one or more attributes in the first group, and sending the attribute from the second group to the client program.

24. The system of claim 14 wherein a description of the first collection and common attributes for the first collection comprises:

a name of the first collection; and

a description of a data structure defining the attributes.

25. The system of claim 14 wherein the first operation is a query and executing the first operation further comprises searching for individual data elements within the first collection and returning keys representing the individual data elements.

26. The system of claim 25 wherein the repository comprises a definition of the query comprising:

a search parameter structure of the query; and

an input name defining a key that is used for filtering one or more data from the first collection.

27. A machine-readable storage medium comprising a method implemented as instructions for execution by a computer, the method comprising:

representing, in a repository, services from a server, the services comprising a first service for operating on a first collection of data elements and a second service for operating on a second collection of data elements, the repository comprising metadata describing attributes and operations available on the first collection and the second collection, the metadata organized according to a meta model that defines a syntax for requesting the services;

storing the first collection of data elements in a first format and the second collection of data elements in a second format, the first collection and second collection being stored separately from the repository, the second format being different than the first format;

receiving a first request from a software entity to request the first service represented in the repository, the first service representing a first operation on a data element in the first collection;

receiving a second request from the software entity to request the second service represented in the repository, the second service representing a second operation on a data element in the second collection;

executing the first service to perform the first operation on the data element in the first collection, the first operation comprising either reading the data element from the first collection, modifying the data element in the first collection, or locking the data element in the first collection to prevent the data element in the first collection from being read or modified; and

executing the second service to perform the second operation on the data element in the second collection;

wherein the first request and the second request both conform with the syntax defined by the meta-model, the first service maps the first request to the first format, and the second service maps the second request to the second format.