Results for “org_contact_role_id”

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

Overview

OZF_CUST_PROD_CONT is a Trade Management (OZF) view in the APPS schema that consolidates customer, product, and contact associations used by Oracle Trade Management. In Oracle EBS 12.1.1 and 12.2.2, the view exposes the intersection of a customer (or customer account/site), a product hierarchy node, and an organization contact, allowing Trade Management functionality — such as trade promotions, offers, and accruals — to resolve which contacts are associated with which products for a given customer. Because it is an operational (Multi-Org) view, it enforces Org ID security by restricting visibility to the current operating unit as determined through USERENV('CLIENT_INFO').

Underlying Base Objects

The view is defined over a single base object: OZF_CUST_PROD_CONT_ALL, which is exposed via a synonym. OZF_CUST_PROD_CONT is the multi-org secured layer over that _ALL table. The WHERE clause compares the row's ORG_ID against the client's session Org ID derived via DECODE(SUBSTR(USERENV('CLIENT_INFO'),1,10)). Following standard EBS multi-org view design, this means the view returns only records belonging to the operating unit of the session (or records where ORG_ID is null, defaulted to -99 per the NVL logic).

Key Columns

• CUST_PROD_CONTACT_ID — Primary key/unique identifier for the customer-product-contact association row.
• CUSTOMER_ID / PARTY_SITE_USE_ID / CUST_ACCOUNT_ID / CUST_ACCT_SITE_ID — Identify the customer party, party site use, customer account, and account site involved in the association.
• PRODUCT_HIERARCHY — The product hierarchy (category set) within which the product node is defined.
• PRODUCT_LEVEL — The hierarchy level at which the association applies.
• PRODUCT_LEVEL_VALUE — The specific product/category value at the identified level, representing the product to which the contact relationship applies. This is the column referenced in the user's search and is central to resolving product-specific contact assignments.
• ORG_CONTACT_ID / ORG_CONTACT_ROLE_ID / PERSON_ID — The organization contact record, its role, and the underlying person.
• PARTY_SITE_ID — The party site associated with the contact.
• CREATED_FROM — Indicates the origin/source of the record creation.
• Standard WHO columns — OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN for concurrency and audit.
• Concurrent program columns — REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE for traceability of batch loads.
• ORG_ID — Operating unit; used by the multi-org view filter.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield (DFF) columns for extensibility.

Common Use Cases and Queries

Typical use cases include resolving which organization contacts are responsible for a product at a customer account, supporting trade promotion targeting, and extracting data for reporting or integration into external trade planning systems. The view is Org-secured, so the querying session must have an operating unit context set.

Sample query to list product-level contact associations for the current operating unit:

SELECT cust_prod_contact_id,
       customer_id,
       cust_account_id,
       product_hierarchy,
       product_level,
       product_level_value,
       org_contact_id,
       person_id,
       org_contact_role_id
FROM   ozf_cust_prod_cont
WHERE  product_level_value = :product_value;

To join contact associations to customer account details:

SELECT c.product_level_value,
       c.customer_id,
       c.cust_account_id,
       c.org_contact_id,
       p.person_first_name,
       p.person_last_name
FROM   ozf_cust_prod_cont c,
       hz_parties h
WHERE  h.party_id = c.person_id
AND    c.cust_account_id = :cust_account_id;

Because the view is a thin, secured projection of OZF_CUST_PROD_CONT_ALL, developers requiring cross-operating-unit visibility (for example, during data migration or reconciliation) query the _ALL base table directly, while application and reporting code should generally use OZF_CUST_PROD_CONT to respect operating unit security.