Arthur Ria
76 lines
4.0 KiB
Markdown
76 lines
4.0 KiB
Markdown
---
|
|
title: "Tense Flow (Flux tendu)"
|
|
type: concept
|
|
sources:
|
|
- sources/archives/16_Tense_Flow.md
|
|
related:
|
|
- concepts/picking.md
|
|
- concepts/replenishment.md
|
|
- concepts/reception.md
|
|
- concepts/order-outbound.md
|
|
- concepts/stations.md
|
|
last_compiled: "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:
|
|
1. A **tense-flow element** + an associated **buffer stage** (typically named `PREPARATION`).
|
|
2. A **replenishment task** from the source location(s) to the buffer, triggered at order release.
|
|
3. **Virtual picking** on the RF terminal — the operator scans the source support + the newly created client container and declares the picked quantity.
|
|
4. A closing step that transfers the client containers to the shipping buffer.
|
|
|
|
## EasyS Configuration
|
|
|
|
1. Add a **Tense Flow** element + an associated **buffer** (e.g. `PREPARATION`).
|
|
2. Associate the tense-flow element to an aisle (`Count`, `Load`, `Pick`, `Put`, `Unload`).
|
|
3. Associate the tense-flow element to the buffer as a `Delivery Stage`.
|
|
4. 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**.
|
|
|
|
1. Scan the **source support** (the pallet / container now at the buffer).
|
|
2. Create a **new client container** — use the **"Générer SSCC"** button to assign a fresh SSCC.
|
|
3. Scan the new container or the destination location.
|
|
4. 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](picking.md) — tense flow is a special picking mode that bypasses storage
|
|
- [Replenishment](replenishment.md) — tense flow generates an upstream replenishment task with its own eligibility flag
|
|
- [Reception](reception.md) — tense flow is commonly used to ship freshly received stock without storing it first
|
|
- [Outbound Order](order-outbound.md) — tense flow is triggered on a released outbound order
|
|
- [Stations & Routes](stations.md) — tense-flow buffer and element are configured alongside standard stations
|