Results for “mrp_srs_sched_load_source_v”

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

Overview

The MRP_SRS_SCHED_LOAD_SOURCE_V view is an Oracle EBS Master Scheduling/MRP (MRP) dictionary object owned by the APPS schema. It is documented in ETRM with a status of VALID under release 12.1.1 and 12.2.2. Its stated purpose is "Sources for schedule load," meaning it consolidates the various planning entities — load selections, schedule designators, forecast designators, plan designators, and a null placeholder — that may be selected as the source when a scheduling or planning process loads data. The view functions as a unified, user-facing lookup of selectable load sources rather than as a transactional data store, making it a convenient reporting and integration surface for windows, concurrent programs, and custom extensions that need to enumerate valid load sources.

Underlying Base Objects

The view is defined over a UNION ALL of seven query blocks. The documented referenced objects are MFG_LOOKUPS, MRP_DESIGNATORS_VIEW, MRP_FORECAST_DESIGNATORS, MRP_LOAD_SELECTIONS, MRP_ORGANIZATIONS_V, MRP_PLAN_ORGANIZATIONS_V, MRP_SCHEDULE_DESIGNATORS, and DUAL. Each block contributes a distinct source category, identified in the second column by a literal type code:

• 6 — selections from MRP_LOAD_SELECTIONS where SELECTION_LIST_TYPE = 1
• 7 — selections where SELECTION_LIST_TYPE = 3
• 9 — selections where SELECTION_LIST_TYPE = 4
• 1 — schedule designators (SCHEDULE_TYPE = 1) from MRP_SCHEDULE_DESIGNATORS, joined to MFG_LOOKUPS on lookup type 'MRP_DESIGNATOR_TYPE_SHORT'
• 8 — schedule designators (SCHEDULE_TYPE = 2) outer-joined to MRP_ORGANIZATIONS_V to resolve the planned organization
• 2 — forecast designators from MRP_FORECAST_DESIGNATORS
• 3 — a single null-valued row sourced from DUAL
• 4 — plan designators from MRP_DESIGNATORS_VIEW where DESIGNATOR_TYPE != 1, outer-joined to MRP_PLAN_ORGANIZATIONS_V

Designator-based blocks apply a date filter that excludes rows whose DISABLE_DATE has passed, comparing against TRUNC(SYSDATE)+1. Lookup joins supply the MEANING column, while an outer join against the plan/organization views resolves the owning or planned organization.

Key Columns

The view exposes five columns. Note that only four are explicitly named in the view text; the second SELECT expression is an unnamed numeric literal, effectively column 2 of the projection:

• ORGANIZATION_ID — the organization associated with the source. For schedule designators of type 2 and plan designators, this is derived via NVL from the planned organization (MRP_PLAN_ORGANIZATIONS_V / MRP_ORGANIZATIONS_V) or the designator's own organization.
• Source type code (literal) — an integer (1, 2, 3, 4, 6, 7, 8, 9) that discriminates the kind of load source: selections, schedule designators, forecast designators, a null placeholder, schedule designators of type 2, and plan designators.
• Selection list / designator name — SELECTION_LIST_NAME, SCHEDULE_DESIGNATOR, FORECAST_DESIGNATOR, or DESIGNATOR, providing the human-readable identifier; it is NULL for the DUAL-sourced placeholder row.
• DESCRIPTION — descriptive text for the selection or designator.
• MEANING — the decoded lookup meaning from MFG_LOOKUPS (MRP_DESIGNATOR_TYPE_SHORT) for designator-based rows; NULL for selection and forecast rows.

Common Use Cases and Queries

Typical uses include populating a load-source list of values in a scheduling window, validating a user-supplied source before invoking a load program, and generating reports of available schedule/forecast/plan sources per organization. Because the view already filters disabled designators and normalizes organization resolution, consumers avoid duplicating that logic. A representative query enumerating valid sources for an organization is:

• SELECT organization_id, selection_list_name, description FROM apps.mrp_srs_sched_load_source_v WHERE organization_id = :org_id ORDER BY selection_list_name;
• SELECT DISTINCT organization_id FROM apps.mrp_srs_sched_load_source_v WHERE organization_id IS NOT NULL;

Integrations should treat the numeric type literal as the discriminator for source category and rely on the built-in date filtering rather than re-applying DISABLE_DATE predicates. As with all APPS-owned views, access should be granted through the appropriate responsibility or a synonym, and consumers should expect the underlying UNION structure to remain the authoritative definition.