Search Results mrp_project_v




Overview
Explore in AI Chat

Overview

MRP_PROJECT_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Master Scheduling/MRP (MRP) product family and is documented as a "Project information view." Its purpose is to expose descriptive project attributes — project identifier, number, name, and planning group — in a normalized shape that MRP planning engines, concurrent programs, and custom extensions can consume without querying the underlying project tables directly. Because the view isolates a curated set of columns and enforces a consistent data type across its union branches, it behaves as a lightweight integration and reporting surface rather than a transactional object.

The view is significant in that it surfaces the PLANNING_GROUP attribute, the term most associated with user searches against this object. Planning groups are used to partition demand, supply, and project references into logical buckets for planning and reporting purposes, allowing planners to segregate project data by organizational or business grouping criteria.

Underlying Base Objects

The documented view text comprises a UNION ALL of two branches: a primary SELECT from MTL_PROJECT_V and a synthetic row generated from DUAL. The first branch carries PROJECT_ID, PROJECT_NUMBER, PROJECT_NAME, and PLANNING_GROUP from MTL_PROJECT_V, which is the project information view maintained by Oracle Projects inventory integration. The second branch contributes a single row of NULLs for the first four columns and the literal value 1 for the fifth column, aliased as DUMMY. This dummy row ensures the view always returns at least one row, supporting outer-join and reporting patterns where a project context may be optional.

Metadata for the 12.2.2 release records the following referenced objects: MTL_PROJECT_V (VIEW); the packages MRP_GET_PROJECT, PA_PROJECT_UTILS, PA_SECURITY, PA_CROSS_BUSINESS_GRP, and FND_PROFILE; and the DUAL synonym. These references indicate that project data retrieval is mediated by Oracle Projects security and cross-business-group logic, and that profile options from FND_PROFILE can influence which project rows are visible. The view is dependent on Oracle Projects and Inventory schemas being present and accessible within the APPS synonym chain.

Key Columns

  • PROJECT_ID — Numeric identifier of the project, matching the primary key used throughout Oracle Projects and MRP planning entities.
  • PROJECT_NUMBER — The user-facing project number, commonly used in reports and cross-references to Project Accounting.
  • PROJECT_NAME — The descriptive project name, suitable for display in planning and inquiry screens.
  • PLANNING_GROUP — The planning group value associated with the project, used to partition or categorize project references for planning purposes.
  • DUMMY — A synthetic column populated only by the DUAL branch (value 1); the primary branch emits NULL. It exists to guarantee a non-empty result set.

Common Use Cases and Queries

Typical usage includes LOV queries, custom planning reports, and integration extracts that require a compact project reference list. A basic enumeration of projects and their planning groups is shown below:

  • SELECT project_id, project_number, project_name, planning_group FROM mrp_project_v WHERE planning_group IS NOT NULL ORDER BY project_number;
  • SELECT planning_group, COUNT(*) FROM mrp_project_v GROUP BY planning_group;
  • SELECT p.project_number, p.project_name FROM mrp_project_v p WHERE p.project_id = :project_id;

Because the view filters through Oracle Projects security packages, results are subject to the security profile of the executing user, and the accessible row set may differ between responsibilities. Applications should treat MRP_PROJECT_V as a validation and lookup source rather than as a substitute for the full project definition.