Search Results delete_template_association




Overview
Explore in AI Chat

Overview

The APPS.IRC_TEMPLATE_ASSOCIATION_API package body is a public PL/SQL API within the Oracle E-Business Suite iRecruitment (IRC) application module. Its business function is to manage the association between recruitment templates and the organizational entities to which they apply — specifically jobs, positions, and organizations. These associations determine the scope and applicability of a template, controlling which templates are available for use within a given recruiting context across a specified date range. The package encapsulates the full lifecycle of a template association record, providing a controlled, validated interface for creating, modifying, and removing associations while maintaining the audit and object versioning conventions required by EBS public APIs.

Key Procedures and Functions

The package exposes three documented procedures, all classified as API entry points:

  • CREATE_TEMPLATE_ASSOCIATION — Inserts a new association record linking a template to a job, position, and/or organization, with effective-dating support. It validates inputs, resolves the effective date (defaulting it to the truncated start date when not supplied), issues a savepoint, and invokes the corresponding before-process user hook. Only the input parameters are documented; the procedure also returns the generated object version number and template association identifier to the caller via out parameters.
  • UPDATE_TEMPLATE_ASSOCIATION — Modifies an existing association record. It applies the same effective-dating and validation discipline as the create operation, supports the before-process user hook pattern, and manages the object version number in accordance with EBS concurrency conventions.
  • DELETE_TEMPLATE_ASSOCIATION — Removes an existing association record, again honoring the effective-date model and user hook framework so that date-tracked history is preserved rather than physically destroyed where applicable.

All three procedures follow the standard EBS API architecture: a business logic layer (_bk1) is called from the public API, enabling customers to extend behavior through user hooks without modifying Oracle-owned code.

Tables Accessed

The ETRM documentation excerpt for this package does not enumerate the underlying tables accessed through APPS synonyms. Based on the parameters and business context, the package operates against the iRecruitment template association schema — the entity that stores the template identifier, default association flag, job, position, and organization references, the start and end dates, the effective date, and the object version number. The package is the sole supported interface for maintaining this data, so direct DML against the base table is neither required nor recommended. One other package references this API, indicating that it participates in a broader iRecruitment dependency chain.

Usage Notes

This API is typically invoked from iRecruitment setup and administration forms, from concurrent programs that load or maintain recruitment template configuration, and from custom PL/SQL extensions that provision template-to-organization associations. Because it is an effective-dated API, callers should supply p_effective_date where date-tracked corrections are required; when omitted, the procedure falls back to the start date. Callers must pass a Boolean p_validate value to control rollback behavior during testing or dry-run validation. The header comment records the package as noship, meaning it ships with the application. In both Oracle EBS 12.1.1 and 12.2.2 the calling conventions are consistent, and the presence of the before-process hooks makes the package safe to extend without patching Oracle source. Custom code should always route template association maintenance through this API to preserve validation, versioning, and audit integrity.