Search Results per_cal_entry_geo_list




Overview
Explore in AI Chat

Overview

PER_CAL_ENTRY_GEO_LIST is a table owned by the HR schema within the Oracle E-Business Suite Human Resources (PER) module. Its documented description is "Calendar Entry Geo Coverage Cache." The table functions as a caching structure that records the geographic coverage associated with calendar entries, allowing the application to resolve which calendar entries apply to specific organizational hierarchy nodes without recalculating that coverage on every access. In EBS 12.1.1 and 12.2.2, this cache supports calendar and availability processing used by HR and related scheduling functions.

The ETRM metadata classifies this object heuristically as a link table under a Data Vault modeling approach. This classification is suggested by its foreign key structure: the table sits between two parent entities and resolves a many-to-many-style association. Specifically, it links PER_CALENDAR_ENTRIES to PER_GEN_HIERARCHY_NODES, expressing which calendar entries cover which hierarchy nodes. A link classification is a modeling suggestion derived from the FK topology rather than a formal declaration in the EBS data dictionary.

Key Information Stored

The documented physical schema contains eight columns in the HR schema. The most significant columns and their roles are:

  • CALENDAR_ENTRY_ID — Foreign key to PER_CALENDAR_ENTRIES. Identifies the calendar entry whose geographic coverage is being cached. This is one half of the link's composite business identity.
  • HIERARCHY_NODE_ID — Foreign key to PER_GEN_HIERARCHY_NODES. Identifies the organization hierarchy node covered by the calendar entry. This is the second half of the link's composite business identity.
  • OVR_CAL_ENTRY_VALUE_ID — An override reference associated with the calendar entry value for the covered node, supporting override behavior in coverage resolution.
  • LAST_UPDATE_DATE — Standard EBS audit column recording the most recent modification timestamp.
  • LAST_UPDATED_BY — Standard audit column identifying the user who last modified the row.
  • LAST_UPDATE_LOGIN — Standard audit column capturing the login session of the last update.
  • CREATED_BY — Standard audit column identifying the user who created the row.
  • CREATION_DATE — Standard audit column recording the row creation timestamp.

The documented metadata does not identify a single-column surrogate primary key; the natural business key is the combination of CALENDAR_ENTRY_ID and HIERARCHY_NODE_ID, which together form the link relationship. The remaining columns are either the override reference or standard WHO-column audit attributes.

Common Use Cases and Queries

Because this table is a cache, its primary use is resolving calendar coverage for hierarchy nodes during availability and scheduling operations. Queries typically join it to its two parents. A representative pattern to list coverage for a given calendar entry is:

  • SELECT g.HIERARCHY_NODE_ID, g.OVR_CAL_ENTRY_VALUE_ID FROM PER_CAL_ENTRY_GEO_LIST g WHERE g.CALENDAR_ENTRY_ID = :entry_id;
  • A reverse lookup by node: SELECT g.CALENDAR_ENTRY_ID FROM PER_CAL_ENTRY_GEO_LIST g WHERE g.HIERARCHY_NODE_ID = :node_id;
  • Reporting joins to PER_CALENDAR_ENTRIES and PER_GEN_HIERARCHY_NODES to produce calendars per organizational node for HR availability analysis.
  • Data-quality checks for duplicate link pairs, since the natural key is the CALENDAR_ENTRY_ID and HIERARCHY_NODE_ID combination.

Administrators may inspect this table when calendar coverage appears stale, since its cache nature means reconciliation with the underlying calendar and hierarchy definitions may be required.

Related Objects

  • PER_CALENDAR_ENTRIES — Parent table joined via PER_CAL_ENTRY_GEO_LIST.CALENDAR_ENTRY_ID = PER_CALENDAR_ENTRIES.CALENDAR_ENTRY_ID.
  • PER_GEN_HIERARCHY_NODES — Parent table joined via PER_CAL_ENTRY_GEO_LIST.HIERARCHY_NODE_ID = PER_GEN_HIERARCHY_NODES.HIERARCHY_NODE_ID.
  • PER_CALENDAR_EVENTS and related PER calendar definition tables, which define the entries referenced above.
  • PER_GEN_HIERARCHIES, which defines the hierarchy to which covered nodes belong.
  • HR availability and scheduling APIs that consume calendar coverage when resolving organizational applicability.