Search Results pattern_purpose




Overview
Explore in AI Chat

Overview

HR_CALENDAR_USAGES_V is a view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PER (Human Resources) product family and is documented in ETRM as a UI-supporting object: "Used to support user interface." The view consolidates calendar usage records stored in HR_CALENDAR_USAGES with pattern-purpose configuration held in HR_PATTERN_PURPOSE_USAGES, and resolves the human-readable meanings of those lookups through HR_LOOKUPS. It joins each usage to a schedulable entity — a person or an assignment — so that forms and concurrent programs can display the correct entity reference, lookup meaning, and pattern purpose for each calendar usage.

Because the view enforces session-scoped security and effective-dating logic internally, it presents a ready-to-consume rowset for reporting and integration rather than a raw table image. The pattern_purpose searched by the user appears here as PPU.PATTERN_PURPOSE, resolved against the PATTERN_PURPOSE lookup type to produce PURPOSE.MEANING.

Underlying Base Objects

The documented underlying objects span tables, views, synonyms, and packages:

The UNION ALL structure separates the person entity (returning ENTITY.FULL_NAME) from the assignment entity (returning ENTITY.ASSIGNMENT_NUMBER), so the "primary key" column has different semantic meaning per branch.

Key Columns

  • CALENDAR_ID / CALENDAR_USAGE_ID — primary keys identifying the calendar and its usage row.
  • PRIMARY_KEY_VALUE — the entity key; a PERSON_ID in the person branch, an assignment identifier in the assignment branch.
  • PURPOSE_USAGE_ID — links the usage to its pattern-purpose configuration.
  • START_DATE / END_DATE — full datetime values, supplemented by truncated date and HH24:MI time representations.
  • ENTITY_NAME — the schedulable entity type ("PERSON" or assignment).
  • PATTERN_PURPOSE — the lookup code whose meaning the user is retrieving.
  • The lookup MEANING columns — human-readable descriptions of the entity and the pattern purpose.
  • Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER).

Common Use Cases and Queries

Typical scenarios include verifying which calendars apply to a person, extracting usages by pattern purpose, and validating pattern-purpose lookup configuration. A sample query filtered on pattern purpose:

  • SELECT calendar_usage_id, primary_key_value, entity_name, pattern_purpose, start_date, end_date FROM apps.hr_calendar_usages_v WHERE pattern_purpose = :p_pattern_purpose;
  • Reporting all person-level usages: SELECT ... WHERE entity_name = 'PERSON' AND primary_key_value = :person_id;
  • Resolving lookup meanings: selecting the MEANING columns alongside PATTERN_PURPOSE for display or reconciliation.

Because FND_SESSIONS and HR_SECURITY constrain results, queries executed outside an initialized EBS session may return no rows, and effective-dated entities reflect only the session's effective date.