# US 2018/0322177 A1 · Flexible content integration

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2018/0322177 A1
- Document ID: US20180322177A1
- Status: Published application
- Kind: A1
- Application number: 15/587,952
- Filed: 2017-05-05
- Published: 2018-11-08
- Earliest claimed: 2017-05-05
- Assignees: Sap SE
- Applicants: Sap SE
- Inventors: Apoorv Bhargava; Madathiveetil Bipin; Markus Schmidt-Karaca; Ismail Basha; Gonda Marcusse; Anthony Arun B; Vishnu Kare; Naveed Mohammed
- Web page: https://patentgrep.com/patent/US20180322177A1

## CPC

- G06F 16/254: {Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses}
- G06F 16/214: {Database migration support}
- G06F 16/252: {between a Database Management System and a front-end application}
- G06F 16/256: {in federated or virtual databases}
- G06F 16/86: {Mapping to a database}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Methods, systems, and computer program products for a database processing system are described. A core database comprises common procedures for processing information, at least one of the common procedures configured to provide a common functionality to an analysis application. A content import database comprises content-specific procedures, at least one of the content-specific procedures configured to provide access for at least one of the common procedures to content of the content import database that conforms to a content-specific data model.

## Claims

### Claim 1

A database system for processing information, the database system comprising:
a core database, comprising at least one hardware processor and comprising one or more common procedures for processing the information, at least one of the common procedures configured to provide a common functionality to an analysis application; and
a content import database, comprising the at least one hardware processor and comprising one or more content-specific procedures, at least one of the content-specific procedures configured to provide access for at least one of the common procedures to content of the content import database that conforms to a content-specific data model.

### Claim 2 (depends on 1)

The database system of claim 1, further comprising a content onboarding application for importing the content to the content import database.

### Claim 3 (depends on 2)

The database system of claim 2, wherein the importing the content comprises transforming data obtained from one or more physical source systems to conform to the content-specific data model.

### Claim 4 (depends on 1)

The database system of claim 1, wherein at least one of the content-specific procedures is configured based on a context of a logical system.

### Claim 5 (depends on 1)

The database system of claim 1, wherein the content conforming to the content-specific data model is mapped to a generic content model of the core database.

### Claim 6 (depends on 1)

The database system of claim 1, wherein the common functionality is mapped to functionality of at least one of the content-specific procedures.

### Claim 7 (depends on 1)

The database system of claim 1, wherein the content-specific procedures utilize the content-specific data model and a generic data model to implement a content behavior.

### Claim 8 (depends on 1)

The database system of claim 1, wherein an element of the content is stored in an entity type table of the content import database and an entry in a relation type table describes a relation between two or more elements of the entity type table.

### Claim 9 (depends on 1)

The database system of claim 1, wherein an element of the content is accessed via an entity type view of the content import database and a description of a relation between two or more elements of the entity type view is accessed via a relation type view defined by configuration data.

### Claim 10 (depends on 1)

The database system of claim 1, wherein a logical source system identifier identifies a mapping of data of a physical source system to a selected content-specific model during the importation of data from the physical source system to the content import database.

### Claim 11 (depends on 1)

The database system of claim 1, further comprising a plurality of logical systems, wherein each logical system integrates content together from one or more physical source systems.

### Claim 12 (depends on 11)

The database system of claim 11, wherein each logical system uses a corresponding content-specific data model.

### Claim 13 (depends on 9)

The database system of claim 9, wherein the entity type view is one of a plurality of available entity type views and wherein an entity type view is selected to access the content based on a selection of a logical system.

### Claim 14

A computerized method for processing information, the method comprising:
processing the information using one or more common procedures of a core database, the core database comprising at least one hardware processor, at least one of the common procedures configured to provide a common functionality to an analysis application; and
providing, using at least one content-specific procedure of a content import database, access for at least one of the common procedures to content of the content import database that conforms to a content-specific data model.

### Claim 15 (depends on 14)

The computerized method of claim 14, further comprising importing the content to the content import database.

### Claim 16 (depends on 14)

The computerized method of claim 14, wherein the content-specific procedure is configured based on a context of a logical system.

### Claim 17 (depends on 14)

The computerized method of claim 14, wherein the content conforming to the content-specific data model is mapped to a generic content model of the core database.

### Claim 18 (depends on 14)

The computerized method of claim 14, wherein the common functionality is mapped to functionality of the content-specific procedure.

### Claim 19 (depends on 14)

The computerized method of claim 14, wherein an element of the content is accessed via an entity type view of the content import database and a description of a relation between two or more elements of the entity type view is accessed via a relation type view defined by configuration data.

### Claim 20

A non-transitory machine-readable storage medium comprising instructions, which when implemented by one or more machines, cause the one or more machines to perform operations comprising:
processing the information using one or more common procedures of a core database, the core database comprising at least one hardware processor, at least one of the common procedures configured to provide a common functionality to an analysis application; and
providing, using at least one content-specific procedure of a content import database, access for at least one of the common procedures to content of the content import database that conforms to a content-specific data model.
