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

IRC_CAND_PROFILE_USAGES_M

SharedUsed in 0 subject areas17 reporting columns

Recruiting (IRC).

Likely primary key: CAND_PROFILE_USAGE_ID (inferred from Oracle naming conventions, verify against Tables & Views)
Joins (inferred from key columns): PROFILE_ID → HRT_PROFILES_B

Columns

ColumnKeyIn reportsDescription (inferred)
CAND_PROFILE_USAGE_IDPK?●Identifier for the cand profile usage.
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_LATEST_CHANGE●Effective latest change.
EFFECTIVE_SEQUENCE●Effective sequence.
EFFECTIVE_START_DATE●Start date of the effective-dated record.
JOB_DEFINITION_NAME●Name of the job definition.
JOB_DEFINITION_PACKAGE●Job definition package.
LAST_UPDATED_BY●User who last updated the row.
LAST_UPDATE_DATE●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_ID●Identifier for the person.
PROFILE_ID●Identifier for the profile.
PROFILE_TYPE●Type of profile.
REQUEST_ID●Identifier of the process that created or last updated the row.

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