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

HNS_PERSONS

SharedUsed in 0 subject areas18 reporting columnsBICC incremental-ready

Health & Safety (HNS).

Likely primary key: PERSON_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): TASK_TYPE_CODE → DOO_TASK_TYPES_B

Columns

ColumnKeyIn reportsDescription (inferred)
ACTION_REQUIRED_FLAG●Indicator (Y/N) for the action required.
ACTUAL_COMPLETION_DATE●Actual completion date.
COMPLETED_FLAG●Indicator (Y/N) for the completed.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
DELETED_FLAG●Indicator (Y/N) for the deleted.
EMPLOYEE_ID●Identifier for the employee.
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.
PERSON_ASSIGN_ID●Identifier for the person assign.
PERSON_IDPK?●Identifier for the person.
RESULT_CODE●Code identifying the result.
ROLE_CODE●Code identifying the role.
TARGET_COMPLETION_DATE●Target completion date.
TASK_ID●Identifier for the task.
TASK_TYPE_CODE●Code identifying the task type.

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 HNS_PERSONS?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
What the extract does not carry · The export ceiling · The extraction pattern