Results for “fiscal_year”

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

Overview

PMIBV_INVCAL_LOV_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the Process Manufacturing Intelligence (PMI) product family, which is documented as obsolete in Release 12.1.1 and 12.2.2. The view functions as a List of Values (LOV) source for inventory calendars, exposing a minimal projection of the inventory calendar header data so that concurrent programs, forms, and reporting components within the PMI module can present a selection list of valid organization code, fiscal year, and calendar description combinations.

The object name and its LOV designation indicate that it was designed primarily to drive value-selection widgets rather than to serve as a general-purpose reporting view. Because PMI is obsolete, the view is retained in the APPS schema primarily for backward compatibility with any remaining customizations, historical reports, or interfaces that reference it. It carries no business logic beyond a simple column projection and the WITH READ ONLY clause, which guarantees that no DML can be issued against it.

Underlying Base Objects

The view is defined over a single object: IC_CLDR_HDR. In the documented metadata, IC_CLDR_HDR is referenced through a SYNONYM, which resolves to the underlying inventory calendar header table in the Process Manufacturing / Oracle Inventory schema set. IC_CLDR_HDR stores the header-level definition of inventory calendars, including the organization that owns the calendar, the fiscal year to which it applies, and descriptive text for the calendar.

The relationship is strictly one-to-one at the row level. PMIBV_INVCAL_LOV_V performs a vertical slice of IC_CLDR_HDR, returning only three of the header table's columns and applying no filtering, joins, or aggregation in the documented view text. Any WHERE clause or LOV validation logic is expected to be supplied by the calling form or program rather than by the view itself.

Key Columns

• ORGN_CODE — The organization code that identifies the inventory organization owning the calendar. In LOV usage this is the primary discriminator that restricts calendar choices to a specific organization.
• FISCAL_YEAR — The fiscal year associated with the calendar header record. Combined with ORGN_CODE, it typically forms the unique business key used to select a specific calendar instance.
• CALENDAR_DESC — The descriptive name of the inventory calendar, presented to the user in the LOV popup as the human-readable selection label.

Since the view exposes no surrogate key or ID column, consumers must rely on the ORGN_CODE and FISCAL_YEAR combination to uniquely identify a calendar row. This is consistent with an LOV pattern where the returned values are used directly as query predicates rather than as foreign keys to a separate lookup.

Common Use Cases and Queries

The principal use case is populating an LOV in a PMI-related form or concurrent program where the user must choose an inventory calendar for a given organization and fiscal year. A typical query retrieves the available calendars for a specific organization:

• SELECT ORGN_CODE, FISCAL_YEAR, CALENDAR_DESC FROM APPS.PMIBV_INVCAL_LOV_V WHERE ORGN_CODE = :orgn_code ORDER BY FISCAL_YEAR;
• SELECT ORGN_CODE, FISCAL_YEAR, CALENDAR_DESC FROM APPS.PMIBV_INVCAL_LOV_V WHERE ORGN_CODE = :orgn_code AND FISCAL_YEAR = :fiscal_year;
• SELECT DISTINCT FISCAL_YEAR FROM APPS.PMIBV_INVCAL_LOV_V WHERE ORGN_CODE = :orgn_code ORDER BY FISCAL_YEAR;

Because the view is read-only and unfiltered, organizations adopting it in custom reports should add their own predicates to avoid full-table scans of IC_CLDR_HDR. Given the obsolete status of the PMI product, new development should generally query IC_CLDR_HDR directly or use supported Inventory calendar APIs; however, PMIBV_INVCAL_LOV_V remains valid and usable for maintaining continuity with existing PMI-based customizations.