Search Results irc_default_posting_swi




Overview
Explore in AI Chat

Overview

IRC_DEFAULT_POSTING_SWI is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, categorized under the API classification OTHER within the E-Business Suite Technical Reference Manual (ETRM). Its name and member procedures associate it with the Oracle iRecruitment product family, where the IRC prefix denotes database objects belonging to iRecruitment. The suffix SWI (Supplemental Web Interface or similar internal convention) indicates that this package acts as a server-side wrapper that encapsulates the default posting behaviour used when recruiting vacancies are published to internal and external job boards.

The package is documented as VALID in the ETRM for both 12.1.1 and 12.2.2, and it depends on the HR_API package and the SYS.STANDARD library, confirming that it participates in the HR/iRecruitment integration layer and uses standard PL/SQL constructs. It is a self-referencing object: the ETRM notes that APPS.IRC_DEFAULT_POSTING_SWI references and is referenced by APPS.IRC_DEFAULT_POSTING_SWI, meaning the specification and body are listed as mutual dependencies, and the package is not referenced by any other documented package. This self-contained nature confirms it is a leaf-level utility rather than a foundation API.

Key Procedures and Functions

The ETRM documents three procedures within the package, all of which operate on the concept of a "default posting" record — the reusable posting template or default publication attributes applied to a vacancy before it is released.

  • CREATE_DEFAULT_POSTING — Inserts a new default posting definition. This procedure is used when a recruiting administrator or setup routine establishes a new default posting configuration that subsequent vacancy publications can inherit.
  • DELETE_DEFAULT_POSTING — Removes an existing default posting definition. Invoked when a default posting is retired or no longer applicable to the organization's recruitment configuration.
  • UPDATE_DEFAULT_POSTING — Modifies the attributes of an existing default posting. This is the routine used to change posting parameters such as visibility, duration, or associated board definitions without recreating the record.

No parameter lists are documented in the ETRM excerpt; the call signatures should be obtained directly from the package specification in the database. The procedures form a complete create, update, and delete (CRUD) triad for the default posting entity.

Tables Accessed

The ETRM metadata for IRC_DEFAULT_POSTING_SWI does not enumerate any base tables accessed through APPS synonyms. The only documented dependencies are on the HR_API package and the SYS.STANDARD library. Because the package is an iRecruitment object, its underlying data operations are expected to target the iRecruitment posting tables — the family of tables supporting vacancy posting defaults and related board configuration — but the ETRM excerpt provided does not confirm specific table names. Consultants performing impact analysis should query ALL_DEPENDENCIES for the package body to obtain the authoritative table list, since the published metadata omits it.

Usage Notes

This package is intended for internal consumption by iRecruitment application code rather than by end users or custom extensions. Because it is referenced by no other documented package and does not appear in the form or concurrent program layer of the ETRM, it is most likely called from the iRecruitment web user interface flows that manage default posting setup, or from other iRecruitment server-side PL/SQL that handles vacancy publication.

Custom code should generally avoid calling IRC_DEFAULT_POSTING_SWI directly. The supported integration surface for iRecruitment and HR data is the HR_API family and public iRecruitment APIs. Direct invocation risks bypassing validation, audit, and security checks performed at higher layers. When troubleshooting default posting behaviour in 12.1.1 or 12.2.2, the recommended approach is to trace execution to this package and inspect its body source, then confirm whether the failure originates in CREATE_DEFAULT_POSTING, UPDATE_DEFAULT_POSTING, or DELETE_DEFAULT_POSTING. Because the package is documented as VALID, no recompilation is required unless a dependency such as HR_API is invalidated.