A warehouse clerk receives a shipment two weeks early, three hundred units over what was ordered, against a PO that already had an advance shipment notice. No warning fired. No block. The receipt sailed through, and the mess only surfaced at month end when the numbers would not reconcile. Nobody did anything wrong at the dock. The system was set to allow all of it, because a handful of parameters on one setup page were left wide open. Receiving parameters are the quietest, most underestimated controls in Fusion, and they decide what your warehouse can and cannot do every single day.

Get them right and bad receipts stop at the door. Get them wrong, or leave them at defaults, and the warehouse becomes a place where anything goes.

One page, enormous reach

Everything here lives in the Manage Receiving Parameters task, set per inventory organization. That last part matters. These are not global. Each organization gets its own, which means each site can enforce its own discipline, and also means a new org set up carelessly inherits nothing useful. The page looks modest. Its reach is not.

The parameters split into a few groups that each answer a different question. When is a receipt too early or too late. How much extra quantity is too much. What happens when a shipment already has an ASN. And how received goods physically move through the warehouse. Walk through them the right way and the logic is clean.

The date controls, and the switch that makes them real

Three settings work as a set here, and missing the third is the classic mistake.

Early Receipt Tolerance in Days sets how many days ahead of the promise date a receipt is allowed. Late Receipt Tolerance in Days does the same on the back end. Simple enough on their own. But here is the catch that trips people up constantly. Those two numbers do nothing by themselves. The setting that gives them teeth is Receipt Days Exceed Action, and it has three values.

Set it to None and the tolerances are decorative. A receipt can come in five days early against a three day tolerance and the application waves it through, because no action is enforced. This is exactly the scenario from the opening, and it is almost always an oversight rather than a decision. Set it to Warning and the receiver sees a message but can still proceed, which suits a business that wants awareness without a hard stop. Set it to Reject and a receipt outside the window is blocked outright with an error.

So the tolerance days define the window, and the exceed action decides whether that window is a suggestion, a nudge, or a wall. Configure the days and forget the action, and you have built a fence with no gate.

One detail worth carrying into design conversations. The date math runs on regular calendar days, weekends and holidays included, and it keys off the promise date, falling back to the need by date when no promise date exists. That surprises people who assume working days.

The quantity control

Over-Receipt Tolerance sets the percentage above the ordered quantity that a receipt may reach. Order a hundred, set ten percent, and a hundred and ten is the ceiling. Its partner, Over-Receipt Action, works exactly like the date action. None lets any quantity through. Reject blocks anything past the ceiling with an error. Warning allows it with a message.

The pattern repeats on purpose. A tolerance sets the limit, an action decides how hard the limit bites. Once that pairing clicks for dates, it reads the same way everywhere on the page.

The ASN control people forget

Here is a subtle one with real consequences. ASN Control Action decides what happens when someone receives against a PO shipment that already has an advance shipment notice. Leave it at None and there is no validation at all, so a receiver can bypass the ASN entirely and receive straight against the PO, which quietly defeats the whole point of having suppliers send ASNs. Reject forces the ASN to be used by blocking the direct PO receipt. Warning flags it and lets the receiver choose.

For any client who invested in supplier ASNs, this setting decides whether that investment actually holds. It is easy to miss, and missing it undermines a process the business already paid to build.

Receipt routing, the physical flow

Receipt Routing sets how goods move once they arrive, and it is the parameter with the most operational weight. Three options. Direct Delivery sends goods straight to their destination in a single step, fast and light on transactions. Standard Receipt splits the flow into a receive step and a separate putaway, which gives a staging point and more control. Inspection Required inserts an inspection step before putaway, for goods that must be checked before they enter usable stock.

None of these is best in the abstract. A distribution center moving fast wants Direct Delivery. A regulated or quality sensitive operation wants Inspection Required. The right pick is a business decision about how much control each type of material actually needs, and the parameter sets the default the whole org will follow.

A few more worth knowing

Several smaller switches quietly shape daily work. Blind receiving hides the expected quantity from the receiver, forcing an honest manual count rather than letting them rubber stamp the number on screen, which is a genuine data integrity gain. Options exist to default lot and serial details from the ASN, saving the receiver from retyping what the supplier already sent. And receipt numbering can run manual or automatic, with automatic keyed off a starting sequence.

The theme across the whole page is control versus speed. Every parameter is a dial between letting the warehouse move fast and forcing it to move carefully. There is no universally correct setting, only the setting that matches how much rigor a given operation and a given material actually need.

That is why these parameters deserve a real conversation during setup, not a rushed pass with defaults. They are quiet, they sit on one unassuming page, and they govern what happens at the dock every hour of every day. Treat them like the control panel they are.

More practical Oracle Fusion walkthroughs land here every day. Video versions live on the SCM Simplified YouTube channel.