Analytics Catalog/Data dictionary/INV_ITEM_LOCATIONS
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Data dictionary

INV_ITEM_LOCATIONS

InventoryUsed in 28 subject areas18 reporting columns

Inventory (INV).

Likely primary key: INVENTORY_LOCATION_ID (inferred from Oracle naming conventions, verify against Tables & Views)
Joins (inferred from key columns): ORGANIZATION_ID → INV_ORGANIZATION_DEFINITIONS_V

Columns

ColumnKeyIn reportsDescription (inferred)
DEPRECIABLE_FLAG●Indicator (Y/N) for the depreciable.
DESCRIPTION●Description.
DISABLE_DATE●Disable date.
END_DATE_ACTIVE●End date active.
INVENTORY_LOCATION_IDPK?●Identifier for the inventory location.
INVENTORY_LOCATION_TYPE●Type of inventory location.
LOCATOR_STATUS●Status of the locator.
ORGANIZATION_ID●Identifier for the organization.
PHYSICAL_LOCATION_CODE●Code identifying the physical location.
PICKING_ORDER●Picking order.
SEGMENT1●Segment1.
SEGMENT2●Segment2.
SEGMENT3●Segment3.
START_DATE_ACTIVE●Start date active.
STATUS_ID●Identifier for the status.
STRUCTURE_INSTANCE_NUMBER●Structure instance number.
SUBINVENTORY_CODE●Code identifying the subinventory.
SUBINVENTORY_ID●Identifier for the subinventory.

Used by reports

No cataloged report reads from this table yet, it's part of the broader Fusion dictionary.

Where this surfaces in OTBI

The OTBI subject areas that expose this table. In OTBI they combine only through shared dimensions or set operators such as union, inside one application; the owned conformed model joins this table across modules and systems on conformed keys.

Need the extract + dbt staging for INV_ITEM_LOCATIONS?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
Inventory as of any date · What the extract does not carry · The export ceiling