Results for “msc_net_supply_schd_v”

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

Overview

MSC_NET_SUPPLY_SCHD_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSC (Advanced Supply Chain Planning) product family. It is a lightweight, purpose-built view that exposes a curated list of the network supply schedules (production plans and master schedules) that have been configured within the planning application. Rather than presenting the transactional planning data itself, the view functions as a metadata or lookup layer, translating internal codes stored in the form-query infrastructure into user-meaningful values.

Its primary role is to supply a name-and-identifier list of net supply schedules together with a descriptive schedule designator. This makes it suitable for LOV (List of Values) population, concurrent program parameters, Discoverer or BI Publisher reports, and integration interfaces that must resolve a stored designator type into a human-readable meaning. Because it joins the designator code to the MRP_DESIGNATOR_TYPE_SHORT lookup, downstream consumers are shielded from having to re-implement that lookup resolution logic themselves.

Underlying Base Objects

The view is defined over two referenced base objects: MSC_FORM_QUERY (exposed in the APPS schema as a synonym) and MFG_LOOKUPS (itself implemented as a view). MSC_FORM_QUERY stores the persisted query and parameter combinations captured by the planning forms, including the columns CHAR1 through CHAR4 and NUMBER1 through NUMBER6 that carry schedule and designator attributes. MFG_LOOKUPS holds Oracle's standard lookup definitions.

The join predicate is MFG.LOOKUP_CODE = MFQ.NUMBER2, constrained by MFQ.NUMBER1 = 5, MFQ.NUMBER6 = 2, and MFG.LOOKUP_TYPE = 'MRP_DESIGNATOR_TYPE_SHORT'. In effect, the view filters MSC_FORM_QUERY to a specific form-query category (NUMBER1 = 5, NUMBER6 = 2) and then decorates each surviving row with the meaning from the short designator type lookup. This design keeps the view narrow and predictable, since only rows matching the fixed filter set are returned.

Key Columns

• QUERY_ID — The primary identifier of the stored form query in MSC_FORM_QUERY, used to reference a specific schedule/plan entry.
• PLAN_NAME — The name of the plan or schedule, sourced from the form-query character columns.
• ORG_CODE — The organization code associated with the schedule.
• INPUT_NAME and INPUT_SCHEDULE_DESC — Identifiers and the description of the input schedule.
• DESIGNATOR_TYPE — The user-facing designator for the schedule, derived from MFG.MEANING via the MRP_DESIGNATOR_TYPE_SHORT lookup join. This is the column users most often search for and the one that gives the view its reporting value.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle WHO columns for audit and concurrency tracking.

Common Use Cases and Queries

Typical uses include constraining a schedule LOV in a custom form, filtering a report to only those schedules of a given designator type, and sourcing a parameter list for a concurrent program in Advanced Supply Chain Planning.

To list all net supply schedules with their decoded designator:

SELECT query_id,
       plan_name,
       org_code,
       input_name,
       input_schedule_desc,
       designator_type
FROM   apps.msc_net_supply_schd_v
ORDER  BY plan_name;

To retrieve the designator for a single schedule:

SELECT designator_type
FROM   apps.msc_net_supply_schd_v
WHERE  query_id = :p_query_id;

To restrict a report to a particular designation:

SELECT plan_name, org_code, input_schedule_desc
FROM   apps.msc_net_supply_schd_v
WHERE  designator_type = :p_designator;

Because the view carries no organization-security or operating-unit predicates of its own, any responsibility-level data restriction must be applied by the calling report or form. The view should be treated as read-only reference data.