Search Results unit_initialization_date




Overview
Explore in AI Chat

Overview

APPS.INVFV_SERIAL_NUMBERS is a Business Intelligence System (BIS) view in the Oracle E-Business Suite APPS schema, carrying FND Design Data reference INV.INVFV_SERIAL_NUMBERS. It is classified as a view rather than a base table and is documented as VALID at release levels 12.1.1 and 12.2.2. Its stated purpose is to present serial numbers together with their descriptions, offering a denormalized, read-only projection of serialized inventory, receiving, shipping, and manufacturing attributes.

The view is intended primarily for reporting and integration rather than transactional processing. Because it resolves foreign-key identifiers into human-readable names — item name, organization code and name, locator name, vendor name, and WIP entity name — it removes the need for consumers to join the core Inventory tables themselves. Report builders, discoverer workbooks, and external interfaces can therefore query a single object to obtain a complete descriptive picture of a serialized unit.

Underlying Base Objects

The documented dependency list identifies the following referenced objects: HR_ALL_ORGANIZATION_UNITS, MTL_ITEM_LOCATIONS, MTL_PARAMETERS, MTL_SERIAL_NUMBERS, MTL_SYSTEM_ITEMS, PO_VENDORS (itself a view), and WIP_ENTITIES. All are referenced through APPS synonyms except PO_VENDORS, which is a view.

The driving table is MTL_SERIAL_NUMBERS, which holds the serial number record and the transaction, receipt, and shipment dates. MTL_SYSTEM_ITEMS supplies item-level attributes used to derive the item name key flexfield, while MTL_PARAMETERS provides organization context and MTL_ITEM_LOCATIONS supplies locator information. HR_ALL_ORGANIZATION_UNITS resolves the inventory organization code and name. The vendor name is obtained through PO_VENDORS, and WIP_ENTITIES supplies the originating work in process entity name for units built internally. This dependency pattern confirms the view is an Inventory-centric construct that reaches across Procurement and Work in Process to enrich each serial record.

Key Columns

The view exposes 26 columns. The primary identifier is SERIAL_NUMBER (VARCHAR2(30)), accompanied by INVENTORY_ITEM_ID and the descriptive _KF:INVENTORY_ITEM_NAME. Organization context is provided by ORGANIZATION_ID, ORGANIZATION_CODE, and ORGANIZATION_NAME.

UNIT_INITIALIZATION_DATE is a DATE column representing the point at which the serialized unit was initialized in Oracle Inventory. It is frequently queried to determine how long a unit has existed in the system and to reconcile serial records against acquisition or build dates. Related date columns include RECEIPT_DATE and SHIP_DATE.

Location and categorization attributes include SUBINVENTORY_NAME, INVENTORY_LOCATOR_ID, the descriptive _KF:INVENTORY_LOCATION_NAME, REVISION, and LOT_NUMBER. Status is surfaced through _LA:SERIAL_NUMBER_STATUS. Manufacturing and vendor traceability is provided by ORIGINAL_WIP_ENTITY_ID, ORIGINAL_WIP_ENTITY_NAME, ORIGINAL_UNIT_VENDOR_ID, VENDOR_NAME, VENDOR_SERIAL_NUMBER, and VENDOR_LOT_NUMBER. Transaction metadata includes LAST_TRANSACTION_ID and LAST_RECEIPT_ISSUE_TYPE, while the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and END_ITEM_UNIT_NUMBER complete the structure.

Common Use Cases and Queries

Typical applications include serial number genealogy and traceability reports, cycle count reconciliation, warranty and asset age analysis, and vendor return or recall investigations.

To retrieve serialized units filtered by initialization date for a given organization:

  • SELECT serial_number, inventory_item_id, _KF:INVENTORY_ITEM_NAME, organization_code, unit_initialization_date, _LA:SERIAL_NUMBER_STATUS FROM apps.invfv_serial_numbers WHERE organization_code = :org AND unit_initialization_date BETWEEN :from_date AND :to_date ORDER BY unit_initialization_date;
  • SELECT serial_number, vendor_name, vendor_serial_number, vendor_lot_number, receipt_date FROM apps.invfv_serial_numbers WHERE vendor_name IS NOT NULL;
  • SELECT serial_number, original_wip_entity_name, ship_date FROM apps.invfv_serial_numbers WHERE original_wip_entity_id IS NOT NULL AND ship_date IS NOT NULL;

Because the view is a BIS construct owned by APPS, queries should be schema-qualified and treated as read-only. Filtering on UNIT_INITIALIZATION_DATE is the most direct path when the search objective concerns when a unit entered Inventory.