Integration tables
The table-based integration stored procedures generate a number of staging and
intermediary tables.
These integration tables are generated by the _CREATE_SCHEMA
stored procedures and are removed by the _CLEAR_SCHEMA
stored procedures.
In general, the tables are labeled with prefixes and suffixes which categorize them as:
Table | Description |
---|---|
ATT_ | A prefix indicating a table that contains cube fact data or dynamic attribute data in the format that Designer can import directly into a cube. In Infor d/EPM table-naming conventions, the third letter of the name typically indicates C for cube or D for dimension. For example, WDCDRIVER cube or WDDDRIVER dimension. |
DAT_ | A prefix indicating a table containing staged or transformed data. These are not read by Designer when importing dimensions or cube data. |
DIM_ | A prefix indicating one of the set of four dimension tables that Designer requires in order to create a dimension. |
METADATA_ | A prefix indicating a table that contains variables required for cube data load. |
_ATTRIBUTES | One of the four dimension tables that Designer requires in order to create a dimension. It holds attributes for dimension elements. |
_ELEMENTS | One of the four dimension tables that Designer requires in order to create a dimension. It holds the list of dimension elements. |
_HIERARCHIES | One of the four dimension tables that Designer requires in order to create a dimension. It holds the list of hierarchies in the dimension. |
_PARENTS | One of the four dimension tables that Designer requires in order to create a dimension. It holds parent/child relationships between elements. |
_STAGE | A table (prefixed with DAT_) to hold the data from the source
system that is to be imported into Infor d/EPM via
Designer. The data in these tables are
read by stored procedures ending in _PREPARE_STAGING that validate the data and write it out to a separate
copy of the table having a suffix of _TRANSFORMED. |
_TRANSFORMED | A table (prefixed with DAT_) that holds validated staged data
processed by stored procedures ending in _PREPARE_STAGING . This validated data is in turn processed by a second
stored procedure to write it to cube tables required by Designer. The _TRANSFORMED table may contain values marked by the
_PREPARE_STAGING stored procedures
as errors. These values are prefixed with _ERROR_ so they can be found with queries.
Processing cannot continue until the _ERROR_ values are corrected. |