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

PER_GRADES_IN_LADDERS_F

HCMUsed in 0 subject areas14 reporting columnsBICC incremental-ready

Person / Worker (PER).

Likely primary key: GRADES_IN_LADDER_ID, EFFECTIVE_START_DATE (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): ACTION_OCCURRENCE_ID → PER_ACTION_OCCURRENCES

Columns

ColumnKeyIn reportsDescription (inferred)
ACTION_OCCURRENCE_ID●Identifier for the action occurrence.
BUSINESS_GROUP_ID●Identifier for the business group.
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_DATEPK?●Start date of the effective-dated record.
GRADES_IN_LADDER_IDPK?●Identifier for the grades in ladder.
GRADE_ID●Identifier for the grade.
GRADE_LADDER_ID●Identifier for the grade ladder.
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.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
SEQUENCE●Sequence.

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