Search Results project_bil_rate_type




Overview
Explore in AI Chat

Overview

PA_PROJ_FUND_VALID_V is a Projects (PA) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, security-filtered list of projects that are eligible for funding or billing validation activities, exposing both project-level attributes and the currency/rate configuration that governs multi-currency billing. The view is a denormalized join of project, project type, customer, and lookup data, combined with conversion type references, and it is intended for LOV, validation, and integration use rather than for transactional updates.

Because the view applies PA_SECURITY.ALLOW_QUERY and PA_SECURITY.ALLOW_UPDATE predicates, only projects the current user is permitted to query and update are returned. Projects flagged as templates are exempted from the security check. Projects whose status is closed (via PA_PROJECT_STUS_UTILS.IS_PROJECT_STATUS_CLOSED) are excluded entirely.

Underlying Base Objects

The view is defined over the following documented base objects:

  • PA_PROJECTS_ALL (via the PA_PROJECTS synonym) — primary project records, including template flag, multi-currency billing flag, org, and rate attributes.
  • PA_PROJECT_TYPES_ALL (via PA_PROJECT_TYPES synonym) — project type attributes such as allowable funding level and class code.
  • PA_PROJECT_CUSTOMERS — customer association per project, including bill split.
  • PA_LOOKUPS — resolves the allowable funding level code to its meaning.
  • PA_CONVERSION_TYPES_V (aliased C and C1) — conversion type definitions used for project and project functional billing rate type names.
  • PA_SECURITY, PA_PROJECT_STUS_UTILS, and PA_MULTI_CURRENCY_BILLING packages — invoked for security filtering, closed-project exclusion, and cross-operating-unit funding logic respectively.

The joins require project type match on PROJECT_TYPE and ORG_ID; an NVL comparison on ORG_ID allows records without an org to be matched.

Key Columns

Common Use Cases and Queries

Typical uses include validation LOVs during funding entry, resolving project currency and billing rate context, and reporting on open, fundable projects by operating unit.

Basic listing by currency:

  • SELECT PROJECT_ID, NAME, SEGMENT1, PROJECT_CURRENCY_CODE, PROJFUNC_CURRENCY_CODE FROM PA_PROJ_FUND_VALID_V WHERE PROJECT_CURRENCY_CODE = :p_currency;

Filtering by funding level and org:

  • SELECT PROJECT_ID, SEGMENT1, MEANING, ORG_ID FROM PA_PROJ_FUND_VALID_V WHERE ALLOWABLE_FUNDING_LEVEL_CODE = :p_level AND ORG_ID = :p_org_id;

Identifying multi-currency projects:

  • SELECT PROJECT_ID, NAME, MULTI_CURRENCY_BILLING_FLAG FROM PA_PROJ_FUND_VALID_V WHERE MULTI_CURRENCY_BILLING_FLAG = 'Y';

Because security predicates are embedded, no additional project-security filter is required; results are implicitly restricted to the querying user's authorized projects.