Search Results year_type_in_name




Overview
Explore in AI Chat

Overview

OKL_GL_PERIOD_TYPES_UV is a reporting view owned by the APPS schema in Oracle E-Business Suite, documented for releases 12.1.1 and 12.2.2. It exposes a curated projection of the General Ledger period type definition, presenting accounting calendar period types in a form suited to Oracle Lease and Finance Management (OKL/ETRM) processing and to downstream reporting and integration consumers. Rather than publishing the raw GL_PERIOD_TYPES row, the view renames the primary key column and resolves a coded attribute—YEAR_TYPE_IN_NAME—into a human-readable period set name. This translation is performed by a call to the OKL_ACCOUNTING_UTIL package, which is an ETRM-owned utility rather than a core General Ledger program. The view is therefore a lightweight, read-only integration surface: it bridges the seeded GL period type repository and the leasing application's lookup conventions without duplicating the underlying data.

Underlying Base Objects

The view is defined over two documented referenced objects:

  • GL_PERIOD_TYPES (SYNONYM) — the base General Ledger table that stores period type definitions. The APPS synonym resolves to the GL schema object. The view selects USER_PERIOD_TYPE, YEAR_TYPE_IN_NAME, NUMBER_PER_FISCAL_YEAR, and DESCRIPTION from this source without filtering or aggregation.
  • OKL_ACCOUNTING_UTIL (PACKAGE) — the ETRM accounting utility package. Its GET_LOOKUP_MEANING function is invoked once per row in the SELECT list to convert the YEAR_TYPE_IN_NAME lookup code into a display value.

Because the view inherits the GL synonym's privileges and calls an ETRM package, access is governed through APPS. There is no join, UNION, or subquery: the relationship is strictly one-to-one between a source GL_PERIOD_TYPES row and a view row.

Key Columns

  • PERIOD_TYPE — aliased from USER_PERIOD_TYPE, this is the user-facing identifier of the period type (for example, a monthly or weekly calendar period type) and serves as the effective key for the view.
  • PERIOD_SET_NAME — derived from YEAR_TYPE_IN_NAME via OKL_ACCOUNTING_UTIL.GET_LOOKUP_MEANING('YEAR_TYPE_IN_NAME', YEAR_TYPE_IN_NAME, 101, 101). The literal 101 arguments identify the lookup context used by the utility. This column returns the decoded meaning of the year-type lookup rather than its stored code.
  • NUMBER_PER_FISCAL_YEAR — the count of periods defined within each fiscal year for the period type, used for validation and calendar arithmetic.
  • DESCRIPTION — the free-text description attached to the period type in General Ledger.

Common Use Cases and Queries

The view is typically used to validate or display accounting calendar period types within ETRM configuration and reporting. A representative query listing all period types follows:

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

Because the second column depends on the YEAR_TYPE_IN_NAME lookup, users searching on that term are usually verifying whether the lookup has been seeded or personalised correctly: an unresolved or missing meaning indicates a lookup configuration gap in the 101 context. Typical scenarios include populating LOVs and report parameters that constrain period selection, reconciling the number of fiscal periods against depreciation and accrual schedules, and feeding period type metadata into lease accounting interfaces. The view should be treated as read-only; modifications belong to GL_PERIOD_TYPES and the Year Type lookup, not to the view itself.