Mapping non-relational database objects into a relational database model
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.
1. A computer implemented method, the method comprising:
receiving information about a non-relational database object having a plurality of import parameters and a plurality of export parameters, wherein the non-relational database object represents a programming function; and
mapping, via a processor, the programming function into a relational database model by:
flattening at least one multi-field import parameter into a set of single-field import parameters,
flattening at least one multi-field export parameter into a set of single-field export parameters,
creating a first table containing a column for: (i) each import parameter, including the set of single-field import parameters, (ii) each export parameter, including the set of single-field export parameters, and (iii) an attribute identifier; and
creating a primary key, for the first table, composed of each import parameter and the attribute identifier, wherein the programming function is associated with an output table parameter and said mapping further comprises:
creating a second table for the output table parameter, the second table containing a column for: (i) each import parameter associated with the programming function, (ii) all of the fields of the first table, and (iii) one reference identifier attribute to reference the primary key of the first table.
2. The method of claim 1 , wherein the programming function is associated with a plurality of output table parameters and a separate table is created for each output table parameter.
3. The method of claim 2 , wherein at least one table is nested within another table.
4. The method of claim 1 , wherein the programming function includes at least one changing parameter that is translated into both an import parameter and an export parameter.
5. The method of claim 1 , wherein the non-relational database object is associated with an enterprise resource planning system.
6. The method of claim 1 , wherein the relational database model is associated with a business intelligence platform.
7. The method of claim 1 , further comprising:
generating a report in accordance with the mapping of the programming function into the relational database model.
8. The method of claim 1 , wherein flattening the at least one multi-field export parameter into a set of single-field export parameters comprises:
converting each input parameter into table input columns; and
converting each output parameter into table output columns.
9. A computer implemented method, the method comprising:
receiving information about a non-relational database object having a plurality of import parameters and a plurality of export parameters, wherein the non-relational database object represents a programming function; and
mapping, via a processor, the programming function into a relational database model by:
flattening at least one multi-field import parameter into a set of single-field import parameters,
flattening at least one multi-field export parameter into a set of single-field export parameters, and
creating a first table containing a column for: (i) each import parameter, including the set of single-field import parameters, (ii) each export parameter, including the set of single-field export parameters, and (iii) an attribute identifier, wherein the programming function includes at least one changing parameter that is translated into both an import parameter and an export parameter, wherein the programming function is associated with an output table parameter and said mapping further comprises:
creating a second table for the output table parameter, the second table containing a column for: (i) each import parameter associated with the programming function, (ii) all of the fields of the first table, and (iii) one reference identifier attribute to reference the primary key of the first table.