Results for “end_date”

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

Overview

PMIBV_COSTCALPERIOD_LOV_V is an APPS-owned database view in Oracle E-Business Suite, registered in the ETRM repository as a VALID object belonging to the Process Manufacturing Intelligence (PMI) product family. As its name and documented description indicate, it is a List of Values (LOV) view built specifically for Cost Calendar Period selection. In Oracle EBS, LOV views are lightweight, read-only projections that populate the value lists attached to Oracle Forms fields, concurrent program parameters, and OAF-based pages, ensuring that users select only valid cost calendar period combinations rather than typing free-form values. The title "PMI LOV View for Cost Calendar Period" confirms this purpose directly: it supplies the data set from which cost calendar and period values are offered to the user.

Because it is a view rather than a table, PMIBV_COSTCALPERIOD_LOV_V stores no data of its own. It is a query-only construct, and the underlying view text confirms this with an explicit WITH READ ONLY clause, which instructs the optimizer to treat the view as non-updatable and prevents DML through the view entirely.

Underlying Base Objects

The view is defined over a single documented base object: CM_CLDR_DTL, accessed through a SYNONYM in the APPS schema. CM_CLDR_DTL is the cost calendar detail table in the Process Manufacturing (OPM/CM) cost management schema, which holds the individual period rows belonging to each cost calendar. The view performs no joins and applies no WHERE predicate in its documented definition — it is a straight column projection of CM_CLDR_DTL. The documented view text is:

• SELECT CALENDAR_CODE, PERIOD_CODE, PERIOD_DESC, START_DATE, END_DATE FROM CM_CLDR_DTL WITH READ ONLY

Filtering, where required, is delegated to the consuming LOV definition or to caller-supplied predicates rather than being embedded in the view itself. This keeps the view generic and reusable across any cost calendar period lookup scenario.

Key Columns

• CALENDAR_CODE — Identifier of the cost calendar to which the period belongs. This is the primary grouping key for cost calendar periods and is commonly the first segment of an LOV key.
• PERIOD_CODE — The period identifier within the calendar. This is the column that users searched for ("period_code") and is the value most frequently retrieved, displayed, or passed as a parameter by PMI reports and integrations.
• PERIOD_DESC — The descriptive name of the period, typically the human-readable label presented in the LOV list and on report output.
• START_DATE — The effective start date of the period, used for date-range filtering and for determining which period a transaction falls into.
• END_DATE — The effective end date of the period, bounding the period's date window alongside START_DATE.

Common Use Cases and Queries

The most common use is validation and lookup during cost calculation, period-close reporting, and PMI analytical queries where a period code must be resolved to its calendar, description, and date range. Because the view carries both PERIOD_CODE and its date boundaries, it is equally suitable for translating a user-selected period into dates or for mapping a transaction date back to a period.

Example: retrieve all periods for a specific cost calendar, ordered chronologically.

• SELECT calendar_code, period_code, period_desc, start_date, end_date FROM apps.pmibv_costcalperiod_lov_v WHERE calendar_code = :calendar_code ORDER BY start_date;

Example: resolve a period code to its descriptive details and date window.

• SELECT calendar_code, period_desc, start_date, end_date FROM apps.pmibv_costcalperiod_lov_v WHERE period_code = :period_code;

Example: identify the cost period covering a given transaction date.

• SELECT calendar_code, period_code, period_desc FROM apps.pmibv_costcalperiod_lov_v WHERE :transaction_date BETWEEN start_date AND end_date;

Because the view is read-only and unfiltered, these queries should always supply a restricting predicate on CALENDAR_CODE, PERIOD_CODE, or date range to avoid an unbounded scan of the cost calendar detail table.