IP Library Granted Patent US 9,038,021
Granted Patent B2
US 9,038,021 · App. 13/586,189 · Granted May 19, 2015

Naming algorithm for extension fields in de-normalized views

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,038,021
App. No.
13/586,189
Granted
May 19, 2015
Kind
B2
Abstract

An extension naming approach for avoiding naming collisions in de-normalized view on a business object can include accessing a reference field bundle, which includes reference field(s) corresponding to a core business object defined in a core software platform of a software architecture, from a metadata repository. A user can define an extension to the business object based on the core business object, for example via a development environment. The reference field(s) can include a defined path from a node in a peripheral object to a corresponding node in the core business object. A unique and reproducible name for the extension field can be generated based on the reference field, and the extension field with the unique and reproducible name can be added to the business object and to a data model of the peripheral object.

Claims (33)

1. A computer program product comprising a non-transitory machine-readable medium storing instructions that, when executed by at least one programmable processor, cause the at least one programmable processor to perform operations comprising:

receiving, via a development environment supporting extensions to a business object model of a software architecture, a definition of an extension field to a business object;

accessing a reference field bundle from a metadata repository, the reference field bundle comprising at least one reference field corresponding to a core business object defined in a core software platform of the software architecture, the business object being based on the core business object, the at least one reference field comprising a defined path from a node in a peripheral object to a corresponding node in the core business object;

generating a unique and reproducible name for the extension field based on the reference field; and

adding the extension field with the unique and reproducible name to the business object and to a data model of the peripheral object.

2. A computer program product as in claim 1 , wherein the generating comprises appending a suffix to an extension field name of the extension field in the business object, the extension field name being provided by a user in the development environment.

3. A computer program product as in claim 2 , wherein the suffix comprises a hash value.

4. A computer program product as in claim 3 , wherein operations performed by the processor further comprise calculating the hash value based on a name of the business object, a name of a business object node in the business object to which the extension field is added, and a role of a node instance of the business object node.

5. A computer program product as in claim 1 , wherein the peripheral object represents a de-normalized view of the business object.

6. A computer program product as in claim 1 , wherein the development environment conceals the unique and reproducible name from a user.

7. A system comprising:

at least one programmable processor; and

a machine-readable medium storing instructions that, when executed by the at least one programmable processor, cause the at least one programmable processor to perform operations comprising:

receiving, via a development environment supporting extensions to a business object model of a software architecture, a definition of an extension field to a business object;

accessing a reference field bundle from a metadata repository, the reference field bundle comprising at least one reference field corresponding to a core business object defined in a core software platform of the software architecture, the business object being based on the core business object, the at least one reference field comprising a defined path from a node in a peripheral object to a corresponding node in the core business object;

generating a unique and reproducible name for the extension field based on the reference field; and

adding the extension field with the unique and reproducible name to the business object and to a data model of the peripheral object.

8. A system as in claim 7 , wherein the generating comprises appending a suffix to an extension field name of the extension field in the business object, the extension field name being provided by a user in the development environment.

9. A system as in claim 8 , wherein the suffix comprises a hash value.

10. A system as in claim 9 , wherein the operations further comprise calculating the hash value based on a name of the business object, a name of a business object node in the business object to which the extension field is added, and a role of a node instance of the business object node.

11. A system as in claim 7 , wherein the peripheral object represents a de-normalized view of the business object.

12. A system as in claim 7 , wherein the development environment conceals the unique and reproducible name from a user.

13. A computer-implemented method comprising:

receiving, via a development environment supporting extensions to a business object model of a software architecture, a definition of an extension field to a business object;

accessing a reference field bundle from a metadata repository, the reference field bundle comprising at least one reference field corresponding to a core business object defined in a core software platform of the software architecture, the business object being based on the core business object, the at least one reference field comprising a defined path from a node in a peripheral object to a corresponding node in the core business object;

generating a unique and reproducible name for the extension field based on the reference field; and

adding the extension field with the unique and reproducible name to the business object and to a data model of the peripheral object.

14. A computer-implemented method as in claim 13 , wherein the generating comprises appending a suffix to an extension field name of the extension field in the business object, the extension field name being provided by a user in the development environment.

15. A computer-implemented method as in claim 14 , wherein the suffix comprises a hash value.

16. A computer-implemented method as in claim 15 , wherein operations performed by a processor further comprise calculating the hash value based on a name of the business object, a name of a business object node in the business object to which the extension field is added, and a role of a node instance of the business object node.

17. A computer-implemented method as in claim 13 , wherein the peripheral object represents a de-normalized view of the business object.

18. A computer-implemented method as in claim 13 , wherein the development environment conceals the unique and reproducible name from a user.

19. A computer-implemented method as in claim 13 , wherein at least one of the receiving, the accessing, the generating, and the adding is performed by a system comprising at least one programmable processor.

Assignments (2)
CHANGE OF NAME Recorded Aug 26, 2014
From: SAP AG
To: SAP SE
Reel/Frame 033625/0223 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 15, 2012
From: SCHLARB, UWE; DEHN, RENE; FIGUS, DANIEL; NIEHOFF, DANIEL; BAEUERLE, STEFAN; WILHELM, GEORG
To: SAP AG
Reel/Frame 028790/0831 →