Results for “fsts_forecast_set_dp”

5 results




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

Overview

EDW_MRP_FORECAST_M is a denormalized forecast master table that resides in the ISC schema and is documented under the BIS – Applications BIS product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It appears in the Enterprise Technical Reference Model (ETRM) as a physical, warehouse-facing structure rather than a native transactional MRP object. The "_M" suffix and the EDW_ prefix indicate that it is intended as a master-level staging or reporting table consumed by the Enterprise Data Warehouse layer, exposing both forecast header data (FCST_*) and forecast set data (FSTS_*) side by side in a single wide row.

The ETRM documentation marks this object as "Not implemented in this database," meaning the table is registered in the ETRM metadata but is not physically deployed in every environment. Its Data Vault classification, mined heuristically from the foreign-key structure, is standalone. In Data Vault modeling terms, this suggests the table behaves as an independent structure with no parent hubs or links asserted by constraint, and it should be modeled as a hub or standalone satellite candidate rather than as a dependent link. Because it carries a two-part business key, a satellite treatment keyed on the forecast identifier is the most natural fit.

Key Information Stored

The documented physical schema contains 29 columns. The most operationally significant are the key, descriptive, and lifecycle fields rather than the full enumeration.

Business-key candidates are the unique indexes EDW_MRP_FORECAST_M_U1 (FCST_FORECAST_PK, FCST_FORECAST_PK_KEY) and EDW_MRP_FORECAST_M_U2 (FCST_FORECAST_PK_KEY). The surrogate PK (EDW_MRP_FCDM_FORECAST_UK) is distinct from these derived natural keys.

Common Use Cases and Queries

Typical usage centers on warehouse extraction and forecast-versus-actual analysis. A staging query joins forecast to set context:

  • Current, non-disabled forecasts: SELECT fcst_forecast_name, fsts_forecast_set_name FROM edw_mrp_forecast_m WHERE fcst_disable_date IS NULL;
  • Incremental loads: WHERE last_update_date > :last_run.
  • Set-level rollups: GROUP BY fsts_forecast_set_pk_key.
  • Consumption-level reporting using FSTS_CONSUMPTION_LEVEL to separate dependent versus independent demand.
  • Reconciliation of source instance codes across consolidated organizations.

Related Objects

Because the heuristic classification is standalone, no FK constraints were mined. The significant dependents are logical rather than enforced.