Search Results per_cal_entry_org_list




Overview
Explore in AI Chat

Overview

PER_CAL_ENTRY_ORG_LIST is a Human Resources (PER) module table owned by the HR schema. Its documented description is "Calendar Entry Org Coverage Cache." The table functions as a denormalized cache that links individual calendar entries held in PER_CALENDAR_ENTRIES to the organization units that are covered by, or affected by, those entries. Rather than resolving organization coverage dynamically at runtime through the organizational hierarchy, Oracle E-Business Suite materializes the relationship here, allowing calendar-based processes and user interfaces to determine quickly which organizations a given calendar entry applies to.

Under the heuristic Data Vault classification derived from its foreign key structure, this object is modeled as a link. It sits between two hubs — the calendar entry (PER_CALENDAR_ENTRIES) and the organization unit (HR_ALL_ORGANIZATION_UNITS) — and records the association between them. A link classification is appropriate because the table's primary purpose is to resolve a many-to-many relationship rather than to store descriptive attributes of a single business entity. In Oracle EBS 12.1.1 and 12.2.2 the physical definition is consistent, with the documented schema exposing eight columns.

Key Information Stored

The table is intentionally narrow. Its most significant columns are:

  • CALENDAR_ENTRY_ID — Foreign key to PER_CALENDAR_ENTRIES; identifies the calendar entry whose organizational coverage is being cached.
  • ORGANIZATION_ID — Foreign key to HR_ALL_ORGANIZATION_UNITS; identifies the organization unit covered by the entry.
  • OVR_CAL_ENTRY_VALUE_ID — References the override calendar entry value associated with this coverage record, supporting date-effective or overriding behavior for specific organizations.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns capturing who last modified the row and when.
  • CREATED_BY, CREATION_DATE — Standard creation audit columns identifying the originating user and timestamp.

The natural business key is the combination of CALENDAR_ENTRY_ID and ORGANIZATION_ID; the documented metadata does not expose a separate surrogate primary key column, so these two attributes together act as the effective row identifier. No standalone business-key unique index is documented beyond this composite relationship.

Common Use Cases and Queries

Typical uses include reporting on which organizations are affected by a calendar entry, validating coverage before a calendar build, and diagnosing missing coverage during calendar generation. A representative query resolves the organization name for each covered entry:

  • SELECT ceo.calendar_entry_id, ceo.organization_id, hou.name
    FROM per_cal_entry_org_list ceo, hr_all_organization_units hou
    WHERE ceo.organization_id = hou.organization_id
    AND ceo.calendar_entry_id = :entry_id;
  • Coverage counts per entry: SELECT calendar_entry_id, COUNT(*) FROM per_cal_entry_org_list GROUP BY calendar_entry_id;
  • Detecting overrides: filter on OVR_CAL_ENTRY_VALUE_ID IS NOT NULL to isolate entries where an organization-specific override value applies.

Because the table is a cache, it should generally be queried rather than updated manually; regeneration occurs through the standard calendar processes.

Related Objects

  • PER_CALENDAR_ENTRIES — joined via PER_CAL_ENTRY_ORG_LIST.CALENDAR_ENTRY_ID; the parent calendar entry.
  • HR_ALL_ORGANIZATION_UNITS — joined via PER_CAL_ENTRY_ORG_LIST.ORGANIZATION_ID; the covered organization.
  • PER_CALENDAR_EVENTS and PER_CALENDAR_EVENT_ENTRIES — related calendar structures that drive entry generation.
  • PER_TIME_PERIODS — monthly calendar periods that reference the parent calendar and organization coverage indirectly.
  • The override value reference (OVR_CAL_ENTRY_VALUE_ID) links logically to override definition tables used by the calendar override feature.