Results for “cst_xla_inv_sec_invs_ref_v”

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

Overview

The view CST_XLA_INV_SEC_INVS_REF_V is an APPS-owned database view in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified under the BOM — Bills of Material product family, although its columns and base object indicate it functions primarily as a subinventory reference source for inventory costing and Subledger Accounting (XLA/SLA) processing. The naming convention (CST_XLA_INV_SEC_INVS_REF_V) reflects its role within the Costing (CST) and XLA (Subledger Accounting) integration layer, where it supplies a lightweight, denormalized reference to secondary inventory (subinventory) attributes.

The view presents a curated projection of MTL_SECONDARY_INVENTORIES, exposing only the columns relevant to costing and accounting rules rather than the full set of subinventory attributes. This makes it suitable for joins in SLA event accounting and inventory valuation reporting without incurring the overhead of the wider base table.

Underlying Base Objects

The view is defined exclusively over a single base object: MTL_SECONDARY_INVENTORIES (referenced via a synonym in the APPS schema). No additional tables, joins, or unions are documented in the view text, so its contents are a direct, row-for-row reflection of the base subinventory definitions with limited column selection and one expression-based transformation (the ASSET_INVENTORY decode).

Because MTL_SECONDARY_INVENTORIES stores one row per subinventory per organization, the view likewise returns one row for each defined subinventory in each inventory organization. Filtering by organization is achieved through the exposed SUBINV_ORGANIZATION_ID column.

Key Columns

• SUBINVENTORY — The secondary inventory (subinventory) name, aliased from SECONDARY_INVENTORY_NAME. This is the human-readable identifier used in material transactions and costing queries.
• SUBINV_ORGANIZATION_ID — The inventory organization identifier, aliased from ORGANIZATION_ID. It scopes each subinventory to its owning organization.
• LOCATOR_TYPE — Indicates the type of locator control associated with the subinventory (for example, whether it uses locators and at what level of precision). This column is directly relevant to the user's search term "locator_type" and governs how stock locators are applied during receiving, issuing, and transfer transactions.
• ASSET_INVENTORY — A derived column produced by DECODE(ASSET_INVENTORY, 1, 'Y', 'N'), yielding 'Y' when the subinventory is asset-tracked and 'N' otherwise. This flag is significant for accounting, since only asset subinventories generate inventory asset balances and corresponding SLA entries.
• SUBINVENTORY_TYPE — Classifies the subinventory (for example, standard storage versus receiving or other functional types), which influences transaction and valuation behavior.

Common Use Cases and Queries

This view is commonly joined into costing and SLA queries to resolve locator control and asset status for a given subinventory. A typical retrieval lists asset subinventories for a specific organization:

SELECT subinventory,
       subinv_organization_id,
       locator_type,
       asset_inventory,
       subinventory_type
FROM   cst_xla_inv_sec_invs_ref_v
WHERE  subinv_organization_id = :org_id
AND    asset_inventory = 'Y';

Analysts investigating a specific locator type can constrain on the documented column directly:

SELECT subinventory, subinv_organization_id
FROM   cst_xla_inv_sec_invs_ref_v
WHERE  locator_type = :locator_type;

Because the view exposes only five columns, it is efficient for use as a lookup within larger costing joins, such as combining subinventory attributes with on-hand or transaction data. All statements should be grounded in the documented structure above; the view performs no aggregation and returns one row per subinventory per organization.