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

IRC_PROSPECTS

SharedUsed in 0 subject areas17 reporting columnsBICC incremental-ready

Recruiting (IRC).

Likely primary key: PROSPECT_ID (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE
Joins (inferred from key columns): REQUISITION_ID → IRC_REQUISITIONS_B · SUBMISSION_ID → IRC_SUBMISSIONS

Columns

ColumnKeyIn reportsDescription (inferred)
ADDED_BY_PERSON_ID●Identifier for the added by person.
CANDIDATE_PERSON_ID●Identifier for the candidate person.
CONTEXT_ID●Identifier for the context.
CONTEXT_TYPE_CODE●Code identifying the context type.
CREATED_BY●User who created the row.
CREATION_DATE●Date and time the row was created.
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_STATUS●Status of the object.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
PROSPECT_IDPK?●Identifier for the prospect.
PROSPECT_STATUS_CODE●Code identifying the prospect status.
PROSPECT_TYPE_CODE●Code identifying the prospect type.
REFERRAL_ID●Identifier for the referral.
REQUISITION_ID●Identifier for the requisition.
SUBMISSION_ID●Identifier for the submission.

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