Results for “asf_org_org_rels_eo_v”

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

Overview

The view ASF_ORG_ORG_RELS_EO_V belongs to the ASF – Sales Online product family within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It exposes organization-to-organization relationship data as maintained in the Oracle Trading Community Architecture (TCA) model, specifically the HZ_RELATIONSHIPS and HZ_PARTIES tables. In sales and order-capture contexts, this view supports the reporting of hierarchical or associative links between legal entities, customers, and partner organizations.

The EO suffix indicates an "Entity Object" style view, commonly used as a programmatic data source in ASF Sales Online flows and downstream integrations. In the context of the user's search — wealth ODS extracts feeding an Agile Board tracked through Enterprise Jira on AWS — this view typically appears as a source object for ODS staging, mapping organization relationships into warehouse dimensions.

Underlying Base Objects

The view is defined over the TCA tables HZ_RELATIONSHIPS, HZ_PARTIES (aliased as SPARTY, OPARTY, and PARTY), HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_CONTACT_POINTS (joined twice for phone and email). Key join predicates include:

• REL.SUBJECT_ID = SPARTY.PARTY_ID and REL.OBJECT_ID = OPARTY.PARTY_ID, restricting both parties to PARTY_TYPE = 'ORGANIZATION'.
• REL.PARTY_ID = PARTY.PARTY_ID, linking the party master record.
• Outer joins (+) to HZ_PARTY_SITES, HZ_LOCATIONS, and to primary phone/email contact points owned by the party (OWNER_TABLE_NAME = 'HZ_PARTIES').
• Filters on REL.STATUS = 'A', DIRECTIONAL_FLAG = 'F', and SUBJECT_TABLE_NAME/OBJECT_TABLE_NAME = 'HZ_PARTIES'.

Note that the ETRM documentation records no explicitly registered base objects, and the view reports as not implemented in the reference database — implying it is conditionally deployed or replaced by equivalent queries in some environments.

Key Columns

• RELATIONSHIP_ID – Primary identifier of the underlying HZ_RELATIONSHIPS record.
• SUBJECT_ID / SUBJECT_ORG – Party ID and name of the subject organization.
• OBJECT_ID / OBJECT_ORG – Party ID and name of the object (related) organization.
• PARTY_RELATIONSHIP_TYPE / RELATIONSHIP_CODE – The nature of the link (e.g., parent, subsidiary, affiliate).
• START_DATE / END_DATE – Effective dating of the relationship.
• REL_PARTY_ID / PARTY_LAST_UPDAT – Party ID and last update timestamp used for change-data-capture and ODS incremental loads.
• SITE.PARTY_SITE_ID, LOC.LOCATION_ID, ADDRESS1..COUNTRY – Address details for the related party site.
• PHONE_*, EMAIL_ADDRESS – Primary phone and email contact points.

Common Use Cases and Queries

The view is typically queried for organization relationship extraction into an ODS or enrichment of customer hierarchy dimensions. A representative query:

• SELECT relationship_id, subject_org, object_org, party_relationship_type, start_date, end_date FROM asf_org_org_rels_eo_v WHERE end_date IS NULL OR end_date > SYSDATE;
• Incremental ODS loads filter on party_last_updat: WHERE party_last_updat > :last_extract_ts.
• Analysts join object_id to HZ_CUST_ACCOUNTS to resolve customer numbers for wealth and sales reporting.

Because the view carries no documented base-object registration, administrators should validate its availability (or its _EO successor) in the target 12.2.2 environment prior to reuse in Agile Board-tracked integration builds.