Search Results allowable_funding_level

Overview

APPS.OKE_PROJECTS_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as OKE.OKE_PROJECTS_V with a status of VALID. It belongs to the Oracle Project Contracts (OKE) module and provides a denormalized, form-oriented projection of project header information. The view consolidates core attributes from the Oracle Projects foundation — project identity, descriptive fields, scheduling dates, owning organization, project type, and status — together with the funding attributes that control how a project is funded. Because it is a supplementary view intended to simplify Oracle Forms coding, Oracle explicitly warns that it should not be used as a query or DML target for custom development, since its definition may change dramatically between minor or major releases.

For the search term allowable_funding_level, this view is significant because it exposes both ALLOWABLE_FUNDING_LEVEL_CODE and the decoded ALLOWABLE_FUNDING_LEVEL, along with the related PROJECT_LEVEL_FUNDING_FLAG. These columns describe the funding control option configured against the project type and the current baselined funding level for the project.

Underlying Base Objects

The documented base objects underlying OKE_PROJECTS_V are HR_GENERAL (PACKAGE), HR_ORGANIZATION_UNITS (VIEW), HR_SECURITY (PACKAGE), PA_LOOKUPS (VIEW), PA_PROJECTS_ALL (SYNONYM), PA_PROJECT_STATUSES (SYNONYM), and PA_PROJECT_TYPES_ALL (SYNONYM).

• PA_PROJECTS_ALL supplies the primary project rows: project identifier, number, name, description, dates, carrying-out organization, project type, and status code.
• PA_PROJECT_STATUSES provides the decoded status name (PROJECT_STATUS_NAME) corresponding to the internal PROJECT_STATUS_CODE.
• PA_PROJECT_TYPES_ALL provides project type classification and the funding-control configuration from which the allowable funding level is derived.
• PA_LOOKUPS resolves internal codes such as ALLOWABLE_FUNDING_LEVEL_CODE into the descriptive ALLOWABLE_FUNDING_LEVEL value.
• HR_ORGANIZATION_UNITS supplies the carrying-out organization name.
• HR_SECURITY and HR_GENERAL are the HR security and utility packages used to enforce organization-level access, ensuring a user only sees projects belonging to organizations within their security profile.

Key Columns

• ROW_ID — database-generated row identifier (ROWID) for the row.
• PROJECT_ID — system-generated unique identifier of the project.
• PROJECT_NUMBER / NAME / DESCRIPTION — the project's user-facing number, name, and description.
• START_DATE / COMPLETION_DATE — the date the project becomes effective and the scheduled completion date.
• CARRYING_OUT_ORGANIZATION_ID / ORGANIZATION_NAME — the organization responsible for the project work and its name.
• PROJECT_TYPE / PROJECT_TYPE_CLASS_CODE — the project type and its classification.
• PROJECT_STATUS_CODE / PROJECT_STATUS_NAME — the internal status code and its displayed name.
• ALLOWABLE_FUNDING_LEVEL_CODE — internal code indicating the option controlling the level of funding based on project type.
• ALLOWABLE_FUNDING_LEVEL — the current allowable project funding level (decoded, e.g. project, top task, or task level).
• PROJECT_LEVEL_FUNDING_FLAG — flag indicating the existing baselined project funding level.

Common Use Cases and Queries

The view is most often used for reporting and integration reads that need project header attributes together with funding-level configuration, without joining the Projects base tables manually. Typical scenarios include funding-control validation, organization-scoped project listings, and status reporting. Because Oracle discourages direct use of supplementary views, production queries should preferably be redirected to the documented base tables (PA_PROJECTS_ALL, PA_PROJECT_TYPES_ALL, PA_LOOKUPS).

A representative query retrieving funding level for active projects is:

• SELECT p.project_number, p.name, p.project_status_name, p.allowable_funding_level_code, p.allowable_funding_level, p.project_level_funding_flag FROM apps.oke_projects_v p WHERE p.project_status_name = 'Active' ORDER BY p.project_number;

To filter on a specific funding level:

• SELECT project_id, project_number, name, allowable_funding_level FROM apps.oke_projects_v WHERE allowable_funding_level_code = :funding_code;

Additional reading of the ALLOWABLE_FUNDING_LEVEL column should always be interpreted together with PROJECT_LEVEL_FUNDING_FLAG, since the flag records whether a funding level has already been baselined for the project.