Oracle Fusion SCM: On-Hand vs Available to Transact Quantity
Oracle Fusion on-hand quantity vs available to transact quantity difference
Also searched as
- Fusion inventory available to reserve vs available to transact
- why is on hand quantity not available to transact Oracle Fusion
- Fusion SCM review on-hand quantities material status
- Oracle Cloud inventory quantity not available for transfer
Short answer
On-hand is the physical quantity recorded in a subinventory, locator and lot. Available to transact is what is left after material status restrictions and pending demand are applied, and available to reserve is stricter again because existing reservations are deducted. To find the gap, open Review On-Hand Quantities in Inventory Management, group by status, and compare against reservations and pending transactions.
Applies to: Oracle Fusion Cloud SCM (Inventory Management), recent quarterly releases; labels vary slightly by release
How to trace why on-hand does not equal available to transact
- 1Open Inventory Management and use the On-Hand Quantity review page for the item and organization; display the on-hand, available to transact and available to reserve columns together.
- 2Expand the detail by subinventory, locator, lot and serial so you see which exact row carries the quantity, rather than the item total.
- 3Check the material status on the subinventory, locator, lot and serial. A status that does not allow transactable or reservable use removes the quantity from the available figures even though on-hand is unchanged.
- 4Look for reservations against the item (sales order, work order or transfer order demand) that have been pegged to that row.
- 5Check for pending transactions, such as an unprocessed move order allocation or a transaction sitting in an error state in the Manage Pending Transactions style review for the organization.
- 6Confirm the subinventory attributes: quantity tracked, reservable and nettable flags control whether its quantity counts as available.
- 7Fix the root cause: change the material status through a status update transaction, release the stale reservation, or resolve the errored transaction, then refresh the page.
- 8Re-query the on-hand view to confirm available to transact now matches your expectation.
The three quantities and what drives each
On-hand quantity is the sum of material actually recorded in the inventory organization at the lowest level of detail you track. It only changes through completed inventory transactions: receipts, issues, transfers, adjustments and so on. Nothing about demand or restrictions touches it.
Available to transact subtracts quantity whose material status disallows transactions, and quantity already committed to pending transactions that have not yet completed. Available to reserve goes further and subtracts quantity locked by existing reservations, and excludes anything in a non-reservable subinventory or status. Support teams often confuse the two and open a defect when the data is behaving as designed.
Material status is the usual culprit
Material status is an attribute you assign to subinventories, locators, lots and serials. Each status is a bundle of flags, for example whether the material is allowed for pick, ship, issue to work order, reserve or transact. Receiving routes often drop quantity into a receiving or inspection status that blocks use until quality releases it.
Because statuses stack, the most restrictive one wins. A lot with a Hold status inside an otherwise open subinventory will show on-hand but zero available. When a user complains that stock exists but the pick wave cannot find it, status is the first thing to check, ahead of any scheduling logic.
Reservations and pending transactions
Reservations are created by order promising and supply allocation, and can persist after the demand has changed. A cancelled or re-sourced sales order line can leave a reservation behind until it is released, which silently reduces available to reserve for everyone else.
Pending transactions are different: they are movements started but not completed, such as a transfer order shipment awaiting confirmation or a transaction that failed validation. They hold quantity out of the available figures and appear in the pending transactions review for the organization. Clearing the error, or deleting a transaction that can no longer succeed, releases the quantity.
Common pitfalls
- !Comparing item-level totals instead of subinventory, locator and lot level rows, which hides the row with the restrictive status.
- !Fixing the symptom with a miscellaneous receipt, which inflates on-hand and corrupts cost instead of correcting the status or reservation.
- !Assuming a non-nettable subinventory is broken, when nettable simply controls whether planning counts that stock as supply.
- !Releasing reservations in bulk without checking whether the demand behind them is still valid.
- !Ignoring errored pending transactions because they are on another page, so the same quantity keeps being blocked.
How an ERP-grounded AI assistant handles this
An assistant grounded in your Fusion SCM data, such as ERPray, can answer why 40 units of an item are on hand but not available by joining the on-hand row to its material status, reservations and pending transactions and showing the query behind the answer. It stays read-only and respects your Fusion roles; releasing a reservation or changing a status remains a human-approved action.
Frequently asked questions
Is available to transact the same as available to reserve?
No. Available to reserve also deducts existing reservations and excludes non-reservable subinventories or statuses. A quantity can be available to transact but not available to reserve if it is already promised to another order.
Does changing material status change on-hand quantity?
No. Status only changes what the quantity may be used for. On-hand stays the same, but available to transact and available to reserve move as the status flags permit or block use.
Why does planning ignore stock that shows on-hand?
Planning counts only nettable supply. If the subinventory is flagged non-nettable, or the status excludes it, the stock appears in inventory but not as supply in the plan.
Can I see this through reports instead of the page?
Yes, on-hand data is exposed through OTBI subject areas and BI Publisher, and REST resources exist for on-hand quantities. Confirm the exact subject area and fields available in your release before building a report.
Related
Oracle Fusion Inventory: Cycle Count Setup and Adjustment Approval
In Fusion, a cycle count is defined for an inventory organization with item selection, a count schedule and tolerances. Counts are entered, variances outside tolerance need approval, and approved adjustments become inventory transactions that are costed and accounted like any other. Most problems come from tolerance setup, approval routing or an adjustment account.
Error fixOracle Fusion: Cost Accounting Distributions Not Created
When an inventory or work order transaction has no cost accounting distributions, it is almost always stuck before costing: the item or organization is not set up in a cost organization and cost book, the item has no cost to apply, or the cost processing and accounting scheduled processes have not picked it up. Work through setup first, then the transaction status, then the jobs.
How-toFix Wrong Row Counts When Joining Across OTBI Subject Areas
Most subject areas in Oracle Fusion OTBI are self-contained and only support reliable analysis within their own folders; dragging a folder from a second subject area into the same analysis without a genuine shared join key silently produces duplicated or missing rows because OTBI has no way to correctly relate the two fact grains. Fix it by staying inside one subject area where possible, or by explicitly using a subject area that Oracle designed to cross domains, rather than combining arbitrary folders yourself.
Error fixClear An Oracle Fusion ESS Job Stuck In Blocked Status
A Blocked status on an Oracle Fusion Enterprise Scheduler (ESS) job almost always means an earlier instance of the exact same job is still running or stuck, and the job definition does not allow simultaneous requests. Find and finish, or cancel, the earlier request first; only then does the Blocked request move to Running.
Error fixFix FBDI Import Failures From Interface Table Validation Errors
When a Fusion FBDI import job errors out, the cause is almost always bad data in the interface tables (an invalid value set, a wrong date format, or a missing required column), not the ESS job itself. Open the process's Interface Errors Report or the Correct Import Errors spreadsheet to see the exact rejected rows and reason codes, fix the source data, and resubmit from the interface tables instead of re-running the whole FBDI load.
How-toOTBI vs BI Publisher: Which One Should You Use
Use OTBI when a business user needs ad hoc, self-service, real-time analysis with no fixed layout. Use BI Publisher when you need a pixel-perfect, scheduled, high-volume, or externally distributed document such as an invoice, check, or statutory report. Most Fusion implementations end up using both, not one instead of the other.
AI for ERPAI for Oracle Cloud SCM and Manufacturing, Grounded in Your Planning Data
Add grounded AI to Oracle Cloud SCM and Fusion Manufacturing: demand plans, work orders, and supplier data, answered on-prem or in a private cloud with full query visibility.
AI for ERPFusion Cloud ERP AI: OCI Generative AI Service vs. a Private LLM
Oracle's OCI Generative AI Service is a real option for Fusion Cloud ERP, but not the only one. Compare it honestly against a private LLM for sensitive data.
Stuck on Oracle Fusion Cloud SCM?
Talk to engineers who work inside Oracle Fusion Cloud SCM every week, and who build private AI that answers these questions from your own ERP data.