Results for “pa_projects_erp_ext_b”

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

Overview

PA_PROJECTS_ERP_EXT_B is a Projects (PA) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores user-defined attribute data for the project and task level. It is a descriptive flexfield–style extension table that captures customer-specific attribute values which cannot be modeled in the standard PA_PROJECTS_ALL and PA_PROJ_ELEMENTS columns. The table is owned by the APPS-facing PA schema and is documented as VALID in ETRM for release 12.2.2 with 99 columns.

Structurally the table records one row per project or project element, keyed by a surrogate EXTENSION_ID and related to the parent project and element through foreign keys. Its purpose is to hold the "extra" information that customers configure through project descriptive flexfields, including the enterprise-defined attribute groups referenced by ATTR_GROUP_ID.

From a Data Vault modeling perspective, the mined foreign key structure suggests this object behaves as a link. A link resolves relationships between hubs — here the PA_PROJECTS_ALL hub (via PROJECT_ID) and the PA_PROJ_ELEMENTS hub (via PROJ_ELEMENT_ID) — and would carry the attribute values as link-level descriptive data. This classification is heuristic and should be treated as a modeling suggestion rather than a documented Data Vault assignment.

Key Information Stored

The table contains the following significant columns:

• EXTENSION_ID — the surrogate primary key, defined by the constraint PA_PROJECTS_ERP_EXT_B_PK. It is also the sole documented unique index (PA_PROJECTS_ERP_EXT_B_U1), making it the primary business-key candidate for direct lookups.
• PROJECT_ID — foreign key to PA_PROJECTS_ALL, identifying the parent project.
• PROJ_ELEMENT_ID — foreign key to PA_PROJ_ELEMENTS, identifying the specific project element or task.
• ATTR_GROUP_ID — identifies the attribute group under which the user-defined attributes are organized.
• C_EXT_ATTR1 through C_EXT_ATTR40 — forty character-type user-defined attribute columns, the primary carriers of descriptive flexfield text data.
• N_EXT_ATTR1 through N_EXT_ATTR20 with UOM_EXT_ATTR1 through UOM_EXT_ATTR20 — twenty numeric attribute pairs, each with a corresponding unit-of-measure column.
• D_EXT_ATTR1 through D_EXT_ATTR10 — ten date-type user-defined attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS who-columns providing audit and concurrency control.

The surrogate EXTENSION_ID is the technical anchor; PROJECT_ID and PROJ_ELEMENT_ID carry the business relationships that give each extension row its meaning.

Common Use Cases and Queries

Typical uses include retrieving user-defined values for a project or task, validating captured extension data, and populating custom reports or extracts that blend standard project data with configured attributes.

A common pattern joins the extension row back to its project and element:

• Select e.C_EXT_ATTR1, e.N_EXT_ATTR1, e.D_EXT_ATTR1 FROM PA.PA_PROJECTS_ERP_EXT_B e JOIN PA.PA_PROJECTS_ALL p ON e.PROJECT_ID = p.PROJECT_ID WHERE p.PROJECT_NUMBER = :project_number.
• Restrict by element: join PA_PROJ_ELEMENTS on e.PROJ_ELEMENT_ID to retrieve task-level attributes for a single element.
• Aggregate by ATTR_GROUP_ID to report which users or groups have populated which attribute sets.

Because direct table access is unsupported in EBS, production reporting should be built through the supported project descriptive flexfield views and APIs rather than querying PA_PROJECTS_ERP_EXT_B directly. When direct SQL is unavoidable for diagnostics, it should be read-only and constrained by EXTENSION_ID or PROJECT_ID to avoid full scans across the 99-column structure.

Related Objects

The following objects are most significant in relation to PA_PROJECTS_ERP_EXT_B:

• PA_PROJECTS_ALL — referenced via PROJECT_ID; the parent project record supplying project-level context and identifiers such as PROJECT_NUMBER and PROJECT_NAME.
• PA_PROJ_ELEMENTS — referenced via PROJ_ELEMENT_ID; supplies the task or element-level context for the extension row.
• PA_PROJECTS_ERP_EXT_B_PK / PA_PROJECTS_ERP_EXT_B_U1 — the primary key and unique index on EXTENSION_ID that enforce row uniqueness.
• PA descriptive flexfield views and APIs — the supported integration layer through which these attributes are normally read and maintained, abstracting the underlying extension table.

All cross-table access to this object should be made through the documented foreign keys to PA_PROJECTS_ALL and PA_PROJ_ELEMENTS, ensuring that extension data remains tied to its correct project and element context.