Search Results org_pk




Overview
Explore in AI Chat

Overview

APPS.MSD_MFG_FCST_V is an Oracle E-Business Suite (EBS) view that exposes manufacturing forecast data for reporting and integration purposes. It is defined over the manufacturing forecast base data and resolves surrogate primary keys into their corresponding readable level values by joining to the level value table multiple times. The view is part of the MSD (Manufacturing Scheduling and Demand) schema objects used by Oracle Advanced Planning, Demand Planning, and related supply chain modules. In the context of EBS 12.1.1 and 12.2.2, this view is frequently referenced when consumers need a denormalized, human-readable projection of forecast records without performing the multi-table key resolution themselves.

The user search term "org_pk" maps directly to the view's aliased column ORG_PK, which is derived from MSD_LEVEL_VALUES with a level_id of 7 (inventory organization level). The view resolves each forecast row's surrogate keys for organization, item, customer, sales channel, and ship-to location into paired LEVEL_VALUE and LEVEL_PK columns.

Underlying Base Objects

The view definition references two documented base objects, both listed as synonyms in the ETRM metadata: MSD_MFG_FORECAST and MSD_LEVEL_VALUES. The primary driving table is MSD_MFG_FORECAST (aliased MBD), which holds the raw forecast records. Five separate aliased instances of MSD_LEVEL_VALUES are joined to it — ORG_PK, ITEM_PK, CUSTOMER_PK, SALES_CHANNEL_PK, and SHIP_TO_LOC_PK — each joining on both the INSTANCE column and the relevant SR_*_PK surrogate key column in the forecast table.

Each level value join is additionally constrained by a LEVEL_ID that identifies the dimension: organization (level_id = 7), item (level_id = 1), customer (level_id = 15), sales channel (level_id = 27), and ship-to location (level_id = 11). The organization and item joins are inner joins, while customer, sales channel, and ship-to location use outer joins (indicated by the (+) operator), meaning forecast rows without those attributes are still returned.

Key Columns

  • FORECAST_DESIGNATOR — Identifier of the forecast designator associated with the manufacturing forecast record.
  • ORG_PK.LEVEL_VALUE / ORG_PK.LEVEL_PK — The resolved inventory organization value and its surrogate key (level_id = 7). This is the column pair correlated with the search term "org_pk".
  • ITEM_PK.LEVEL_VALUE / ITEM_PK.LEVEL_PK — The resolved item value and key (level_id = 1).
  • CUSTOMER_PK.LEVEL_VALUE / LEVEL_PK — Resolved customer value and key (level_id = 15), populated via outer join.
  • SALES_CHANNEL_PK.LEVEL_VALUE / LEVEL_PK — Resolved sales channel value and key (level_id = 27), populated via outer join.
  • SHIP_TO_LOC_PK.LEVEL_VALUE / LEVEL_PK — Resolved ship-to location value and key (level_id = 11), populated via outer join.
  • USER_DEFINED1 / USER_DEFINED2 — Descriptive flexfield attributes; the corresponding _PK columns are emitted as NULL.
  • BUCKET_TYPE, FORECAST_DATE, RATE_END_DATE — Forecast bucket and date range attributes.
  • ORIGINAL_QUANTITY, CURRENT_QUANTITY — The forecasted quantity as originally entered and its current value.

Common Use Cases and Queries

The view is typically used to produce readable forecast reports keyed by organization, item, and demand dimension. A common pattern retrieves forecast quantities for a specific inventory organization by filtering on the resolved organization value:

  • Reporting forecast demand per item within an organization for a given forecast designator.
  • Extracting forecast rows by customer, sales channel, or ship-to location for demand analysis.
  • Integrating manufacturing forecast data into external planning or BI systems where readable dimension values are required.

Representative query:

SELECT org_pk_level_value, item_pk_level_value, forecast_date, current_quantity FROM apps.msd_mfg_forecast_v WHERE forecast_designator = :designator AND org_pk_level_value = :organization;

Because organization and item joins are inner joins, filters on those dimensions are always safe. Filters on customer, sales channel, or ship-to should account for the outer-join semantics, as those columns may return NULL. Performance is influenced by the INSTANCE and SR_*_PK join predicates against MSD_LEVEL_VALUES.