Search Results load_source




Overview

MRP_LOAD_PARAMETERS_V is an APPS-owned view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) product. It is documented as providing "Forecast and master schedule source list information," and its role is to present a consolidated, readable projection of the load parameters that drive the loading of forecast and master schedule data into a planning session. The underlying MRP_LOAD_PARAMETERS table stores the raw load request rows, including internal identifiers, designators, and status flags, but it references source designators and organizations only by numeric identifier. The view resolves those identifiers into descriptive information, so report writers and integration developers can identify the load source without performing their own joins to the forecast, schedule, and organization lookup objects.

Because the object is a view and not a table, it is read-only, exposes no DML, and inherits the security and grants applied at the APPS layer. It is reported as VALID in the ETRM metadata for 12.2.2 and is also available in 12.1.1, where the same column set and UNION structure apply.

Underlying Base Objects

The documented base objects are MRP_LOAD_PARAMETERS, MRP_FORECAST_DESIGNATORS, MRP_SCHEDULE_DESIGNATORS, MTL_PARAMETERS, MRP_DESIGNATORS_VIEW, MRP_ORGANIZATIONS_V, and MRP_PLAN_ORGANIZATIONS_V, several of which are exposed through synonyms in the APPS schema. The view text is a UNION of two branches that distinguish the load source. The first branch selects rows where LOAD_SOURCE equals 2 and joins MRP_LOAD_PARAMETERS to MRP_FORECAST_DESIGNATORS on SOURCE_FORECAST_DESIGNATOR and SOURCE_ORGANIZATION_ID, and to MTL_PARAMETERS on ORGANIZATION_ID. The second branch selects rows where LOAD_SOURCE equals 1 and joins to MRP_SCHEDULE_DESIGNATORS and MRP_ORGANIZATIONS_V, with outer joins on the organization view, and again joins MTL_PARAMETERS for the organization code. The schedule designator branch also references MRP_DESIGNATORS_VIEW and MRP_PLAN_ORGANIZATIONS_V in the broader object dependency list. Each branch contributes a literal SOURCE_TYPE (5 for forecast sources, SCHEDULE_TYPE for master schedule sources) and aliases SOURCE_DESIGNATOR from the corresponding designator column.

Key Columns

Common Use Cases and Queries

Typical uses include diagnostics of failed forecast or schedule loads, reporting of source-to-destination load definitions, and integration extracts that populate external planning systems with source list information.

List load rows with resolved sources:

  • SELECT query_id, process_status, source_type, source_organization_code, source_designator, source_description, error_message FROM mrp_load_parameters_v WHERE process_status = 'ERROR';

Retrieve forecast load definitions for a destination organization:

  • SELECT schedule_designator, forecast_designator, source_designator, source_description, selection_list_name FROM mrp_load_parameters_v WHERE organization_id = :org_id AND source_type = 5;

Inspect master schedule sources and demand classes:

  • SELECT organization_id, schedule_designator, source_designator, source_description, source_demand_class FROM mrp_load_parameters_v WHERE load_source = 1;