Search Results partner_value_index

Overview

AMS_DM_PARTY_PROFIT_V is a database view owned by the Oracle Marketing (AMS) module and is delivered as part of the Oracle E-Business Suite 12.1.1 and 12.2.2 codebase. Its purpose is to expose profitability metrics for parties stored in the Trading Community Architecture (TCA) so that the seeded data mining profitability data source can consume them. In other words, the view acts as a reporting contract between the underlying customer profitability data and the Oracle Marketing data mining engine, normalizing measures such as profit contribution, profit percentile, relationship expense, allocated equity, return on equity, and contribution after capital charge into a single flat record per party. Because it is defined at the party (customer) level, it enables segmentation, ranking, and scoring of customers for marketing campaigns, loyalty programs, and analytical dashboards without requiring report authors to know the physical schema of the profitability source. The view is a read-only presentation layer rather than a transactional object, and its implementation status may vary across environments — in the documented metadata it is marked as "Not implemented in this database," meaning it is a seeded definition that only materializes where the data mining profitability source has been installed and configured.

Underlying Base Objects

The documented metadata lists no referenced base objects and no explicit owner, which indicates the view is a thin projection over a profitability or data-warehouse staging structure rather than being defined directly against a base transaction table such as HZ_CUST_ACCOUNTS. The column names in the view text — PROFIT_CONTRIB, PROFIT_PERCENTILE, RELATIONSHIP_EXP, ALLOCATED_EQUITY, CUR_NET_BOOK_BAL, PTD_BALANCE, PRI_ACCOUNTS, and NUMERIC_MEASURE01 through NUMERIC_MEASURE05 — are characteristic of an analytical or extract table populated by a profitability engine. The view therefore sits one layer above that staging table, renaming CUSTOMER_ID to PARTY_ID and mapping generic NUMERIC_MEASURE_n columns into semantic buckets (REVENUE1–5, EXPENSE1–5, PROFIT1–5, etc.). This design isolates the data mining data source from changes in the underlying profitability schema and supports the TCA party model by keying the output on the party/customer identifier.

Key Columns

• PARTY_ID — the customer identifier mapped from CUSTOMER_ID; joins to the TCA party model.
• PROFIT / PROFIT_TOTAL — profit contribution for the party.
• PROFIT_PCT — profit percentile used for ranking and decile segmentation.
• RELATIONSHIP_EXPENSE — relationship expense associated with servicing the party.
• TOTAL_EQUITY / TOTAL_ROE — allocated equity and return on equity ratios.
• CONTRIB_AFTER_CPTL_CHG (CACC1–CACC_TOTAL) — contribution after capital charge, the core risk-adjusted profitability measure.
• REVENUE1–REVENUE5 / REVENUE_TOTAL — revenue components and their total.
• EXPENSE1–EXPENSE5 / EXPENSE_TOTAL — expense components and their total.
• PROFIT1–PROFIT5 — profit components mirroring the revenue and expense buckets.
• BALANCE1–BALANCE5 — net book balances for the party.
• ACCOUNTS1–ACCOUNTS5 — count of primary accounts.
• YTD1–YTD4 — period-to-date (PTD_BALANCE) values representing year-to-date figures.
• ISO_CURRENCY_CD — currency code for the monetary measures.
• TRANSACTION1–5, RATIO1–5, VALUE1–5, PARTNER_VALUE_INDEX — placeholder and derived measures, several hard-coded to 1 as defaults.

Common Use Cases and Queries

The view is typically consumed by Oracle Marketing data mining, but it is also useful for ad hoc analysis of customer profitability. Typical scenarios include ranking high-value customers, identifying low-profit segments for retention campaigns, and feeding profitability attributes into scoring models. A representative query to retrieve the top profit contributors is:

SELECT party_id,
       profit,
       profit_pct,
       total_roe,
       iso_currency_cd
FROM   ams_dm_party_profit_v
WHERE  profit_pct >= 90
ORDER  BY profit DESC;

A second common pattern joins the view to TCA to enrich the output with customer names and account context:

SELECT p.party_id,
       p.profit_total,
       p.contrib_after_cptl_chg,
       p.revenue_total,
       p.expense_total
FROM   ams_dm_party_profit_v p
WHERE  p.contrib_after_cptl_chg > 0;

Because the view is not always implemented at the database level, report developers should verify its existence in the target environment before referencing it in concurrent programs, BI Publisher reports, or custom PL/SQL. Where the view is absent, the equivalent profitability staging table or the Oracle Marketing data mining data source configuration should be used instead.