Managing extension projects with repository based tagging

• US 9,021,392 B2
• Filed: 07/26/2010
• Issued: 04/28/2015
• 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, Specht, Jurgen, Fanghnel, Karsten, Lebr, Matthias, Rauer, Klaus, Jentsch, Frank
• Primary Examiner(s): Bycer, Eric J
• Application Number:
  US12/843,180
• Publication Number:
  US 20120023445A1
• Time in Patent Office: 1,737 Days
• Field of Search: 707/803, 707/E17.044, 715/810
• 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 first description tag for the delta change package and a second description tag for the delta change package, the first description tag associated with a first particular customer extension project and the second description tag associated with a second particular customer extension project;

associating the delta change package with the first description tag and the second description tag in a same repository of an execution platform of the business service provider, the repository comprising (i) the first description tag with a link to the delta change package and (ii) the second description tag with the link to the delta change package;

determining, via a computer, a list of delta change packages belonging to the first particular customer extension project by grouping delta change packages based on the first description tag; and

assembling, via the computer, the first customer extension project based on first description tag where assembly comprises evaluating (i) whether all required artifacts associated with the first customer extension project are included and (ii) whether the grouping of delta change packages was based on the first description tag or the second description tag.

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 first description tag and the second 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 to the user via a user interface.

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

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

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

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

9. 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.

10. A non-transitory, tangible computer-readable medium storing program code executable by a computer to:

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

receive, from a user, a first description tag for the delta change package and a second description tag for the delta change package, the first description tag associated with a first particular customer extension project and the second description tag associated with a second particular customer extension project;

associate the delta change package with the first description tag and the second description tag in a same repository of an execution platform of the business service provider, the repository comprising (i) the first description tag with a link to the delta change package and (ii) the second description tag with the link to the delta change package;

determine, via a computer, a list of delta change packages belonging to the first particular customer extension project by grouping delta change packages based on the first description tag; and

assemble, via the computer, the first customer extension project based on first description tag where assembly comprises evaluating (i) whether all required artifacts associated with the first customer extension project are included and (ii) whether the grouping of delta change packages was based on the first description tag or the second description tag.

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

12. The medium of claim 11, 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.

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

14. A business service provider execution platform, comprising:

a hardware communication port to receive;

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

a repository to store associations between the delta change package and the first and second description tags in a same repository of an execution platform of the business service provider, the repository comprising (i) the first description tag with a link to the delta change package and (ii) the second description tag with the link to the delta change package;

and

an engine to apply the delta change package to the content from the business service provider and to determine a list of delta change packages belonging to the first customer extension project by grouping delta change packages based on first description tag and to assemble the first customer extension project based on the first description tag where assembly comprises evaluating (i) whether all required artifacts associated with the first customer extension project are included and (ii) whether the grouping of delta change packages was based on the first description tag or the second description tag.

15. The business service provider execution platform of claim 14, 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.

16. The business service provider execution platform of claim 14, 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.

17. The business service provider execution platform of claim 16, 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.