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

HWM_ALLOCATION_RULES_F

SharedUsed in 0 subject areas17 reporting columnsBICC incremental-ready

Source object in the Oracle Fusion data model.

Likely primary key: ALLOCATION_RULE_ID, EFFECTIVE_START_DATE (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE

Columns

ColumnKeyIn reportsDescription (inferred)
ALLOCATION_ID●Identifier for the allocation.
ALLOCATION_RULE_IDPK?●Identifier for the allocation rule.
ALLOCATION_RULE_PRIORITY●Allocation rule priority.
ALLOCATION_TYPE●Type of allocation.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
DATA_LEVEL●Data level.
EFFECTIVE_END_DATE●End date of the effective-dated record.
EFFECTIVE_START_DATEPK?●Start date of the effective-dated record.
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.
MODULE_ID●Identifier for the module.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
RUN_SUMMATION_LEVEL●Run summation level.
TCAT_ID●Identifier for the tcat.

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_ALLOCATION_RULES_F?
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