How-toOracle Fusion Cloud SCMInventory Management / Cycle Counting

Oracle Fusion Inventory: Cycle Count Setup and Adjustment Approval

Question
how to set up cycle count and approve adjustments in Oracle Fusion Inventory

Also searched as

  • Fusion cycle count adjustment approval
  • Oracle Cloud inventory cycle counting setup
  • Fusion cycle count tolerance and accounting
  • Fusion cycle count adjustment not posted

Short answer

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.

Applies to: Oracle Fusion Cloud SCM Inventory Management; labels and some features depend on release

How to run a cycle count end to end

  1. 1Define the cycle count for the inventory organization, selecting the items or categories to count and whether ABC classification drives frequency.
  2. 2Set count tolerances for positive and negative quantity and cost variance so only meaningful variances go to approval.
  3. 3Set the adjustment account for the count so approved adjustments have somewhere to post, or confirm it is derived from your cost accounting rules.
  4. 4Generate count requests or schedule the count so sequences are created for each item and location in scope.
  5. 5Enter counts against the count requests, including lot and serial detail where items are tracked.
  6. 6Review variances; those within tolerance are accepted, while those outside tolerance go to approval or recount.
  7. 7Approve or reject adjustments, or request a recount, in line with your authorization limits.
  8. 8Confirm the adjustment transactions complete, then check cost processing and accounting for the adjustments in Cost Management.

Definition, schedule and selection

The cycle count definition is the contract for the count: which organization, which items, how often, and what rules apply. ABC classes let high-value items be counted more often than low-value ones, which is the usual way to cover an inventory without a full wall-to-wall count.

Selection is where most surprises arise. Items that are not stocked, are disabled for inventory transactions, or are excluded by the selection criteria do not generate counts. If a location looks uncounted, check whether it was in scope before suspecting a scheduling fault.

Tolerances and approval

Tolerances separate noise from real discrepancy. A tight tolerance on a high-cost item sends nearly every count to approval, which overloads approvers, while a loose one lets real shrinkage pass without review. Set them by value and risk rather than a single global number.

Approval can be routed to a person or role based on the variance size. When an adjustment sits unapproved, the quantity in the system remains wrong and the book value is unchanged, so watch the approval queue as part of daily inventory control.

Adjustment transactions and accounting

Approved adjustments post as inventory transactions that change on-hand. Cost Management values them at the item cost and creates distributions, and Create Accounting turns them into subledger entries that hit inventory and the adjustment account in the general ledger.

If an adjustment has been approved but has not posted to the ledger, follow the same chain as any transaction: on-hand updated, costing processed, accounting created, then transferred. A gap at any step explains the difference between a counted quantity and a ledger balance.

Common pitfalls

  • !Using one tolerance for all items regardless of value, which overloads approvers or hides losses.
  • !Counting items in a subinventory with a restrictive material status and expecting available quantities to change.
  • !Leaving adjustments pending approval over a period close, so on-hand and the ledger disagree.
  • !Skipping lot and serial detail on tracked items, which causes count rejection or incorrect adjustments.
  • !Posting manual miscellaneous transactions to fix count variances instead of using the count adjustment flow.

How an ERP-grounded AI assistant handles this

ERPray, grounded on Fusion inventory and cost data, can show which counts are awaiting approval, the value of pending variances by item and subinventory, and which approved adjustments have not yet been costed or accounted. It reads only and shows the query, leaving approval decisions to your inventory controllers.

Frequently asked questions

Can I use ABC classification in Fusion cycle counts?

Yes, cycle counts can be driven by item classification so higher-value classes are counted more often. Define the classification and link it to the count frequency rules for your organization.

What happens to variances within tolerance?

They can be accepted without approval and adjusted, depending on how the count is configured. Variances outside tolerance go through approval or recount.

Where does the adjustment hit the ledger?

Through cost accounting and Create Accounting, which debit or credit inventory and the adjustment account per your accounting rules, then transfer to the general ledger.

Why was an item not included in the count?

Usually because it fell outside the selection criteria, is not stocked in the organization, or is not enabled for inventory transactions. Review the definition and item attributes first.

Related

How-to

Oracle Fusion SCM: On-Hand vs Available to Transact Quantity

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.

Error fix

Oracle 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-to

Oracle Fusion Period Close: A Practical Checklist

Closing a Fusion GL period cleanly means closing every feeder subledger first (Payables, Receivables, Costing, Fixed Assets), running Create Accounting to post everything to GL, reconciling subledger-to-GL balances, and only then setting the GL period status to Closed - not Close Pending, which still allows adjustments. Close Monitor gives a single dashboard of every subledger's close status instead of checking each module separately.

Error fix

Clear 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 fix

Fix 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-to

OTBI 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 ERP

AI 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 ERP

Fusion 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.