Results for “per_calendar_entries_pk”

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

Overview

PER_CALENDAR_ENTRIES is a Human Resources (PER) table in Oracle E-Business Suite 12.1.1 and 12.2.2, owned by the HR schema and stored under the HR database user. Its documented description is "Calendar Entries." The table defines calendar-entry records that associate a named calendar definition with a general hierarchy, a value set, and one or more organization structures or organization structure versions. In practice, it functions as the header or definition record for calendar-based constructs used within Oracle HRMS, while the detailed applicability of each entry (organization lists, geography lists, and calendar values) is held in dependent child tables.

From a Data Vault modeling perspective, ETRM metadata classifies this object as hub-leaning. This heuristic classification is a modeling suggestion rather than a fixed design: the table carries a single surrogate primary key (CALENDAR_ENTRY_ID), several foreign-key references to other descriptive entities, and descriptive attributes such as name, type, and date/time boundaries. That profile is consistent with a hub or a low-grain reference table rather than a pure transactional link or a pure satellite.

Key Information Stored

The table contains 24 documented columns. The following are the most significant for definition and query purposes.

• CALENDAR_ENTRY_ID — the surrogate primary key, defined by the unique index PER_CALENDAR_ENTRIES_PK. In the documented 12.2.2 schema this index is composite, covering CALENDAR_ENTRY_ID together with ZD_EDITION_NAME, which supports edition-based redefinition and makes the pair the effective business-key candidate.
• ZD_EDITION_NAME — the edition identifier used by Oracle's editioning framework; it distinguishes multiple editions of the same logical entry.
• NAME and DESCRIPTION — the descriptive identity and free-text explanation of the calendar entry.
• TYPE — the category of the calendar entry, which governs how the entry is interpreted by downstream logic.
• START_DATE, START_HOUR, START_MIN — the effective start point of the calendar entry, split into date and time components.
• END_DATE, END_HOUR, END_MIN — the effective end point, similarly decomposed.
• HIERARCHY_ID — foreign key to PER_GEN_HIERARCHY, identifying the general hierarchy to which the entry belongs.
• VALUE_SET_ID — foreign key to FRM_PART_VALUE_SETS, linking the entry to its value set.
• ORGANIZATION_STRUCTURE_ID and ORG_STRUCTURE_VERSION_ID — foreign keys to PER_ORGANIZATION_STRUCTURES and PER_ORG_STRUCTURE_VERSIONS respectively, scoping the entry to a particular organization structure and its version.
• BUSINESS_GROUP_ID and LEGISLATION_CODE — the business group and legislative context for the record.
• IDENTIFIER_KEY — a business identifier attribute carried on the entry.
• OBJECT_VERSION_NUMBER — the optimistic locking column, together with the standard WHO audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical reporting scenarios resolve calendar entries by name, type, or effective period, then join upward to hierarchy, value set, and organization structure metadata. A simple lookup of active definitions follows:

• SELECT calendar_entry_id, name, type, start_date, end_date FROM per_calendar_entries WHERE business_group_id = :p_bg ORDER BY name;
• Joining the hierarchy for reporting: SELECT c.name, h.* FROM per_calendar_entries c, per_gen_hierarchy h WHERE c.hierarchy_id = h.hierarchy_id;
• Enumerating the organizations applicable to an entry via the child list table: SELECT c.name, l.* FROM per_calendar_entries c, per_cal_entry_org_list l WHERE c.calendar_entry_id = l.calendar_entry_id;
• Retrieving the values attached to an entry: SELECT v.* FROM per_cal_entries_v… , per_cal_entry_values v WHERE v.calendar_entry_id = c.calendar_entry_id;

Because the primary index includes ZD_EDITION_NAME, queries on 12.2.2 should be aware of editioning when filtering by identifier. Effective-dating checks using START_DATE/END_DATE are appropriate for determining whether an entry applies to a given reporting period.

Related Objects

The following objects are directly related through documented primary- and foreign-key relationships.

• PER_GEN_HIERARCHY — referenced by PER_CALENDAR_ENTRIES.HIERARCHY_ID.
• FRM_PART_VALUE_SETS — referenced by PER_CALENDAR_ENTRIES.VALUE_SET_ID.
• PER_ORGANIZATION_STRUCTURES — referenced by PER_CALENDAR_ENTRIES.ORGANIZATION_STRUCTURE_ID.
• PER_ORG_STRUCTURE_VERSIONS — referenced by PER_CALENDAR_ENTRIES.ORG_STRUCTURE_VERSION_ID.
• PER_CAL_ENTRY_GEO_LIST — child table referencing CALENDAR_ENTRY_ID.
• PER_CAL_ENTRY_ORG_LIST — child table referencing CALENDAR_ENTRY_ID.
• PER_CAL_ENTRY_VALUES — child table referencing CALENDAR_ENTRY_ID.

These relationships define the entry's definitional context and its enumerations of geographies, organizations, and values, and they form the basis for joins in any extraction or reporting exercise against PER calendar data.