Order cockpit¶
The detail page of an order (/booking/{id}) opens with the process header. It
answers three questions without you having to look at the positions: where
does the record stand, how far have delivery and billing come, and what is next.
Process chain¶
The horizontal chain shows every stage of the order workflow:
Order request → Offer → Offer submitted → Order → Partial delivery → Delivery → Invoice → Completed
| Appearance | Meaning |
|---|---|
| filled, coloured background | already passed |
| strongly highlighted | current stage |
| plain, clickable | reachable now — one click sets the status |
| greyed out with a lock icon | currently refused; the tooltip names the reason |
| dashed | your installation has no status for this stage |
The tooltip is the instruction
A refused step does not just say "not possible", it says why: "The record has no positions", "No customer is assigned", "No position is assigned to a partial delivery". Fix what it names and the step becomes clickable.
If your order sits on a status your organisation created itself — a calibration workstation such as "Wareneingang" or "KP1" — the chain hides itself. It has no position there and would otherwise claim a stage that does not exist. Changing the status through "Status setzen" in the page header stays fully available.
Delivery and billing progress¶
Below the chain are two bars, not one:
- Delivered — how many positions are assigned to a partial delivery
- Invoiced — how many positions are assigned to a partial invoice
The two advance independently. An order can be three quarters delivered and not invoiced at all; a single progress figure would have to hide one of the two statements. The numbers come from the positions and refresh as soon as you create a partial delivery or partial invoice in the Positions tab.
An order without positions shows "No positions yet" and two empty bars — not 100 %.
Printing partial documents¶
In the Positions tab a button sits above the table for each part created:
L1, L2 … for partial deliveries, R1, R2 … for partial invoices.
Clicking one opens the familiar report dialog with a preview of the
document — download, print, file in the DMS, release or send it from there.
The document contains exactly the positions assigned to that part; the
Positions selector in the dialog can still narrow it down to types or
devices.
Why the subtotal can be smaller than the lines¶
Depending on the status, a document lists either the device types (offer, order confirmation) or the actual devices (delivery note, invoice). The other kind stays in the position list but does not count towards the total — otherwise the same item would appear twice on the invoice. Those lines are struck through in the Line net column, and the number of them is stated below the totals.
Next step¶
At the bottom right sits a button with the nearest allowed step, for example "Next step: Delivery". It does exactly what clicking that stage in the chain does; it is there so you do not have to look for it in the normal case.
The button appears only when there is an allowed step forward and you hold the
bookings_edit permission.
Which steps are refused¶
The server applies two kinds of rule:
Order of the chain. Delivery, invoicing and completion presuppose a placed order. You cannot invoice straight out of an offer — an offer is not a delivery basis.
Completeness of the data. Checked where a document reaches the customer:
| Target | Requirement |
|---|---|
| Offer submitted | at least one position |
| Partial delivery | at least one position, at least one of them assigned to a delivery part |
| Delivery | at least one position |
| Invoice | customer assigned, at least one position |
Not checked:
- the step to Order — creating the order shell and adding positions as the devices arrive is a common way to work
- moving backwards — correcting a mis-set status is normal work
- any transition involving a status your organisation defined