Business object model layer interface

Patent metadata

Field	Value
Publication number	US-9870202-B2
Application number	US-201414303563-A
Country	US
Kind code	B2
Filing date	Jun 12, 2014
Priority date	Dec 5, 2013
Publication date	Jan 16, 2018
Grant date	Jan 16, 2018

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.

First claim

What is claimed is:

1. A method comprising:
identifying a plurality of consumption layer objects as developer tools, 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 configured to simultaneously provide an interface between two or more consumption layer objects and two or more frameworks, each of the plurality of interface objects being configured to translate each of the business objects to a common intermediate representation, each of the plurality of interface objects being implemented separate from the plurality of consumption layer objects and separate from the corresponding framework, wherein translating each of the business objects into the common intermediate representation includes converting data objects into metadata;
associating the 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 translating code associated with a procedure into a string of symbols having a common or standard language.

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

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

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

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

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

9. 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 as developer tools, 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, each of the plurality of business objects including a data model, a function, a relationship to another of the business objects and a business logic;
generating a plurality of interface objects each configured to simultaneously provide an interface between two or more consumption layer objects and two or more frameworks, each of the plurality of interface objects being configured to translate each of the business objects to a common intermediate representation, each of the plurality of interface objects being implemented separate from the plurality of consumption layer objects and the corresponding framework, wherein translating each of the business objects into the common intermediate representation includes converting data objects into metadata;
associating the metadata with the plurality of interface objects; and
associating a runtime interface with the plurality of interface objects.

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

11. The non-transitory computer-readable storage medium of claim 9 , 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.

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

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

14. The non-transitory computer-readable storage medium of claim 9 , 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.

15. An apparatus including a processor and a non-transitory computer readable medium, the apparatus comprising:
a business entity communicatively coupled between a plurality of consumption layer objects and a plurality of model layer objects, the business entity being configured to simultaneously provide an interface between two or more of the consumption layer objects and two or more frameworks associated with the model layer objects, the business entity being configured to independently implement the plurality of model layer objects in a common structure, the business entity including:
a plurality of interfaces configured to translate a business object in the corresponding one of the plurality of model layer objects,
a runtime interface configured to access data associated with the 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, wherein translating each of the business objects includes converting data objects into the metadata, the metadata including references to the business entity, at least one business object association, elements of the business object and function calls in the business object.

16. The apparatus of claim 15 , 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.

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

18. The apparatus of claim 15 , 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.

Assignees

• Hermanns Marcel
• Sap Se

Inventors

• Hermanns Marcel

Classifications

• G06F16/288

  Entity relationship models · CPC title

• G06F16/212

  with details for data modelling support · CPC title

• G06F8/20 Primary

  Software design · CPC title

• G06F8/22

  Procedural · CPC title

• G06F8/24

  Object-oriented · CPC title