Search Results month_period_label

Overview

APPS.CST_BIS_MARGIN_ANALYSIS_V is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite. It is registered in the FND Design Data repository under the BOM product family as BOM.CST_BIS_MARGIN_ANALYSIS_V, and is marked VALID in both 12.1.1 and 12.2.2. The view consolidates order-to-invoice margin data — sales revenue against cost of goods sold — into a single, denormalized reporting structure that spans product, customer, sales organization, geography, and time dimensions.

Its purpose is to serve operational costing and profitability analysis. Rather than joining sales, receiving, costing, and customer master tables at query time, the view exposes a pre-integrated projection suitable for ad hoc margin reporting, BI Publisher datasets, Discoverer/OBIEE extracts, and custom concurrent programs. Because it is a BIS view backed by summary structures, it is intended for read-only analytical consumption, not transactional processing.

Underlying Base Objects

The documented dependency list shows the view is defined over a mix of synonyms, packages, and lookups:

• CST_BIS_MARGIN_SUMMARY and CST_BIS_MARGIN_BUILD — the costing BIS summary and build objects that materialize the margin aggregates consumed by this view.
• AR_LOOKUPS and SO_LOOKUPS — value sets that resolve coded columns such as sales channel and customer class into descriptive text.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — the Trading Community Architecture tables that supply customer name and customer class attributes.
• MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_CATEGORIES_KFV, and MTL_PARAMETERS — item master and category key flexfield views providing item number, primary UOM, and product category.
• RA_SALESREPS_ALL and RA_TERRITORIES — sales representative and territory definitions.
• FND_GLOBAL — the standard EBS package supplying session context (org, user, responsibility) used for row filtering.

These objects are referenced through APPS-owned synonyms, so the view adheres to the standard EBS synonym layer and remains independent of the underlying application schema names.

Key Columns

The view exposes thirty columns. Among the most significant:

• CUSTOMER_CLASS_NAME (VARCHAR2(80)) — the customer classification derived through HZ_PARTIES and AR_LOOKUPS. This is the column most frequently targeted when users search on "customer_class_name", and is commonly used to segment revenue, cost, and margin by customer tier or channel class.
• PRODUCT_CATEGORY (VARCHAR2(163)) and ITEM_NUMBER (VARCHAR2(40)) — product dimension sourced from the MTL category and item key flexfields.
• CUSTOMER_NAME (VARCHAR2(360)), SALES_REP_NAME, SALES_CHANNEL_NAME, TERRITORY_NAME, AREA_NAME, COUNTRY_NAME, and REGION_NAME — the commercial and geographic dimensions.
• YEAR, QUARTER, MONTH, and the accompanying period number, label, and sequence columns — the time dimension, including QTR_PERIOD_LABEL and MONTH_PERIOD_LABEL for calendar-based reporting.
• QUANTITY_INVOICED, QUANTITY_SHIPPED, SALES_REVENUE_VALUE, and COST_OF_GOODS_SOLD_VALUE — the core numeric measures from which margin is calculated.
• LEGAL_ENTITY_NAME and OPERATING_UNIT_NAME — the organizational/ledger dimension.

Common Use Cases and Queries

Typical uses include gross margin reporting by customer class, product category profitability, territory and sales rep performance, and period-over-period revenue-versus-cost trend analysis. A representative query grouping revenue and cost by customer class and period is:

• SELECT CUSTOMER_CLASS_NAME, YEAR, MONTH, SUM(SALES_REVENUE_VALUE) REVENUE, SUM(COST_OF_GOODS_SOLD_VALUE) COGS, SUM(SALES_REVENUE_VALUE - COST_OF_GOODS_SOLD_VALUE) MARGIN FROM APPS.CST_BIS_MARGIN_ANALYSIS_V GROUP BY CUSTOMER_CLASS_NAME, YEAR, MONTH ORDER BY CUSTOMER_CLASS_NAME, YEAR, MONTH;
• Filtering by product category and operating unit for inventory costing review: SELECT PRODUCT_CATEGORY, ITEM_NUMBER, SUM(SALES_REVENUE_VALUE), SUM(COST_OF_GOODS_SOLD_VALUE) FROM APPS.CST_BIS_MARGIN_ANALYSIS_V WHERE OPERATING_UNIT_NAME = :p_org AND YEAR_PERIOD_NUM = :p_period GROUP BY PRODUCT_CATEGORY, ITEM_NUMBER;
• Territory-level margin analysis: SELECT TERRITORY_NAME, SALES_REP_NAME, SUM(SALES_REVENUE_VALUE) - SUM(COST_OF_GOODS_SOLD_VALUE) MARGIN FROM APPS.CST_BIS_MARGIN_ANALYSIS_V GROUP BY TERRITORY_NAME, SALES_REP_NAME;

All columns are exposed in the documented Query Text, enabling direct SELECT against APPS.CST_BIS_MARGIN_ANALYSIS_V with no additional join logic required by the reporting layer.