Search Results charges_allowed_flag




Overview
Explore in AI Chat

Overview

APPS.PA_PROJECTS_ALL_BASIC_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under application design data as PA.PA_PROJECTS_ALL_BASIC_V with a VALID status in both 12.1.1 and 12.2.2. Its stated purpose, as documented in the ETRM metadata, is to simplify forms coding by presenting a consolidated, denormalized projection of project header information together with derived attributes such as the carrying-out organization's operating unit and the project function currency and rate attributes. The view is a supplementary view; Oracle explicitly warns that it should not be queried or altered for data-maintenance purposes because its definition may change dramatically in subsequent minor or major releases.

For consultants searching on CHARGES_ALLOWED_FLAG, this view is significant because it exposes that column directly, allowing chargeability to be evaluated alongside project status, project type, currency, and organization context without joining to PA_PROJECTS_ALL or PA_PROJECT_TYPES_ALL manually.

Underlying Base Objects

The documented dependency list for the view includes the following objects: FND_PROFILE (package), HR_ALL_ORGANIZATION_UNITS (synonym), PA_CROSS_BUSINESS_GRP (package), PA_IMPLEMENTATIONS_ALL (synonym), PA_PROJECTS_ALL (synonym), PA_PROJECT_TYPES_ALL (synonym), PA_PROJECT_UTILS (package), and PA_SECURITY (package).

  • PA_PROJECTS_ALL supplies the core project header rows, including project number, name, description, status code, start and completion dates, and the chargeability indicator.
  • PA_PROJECT_TYPES_ALL supplies the project type classification (PROJECT_TYPE_CLASS_CODE) required to resolve chargeability rules by project class.
  • HR_ALL_ORGANIZATION_UNITS supplies the operating unit and organization context used in the CARRYING_OUT_ORGANIZATION_ID and OPERATING_UNIT columns.
  • PA_IMPLEMENTATIONS_ALL and PA_CROSS_BUSINESS_GRP provide the implementation-level and business-group control settings that govern cross-charge and multi-organization behavior.
  • FND_PROFILE, PA_PROJECT_UTILS, and PA_SECURITY supply profile-option resolution, currency and rate derivation, and row-level security enforcement.

The view therefore inherits security enforcement from PA_SECURITY; not every project row in PA_PROJECTS_ALL will necessarily be visible to a given user.

Key Columns

Common Use Cases and Queries

The most frequent use is validating whether a project currently accepts charges before feeding it to interfaces that create expenditure, requisitions, or labor costs. Because the view is unsupported for maintenance, queries should be read-only.

Example: retrieve project identity and chargeability for active projects in an operating unit.

SELECT project_id, project_number, project_name,
       project_status_code, project_type_class_code,
       charges_allowed_flag
FROM   apps.pa_projects_all_basic_v
WHERE  org_id = :p_org_id
AND    project_status_code = 'APPROVED';

The view is also useful in project setup validation reports and in reconciliations that compare chargeability across project types:

SELECT project_type_class_code, charges_allowed_flag, COUNT(*)
FROM   apps.pa_projects_all_basic_v
GROUP BY project_type_class_code, charges_allowed_flag;

Because it leverages PA_SECURITY and FND_PROFILE, the view honors the responsibility-level profile and security context of the invoking user, making it appropriate for forms-driven and inquiry-only reporting where full PA table joins would otherwise be required.