Search Results nettable_quantity




Overview
Explore in AI Chat

Overview

The MRP_RHX_ONHAND_QUANTITIES_V view is an Oracle E-Business Suite Integration Toolkit (often referred to as the "RHX" or "Rapid Implementation" interface set) object delivered under the MRP – Master Scheduling/MRP product family. It is designed to expose on-hand quantity information for items that are recognized as planned items, so that the data can be consumed by external integration layers, planning extracts, or custom reporting rather than being queried directly from the raw inventory tables.

The view aggregates on-hand balances at the intersection of item and organization, and separates the results into nettable and nonnettable quantities. A useful consequence of this design is that the view returns planning-relevant on-hand figures without requiring the consumer to understand MTL schema join logic, subinventory attributes, or lot aliasing.

Underlying Base Objects

The view text is built from three principal sources: MTL_ONHAND_QUANTITIES (on-hand balances by subinventory and lot, aliased MOQ), MTL_SECONDARY_INVENTORIES (subinventory definitions and their availability type, aliased MSI/SUB), and the Integration Toolkit view MRP_RHX_PLANNED_ITEMS_V (aliased ITEMS), which restricts the population to items that the MRP planning process considers planned. The item/organization pair in the on-hand tables is joined to the planned-items view on ORGANIZATION_ID and INVENTORY_ITEM_ID, and the subinventory code is joined to MTL_SECONDARY_INVENTORIES on SECONDARY_INVENTORY_NAME and ORGANIZATION_ID.

Two query blocks are combined with a UNION ALL: one driving on-hand rows directly from MTL_ONHAND_QUANTITIES, and a second sourcing from a temporary structure (TEMP) for the additional quantities path. Both blocks derive nettable versus nonnettable amounts using a DECODE on the subinventory AVAILABILITY_TYPE attribute, and lot number parsing for the ATTRIBUTE_ALIAS column is conditional on the profile parameter MRP_I2_P_ENABLE_ABP and the separator defined by MRP_I2_P_INV_AA_SEP, resolved per organization through MRP_I2_ERP.GET_PARAMETER.

Key Columns

  • ITEM_ID / ORG_ID – The inventory item and organization identifiers, matching the primary keys of the planning entities.
  • ITEM_NUMBER – The concatenated user-facing item name from the planned items view, useful for display and CSV extracts.
  • SUBINVENTORY_CODE – The subinventory name where the on-hand quantity resides.
  • AVAILABILITY_TYPE – The subinventory availability indicator. A value of 1 marks the subinventory as nettable, in which case quantity flows into NETTABLE_QUANTITY; any other value routes quantity into NONNETTABLE_QUANTITY. This is the column most commonly referenced when filtering or grouping by MRP netting behavior.
  • SUM(NETTABLE_QUANTITY) – Aggregated quantity available to the MRP/MPS netting process.
  • SUM(NONNETTABLE_QUANTITY) – Aggregated quantity that is excluded from netting (for example, subinventories flagged as nonnettable).
  • ATTRIBUTE_ALIAS – A lot-derived attribute returned only when the ABP parameter is enabled; otherwise NULL. It is used to convey lot-level aliasing information to the integration consumer.

Common Use Cases and Queries

Because the view aggregates quantity and separates nettable from nonnettable on-hand, it is well suited to feeding planning extracts, material availability dashboards, and reconciliation reports between planning and inventory data. A typical query retrieving organization-level nettable on-hand by item is:

SELECT ITEM_NUMBER, ORG_ID, SUM(NETTABLE_QUANTITY) NETTABLE_ONHAND
FROM   MRP_RHX_ONHAND_QUANTITIES_V
GROUP  BY ITEM_NUMBER, ORG_ID;

To inspect only nonnettable balances and identify the subinventories driving them:

SELECT ITEM_NUMBER, SUBINVENTORY_CODE, SUM(NONNETTABLE_QUANTITY) NONNETTABLE
FROM   MRP_RHX_ONHAND_QUANTITIES_V
WHERE  NONNETTABLE_QUANTITY > 0
GROUP  BY ITEM_NUMBER, SUBINVENTORY_CODE;

Filtering on AVAILABILITY_TYPE is also common when a report needs to explain why a quantity was classified as nettable or nonnettable. Note that the view aggregates nettable and nonnettable quantities separately, so quantities cannot simply be re-summed across the two measures without understanding the aggregation grain (item, organization, subinventory, and availability type). When used inside the Integration Toolkit, the view is normally accessed programmatically rather than for interactive reporting, and consumers should account for the parameter-driven behavior of ATTRIBUTE_ALIAS. The documented metadata lists no explicit base tables under "Referenced base objects"; however, the view text confirms its dependence on the MTL on-hand, subinventory, and RHX planned-items structures as described above.