Results for “primary_flag”

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

Overview

The CS_SR_HZ_CONT_PTS_EMAILS_V view is a Service (CS) module database object owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a filtered, denormalized projection of contact point email records drawn from the Trading Community Architecture (TCA) model, restricted to parties and joined to lookup metadata. Its principal role is to expose email contact points in a form readily consumable by Service-related forms, concurrent programs, and reporting or integration logic that must resolve the email address, contact point classification, and status for a given party.

By centralizing the join between HZ_CONTACT_POINTS and AR_LOOKUPS and by pre-filtering on CONTACT_POINT_TYPE = 'EMAIL' and OWNER_TABLE_NAME = 'HZ_PARTIES', the view shields callers from repetitive predicate logic and from handling the outer join to lookup meanings. This makes it a practical source for Service Request notification and escalation workflows that need to identify a party's primary or active email address.

Underlying Base Objects

The view is defined over two documented referenced objects:

• HZ_CONTACT_POINTS (documented as a SYNONYM pointing to the TCA contact point entity) — the driving table supplying email addresses, contact point type, primary flag, status, timezone, and owner identifiers.
• AR_LOOKUPS (VIEW) — the lookup source supplying the human-readable meaning for the communication type via an outer join.

The join is an outer join on AR.LOOKUP_CODE where AR.LOOKUP_TYPE = 'COMMUNICATION_TYPE', ensuring rows are not dropped when a matching lookup meaning is absent. The OWNER_TABLE_NAME = 'HZ_PARTIES' predicate restricts results to contact points owned by parties rather than by other TCA entities.

Key Columns

• EMAIL — the email address (CP.EMAIL_ADDRESS); the primary payload of the view.
• CONT_POINT_TYPE_MEANING — decoded meaning of the contact point type from AR_LOOKUPS.
• OWNER_TABLE_ID — identifier of the owning entity (the party) that owns the contact point.
• CONTACT_POINT_ID — unique surrogate key of the contact point record.
• TIMEZONE_ID — timezone associated with the contact point.
• CONTACT_POINT_TYPE — raw type code; always 'EMAIL' by virtue of the view's filter.
• PRIMARY_FLAG — indicates whether this is the party's primary email contact point.
• STATUS — lifecycle status of the contact point.

Common Use Cases and Queries

Typical scenarios include retrieving a party's active email addresses for Service Request notifications, identifying the primary email for a contact, and validating contact point status before dispatch.

Retrieve all emails for a specific party:

SELECT email, primary_flag, status
FROM   cs_sr_hz_cont_pts_emails_v
WHERE  owner_table_id = :party_id
AND    status = 'A';

Fetch only the primary email:

SELECT email
FROM   cs_sr_hz_cont_pts_emails_v
WHERE  owner_table_id = :party_id
AND    primary_flag = 'Y';

Because the view performs no BILL_TO or SITE restrictions, additional party-site context must be sourced from related TCA tables when required. Queries should always constrain on OWNER_TABLE_ID or CONTACT_POINT_ID to avoid full scans of the underlying contact point entity.