Search Results parent_group




Overview
Explore in AI Chat

Overview

APPS.MSD_SR_SALES_FCST_V is a reporting view in the Oracle E-Business Suite Sales and Operations Planning / Demand Planning schema (MSD), designed to expose forecast and pipeline amounts at the sales-representative group level, normalized across currencies and reporting periods. It consolidates opportunity worksheet forecast data with forecast categories and the GL period calendar, converting all monetary amounts into a global reporting currency using a period-end conversion rate. The view is primarily consumed by Oracle Demand Planning, ETRM (Enterprise Territory and Resource Management) territory analytics, and downstream sales forecasting dashboards.

The "parent_group" reference in this view originates from its inline subquery against JTF_RS_GRP_RELATIONS, which classifies each sales group by hierarchy level. Groups that appear as top-level parents (relation_type = 'PARENT_GROUP') are assigned level 1, while their child groups are assigned level 2. This hierarchy classification drives roll-up reporting and is the primary reason users search for "parent_group" in the context of this object.

Underlying Base Objects

The view is defined over several synonyms and a package:

Key Columns

  • best_forecast_amount / forecast_amount / worst_forecast_amount — three-point forecast estimates, each multiplied by the global currency conversion factor.
  • pipeline_amount / weighted_pipeline_amount — raw and probability-weighted opportunity pipeline values.
  • start_date / end_date — reporting period boundaries joined from GL_PERIODS.
  • forecast_category_name — the category label from AS_FORECAST_CATEGORIES.
  • decode(glp.period_type,...) — a numeric indicator (3=Month, 4=Quarter, 5=Year) for period granularity.
  • lvl — the hierarchy level derived from the PARENT_GROUP logic: 1 for parent groups, 2 for child groups.

Common Use Cases and Queries

Typical usage involves rolling up forecast amounts by hierarchy level, filtering to submitted worksheet lines, or comparing parent versus child group performance.

Example — list parent-level groups and their forecast totals:

  • SELECT sales_group_id, lvl, SUM(forecast_amount) FROM APPS.MSD_SR_SALES_FCST_V WHERE lvl = 1 GROUP BY sales_group_id, lvl;

Example — period comparison by forecast category:

  • SELECT forecast_category_name, start_date, SUM(weighted_pipeline_amount) FROM APPS.MSD_SR_SALES_FCST_V GROUP BY forecast_category_name, start_date;