Search Results decision_maker_flag

Overview

AST_ORG_CONTACTS_V is a TeleSales (AST) reporting and integration view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, denormalized projection of organization contacts by joining relationship records, party master records, organization contact detail records, and lookup translations. The view exposes contact identity, contact role, organization context, and descriptive flexfield attributes in a single queryable shape, which allows reporting tools, concurrent programs, and integration extracts to retrieve organization contact information without reconstructing the underlying TCA (Trading Community Architecture) join logic themselves.

The view is a read-only construct; it does not store data. All inserts, updates, and deletions must be directed against the underlying base tables. Because the object is a view rather than a table, it cannot be used as the driving entity for DML in standard EBS forms, and concurrent programs that need to write contact data must reference HZ_ORG_CONTACTS directly.

The user search term "decision_maker_flag" maps directly to a column exposed by this view. The flag is sourced from HZ_ORG_CONTACTS.DECISION_MAKER_FLAG and indicates whether the contact is designated as a decision maker for the organization. This column is frequently used in TeleSales and CRM-style segmentation to prioritize outreach and to select high-value contacts in campaign or opportunity reports.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, AST_ORG_CONTACTS_V is defined over the following referenced objects:

• HZ_RELATIONSHIPS (synonym) — provides the relationship row identity and relationship-level attributes, aliased as PARTY_REL. Supplies RELATIONSHIP_ID, SUBJECT_ID, OBJECT_ID, PARTY_ID, RELATIONSHIP_TYPE, DIRECTIONAL_FLAG, STATUS, and the relationship start and end dates.
• HZ_ORG_CONTACTS (synonym) — provides the organization contact detail, aliased as ORG_CONT. Supplies ORG_CONTACT_ID, CONTACT_NUMBER, DEPARTMENT_CODE, DEPARTMENT, TITLE, JOB_TITLE, DECISION_MAKER_FLAG, JOB_TITLE_CODE, REFERENCE_USE_FLAG, RANK, PARTY_SITE_ID, and the contact descriptive flexfield columns ATTRIBUTE1 through ATTRIBUTE24.
• HZ_PARTIES (synonym) — provides party master information, aliased as HP. Supplies PARTY_NUMBER, CATEGORY_CODE, and party-level audit columns.
• AR_LOOKUPS (view) — used as LKUP1, LKUP2, and LKUP3 to translate lookup codes into user-facing meanings for relationship type or status, job title, and category code respectively.

The join path links relationship rows to organization contact rows through the party and object identifiers, and enriches each row with party master data and decoded lookup meanings.

Key Columns

• DECISION_MAKER_FLAG — from HZ_ORG_CONTACTS; identifies contacts flagged as decision makers. Principal column for the searched term.
• ORG_CONTACT_ID — primary identifier of the organization contact record; the correct foreign key for joins back to HZ_ORG_CONTACTS.
• RELATIONSHIP_ID, SUBJECT_ID, OBJECT_ID, PARTY_ID — relationship and party linkage keys from HZ_RELATIONSHIPS.
• PARTY_NUMBER, CATEGORY_CODE — party master identity and classification from HZ_PARTIES.
• CONTACT_NUMBER, DEPARTMENT[, _CODE], TITLE, JOB_TITLE[, _CODE], RANK — organizational role and seniority attributes.
• REFERENCE_USE_FLAG, STATUS — usability and lifecycle indicators for the contact record.
• MEANING (LKUP1/LKUP2/LKUP3) — decoded lookup descriptions for relationship type, job title, and party category.
• ATTRIBUTE1–ATTRIBUTE24, ATTRIBUTE_CATEGORY — organization contact descriptive flexfield segments.
• START_DATE, END_DATE, LAST_UPDATE_DATE, CREATED_BY, OBJECT_VERSION_NUMBER — effective dating, audit, and optimistic locking columns (note that LAST_UPDATE_DATE appears multiple times in the select list from different aliases).

Common Use Cases and Queries

Typical uses include decision-maker identification, organization contact rosters, job title and department reporting, and integration extracts requiring denormalized contact data.

To list all decision makers for organizations:

• SELECT party_number, contact_number, title, department, decision_maker_flag
• FROM apps.ast_org_contacts_v
• WHERE decision_maker_flag = 'Y';

To retrieve contacts for a specific party with decoded lookup meanings:

• SELECT contact_number, job_title, meaning, rank
• FROM apps.ast_org_contacts_v
• WHERE party_id = :p_party_id
• AND status = 'A';

To count decision makers per organization:

• SELECT party_number, COUNT(*) decision_makers
• FROM apps.ast_org_contacts_v
• WHERE decision_maker_flag = 'Y'
• GROUP BY party_number;

Because LAST_UPDATE_DATE and other audit columns appear more than once in the view definition, queries should reference columns by name only where unique; ambiguous names should be aliased in the underlying definition or avoided in ad hoc SQL.