Results for “max_quantity”

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

Overview

The CSP_PLANNING_SUBINVENTORY_HDR_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite Spares Management (CSP) product. It presents a consolidated, item-level picture of planning subinventories by joining usage header definitions to item master attributes and subinventory min-max planning settings. Because the view exposes Item Number, Item Description, Minimum Quantity, and Maximum Quantity alongside the core keys (inventory item, organization, and secondary inventory), it is designed to support spares planning enquiries, replenishment analysis, and downstream integrations that require a denormalised view of subinventory-level planning data.

Its principal filtering behaviour is defined within the view text: only rows from CSP_USAGE_HEADERS where HEADER_DATA_TYPE = 1 are returned. This restricts the result set to usage headers representing planning data, so the view does not surface every usage header definition stored in the base table.

Underlying Base Objects

The view is defined over three referenced objects as documented in the ETRM metadata:

• CSP_USAGE_HEADERS (SYNONYM) — the driving table, aliased as CUH. It supplies USAGE_HEADER_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, and SECONDARY_INVENTORY, and is filtered on HEADER_DATA_TYPE = 1.
• MTL_ITEM_SUB_INVENTORIES (SYNONYM) — the item/subinventory planning table, aliased as MISI. It provides MIN_MINMAX_QUANTITY and MAX_MINMAX_QUANTITY, joined to the usage header on inventory item, organization, and secondary inventory.
• MTL_SYSTEM_ITEMS_B_KFV (VIEW) — the key flexfield view over the item master, aliased as MSI. It supplies CONCATENATED_SEGMENTS (rendered as ITEM_NUMBER) and DESCRIPTION (rendered as ITEM_DESCRIPTION), joined on inventory item and organization.

All joins to MTL_SYSTEM_ITEMS_B_KFV and MTL_ITEM_SUB_INVENTORIES use the outer-join (+) operator, so usage header rows are preserved even where no matching item master or min-max record exists. The result set is ordered by the item's concatenated segments, producing output sorted by item number.

Key Columns

• USAGE_HEADER_ID — primary key of the CSP usage header; identifies the planning header record.
• INVENTORY_ITEM_ID — surrogate key of the inventory item, joining to the item master.
• ORGANIZATION_ID — the inventory organization in which the item and subinventory reside.
• SECONDARY_INVENTORY — the subinventory name for which planning quantities apply.
• ITEM_NUMBER — the concatenated item key flexfield segments, providing the user-facing item identifier.
• ITEM_DESCRIPTION — the item's descriptive text from the item master.
• MIN_QUANTITY — the minimum min-max planning quantity from MTL_ITEM_SUB_INVENTORIES.
• MAX_QUANTITY — the maximum min-max planning quantity from MTL_ITEM_SUB_INVENTORIES.

Common Use Cases and Queries

Typical usage covers spares planning reports, min-max threshold reviews, and integration extracts feeding replenishment or planning systems. A representative query retrieving planning data for a specific organization is:

• SELECT item_number, item_description, secondary_inventory, min_quantity, max_quantity FROM csp_planning_subinv_hdr_v WHERE organization_id = :org_id ORDER BY item_number;
• SELECT item_number, secondary_inventory, max_quantity FROM csp_planning_subinv_hdr_v WHERE min_quantity IS NOT NULL; — to isolate items with defined min-max thresholds.
• SELECT organization_id, COUNT(*) FROM csp_planning_subinv_hdr_v GROUP BY organization_id; — to audit planning header coverage per organization.

Because the joins are outer joins, consumers should anticipate NULL item numbers, descriptions, or quantities where the corresponding item master or min-max record is absent, and should apply appropriate NVL handling in reporting logic.