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

PAY_PAY_RELATIONSHIPS_DN

PayrollUsed in 0 subject areas14 reporting columnsBICC incremental-ready

Payroll (PAY).

Primary key: not yet catalogued for PAY_PAY_RELATIONSHIPS_DN, reference Oracle Tables & Views guide. · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): LEGISLATIVE_DATA_GROUP_ID → PER_LEGISLATIVE_DATA_GROUPS · PAYROLL_RELATIONSHIP_ID → PAY_REL_GROUPS_DN

Columns

ColumnKeyIn reportsDescription (inferred)
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
END_DATE●End date.
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.
PAYROLL_RELATIONSHIP_NUMBER●Payroll relationship number.
PAYROLL_STAT_UNIT_ID●Identifier for the payroll status unit.
PERSON_ID●Identifier for the person.
RELATIONSHIP_TYPE_ID●Identifier for the relationship type.
START_DATE●Start date.

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