Search Results sales_pct




Overview
Explore in AI Chat

Overview

APPS.ICX_CST_TERRITORY_7DAY_V is a reporting view in the Oracle E-Business Suite ETRM (Enterprise Territory and Resource Management) module. It presents a seven-day rolling summary of invoiced revenue and margin performance aggregated by sales territory. The view is designed primarily for the Oracle iStore / Customer Self-Service margin analytics dashboards and web-based reporting pages, where it supplies territory-level revenue and margin ratio metrics for a fixed lookback period of seven days.

The view carries the naming prefix ICX, indicating that it belongs to the customer-facing (Internet Computing) application schema associated with Oracle iStore and related self-service web applications. Its data is consumed by margin analysis web pages rather than by transactional processing. Because the period filter is hard-coded as 7D and the aggregation window is anchored on the current date, the view reflects near-real-time performance over the trailing week, recalculated each time it is queried.

The presence of the SALES_PCT column—the term that frequently drives searches such as sales_pct—reflects the view's principal role: expressing each territory's invoiced amount as a percentage of total enterprise sales for the same seven-day window. This normalization makes the view suitable for ranked or comparative territory displays.

Underlying Base Objects

The view is defined over three documented base objects, joined as follows:

  • ICX_MARGIN_ANALYSIS MA — the primary fact source, supplying INVOICED_AMOUNT, MARGIN, TERRITORY_ID, ORG_ID, BUILD_ID, and PERIOD. The view filters on MARGIN IS NOT NULL and PERIOD = '7D'.
  • CST_MARGIN_BUILD MB — joined to ICX_MARGIN_ANALYSIS on BUILD_ID, providing the margin build context for the summarized run.
  • RA_TERRITORIES RT — joined on TERRITORY_ID with an outer join (RT.TERRITORY_ID(+)), supplying the territory name (RT.NAME) while allowing territory rows that may not resolve to a defined territory record.

Multi-org security is enforced through USERENV('CLIENT_INFO'), which extracts the operating unit identifier from the session client information and compares it against MA.ORG_ID. When the client information is blank, the comparison defaults to -99, effectively restricting or neutralizing results depending on session context. The grouping key combines TO_DATE, TERRITORY_ID, PERIOD, and RT.NAME.

Key Columns

  • TERRITORY_ID — identifier of the sales territory the metrics are aggregated for.
  • PERIOD — always 7D in results, since the HAVING clause restricts the period.
  • RT.NAME — the descriptive territory name sourced from RA_TERRITORIES.
  • SUM(INVOICED_AMOUNT) — total invoiced revenue for the territory over the period.
  • SUM(MARGIN) — total margin for the territory over the period.
  • CUSTOMER_MARGIN_PCT — margin as a percentage of invoiced amount, rounded to two decimals; returns NULL when invoiced amount is zero.
  • SALES_PCT — the territory's invoiced amount divided by the organization-wide total sales for the period, returned by ICX_MARGIN_WEB_ANA_PKG.ICX_GET_TOTAL_SALES('7D'); NULL when the total is zero.
  • MARGIN_PCT — the territory's margin divided by the organization-wide total margin from ICX_GET_TOTAL_MARGIN('7D'); NULL when the total is zero.
  • TO_DATE and TO_DATE - 7 — the closing and opening dates of the rolling analysis window.

Common Use Cases and Queries

The view is typically queried to power territory performance rankings, contribution analysis, and margin dashboards. A representative query ranks territories by share of sales:

  • SELECT territory_id, name, sales_pct, margin_pct, customer_margin_pct FROM apps.icx_cst_territory_7day_v ORDER BY sales_pct DESC;
  • Comparing margin contribution across territories: SELECT name, SUM(margin) FROM apps.icx_cst_territory_7day_v GROUP BY name ORDER BY 2 DESC;
  • Filtering low-margin territories: SELECT name, customer_margin_pct FROM apps.icx_cst_territory_7day_v WHERE customer_margin_pct < 10;

Because the view is not documented with a formal owner in the ETRM 12.2.2 metadata repository, administrators should treat it as an internal supporting object for the margin web analytics package rather than a supported public interface. Querying it directly is common for troubleshooting and ad hoc reporting, but production integrations should favor the packaged APIs within ICX_MARGIN_WEB_ANA_PKG where equivalent functionality is exposed.