Results for “asf_cnt_org_rels_vo_v”

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

Overview

ASF_CNT_ORG_RELS_VO_V is a reporting view belonging to the ASF - Sales Online product family in Oracle E-Business Suite. It presents a denormalized, query-ready projection of organization contact relationships held in the Oracle Trading Community Architecture (TCA) model. The view joins relationship records to both the subject party (a person) and the object party (an organization), and attaches the associated organization contact record so that attributes such as job title, decision maker flag, and reference use flag are available alongside the relationship itself. This makes the view a convenient single source for answering questions about who is the contact at a given organization, what role that contact plays, and whether that contact is marked as a decision maker.

As a "VO" (value object) view, it is typically consumed by the Sales Online application layer and by custom reporting rather than being a base transactional entity. It is important to note that the ETRM metadata records this view as not implemented in this database, and no owner or referenced base objects are documented in the 12.2.2 metadata. Organizations should confirm its existence via ALL_VIEWS before depending on it as a stable interface.

Underlying Base Objects

The documented view text defines the view over five TCA tables, all referenced in the FROM clause:

• HZ_RELATIONSHIPS REL — the driving table; supplies relationship identity, subject/object references, relationship code, status, and directional flag.
• HZ_PARTIES SPARTY — the subject party, restricted to PERSON type; provides person first and last names.
• HZ_PARTIES OPARTY — the object party, restricted to ORGANIZATION type; provides the organization name.
• HZ_ORG_CONTACTS CONT — the organization contact detail, joined on PARTY_RELATIONSHIP_ID; supplies job title, decision maker flag, and reference use flag.
• HZ_PARTIES PARTY — a third party alias used to validate party status.

The joins enforce that the subject party is a person, the object party is an organization, and the relationship direction is forward (DIRECTIONAL_FLAG = 'F'). Subject and object table names are constrained to HZ_PARTIES. Status filters allow 'A' (active) and 'I' (inactive) on all three party instances, on the contact, while the relationship itself must be 'A'. No base objects are formally documented in the ETRM metadata beyond those appearing in the view text.

Key Columns

• RELATIONSHIP_ID — primary key of the underlying HZ_RELATIONSHIPS row.
• SUBJECT_ID / OBJECT_ID — party identifiers for the person and the organization respectively.
• PERSON_FIRST_NAME, PERSON_LAST_NAME — name of the contact person.
• ORG_CONTACT_ID, JOB_TITLE — the organization contact record and the contact's job title.
• ORGANIZATION_NAME — name of the object organization (aliased from OPARTY.PARTY_NAME).
• DECISION_MAKER_FLAG — indicates whether the contact is designated a decision maker; the principal column for the searched term.
• REFERENCE_USE_FLAG — indicates whether the contact may be used as a reference.
• START_DATE, END_DATE — validity window of the relationship.
• LAST_UPDATE_DATE, PARTY_LAST_UPDATE_DATE, ORG_CNT_LAST_UPDATE_DATE — audit timestamps for incremental extraction.

Common Use Cases and Queries

Typical scenarios include identifying decision makers within customer organizations for sales targeting, populating contact pickers in Sales Online, and extracting contact-organization mappings for downstream CRM or data warehouse loads.

• Locate decision makers for a specific organization:

SELECT person_first_name, person_last_name, job_title, decision_maker_flag
FROM   asf_cnt_org_rels_vo_v
WHERE  organization_name = :p_org_name
AND    decision_maker_flag = 'Y';

• List all contacts, with reference-use indicators, for a party:

SELECT relationship_id, person_last_name, job_title,
       decision_maker_flag, reference_use_flag, start_date, end_date
FROM   asf_cnt_org_rels_vo_v
WHERE  subject_id = :p_person_party_id
AND    (end_date IS NULL OR end_date > SYSDATE);

• Incremental extraction based on audit columns:

SELECT *
FROM   asf_cnt_org_rels_vo_v
WHERE  GREATEST(last_update_date, party_last_update_date,
                org_cnt_last_update_date) >= :p_since;

Because the metadata records no owner, no documented base objects, and an "not implemented" status, deployments should validate availability and column names against the target instance prior to production use.