Analytics Catalog/Data dictionary/HWM_TM_REC_GRP_USAGES
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Data dictionary

HWM_TM_REC_GRP_USAGES

SharedUsed in 0 subject areas15 reporting columnsBICC incremental-ready

Source object in the Oracle Fusion data model.

Likely primary key: TM_REC_GRP_USAGES_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): TM_REC_GRP_ID → HWM_TM_REC_GRP · TM_REC_ID → HWM_TM_REC

Columns

ColumnKeyIn reportsDescription (inferred)
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
DATA_SET_ID●Identifier for the data set.
ENTERPRISE_ID●Identifier for the enterprise.
LAST_UPDATED_BY●User who last updated the row.
LAST_UPDATE_DATEINCR●Date and time the row was last updated (the incremental-extract key).
LAST_UPDATE_LOGIN●Session login of the user who last updated the row.
LATEST_VERSION●Latest version.
LAYER_CODE●Code identifying the layer.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
TM_REC_GRP_ID●Identifier for the tm rec grp.
TM_REC_GRP_USAGES_IDPK?●Identifier for the tm rec grp usages.
TM_REC_GRP_VERSION●Tm rec grp version.
TM_REC_ID●Identifier for the tm rec.
TM_REC_VERSION●Tm rec version.

Used by reports

No cataloged report reads from this table yet, it's part of the broader Fusion dictionary.

Subject areas

Need the extract + dbt staging for HWM_TM_REC_GRP_USAGES?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
What the extract does not carry · The export ceiling · The extraction pattern