Search Results end_assembly_pegging_flag

Overview

The view MRP_AP_SYS_ITEMS_V is an Oracle EBS Master Scheduling/MRP (MRP) reporting object that exposes item planning and master data for a given inventory organization in a flattened, query-ready form. Its name follows the convention used by the "AP" (Advanced Planning) family of MRP views, and it is intended to present the core fields that planning, sourcing, and ATP logic rely upon — planning make/buy code, lead times, order modifiers, safety stock rules, planner and buyer assignments, and the inventory planning code — without requiring the caller to join the full set of base item tables.

Although the view is documented as a system/planning support object, it is valuable as a single-row-per-item-per-organization source that abstracts the relationship across item master, organization item, item category, and organization parameter data. It is therefore commonly embedded in custom reports, interfaces, and planning extracts. Notably, the inventory planning code (INVENTORY_PLANNING_CODE) — the term the user searched for — is directly exposed here, making this view a convenient place to determine whether an item is planned as planned, unplanned, or not planned at the item/organization level.

Underlying Base Objects

The ETRM metadata states that no base objects are documented for this view, and that it is "Not implemented in this database" in the source extract. Despite that, the view text reveals the tables the definition draws upon. The primary driving table is MRP_AP_SYS_ITE… (aliased MSIK), the MRP system item source that supplies the bulk of item planning attributes. Supporting objects include:

• MRP_SYSTEM_ITEMS-class planning data (MSIK) — the authoritative planning attributes.
• Category data (DIC) — item category and category name (CATEGORY_ID, CATEGORY_NAME).
• Organization parameters (MP) — organization code, cost organization, and primary cost method.
• Planning parameters (MRPP) — default ABC assignment group and ranking.
• HR_ALL_ORGANIZATION_UNITS (HAOU) and the HR_SECURITY package — used to apply organizational security so that only records the user is permitted to view are returned.

The definition is a single ordered join with a hint of /*+ ORDERED */, and it derives INVENTORY_TYPE as the literal 1, indicating a system item classification.

Key Columns

• ORGANIZATION_ID, INVENTORY_ITEM_ID, BASE_ITEM_ID, ITEM_NAME, DESCRIPTION — item and organization identity.
• INVENTORY_PLANNING_CODE — the planning code for the item (planned / unplanned / not planned).
• MRP_PLANNING_CODE, PLANNING_MAKE_BUY_CODE — planning methodology and make/buy determination.
• FIXED_LEAD_TIME, VARIABLE_LEAD_TIME, PREPROCESSING_LEAD_TIME, POSTPROCESSING_LEAD_TIME, FULL_LEAD_TIME, CUMULATIVE_TOTAL_LEAD_TIME, CUM_MANUFACTURING_LEAD_TIME — lead-time attributes used by the planning engine.
• FIXED_ORDER_QUANTITY, FIXED_LOT_MULTIPLIER, MINIMUM_ORDER_QUANTITY, MAXIMUM_ORDER_QUANTITY, ROUNDING_CONTROL_TYPE, FIXED_DAYS_SUPPLY — order quantity modifiers.
• MRP_SAFETY_STOCK_CODE, MRP_SAFETY_STOCK_PERCENT, SAFETY_STOCK_BUCKET_DAYS, SHRINKAGE_RATE — safety stock and shrinkage rules.
• PLANNER_CODE, BUYER_ID, PLANNING_EXCEPTION_SET — ownership and exception-set assignment.
• MP.ORGANIZATION_CODE, COST_ORGANIZATION_ID, PRIMARY_COST_METHOD — organization-level context.
• CATEGORY_ID, CATEGORY_NAME, DEFAULT_ABC_ASSIGNMENT_GROUP — classification and ABC context.

Common Use Cases and Queries

The view is typically used to retrieve planning attributes for every item in an organization or to filter by the inventory planning code. A representative query identifying planned items is:

• SELECT organization_id, inventory_item_id, item_name, inventory_planning_code, mrp_planning_code, planning_make_buy_code FROM mrp_ap_sys_items_v WHERE organization_id = :org_id AND inventory_planning_code = 2;
• Comparing order modifier settings across items: select item_name, fixed_order_quantity, minimum_order_quantity, rounding_control_type for a planner or category.
• Auditing lead times and make/buy decisions: select item_name, full_lead_time, cumulative_total_lead_time, planning_make_buy_code filtered by planner_code.
• Validating safety stock strategy by reading mrp_safety_stock_code and mrp_safety_stock_percent.

Because the view applies HR organization security through HR_SECURITY.SHOW_RECORD, query results are automatically restricted to the organizations the signed-in responsibility is permitted to access. Where the metadata marks the object as not implemented, the view should be validated in the target database before use; if it is absent, equivalent attributes can be obtained from MRP_SYSTEM_ITEMS joined to MTL_SYSTEM_ITEMS and organization parameters.