Search Results decision_maker_flag

Overview

OE_RA_CONTACTS_V is a validation view owned by the APPS schema in Oracle E-Business Suite, residing in the Order Management (ONT) product family. Its documented purpose is the validation of contact identification — that is, confirming that a contact referenced against a customer account is a legitimate, active, and properly qualified record within the Trading Community Architecture (TCA) model. In Oracle EBS 12.1.1 and 12.2.2, the view is used by Order Management and downstream order-to-cash flows (order entry, returns, and returns authorization) to resolve and verify a contact associated with a customer account or account site before that contact is stored or acted upon. Rather than presenting a raw table, the view performs the join logic that reconciles the account role, the party, the party relationship, and the organization contact record into a single, flat, denormalized result set. This makes it suitable for lookups (LOV), validation routines, and ad hoc reporting where a contact must be confirmed against its customer account. As with most schema-level views in EBS, it is not in itself a data container, and it inherits the security model of the underlying TCA tables.

Underlying Base Objects

The ETRM 12.2.2 metadata records the view as defined over the following referenced base objects, all consumed through APPS synonyms:

• HZ_CUST_ACCOUNTS — the customer account header.
• HZ_CUST_ACCOUNT_ROLES — the account role/contact assignment records, driving the primary key and audit columns of the view.
• HZ_ORG_CONTACTS — the organization contact attributes (job title, mail stop, decision maker flag, managed_by, telephony/contact metadata).
• HZ_PARTIES — the party master, supplying name components, customer key, language, and do-not-mail flag.
• HZ_RELATIONSHIPS — the party relationship that links the contact party to the account party, supplying the e-mail address.

The view text joins HZ_CUST_ACCOUNT_ROLES (aliased ACCT_ROLE) to HZ_PARTIES (PARTY), HZ_RELATIONSHIPS (REL), and HZ_ORG_CONTACTS (ORG_CONT). The role record supplies identity and audit columns; the party supplies name and personal attributes; the relationship supplies contact-channel data such as e-mail; and the organization contact supplies employment/job attributes. Columns not physically sourced at the view definition, such as CONTACT_PERSONAL_INFORMATION, OTHER_LANGUAGE_1, OTHER_LANGUAGE_2, SEX_CODE, and SALUTATION, are exposed as NULL literals to preserve a compatibility interface for callers expecting the fuller contact structure.

Key Columns

The view exposes a broad column set, with the following being most significant in a validation context:

• CUST_ACCOUNT_ROLE_ID — primary identifier of the account-role (contact) row; the principal key returned for validation.
• CUST_ACCOUNT_ID — the account to which the contact role belongs, enabling account-scoped validation.
• CUST_ACCT_SITE_ID — presented in the view text with the inline comment ADDRESS_ID; ties the contact to a specific account site.
• STATUS — active/inactive state of the account role, core to whether a contact may be used.
• LAST_NAME and FIRST_NAME — derived with SUBSTRB truncation (50 and 40 bytes respectively) from the party's last and first name fields.
• MANAGED_BY — sourced from HZ_ORG_CONTACTS.MANAGED_BY, indicating the manager relationship for the contact; this is the column most directly relevant to searches for "managed_by".
• DECISION_MAKER_FLAG, JOB_TITLE, JOB_TITLE_CODE, DEPARTMENT, DEPARTMENT_CODE, RANK, MAIL_STOP — organizational contact attributes describing the individual's position.
• EMAIL_ADDRESS — from HZ_RELATIONSHIPS, the contact's electronic address.
• CUSTOMER_KEY, NATIVE_LANGUAGE, SUFFIX, DO_NOT_MAIL_FLAG, CONTACT_NUMBER, ORIG_SYSTEM_REFERENCE — party and contact identifiers/filters.
• PRIMARY_FLAG, REFERENCE_USE_FLAG, MATCH_GROUP_ID, MAILING_ADDRESS_ID — flags and linkage attributes governing the contact's role.
• Standard WHO/audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the ATTRIBUTE1–25 and PROGRAM/REQUEST columns.

Common Use Cases and Queries

Typical uses include validating a contact before order entry, populating contact LOVs, and confirming manager relationships via the managed_by column. A simple validation query:

SELECT cust_account_role_id, first_name, last_name, managed_by, status, email_address FROM oe_ra_contacts_v WHERE cust_account_id = :p_account_id AND status = 'A';

To locate contacts by manager:

SELECT cust_account_role_id, first_name, last_name, job_title, managed_by FROM oe_ra_contacts_v WHERE managed_by = :p_manager AND cust_account_id = :p_account_id;

To confirm a specific contact's identity by name and e-mail:

SELECT cust_account_role_id, first_name, last_name, email_address, cust_acct_site_id FROM oe_ra_contacts_v WHERE last_name = :p_last AND email_address = :p_email;