Search Results pa_projects_all_basic_v

Overview

The APPS.PA_PROJECTS_ALL_BASIC_V view is a Projects (PA) module security and lookup construct delivered in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to present the set of projects against which a user is permitted to search, primarily to drive List of Values (LOV) pickers and validation logic inside Projects subledgers and other calling modules. It is a "basic" view in the sense that it exposes a lightweight, flattened projection of project header data rather than the full PA_PROJECTS_ALL column set, making it efficient for high-frequency LOV queries and subledger entry screens.

Two behaviors distinguish this view from the base project table. First, it excludes project templates via the predicate NVL(P.TEMPLATE_FLAG,'N') <> 'Y', so template projects never appear in lookup results. Second, it enforces row-level Projects security by invoking PA_SECURITY.ALLOW_QUERY(P.PROJECT_ID), returning only projects the current user is authorized to query. Cross-business-group access is governed through PA_CROSS_BUSINESS_GRP, so the view respects operating unit and business group boundaries configured in the environment.

Underlying Base Objects

PA_PROJECTS_ALL_BASIC_V is defined over the following documented objects:

• PA_PROJECTS_ALL (synonym) — the primary source of project header attributes such as PROJECT_ID, SEGMENT1, NAME, and status.
• PA_PROJECT_TYPES_ALL (synonym) — joined on PROJECT_TYPE and ORG_ID to supply PROJECT_TYPE_CLASS_CODE and CC_PRVDR_FLAG; the join also filters out the internal AWARD_PROJECT type.
• PA_IMPLEMENTATIONS_ALL (synonym) — joined on ORG_ID to provide SET_OF_BOOKS_ID for the operating unit.
• HR_ALL_ORGANIZATION_UNITS (synonym) — supplies the operating unit NAME, joined on HR.ORGANIZATION_ID = PT.ORG_ID.
• PA_SECURITY (package) — the ALLOW_QUERY function enforces project-level security.
• PA_PROJECT_UTILS (package) — the CHECK_PRJ_STUS_ACTION_ALLOWED function derives the CHARGES_ALLOWED_FLAG.
• PA_CROSS_BUSINESS_GRP (package) — controls whether cross business group querying is enabled.
• FND_PROFILE (package) — retrieves the PER_BUSINESS_GROUP_ID profile value.

The view therefore functions as a security- and context-aware projection over the PA project hierarchy, embedding both data joins and access-control logic directly in its SQL.

Key Columns

• PROJECT_ID, PROJECT_NUMBER (SEGMENT1), PROJECT_NAME — the primary, user-facing, and descriptive identifiers used as LOV return values.
• PROJECT_TYPE, PROJECT_TYPE_CLASS_CODE, CC_PRVDR_FLAG — classify the project and indicate cross-charge provider eligibility.
• PROJECT_STATUS_CODE — current lifecycle status (e.g., Approved, Closed).
• CHARGES_ALLOWED_FLAG — derived via PA_PROJECT_UTILS; indicates whether new transactions may be charged to the project.
• TEMPLATE_FLAG — always effectively 'N', since templates are excluded.
• ORG_ID, OPERATING_UNIT — the owning operating unit, critical for multi-org reporting.
• CARRYING_OUT_ORGANIZATION_ID — the organization responsible for executing the project.
• START_DATE, COMPLETION_DATE — project duration.
• PROJECT_CURRENCY_CODE, PROJFUNC_CURRENCY_CODE, PROJECT_RATE_DATE/TYPE, PROJFUNC_COST_RATE_DATE/TYPE — currency and rate context for project and project functional amounts.
• ALLOW_CROSS_CHARGE_FLAG, PROJ_SET_OF_BOOKS_ID, PM_PROJECT_REFERENCE — cross-charge permission, ledger linkage, and the project manager reference.

Common Use Cases and Queries

The view is most commonly used to populate LOVs in subledger entry screens, validate project selections during transaction entry, and drive user-scoped project reporting where the standard project security rules must be honored. Because security is enforced inside the view, developers can query it without re-implementing PA_SECURITY logic.

A typical lookup query retrieves chargeable projects for a given operating unit:

• SELECT project_id, project_number, project_name FROM pa_projects_all_basic_v WHERE org_id = :p_org_id AND charges_allowed_flag = 'Y' ORDER BY project_number;

For LOV population filtered on active projects, a common pattern is:

• SELECT project_number, project_name FROM pa_projects_all_basic_v WHERE project_status_code = 'APPROVED' AND start_date <= SYSDATE AND (completion_date IS NULL OR completion_date >= SYSDATE);

For reporting by class, developers join or filter on PROJECT_TYPE_CLASS_CODE:

• SELECT project_number, project_name, operating_unit FROM pa_projects_all_basic_v WHERE project_type_class_code = 'CONTRACT' ORDER BY operating_unit, project_number;

Because PA_SECURITY.ALLOW_QUERY and PA_CROSS_BUSINESS_GRP.ISCROSSBGPROFILE are evaluated at runtime, results vary by the connecting user and profile settings, which is essential for multi-org and shared-services deployments.