Results for “irc_template_associations”

50+ results




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

Overview

IRC_TEMPLATE_ASSOCIATIONS is a table owned by the HR schema and delivered within the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented description is "Offer Template Association table." It functions as the linking mechanism that binds an offer template stored in the XDO_TEMPLATES_B repository to a specific job, and optionally to a position and organization, so that recruitment offers presented to candidates use the correct template for a given requisition context. This enables organizations to drive template selection through job and organization data rather than through manual assignment.

The ETRM metadata carries a heuristic Data Vault classification of link for this table. As a modeling suggestion, this reflects the fact that the table primarily resolves many-to-many style relationships between offer templates and organizational entities (jobs, positions, organizations) rather than acting as a standalone hub or a descriptive satellite. It carries a small set of descriptive and effective-dating attributes alongside its foreign keys, but its core identity is relational.

Key Information Stored

The documented physical schema exposes 14 columns. The most significant are listed below.

The surrogate key TEMPLATE_ASSOCIATION_ID is distinct from any business-key candidate: no alternate unique index beyond IRC_TEMPLATE_ASSOCIATION_PK is documented, so uniqueness of a given job/template combination is not enforced by a separate constraint.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios involve resolving which template is offered for a given job, or auditing the template-to-job mappings in use. A representative query joining the primary foreign keys is:

  • Resolving a template per job: SELECT a.template_association_id, a.job_id, a.template_id, a.default_association FROM irc_template_associations a WHERE a.job_id = :job_id;
  • Filtering active associations by effective date: ... WHERE TRUNC(SYSDATE) BETWEEN a.start_date AND NVL(a.end_date, TRUNC(SYSDATE));
  • Identifying defaults: ... WHERE a.default_association = 'Y';
  • Join to templates for descriptive output: SELECT a.job_id, t.template_name FROM irc_template_associations a, xdo_templates_b t WHERE a.template_id = t.template_id;
  • Join to jobs: SELECT a.template_id, j.name FROM irc_template_associations a, per_jobs j WHERE a.job_id = j.job_id;

These patterns support recruitment configuration audits, template rationalization projects, and troubleshooting when the wrong offer template appears for a requisition.

Related Objects

  • XDO_TEMPLATES_B — referenced via IRC_TEMPLATE_ASSOCIATIONS.TEMPLATE_ID; the template repository table holding the offer template definition.
  • PER_JOBS — referenced via IRC_TEMPLATE_ASSOCIATIONS.JOB_ID; defines the job to which the template is associated.
  • IRC_TEMPLATE_ASSOCIATIONS itself, keyed by IRC_TEMPLATE_ASSOCIATION_PK (TEMPLATE_ASSOCIATION_ID).
  • PER_POSITIONS — implied by POSITION_ID, providing position-level association context.
  • HR_ORGANIZATION_UNITS — implied by ORGANIZATION_ID, supplying the organization context.
  • IRC_OFFER_TEMPLATES / recruitment offer APIs — the consuming logic that reads these associations during offer generation.

Because requirement and offer flows depend on these mappings, changes to rows in this table directly affect which templates candidates receive.