Search Results source_demand_class

Overview

APPS.MRP_LOAD_PARAMETERS_V is a reporting and integration view in Oracle E-Business Suite (12.1.1 and 12.2.2) that consolidates load parameter definitions used by the MRP/MPS planning engine. The underlying table MRP_LOAD_PARAMETERS stores the control records that describe a load or copy operation between source and destination planning organizations — specifying which forecast, master schedule, or schedule designator is being loaded, and how its status is tracked. The physical table, however, holds only internal numeric identifiers (ORGANIZATION_ID, SOURCE_ORGANIZATION_ID, designator codes). The view enriches those rows with descriptive attributes so that planning administrators and integration routines can interpret load processes in business terms.

The view is a UNION of two branches distinguished by the LOAD_SOURCE column. When LOAD_SOURCE = 2, the record represents a forecast-based load; when LOAD_SOURCE = 1, it represents a schedule-based load. A literal or derived SOURCE_TYPE is projected accordingly (5 for forecasts, SCHEDULE_TYPE for schedules), giving consumers a single uniform result set regardless of the underlying demand source. This design makes the view suitable for forms, concurrent program reports, and outbound interfaces that must present load definitions without re-implementing the join logic.

Underlying Base Objects

The documented base objects referenced by the view are MTL_PARAMETERS, MRP_FORECAST_DESIGNATORS, MRP_SCHEDULE_DESIGNATORS, MRP_ORGANIZATIONS_V, MRP_PLAN_ORGANIZATIONS_V, MRP_DESIGNATORS_VIEW, and MRP_LOAD_PARAMETERS itself (exposed through synonyms). In the forecast branch, MRP_LOAD_PARAMETERS is joined to MRP_FORECAST_DESIGNATORS on both FORECAST_DESIGNATOR and ORGANIZATION_ID, and to MTL_PARAMETERS on ORGANIZATION_ID to retrieve the organization code. In the schedule branch, MRP_LOAD_PARAMETERS is joined to MRP_SCHEDULE_DESIGNATORS, then outer-joined to MRP_ORGANIZATIONS_V (which in turn draws on MRP_PLAN_ORGANIZATIONS_V) to resolve a planned organization, and joined to MTL_PARAMETERS for the organization code. The join conditions require the source designator to be non-null, so incomplete or placeholder rows are excluded.

Key Columns

• ROW_ID — the ROWID of the underlying MRP_LOAD_PARAMETERS record, useful for row-level updates.
• QUERY_ID — identifies the load/query definition being processed.
• PROCESS_STATUS — the current status of the load operation.
• ORGANIZATION_ID, SCHEDULE_DESIGNATOR, FORECAST_DESIGNATOR — the destination organization and its schedule/forecast designators.
• LOAD_SOURCE — discriminator indicating forecast (2) or schedule (1) origin.
• LOAD_DESTINATION — target of the load operation.
• SOURCE_ORGANIZATION_ID — the organization supplying the demand data.
• SOURCE_SCHEDULE_DESIGNATOR, SOURCE_FORECAST_DESIGNATOR — the originating designators.
• SOURCE_TYPE — derived type of the source (5 for forecast, or schedule type).
• SOURCE_DESCRIPTION, SOURCE_DEMAND_CLASS — descriptive text and demand class of the source designator.
• SOURCE_DESIGNATOR — alias exposing the source forecast or schedule designator.
• SOURCE_ORGANIZATION_CODE — the organization code from MTL_PARAMETERS, the value most commonly searched for as source_organization_code.
• ERROR_MESSAGE, SELECTION_LIST_NAME, SELECTION_LIST_TYPE — diagnostics and selection-list context.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).

Common Use Cases and Queries

Typical uses include auditing which source organizations feed a given plan, troubleshooting failed loads, and driving integration extracts. Because the user searched for source_organization_code, the most relevant pattern is filtering or grouping by that column:

• List all load parameters for a source organization:
  SELECT query_id, source_organization_code, source_designator, load_source, process_status FROM apps.mrp_load_parameters_v WHERE source_organization_code = :org_code;
• Find failed loads by source:
  SELECT source_organization_code, query_id, error_message FROM apps.mrp_load_parameters_v WHERE process_status = 'ERROR';
• Distinguish forecast versus schedule sources:
  SELECT source_organization_code, source_type, source_demand_class FROM apps.mrp_load_parameters_v WHERE load_source IN (1,2);

Reporting solutions frequently join the view back to MRP_LOAD_PARAMETERS on QUERY_ID or ROW_ID to obtain columns not projected here, while the view supplies the human-readable organization codes and designator descriptions.