Search Results per_cal_entry_values_v




Overview
Explore in AI Chat

Overview

The PER_CAL_ENTRY_VALUES_V view is a public Oracle EBS database object owned by the APPS schema in the Human Resources (PER) product family. It presents Calendar Entry Values — the assignment of specific values (such as a person, organization, or hierarchy entity) to entries within an HR calendar. In Oracle EBS 12.1.1 and 12.2.2 it serves as the reporting and integration surface for calendar entry value data, shielding downstream consumers from the underlying normalization and from the API calls required to derive a human-readable display value.

The view is documented in ETRM as VALID and is intended for query access rather than direct DML. Because calendar entries underpin Availability, Absence, and workforce scheduling functionality, this view is frequently used in custom reports, extracts, and interfaces that need to resolve which entity occupies a given calendar entry.

Underlying Base Objects

The view is defined over three base objects joined in the APPS schema:

Two PL/SQL packages are invoked for value derivation:

The outer joins ensure that entry values without a hierarchy node or organization structure element still return a row.

Key Columns

  • CAL_ENTRY_VALUE_ID — primary identifier of the calendar entry value row.
  • CALENDAR_ENTRY_ID — the parent calendar entry to which the value applies.
  • HIERARCHY_NODE_ID — the hierarchy node, when the value references a node rather than a raw ID value.
  • IDVALUE — the source identifier value; the unaliased column in the view text. (Note: the ETRM column list includes IDVALUE, which is consumed by the DECODE logic to yield the third select column.)
  • DISPLAY_VALUE — the decoded, human-readable value derived via HR_CAL_ENTRY_VALUE_API.GET_DISPLAY_VALUE or HR_GENERAL.DECODE_ORGANIZATION. This is the primary column for reporting.
  • OVERRIDE_NAME and OVERRIDE_TYPE — user-supplied overrides for the entry value label and type.
  • PARENT_ENTRY_VALUE_ID — self-referencing parent, enabling hierarchical entry values.
  • USAGE_FLAG — indicates how the value is used.
  • IDENTIFIER_KEY — the descriptive key identifying the entry value.
  • ORG_STRUCTURE_ELEMENT_ID and ORGANIZATION_ID — organizational context for the value.
  • OBJECT_VERSION_NUMBER, plus the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — audit and concurrency attributes.

Common Use Cases and Queries

Typical uses include reporting calendar entry values for a specific calendar entry, resolving display names for integration extracts, and auditing organizational assignments within HR calendars.

List entry values for a calendar entry:

SELECT cal_entry_value_id,
       calendar_entry_id,
       display_value,
       override_name,
       usage_flag,
       organization_id
FROM   apps.per_cal_entry_values_v
WHERE  calendar_entry_id = :p_calendar_entry_id;

Retrieve organizational entry values with their resolved names:

SELECT v.cal_entry_value_id,
       v.display_value,
       v.organization_id,
       v.identifier_key
FROM   apps.per_cal_entry_values_v v
WHERE  v.org_structure_element_id IS NOT NULL
ORDER  BY v.display_value;

Resolve hierarchy-node-based values:

SELECT v.calendar_entry_id,
       v.hierarchy_node_id,
       v.display_value
FROM   apps.per_cal_entry_values_v v
WHERE  v.hierarchy_node_id IS NOT NULL;

Because DISPLAY_VALUE is computed through PL/SQL API calls, queries returning large result sets may incur performance overhead; filtering on indexed columns such as CALENDAR_ENTRY_ID is recommended. All access should be read-only, with DML performed through the supported HR calendar entry value APIs.