Search Results revenue_category_code




Overview
Explore in AI Chat

Overview

PA_REVENUE_CATEGORIES_RES_V is an Oracle EBS Projects (PA) view owned by the APPS schema. It is documented in the ETRM repository with the description "10Sc only," indicating that its functional scope is limited to the revenue category resolution logic associated with labor-tracked resource treatment. Despite its origins, the object remains VALID in the ETRM 12.2.2 reference and is still resolvable within an Oracle EBS 12.1.1 / 12.2.2 environment.

The view presents a normalized list of revenue categories, one row per category, and augments each row with flags that describe whether the category is treated as a labor resource and whether quantities should be rolled up. Because the project accounting module drives revenue generation, billing, and cost-to-revenue mapping, applications and interfaces that require a certified list of valid revenue categories—along with their labor behavior—can consume this view rather than re-implementing the join and date-filter logic themselves.

In practice, the view primarily serves reporting, validation (LOV) queries, and integration extracts where a caller needs to know whether a given revenue_category_code behaves as labor. It is a resolution view rather than a transactional one; it does not store revenue or billing amounts.

Underlying Base Objects

The view is defined over three documented objects:

The active-date logic is controlled by DECODE(PA_GET_RESOURCE.INCLUDE_INACTIVE_RESOURCES, 'Y', START_DATE_ACTIVE, TRUNC(SYSDATE)) nested between START_DATE_ACTIVE and NVL(END_DATE_ACTIVE, TRUNC(SYSDATE)). When the global is 'Y', the effective comparison date becomes the row's own start date, allowing expired categories to surface; otherwise the current system date is used and only currently active categories are returned.

The view body is a UNION ALL of two branches. The first returns non-labor categories with TRACK_AS_LABOR_FLAG = 'N', UNIT_OF_MEASURE = NULL, and ROLLUP_QUANTITY_FLAG = 'N'. The second returns labor categories with 'Y', unit of measure 'HOURS', and rollup flag 'Y'.

Key Columns

  • REVENUE_CATEGORY_CODE – the unique business key of the revenue category. This is the column most commonly searched by users (e.g., searching "revenue_category_code") and is used to join to project, billing, and expenditure data.
  • DESCRIPTION – derived from REVENUE_CATEGORY_M in PA_REVENUE_CATEGORIES_V; the descriptive name of the category.
  • TRACK_AS_LABOR_FLAG – 'Y' when the category maps to a labor expense type; 'N' otherwise. This flag directly determines the unit of measure and rollup behavior assigned in the same branch.
  • UNIT_OF_MEASURE – 'HOURS' for labor categories, NULL for others.
  • ROLLUP_QUANTITY_FLAG – 'Y' for labor categories (quantities are rolled up, e.g., hours), 'N' otherwise.

Common Use Cases and Queries

Typical uses include populating revenue category LOVs, validating user-supplied category codes before loading billing or revenue events, and extracting a labor/non-labor classification for downstream processing.

Retrieve all currently active revenue categories:

SELECT revenue_category_code,
       description,
       track_as_labor_flag,
       unit_of_measure,
       rollup_quantity_flag
  FROM apps.pa_revenue_categories_res_v
 ORDER BY revenue_category_code;

Isolate labor-tracked categories only:

SELECT revenue_category_code, description
  FROM apps.pa_revenue_categories_res_v
 WHERE track_as_labor_flag = 'Y';

Resolve a specific category code, which is the most frequent pattern given user searches on revenue_category_code:

SELECT revenue_category_code,
       description,
       track_as_labor_flag
  FROM apps.pa_revenue_categories_res_v
 WHERE revenue_category_code = :p_category_code;

Because the code relies on the PA_GET_RESOURCE package global, callers should not assume a fixed active-date scope; the returned row set changes depending on the session value of INCLUDE_INACTIVE_RESOURCES. For deterministic reporting, wrap the query with an explicit filter on track_as_labor_flag or supply the global value in the calling environment.