Search Results schedulable_entity

Overview

APPS.HR_CALENDAR_USAGES_V is a reporting view that exposes calendar usage assignments for schedulable entities within Oracle E-Business Suite 12.1.1 and 12.2.2 (also referenced as 12.2 ETRM). It joins the base calendar usage table HR_CALENDAR_USAGES to the pattern purpose usages definition HR_PATTERN_PURPOSE_USAGES, and then resolves the schedulable entity type — the value the user searched for, schedulable_entity — by joining HR_LOOKUPS on LOOKUP_TYPE = 'SCHEDULABLE_ENTITY'. This view allows reporting tools and integrations to display calendar usage by date, time, purpose, and entity without manually performing the lookup joins.

Because schedulable entities can be people or assignments, the view is defined as a UNION ALL that returns separate result blocks for person-based and assignment-based usages. The first block joins PER_ALL_PEOPLE_F for the PERSON entity, and the second block joins PER_ASSIGNMENTS_F for the ASSIGNMENT entity. The view exposes the base table columns along with friendly lookups, making it suitable for both user-facing reports and API-driven integration.

Underlying Base Objects

The ETRM metadata documents the view as referencing the synonyms HR_CALENDAR_USAGES, HR_PATTERN_PURPOSE_USAGES, PER_ALL_PEOPLE_F, and PER_JOBS_TL; the views HR_LOCATIONS, HR_LOOKUPS, HR_ORGANIZATION_UNITS, HR_POSITIONS_F, and PER_ASSIGNMENTS_F; the FND_SESSIONS synonym; and the packages HR_API, HR_GENERAL, HR_SECURITY, and FND_PROFILE.

• HR_CALENDAR_USAGES — base table of individual calendar usage records; the view exposes its columns directly.
• HR_PATTERN_PURPOSE_USAGES — defines the pattern purpose and schedulable entity association (ENTITY_NAME, PATTERN_PURPOSE).
• PER_ALL_PEOPLE_F and PER_ASSIGNMENTS_F — entity sources for the PERSON and ASSIGNMENT UNION ALL branches.
• HR_LOOKUPS — provides the MEANING for the schedulable entity and pattern purpose codes (lookup types SCHEDULABLE_ENTITY and PATTERN_PURPOSE).
• FND_SESSIONS — filters by session and the session effective date to determine the valid person record.

Key Columns

• CALENDAR_ID, CALENDAR_USAGE_ID, PURPOSE_USAGE_ID, PRIMARY_KEY_VALUE — identifiers linking usage to its calendar, purpose, and primary entity key.
• START_DATE, END_DATE — exposed both as full date and as truncated date plus HH24:MI time via TO_CHAR/TRUNC expressions.
• ENTITY_NAME, MEANING, PURPOSE, FULL_NAME / ASSIGNMENT_NUMBER — schedulable entity code and lookup meaning, plus the resolved person name or assignment number.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns inherited from the base table.

Common Use Cases and Queries

The view is typically queried for calendar availability reporting, leave and shift pattern validation, and for identifying which calendar usage records apply to a given person or assignment.

Sample query filtering by schedulable entity:

• SELECT person_name, meaning, pattern_purpose, start_date, end_date FROM apps.hr_calendar_usages_v WHERE entity_name = 'PERSON';
• SELECT calendar_usage_id, calendar_id, start_date, end_date FROM apps.hr_calendar_usages_v WHERE primary_key_value = :person_id ORDER BY start_date;

Because the view's predicate on FND_SESSIONS uses USERENV('SESSIONID') and the session effective date, queries execute against the effective person record for the current session, aligning with HR security handled by HR_SECURITY and HR_API.