Results for “mrp_ap_system_items_v”

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

Overview

The view MRP_AP_SYSTEM_ITEMS_V belongs to the Oracle Master Scheduling/MRP (MRP) module and is distributed as part of the Advanced Planning (AP) schema objects that support planning and scheduling logic in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes item-level planning attributes for planning-enabled organizations and is consumed by planning, sourcing, and replenishment processes that require an item master context without directly joining the many base tables of the Oracle Inventory (INV) item definition model. The view behaves as a denormalized presentation layer over the system items foundation, allowing planning reports, concurrent programs, and integration interfaces to retrieve planning-relevant item attributes through a single database object.

The view is not implemented as a physical database object in this environment; its definition is supplied as a query excerpt and is intended to be referenced at runtime. Because the ETRM metadata documents no base objects explicitly, the view text itself provides the authoritative evidence of the underlying columns and joins.

Underlying Base Objects

The documented view metadata records no referenced base objects, and the implementation note states that the view is not implemented in the database. The SELECT text, however, clearly references an aliased source, MASIVA, together with MAC (ABC class), MAA (ABC assignments), CIC (item cost), PPX (buyer/employee), and MPES (planning exception summary). The dominant source alias MASIVA corresponds to the system-items view family that consolidates MTL_SYSTEM_ITEMS_B and MTL_SYSTEM_ITEMS_TL style data. Supplementary aliases map to ABC class definitions, ABC assignment records, item cost calculations, per-business-unit employee records, and planning exception data. Because no base objects are formally documented, references beyond the view text should be validated against the deployed 12.2.2 schema before reliance.

Key Columns

The view exposes a broad set of planning attributes. The column most relevant to the search term rounding_control_type is projected as:

• NVL(MASIVA.ROUNDING_CONTROL_TYPE, 2) ROUNDING_CONTROL_TYPE — controls how order quantities are rounded during planning. A default of 2 is applied when the source value is null.
• FIXED_ORDER_QUANTITY, FIXED_LOT_MULTIPLIER, MINIMUM_ORDER_QUANTITY, MAXIMUM_ORDER_QUANTITY — order quantity modifiers that interact with rounding control.
• FIXED_DAYS_SUPPLY, SHRINKAGE_RATE, LOT_CONTROL_CODE, LOTS_EXPIRATION — supply and lot-handling attributes.
• MRP_PLANNING_CODE, PLANNING_MAKE_BUY_CODE, PLANNER_CODE, PLANNING_EXCEPTION_SET — planning classification and responsibility.
• FIXED_LEAD_TIME, VARIABLE_LEAD_TIME, PREPROCESSING_LEAD_TIME, POSTPROCESSING_LEAD_TIME, FULL_LEAD_TIME, CUMULATIVE_TOTAL_LEAD_TIME — lead-time dimensions used by the planner.
• ABC_CLASS_NAME, ABC_CLASS_ID, ITEM_COST, BUYER_NAME, EXCESS_QUANTITY — derived classification, costing, and exception measures.

Common Use Cases and Queries

Typical usage includes planning exception reporting, order-quantity verification, and integration extracts where rounding behavior must be confirmed. A representative query:

• SELECT organization_id, inventory_item_id, item_name, rounding_control_type FROM mrp_ap_system_items_v WHERE organization_id = :org_id;
• SELECT item_name, fixed_order_quantity, fixed_lot_multiplier, minimum_order_quantity FROM mrp_ap_system_items_v WHERE rounding_control_type = 2;
• SELECT item_name, abc_class_name, item_cost, buyer_name FROM mrp_ap_system_items_v WHERE planner_code = :planner;

These queries support validation of item planning setups and exception-driven replenishment analysis within the MRP module.