4.0 KiB
title, type, sources, related, last_compiled
| title | type | sources | related | last_compiled | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Tense Flow (Flux tendu) | concept |
|
|
2026-04-17 |
Tense Flow (Flux tendu)
Overview
Tense Flow (FR : flux tendu) enables picking directly from one or more source supports — typically to prepare an outbound order straight from reception without first putting the stock away. The stock never hits a "normal" storage location : it is replenished to a dedicated buffer (FR : poumon PREPARATION) and consumed from there virtually.
The flow combines:
- A tense-flow element + an associated buffer stage (typically named
PREPARATION). - A replenishment task from the source location(s) to the buffer, triggered at order release.
- Virtual picking on the RF terminal — the operator scans the source support + the newly created client container and declares the picked quantity.
- A closing step that transfers the client containers to the shipping buffer.
EasyS Configuration
- Add a Tense Flow element + an associated buffer (e.g.
PREPARATION). - Associate the tense-flow element to an aisle (
Count,Load,Pick,Put,Unload). - Associate the tense-flow element to the buffer as a
Delivery Stage. - Configure the source locations (buffers and racks) with the option "Allow origin of replenishement of tense flow" set to true, otherwise the replenishment task generated at "Lancer en flux tendu" will find no candidate origins.
⚠️ Tense Flow always creates a replenishment task towards the buffer first — the source locations must be eligible as tense-flow origins, not only as normal-flow origins.
Functional Flow
1. Launch in tense flow (SmartUI)
On a released outbound order, click "Lancer en flux tendu". The order transitions to "Assigned" and a replenishment task to the PREPARATION buffer is created automatically.
2. Execute the replenishment (RFT)
RFT menu : Tâches → Tâches à flux tendu. Execute the task to move stock from the source location to the buffer.
3. Virtual picking (RFT)
RFT menu : Ordres de sortie → Picking virtuel.
- Scan the source support (the pallet / container now at the buffer).
- Create a new client container — use the "Générer SSCC" button to assign a fresh SSCC.
- Scan the new container or the destination location.
- Enter the item + picked quantity (and any logistic attributes).
The system then offers to put the remaining stock away using the standard putaway strategies.
4. End of tense flow
Once all the client containers are filled, transfer them to the EXPEDITION buffer (the task is created automatically), then continue the order normally (truck loading, prepackaging, or transfer to the shipping dock).
Common Errors
"Lancer en flux tendu" creates no replenishment task : either the outbound order is not released yet, or the source locations are not marked as Allow origin of replenishement of tense flow. Tense Flow replenishment uses a separate eligibility flag from the standard replenishment — enable it on the candidate origins.
Virtual picking screen rejects the source scan : the stock is not on the PREPARATION buffer yet — the replenishment task must be executed first.
Remaining stock is not proposed for putaway : the tense-flow element is not associated to the buffer as a Delivery Stage — re-check EasyS step 3.
Related
- Picking — tense flow is a special picking mode that bypasses storage
- Replenishment — tense flow generates an upstream replenishment task with its own eligibility flag
- Reception — tense flow is commonly used to ship freshly received stock without storing it first
- Outbound Order — tense flow is triggered on a released outbound order
- Stations & Routes — tense-flow buffer and element are configured alongside standard stations