Results for “product_cat_set_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
ASF_WIN_LOSS_PRODCAT_MV is a materialized view owned by the APPS schema in Oracle E-Business Sales Online (ASF), the foundation module underlying Oracle Sales, Oracle TeleSales, and Oracle Partners products. It stores aggregated win/loss performance metrics broken down by product category, sales resource, and sales group, and is consumed by sales management dashboards, pipeline analytics, and quota attainment reporting. In EBS 12.1.1 the documented physical schema exposes 13 columns; the object remains VALID in 12.2.2 and is queried through the same APPS synonym. Because the object is materialized, its contents reflect the state of the underlying transactional tables at the time of the most recent refresh, so latency between the base tables (opportunity and product category data) and this view must be accounted for in operational reporting.
Key Information Stored
The documented metadata classifies ASF_WIN_LOSS_PRODCAT_MV as standalone under a heuristic Data Vault assessment. In Data Vault terms a materialized aggregate of this shape most closely resembles a satellite, since each row describes measurable outcome attributes (won and loss counts) attached to a business key rather than acting as an independent hub or an associating link.
- PRODUCT_CATEGORY_ID and PRODUCT_CAT_SET_ID — the product category and its category set, forming the primary analytical grain of the view.
- WON and LOSS — aggregated counts or amounts of successful and unsuccessful sales outcomes per category.
- SALESFORCE_ID — foreign key to AS_SALESFORCE, identifying the sales organization whose performance is summarized.
- CREDIT_TYPE_ID — foreign key to IGS_FI_CR_TYPES_ALL, indicating the credit type associated with the win/loss record.
- PARENT_RESOURCE_ID, SALES_GROUP_ID, and PARENT_GROUP_ID — hierarchical identifiers enabling roll-up reporting across resource and group structures.
- FORECAST_ROLLUP_FLAG — indicates whether the row participates in forecast aggregation.
- CURRENCY_CODE, CONVERSION_PERIOD_TYPE, and CONVERSION_PERIOD_NAME — currency and period context used for monetary conversion.
The view's uniqueness is derived from the combination of product category, category set, and the resource/group dimensions rather than from a single surrogate key column, which is typical of aggregate materialized views.
Common Use Cases and Queries
Typical scenarios include win rate analysis by product category, period-over-period comparison of wins and losses, and roll-up of results to parent sales groups. A representative query pattern joining the two documented foreign keys is:
- Win rate by category:
SELECT p.product_category_id, p.won, p.loss, (p.won / NULLIF(p.won + p.loss,0)) win_rate FROM asf_win_loss_prodcat_mv p WHERE p.forecast_rollup_flag = 'Y' - Salesforce-scoped performance: join
p.salesforce_id = s.salesforce_idto AS_SALESFORCE to filter results by organization. - Credit-type reporting: join
p.credit_type_id = c.credit_type_idto IGS_FI_CR_TYPES_ALL to break results down by credit type. - Currency normalization using CURRENCY_CODE together with CONVERSION_PERIOD_TYPE and CONVERSION_PERIOD_NAME for period-consistent financial roll-ups.
Related Objects
The documented foreign keys identify the principal dependencies. AS_SALESFORCE (joined on SALESFORCE_ID) supplies the sales organization context, and IGS_FI_CR_TYPES_ALL (joined on CREDIT_TYPE_ID) supplies credit-type definitions. The product category columns (PRODUCT_CATEGORY_ID, PRODUCT_CAT_SET_ID) reference the standard EBS product category structures, commonly FND_ID_FLEX_STRUCTURES and the category set tables in the inventory/advanced pricing schema. Because this object is a materialized view, it depends on the underlying base tables for opportunities and product category assignments; its refresh schedule should be verified prior to relying on it for near-real-time reporting.
-
Resolving table between AS_FORECAST_CATEGORIES and AS_INTEREST_TYPES_B
-
Define interest statuses
-
Define interest statuses
-
Define Interest types - base table
-
View: AST_INV_ITEM_LOV_V 12.1.1
APPS.AST_INV_ITEM_LOV_V·↳ ENI_PROD_DEN_HRCHY_PARENTS_V·↳ MTL_ITEM_CATEGORIES·↳ MTL_SYSTEM_ITEMS_B_KFV·Explore AST module →
-
Hold purchase line change history
-
Define Interest types - base table
-
View: AS_INTERESTS 12.2.2
Interests (multi-org)
-
APPS.AST_LM_OPP_QUICK_INTTYPES_V·↳ AS_LEADS_ALL·↳ AS_LEAD_LINES_ALL·↳ AS_SALES_STAGES_ALL_TL·Explore AST module →
-
Mapping table between plan elements in osc and forecast
-
Define Interest code - Base table
-
Hold purchase line change history
-
View: AST_SALES_LEAD_LINES_V 12.2.2
APPS.AST_SALES_LEAD_LINES_V·↳ AMS_SOURCE_CODES·↳ AS_SALES_LEAD_LINES·↳ ENI_PROD_DEN_HRCHY_PARENTS_V·Explore AST module →
-
View: AS_LEAD_LINES 12.1.1
Sales opportunity lines (multi-org)
-
Resolving table between AS_FORECAST_CATEGORIES and AS_INTEREST_TYPES_B
-
View: AST_INV_ITEM_LOV_V 12.2.2
APPS.AST_INV_ITEM_LOV_V·↳ ENI_PROD_DEN_HRCHY_PARENTS_V·↳ MTL_ITEM_CATEGORIES·↳ MTL_SYSTEM_ITEMS_B_KFV·Explore AST module →
-
Stores product interests, customer and opportunity classifications
-
Stores product interests, customer and opportunity classifications
-
View: AST_SALES_LEAD_LINES_V 12.1.1
APPS.AST_SALES_LEAD_LINES_V·↳ AMS_SOURCE_CODES·↳ AS_SALES_LEAD_LINES·↳ ENI_PROD_DEN_HRCHY_PARENTS_V·Explore AST module →
-
APPS.AST_CONT_CLASSIFICATION_INT_V·↳ AS_INTERESTS_ALL·↳ AS_LOOKUPS·↳ ENI_PROD_DEN_HRCHY_PARENTS_V·Explore AST module →
-
View: AS_LEAD_LINES 12.2.2
Sales opportunity lines (multi-org)
-
This table will hold all the revenue objectives for each of the account plans
-
Table to store the forecast information on all possible product categories for individual or sales group
-
View: AS_INTEREST_TYPES_VL 12.1.1
Interest types (single org, single language view)
APPS.AS_INTEREST_TYPES_VL·↳ AS_INTEREST_TYPES_B·↳ AS_INTEREST_TYPES_TL·Explore AS module →
-
View: AS_INTEREST_TYPES_VL 12.2.2
Interest types (single org, single language view)
APPS.AS_INTEREST_TYPES_VL·↳ AS_INTEREST_TYPES_B·↳ AS_INTEREST_TYPES_TL·Explore AS module →
-
stores the ship and debit request line information
-
Mapping table between plan elements in osc and forecast
-
View: AS_INTEREST_CODES_VL 12.1.1
MLS Compliant view on _B and _TL tables.
APPS.AS_INTEREST_CODES_VL·↳ AS_INTEREST_CODES_B·↳ AS_INTEREST_CODES_TL·Explore AS module →
-
View: AS_OPPORTUNITY_LINES_V 12.1.1
APPS.AS_OPPORTUNITY_LINES_V·↳ AMS_P_SOURCE_CODES_V·↳ AS_LEAD_LINES_ALL·↳ ENI_PROD_DEN_HRCHY_PARENTS_V·Explore AS module →
-
View: AS_OPPORTUNITY_LINES_V 12.2.2
APPS.AS_OPPORTUNITY_LINES_V·↳ AMS_P_SOURCE_CODES_V·↳ AS_LEAD_LINES_ALL·↳ ENI_PROD_DEN_HRCHY_PARENTS_V·Explore AS module →
-
Denormalized table to store opportunity data denormalized from AS_LEADS_ALL, AS_LEAD_LINES_ALL, AS_SALES_CREDITS, AS_SALES_STAGE_ALL, AS_INTEREST_TYPES_ALL, AS_INTEREST_CODES_ALL, HZ_PARTIES, AS_SALES_GROUPS, PER_ALL_PEOPLR_F
-
APPS.AST_LM_OPP_QUICK_INTTYPES_V·↳ AS_LEADS_ALL·↳ AS_LEAD_LINES_ALL·↳ AS_SALES_STAGES_ALL_TL·Explore AST module →
-
View: AS_INTERESTS 12.1.1
Interests (multi-org)
-
Holds sales opportunity lines
-
APPS.AST_OPPORTUNITY_LINES_V·↳ AMS_P_SOURCE_CODES_V·↳ AS_LEAD_LINES_ALL·↳ ENI_PROD_DEN_HRCHY_PARENTS_V·Explore AST module →
-
This table will hold all the revenue objectives for each of the account plans
-
Table to store the forecast information on all possible opportunities for individual or sales group
-
Denormalized table to store opportunity data denormalized from AS_LEADS_ALL, AS_LEAD_LINES_ALL, AS_SALES_CREDITS, AS_SALES_STAGE_ALL, AS_INTEREST_TYPES_ALL, AS_INTEREST_CODES_ALL, HZ_PARTIES, AS_SALES_GROUPS, PER_ALL_PEOPLR_F
-
View: AS_INTEREST_CODES_VL 12.2.2
MLS Compliant view on _B and _TL tables.
APPS.AS_INTEREST_CODES_VL·↳ AS_INTEREST_CODES_B·↳ AS_INTEREST_CODES_TL·Explore AS module →
-
Define Interest code - Base table
-
stores the ship and debit request line information
-
APPS.AST_CONT_CLASSIFICATION_INT_V·↳ AS_INTERESTS_ALL·↳ AS_LOOKUPS·↳ ENI_PROD_DEN_HRCHY_PARENTS_V·Explore AST module →