Results for “pa_resources”

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

Overview

PA_RESOURCES is a foundational master data table in the Oracle Projects (PA) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the resource definitions used throughout project budgeting, forecasting, project summarization, and resource management. A "resource" in this context represents any unit of supply that can be planned, assigned, or tracked against project work — labor resources, organizations, expenditure categories, or non-labor items such as equipment and material. Because budgeting and summarization logic flows through this table, PA_RESOURCES functions as the central reference point that many downstream PA objects resolve to.

From a heuristic Data Vault modeling perspective, the FK structure suggests PA_RESOURCES behaves as a hub-leaning entity. It carries a surrogate primary key (RESOURCE_ID) that is referenced by a large fan of dependent child tables, while itself referencing a small number of parent tables. This pattern is characteristic of a business-key hub with attached descriptive attributes, though the presence of extensive descriptive and audit columns means satellite behavior is also present. This is offered as a modeling suggestion only; the physical implementation is a normalized 37-column Oracle table owned by the PA schema.

Key Information Stored

The table's documented physical schema contains 37 columns, owned by PA. The most significant columns are:

• RESOURCE_ID — The surrogate primary key, defined by the unique index PA_RESOURCES_PK. This value is the join key referenced by virtually every dependent PA table.
• NAME — The user-visible resource name displayed in budgeting and assignment screens.
• DESCRIPTION — Free-text description of the resource.
• RESOURCE_TYPE_ID — Foreign key to PA_RESOURCE_TYPES, classifying the resource (for example, labor versus non-labor).
• UNIT_OF_MEASURE — The unit in which quantities for this resource are expressed.
• ROLLUP_QUANTITY_FLAG — Controls whether quantities roll up into summary amounts for the resource.
• TRACK_AS_LABOR_FLAG — Indicates whether the resource is treated as labor for costing and reporting purposes.
• START_DATE_ACTIVE / END_DATE_ACTIVE — The effective date range during which the resource is active.
• JTF_RESOURCE_ID — Links the PA resource to its counterpart in the CRM/Territory resource model.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle flexfield (descriptive flexfield) columns for customer-defined extensions.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — The standard concurrent program audit columns.
• ZD_EDITION_NAME — The editioning column introduced in 12.2 online patching (EBS 12.2.2), part of the business-key candidate PA_RESOURCES_U1.

The unique index PA_RESOURCES_U1 is defined on (RESOURCE_ID, ZD_EDITION_NAME). In EBS 12.1.1 the editioning column does not exist, so RESOURCE_ID alone effectively serves as the key; in 12.2.2 the composite index supports editioning. Note that a second FK relationship maps PA_RESOURCES.RESOURCE_ID back to JTF_RS_RESOURCE_EXTNS, reflecting the inheritance of the resource identity from the CRM resource model.

Common Use Cases and Queries

Typical scenarios include resource lookups during project assignment, budget validation, and reporting on labor versus non-labor usage.

• Resolving a resource name from an assignment or forecast line:

  SELECT r.name, r.resource_type_id, r.track_as_labor_flag
  FROM   pa_resources r
  WHERE  r.resource_id = :resource_id;

• Listing active resources by type within an effective window:

  SELECT resource_id, name, unit_of_measure
  FROM   pa_resources
  WHERE  resource_type_id = :type_id
  AND    SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

• Joining to classifications: pa_resources.resource_type_id = pa_resource_types.resource_type_id.
• Reporting on resources referenced by project assignments or candidates, driving budget-versus-actual analysis.

Because RESOURCE_ID is heavily referenced, queries that filter by resource type, active dates, or the labor flag benefit from the RESOURCE_TYPE_ID and date columns; the PK index backs the join path.

Related Objects

The FK and PK relationships establish PA_RESOURCES as a hub referenced by numerous dependent tables:

• PA_RESOURCE_TYPES — parent; joined on RESOURCE_TYPE_ID.
• PA_PROJECT_ASSIGNMENTS — references RESOURCE_ID; holds resource assignment to projects.
• PA_CANDIDATES — references RESOURCE_ID; candidate resource records.
• PA_PROJECT_PARTIES — references RESOURCE_ID; project party associations.
• PA_FORECAST_ITEM_DETAILS — references RESOURCE_ID; forecast line detail.
• PA_RESOURCE_LIST_MEMBERS — references RESOURCE_ID; membership in resource lists.
• PA_RESOURCE_ACCUM_DETAILS — references RESOURCE_ID; accumulated summary amounts.
• PA_ROLE_PROFILES — references RESOURCE_ID; role-to-resource mapping.
• PA_RES_AVAILABILITY — references RESOURCE_ID; resource availability records.
• JTF_RS_RESOURCE_EXTNS — parent; joined on RESOURCE_ID for CRM resource inheritance.

Collectively, these relationships confirm that PA_RESOURCES is the canonical resource dimension for Oracle Projects budgeting and summarization.