Search Results number_per_fiscal_year

Overview

OKL_GL_PERIOD_TYPES_UV is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL – Leasing and Finance Management module. The view exposes accounting calendar period type information sourced from the Oracle General Ledger period type definitions, presented in a form that is directly usable by Oracle Lease Management (OLM) processing and reporting logic. Its status is VALID and it is documented as an ETRM reference object in both EBS 12.1.1 and 12.2.2.

The view is a thin transformation layer: it selects a small set of columns from GL_PERIOD_TYPES and applies a lookup translation to derive a human-readable period set name. This makes it the standard access point for lease-related programs that need to resolve the fiscal calendar structure—most notably the number of accounting periods defined per fiscal year—without querying the GL base table directly.

The presence of the column NUMBER_PER_FISCAL_YEAR in the view is significant for users searching that term. It is passed through unchanged from GL_PERIOD_TYPES and represents the count of periods defined for each fiscal year within a given accounting period type.

Underlying Base Objects

The documented base objects referenced by OKL_GL_PERIOD_TYPES_UV are:

• GL_PERIOD_TYPES (SYNONYM) – the primary source object. In the APPS schema this is a synonym resolving to the General Ledger period type definition table. It supplies the period type code, the year type name, the number of fiscal periods per year, and the description.
• OKL_ACCOUNTING_UTIL (PACKAGE) – an OKL accounting utility package whose function GET_LOOKUP_MEANING is invoked in the view definition to translate the YEAR_TYPE_IN_NAME value into a descriptive period set name.

The view text is:

SELECT USER_PERIOD_TYPE PERIOD_TYPE, OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING('YEAR_TYPE_IN_NAME', YEAR_TYPE_IN_NAME, 101, 101) PERIOD_SET_NAME, NUMBER_PER_FISCAL_YEAR, DESCRIPTION FROM GL_PERIOD_TYPES

Because the definition joins to a PL/SQL function rather than a second table, the view introduces no additional row cardinality: one row in GL_PERIOD_TYPES yields exactly one row in the view. The lookup call adds a translation step, so the view is dependent on the OKL_ACCOUNTING_UTIL package being valid and compiled in the APPS schema.

Key Columns

• PERIOD_TYPE – the accounting period type identifier, aliased from USER_PERIOD_TYPE in GL_PERIOD_TYPES. It is the key used throughout GL and OKL to identify a specific calendar definition (for example, a monthly or weekly calendar).
• PERIOD_SET_NAME – the result of the GET_LOOKUP_MEANING call on YEAR_TYPE_IN_NAME, parameterized with 101, 101. This presents the period set as a readable meaning rather than the raw code.
• NUMBER_PER_FISCAL_YEAR – the number of accounting periods defined per fiscal year for the period type. This is the column most frequently referenced when reconciling lease schedules, depreciation, or revenue recognition against the fiscal calendar.
• DESCRIPTION – the descriptive text maintained on the GL period type definition.

Common Use Cases and Queries

Typical uses include validating that a lease accounting calendar has the expected number of periods, driving period-count calculations in lease amortization, and presenting period type information in OLM setup or diagnostic reports.

Listing all period types with their fiscal period counts:

SELECT period_type, period_set_name, number_per_fiscal_year, description FROM apps.okl_gl_period_types_uv ORDER BY period_type;

Retrieving the fiscal period count for a specific period type:

SELECT period_set_name, number_per_fiscal_year FROM apps.okl_gl_period_types_uv WHERE period_type = :p_period_type;

Because the view is a simple projection over GL_PERIOD_TYPES with no filtering predicates, it returns every period type defined in the ledger configuration; callers are expected to supply their own WHERE clause when a single calendar is required.