Results for “irc_all_recruiting_sites_vl”

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

Overview

IRC_ALL_RECRUITING_SITES_VL is a translated (VL) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PER — Human Resources product family. It presents recruiting site definitions in the session language of the querying user, exposing configuration for internal, external, and third-party job posting destinations used by Oracle iRecruitment. The view is a standard EBS MLS (Multi-Language Support) construct: it joins the base entity table to its translation table and filters the translation rows by the user's language environment, so that the site name and URL attributes returned are locale-appropriate.

In both 12.1.1 and 12.2.2 the object is documented as VALID with the same definition, and it is referenced by reporting, integration, and troubleshooting activity rather than by direct end-user data entry. It is commonly queried when diagnosing posting credentials and endpoint configuration, particularly around the POSTING_USERNAME and POSTING_PASSWORD columns, which carry the site credentials used for automated job postings.

Underlying Base Objects

The view is defined over two documented synonyms:

• IRC_ALL_RECRUITING_SITES (aliased RSE) — the base entity table holding recruiting site identifiers, posting flags, cost attributes, descriptive flexfield columns, WHO audit columns, and the posting credential columns. The view selects RSE.ROWID along with RECRUITING_SITE_ID, POSTING_USERNAME, POSTING_PASSWORD, INTERNAL_NAME, and the DFF attributes from this table.
• IRC_ALL_RECRUITING_SITES_TL (aliased IRT) — the translation table supplying SITE_NAME, REDIRECTION_URL, and POSTING_URL for the session language.

The two are joined on RECRUITING_SITE_ID, with the translation side constrained by IRT.LANGUAGE = USERENV('LANG'). Because the join key is the site identifier and the language filter is applied to the TL side, each recruiting site resolves to exactly one translated row for a given session language, preserving the one-row-per-site semantic expected of a VL view. Note that the view exposes the ROWID and base-table audit columns from IRC_ALL_RECRUITING_SITES, not from the translation table.

Key Columns

• RECRUITING_SITE_ID — Primary identifier for the recruiting site; the join key between the base and translation tables.
• SITE_NAME — Translated display name of the recruiting site, sourced from IRC_ALL_RECRUITING_SITES_TL.
• POSTING_USERNAME / POSTING_PASSWORD — Credentials used when posting requisitions or vacancies to the external site. These are the columns most frequently located through searches on "posting_username".
• POSTING_URL / REDIRECTION_URL — Translated posting endpoint and the redirect target used after the posting flow completes.
• INTERNAL, EXTERNAL, THIRD_PARTY — Flags indicating whether the site serves internal candidates, external candidates, or is a third-party board.
• POSTING_COST, POSTING_COST_PERIOD, POSTING_COST_CURRENCY — Cost attributes associated with using the site.
• STYLESHEET — Rendering stylesheet reference for the posting page.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — Descriptive flexfield context and segment values.
• DATE_FROM / DATE_TO — Effective dating for the site configuration.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — Standard WHO audit and optimistic locking columns.

Common Use Cases and Queries

The most frequent operational need is locating the stored posting credentials for a site. A typical lookup is:

SELECT recruiting_site_id, site_name, posting_url,
       posting_username, internal, external, third_party
FROM   apps.irc_all_recruiting_sites_vl
WHERE  UPPER(posting_username) LIKE UPPER('%&username%');

Because the view already applies the language filter, it returns the site name in the current session language, making it preferable to joining the base and TL tables manually in ad hoc reports. Other common uses include:

• Auditing which sites are active for internal versus external postings, and confirming effective dates.
• Inventorying posting costs and currencies across third-party boards.
• Reviewing descriptive flexfield attribute usage on recruiting sites before migration or upgrade.
• Building custom concurrent programs or BI Publisher reports on recruiting site configuration.

For bulk inspection, a query listing all sites with their posting flags and auditing timestamps is sufficient:

SELECT recruiting_site_id, site_name, posting_username,
       date_from, date_to, last_update_date, last_updated_by
FROM   apps.irc_all_recruiting_sites_vl
ORDER  BY recruiting_site_id;

When credential values are not populated as expected, comparing the VL view against IRC_ALL_RECRUITING_SITES_TL for the relevant language is a useful diagnostic step, since missing translation rows will suppress SITE_NAME, POSTING_URL, and REDIRECTION_URL from the view output while the base table retains the credential columns.