Search Results customer_bill_id




Overview
Explore in AI Chat

Overview

APPS.MRPBV_FORECASTS is a Business Intelligence System (BIS) view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as MRP.MRPBV_FORECASTS and reported with a status of VALID. The view presents an estimate of future demand on inventory items. Each row represents a forecast entry carrying the original and current forecast quantities — before and after consumption — together with the confidence factor and any specific customer information associated with the demand. Because it is a BIS view, its intended role is read-only reporting, extraction, and integration rather than transactional maintenance; it exposes denormalized, human-readable attributes such as organization code and organization name alongside the underlying surrogate identifiers, allowing report authors and downstream systems to avoid repetitive joins to master data tables.

Underlying Base Objects

Per the documented dependency information, APPS.MRPBV_FORECASTS references three base objects through APPS-owned synonyms: HR_ALL_ORGANIZATION_UNITS, MRP_FORECAST_DESIGNATORS, and MTL_PARAMETERS. HR_ALL_ORGANIZATION_UNITS supplies the organization context, which is why the view can project ORGANIZATION_CODE and ORGANIZATION_NAME without a manual join to the organization definitions. MTL_PARAMETERS provides the inventory organization parameters that qualify a valid inventory organization, ensuring that forecast rows are reported in the context of a defined inventory organization. MRP_FORECAST_DESIGNATORS is the core forecasting table in the MRP schema and supplies the forecast name, description, forecast set, demand class, inactive date, and the customer identifiers. The metadata explicitly states that APPS.MRPBV_FORECASTS is not referenced by any other database object, confirming its position as a terminal, consumer-facing view.

Key Columns

  • ORGANIZATION_CODE, ORGANIZATION_NAME — the inventory organization short code and descriptive name, derived from HR_ALL_ORGANIZATION_UNITS.
  • FORECAST_NAME (10), FORECAST_DESCRIPTION (50) — the identifier and free-text description of the forecast.
  • FORECAST_SET_NAME (10), DEMAND_CLASS (30), INACTIVE_DATE — the forecast set grouping, demand class used for consumption and prioritization, and the date on which the forecast becomes inactive.
  • ORGANIZATION_ID — the numeric inventory organization identifier.
  • CUSTOMER_ID, CUSTOMER_SHIP_ID, CUSTOMER_BILL_ID — the customer, ship-to, and bill-to identifiers associated with the forecasted demand. CUSTOMER_BILL_ID is the column most relevant to the search term "customer_bill_id"; it identifies the bill-to customer for the forecast line, allowing reporting by paying customer independently of the ship-to destination.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS audit columns.

Common Use Cases and Queries

The view is typically used for forecast consumption analysis, demand-by-customer reporting, and data extraction into planning or BI systems. A common pattern filters by organization and active forecasts:

SELECT organization_code, forecast_name, demand_class,
       customer_id, customer_bill_id, inactive_date
FROM   apps.mrpv_forecasts
WHERE  organization_id = :org_id
AND    (inactive_date IS NULL OR inactive_date > SYSDATE);

To aggregate forecasted demand by bill-to customer, the CUSTOMER_BILL_ID column can be grouped directly against customer master data. Because the view already carries organization name and code, no additional join to HR_ALL_ORGANIZATION_UNITS is required. For integration, the full column list can be selected and staged into a planning interface table, with audit columns supporting incremental extraction based on LAST_UPDATE_DATE.