Search Results revenue_category_code




Overview
Explore in AI Chat

Overview

APPS.PA_REVENUE_CATEGORIES_RES_V is a resource-listing view within the Oracle E-Business Suite Projects (PA) module. It exposes revenue categories as selectable resources, presenting each row as a combination of a revenue category code, its descriptive name, and two derived indicator values that describe how the category behaves in relation to labor tracking. The view is one of a family of "resource" views built on top of the base revenue category definition and the central resource-resolution package, PA_GET_RESOURCE.

Its role is to supply LOV (list of values) and validation sources for forms and concurrent programs that require revenue categories to be presented in a resource-oriented format. Because it carries the tracked-as-labor and unit-of-measure semantics alongside each category, consumers can filter or branch behaviour based on whether a revenue category is associated with labor expenditure types without querying the expenditure type views themselves. The view is documented as Oracle proprietary and confidential, owned by the APPS schema, and is available in both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over three documented objects: PA_REVENUE_CATEGORIES_V (VIEW), PA_EXPENDITURE_TYPES_RES_V (VIEW), and the package PA_GET_RESOURCE. PA_REVENUE_CATEGORIES_V supplies the core revenue category rows, including REVENUE_CATEGORY_CODE, REVENUE_CATEGORY_M, START_DATE_ACTIVE, and END_DATE_ACTIVE. PA_GET_RESOURCE is referenced for its INCLUDE_INACTIVE_RESOURCES setting, which determines whether the date predicate is evaluated against the category's own start date or against the current system date. PA_EXPENDITURE_TYPES_RES_V is queried in a correlated EXISTS/NOT EXISTS subquery to test whether an expenditure type with TRACK_AS_LABOR_FLAG = 'Y' shares the same revenue category code.

The view body is a UNION ALL of two branches. The first branch selects categories that are not linked to a labor-tracked expenditure type and labels them as not labor-tracked. The second branch selects categories that are linked to a labor-tracked expenditure type and labels them as labor-tracked with a unit of measure of HOURS. Both branches apply the same date-effectiveness predicate, ensuring consistent filtering across the union.

Key Columns

  • REVENUE_CATEGORY_CODE — the unique identifier of the revenue category, drawn directly from PA_REVENUE_CATEGORIES_V. This is the column most commonly searched and joined against.
  • REVENUE_CATEGORY_M — the descriptive name of the revenue category as maintained in the base view.
  • Tracked-as-labor indicator — a hard-coded flag ('N' in the first branch, 'Y' in the second) reflecting whether a labor-tracked expenditure type exists for the category.
  • Unit of measure — NULL for non-labor categories and the literal 'HOURS' for labor-tracked categories.
  • Additional flag — a further hard-coded indicator ('N' or 'Y') aligned to the union branch.

Because the last three columns are derived literals rather than stored attributes, they reflect the view's classification logic at query time rather than persisted data.

Common Use Cases and Queries

Typical uses include populating revenue category LOVs on project and billing forms, driving validation logic in revenue generation concurrent programs, and reporting on which revenue categories are labor-bearing versus non-labor. A representative query returning all active resources is:

SELECT revenue_category_code, revenue_category_m FROM apps.pa_revenue_categories_res_v ORDER BY revenue_category_code;

To isolate labor-tracked categories only:

SELECT revenue_category_code, revenue_category_m FROM apps.pa_revenue_categories_res_v WHERE <labor_indicator_column> = 'Y';

Because the view honours PA_GET_RESOURCE.INCLUDE_INACTIVE_RESOURCES, administrators should note that results depend on that package-level setting: when it is 'Y', the date predicate uses each category's own start date and inactive categories are included; otherwise TRUNC(SYSDATE) is applied, restricting output to currently effective categories. Queries joining this view to PA_EXPENDITURE_TYPES or PA_REVENUE_CATEGORIES should be aware that the union may return one row per category, with the branch determined by labor association.