Results for “bic_sumv_satisfaction”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
BIC_SUMV_SATISFACTION is a read-only database view belonging to the BIC — Customer Intelligence product family within Oracle E-Business Suite. In the ETRM metadata it is classified under the legacy/obsolete Customer Intelligence module. The view is designed to surface aggregated customer satisfaction metrics at the party level, partitioned by organizational and calendar dimensions, so that satisfaction measurements can be reported alongside customer category, market segment, and geography.
The object presents a denormalized reporting surface rather than a transaction-processing entity. Its purpose is to support analytical queries, dashboards, and extract routines that monitor satisfaction trends over accounting periods, quarters, and halves. The ETRM entry explicitly documents that BIC_SUMV_SATISFACTION is not implemented in the reference database, meaning no physical instance exists there; the object is documented for completeness and compatibility. This is characteristic of Customer Intelligence objects that were superseded as the product moved toward the Trade Management and Customer Intelligence 11i/12.x lineage.
Underlying Base Objects
The view text is a simple projection with no joins, filters, or aggregation logic inside the definition itself. It is defined over a single base object: BIC_PARTY_SUMM_V, another Customer Intelligence summary view, and is declared WITH READ ONLY. The ETRM metadata records no additional referenced base tables, indicating that any joins to customer, party, or segment masters occur below BIC_PARTY_SUMM_V rather than inside this view.
This single-source structure means BIC_SUMV_SATISFACTION inherits all partitioning and materialization behavior from BIC_PARTY_SUMM_V. Any performance characteristic — indexing, refresh cadence, or collection program — is governed by the underlying summary view and its supporting summary tables, not by this object.
Key Columns
- PERIOD_START_DATE / START_DATE — The accounting or reporting period begin date anchoring the satisfaction measurement.
- VALUE — The numeric satisfaction metric for the row; the core measure of the view.
- ORG_ID — Operating unit identifier, enabling multi-org filtering and row-level security by organization.
- CUSTOMER_CATEGORY_FK / MARKET_SEGMENT_FK — Foreign keys to customer classification and market segmentation, supporting roll-ups and comparative reporting.
- PARTY_ID — The customer or party for whom the satisfaction value is recorded.
- COUNTRY / CITY / STATE — Geographic attributes supporting regional analysis.
- ACT_PERIOD_NAME, ACT_PERIOD_START_DATE, ACT_PERIOD_END_DATE, ACT_PERIOD_NUM — The active accounting period descriptors, aligned to the General Ledger calendar.
- ACT_YEAR, ACT_QUARTER, ACT_HALF_YEAR — Calendar hierarchy attributes for time-series aggregation.
- ACT_YEAR_START_DATE, ACT_QUARTER_START_DATE — Period boundary dates used for fiscal-to-date and quarter-to-date calculations.
Common Use Cases and Queries
The view supports satisfaction trend analysis, segmentation comparisons, and geographic breakdowns. Because it is read-only and inherits its aggregation from BIC_PARTY_SUMM_V, queries are typically simple selects with grouping and filtering rather than complex joins. A representative query follows:
SELECT act_year, act_quarter, country, SUM(value) sat_total, COUNT(DISTINCT party_id) parties FROM bic_sumv_satisfaction WHERE org_id = :p_org AND act_year = :p_year GROUP BY act_year, act_quarter, country ORDER BY act_year, act_quarter;— quarterly satisfaction totals by country.SELECT customer_category_fk, market_segment_fk, AVG(value) avg_sat FROM bic_sumv_satisfaction WHERE act_period_start_date BETWEEN :p_from AND :p_to GROUP BY customer_category_fk, market_segment_fk;— average satisfaction by customer and market segment.SELECT act_period_name, value FROM bic_sumv_satisfaction WHERE party_id = :p_party_id ORDER BY act_period_start_date;— a single party's satisfaction history.
In integration scenarios the view serves as a source for ETL extracts feeding external analytics or a data warehouse. Note that since the object is documented as obsolete and not implemented, confirmation against the target instance is required before use.
-
View: BIC_SUMV_SATISFACTION 12.1.1
Not implemented in this database·Explore BIC module →
-
View: BIC_SUMV_SATISFACTION 12.2.2
Not implemented in this database·Explore BIC module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1