Search Results period_desc




Overview
Explore in AI Chat

Overview

The Oracle E-Business Suite view APPS.PMIBV_INVCALPERIOD_LOV_V is a list-of-values (LOV) view defined in the APPS schema. It belongs to the PMI — Process Manufacturing Intelligence product family, which Oracle has classified as obsolete in release 12.1.1 and 12.2.2. The view is documented in the ETRM repository with a status of VALID and carries the description "PMI LOV View for Cost Calendar Period."

Its sole purpose is to supply the period selection values presented to users in Process Manufacturing Intelligence forms and concurrent programs. Rather than querying the underlying cost calendar table directly, PMI components reference this view, which projects only the columns relevant to a period LOV. The view is a thin, read-only projection defined with a WITH READ ONLY clause, meaning it cannot be used as the target of DML statements. The most frequently searched column associated with this object is PERIOD_DESC, the human-readable period description that distinguishes one calendar period from another in the LOV display.

Underlying Base Objects

The view is defined over a single referenced object, documented in the ETRM metadata as the synonym IC_CLDR_DTL. In a standard EBS installation this synonym resolves to the cost calendar detail table belonging to the Process Manufacturing / cost management schema. The ETRM view text confirms a straightforward, unjoined projection:

Because the definition contains no joins, aggregations, or filters, the view inherits the row granularity of IC_CLDR_DTL: one row per cost calendar period per organization per fiscal year. The view performs no transformation of the data — it exposes a stable, named interface that insulates PMI list-of-values logic from direct dependencies on the base table.

Key Columns

  • ORGN_CODE — The organization code identifying the inventory or cost organization to which the calendar period belongs. This column is essential for restricting an LOV query to the operating unit or organization context of the current session.
  • FISCAL_YEAR — The fiscal year label for the period, used to scope period selection to a single accounting year.
  • PERIOD — The period number or code within the fiscal year, providing the internal key for the period.
  • PERIOD_DESC — The descriptive name of the period, as returned to the user in the LOV. This is the primary display column and the term most commonly searched against this object.
  • PERIOD_END_DATE — The closing date of the period, which determines which transactions fall within the calendar period boundary.

Together these columns give consumers both the keys needed to bind a period (ORGN_CODE, FISCAL_YEAR, PERIOD) and the display and date attributes needed to render and validate the selection.

Common Use Cases and Queries

The principal use case is populating a period LOV in PMI costing and intelligence screens, and resolving a chosen PERIOD_DESC back to its underlying period identifier. A typical query restricted to one organization and fiscal year is:

  • SELECT period_desc, period, period_end_date FROM apps.pmibv_invcalperiod_lov_v WHERE orgn_code = :orgn_code AND fiscal_year = :fiscal_year ORDER BY period_end_date;

A lookup variant that drives selection from the description rather than presenting a list is equally common:

  • SELECT orgn_code, fiscal_year, period, period_end_date FROM apps.pmibv_invcalperiod_lov_v WHERE period_desc = :period_desc AND orgn_code = :orgn_code;

Because the view is read-only and unindexed beyond the base table's own indexes, queries returning large period ranges should always be filtered by ORGN_CODE and FISCAL_YEAR. Report developers replacing obsolete PMI functionality should treat this view as a compatibility shim over IC_CLDR_DTL and consider querying the base table directly in new development, while existing PMI code continues to resolve through APPS.PMIBV_INVCALPERIOD_LOV_V.