Results for “active_flag”

8 results




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

Overview

POR_EXP_ORG_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. It is a purpose-built list-of-values (LOV) view that exposes expenditure organizations eligible for selection within iProcurement flows, such as requisition creation and shopping cart entry. The view carries a VALID status across both 12.1.1 and 12.2.2 releases and requires no separate compilation, as it derives its result set entirely from an underlying Projects view at runtime.

The object originated as a new view in iProcurement for the Expenditure Organization, providing a filtered, date-effective presentation of expenditure organizations. Its defining characteristic is that it does not expose all organizations defined in the Projects expenditure hierarchy; it restricts the result set to organizations that are currently active and effective as of the system date. This makes it suitable as a validated LOV source rather than a general-purpose reporting view.

Underlying Base Objects

The view text is a direct projection over PA_ORGANIZATIONS_EXPEND_V, itself a Projects view built on the PA_ORGANIZATIONS and PA_ORGANIZATION_CLASSIFICATIONS tables. The documented 12.2.2 base object list also records HR_GENERAL, HR_SECURITY, and MO_GLOBAL packages. These are not referenced by the view text directly, but are dependencies inherited through PA_ORGANIZATIONS_EXPEND_V.

  • PA_ORGANIZATIONS_EXPEND_V – the immediate parent view supplying ORGANIZATION_ID, BUSINESS_GROUP_ID, NAME, DATE_FROM, DATE_TO, and ACTIVE_FLAG.
  • HR_GENERAL – provides business group and organization-related utility functions used in the parent view chain.
  • HR_SECURITY – enforces Oracle HRMS security profiles, restricting returned organizations to those the querying user is permitted to access.
  • MO_GLOBAL – supplies multi-org (operating unit) context handling.

The relationship is therefore a layered one: POR_EXP_ORG_LOV_V narrows and orders the parent view, while the parent view handles organization classification, security, and multi-org resolution.

Key Columns

  • ORGANIZATION_ID – the unique identifier of the expenditure organization; the primary value returned by the LOV and the value stored on downstream transactions.
  • BUSINESS_GROUP_ID – the business group to which the organization belongs, used for HRMS security and multi-org partitioning.
  • NAME – the display name shown to the user in the LOV and used as the sort key.
  • DATE_FROM – the effective start date of the organization's validity.
  • DATE_TO – the optional end date; a NULL value indicates the organization remains open-ended.
  • ACTIVE_FLAG – the active/inactive indicator; the view returns only rows where this evaluates to 'Y'.

Common Use Cases and Queries

The principal use is as the LOV source for the Expenditure Organization field in iProcurement requisitions. Reporting queries can reuse it to obtain a consistently filtered, date-effective organization list without re-implementing the active and date logic.

SELECT organization_id,
       business_group_id,
       name,
       date_from,
       date_to
FROM   apps.por_exp_org_lov_v
ORDER  BY name;

A lookup by identifier or by business group is equally common:

SELECT organization_id, name
FROM   apps.por_exp_org_lov_v
WHERE  organization_id = :p_org_id;

SELECT organization_id, name
FROM   apps.por_exp_org_lov_v
WHERE  business_group_id = :p_business_group_id
ORDER  BY name;

Because the view applies NVL(ACTIVE_FLAG,'*') = 'Y' and TRUNC(SYSDATE) BETWEEN DATE_FROM AND NVL(DATE_TO, TRUNC(SYSDATE)), results are implicitly constrained to organizations active on the current date. Queries requiring historic or future-dated organizations must therefore target PA_ORGANIZATIONS_EXPEND_V directly instead.

The user search term "pa_organizations_expend_v" corresponds precisely to the immediate parent of this view, confirming that POR_EXP_ORG_LOV_V is best understood as the iProcurement-facing, activity-filtered layer over that Projects view.