Oracle Fusion · Data dictionary
INV_SUPPLY
InventoryUsed in 1 subject areas10 reporting columns
Inventory (INV).
Likely primary key: SUPPLY_SOURCE_ID (inferred from Oracle naming conventions — verify against Tables & Views)
Columns
| Column | Key | In reports | Description (inferred) |
|---|---|---|---|
| DESTINATION_TYPE_CODE | ● | Code identifying the destination type. | |
| EXPECTED_DELIVERY_DATE | ● | Expected delivery date. | |
| NEED_BY_DATE | ● | Need by date. | |
| QUANTITY | ● | Quantity. | |
| RECEIPT_DATE | ● | Receipt date. | |
| SUPPLY_SOURCE_ID | PK? | ● | Identifier for the supply source. |
| SUPPLY_TYPE_CODE | ● | Code identifying the supply type. | |
| TO_ORG_PRIMARY_QUANTITY | ● | To organization primary quantity. | |
| TO_ORG_PRIMARY_UOM_CODE | ● | Code identifying the to organization primary unit of measure. | |
| UOM_CODE | ● | Code identifying the unit of measure. |
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. You can't join across them in OTBI — the owned conformed model joins them on shared keys.
Need the extract + dbt staging for INV_SUPPLY?
We ship parameterized SQL, BICC config, and dbt models you own.