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

PER_PHONES

HCMUsed in 42 subject areas20 reporting columnsBICC incremental-ready

Person / Worker (PER).

Likely primary key: PHONE_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE

Columns

ColumnKeyIn reportsDescription (inferred)
AREA_CODECode identifying the area.
BUSINESS_GROUP_IDIdentifier for the business group.
COUNTRY_CODE_NUMBERCountry code number.
CREATED_BYUser who created the row.
CREATION_DATEDate and time the row was created.
DATE_FROMDate from.
DATE_TODate to.
EXTENSIONExtension.
LAST_UPDATED_BYUser who last updated the row.
LAST_UPDATE_DATEINCRDate and time the row was last updated (the incremental-extract key).
LAST_UPDATE_LOGINSession login of the user who last updated the row.
LEGISLATION_CODECode identifying the legislation.
OBJECT_VERSION_NUMBEROptimistic-locking version number, incremented on each update.
PERSON_IDIdentifier for the person.
PHONE_IDPK?Identifier for the phone.
PHONE_NUMBERPhone number.
PHONE_TYPEType of phone.
SEARCH_PHONE_NUMBERSearch phone number.
SPEED_DIAL_NUMBERSpeed dial number.
VALIDITYValidity.

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