Search Results pa_projects_n6

Overview

PA.PA_PROJECTS_ALL is the master project definition table in the Oracle E-Business Suite Projects (PA) schema. It stores the header-level attributes of every project and project template managed by Oracle Projects, including descriptive identifiers, classification, status, scheduling dates, billing and revenue configuration, cross-charge rules, currency and funding parameters, and integration references to Oracle Project Management and other applications. The table is a partitioned-style "ALL" object, and each project is uniquely identified by a numeric surrogate key, PROJECT_ID. Because virtually every subordinate Projects construct — tasks, budgets, expenditures, events, invoices, forecasts, resource assignments, and asset capitalisation records — is anchored to a row in this table, PA_PROJECTS_ALL functions as the central reference point for the entire Projects domain. Its ETRM status is VALID, its owner is PA, and it is physically stored in the APPS_TS_TX_DATA tablespace with indexes in APPS_TS_TX_IDX. Under a heuristic Data Vault classification, this object would be modelled as a hub: PROJECT_ID is an immutable business key that other subject areas reference through foreign keys or association to their own hubs. As with all Oracle Applications internal tables, access should be obtained through supported Oracle APIs or views rather than direct DML.

Key Information Stored

The surrogate primary key is PROJECT_ID, enforced by the PA_PROJECTS_PK constraint. Five unique indexes act as documented business-key candidates:

• PA_PROJECTS_U1 — PROJECT_ID, SEGMENT1 (project number; reinforces the surrogate identity with the user-visible number).
• PA_PROJECTS_U2 — SEGMENT1, the project number displayed and entered by users.
• PA_PROJECTS_U3 — NAME, the short project name.
• PA_PROJECTS_U4 — PM_PROJECT_REFERENCE, PM_PRODUCT_CODE, linking the record to Oracle Project Management.
• PA_PROJECTS_U5 — LONG_NAME, the descriptive project title.

The most significant non-key columns include: PROJECT_TYPE, which points to PA_PROJECT_TYPES_ALL and drives transaction and billing behaviour; PROJECT_STATUS_CODE (PA_PROJECT_STATUSES), governing whether a project is active, closed, or pending; CARRYING_OUT_ORGANIZATION_ID (HR_ALL_ORGANIZATION_UNITS), the owning operating unit; START_DATE, COMPLETION_DATE, and CLOSED_DATE for lifecycle tracking; PUBLIC_SECTOR_FLAG, TEMPLATE_FLAG, and SUMMARY_FLAG, which control project classification; ORG_ID, which identifies the operating unit in a multi-org context; PROJECT_CURRENCY_CODE and the four currency/rate-type columns used for billing and revenue; and the standard WHO columns LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY. The table contains 201 documented columns in total, covering the full range of billing, cross-charge, funding, indirect-rate, and capitalisation controls.

Common Use Cases and Queries

PA_PROJECTS_ALL is queried constantly for project lookups, status validation, and reporting. A typical pattern joins the table to status and organisation references to produce an active-project listing:

• Project status validation during transaction entry: "SELECT p.project_id, p.segment1, p.name, s.project_status_code FROM pa_projects_all p, pa_project_statuses s WHERE p.project_status_code = s.project_status_code AND p.segment1 = :project_number" — used to confirm a project is open before charging expenditures.
• Reference validation for cross-module keys: joins from AP_INVOICES_ALL, PO_REQUISITIONS_INTERFACE_ALL, or FA_MASS_ADDITIONS back to PA_PROJECTS_ALL on PROJECT_ID confirm the project exists and is enabled.
• Template discovery: filter on TEMPLATE_FLAG and ORG_ID to list project templates available to an operating unit.
• Currency and billing configuration reports: select PROJECT_CURRENCY_CODE, INVOICE_METHOD, and REVENUE_ACCRUAL_METHOD for revenue-recognition analysis.
• Data-model navigation: the unique index PA_PROJECTS_U5 on LONG_NAME supports lookup by descriptive title; PA_PROJECTS_N5 on ADW_NOTIFY_FLAG and PA_PROJECTS_N6 on TEMPLATE_FLAG support operational reporting filters.

Because the ETRM metadata warns against direct application data access, ad-hoc queries should be limited to read-only reporting against supported or seeded views.

Related Objects

The foreign keys and inbound references to PA_PROJECTS_ALL are extensive; the following are the most significant for design and development work:

• PA.PA_TASKS — references PROJECT_ID; the primary child of the project hierarchy where WBS work is organised.
• PA.PA_EXPENDITURE_ITEMS_ALL — mature, audited cost transactions charged to each project via PROJECT_ID.
• PA.PA_BUDGETS and PA.PA_BUDGET_VERSIONS — store baseline and current project budgets keyed by PROJECT_ID.
• PA.PA_EVENTS and PA.PA_DRAFT_REVENUES_ALL — revenue-generation and accrual records tied to the project.
• PA.PA_DRAFT_INVOICES_ALL — billing documents generated for the project reference PROJECT_ID (and CC_PROJECT_ID for cross-charge).
• PA.PA_PROJECT_ASSIGNMENTS and PA.PA_RESOURCE_ASSIGNMENTS — assign people, roles, and resources to the project.
• PA.PA_PROJECT_CUSTOMERS and PA.PA_PROJECT_PLAYERS — capture customer and team-member associations.
• PA.PA_PROJECTS_ERP_EXT_B and PA.PA_PROJECTS_ERP_EXT_TL — extension tables holding additional project attributes keyed by PROJECT_ID.
• AP.AP_INVOICES_ALL and AP.AP_EXPENSE_REPORT_LINES_ALL — external modules referencing PROJECT_ID for project-related payables and expense charges.
• PJI.* tables such as PJI_REP_XBS_DENORM and PJI_AC_XBS_ACCUM_F — Projects Intelligence reporting objects built on the project dimension.

These relationships confirm the hub role of PA_PROJECTS_ALL: it is the anchor dimension for Projects, Payables, Assets, Purchasing, Grants, and Property Manager data across the EBS 12.1.1 and 12.2.2 application suites.