BUSINESS OBJECT MODEL LAYER INTERFACE

• US 20150160928A1
• Filed: 06/12/2014
• Published: 06/11/2015
• Est. Priority Date: 12/05/2013
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Hermanns, Marcel
• Granted Patent: US 9,870,202 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/212 with details for data modelling support
• CPC Class Codes: G06F 16/288 Entity relationship models
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/22 Procedural
• CPC Class Codes: G06F 8/24 Object-oriented
• CPC Class Codes: G06F 8/40 Transformation of program code

Abstract

A method includes identifying a plurality of consumption layer objects, at least two of the plurality of consumption layer objects being associated with a different framework and each of the plurality of consumption layer objects include a plurality of business objects, generating a plurality of interface objects each corresponding to a framework, each of the plurality of interface objects being configured to translate each of the business objects to a common intermediate representation, associating metadata with the plurality of interface objects, and associating a runtime interface with the plurality of interface objects.

Claims

1. A method comprising:

identifying a plurality of consumption layer objects, at least two of the plurality of consumption layer objects being associated with a different framework and each of the plurality of consumption layer objects include a plurality of business objects;

generating a plurality of interface objects each corresponding to a framework, each of the plurality of interface objects being configured to translate each of the business objects to a common intermediate representation;

associating metadata with the plurality of interface objects; and

associating a runtime interface with the plurality of interface objects.

2. The method of claim 1, wherein translating each of the business objects into the intermediate representation includes converting data objects into a data structure.

3. The method of claim 1, wherein translating each of the business objects into the intermediate representation includes converting data objects into metadata.

4. The method of claim 1, wherein translating each of the business objects into the intermediate representation includes translating code associated with a procedure into a string of symbols having a common or standard language.

5. The method of claim 1, wherein translating each of the business objects into the intermediate representation includes a mapping of relationships between business objects.

6. The method of claim 1, wherein

translating each of the business objects into the intermediate representation includes using a unique translation scheme for each framework.

7. The method of claim 1, wherein translating each of the business objects into the intermediate representation includes generating a Service Adaptation Definition Language (SADL) definition for each of the business objects.

8. The method of claim 1, wherein associating metadata with the plurality of interface objects includes specifying a SADL data source.

9. The method of claim 1, wherein translating each of the business objects into the intermediate representation decouple each of the business objects from the associated framework used to implement each of the business objects.

10. A non-transitory computer-readable storage medium having stored thereon computer executable program code which, when executed on a computer system, causes the computer system to perform steps comprising:

identifying a plurality of consumption layer objects, at least two of the plurality of consumption layer objects being associated with a different framework and each of the plurality of consumption layer objects include a plurality of business objects;

generating a plurality of interface objects each corresponding to a framework, each of the plurality of interface objects being configured to translate each of the business objects to a common intermediate representation;

associating metadata with the plurality of interface objects; and

associating a runtime interface with the plurality of interface objects.

11. The non-transitory computer-readable storage medium of claim 10, wherein translating each of the business objects into the intermediate representation includes converting data objects into a data structure.

12. The non-transitory computer-readable storage medium of claim 10, wherein translating each of the business objects into the intermediate representation includes converting data objects into metadata.

13. The non-transitory computer-readable storage medium of claim 10, wherein translating each of the business objects into the intermediate representation includes translating code associated with a procedure into a string of symbols having a common or standard language.

14. The non-transitory computer-readable storage medium of claim 10, wherein translating each of the business objects into the intermediate representation includes a mapping of relationships between business objects.

15. The non-transitory computer-readable storage medium of claim 10, wherein translating each of the business objects into the intermediate representation includes using a unique translation scheme for each framework.

16. The non-transitory computer-readable storage medium of claim 10, wherein translating each of the business objects into the intermediate representation decouple each of the business objects from the associated framework used to implement each of the business objects.

17. An apparatus including a processor and a non-transitory computer readable medium, the apparatus comprising:

a business entity configured to implement a plurality of model layer objects in a common structure such that each of a plurality of consumption layer object utilizes a single structure in order to interface with each of the plurality of model layer objects, the business entity including;

a runtime interface configured to accessing data associated with a business object associated with one or more of the of the plurality of model layer objects, and

metadata associated with each of the plurality of interface objects, the metadata including references to the business, at least one business object association, elements of the business object and function calls in the business object.

18. The apparatus of claim 17, wherein the business entity is further configured to decouple each of the business objects from the associated framework used to implement each of the business objects.

19. The apparatus of claim 17, wherein the runtime accesses a service manager for a model layer framework to implement a service.

20. The apparatus of claim 17, wherein at least two of the plurality of consumption layer objects are associated with a different model layer framework and each of the plurality of consumption layer objects include a plurality of business objects.