Mapping Non-Relational Database Objects to Relational Models
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Non-relational database objects, such as those from ERP systems, are difficult to integrate with relational database models like the SAP BusinessObjects Business Intelligence platform due to the lack of a common language and differing API techniques, making reporting challenging.
Innovation Solution
An efficient mechanism is developed to map non-relational database objects into a relational database model by creating tables that correspond to InfoSets and ABAP functions, using a connection server component to facilitate communication and generate reports, and an SQL engine translates queries to handle non-relational data sources transparently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If non-relational database objects are integrated directly without mapping, then data from ERP systems can be accessed, but different API techniques and lack of common language make querying and reporting difficult
Solution Approach 1:
The patent introduces an intermediary mapping layer that translates non-relational database objects (such as ERP system objects) into a relational database model. This intermediary component handles the complexity of different API techniques and data structures, allowing users to query non-relational data sources using standard relational SQL operations without directly dealing with the underlying complexity.
2Ease of operation
If mapping mechanisms are implemented to translate non-relational objects into relational models, then querying becomes easier, but system complexity increases due to additional translation layers
Solution Approach 1:
The patent creates a virtual copy or representation of non-relational database objects in terms of the relational database model. Instead of physically transforming data, the system creates mapped representations that mirror the structure and behavior of non-relational objects using relational concepts, thereby simplifying querying while avoiding the need for complex real-time translation mechanisms.
3Productivity
If a common language interface is created for non-relational database objects, then reporting becomes more efficient, but the effort required for authoring tools increases
Solution Approach 1:
The patent creates a universal mapping framework that can handle multiple types of non-relational database objects through a common relational model interface. This universal approach allows the same reporting tools and query mechanisms to work with diverse data sources (ERP systems, file systems, etc.) by translating them all into the standard relational model, thereby improving reporting efficiency while reusing existing authoring tool infrastructure.
Data Source
AI summary
According to some embodiments, information may be received about a non-relational database object, such as an InfoSet, InfoSet query, or Advanced Business Application Programming (“ABAP”) function for an enterprise resource planning system. The non-relational database object may then be mapped into a relational database model, such as a model associated with a business intelligence platform. As a result, Structured Query Language (“SQL”) inputs from a business intelligence platform may be used create reports based on information in an enterprise resource planning system.