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

PAY_DIR_CARDS_F

PayrollUsed in 0 subject areas16 reporting columnsBICC incremental-ready

Payroll (PAY).

Likely primary key: DIR_CARD_ID, EFFECTIVE_START_DATE (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): DIR_CARD_DEFINITION_ID → PAY_DIR_CARD_DEFINITIONS_VL · LEGISLATIVE_DATA_GROUP_ID → PER_LEGISLATIVE_DATA_GROUPS · PAYROLL_RELATIONSHIP_ID → PAY_REL_GROUPS_DN · SOURCE_ID → HRT_SOURCES_B

Columns

ColumnKeyIn reportsDescription (inferred)
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
CREATOR_TYPE●Type of creator.
DIR_CARD_DEFINITION_ID●Identifier for the dir card definition.
DIR_CARD_IDPK?●Identifier for the dir card.
EFFECTIVE_END_DATE●End date of the effective-dated record.
EFFECTIVE_START_DATEPK?●Start date of the effective-dated record.
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.
LEGISLATIVE_DATA_GROUP_ID●Identifier for the legislative data group.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
PAYROLL_RELATIONSHIP_ID●Identifier for the payroll relationship.
SOURCE_ID●Identifier for the source.
SOURCE_TYPE●Type of source.
STATUS●Status.

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_DIR_CARDS_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