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

PAY_RUN_TYPES_F

PayrollUsed in 0 subject areas17 reporting columnsBICC incremental-ready

Payroll (PAY).

Primary key: not declared here, see Oracle's Tables and Views page for PAY_RUN_TYPES_F · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): LEGISLATIVE_DATA_GROUP_ID → PER_LEGISLATIVE_DATA_GROUPS

Columns

ColumnKeyIn reportsDescription (inferred)
BASE_RUN_TYPE_NAME●Name of the base run type.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
EFFECTIVE_END_DATE●End date of the effective-dated record.
EFFECTIVE_START_DATE●Start date of the effective-dated record.
INCLUSION_FLAG●Indicator (Y/N) for the inclusion.
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.
RUN_METHOD●Run method.
RUN_TYPE_ID●Identifier for the run type.
SHORTNAME●Shortname.
SRS_FLAG●Indicator (Y/N) for the srs.

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 PAY_RUN_TYPES_F?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
The report that lies quietly · Approval history vanishes · What the extract does not carry