Orchestrate

Nowhere to stage the pick

Break-fix drill · Logistics · about 5 minutes · starts after stage 11 of 11, "Pay and close the month", and the Warehouse chapter up to "Seal kits to a distributor"

What the user reports

Monday 21 December. Hallam's delivery for 10 seal kits (reference HFS-PO-7871) is ready to pick, and the shelf holds 90. On Friday the supply chain consultant started renaming the staging lanes after the dock doors.

The error: Pick tasks for Hallam's delivery refused: RKDC has no staging bin.

What you'll do

  1. See the problem as the warehouse clerk: On Outbound and picking, create the pick tasks in RKDC for Hallam's delivery of 10 CP-SK200 (reference HFS-PO-7871).
  2. Find the cause: There is stock to pick and nothing blocks the shelf. Why does a pick task need a staging bin before it can be created?
  3. Fix it as the supply chain consultant.
  4. Prove it: run the step that failed again.

Start the drill

The drill runs in the lab on its own prepared copy of the fictional Calder Pumpworks, saved in this browser apart from your company. All codes and values are fictional course labels.

Answer and explanation (open after the drill)

The fix: A task says where the stock goes as well as where it comes from, and picks go to the staging area.

A warehouse task is a move from one bin to another. A pick takes the carton from the shelf to the staging area, where the shipment is gathered for the truck, so the task needs a destination bin before it exists. The staging area still exists as a storage type, but without a bin it has no address. Nothing posts at staging: the goods issue later posts from the storage location, and the shipping point is unchanged.

Why it broke

Every warehouse task needs a source and a destination bin, so a storage type with no bins is a dead end for every process that goes through it. Renaming bins by deleting first and creating later leaves a gap in which picking stops. The lab refuses the pick at once; a real system would also stop at task creation, often with a message about the destination.

How teams prevent it

Rename or replace bins by creating the new ones first, moving work to them, and deleting the old ones last, in the test system first. Before deleting a bin, check that it is empty, that no open task points at it, and that its storage type keeps at least one bin.

Across teams

The warehouse clerk can't pick, customer service has Hallam waiting, and the shipping team has a truck at 14:00. The bin belongs to the warehouse layout, owned by the supply chain consultant during the project and the warehouse's key user after go-live.

Where AI fits

A check before deleting a bin (is it empty, is it referenced, is it the last one of its type?) is plain automation. An assistant can turn the error into a clear explanation and find the recent layout change behind it (retrieve). It should not create bins on its own; the layout describes a real building.

Learn more: Warehouse and transportation execution

All drills · Back to the lab

Sign in to track your progress

We'll email you a one-time sign-in link. No password needed.

or

Tell us a little about you

Optional, every field. It helps us pitch answers to your questions at the right level and decide which topics to write next. It is never shown publicly, and you can change or clear it anytime from the account menu.

SAP areas you work in