Results for “irc_default_postings”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IRC_DEFAULT_POSTINGS table is an Oracle E-Business Suite (EBS) table owned by the HR schema and delivered under the PER — Human Resources product family. It stores a library of default postings, where each posting record is mapped to exactly one of a position, a job, or an organization. In the context of Oracle iRecruitment and the broader Human Resources model, this table acts as a reusable template catalog: recruiters and HR administrators can define posting content once and associate it with common organizational constructs such as a job, a position, or an organization unit, then leverage those defaults when creating new requisitions or vacancy postings.

From a dimensional modeling perspective, the mined foreign key structure — pointing outward to PER_JOBS and HR_ALL_ORGANIZATION_UNITS via surrogate identifiers — suggests a link classification. That is, IRC_DEFAULT_POSTINGS behaves less like an independent hub of business entities and more like an associative/link table that connects posting attributes to existing master records held elsewhere in the HR schema. This classification is a heuristic derived from the FK topology and should be treated as a modeling suggestion rather than an authoritative Data Vault assignment.

Key Information Stored

The table contains 41 documented columns in the ETRM 12.2.2 physical schema. The most business-relevant columns are:

• DEFAULT_POSTING_ID — the surrogate primary key, enforced by the unique index IRC_DEFAULT_POSTINGS_PK. This is the only documented unique index and therefore the only business-key candidate in the metadata.
• POSITION_ID — references the position to which the default posting is bound, when the posting is position-scoped.
• JOB_ID — foreign key to PER_JOBS; identifies the job associated with the default posting.
• ORGANIZATION_ID — foreign key to HR_ALL_ORGANIZATION_UNITS; identifies the organization unit scoped to the posting.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — a standard EBS descriptive flexfield (DFF) block, allowing customer-specific extensions without schema change.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard "WHO" audit columns maintained by EBS.
• CREATED_BY and CREATION_DATE — insertion audit columns.
• OBJECT_VERSION_NUMBER — the optimistic-locking column used by the Oracle Application Framework (OAF) and BC4J layers to detect concurrent updates.

Note that DEFAULT_POSTING_ID is the surrogate key; no additional composite business-key unique index is documented beyond the primary key, so natural-key uniqueness on (JOB_ID, ORGANIZATION_ID, POSITION_ID) is not formally enforced at the database level in the documented metadata.

Common Use Cases and Queries

Typical scenarios include reporting on which default postings exist per job or organization, verifying posting template coverage before a recruitment cycle, and diagnosing why a default posting did not appear for a given vacancy. Because the table is FK-anchored to PER_JOBS and HR_ALL_ORGANIZATION_UNITS, most queries join through those parents.

A representative query listing postings by job is:

• SELECT p.DEFAULT_POSTING_ID, j.NAME job_name, p.LAST_UPDATE_DATE FROM IRC_DEFAULT_POSTINGS p JOIN PER_JOBS j ON p.JOB_ID = j.JOB_ID;
• SELECT p.DEFAULT_POSTING_ID, o.NAME org_name FROM IRC_DEFAULT_POSTINGS p JOIN HR_ALL_ORGANIZATION_UNITS o ON p.ORGANIZATION_ID = o.ORGANIZATION_ID;
• Audit reporting: filter on LAST_UPDATE_DATE to track recent template changes, and use OBJECT_VERSION_NUMBER to detect records modified after a given baseline.

Related Objects

• PER_JOBS — parent master table joined via IRC_DEFAULT_POSTINGS.JOB_ID = PER_JOBS.JOB_ID.
• HR_ALL_ORGANIZATION_UNITS — parent master table joined via IRC_DEFAULT_POSTINGS.ORGANIZATION_ID = HR_ALL_ORGANIZATION_UNITS.ORGANIZATION_ID.
• IRC_DEFAULT_POSTINGS_PK — the unique index on DEFAULT_POSTING_ID that backstops the primary key.
• Other iRecruitment (IRC_%) tables that consume default posting definitions when building vacancy and requisition content.
• Standard HR "WHO" columns reference FND_USER/PER_ALL_PEOPLE_F indirectly through LAST_UPDATED_BY and CREATED_BY, supporting audit traceability.