Results for “per_time_period_types”

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

Overview

PER_TIME_PERIOD_TYPES is a predefined reference table owned by the HR schema within the Oracle E-Business Suite Human Resources (PER) product family. It stores the master list of valid period types — such as Weekly, Bi-Weekly, Semi-Monthly, Monthly, Quarterly, and Annually — that Oracle Payroll and Oracle HRMS budgeting functionality use to define the frequency and structure of calendars, payroll cycles, and budget commitment elements. Because period types are consumed by both payroll calendar definition and HR budget calendar definition, this table acts as a shared reference point across the payroll and budgeting sub-modules rather than being tied to a single transactional process.

From a Data Vault modeling perspective, the mined foreign-key topology suggests this object is hub-leaning. It contains no foreign keys of its own and serves as the target of many inbound references, which is characteristic of a hub entity (a stable, uniquely identified business concept) rather than a transactional link or a descriptive satellite. Downstream tables depend on it to qualify the frequency of the records they store, and the row count is intentionally small and stable since these are predefined system values.

Key Information Stored

The documented primary key is PER_TIME_PERIOD_TYPES_PK, defined on the PERIOD_TYPE column (the unique index in 12.2.2 also includes ZD_EDITION_NAME, reflecting the editioning feature introduced in the multi-tenant architecture). PERIOD_TYPE is both the surrogate/business key and the value that all dependent tables store as a foreign key, so it is the single most important column in the table.

• PERIOD_TYPE — primary key and business-key candidate; the short code identifying each period type.
• DISPLAY_PERIOD_TYPE — the user-facing label presented in forms and lists.
• DESCRIPTION — the full descriptive name of the period type.
• NUMBER_PER_FISCAL_YEAR — how many such periods fall within a fiscal year, used for proration and frequency conversion.
• YEAR_TYPE_IN_NAME — flag controlling whether the year is embedded in the period name (for example, "January 2024").
• SYSTEM_FLAG — indicates whether the row is a seeded system value or user-defined.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — the standard Oracle EBS descriptive flexfield (DFF) column set for extending the definition without schema changes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns tracking creation and modification.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context recorded when rows are inserted or updated.
• ZD_EDITION_NAME — editioning column supporting online patching in 12.2.x.

Common Use Cases and Queries

Typical usage centers on joining this reference table to dependent tables to resolve a period code into a human-readable frequency. For example, listing payroll calendars with their actual frequency, or reporting budget commitment element default frequencies, requires a join on PERIOD_TYPE. A representative query follows:

SELECT pt.DISPLAY_PERIOD_TYPE, pc.CALENDAR_NAME
FROM PAY_CALENDARS pc, PER_TIME_PERIOD_TYPES pt
WHERE pc.ACTUAL_PERIOD_TYPE = pt.PERIOD_TYPE;

Because the table is a hub, it is also useful as a lookup when validating values loaded into interfaces — confirming that a given PERIOD_TYPE code exists and is active before inserting into PAY_CALENDARS or PER_TIME_PERIOD_SETS. Reporting scenarios include frequency distribution analysis of calendars and payrolls, and cross-referencing budget commitment elements by their default element frequency.

Related Objects

Multiple significant tables reference PER_TIME_PERIOD_TYPES through their foreign keys, confirming its hub role. The most notable dependents are:

• PAY_CALENDARS — via ACTUAL_PERIOD_TYPE; defines the period type of each payroll calendar.
• PAY_ALL_PAYROLLS_F — via PERIOD_TYPE; records the payroll's processing frequency.
• PAY_ELE_PAYROLL_FREQ_RULES — via RESET_PERIOD_TYPE; governs element frequency reset behavior.
• PER_TIME_PERIOD_SETS — via PERIOD_TYPE; groups period types for calendar and budget use.
• PER_COBRA_COV_ENROLLMENTS — via PERIOD_TYPE; links COBRA coverage enrollment frequency.
• PQH_BDGT_CMMTMNT_ELMNTS — via DFLT_ELMNT_FREQUENCY; the HR budget commitment element default frequency.

These relationships establish PER_TIME_PERIOD_TYPES as a foundational reference table whose values propagate consistently across payroll, benefits, and budgeting configuration.