Search Results ra_site_uses_all




Overview
Explore in AI Chat

Overview

MRPFV_FORECASTS is an APPS-owned read-only view in the Oracle E-Business Suite Master Scheduling/MRP product family. It presents forecast designator records from MRP_FORECAST_DESIGNATORS joined to organization and customer master data, exposing forecast consumption information in a business-friendly format. The view is defined with the WITH READ ONLY clause, so it is intended exclusively for reporting, inquiry, and integration extracts rather than for transactional DML.

The "FV" prefix indicates a forecast view, and its primary business purpose is to answer the question of which customers, ship-to and bill-to addresses, and demand classes are associated with each forecast designator. Because it resolves customer IDs into customer names and numbers and resolves site-use IDs into actual street addresses, it removes the need for report authors to repeatedly re-implement the join logic. The view also embeds a security predicate (_SEC:DE.ORGANIZATION_ID) that enforces organization-level access, making it suitable for use in multi-org deployments without exposing data across operating units.

Underlying Base Objects

The documented base objects referenced by the view include MTL_PARAMETERS, HR_ALL_ORGANIZATION_UNITS, MRP_FORECAST_DESIGNATORS, and, via the customer model, HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES. Note that the view text documented in ETRM references the older RA_* tables (RA_CUSTOMERS, RA_SITE_USES_ALL, RA_ADDRESSES_ALL); in 12.1.1 and 12.2.2 these RA_ objects are retained as synonyms or compatibility views over the HZ_ (Trading Community Architecture) tables, so the logical structure is unchanged.

The driving table is MRP_FORECAST_DESIGNATORS, filtered by FORECAST_SET IS NOT NULL. MTL_PARAMETERS and HR_ALL_ORGANIZATION_UNITS supply the organization code and organization name respectively. The customer, site-use, and address tables are joined with outer joins ((+)) on CUSTOMER_ID, BILL_ID, and SHIP_ID, so forecasts without a defined customer or address still appear with null customer and address columns.

Key Columns

Common Use Cases and Queries

Typical uses include validating forecast setup before a planning run, auditing which customers are linked to a designator, and feeding forecast metadata into custom reports or interfaces.

List active forecast designators for an organization:

  • SELECT forecast_name, forecast_set_name, customer_name FROM mrfv_forecasts WHERE organization_code = :org AND (inactive_date IS NULL OR inactive_date > SYSDATE);

Review ship-to linkage for forecasting accuracy:

  • SELECT forecast_name, customer_number, customer_ship_address FROM mrfv_forecasts WHERE forecast_set_name = :set_name ORDER BY forecast_name;

Because the view enforces the organization security predicate, queries return only organizations to which the executing user has access, which is useful when building cross-organization dashboards. When the source for a query mentions ra_site_uses_all, this view is the supported, customer-model-consistent alternative, since it exposes the resolved site-use and address information without requiring direct joins to the transactional site-use table.