Results for “plan_description”

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

Overview

ICX_EDM_MFG_PLAN_V is an APPS-owned database view that exposes manufacturing plan information organized by project. It is delivered as part of the ICX product family, Oracle iProcurement, and is registered in EBS 12.1.1 and 12.2.2 as a VALID object. Its stated purpose is to present "Manufacturing Plan Information by Project," meaning it flattens data drawn from Oracle Manufacturing planning tables (MRP designators and plans) and correlates each plan with project and task context where planning activity exists.

The view occupies a reporting and integration role rather than a transactional one. It is a read-only projection intended for inquiry, personalization, and downstream extraction, allowing applications and users to identify which manufacturing plans reference a given project and task combination. Because the definition embeds an EXISTS predicate against MRP_RECOMMENDATIONS and MRP_GROSS_REQUIREMENTS, the view only surfaces plans that actually have planning supply or demand tied to a project and task. This makes it a discovery mechanism for project-referenced planning activity rather than a full list of all defined plans.

The search term "mrp_recommendations" maps directly to one of the two driving subqueries in the view text. MRP_RECOMMENDATIONS is the Oracle MRP table holding planned orders and other planning suggestions, such as planned orders and reschedule recommendations. Its presence in the EXISTS clause confirms that the view exists to answer the question: which manufacturing plans contain MRP recommendations (or gross requirements) for this project and task?

Underlying Base Objects

ETRM documents the following referenced base objects: HR_GENERAL (package), HR_ORGANIZATION_UNITS (view), HR_SECURITY (package), MFG_LOOKUPS (view), MRP_DESIGNATORS (synonym), MRP_GROSS_REQUIREMENTS (synonym), MRP_PLANS (synonym), MRP_RECOMMENDATIONS (synonym), MTL_PARAMETERS (synonym), PA_PROJECTS_ALL (synonym), PA_TASKS (synonym), and PJM_SEIBAN_NUMBERS (synonym).

• MRP_DESIGNATORS supplies the plan identity: COMPILE_DESIGNATOR, DESCRIPTION, and ORGANIZATION_ID.
• MRP_PLANS supplies plan attributes: CURR_PLAN_TYPE, PLAN_START_DATE, PLAN_COMPLETION_DATE, and CURR_CUTOFF_DATE (aliased as PLAN_HORIZON).
• MRP_RECOMMENDATIONS and MRP_GROSS_REQUIREMENTS are used inside the EXISTS predicate to restrict the result set to plans that carry project- and task-referenced planning activity.
• HR_ORGANIZATION_UNITS and MTL_PARAMETERS provide organization naming and the organization code.
• MFG_LOOKUPS resolves the plan type code to its translated meaning for lookup type MRP_PLAN_TYPE.
• PA_PROJECTS_ALL and PA_TASKS provide project and task identifiers; PJM_SEIBAN_NUMBERS contributes the Seiban/project branch used in the second half of the UNION.
• HR_GENERAL and HR_SECURITY are supporting packages referenced by the underlying organization views to enforce security.

Key Columns

• PLAN — the compile designator identifying the MRP plan.
• PLAN_DESCRIPTION — narrative description of the plan from MRP_DESIGNATORS.
• PLAN_TYPE_CODE and PLAN_TYPE_DESCRIPTION — the plan type value and its decoded meaning from MFG_LOOKUPS.
• ORGANIZATION_ID, ORGANIZATION_NAME, and ORGANIZATION_CODE — the planning organization.
• PLAN_START_DATE, PLAN_COMPLETION_DATE, and PLAN_HORIZON — the plan window and cutoff date.
• PROJECT_ID and TASK_ID — the project and task each row is associated with; TASK_ID may be null for the Seiban union branch.

Common Use Cases and Queries

Typical scenarios include identifying plans that contain MRP recommendations for a project, driving project-centric planning reports, and feeding iProcurement or custom dashboards with plan-to-project mappings. A representative query is:

SELECT plan, organization_name, project_id, task_id FROM apps.icx_edm_mfg_plan_v WHERE project_id = :p_project_id AND organization_id = :p_org_id;

The view is commonly joined back to MRP_RECOMMENDATIONS to retrieve the actual planned orders for a returned plan, project, and task tuple.