Search Results data_completion_date




Overview
Explore in AI Chat

Overview

The MRP_BOM_PLAN_NAME_LOV_V view is a list-of-values (LOV) reporting object in Oracle E-Business Suite, owned by the APPS schema and delivered under the Master Scheduling/MRP product family. Its documented purpose is to expose a flattened, query-friendly list of plan names together with descriptive and item-attribute context, so that forms, concurrent programs, and custom reports can present a validated selection list of MRP/MPS/DRP plans to end users. The view is defined in both 12.1.1 and 12.2.2 and is registered as VALID.

Unlike transactional tables, this view does not persist data; it is a stored query that joins plan designators, plan definitions, plan organizations, and system item records, filtering for currently applicable rows. A notable characteristic is that it restricts results to items whose inventory use-up date has not yet passed and whose plan has completed its explosion and data-collection phases — meaning the LOV surfaces only plans that are meaningfully usable at query time. The user search term plan_completion_date maps directly to a column exposed here as COMPLETION_DATE, sourced from MRP_PLANS.PLAN_COMPLETION_DATE.

Underlying Base Objects

Per documented ETRM metadata, the view is built on the following referenced objects:

  • MRP_PLANS (alias MP2, synonym) — provides the plan designator, plan type, plan completion date, data completion date, and explosion completion date.
  • MRP_PLAN_ORGANIZATIONS (alias MP, synonym) — supplies the planned organization context and plan level.
  • MRP_SYSTEM_ITEMS (alias MSI, synonym) — the primary item/plan link, contributing compile designator, organization, inventory item, and use-up date.
  • MRP_DESIGNATORS_VIEW (alias MD, view) — supplies the plan description text.
  • MTL_ITEM_FLEXFIELDS (alias MIF, view) — supplies the concatenated item number used in the LOV display.

The joins are driven by organization_id, inventory_item_id, and compile_designator. Outer joins (+) on MRP_PLAN_ORGANIZATIONS allow plans without a matching planned organization to still be returned, and the NVL on PLANNED_ORGANIZATION preserves organization linkage. The MD designator/organization join ties textual descriptions to each plan.

Key Columns

Common Use Cases and Queries

Typical usage includes populating plan LOVs in concurrent program parameters, validating plan names in custom PL/SQL, and reporting on plan completion timing filtered by item use-up dates.

SELECT plan_name, description, completion_date, item
FROM   apps.mrp_bom_plan_name_lov_v
WHERE  completion_date IS NOT NULL
AND    organization_id = :org_id
ORDER BY completion_date DESC;

Restricting by plan type is not possible directly, but the view already limits PLAN_TYPE IN (1,2,3,4) and requires explosion and data completion to have occurred before plan completion, ensuring only operational plans appear.