Results for “start_date_active”

50+ results




Overview
Explore in AI Chat

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

Overview

PA_REVENUE_CATEGORIES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, residing in the Projects (PA) product family. Its documented description in the ETRM repository is "10Sc only," indicating that the object originates from the older 10SC (Oracle Projects) data model lineage and is retained for backward compatibility rather than being a core component of later releases. The view exposes the set of valid revenue category lookup values that Oracle Projects uses to classify project revenue by type.

Functionally, the view serves as a filtered, denormalized window onto the PA_LOOKUPS lookup table. It isolates the single lookup type 'REVENUE CATEGORY' and presents each defined revenue category together with its meaning, description, and effective dating. Because revenue category is a controlled lookup rather than a standalone entity, the view provides a convenient, stable interface for reports, concurrent programs, and integrations that need to enumerate revenue categories without embedding the underlying lookup_type predicate. It is a read-only construct and carries no DML behavior of its own.

Underlying Base Objects

The documented referenced base object is PA_LOOKUPS, itself exposed as a view in the APPS schema. The view text is a straightforward projection with a single filter predicate:

PA_LOOKUPS is the Projects module's lookup repository, storing code/meaning pairs that drive list-of-values behavior across Oracle Projects. PA_REVENUE_CATEGORIES_V therefore inherits the row-level content of PA_LOOKUPS for the revenue category lookup type and adds no joins, aggregations, or derived columns. Any change made to a revenue category lookup in the Projects setup—whether a new code is added or an existing one is end-dated—is immediately reflected through this view, since it is a non-materialized view. Because the view depends on PA_LOOKUPS, its validity and performance characteristics mirror those of the base view, including any multilanguage or translation behavior implemented beneath PA_LOOKUPS.

Key Columns

  • REVENUE_CATEGORY_CODE — The lookup code value for the revenue category. In the view text this is sourced from LOOKUP_CODE; it is the unique identifier used to reference a revenue category in project setup, revenue generation, and reporting logic.
  • REVENUE_CATEGORY_M — The meaning or display name associated with the revenue category code, sourced from MEANING. This is the user-facing label typically shown in list-of-values and report output.
  • DESCRIPTION — Free-text description of the revenue category, sourced from DESCRIPTION, providing additional context beyond the meaning.
  • START_DATE_ACTIVE — The date on which the revenue category becomes active; null indicates no defined start restriction.
  • END_DATE_ACTIVE — The date on which the revenue category becomes inactive; null indicates the category remains open-ended.

The effective date columns allow consumers to filter for currently valid revenue categories by comparing the system date against START_DATE_ACTIVE and END_DATE_ACTIVE.

Common Use Cases and Queries

Typical usage includes revenue category list-of-values generation, project setup validation, and reporting that groups project revenue by category. The following query lists all revenue categories, including those that are end-dated:

  • SELECT revenue_category_code, revenue_category_m, description, start_date_active, end_date_active FROM apps.pa_revenue_categories_v ORDER BY revenue_category_m;

To retrieve only currently active categories as of the current date:

  • SELECT revenue_category_code, revenue_category_m FROM apps.pa_revenue_categories_v WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

Because the underlying object is described as "10SC only," implementations on Oracle EBS 12.1.1 and 12.2.2 should verify the view's presence and behavior in their specific environment and confirm whether newer Projects revenue setup functionality supersedes it. Where the view remains valid, it provides a reliable read-only access path for revenue category reference data without querying PA_LOOKUPS directly.