Search Results pa_proj_all_basic_un_sec_v

Overview

PA_PROJ_ALL_BASIC_UN_SEC_V is an APPS-owned database view in the Oracle E-Business Suite Projects (PA) module. It is documented as "a view of the projects to which you can do search (for subledgers LOV)." In practice, this view serves as a filtered, security-aware list of projects that can be presented to users in a List of Values (LOV) when they are entering project-related data in subledger transactions — for example, when associating a project with an expenditure, invoice, or other subledger accounting entry. Unlike secured project views that enforce full project-level access control through PA security profiles, this view is labeled "UN_SEC" (unsecured) and is intended to return the broad set of projects available for search, subject to the business-group and operating-unit conditions defined in its query rather than to a specific user's project security hierarchy.

The view is defined with STATUS: VALID and is available in both Oracle EBS 12.1.1 and 12.2.2. It exists to simplify subledger development and configuration by exposing a single, pre-joined result set of projects together with their project types, set of books, and operating unit, so that forms and concurrent programs do not need to reimplement the joining and filtering logic.

Underlying Base Objects

The view is constructed over a join of several base objects. The documented referenced objects are:

• PA_PROJECTS_ALL (SYNONYM) — the primary source of project rows, providing project identifier, number, name, dates, currency, and status.
• PA_PROJECT_TYPES_ALL (SYNONYM) — supplies the project type class code and the cross-charge provider flag, joined on PROJECT_TYPE and ORG_ID.
• PA_IMPLEMENTATIONS_ALL (SYNONYM) — provides the set of books identifier associated with each operating unit.
• HR_ALL_ORGANIZATION_UNITS (SYNONYM) — the operating unit (organization) name, joined on ORGANIZATION_ID equal to the project type's ORG_ID.
• PA_PROJECT_UTILS (PACKAGE) — invoked through CHECK_PRJ_STUS_ACTION_ALLOWED to determine whether the project's current status permits new transactions.
• FND_PROFILE (PACKAGE) — used to read the PER_BUSINESS_GROUP_ID profile value for business-group filtering.
• PA_CROSS_BUSINESS_GRP (PACKAGE) — exposes ISCROSSBGPROFILE to conditionally relax or enforce business-group restrictions.

Key Columns

Among the columns exposed, the following are most significant for reporting and integration:

• PROJECT_ID — the internal unique key of the project.
• PROJECT_NUMBER / PROJECT_NUMBER_SORT_ORDER — the user-facing project number (derived from SEGMENT1) and the sort value applied in LOV presentation.
• PROJECT_NAME and PROJECT_DESCRIPTION — descriptive text for display in lookups.
• PROJECT_TYPE / PROJECT_TYPE_CLASS_CODE — the project type and its classification.
• PROJECT_STATUS_CODE and CHARGES_ALLOWED_FLAG — the current status and whether new transactions are permitted (returned by CHECK_PRJ_STUS_ACTION_ALLOWED for the 'NEW_TXNS' action).
• ORG_ID and OPERATING_UNIT — the operating unit identifier and its name.
• START_DATE / COMPLETION_DATE — the project date range.
• PROJECT_CURRENCY_CODE, PROJFUNC_CURRENCY_CODE — project and project functional currencies.
• PROJ_SET_OF_BOOKS_ID — the associated set of books.
• ALLOW_CROSS_CHARGE_FLAG and CC_PRVDR_FLAG — cross-charge eligibility indicators.
• TEMPLATE_FLAG — always oriented so that template projects are excluded (only non-templates are returned).

Common Use Cases and Queries

The view is most commonly referenced by subledger forms and custom concurrent programs to populate a project LOV or to validate a user-entered project. A typical query filters to non-template, transaction-eligible projects within a given operating unit:

• Populating a project LOV: SELECT project_id, project_number, project_name FROM pa_proj_all_basic_un_sec_v WHERE org_id = :org_id AND charges_allowed_flag = 'Y' ORDER BY project_number_sort_order;
• Validating a project for a subledger entry: SELECT project_id FROM pa_proj_all_basic_un_sec_v WHERE project_number = :project_number AND org_id = :org_id;
• Reporting on active projects by operating unit: SELECT operating_unit, project_number, project_name, project_status_code, start_date FROM pa_proj_all_basic_un_sec_v WHERE project_status_code = 'APPROVED';

Because the view explicitly excludes template projects and award projects (via the PT.PROJECT_TYPE <> 'AWARD_PROJECT' predicate), consumers should rely on it when the intent is to offer receivable/chargeable projects rather than the full project catalog. Where strict project-level security is required, secured project views should be used instead.