Results for “project_level_funding_flag”

50+ results




Overview
Explore in AI Chat

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

Overview

OKE_PROJECTS_V is a validity-restricted view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKE – Project Contracts product family. Its documented purpose is to expose a "valid project listing," meaning the view returns projects drawn from the Projects foundation and joins them to the status, project type, organization, and lookup definitions necessary for downstream contracts processing and reporting. Rather than reading the underlying Projects tables directly, the view consolidates project attributes into a single row per project, providing a stable, denormalized projection suitable for forms, concurrent programs, and integration queries.

The view is present and VALID in both 12.1.1 and 12.2.2. Because it exposes PROJECT_ID, PROJECT_NUMBER, PROJECT_TYPE_CLASS_CODE, PROJECT_STATUS_CODE, and related attributes, it is commonly used in Project Contracts flows where only projects in an allowable state should be selectable.

Underlying Base Objects

The documented referenced base objects are PA_PROJECTS_ALL, PA_PROJECT_STATUSES, PA_PROJECT_TYPES_ALL, PA_LOOKUPS, HR_ORGANIZATION_UNITS, and the HR packages HR_GENERAL and HR_SECURITY. The view text confirms these relationships through explicit joins.

  • PA_PROJECTS_ALL (aliased P) is the driving table, supplying PROJECT_ID, SEGMENT1, NAME, DESCRIPTION, dates, carrying-out organization, project type, and status code.
  • PA_PROJECT_STATUSES (aliased S) supplies PROJECT_STATUS_NAME, restricted to STATUS_TYPE = 'PROJECT'.
  • PA_PROJECT_TYPES_ALL (aliased T) supplies PROJECT_TYPE_CLASS_CODE and ALLOWABLE_FUNDING_LEVEL_CODE, joined on PROJECT_TYPE and matched ORG_ID via NVL(..., -999).
  • HR_ORGANIZATION_UNITS (aliased O) supplies the carrying-out ORGANIZATION_NAME.
  • PA_LOOKUPS (aliased L and L2, outer-joined) resolves the ALLOWABLE_FUNDING_LEVEL meaning under LOOKUP_TYPE = 'ALLOWABLE FUNDING LEVEL'.
  • HR_GENERAL and HR_SECURITY provide organization security, ensuring the listing respects the operating unit context.

Key Columns

  • PROJECT_ID / PROJECT_NUMBER / NAME / DESCRIPTION – core project identity attributes.
  • START_DATE / COMPLETION_DATE – project schedule boundaries.
  • CARRYING_OUT_ORGANIZATION_ID / ORGANIZATION_NAME – owning organization and its descriptive name.
  • PROJECT_TYPE / PROJECT_TYPE_CLASS_CODE – type and its classification, notably 'CONTRACT'.
  • PROJECT_STATUS_CODE / PROJECT_STATUS_NAME – state and readable status.
  • ALLOWABLE_FUNDING_LEVEL_CODE – the funding level code carried on the project type; only surfaced for class 'CONTRACT'.
  • ALLOWABLE_FUNDING_LEVEL / PROJECT_LEVEL_FUNDING_FLAG – derived meaning, resolved from PA_LOOKUPS by the flag ('Y'→'P', 'N'→'T').

Common Use Cases and Queries

The view is typically queried to populate selection lists for contract funding, validate project eligibility, and report on project type/status. Because the search term was allowable_funding_level_code, a representative query filters or displays that attribute:

  • List contract projects allowed at a given funding level: SELECT PROJECT_NUMBER, NAME, ALLOWABLE_FUNDING_LEVEL_CODE FROM OKE_PROJECTS_V WHERE PROJECT_TYPE_CLASS_CODE = 'CONTRACT' AND ALLOWABLE_FUNDING_LEVEL_CODE = :p_level;
  • Show project funding configuration: SELECT PROJECT_NUMBER, PROJECT_TYPE, ALLOWABLE_FUNDING_LEVEL, PROJECT_LEVEL_FUNDING_FLAG FROM OKE_PROJECTS_V WHERE PROJECT_ID = :p_id;
  • Filter active projects for a picker: SELECT PROJECT_ID, PROJECT_NUMBER, NAME FROM OKE_PROJECTS_V WHERE PROJECT_STATUS_NAME = 'Approved';
  • Organizational reporting: SELECT ORGANIZATION_NAME, COUNT(*) FROM OKE_PROJECTS_V GROUP BY ORGANIZATION_NAME;

All queries benefit from the view's pre-built joins, avoiding direct manipulation of PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, and PA_LOOKUPS.