Search Results sys_link_end_date_active




Overview
Explore in AI Chat

Overview

POR_EXPENDITURE_LOV_V is a database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ICX – Oracle iProcurement product module. As its name and documented description indicate, the view provides the List of Values (LOV) for Expenditure used within the iProcurement application. In the iProcurement shopping and requisition-entry flows, users are required to select a valid expenditure type when charging costs to a project. Rather than exposing the underlying Project Accounting tables directly, iProcurement presents a curated, filtered list through this view, ensuring that only expenditure types eligible for system linkage are offered to the end user.

The object is documented with a status of VALID in the ETRM repository for both Oracle EBS 12.1.1 and 12.2.2. Its role is primarily one of controlled data exposure: it mediates between the transactional LOV mechanism of the iProcurement user interface and the Project Accounting foundation data, applying date and linkage-function filters at the database layer so that the application tier receives only currently effective, iProcurement-relevant rows.

Underlying Base Objects

According to the documented metadata, POR_EXPENDITURE_LOV_V is defined over a single referenced base object: PA_EXPENDITURE_TYPES_EXPEND_V, itself a view in the APPS schema belonging to the Project Accounting (PA) product. The relationship is one of derivation and filtering. POR_EXPENDITURE_LOV_V does not add columns beyond those projected from its parent; instead it constrains the parent result set using three predicate conditions defined in its view text.

The dual date filters ensure that both the expenditure type itself and its association to iProcurement are active on the query date.

Key Columns

The documented columns exposed by the view are as follows.

  • EXPENDITURE_TYPE — the name of the expenditure type, used as the displayed and stored value in the iProcurement LOV.
  • DESCRIPTION — the descriptive text associated with the expenditure type, typically shown alongside the name to aid user selection.
  • START_DATE_ACTIVE — the start date of the system linkage effective period, propagated from SYS_LINK_START_DATE_ACTIVE in the parent view.
  • END_DATE_ACTIVE — the end date of the system linkage effective period, propagated from SYS_LINK_END_DATE_ACTIVE.

Note that while the WHERE clause references the expenditure type's own active dates (EXPND_TYP_START_DATE_ACTIVE and EXPND_TYP_END_DATE_ACTIVE), those columns are not projected in the documented column list; only the system linkage dates are exposed. This confirms the view's purpose as a selection LOV rather than a full audit listing.

Common Use Cases and Queries

The principal use case is the iProcurement expenditure type LOV, which populates the selection list when a shopper assigns a project expenditure type to a requisition line. Because the view applies all effectiveness filtering internally, applications and reports can query it without re-implementing date logic. A typical query is:

  • SELECT expenditure_type, description FROM apps.por_expenditure_lov_v ORDER BY expenditure_type;
  • SELECT expenditure_type, description FROM apps.por_expenditure_lov_v WHERE UPPER(description) LIKE UPPER(:p_search)||'%';
  • SELECT expenditure_type, start_date_active, end_date_active FROM apps.por_expenditure_lov_v WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE+1);

These queries support validation routines, custom LOV extensions, and diagnostic checks confirming which expenditure types are currently offerable through iProcurement. Any such query should be run as the APPS schema or a user with equivalent privileges.