Results for “object_id”

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

Overview

ASO_PVT_PARTY_RLTN_V is a database view owned by the APPS schema within the Oracle E-Business Suite Order Capture (ASO) product family. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a filtered presentation layer over the Trading Community Architecture (TCA) relationship data stored in HZ_RELATIONSHIPS. Its purpose is to expose only those party relationships that are currently active as of the system date, shielding callers from the status and date-range logic required to identify valid relationships.

Because the predicate logic is embedded in the view definition, any report, concurrent program, or integration that selects from ASO_PVT_PARTY_RLTN_V automatically inherits the same "active relationship" semantics. This makes the view a convenient and consistent source for order capture processing, where relationships between parties (for example, between a customer and a contact, or between related organizations) must reflect the state of the relationship at query time rather than at some earlier point. The view is documented as VALID, indicating that it compiles successfully against its referenced base object.

Underlying Base Objects

The view is defined exclusively over a single base object, HZ_RELATIONSHIPS, referenced through a synonym in the APPS schema. HZ_RELATIONSHIPS is the central TCA table that stores the directional relationships between parties, where each row identifies a subject party, an object party, and the nature of the relationship.

The ETRM metadata for this view identifies the referenced base object as HZ_RELATIONSHIPS (SYNONYM), confirming that no joins, unions, or additional tables are involved. The view text applies three filtering conditions to that table:

• STATUS = 'A' — restricts output to relationships whose status is Active.
• TRUNC(START_DATE) <= TRUNC(SYSDATE) — excludes relationships that have not yet begun as of the current date.
• TRUNC(NVL(END_DATE, SYSDATE)) >= TRUNC(SYSDATE) — excludes relationships that have already ended, and treats a null end date as open-ended.

All date comparisons are truncated to the day, so the view is insensitive to the time component of START_DATE and END_DATE. Callers therefore receive a day-granular view of relationship validity.

Key Columns

The view projects a small, focused set of columns. The ETRM metadata lists the following column names: PARTY_RELATIONSHIP_ID, SUBJECT_ID, OBJECT_ID, and PARTY_ID. The underlying view text selects RELATIONSHIP_ID, SUBJECT_ID, OBJECT_ID, and PARTY_ID from HZ_RELATIONSHIPS, which indicates that PARTY_RELATIONSHIP_ID is the alias applied to RELATIONSHIP_ID in the projection.

• PARTY_RELATIONSHIP_ID — the unique identifier of the relationship record, corresponding to RELATIONSHIP_ID in HZ_RELATIONSHIPS.
• SUBJECT_ID — the party identifier for the subject (source) side of the relationship.
• OBJECT_ID — the party identifier for the object (target) side of the relationship.
• PARTY_ID — an additional party identifier carried from the base table, typically associated with the party context of the relationship row.

Because the identifiers are numeric party keys rather than descriptive attributes, consumers typically join to HZ_PARTIES or related TCA views to resolve party names and other descriptive details.

Common Use Cases and Queries

Typical usage centers on determining which relationships are currently in force for a given party. A common pattern filters on SUBJECT_ID or OBJECT_ID and joins to HZ_PARTIES to obtain names:

• Listing all active relationships in which a party participates, as either subject or object.
• Validating that a relationship exists before creating or processing an order capture record.
• Feeding downstream reports that require only currently valid relationships.

A representative query follows:

SELECT r.PARTY_RELATIONSHIP_ID, r.SUBJECT_ID, r.OBJECT_ID, p.PARTY_NAME
FROM APPS.ASO_PVT_PARTY_RLTN_V r, APPS.HZ_PARTIES p
WHERE r.OBJECT_ID = p.PARTY_ID
AND r.SUBJECT_ID = :subject_party_id;

Because the view encapsulates the status and date-window logic, no additional filtering on relationship status or dates is required in the consuming query. This consistency is the principal benefit of using ASO_PVT_PARTY_RLTN_V rather than querying HZ_RELATIONSHIPS directly.