Results for “mrp_designators_u1”

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

Overview

APPS.MRP_PLAN_SCHED_V is a reporting and integration view within the Oracle E-Business Suite advanced supply chain planning module. It presents a denormalized, human-readable projection of the MRP_PLAN_SCHEDULES entity, combining plan schedule definitions with designator descriptions, planned organization context, and lookup meanings. In EBS 12.1.1 and 12.2.2, the view serves as the primary access point for applications and concurrent programs that require a fully described view of planning schedules without issuing multiple joins against the designator and lookup infrastructure themselves.

The view returns one row per plan schedule record, enriched with the descriptive text of the compile designator, the planned organization, and the decoded input type. It is read-oriented and inherits the security and organization context of its underlying views, making it suitable for reporting, diagnostics of plan compilation, and integration extracts that must resolve internal identifiers into meaningful business values.

Underlying Base Objects

The view is constructed over four documented objects. MRP_PLAN_SCHEDULES supplies the driving rows, including plan level, input type, input name, input organization, and the standard WHO audit columns plus the fifteen descriptive flexfield attributes. In the view text it is aliased MPS and is the target of a ROWID reference, indicating that the view preserves the ability to identify the originating plan schedule row.

MRP_DESIGNATORS_VIEW, aliased DESIG, contributes the designator name and description and is joined on organization and designator to supply the readable plan identity. MRP_PLAN_ORGANIZATIONS_V, aliased MPO, provides the planned organization and compile designator context; it is outer-joined to MRP_PLAN_SCHEDULES on INPUT_ORGANIZATION_ID and INPUT_NAME, with NVL logic resolving either the planned organization or the raw input organization. MFG_LOOKUPS, aliased LU, decodes INPUT_TYPE against lookup type MRP_DESIGNATOR_TYPE_SHORT to produce a user-facing meaning.

The view text includes a hint, INDEX MRP_DESIGNATORS_U1, directing the optimizer to the MRP_DESIGNATORS unique index during join processing. This hint is the direct link to the search term mrp_designators_u1 and confirms that the index is a documented performance dependency of this view.

Key Columns

• ROWID — identifier of the underlying MRP_PLAN_SCHEDULES row, enabling precise drill-back.
• ORGANIZATION_ID, COMPILE_DESIGNATOR, PLAN_LEVEL — the core plan schedule identity attributes.
• NVL(MPO.PLANNED_ORGANIZATION, MPS.INPUT_ORGANIZATION_ID) — the resolved owning organization for the plan.
• DESIGNATOR, DESCRIPTION — the readable designator code and its description from MRP_DESIGNATORS_VIEW.
• INPUT_TYPE and MEANING — the coded input type and its decoded lookup meaning.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program traceability.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield context and segments.

Common Use Cases and Queries

Typical use cases include reporting all plans and their designators for an organization, verifying which scheduled plan was produced by a given concurrent request, and joining the view to planning results for integration extracts.

• List plans by organization: SELECT organization_id, designator, description, meaning FROM apps.mrp_plan_sched_v WHERE organization_id = :org_id ORDER BY designator;
• Trace a concurrent request to its plan schedule: SELECT request_id, designator, plan_level FROM apps.mrp_plan_sched_v WHERE request_id = :request_id;
• Resolve designators and input types for a plan extract: SELECT designator, meaning, input_type FROM apps.mrp_plan_sched_v WHERE designator = :designator;

When tuning queries against this view, awareness of the MRP_DESIGNATORS_U1 index access path is essential, as the join to MRP_DESIGNATORS_VIEW drives the optimizer plan for the majority of filtered queries.