Results for “usage_flag”

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

Overview

The HR.PER_CAL_ENTRY_VALUES table stores the individual value rows that make up calendar entries within Oracle E-Business Suite Human Resources. In the PER (Human Resources) module, calendars are used to define patterns of working and non-working time, holiday schedules, and other recurring or dated events that drive absence accruals, payroll processing, and time-and-labor calculations. PER_CAL_ENTRY_VALUES holds the discrete date/value records associated with each parent calendar entry, including hierarchical relationships between values through the self-referencing PARENT_ENTRY_VALUE_ID column.

The table is implemented in the HR schema and is valid in both 12.1.1 and 12.2.2. The physical definition documents 18 columns, with a primary key constraint PER_CAL_ENTRY_VALUES_PK on CAL_ENTRY_VALUE_ID. From a Data Vault modeling perspective, the metadata heuristic classifies this object as satellite-leaning, reflecting its role as a descriptive detail table attached to a calendar entry hub rather than a link or true hub itself. This classification is a modeling suggestion; the operational structure of the table remains a conventional normalized relational table within the EBS schema.

Key Information Stored

The most significant columns in PER_CAL_ENTRY_VALUES are:

• CAL_ENTRY_VALUE_ID — Surrogate primary key for each calendar entry value row, enforced by PER_CAL_ENTRY_VALUES_PK.
• CALENDAR_ENTRY_ID — Foreign key to PER_CALENDAR_ENTRIES, identifying the parent calendar entry to which this value belongs.
• PARENT_ENTRY_VALUE_ID — Self-referencing foreign key indicating the parent value, enabling multi-level hierarchical structures of calendar values.
• ORG_STRUCTURE_ELEMENT_ID — Foreign key to PER_ORG_STRUCTURE_ELEMENTS, associating the value with a specific organizational unit or structure element.
• HIERARCHY_NODE_ID — Identifier of the hierarchy node tied to this value, supporting the organizational hierarchy context.
• IDVALUE — The actual value identifier carried by the row, commonly the date or date-coded value associated with the calendar entry.
• OVERRIDE_NAME and OVERRIDE_TYPE — Capture override naming and type information when standard calendar behaviour is replaced for a given value.
• USAGE_FLAG — Indicates whether the entry value is active and available for use.
• ORGANIZATION_ID — Business group or organization context for the row.
• IDENTIFIER_KEY — Descriptive identifier used to distinguish the value within its context.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by EBS to manage concurrent updates.
• ZD_EDITION_NAME — Editioning column present in the 12.2.x schema; CAL_ENTRY_VALUE_ID combined with ZD_EDITION_NAME forms a unique index, making the pair the business-key candidate alongside the single-column primary key.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record standard EBS audit trail information.

Common Use Cases and Queries

Typical use cases include auditing calendar patterns, extracting holiday or non-working day lists for a business group, validating hierarchical calendar structures, and reconciling override values applied to standard calendar entries. Reporting queries frequently join to PER_CALENDAR_ENTRIES:

• SELECT cev.cal_entry_value_id, cev.idvalue, cev.usage_flag, ce.calendar_entry_id FROM hr.per_cal_entry_values cev, hr.per_calendar_entries ce WHERE cev.calendar_entry_id = ce.calendar_entry_id;
• Self-join to resolve parent-child value hierarchies: SELECT child.idvalue, parent.idvalue parent_value FROM hr.per_cal_entry_values child, hr.per_cal_entry_values parent WHERE child.parent_entry_value_id = parent.cal_entry_value_id;
• Filter by ORGANIZATION_ID or ORG_STRUCTURE_ELEMENT_ID to report calendar values for a specific organization or hierarchy node.

Data-extraction routines and ETL processes for absence management and payroll frequently read this table to resolve the effective dates behind accrual and eligibility logic.

Related Objects

• PER_CALENDAR_ENTRIES — Parent table; joined on PER_CAL_ENTRY_VALUES.CALENDAR_ENTRY_ID = PER_CALENDAR_ENTRIES.CALENDAR_ENTRY_ID.
• PER_CAL_ENTRY_VALUES — Self-referencing through PARENT_ENTRY_VALUE_ID, supporting hierarchical value resolution.
• PER_ORG_STRUCTURE_ELEMENTS — Referenced through ORG_STRUCTURE_ELEMENT_ID for organizational context.
• PER_CALENDARS / PER_TIME_PERIODS — Calendar-level objects that indirectly depend on these values through the calendar entry chain.
• PER_ABSENCE_ATTENDANCES and accrual-plan related tables — Consume calendar values during absence and accrual calculation.
• Public API / concurrent processes such as date-track and calendar generation routines that populate and read calendar entry values.