Results for “plan_horizon”

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

Overview

PJM_PROJECT_MFG_PLAN_V is a reporting view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PJM (Project Manufacturing) product family and exposes project-related manufacturing plan information for the Web Inquiry. The view consolidates planning data from the MPS/MRP engine — gross requirements, planned recommendations, plan headers, designators, and organization definitions — into a single denormalized rowset scoped by project and task. Its primary purpose is to let a user or application query, for a given project/task/organization combination, which manufacturing plans exist and what planning horizon each covers. Status is VALID, and the metadata carries Oracle Proprietary, Confidential Information and Legal Notices markings, indicating the object is documented under ETRM restrictions.

Underlying Base Objects

The view is defined over the following documented base objects:

• MRP_GROSS_REQUIREMENTS (SYNONYM) and MRP_RECOMMENDATIONS (SYNONYM) — unioned in an inline subquery to supply the driving PROJECT_ID, TASK_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR rows. This dual source ensures both unsatisfied demand and planned order supply are represented.
• MRP_PLAN_ORGANIZATIONS (SYNONYM) and MRP_PLANS (SYNONYM) — unioned in a second inline subquery (PORG) to resolve PLANNED_ORGANIZATION to the owning plan organization and compile designator.
• MRP_DESIGNATORS (SYNONYM) — supplies COMPILE_DESIGNATOR and DESCRIPTION, joined to MRP_PLANS on both organization and designator.
• HR_ALL_ORGANIZATION_UNITS_TL (SYNONYM) — supplies the translated ORGANIZATION_NAME for the reporting organization, filtered to USERENV('LANG').
• MFG_LOOKUPS (VIEW) — supplies the decoded plan type MEANING via an outer join on lookup type 'MRP_PLAN_TYPE'.

The joins tie the demand/supply facts to plan headers, plan organization mappings, designators, and descriptive lookups, with DISTINCT applied to collapse the unions into unique project/task/designator/organization plan rows.

Key Columns

• PROJECT_ID, TASK_ID — Project and task context that qualify the manufacturing plan rows.
• PLAN_NAME, PLAN_DESCRIPTION — Identity and description of the plan (from MRP_PLANS and MRP_DESIGNATORS).
• PLAN_TYPE_CODE, PLAN_TYPE — Raw CURR_PLAN_TYPE code and its decoded meaning from MFG_LOOKUPS.
• ORGANIZATION_ID, ORGANIZATION_NAME — Reporting organization identifier and its language-specific name.
• START_DATE, COMPLETION_DATE — Derived from PLAN_START_DATE and PLAN_COMPLETION_DATE.
• PLAN_HORIZON — The span of planning dates exposed to the inquiry, effectively the interval between the plan start and completion dates (and bounded by the current cutoff). This is the column most relevant to the user search term "plan_horizon", and it is the column most commonly used to filter plans to a specific future window.

Common Use Cases and Queries

Typical usage includes project manufacturing web inquiry screens, custom dashboards showing active plans per project, and data extracts feeding project-aware MRP reporting. A representative query selecting plans whose horizon falls inside a target window:

SELECT project_id,
       task_id,
       plan_name,
       plan_type,
       organization_name,
       start_date,
       completion_date,
       plan_horizon
FROM   apps.pjm_project_mfg_plan_v
WHERE  project_id = :p_project_id
AND    task_id = :p_task_id
AND    plan_horizon BETWEEN :p_from AND :p_to;

Because the view already aggregates gross requirements and recommendations, it is well suited to answering questions such as "which manufacturing plans cover this project for the next quarter" or "what is the current plan type and horizon for each designator associated with this organization." For performance, queries should be bound by PROJECT_ID and ORGANIZATION_ID, since the underlying unions against MRP_GROSS_REQUIREMENTS and MRP_RECOMMENDATIONS can be large; appropriate MPS/MRP indexing and up-to-date statistics on the base planning tables are advisable.