Applicability — ad-hoc relocation
An ad-hoc relocation records a move that has already happened, without a plan upfront. The document is created with the Ad-hoc flag set; facts are then added directly; the system moves the document to Completed automatically once facts are saved. No reservations are made, no incoming-stock records are created.
Server grouping note
To reduce document noise, the server groups ad-hoc facts that share the same executor, warehouse, and hour of day into a single document. When the operator saves a new ad-hoc fact, the server may attach it to an existing ad-hoc document instead of creating a new one — if such a document is found that meets all three conditions and was opened earlier in the current hour. The result is the same from the operator's point of view (the move is recorded) but the document list shows one entry per operator-hour rather than one per fact.
When to choose planned instead
If the move is known in advance — a planned consolidation, a replenishment run, an assignment to a specific operator — use the planned relocation flow so the system reserves stock and prevents conflicts.
On PDTFull PDT flowOn the PDT, ad-hoc relocation uses a dedicated 2-tab screen with a streamlined zone form.