Results for “gl_period_types_v”

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

Overview

GL_PERIOD_TYPES_V is an APPS-owned view in the Oracle E-Business Suite General Ledger (GL) module. Its documentation status is recorded as VALID, and its description in the ETRM metadata is qualified as "10SC ONLY," indicating that the object is documented and supported for a restricted, release-specific context rather than as a general-purpose GL interface. Within that scope, the view presents a read-only, denormalized projection of accounting period type definitions maintained by General Ledger. It exposes the identifying attributes of each period type — including the user-facing period type name, the internal period type code, the year-type designation embedded in the period type name, the number of accounting periods per fiscal year, and the descriptive text.

Because period types govern the calendar structure used by the Accounting Calendar, they are fundamental reference data. Reporting and integration components that must translate between the internal period type identifier and a human-readable label, or that must validate the number of periods in a fiscal year, can consume this view instead of querying the base table directly. The view therefore serves as a lightweight, curated access point for period-type reference data rather than as a transactional or balance-bearing object.

Underlying Base Objects

The view is defined over a single referenced base object: the synonym GL_PERIOD_TYPES, which resolves to the underlying General Ledger period types table. The definition is a straightforward selection with no joins, filters, or aggregation, so each row in the view corresponds one-to-one with a row in the base period type table. No other tables, views, or lookup objects are documented as inputs.

Because the view does not join to GL_CALENDARS or any period-naming table, it does not by itself map period types to specific calendars or to individual accounting periods. Consumers requiring that level of detail must join to the calendar and period entities separately. The absence of a WHERE clause also means that the view returns all defined period types, including any that may be inactive or unused in a given ledger configuration.

Key Columns

• USER_PERIOD_TYPE — The user-defined, display name of the period type. This is the value typically presented to end users and referenced in setups and reports.
• PERIOD_TYPE — The internal period type identifier used within General Ledger to reference the period type programmatically. This is the key used in joins to calendar and period structures.
• YEAR_TYPE_IN_NAME — The year-type designation expressed within the period type naming convention. Because a user searched for this attribute, it is worth noting explicitly: YEAR_TYPE_IN_NAME is not a calendar-year value and should not be confused with a fiscal year number; it reflects the year-type token embedded in the period type definition and is used to distinguish how the annual span is characterized in the period type name.
• NUMBER_PER_FISCAL_YEAR — The count of accounting periods defined within a fiscal year for the period type. Common values are 12 for monthly calendars, 13 for monthly calendars with an adjusting period, and 52 for weekly calendars.
• DESCRIPTION — Free-form descriptive text associated with the period type, provided for documentation and clarity.

Common Use Cases and Queries

Typical scenarios include validating calendar configuration, listing available period types for a setup screen, and resolving a period type code to its user-facing name in reports. A representative query lists all defined period types with their period count:

SELECT user_period_type, period_type, year_type_in_name, number_per_fiscal_year, description FROM apps.gl_period_types_v ORDER BY user_period_type;

To identify monthly and adjusted calendars, the fiscal-year period count can be filtered:

SELECT period_type, user_period_type, number_per_fiscal_year FROM apps.gl_period_types_v WHERE number_per_fiscal_year IN (12, 13);

To resolve a single period type from its internal code, or to report on the year-type designation specifically, the following forms apply:

SELECT user_period_type, description FROM apps.gl_period_types_v WHERE period_type = :p_period_type;

SELECT user_period_type, year_type_in_name, number_per_fiscal_year FROM apps.gl_period_types_v ORDER BY year_type_in_name;

All queries should be issued against the read-only view for reference purposes; period type maintenance itself is performed through the standard General Ledger calendar setup, not through this object.