Search Results customer_ship_address

Overview

APPS.MRPFV_FORECASTS is a Business Intelligence System (BIS) view in Oracle E-Business Suite registered under the FND Design Data identifier MRP.MRPFV_FORECASTS. It exposes forecast demand data originating from Oracle Master Scheduling/MRP and Advanced Supply Chain Planning, presented in a denormalized, business-friendly format. The view describes estimates of future demand on inventory items, including original and current forecast quantities (before and after consumption), confidence information, and customer-specific attributes such as ship-to and bill-to addresses.

The object is owned by the APPS schema and carries a status of VALID in both Oracle EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it holds no data of its own; it projects columns from underlying MRP and Trading Community Architecture (TCA) objects. Its design intent is reporting and integration — providing a stable, readable interface for forecast records that would otherwise require multi-table joins across the MRP and HZ schemas. The view is not referenced by any other database object, so it functions purely as a reporting endpoint.

Underlying Base Objects

The view is defined over the following documented base objects, all accessed through APPS synonyms:

• MRP_FORECAST_DESIGNATORS — the primary MRP source supplying forecast name, description, set name, demand class, inactive date, and consumption quantities.
• HZ_CUST_ACCOUNTS and HZ_PARTIES — supply customer name and customer number.
• HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, and HZ_PARTY_SITES — resolve ship-to and bill-to site usage records and link them to customer accounts.
• HZ_LOCATIONS — provides the formatted address text used in the CUSTOMER_SHIP_ADDRESS and CUSTOMER_BILL_ADDRESS columns.
• HR_ALL_ORGANIZATION_UNITS — supplies organization code and organization name.
• MTL_PARAMETERS — supplies the inventory organization context, including ORGANIZATION_ID.

The joins follow the standard TCA model: party to account, account to account site, account site to site use, and site to location.

Key Columns

• ORGANIZATION_CODE / ORGANIZATION_NAME — identify the inventory organization to which the forecast applies.
• FORECAST_NAME, FORECAST_DESCRIPTION, FORECAST_SET_NAME — identify the forecast and its set.
• DEMAND_CLASS — the demand class associated with the forecast entry, used for demand segmentation.
• CUSTOMER_NAME / CUSTOMER_NUMBER — the customer associated with the forecast demand.
• CUSTOMER_SHIP_ADDRESS / CUSTOMER_BILL_ADDRESS — formatted ship-to and bill-to addresses, each up to 240 characters. These are the columns most directly relevant to the searched term "customer_ship_address."
• CUSTOMER_ID, CUSTOMER_SHIP_ID, CUSTOMER_BILL_ID — surrogate keys linking back to TCA entities.
• INACTIVE_DATE — date after which the forecast is no longer active.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns.

Common Use Cases and Queries

The view is typically queried for demand visibility reporting, forecast consumption analysis, and customer-level demand extraction where ship-to address detail is required. A representative query retrieving customer ship addresses for active forecasts follows:

SELECT ORGANIZATION_CODE,
       FORECAST_NAME,
       DEMAND_CLASS,
       CUSTOMER_NAME,
       CUSTOMER_NUMBER,
       CUSTOMER_SHIP_ADDRESS
FROM   APPS.MRPFV_FORECASTS
WHERE  INACTIVE_DATE IS NULL
  AND  CUSTOMER_SHIP_ADDRESS IS NOT NULL;

Other scenarios include joining the view to MTL_SYSTEM_ITEMS or supply planning extracts on ORGANIZATION_ID and CUSTOMER_ID, aggregating demand by DEMAND_CLASS, or using CUSTOMER_BILL_ID and CUSTOMER_SHIP_ID to reconcile forecast records back to TCA customer sites. Because the view is read-only and not referenced by any database object, it is safe to query directly without impacting transactional processing.