MANAGING EXTENSION PROJECTS WITH REPOSITORY BASED TAGGING

• US 20120023445A1
• Filed: 07/26/2010
• Published: 01/26/2012
• Est. Priority Date: 07/26/2010
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Baeuerle, Stefan A., Schlarb, Uwe, Thimmel, Bernhard, Jentsch, Frank, Fanghänel, Karsten, Specht, Jurgen, Lebr, Matthias, Rauer, Klaus
• Granted Patent: US 9,021,392 B2
• Time in Patent Office: Days
• US Class Current: 715/810
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 8/36 Software reuse
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

According to some embodiments, information about a delta change package may be received. The delta change package may be, for example, associated with a customer extension project to be applied to content from a business service provider. A description tag for the delta change package may be received from a user, and the delta change package may be associated with the description tag in a repository of the business service provider.

Claims

1. A computer implemented method, comprising:

receiving information about a delta change package associated with a customer extension project to be applied to content from a business service provider;

receiving, from a user, a description tag for the delta change package; and

associating the delta change package with the description tag in a repository of an execution platform of the business service provider.

2. The method of claim 1, wherein information about the delta change package is stored in a project maintenance table, associated with the repository, along with the description tag.

3. The method of claim 2, wherein the project maintenance table further stores at least one of:

(i) an entity type, (ii) an extended entity identifier, (iii) an adaptation description, (iv) a user identifier, (v) a save date and time, (vi) an extension project identifier, (vii) a version identifier, or (viii) a publication date and time.

4. The method of claim 2, wherein information from the project maintenance table is displayed the user via a user interface.

5. The method of claim 4, wherein the displayed information is grouped according to description tags.

6. The method of claim 4, wherein the user interface is selectable to provide a drill down view associated with a business object.

7. The method of claim 1, wherein multiple delta change packages are associated with the description tag.

8. The method of claim 1, wherein multiple description tags are associated with the delta change package.

9. The method of claim 1, wherein multiple delta change packages are associated with the customer extension project, each multiple delta change package sharing the description tag.

10. The method of claim 1, wherein log messages store information linking the description tag to the delta change package.

11. The method of claim 1, further comprising:

performing a compliance check for the delta change package based at least in part on the description tag associated with the delta change package.

12. The method of claim 1, further comprising:

executing the delta change package in a staging layer; and

publishing the delta change package from the staging layer to a company wide layer.

13. A computer-readable medium storing program code executable by a computer to:

receiving information about a delta change package associated with a customer extension project to be applied to content from a business service provider;

receiving, from a user, a description tag for the delta change package; and

associating the delta change package with the description tag in a repository of an execution platform of the business service provider.

14. The medium of claim 13, wherein information about the delta change package is stored in a project maintenance table, associated with the repository, along with the description tag.

15. The medium of claim 14, wherein the project maintenance table further stores at least one of:

(i) an entity type, (ii) an extended entity identifier, (iii) an adaptation description, (iv) a user identifier, (v) a save date and time, (vi) an extension project identifier, (vii) a version identifier, or (viii) a publication date and time.

16. The medium of claim 14, wherein information from the project maintenance table is displayed the user via a user interface grouped according to description tags.

17. A business service provider execution platform, comprising:

a communication port to receive;

(1) information about a delta change package associated with a customer extension project to be applied to content from a business service provider, and (2) a description tag for the delta change package;

a repository to store an association between the delta change package and the description tag in a repository of an execution platform of the business service provider; and

an engine to apply the delta change package to the content from the business service provider.

18. The business service provider execution platform of claim 17, further comprising:

runtime buffers supporting enhancements associated with the delta change package, and

runtime entities supporting structures and classes associated with the delta change package.

19. The business service provider execution platform of claim 17, further comprising:

a display engine to display project maintenance table data, including the description tag, to a user, wherein the displayed data further includes at least one of;

(i) an entity type, (ii) an extended entity identifier, (iii) an adaptation description, (iv) a user identifier, (v) a save date and time, (vi) an extension project identifier, (vii) a version identifier, or (viii) a publication date and time.

20. The business service provider execution platform of claim 19, wherein information from the project maintenance table is displayed to the user via a user interface and is selectable to sort table entries according to description tags.