Results for “ozf_res_cust_prod”
34 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OZF_RES_CUST_PROD is a table in the OZF schema (Oracle Trade Management) within Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to store the customer and product associations for a given user, driving the display of the Account Manager dashboard. In practical terms, the table acts as a personalized filter or preference store: it records which customers and which product attributes (or product attribute/value combinations) a specific resource (user) has chosen to monitor or view on that dashboard. This allows each account manager to see a tailored set of accounts and products rather than the full universe of trade management data.
The heuristic Data Vault classification provided in the metadata is standalone, meaning no foreign-key dependencies from other tables point into it, and its own foreign-key relationship is towards HZ_CUST_ACCOUNTS. A Data Vault modeling suggestion for this object would treat it as a link-like or preference/satellite-style structure connecting a resource (user) to a customer account and, optionally, to bill-to/ship-to site uses and a product attribute. Because it stores user-specific selections rather than core master data, it is best regarded as an operational preference or assignment table rather than a transactional fact table.
Key Information Stored
The table contains 7 documented columns. The most important are:
- RESOURCE_ID – Identifies the resource (typically the user/account manager) for whom the customer and product selections are stored. This is the primary personalization key.
- PARTY_ID – The party identifier associated with the customer or contact context being displayed.
- CUST_ACCOUNT_ID – The customer account for which the record applies; this is the documented foreign key pointing to HZ_CUST_ACCOUNTS.
- BILL_TO_SITE_USE_ID – The bill-to site use reference, narrowing the customer context to a specific bill-to location.
- SHIP_TO_SITE_USE_ID – The ship-to site use reference, narrowing the customer context to a specific ship-to location.
- PRODUCT_ATTRIBUTE – The product attribute being filtered or displayed (for example, a product category or item attribute).
- PRODUCT_ATTR_VALUE – The value of the product attribute that the user has selected.
No primary key or unique index is explicitly documented in the supplied metadata. In the absence of that information, the most plausible business-key candidate is the combination of RESOURCE_ID, CUST_ACCOUNT_ID, and the site-use and product attribute columns, since a single user record would logically be unique across that combination. RESOURCE_ID and CUST_ACCOUNT_ID are the principal business-key candidates; CUST_ACCOUNT_ID also functions as the documented foreign key. Any surrogate key, if present, is not enumerated in the available metadata and should be confirmed against the physical data dictionary.
Common Use Cases and Queries
The primary use case is retrieving dashboard content for a specific account manager. A typical query joins the table to HZ_CUST_ACCOUNTS to resolve customer names and to resource tables for the user, filtering by RESOURCE_ID. For example:
SELECT rcp.cust_account_id, rcp.bill_to_site_use_id, rcp.ship_to_site_use_id,
rcp.product_attribute, rcp.product_attr_value
FROM ozf_res_cust_prod rcp
WHERE rcp.resource_id = :p_resource_id;
Reporting scenarios include auditing which customers each account manager has configured, identifying products or product attributes most frequently selected across the sales organization, and troubleshooting dashboard display issues when a user reports missing accounts or products. Administrators may also query the table to verify that bill-to and ship-to site use references are valid. Because the data is user-specific, queries are usually filtered by RESOURCE_ID or aggregated by PRODUCT_ATTRIBUTE and PRODUCT_ATTR_VALUE to reveal configuration trends.
Related Objects
The documented foreign-key relationship links this table to the following object, and additional related objects are suggested by the column semantics:
- HZ_CUST_ACCOUNTS – Referenced via CUST_ACCOUNT_ID; the authoritative customer account master used to resolve account names and numbers.
- HZ_CUST_ACCT_SITES_ALL – Source of site-use records referenced by BILL_TO_SITE_USE_ID and SHIP_TO_SITE_USE_ID.
- HZ_CUST_SITE_USES_ALL – Defines the bill-to and ship-to site use identifiers used in the table.
- HZ_PARTIES – Source of party information associated with PARTY_ID.
- JTF_RS_RESOURCE_EXTNS / PER_ALL_PEOPLE_F – Resource and person definitions corresponding to RESOURCE_ID.
- OZF_RES_ACC_CUST / OZF dashboard objects – Other OZF Trade Management dashboard and resource-preference tables that operate alongside this object.
Because the object is classified as standalone, no dependent child tables are documented as referencing it; the relationships above flow outward from OZF_RES_CUST_PROD to core Trading Community Architecture and resource entities.
-
Table to store the Customer and Products for a user to show on Account Manager dashboard
-
Table to store the Customer and Products for a user to show on Account Manager dashboard
-
TABLE: OZF.OZF_RES_CUST_PROD 12.1.1
-
TABLE: OZF.OZF_RES_CUST_PROD 12.2.2
-
VIEW: OZF.OZF_RES_CUST_PROD# 12.2.2
-
VIEW: OZF.OZF_RES_CUST_PROD# 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - OZF Tables and Views 12.2.2
OZF_XREF_MAP table created for SIebel TPM Integration
-
eTRM - OZF Tables and Views 12.1.1
Table to store the Market eligibilty for a Offer Worksheet
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - OZF Tables and Views 12.1.1
Table to store the Market eligibilty for a Offer Worksheet
-
eTRM - OZF Tables and Views 12.2.2
OZF_XREF_MAP table created for SIebel TPM Integration