Sunday, July 14, 2019

Significance of TDATASEG, TDATASEG_T, and TDATAMAP



TDATASEG table stores the actual data. However TDATASEG_T tables are the staging tables that holds the data until successful data execution and then data will get copied to TDATASEG table
The TDATASEG table is used to store the data loaded by the user, and the transformation between the source dimension members and results of the mapping process.

Only in a successful data rule execution data transformations stored in TDATASEG_T be copied over to TDATASEG.

TDATASEG_T Temporary data table used for transforming data from source to target in a data rule execution.

To ensure read consistency, data is extracted from the corresponding staging table (for example, AIF_EBS_GL_BALANCES_STG, AIF_EBS_GL_DAILY_BAL_STG, or AIF_PS_LEDGER) and copied to TDATASEG_T (partitioned by LOADID), which is then used for transforming source data to target data based on the data mappings specified in TDATAMAP_T.

TDATASEGW Temporary data table used for transforming write-back data from source to target in a write-back rule execution.

Writeback data is extracted from the temporary staging table (AIF_WRITEBACK_ESS_DATA_T) and copied over to TDATASEGW (partitioned by LOADID), which is then used for transforming source data to target data based on the data mappings specified in TDATAMAP_T.

If you have selected to only “Import from Source,” you can query this table by LOADID to view the data transformations that were applied during the write-back rule execution.

TDATASEG Audit table describing the data transformations in a data rule execution.
Only in a successful data rule execution data transformations stored in TDATASEG_T be copied over to TDATASEG.

No comments:

Post a Comment

Other posts

How is the data size calculated for a EPM Cloud service instance?

The total size of data used by your EPM Cloud service instance is the sum of the following: Application data stored in Essbase Artifact...