Requirements

Purpose

The Requirements screen lists the missing articles reported by production. Each row states that a manufacturing order needs a certain quantity of a given article, on a given date.

It is a working list for supply: it answers the question "what is production waiting for that I need to order?". Once a requirement has been handled — order placed, goods taken out of stock — you archive it so that it disappears from the list.

Requirements are not created by hand

This screen is read-only. The rows come from the manufacturing orders and their operations, managed in Production management. No form allows a requirement to be added from the application.

Who can access this module?

The module is visible to accounts holding the Sales management right.

Access

• Menu: Sales management → Requirements
• Address: /besoins
• Screen title: Besoins

The requirement list

The top bar contains ☰ side menu, 🏠 home, the name of the signed-in account, the language selector and the account menu. There is no search field.

Column	Content
Date	The date the requirement was raised, in dd/mm/yyyy format.
OF	The number of the manufacturing order behind the requirement.
Client	The customer the manufacturing is launched for.
Réf. art.	The reference of the article awaited.
Article	Its designation.
Quantité	The quantity needed.
Action	📦 Archiver.

The list shows the first 50 requirements, sorted by name, with no pagination controls.

Beyond 50 requirements, the rest are invisible

The screen offers neither pagination nor a filter. If your production generates a lot of requirements, archive the ones that have been handled on a regular basis: that is the only way to bring the others up into the list.

Handling a requirement

The screen reports the requirement; it does not satisfy it. Handling happens elsewhere, in two stages.

1. Cover the requirement. Depending on the case:
   • the article is in stock → a stock release is enough, see Stock movements;
   • the article is missing → place a purchase order with the supplier, then receive it with a goods receipt note.
2. Archive the row on this screen, once the requirement is covered.

Group before ordering

Several manufacturing orders often ask for the same article. Go through the list and group the quantities of a single reference onto one purchase order, rather than placing one order per row.

Archiving a requirement

Click the 📦 Archiver icon on the row concerned. It disappears from the list, which reloads straight away.

No confirmation, no way back

Archiving is sent immediately on click: there is no confirmation request, no success message, and no way to unarchive from the interface. One unfortunate click removes the row from your working list for good.

Check the row — the MO, the article and the quantity — before clicking.

Archiving orders nothing and releases nothing from stock

Archiving merely removes the row from this list. It creates no order, triggers no stock movement and does not change the manufacturing order. Only archive after the requirement has genuinely been handled.

A failed archiving goes unnoticed

The list reloads whether the operation succeeded or not. If the row is still there after the reload, the archiving failed: try again, then contact support.

Messages and troubleshooting

Situation	Message	What to do
Requirement archived	No message	Check that the row has indeed disappeared from the list.
The row is still there after archiving	No message	The operation failed: try again, then contact support.
The ➕ button does nothing	No message	Normal behaviour: requirements are not created from this screen.
A handled requirement is still displayed	—	It has not been archived: click 📦 Archiver.
A requirement archived by mistake	—	No unarchiving is possible from the interface; contact support.
The list looks incomplete	—	It is limited to the first 50 requirements. Archive the rows that have been handled.

Known limitations in this version

• The ➕ button at the top of the screen has no effect: it corresponds to no action.
• Archiving is not confirmed and cannot be undone.
• No message confirms or denies the archiving.
• The screen has neither search nor pagination, and is limited to the first 50 requirements.
• The columns cannot be sorted: the list follows an imposed order.
• The list cannot be grouped by article, which means duplicates have to be spotted by eye before ordering.

See also

• Purchase orders — ordering the missing articles.
• Goods receipt notes — receiving the goods.
• Articles — the records of the articles awaited.
• Production management → Production launches / MOs — where requirements come from.
• Stock management → Stock movements — serving a requirement from stock.