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

PER_LOCATIONS

HCMUsed in 9 subject areas13 reporting columnsBICC incremental-ready

Person / Worker (PER).

Likely primary key: LOCATION_ID (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 · LOCATION_ID → HZ_LOCATIONS

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.
EMPLOYEE_LOCATION_FLAG●Indicator (Y/N) for the employee location.
INTERNAL_LOCATION_CODE●Code identifying the internal location.
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.
LOCATION_IDPK?●Identifier for the location.
LOCATION_IMAGE_URL●Location image url.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
SET_ID●Identifier for the set.

Used by reports

No cataloged report reads from this table yet, it's part of the broader Fusion dictionary.

Where this surfaces in OTBI

The OTBI subject areas that expose this table. You can't join across them in OTBI, the owned conformed model joins them on shared keys.

Need the extract + dbt staging for PER_LOCATIONS?
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