Search Results irc_posting_contents




Overview
Explore in AI Chat

Overview

IRC_POSTING_CONTENTS is a Human Resources (PER) module table that stores the actual content of a recruitment posting in a reusable form. Rather than duplicating posting text, branding, recruiter and manager contact information, and descriptive attributes across every activity or assignment that references a posting, Oracle iRecruitment centralizes that content in this single table and allows other objects to point to it by POSTING_CONTENT_ID. The table resides in the HR schema and is classified as VALID within the E-Business Suite 12.1.1 / 12.2.2 data model.

The documented physical schema contains 78 columns, with a single unique index, IRC_POSTING_CONTENTS_PK, defined on POSTING_CONTENT_ID. The heuristic Data Vault classification mined from the foreign key structure is hub-leaning, meaning the table functions primarily as a durable, referenced entity keyed by a surrogate identifier, with descriptive payload attached. As a modeling suggestion, it may be best treated as a hub with associated descriptive attributes rather than as a pure transactional link.

Key Information Stored

The surrogate primary key is POSTING_CONTENT_ID, uniquely enforced by IRC_POSTING_CONTENTS_PK; no separate natural business key is documented, so the surrogate key is the reliable join anchor.

Common Use Cases and Queries

Typical reporting retrieves the contact block and DFF content for a set of posting content records, or resolves which assignments and recruitment activities share a given content record.

  • Listing postings with their recruiter and manager contacts: 
    SELECT posting_content_id,
       recruiter_full_name, recruiter_email, recruiter_work_telephone,
       manager_full_name,   manager_email,   manager_work_telephone,
       date_approved
  FROM  irc_posting_contents
 WHERE display_recruiter_info = 'Y';
  • Identifying assignments linked to a specific content record: 
    SELECT a.assignment_id, a.posting_content_id
  FROM  per_all_assignments_f a
 WHERE a.posting_content_id = :posting_content_id;
  • Auditing recently approved posting content using DATE_APPROVED and the WHO columns.
  • Reading flexfield content via IPC_INFORMATION_CATEGORY / IPC_INFORMATIONn for downstream integration or BI extracts.

Related Objects

The documented foreign-key relationships show that this table is a referenced parent (hub) for several recruitment objects.

  • PER_ALL_ASSIGNMENTS_F — references IRC_POSTING_CONTENTS via POSTING_CONTENT_ID; links assignment records to reusable posting content.
  • PER_RECRUITMENT_ACTIVITIES — references IRC_POSTING_CONTENTS via POSTING_CONTENT_ID; ties recruitment activities to the posting content they publish.
  • IRC_PENDING_DATA — references IRC_POSTING_CONTENTS via POSTING_CONTENT_ID; holds staged or pending content changes prior to approval.
  • IRC_POSTING_CONTENTS_PK — the unique index that enforces the primary key and defines the join anchor for all dependents.

Together these objects form the core of iRecruitment posting content management: content is authored and stored once in IRC_POSTING_CONTENTS, approved, and then consumed by activities, assignments, and pending-data staging records through POSTING_CONTENT_ID.