Results for “okl_am_subinventory_uv”

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

Overview

OKL_AM_SUBINVENTORY_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, part of the OKL (Lease and Finance Management) product family. Within EBS 12.1.1 and 12.2.2, the view exposes a filtered, de-duplicated list of asset subinventories used by the Lease Management remarketing setup screen. Users searching for the column or concept secondary_inventory_name commonly encounter this view because its first projected column carries exactly that name, sourced from Oracle Inventory's MTL_SECONDARY_INVENTORIES table. The view presents only those subinventories that are currently active (not disabled), locator-controlled, asset-tracked, and reservable, so that the remarketing setup LOV (list of values) returns only inventory organizations and subinventories suitable for remarketed leased assets. Its status is documented as VALID, and its purpose is limited to read access for setup and inquiry rather than transactional processing.

Underlying Base Objects

The view is defined over a single base object, MTL_SECONDARY_INVENTORIES, referenced through a synonym in the APPS schema. MTL_SECONDARY_INVENTORIES is the Oracle Inventory master table for subinventory definitions. The view applies a WHERE clause that filters the base table on four criteria:

• Active records: NVL(DISABLE_DATE, SYSDATE+1) > SYSDATE — records with no disable date or a disable date in the future are retained, excluding expired subinventories.
• LOCATOR_TYPE = 1 — only subinventories configured as locator-controlled are included.
• ASSET_INVENTORY = 1 — only subinventories flagged as asset inventory are included.
• RESERVABLE_TYPE = 1 — only reservable subinventories qualify.

A SELECT DISTINCT is applied to eliminate duplicates. No join to MTL_SYSTEM_ITEMS, MTL_PARAMETERS, or any OKL table is present in the documented view text, so the view is self-contained and depends solely on the Inventory subinventory master.

Key Columns

The view exposes two columns:

• SECONDARY_INVENTORY_NAME — the unique subinventory name within its inventory organization. This is the columnmost frequently referenced by users searching for "secondary_inventory_name", and it is the value displayed in reminder/remarketing setup LOVs.
• DESCRIPTION — the descriptive text attached to the subinventory in MTL_SECONDARY_INVENTORIES, shown alongside the name to aid selection.

Note that the view does not project ORGANIZATION_ID or INVENTORY_ITEM_ID, so it is not organization-scoped at the row level; results represent subinventory names that satisfy the criteria across all inventory organizations accessible in the queried context. Users requiring organization-level filtering must join back to MTL_SECONDARY_INVENTORIES on SECONDARY_INVENTORY_NAME to obtain ORGANIZATION_ID.

Common Use Cases and Queries

The principal use case is populating the remarketing setup screen's subinventory LOV, ensuring that only eligible asset subinventories are selectable. Reporting and integration queries typically retrieve the list of valid asset subinventories for validation or reference purposes. A representative query is:

• SELECT secondary_inventory_name, description FROM apps.okl_am_subinventory_uv ORDER BY secondary_inventory_name;
• To scope by organization: SELECT msi.organization_id, msi.secondary_inventory_name, msi.description FROM apps.okl_am_subinventory_uv uv, apps.mtl_secondary_inventories msi WHERE uv.secondary_inventory_name = msi.secondary_inventory_name AND msi.organization_id = :org_id;
• To validate a specific subinventory name: SELECT secondary_inventory_name, description FROM apps.okl_am_subinventory_uv WHERE secondary_inventory_name = :name;

Because the view is read-only and defined in the APPS schema, it should be queried rather than modified. Performance is generally acceptable provided the base table's indexes on SECONDARY_INVENTORY_NAME and ORGANIZATION_ID are intact, though the SELECT DISTINCT and NVL-based date predicate may limit index usage on very large subinventory populations.