Search Results psi_column4

Overview

PA_PROJECT_LISTS_V is a VALID Oracle E-Business Suite view owned by the APPS schema and defined in the Projects (PA) product family. It exposes a consolidated, denormalised projection of project master data drawn principally from PA_PROJECTS_ALL, joined to supporting lookups, status, probability, location, territory and organisation tables. The view is designed to present a listing-oriented record set suitable for concurrent extract programs, Oracle Forms LOVs, and custom reports operating within the Oracle EBS 12.1.1 and 12.2.2 file systems.

Because it resolves numerous descriptive attributes — such as the project manager, primary customer name, project status name, and territory short name — through PL/SQL utility packages and lookup views, PA_PROJECT_LISTS_V removes the join complexity that would otherwise be required of report developers. It functions as a convenience interface layer over the Projects transactional base rather than as a transactional object in its own right; it is strictly a read-only construct.

Underlying Base Objects

The documented base objects supporting this view include:

• PA_PROJECTS_ALL — the principal source of project rows, holding project identifiers, names, segment values, dates, currency, and flags.
• PA_PROJECT_STATUSES — supplies the PROJECT_STATUS_NAME and related status reporting attributes.
• PA_PROJECT_TYPES_ALL — provides project type classification.
• PA_PROBABILITY_MEMBERS — supplies probability percentages for pipeline-style records.
• PA_PROJECT_OPP_ATTRS — contributes opportunity attribute data.
• PA_LOCATIONS, FND_TERRITORIES_VL, HR_ALL_ORGANIZATION_UNITS — supply address, country, territory short name, and carrying-out organisation name.
• FND_LOOKUPS and PA_LOOKUPS — resolve meaning columns for coded values.
• PA_PROJ_CURR_STATUS_REP_V — provides the current progress/status reporting columns.
• PA_PROJECT_PARTIES_UTILS, PA_PROJECTS_MAINT_UTILS, PA_PROJECT_DATES_UTILS, FND_GLOBAL — packages invoked inline to derive the project manager, project manager name, and primary customer name.

All joins are expressed at the view definition level, so callers see a single flat result set.

Key Columns

• PROJECT_ID — primary project identifier; the standard join key to downstream project queries.
• NAME, SEGMENT1, PROJECT_TYPE — human-readable project name, project number and type.
• CARRYING_OUT_ORGANIZATION_ID plus the joined organisation NAME — the executing organisation.
• PROJECT_STATUS_CODE, PROJECT_STATUS_NAME — status classification used for filtering active versus closed projects.
• START_DATE, COMPLETION_DATE, CLOSED_DATE, ACTUAL_START_DATE, ACTUAL_FINISH_DATE and the early/late/scheduled date variants — the full project scheduling picture.
• PUBLIC_SECTOR_FLAG and the lookup MEANING column — decoded indicator values.
• PROJECT_CURRENCY_CODE, ORG_ID, PROJECT_VALUE, PROBABILITY_MEMBER_ID / PROBABILITY_PERCENTAGE — currency, operating unit and pipeline valuation data.
• Project manager columns returned via PA_PROJECT_PARTIES_UTILS.GET_PROJECT_MANAGER and GET_PROJECT_MANAGER_NAME, and the primary customer name from PA_PROJECTS_MAINT_UTILS.GET_PRIMARY_CUSTOMER_NAME.
• SUMMARY_FLAG, TEMPLATE_FLAG, ENABLED_FLAG — structural flags for distinguishing summary, template and enabled records.

Several trailing columns are returned as NULL or TO_NUMBER(NULL) placeholders, indicating a fixed positional contract for consuming programs.

Common Use Cases and Queries

Typical scenarios include project master listings for reporting, LOV population, and integration extracts that require project manager and customer context without bespoke joins.

List active projects for an operating unit:

• SELECT project_id, name, segment1, project_status_name, start_date, completion_date FROM pa_project_lists_v WHERE org_id = :p_org_id AND project_status_code = 'APPROVED' ORDER BY name;

Retrieve project manager and customer for a given project:

• SELECT name, project_manager_name, primary_customer_name FROM pa_project_lists_v WHERE project_id = :p_project_id;

Extract a pipeline listing filtered on probability:

• SELECT segment1, name, probability_percentage, project_value FROM pa_project_lists_v WHERE probability_member_id IS NOT NULL ORDER BY probability_percentage DESC;

Because the project manager and primary customer are resolved through PL/SQL function calls, queries returning large row counts should apply restrictive WHERE predicates (org_id, status, date range) to limit package invocation overhead.