Results for “project_request_type”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.PA_PROJECT_REQUESTS_V is a reporting and integration view in Oracle EBS 12.1.1 and 12.2.2 that consolidates project request header information with descriptive lookups, project status details, customer party and address data, and source organization context. A project request represents a pre-project record — an opportunity, proposal, or candidate project captured before formal project creation — maintained in the PA_PROJECT_REQUESTS table. The view enriches that base record with decoded lookup meanings, human-readable status names, and customer master information drawn from the Oracle Trading Community Architecture (TCA) tables.

The view is particularly significant in relation to the search term "project_request_type." The request type attribute is resolved through a join to PA_LOOKUPS on lookup type PROJECT_REQUEST_TYPE, meaning the view exposes the lookup meaning rather than the raw lookup code. This makes the view the natural source for reports, dashboards, or interfaces that must present or filter project requests by their business classification without independently resolving lookup codes.

Underlying Base Objects

The view is defined over the following documented base objects:

• PA_PROJECT_REQUESTS (synonym) — the primary driving table containing request headers.
• PA_LOOKUPS (view) — joined on lookup_type = 'PROJECT_REQUEST_TYPE' and pr.request_type = l.lookup_code, supplying the decoded request type meaning.
• PA_PROJECT_STATUSES (synonym) — joined on status_type = 'PROJ_REQ' and matching status code, providing the status name and system status code.
• FND_APPLICATION_TL (synonym) — an outer join supplying the source application name, language-matched via userenv('LANG').
• HZ_PARTIES, HZ_PARTY_SITES, HZ_LOCATIONS, HZ_CUST_ACCOUNTS (synonyms) — outer-joined TCA tables providing party name and number, address elements, and customer account number and name.
• FND_ACCESS_CONTROL_UTIL (package) — invoked as GET_ORG_NAME(pr.source_org_id) to return the source operating unit name.

All TCA and application joins are outer joins, so project requests lacking a linked customer or application still appear in the result set.

Key Columns

• REQUEST_ID / REQUEST_NAME / REQUEST_NUMBER — primary identifier and user-facing name and number of the project request.
• MEANING — decoded PROJECT_REQUEST_TYPE lookup meaning; the business-readable request type.
• PROJECT_STATUS_NAME / PROJECT_SYSTEM_STATUS_CODE — descriptive and internal status values for the request.
• EXPECTED_PROJECT_APPROVAL_DATE / CLOSED_DATE — anticipated approval date and actual closure date.
• APPLICATION_NAME / SOURCE_REFERENCE / VALUE / CURRENCY_CODE — originating application, external reference, and estimated monetary value with currency.
• PARTY_NAME / PARTY_NUMBER and the ADDRESS1–POSTAL_CODE and ADDRESS_LINES_PHONETIC columns — customer identification and address details.
• ACCOUNT_NUMBER / ACCOUNT_NAME — customer account context.
• GET_ORG_NAME(PR.SOURCE_ORG_ID) — source operating unit name.
• RECORD_VERSION_NUMBER — optimistic locking version, useful for integration writes.

Common Use Cases and Queries

Typical scenarios include project pipeline reporting by request type, customer-linked opportunity tracking, and source operating unit analysis. Filtering by decoded request type is the most common requirement:

• Pipeline by request type: SELECT request_number, request_name, meaning, project_status_name, value, currency_code FROM apps.pa_project_requests_v WHERE meaning = 'Proposal';
• Customer-linked requests: SELECT request_number, party_name, account_number, expected_project_approval_date FROM apps.pa_project_requests_v WHERE party_name IS NOT NULL ORDER BY expected_project_approval_date;
• Operating unit summary: SELECT fnd_access_control_util.get_org_name(source_org_id), meaning, COUNT(*) FROM apps.pa_project_requests_v GROUP BY source_org_id, meaning;

Because the view already resolves lookup meanings, statuses, and customer attributes, it eliminates repetitive decode and join logic in custom reports and integration extracts within Oracle EBS 12.1.1 and 12.2.2.