Results for “proc_period_type_m”

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

Overview

PAYBV_CALENDAR_V is a read-only view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PAY (Payroll) product. It exposes configuration data from the payroll calendar definition, allowing reporting tools, concurrent programs, and integration interfaces to query period set information without accessing the underlying base table directly. The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and its definition carries the WITH READ ONLY clause, confirming that it is intended strictly for query and reporting purposes and cannot be used to perform DML against the source data.

The view is particularly relevant to users investigating the PROC_PERIOD_TYPE attribute, since it surfaces this column directly while also providing a decoded, human-readable equivalent. This dual presentation of the raw code and its lookup meaning makes the view a convenient reporting source for payroll administrators and technical consultants who need to verify how calendars are configured across a period set.

Underlying Base Objects

According to the documented view text, PAYBV_CALENDAR_V selects exclusively from the PAY_CALENDARS synonym, aliased as PC. PAY_CALENDARS is the payroll calendar table that stores period set definitions, including date ranges, comments, descriptive flexfield attributes, and audit columns. The view applies a simple projection over this single table with no joins, aggregation, or filtering conditions.

The only other referenced object is the HR_BIS package, invoked as HR_BIS.BIS_DECODE_LOOKUP('YES_NO', PC.PROC_PERIOD_TYPE). HR_BIS is a shared Business Intelligence System utility package used throughout Oracle HRMS and Payroll products to translate lookup codes into their displayed meanings. In this view, the function is called with the lookup type YES_NO and the value of PROC_PERIOD_TYPE, producing the decoded column PROC_PERIOD_TYPE_M. This dependency means the view's output for the decoded column depends on the current contents of the YES_NO lookup type in the application.

Key Columns

The view exposes the following significant columns:

• PERIOD_SET_NAME — the name of the payroll period set to which the calendar definition belongs. This is the primary identifier for grouping related calendar rows.
• PROC_PERIOD_TYPE — the raw processing period type code stored on the calendar record. This is the column the user searched for and represents whether the calendar is used for processing, and in what manner, per the YES_NO lookup semantics.
• PROC_PERIOD_TYPE_M — the decoded meaning of PROC_PERIOD_TYPE derived through HR_BIS.BIS_DECODE_LOOKUP against the YES_NO lookup type, suitable for direct display in reports.
• ACTUAL_PERIOD_TYPE — the period type actually used by the calendar, distinct from the processing indicator.
• START_DATE — the effective start date of the calendar definition.
• COMMENTS — free-text remarks attached to the calendar record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE20 — descriptive flexfield context and segment values, enabling reporting on any custom descriptive attributes configured for payroll calendars.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE, supporting change tracking and data lineage analysis.

Common Use Cases and Queries

The view is typically used to report calendar configuration, validate processing period settings, and feed downstream interfaces requiring period set metadata. A common query lists all calendars for a given period set with decoded processing types:

• SELECT period_set_name, proc_period_type, proc_period_type_m, actual_period_type, start_date FROM paybv_calendar_v WHERE period_set_name = :p_period_set ORDER BY start_date;
• Auditing recently changed calendars: SELECT period_set_name, proc_period_type_m, last_update_date, last_updated_by FROM paybv_calendar_v WHERE last_update_date > SYSDATE - 30;
• Reviewing descriptive flexfield values: SELECT period_set_name, attribute_category, attribute1, attribute2 FROM paybv_calendar_v WHERE attribute_category IS NOT NULL;

Because the view is read-only and projects directly from PAY_CALENDARS, query performance mirrors that of the base table, and no additional integrity or validation logic is applied beyond the lookup decoding performed by HR_BIS.