Search Results customer_ship_id




Overview
Explore in AI Chat

Overview

APPS.MRPBV_FORECASTS is a Business Intelligence System (BIS) view in the Oracle E-Business Suite APPS schema, registered under FND Design Data as MRP.MRPBV_FORECASTS. The view presents an estimate of future demand on inventory items. Each row represents a forecast entry and exposes both the original and current forecast quantities (before and after consumption), the associated confidence factor, and any specific customer information attached to the demand. As a BIS view, it is intended primarily for reporting, ad hoc query, and integration rather than for transactional write operations, and it is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2.

The view is not referenced by any other database object, so it functions as a terminal reporting object layered on top of the MRP forecast designator tables. Because it resolves organization context, forecast set names, and customer identifiers into a single denormalized projection, it reduces the join complexity normally required to report on forecast demand.

Underlying Base Objects

The ETRM dependency metadata documents that MRPBV_FORECASTS references the following base objects through APPS synonyms:

The view therefore acts as a controlled, read-only projection over the forecast designator data, enriched with organization master information. It does not carry FND audit columns other than the standard LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY inherited from the base records.

Key Columns

  • ORGANIZATION_CODE / ORGANIZATION_NAME — the inventory organization short code and full description, resolved from the organization units table.
  • FORECAST_NAME (VARCHAR2 10) and FORECAST_DESCRIPTION (VARCHAR2 50) — identify and describe the forecast designator.
  • FORECAST_SET_NAME (VARCHAR2 10) — groups related forecast entries into a forecast set.
  • DEMAND_CLASS (VARCHAR2 30) — categorizes the demand, typically aligning with demand class usage in planning and ATP.
  • INACTIVE_DATE — the date the forecast entry becomes inactive.
  • ORGANIZATION_ID — the numeric inventory organization identifier.
  • CUSTOMER_ID — the customer party associated with the forecast demand.
  • CUSTOMER_SHIP_ID — the ship-to site identifier for the customer associated with the forecast. This is the column of interest for site-level demand reporting and is the field matched by the search on customer_ship_id.
  • CUSTOMER_BILL_ID — the bill-to site identifier for the customer.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY provide record lineage and change tracking.

Common Use Cases and Queries

This view is typically used to report forecast demand by organization, forecast set, demand class, and customer site. A recurring scenario is identifying all forecast entries tied to a specific ship-to site, which is precisely what a search on customer_ship_id retrieves.

Example — list forecast entries by customer ship-to site:

  • SELECT organization_code, forecast_name, forecast_set_name, demand_class, customer_id, customer_ship_id, customer_bill_id, inactive_date FROM apps.mrpbv_forecasts WHERE customer_ship_id = :p_ship_id;

Example — summarize active forecast entries by organization and demand class:

  • SELECT organization_id, demand_class, COUNT(*) FROM apps.mrpbv_forecasts WHERE inactive_date IS NULL OR inactive_date > SYSDATE GROUP BY organization_id, demand_class ORDER BY organization_id, demand_class;

Because the view resolves organization names and customer references, it is well suited to Cognos, OBIEE, and custom concurrent-program extracts where site-level forecast visibility is required without navigating the underlying designator and organization joins directly.