Search Results purchase_requisitions

Overview

APPS.MRP_WEB_ENTERPRISE_V is a Web view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified by Oracle's design repository under FND Design Data MRP.MRP_WEB_ENTERPRISE_V and is registered with a VALID status in the ETRM metadata. The view is a Web view designed to simplify access from Oracle Self-Service Web Applications. Specifically, it is consumed by the Planning Web Inquiries to display the enterprise view for a plan, and it is based on MRP_MATERIAL_PLANS.

The enterprise view aggregates demand, supply, and project-related attributes for a given plan, organization, and item, so that users of the self-service planning inquiry pages can review gross requirements alongside total supply without writing SQL against the underlying planning tables. Because it exposes numeric quantity columns alongside descriptive plan and organization identifiers, it also serves as a convenient read-only integration surface for custom reports and extracts that need consolidated plan-level quantities.

Underlying Base Objects

The documented base objects referenced by the view are: FND_PROFILE (PACKAGE), MRP_GET_PROJECT (PACKAGE), MRP_MATERIAL_PLANS (SYNONYM), MRP_PROJECT_V (VIEW), MRP_TASK_V (VIEW), MTL_PARAMETERS (SYNONYM), PA_CROSS_BUSINESS_GRP (PACKAGE), PA_PROJECT_UTILS (PACKAGE), PA_SECURITY (PACKAGE), and PA_TASK_UTILS (PACKAGE).

The primary data source is MRP_MATERIAL_PLANS, the material plans table that holds the plan header and item-level plan quantities. The project and task related columns are resolved through MRP_PROJECT_V and MRP_TASK_V, with MRP_GET_PROJECT and the PA_* utility and security packages supplying project, task, and cross-business-group resolution logic. MTL_PARAMETERS supplies organization-level context, while FND_PROFILE is used to evaluate profile options, notably those controlling project and task display behavior. The PA_SECURITY package participates in the project security model, restricting project information according to the responsibilities and profiles of the querying user.

Key Columns

• PLAN_ID — query identifier for the plan.
• ORGANIZATION_ID and PLAN_ORGANIZATION_ID — the organization identifier and the organization of the plan, respectively.
• COMPILE_DESIGNATOR — MPS, MRP, or DRP plan identifier.
• ORGANIZATION_CODE — the organization code.
• INVENTORY_ITEM_ID and ITEM_SEGMENTS — the inventory item identifier and its concatenated item segments.
• SALES_ORDERS, FORECASTS, DEPENDENT_DEMAND, GROSS_REQUIREMENTS — demand-side quantities.
• WIP, PURCHASE_ORDERS, PURCHASE_REQUISITIONS, IN_TRANSIT, IN_RECEIVING — supply-side quantities from work in process, purchasing, and receiving.
• PLANNED_ORDERS, TOTAL_SUPPLY, SCHEDULED_RECEIPTS — planned and scheduled supply quantities.
• PLANNING_GROUP — planning group value, with a maximum length of 4000.
• PROJECT_ID, TASK_ID, PROJECT_NUMBER, TASK_NUMBER — project and task identifiers and their numbers.

The IN_TRANSIT column carries the quantity in transit for the plan organization and item, which is the attribute most commonly targeted by searches against this view. It is reported alongside IN_RECEIVING to distinguish material moving between organizations from material already at the receiving dock.

Common Use Cases and Queries

Typical uses include auditing inter-organization in-transit balances, reconciling total supply components for a plan, and building custom planning inquiry reports. Because project columns are resolved through the PA packages, queries should be executed in a context where project security is properly initialized, usually through a standard EBS responsibility rather than a direct database session.

To isolate in-transit quantities for a plan and organization:

• SELECT plan_id, organization_code, item_segments, in_transit, in_receiving FROM apps.mrp_web_enterprise_v WHERE compile_designator = 'MRP' AND in_transit > 0;

To compare supply components for a specific item:

• SELECT plan_id, organization_code, item_segments, purchase_orders, purchase_requisitions, in_transit, in_receiving, wip, planned_orders, total_supply FROM apps.mrp_web_enterprise_v WHERE inventory_item_id = :item_id AND organization_id = :org_id;

These queries illustrate the view's role as a self-service reporting layer over MRP_MATERIAL_PLANS rather than as a transactional interface.