Search Results inv_item_serial_num_ctrl_code

Overview

AR_INVENTORY_L_V is a seeded Oracle E-Business Suite view owned by the APPS schema and shipped as part of the Oracle Receivables (AR) product. Its documented purpose is to serve as an inventory item line extract. The view is primarily intended to support the Oracle Subledger Accounting (SLA) extraction architecture, where it supplies inventory-related descriptive and attribute data for Receivables transaction lines flowing into the accounting extract. It is classified as VALID and is available in both EBS 12.1.1 and 12.2.2.

The view exposes inventory item context — item description, item type, sales account, serial number control code, category, and global descriptive flexfield attributes — alongside warehouse identification through both a code and a name. Because the search term in question is "warehouse_name," the relevant column is WAREHOUSE_NAME, aliased from ORG_ORGANIZATION_DEFINITIONS.ORGANIZATION_NAME, with a companion column WAREHOUSE_CODE drawn from ORGANIZATION_CODE. This makes the view useful wherever a human-readable warehouse identifier is required rather than a numeric organization ID.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects: AR_XLA_LINES_EXTRACT (SYNONYM), HR_GENERAL (PACKAGE), HR_SECURITY (PACKAGE), MTL_CATEGORIES_B (SYNONYM), MTL_CATEGORY_SET_VALID_CATS (SYNONYM), MTL_ITEM_CATEGORIES (SYNONYM), MTL_SYSTEM_ITEMS_B (SYNONYM), and ORG_ORGANIZATION_DEFINITIONS (VIEW).

The driving object is AR_XLA_LINES_EXTRACT (aliased L), which holds the extract line rows and supplies EVENT_ID, LINE_NUMBER, LANGUAGE, LEDGER_ID, LEVEL_FLAG, WAREHOUSE_ID, SO_ORGANIZATION_ID, and INVENTORY_ITEM_ID. Item master data is joined from MTL_SYSTEM_ITEMS_B (aliased MTLBF), while category information flows through the outer-joined chain of MTL_ITEM_CATEGORIES, MTL_CATEGORIES_B, and MTL_CATEGORY_SET_VALID_CATS. Warehouse naming is resolved from ORG_ORGANIZATION_DEFINITIONS (aliased O). The HR_GENERAL and HR_SECURITY packages are referenced to support organization security and access control. The critical join predicate is MTLBF.ORGANIZATION_ID = NVL(L.WAREHOUSE_ID, L.SO_ORGANIZATION_ID), mirrored on the organization and item-category joins.

Key Columns

• WAREHOUSE_NAME / WAREHOUSE_CODE — Organization name and code derived from ORG_ORGANIZATION_DEFINITIONS for the resolved warehouse or sales organization.
• INV_ITEM_DESCRIPTION — Item description from MTL_SYSTEM_ITEMS_B.DESCRIPTION.
• INV_ITEM_INVENTORY_ITEM_ID — Surrogate inventory item identifier.
• INV_ITEM_TYPE — Item type classification.
• INV_ITEM_SALES_ACCOUNT — Sales account associated with the item.
• INV_ITEM_SERIAL_NUM_CTRL_CODE — Serial number control code for the item.
• INV_ITEM_CAT_ID — Category identifier from MTL_ITEM_CATEGORIES (category set 1).
• INV_ITEM_GLOBAL_ATTR1 through INV_ITEM_GLOBAL_ATTR10 and INV_ITEM_GLOBAL_ATTR_CAT — Global descriptive flexfield attribute columns and category.
• EVENT_ID, LINE_NUMBER, LEDGER_ID, LANGUAGE — Extract line context carried from AR_XLA_LINES_EXTRACT.

Common Use Cases and Queries

Typical usage centers on extracting inventory item detail for accounting and reporting, filtering extract rows, or looking up warehouse names associated with item lines. The view's default result set is constrained to LEVEL_FLAG = 'L' rows.

• Warehouse-oriented lookup: SELECT event_id, line_number, warehouse_name, warehouse_code, inv_item_description FROM ar_inventory_l_v WHERE warehouse_name = 'M1 - Seattle Manufacturing';
• Item attribute extract: SELECT inventory_item_id, inv_item_global_attr1, inv_item_global_attr2 FROM ar_inventory_l_v WHERE ledger_id = :ledger;
• Category reporting: SELECT inv_item_cat_id, warehouse_name, COUNT(*) FROM ar_inventory_l_v GROUP BY inv_item_cat_id, warehouse_name;
• Integration: Joining to AR_XLA_LINES_EXTRACT or SLA tables on EVENT_ID and LINE_NUMBER to enrich accounting extracts.

Because warehouse naming is resolved via NVL(WAREHOUSE_ID, SO_ORGANIZATION_ID), the view returns a meaningful warehouse for both inventory and sales-order organization contexts, which is why WAREHOUSE_NAME is frequently the target column in ad hoc queries.