Search Results msd_sr_prd_pf_v




Overview
Explore in AI Chat

Overview

MSD_SR_PRD_PF_V is a source view owned by the APPS schema within the Oracle E-Business Suite Demand Planning module (MSD). Its purpose is to associate the Product level of the Product Dimension with the Product Family level, supplying the Product-to-Product-Family hierarchy relationship that Demand Planning and related supply chain planning flows rely upon. In an Oracle EBS 12.1.1 or 12.2.2 environment, this view acts as an extraction source: the collections and staging processes that populate the Demand Planning analytical store read from it to build the product dimension rollup. The view is documented as VALID and is intended to be applied to an Oracle Applications 11i-derived instance from which the Product-to-Product-Family association information is sourced, remaining present in the 12.x data model for backward compatibility with those collections.

Underlying Base Objects

The view is defined over a join of several documented base objects, most of which are synonyms or views rather than physical tables:

Key Columns

The view projects a small, fixed set of columns. The first two expose the child (product) identifier: INVENTORY_ITEM_ID and CONCATENATED_SEGMENTS, taken from the CHILD instance of MTL_SYSTEM_ITEMS_KFV. The third and fourth columns expose the corresponding parent (product family) identifier, again as an item ID and a concatenated segment string, but only when the parent resides in the master organization defined by the MSD_MASTER_ORG parameter; otherwise the MSD_SR_UTIL.GET_NULL_PK and GET_NULL_DESC placeholders are returned, effectively orphaning that product from any family. The remaining five columns are populated with NULL and are reserved as positional placeholders in the source-view contract expected by the collections interface. The absence of a column literally named MRP_PLANNING_CODE is significant: that attribute appears only as an internal filter predicate.

Common Use Cases and Queries

The principal use case is validating and diagnosing the product-to-product-family rollup before or after a Demand Planning collection. Analysts frequently search for "mrp_planning_code" because both CHILD and PARENT rows are filtered with the predicate MRP_PLANNING_CODE <> 6, which excludes items flagged as not planned (planning code 6). Additional filters restrict assemblies to BOM_ITEM_TYPE = 5 (product family) and exclude ATO forecast control 3, so the view returns only planned items participating in a family structure.

A representative diagnostic query is:

  • SELECT inventory_item_id, concatenated_segments FROM apps.msd_sr_prd_pf_v WHERE concatenated_segments IS NOT NULL; — lists child products that were successfully linked to a product family.
  • SELECT * FROM apps.msd_sr_prd_pf_v; — inspects the full projection, including the null placeholder columns.

Because the MRP_PLANNING_CODE filter is embedded and cannot be overridden at the view level, users who need to inspect excluded items must query the underlying MTL_SYSTEM_ITEMS_KFV and BOM views directly.