Search Results hr_pattern_bits_v




Overview
Explore in AI Chat

Overview

HR_PATTERN_BITS_V is a valid, Oracle-owned (APPS schema) database view within the PER — Human Resources product module. Its documented purpose is to "support user interface" functionality, meaning it is primarily a presentation-layer construct rather than a standalone transactional or reporting entity. In the context of Oracle EBS 12.1.1 and 12.2.2, this view is typically consumed by Oracle Forms-based setup screens, self-service pages, or lookup-driven list-of-values regions that let administrators define and manage scheduling patterns.

Because it is a view and not a table, HR_PATTERN_BITS_V carries no independent storage; it delivers a denormalized, user-friendly projection of scheduling-related pattern bits by joining the foundational pattern-bit data with lookup translations. For reporting and integration purposes, the view is useful when building custom concurrent programs, OBIEE/BI Publisher extracts, or interface programs that need to display a human-readable time-unit meaning rather than the internal code. Notably, the documentation confirms the view is synchronized with the 12.2.2 Enterprise Technology Reference Manual (ETRM) metadata, where it is registered as a documented view object owned by APPS.

Underlying Base Objects

The documented referenced base objects for HR_PATTERN_BITS_V are:

The view definition illustrates the join logic: it selects the pattern bit attributes from HR_PATTERN_BITS and applies an outer join (+) to HR_LOOKUPS on BASE_TIME_UNIT = LOOKUP_CODE, restricted to LOOKUP_TYPE = 'SCHEDULER_TIME_UNIT' or a null lookup code. This left-outer join ensures every pattern bit is returned even when no matching lookup row exists, which is why the view text explicitly permits the LOOKUP_CODE IS NULL branch. The relationship is therefore one-to-zero-or-one between pattern bits and lookup entries, keeping the row grain at one record per pattern bit.

Key Columns

The view exposes four columns, one of which reflects a column alias relative to the underlying table:

  • PATTERN_BIT_ID — the unique primary key identifier for each pattern bit; used for joins back to HR_PATTERN_BITS and for referential integrity.
  • PATTERN_BIT_CODE — the short code (user-searchable keyword "pattern_bit_code") that uniquely names the bit within the scheduling framework; commonly the value referenced in configuration and integration logic.
  • BASE_TIME_UNIT_MEANING — the descriptive meaning derived from HR_LOOKUPS, giving a readable time-unit label; null when no matching SCHEDULER_TIME_UNIT lookup exists.
  • TIME_UNIT_MULTIPLIER — the numeric factor applied to the time unit, used in scheduling calculations to derive duration or frequency.

Common Use Cases and Queries

Typical scenarios include populating list-of-values on scheduling setup forms, building validation reports for pattern configuration, and extracting human-readable pattern data for integrations. A representative query retrieving bit codes with their meaning follows:

SELECT PATTERN_BIT_ID,
   PATTERN_BIT_CODE,
   BASE_TIME_UNIT_MEANING,
   TIME_UNIT_MULTIPLIER
FROM APPS.HR_PATTERN_BITS_V
ORDER BY PATTERN_BIT_CODE;

To locate a specific bit by its code, filter on the keyword the user searched: WHERE PATTERN_BIT_CODE = :pattern_bit_code. Administrators auditing incomplete lookup setup can add WHERE BASE_TIME_UNIT_MEANING IS NULL to find pattern bits lacking a valid SCHEDULER_TIME_UNIT translation. Because the view is read-only and lightweight, it is safe to query directly in SQL*Plus, ad-hoc reporting, and custom interfaces without affecting the base tables.