This page collects the refusals service users actually hit in xMatix — actions that report nothing pending, contract checks that block a line, a completion that won't set, campaign lines that won't edit — with what each one means and the fix, grounded in how the checks actually decide.
An action reports nothing pending
Fulfilment release, allocation, picking and invoicing all consume per-line pending counters, and each refuses to run when the relevant counter is zero everywhere: no pending fulfilment quantities, no pending allocation quantities, no pending picking quantities, no pending invoice quantities. The message is literal — everything is already processed at that stage, or was cancelled, or the earlier stage never ran (nothing can be allocated that was never released to fulfilment). Check the lines' pending counters and run the missing earlier stage. The Selective variants additionally refuse quantities above a line's pending amount, and the cancel actions refuse when there is nothing allocated or picked to cancel.
A Service Order quote action fails
Do not troubleshoot the seeded Perform Generate Quote action as though it were an eligibility problem: the current Service Order server-action handler does not support that action. The public procedure covers the verified full and selective invoicing paths only.
A line fails contract validation
The asset service contract checks produce distinct messages, and each points at a different fix:
| Message | Meaning |
|---|---|
| Missing Contract… | The service contract definition itself was not found — check the contract named on the line |
| No Active Asset Service Contract… | The definition requires a live entitlement and the asset has none that matches |
| The validity of this contract has lapsed! | An entitlement exists, but the document (or failure) date is past its valid-till date plus grace days |
| The Usage Hours for this contract has lapsed! | The recorded usage hours exceed the entitlement's ceiling plus grace |
| The usage-reading limit message | The odometer/usage reading exceeds the entitlement's ceiling plus grace |
| This is a Single Use contract and has already been utilised! | The entitlement was consumed by an earlier job |
| The Item is not in scope of active Service Contract! | A scope-restricted contract covers a fixed component list, and this item is not on it |
| The quantity of the Item exceeds the quantity allowed… | The item is in scope, but the line quantity is more than the scope line still has pending |
The lapse messages are deliberately specific: when a matching entitlement exists but is out of date, hours or reading, you get the actual reason rather than a generic "no active contract".
Work Completed is refused
The completion gate checks work-item lines only: every non-cancelled work item must have its work ended, and a work item without a time sheet counts as unfinished. End the work on the time sheet or cancel work that will not be done, then set the status again. Part allocation, picking and inventory posting are separate fulfilment controls and do not block this particular status transition.
A campaign action is refused
Service Campaign must be active, has not started yet, has ended — every processing action checks the active flag and the date window. Separately, Campaign mandated items cannot be modified / cannot be deleted protects lines that came from a mandatory campaign item; the mandate lives on the campaign item, not the line.
The VOR purchase order won't generate
No service order lines eligible for vehicle offroad purchase order means no line qualifies: eligible lines have an item, a positive quantity, and are not already linked to a purchase order line. Note also that only part items with no available stock at the order's branch get purchase order lines — parts already in stock are excluded because the fix there is allocation, not procurement.
A recommendation won't delete
Cannot delete a utilized service recommendation. Once invoicing marks a recommendation utilised it is part of the audit trail from finding to billed work, and deletion is refused permanently.
A field won't change
Three families of fixed fields on service documents:
- Branch and partner account on the order are fixed at creation — cancel and recapture to correct them.
- System-maintained flags and computed fields — line-population and fulfilment-release flags, a time sheet's standard and actual duration hours — are written by the platform and reject manual edits.
- A time sheet's order and order-line links are fixed at creation; create a new sheet on the right order instead.