Search Results project_description

Overview

The MRP_AP_PROJECTS_V view is a reporting object within the Oracle EBS Master Scheduling/MRP (MRP) module. It is a snapshot-style database view that consolidates project-level and project-parameter information used by the Advanced Planning and Constraint-Based Optimization (AP/CP) planning engines. The view presents a denormalized projection of project records alongside their organization-specific planning parameters, allowing planning and reporting logic to retrieve project identity, scheduling attributes, and accounting classifications in a single query.

For users and developers who search for project_description, this view is relevant because it explicitly exposes a column named PROJECT_DESCRIPTION, mapped from the DESCRIPTION attribute of the source project table. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a read-only integration and reporting surface rather than a transactional entity; it is referenced by MRP planning processes and by custom reports that need to join project context to planning results. The ETRM metadata notes that the object is not implemented in this database, meaning that in the environment where the metadata was captured, the view was absent or inactive. This condition is common when the relevant MRP source tables or snapshots have not been created, typically because the Advanced Planning product or the associated snapshot program has not been run.

Underlying Base Objects

The view is defined over three MRP snapshot tables:

• MRP_AP_MRP_PARAS_SN — supplies organization-level planning parameters and is joined on ORGANIZATION_ID. It contributes the alias MP and the column RN (RN1).
• MRP_AP_PRJ_ALL_SN — supplies the master project definition, including name, number, description, and dates. It contributes the alias PPA and the columns RN (RN3), START_DATE, and COMPLETION_DATE.
• MRP_AP_PRJ_PARAS_SN — supplies organization- and project-specific planning parameters such as planning group, costing group, and accounting class. It contributes the alias PPP and the column RN (RN2).

The join condition links PPA.PROJECT_ID to PPP.PROJECT_ID and PPP.ORGANIZATION_ID to MP.ORGANIZATION_ID. The three RN columns are row-identifier or surrogate keys originating from the respective snapshot tables and are surfaced for internal use. Because the underlying objects are snapshot tables (suffixed _SN), the view reflects the state of project data as of the last snapshot collection, not live transactional data.

Key Columns

• PROJECT_ID — Unique identifier of the project; the principal join key.
• ORGANIZATION_ID — Inventory organization context for the planning parameters.
• PROJECT_NAME and PROJECT_NUMBER — Human-readable project name and the project number.
• PROJECT_DESCRIPTION — The descriptive text of the project, mapped from PPA.DESCRIPTION. This is the column most relevant to searches for project_description.
• START_DATE and COMPLETION_DATE — Planned project start and completion dates.
• PLANNING_GROUP, COSTING_GROUP_ID, and WIP_ACCT_CLASS_CODE — Planning and cost accounting attributes used by MRP.
• SEIBAN_NUMBER_FLAG — Flag related to Seiban (project) number handling.
• RN1, RN2, RN3 — Surrogate row identifiers from the parameters, project-parameter, and project snapshot tables respectively.

Common Use Cases and Queries

The view is most often used to obtain project descriptions and planning attributes for MRP output. A straightforward query retrieves descriptions and dates for a given organization:

• SELECT PROJECT_NUMBER, PROJECT_NAME, PROJECT_DESCRIPTION, START_DATE, COMPLETION_DATE FROM MRP_AP_PROJECTS_V WHERE ORGANIZATION_ID = :org_id;
• SELECT PROJECT_ID, PROJECT_DESCRIPTION FROM MRP_AP_PROJECTS_V WHERE PROJECT_NUMBER = :project_number;
• Join to MRP planning results on PROJECT_ID to enrich planned orders with the descriptive project text.

Because the view depends on MRP snapshot tables, it is populated only after the relevant snapshot program has executed. If the view is missing or returns no rows, the underlying MRP_AP_*_SN tables should be validated for the target organization.