Search Results p_org_name

Overview

IRC_DEFAULT_POSTING_API is a public PL/SQL API belonging to the Oracle iRecruitment application family (identified by the IRC prefix) and is owned by the APPS schema. Its business purpose is to manage the records that support default recruitment postings — the template-style posting content that iRecruitment uses to describe an organization, job, and opportunity to external and internal candidates before a specific requisition-based posting is created. The package encapsulates the create, update, and delete lifecycle for these default posting definitions, ensuring that the underlying posting tables are populated consistently and that validation logic (including the optional P_VALIDATE flag observed in the package header) is applied before data is committed. In Oracle EBS 12.1.1 and 12.2.2 the package is documented in ETRM with an API classification, confirming that it is a supported programmatic interface rather than a private implementation detail.

Key Procedures and Functions

Three procedures constitute the documented interface of this package:

• CREATE_DEFAULT_POSTING — Creates a new default posting record. The procedure exposes a broad parameter set covering the position, job, and organization context (P_POSITION_ID, P_JOB_ID, P_ORGANIZATION_ID, P_ORG_NAME, P_ORG_DESCRIPTION, P_JOB_TITLE), the descriptive content fields (P_BRIEF_DESCRIPTION, P_DETAILED_DESCRIPTION, P_JOB_REQUIREMENTS, P_ADDITIONAL_DETAILS, P_HOW_TO_APPLY), image references, and the full DFF attribute column range (ATTRIBUTE1 through ATTRIBUTE17). It also accepts P_LANGUAGE_CODE (defaulting to the session language) and P_VALIDATE (defaulting to FALSE).
• UPDATE_DEFAULT_POSTING — Modifies an existing default posting record, allowing the same descriptive and attribute content to be revised.
• DELETE_DEFAULT_POSTING — Removes a default posting record when it is no longer required.

All three procedures are PL/SQL callable and follow the standard EBS API convention of controlled validation and error signalling through the FND message stack.

Tables Accessed

The ETRM metadata for this package does not enumerate the specific base tables it writes to; the documented reference lists tables accessed via APPS synonyms. Functionally, the package operates on the iRecruitment default posting storage — the tables that persist posting header content, organization and job descriptive text, image URLs, and the DFF attribute columns. Because the parameter list mirrors that structure exactly, the package acts as the sole supported write path for those columns, isolating callers from the physical schema. Custom code should never insert into or update those tables directly; the API should be used instead so that validation and attribute handling remain intact.

Usage Notes

IRC_DEFAULT_POSTING_API is typically invoked from iRecruitment setup and administration forms, and from concurrent programs or custom extensions that need to seed or maintain default posting content programmatically. When called from custom code, the recommended pattern is to pass P_VALIDATE => TRUE to force full validation before commit, and to check the FND message stack for errors after the call. The P_ORG_NAME parameter — the term matched in the user's search — is the organization display name used when the posting is rendered to candidates; it is distinct from P_ORGANIZATION_ID, which supplies the internal organization reference. Supplying the ID without a name, or vice versa, may produce incomplete posting output, so both should be provided together. The package is referenced by one other package in the EBS codebase, indicating it is a dependency of downstream recruitment processing and should be treated as a stable, supported entry point. Language handling defaults to the runtime session language, so multilingual deployments should set P_LANGUAGE_CODE explicitly where translated content is required.