Results for “pa_object_relationships_u2”

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

Overview

PA.PA_OBJECT_RELATIONSHIPS is a transactional table in the Oracle E-Business Suite Projects (PA) schema that stores all relationships between projects, project structures, tasks, and related project objects. Each row represents a directed relationship from a predecessor object (the from side) to a successor object (the to side), qualified by a relationship type and optional subtype. The table supports the relationship infrastructure used by Oracle Projects for dependency modeling, scheduling links, and structural associations across project hierarchies in both EBS 12.1.1 and 12.2.2.

From a dimensional modeling perspective, the mined FK structure suggests classifying this object as a link table in a Data Vault model. It resolves many-to-many associations between project entities rather than holding descriptive attributes of a single business key. The presence of standard Who columns, a system-generated surrogate identifier, and multiple unique business-key candidates reinforces this interpretation.

Key Information Stored

The most significant columns are:

• OBJECT_RELATIONSHIP_ID — System-generated unique identifier and the surrogate primary key (PA_OBJECT_RELATIONSHIPS_PK).
• OBJECT_TYPE_FROM — Type of the predecessor object, such as PA_PROJECTS or PA_TASKS.
• OBJECT_ID_FROM1 through OBJECT_ID_FROM5 — Identifier components for the predecessor object. OBJECT_ID_FROM1 typically carries the primary identifier (for example, PROJECT_ID).
• OBJECT_TYPE_TO — Type of the successor object.
• OBJECT_ID_TO1 through OBJECT_ID_TO5 — Identifier components for the successor object.
• RELATIONSHIP_TYPE — The nature of the relationship between the two objects.
• RELATIONSHIP_SUBTYPE — Further classification of the relationship.
• LAG_DAY and IMPORTED_LAG — Lag values used in scheduling relationships.
• PRIORITY and WEIGHTING_PERCENTAGE — Ordering and weighting attributes of the relationship.
• STATUS_CODE and RECORD_VERSION_NUMBER — Lifecycle status and optimistic locking support.
• PM_PRODUCT_CODE — Identifies the originating product context.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who audit columns.

Two unique indexes establish business-key candidates. PA_OBJECT_RELATIONSHIPS_U1 enforces uniqueness on OBJECT_RELATIONSHIP_ID, while PA_OBJECT_RELATIONSHIPS_U2 is a composite natural candidate key spanning OBJECT_TYPE_FROM, OBJECT_ID_FROM1, OBJECT_ID_FROM2, OBJECT_TYPE_TO, OBJECT_ID_TO1, OBJECT_ID_TO2, and RELATIONSHIP_TYPE. Seven non-unique indexes (N1–N7) support efficient traversal in both directions.

Common Use Cases and Queries

Typical usage includes resolving project-to-task hierarchies, traversing scheduling dependencies between tasks, and reporting on cross-project relationships. A common pattern joins on the predecessor side:

• Retrieve all successors for a given task using OBJECT_TYPE_FROM, OBJECT_ID_FROM1, and OBJECT_ID_FROM2.
• Use the N2 index columns (OBJECT_TYPE_TO, OBJECT_ID_TO1, OBJECT_ID_TO2, RELATIONSHIP_TYPE) for reverse lookups of predecessors.
• Filter by RELATIONSHIP_TYPE to isolate dependency, funding, or structural links.
• Join OBJECT_ID_FROM1 or OBJECT_ID_TO1 to PA_CONTROL_ITEMS or PA_PROJ_ELEMENT_VERSIONS to obtain descriptive project and task attributes.

A representative query pattern filters the from side, joins to the to side, and projects descriptive attributes from the referenced project entities. Reporting use cases include dependency analysis, critical path inputs, and structure audits. Queries should respect the composite key columns to leverage U2 and the non-unique indexes, avoiding full scans on this transaction-heavy table.

Related Objects

Foreign key metadata links this table to the following significant objects:

• PA.PA_CONTROL_ITEMS — Referenced through OBJECT_ID_FROM1 and OBJECT_ID_TO1.
• PA.PA_PROJ_ELEMENT_VERSIONS — Referenced through OBJECT_ID_FROM1 and OBJECT_ID_TO1.
• PA.PA_STRUCTURES_TASKS_TMP — References PA_OBJECT_RELATIONSHIPS via OBJECT_RELATIONSHIP_ID, used in temporary structure and task processing.

Applications code that populates, purges, or traverses this table interacts with the Projects task and structure APIs, which manage relationships on behalf of project and task structures. Operational maintenance should account for the eleven indexes documented above, since heavy insert or delete activity against this table carries corresponding index maintenance overhead.