Results for “request_number”

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

Overview

The PA.PA_PROJECT_REQUESTS table stores project creation requests within the Oracle E-Business Suite Projects (PA) module. It functions as the intake staging construct through which project demand — most commonly originating from customer-facing or program-management workflows — is captured before a fully realized project record is instantiated in PA_PROJECTS. Each row represents a discrete request to create a project, carrying identity, classification, status, customer context, and audit metadata. In Oracle EBS 12.1.1 and 12.2.2 the table is documented as VALID with 43 columns.

Under a heuristic Data Vault classification mined from the foreign key structure, PA_PROJECT_REQUESTS models as a link table. Its four foreign keys converge on independent hubs — PA_PROJECT_STATUSES, HZ_PARTIES, HZ_PARTY_SITES, and HZ_CUST_ACCOUNTS — making it a natural intersection recording the association between a project request and its customer party, site, account, and lifecycle status. This classification is a modeling suggestion rather than a documented Oracle fact; the table also carries descriptive attributes that a strict Data Vault treatment would separate into a satellite.

Key Information Stored

The surrogate primary key is REQUEST_ID, enforced by unique index PA_PROJECT_REQUESTS_U1. Two additional unique indexes document business-key candidates: REQUEST_NUMBER (U2) and REQUEST_NAME (U3). These three identifiers should be treated as the authoritative lookup keys when querying or de-duplicating request data.

• REQUEST_TYPE, STATUS_CODE, SOURCE_TYPE — classify the request and drive its lifecycle; STATUS_CODE is the FK to PA_PROJECT_STATUSES.
• CUST_PARTY_ID, CUST_PARTY_SITE_ID, CUST_ACCOUNT_ID — the customer context, resolving to HZ_PARTIES, HZ_PARTY_SITES, and HZ_CUST_ACCOUNTS respectively.
• EXPECTED_PROJECT_APPROVAL_DATE, CLOSED_DATE — planning and completion timestamps.
• VALUE and CURRENCY_CODE — the monetary magnitude associated with the request.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_REQUEST_ID, PROGRAM_UPDATE_DATE — concurrency and program-tracking columns identifying the concurrent program that last touched the row.
• RECORD_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Who columns for audit and optimistic locking.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF/descriptive flexfield segment set for client-specific extension.

Common Use Cases and Queries

Typical reporting centers on open or aging project requests, customer-linked demand, and status throughput. A canonical query joins the request to its status and customer context:

• Listing requests with their current status description by joining STATUS_CODE to PA_PROJECT_STATUSES.
• Aggregating the total request VALUE by CURRENCY_CODE or by CUST_ACCOUNT_ID for customer-facing pipeline reporting.
• Identifying stalled requests using EXPECTED_PROJECT_APPROVAL_DATE against SYSDATE where CLOSED_DATE is null.
• Tracing the originating concurrent program via PROGRAM_REQUEST_ID and PROGRAM_APPLICATION_ID for troubleshooting.

A representative pattern selects REQUEST_NUMBER, REQUEST_NAME, STATUS_CODE, and CUST_ACCOUNT_ID from PA_PROJECT_REQUESTS, filtered on STATUS_CODE and ordered by CREATION_DATE. Because REQUEST_NUMBER is uniquely indexed, it is the preferred join key when linking external extracts back to this table.

Related Objects

The documented foreign keys define the primary relationships:

• PA_PROJECT_STATUSES — joined on PA_PROJECT_REQUESTS.STATUS_CODE = PA_PROJECT_STATUSES.STATUS_CODE.
• HZ_PARTIES — joined on PA_PROJECT_REQUESTS.CUST_PARTY_ID = HZ_PARTIES.PARTY_ID.
• HZ_PARTY_SITES — joined on PA_PROJECT_REQUESTS.CUST_PARTY_SITE_ID = HZ_PARTY_SITES.PARTY_SITE_ID.
• HZ_CUST_ACCOUNTS — joined on PA_PROJECT_REQUESTS.CUST_ACCOUNT_ID = HZ_CUST_ACCOUNTS.CUST_ACCOUNT_ID.

Downstream, the request data feeds the project creation process culminating in PA_PROJECTS and its associated structures. Reporting views and the Projects APIs consume REQUEST_ID and the unique business keys to correlate requests with their resulting projects.