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

FF_USER_TABLES_VL

SharedUsed in 0 subject areas16 reporting columnsBICC incremental-ready

view layer, joins the base table with translations for the current language.

Likely primary key: USER_TABLE_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): LEGISLATIVE_DATA_GROUP_ID → PER_LEGISLATIVE_DATA_GROUPS

Columns

ColumnKeyIn reportsDescription (inferred)
BASE_USER_TABLE_NAME●Name of the base user table.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
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.
LEGISLATION_CODE●Code identifying the legislation.
LEGISLATIVE_DATA_GROUP_ID●Identifier for the legislative data group.
MODULE_ID●Identifier for the module.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
RANGE_OR_MATCH●Range or match.
USER_KEY_UNITS●User key units.
USER_ROW_TITLE●User row title.
USER_TABLE_IDPK?●Identifier for the user table.
USER_TABLE_NAME●Name of the user table.

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