Meta-date driven implementation of business objects and their transactional behavior

• US 8,001,521 B2
• Filed: 06/12/2006
• Issued: 08/16/2011
• Est. Priority Date: 06/12/2006
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Koch, Wolfgang M., Tiple, Abhay A., Aakolk, Michael
• Primary Examiner(s): DAS, CHAMELI
• Application Number:
  US11/450,261
• Publication Number:
  US 20070288891A1
• Time in Patent Office: 1,891 Days
• Field of Search: 717/101, 717/102, 717/106, 717/108, 717/116
• US Class Current: 717/106
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Systems, methods and computer readable media are provided for the creation of a business object. In one exemplary embodiment, the method may include defining the shell of a business object utilizing meta-data stored within a repository. The method may also include storing the defined business object shell within the repository. Moreover, the method may include generating a business object template utilizing the business object shell, meta-data, and hooks for calling generic business logic, and modifying the hooks to insert the generic business logic.

Claims

1. A method of creating a business object:

defining the shell of a business object utilizing meta-data stored within a repository;

storing the defined business object shell within the repository;

generating a business object template utilizing the business object shell and meta-data, wherein the business object template is preconfigured with one or more hooks to generic business logic placed in at least one location within buffer logic of the business object for calling one or more business functions usable by the business object and at least one other business object; and

modifying the one or more hooks to insert the generic business logic,

wherein the one or more hooks define one or more breakpoints in the buffer logic where the generic business logic may be inserted.

2. The method of claim 1, wherein the generic business logic is created by a service provider.

3. The method of claim 1, wherein the buffer logic for manages access of the business object to a database and a state handling of the business object during a transaction.

4. The method of claim 1, wherein the generic business logic is capable of checking transactional data of the business object and at least one other business object for consistency.

5. The method of claim 4, wherein the generic business logic is capable of enriching the transactional data by adding additional information to the transactional data.

6. The method of claim 1, wherein the generic business logic is capable of handling complex actions involving creating, reading, updating and/or deleting transactional data from a database.

7. The method of claim 1, wherein the generic business logic is capable of handling event handlers used for cross business object transactions.

8. A non-transitory computer-readable storage medium storing instructions to configure a processor to perform a method of creating a business object, the method comprising:

defining the shell of a business object utilizing meta-data stored within a repository;

storing the defined business object shell within the repository;

generating a business object template utilizing the business object shell, and meta-data, wherein the business object template is preconfigured with one or more hooks to generic business logic placed in at least one location within buffer logic of the business object for calling one or more business functions usable by the business object and at least one other business object; and

modifying the one or more hooks to insert the generic business logic,

wherein the one or more hooks define one or more breakpoints in the buffer logic where the generic business logic maybe inserted.

9. The non-transitory computer-readable storage medium of claim 8, wherein the generic business logic is created by a service provider.

10. The non-transitory computer-readable storage medium of claim 8, wherein the business logic manages access of the business object to a database and a state handling of the business object during a transaction.

11. The non-transitory computer-readable storage medium of claim 8, wherein the generic business logic is capable of checking transactional data of the business object and at least one other business object for consistency.

12. The non-transitory computer-readable storage medium of claim 11, wherein the generic business logic is capable of enriching the transactional data by adding additional information to the transactional data.

13. The non-transitory computer-readable storage medium of claim 8, wherein the generic business logic is capable of handling complex actions involving creating, reading, updating and/or deleting transaction data from the database.

14. The non-transitory computer-readable storage medium of claim 8, wherein the generic business logic is capable of handling event handlers used for cross business object transactions. database.

15. A system for creating a business object, comprising:

a processor; and

a memory, wherein the processor and the memory are configured to perform a method comprising;

defining a shell of a business object utilizing meta-data stored within a repository;

storing the defined business object shell within the repository;

generating a business object template utilizing the business object shell and meta-data, wherein the business object template is preconfigured with one or more hooks to generic business logic placed in at least one location within buffer logic of the business obiect for calling one or more business functions usable by the business object and at least one other business object; and

modifying the one or more hooks to insert the generic business logic,

wherein the one or more hooks define one or more breakpoints in the buffer logic where the generic business logic may be inserted.

16. The system of claim 15, wherein the generic business logic is created by a service provider.

17. The system of claim 15, wherein the buffer logic manages access of the business object to a database and a state handling of the business object during a transaction.

18. The system of claim 15, wherein the generic business logic is capable of checking transactional data of the plurality of business object and at least one other business obiect for consistency.

19. The system of claim 18, wherein the generic business logic is capable of enriching the transactional data by adding additional information to the transactional data.

20. The system of claim 15, wherein the generic business logic is capable of handling complex actions involving creating, reading, updating and/or deleting transaction data from a database.