Results for “bill_to_zip”

18 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MRP_BIS_FORECAST_WB_V is an Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 view owned by the APPS schema and maintained under the Master Scheduling/MRP product family. It functions as a Business Intelligence System (BIS) presentation object, exposing forecast-versus-actual demand data drawn from the Oracle Demand Planning and Oracle Forecasting foundation. The view sits in the reporting layer of the MRP module and is designed to support analytical inquiries that compare forecasted quantities against booked order quantities and actual shipped quantities across an organization, forecast set, demand class, category, product family, item, and customer dimension set.

The object is registered as VALID and its status confirms it is compiled and available for use. For the ETRM 12.2.2 release, the view resolves to a single referenced base object — the MRP_BIS_FORECAST_WB synonym — and exposes a well-defined column list that includes null placeholders for the "ALL_*" selection columns used by the underlying workbook query. In the EBS BI Publisher and Oracle Discoverer reporting contexts, this view is typically consumed to render forecast accuracy and forecast consumption dashboards; the null columns are artifacts of the workbook's row generator and do not carry data.

The user search term "customer_class" maps directly to the CUSTOMER_CLASS column and its companion ALL_CUSTOMER_CLASSES column, both of which are part of this view's customer dimension. The view is therefore the correct starting point for any report that segments forecast demand by customer classification.

Underlying Base Objects

MRP_BIS_FORECAST_WB_V is defined directly over a single referenced base object: the synonym MRP_BIS_FORECAST_WB. The view definition is a simple projection — it selects a fixed list of columns from the base synonym and assigns NULL to the "ALL_*" selector columns (ALL_DEMAND_CLASSES, ALL_CATEGORY_SETS, ALL_PRODUCT_FAMILIES, ALL_CUSTOMER_CLASSES). No joins, unions, or aggregations are present in the documented view text, so the view inherits the grain, filtering behavior, and security context of the underlying workbook. Any change to the base synonym — for example, the addition of a new dimension — would ripple directly into this view's result set unless the view text is recompiled. DBAs should treat MRP_BIS_FORECAST_WB as the authoritative physical object and MRP_BIS_FORECAST_WB_V as its stable, named reporting interface.

Key Columns

Common Use Cases and Queries

This view is used primarily for forecast accuracy analysis, forecast consumption reporting, and demand segmentation by customer class. A typical query comparing forecast to actuals by customer class is:

SELECT ORGANIZATION_CODE, FORECAST_SET, CUSTOMER_CLASS, FORECAST_DATE, SUM(FORECAST_QUANTITY) FCST_QTY, SUM(SHIPPED_QUANTITY) SHIP_QTY, SUM(FORECAST_AMOUNT) FCST_AMT, SUM(SHIPPED_AMOUNT) SHIP_AMT FROM APPS.MRP_BIS_FORECAST_WB_V WHERE FORECAST_SET = :forecast_set GROUP BY ORGANIZATION_CODE, FORECAST_SET, CUSTOMER_CLASS, FORECAST_DATE ORDER BY CUSTOMER_CLASS, FORECAST_DATE;

Filtering on CUSTOMER_CLASS supports customer-segment dashboards, while grouping by CATEGORY or PRODUCT_FAMILY_NUMBER supports product-line variance analysis. Because the view is a flat projection, it can be joined to inventory item and customer master views for enrichment. Access is read-only and governed by APPS schema privileges granted to the reporting or BI responsibility.