SAP functional issueObjectMaintenance order not settling to the cost centreModulePM_EAM

Maintenance Order Fails to Settle to Cost Centre

Maintenance order settlement to a cost centre fails when the settlement rule is missing or incomplete, the settlement profile does not permit cost centre as a receiver category, the cost centre is locked or outside its validity period, the CO posting period is closed, or the order has not been technically completed. Check the settlement rule in the order first, then the settlement profile, then the cost centre master and CO period status.

Covers why a plant maintenance order posts actual costs but will not settle them to the cost centre when KO88 is run, either as a background job or manually. Walks through the settlement rule, settlement profile, cost centre master, and CO period locking as the four places the failure usually originates, and separates the data fixes a planner can do from the configuration changes that need a transport.

Published 16 Sept 2026· 1,147 words

The business symptom

The maintenance planner or cost centre owner reports that costs booked against a maintenance order never show up on the cost centre report. Finance closes the period and the cost centre still shows zero for that order even though time confirmations, spare parts, and external service costs were posted weeks earlier. Sometimes the order shows as technically complete and even closed, but the balance carried forward keeps appearing on WIP or a settlement error log nobody looked at. The complaint usually surfaces during month end when controlling asks why an order has an open balance sitting on it, or when a cost centre manager disputes a variance because a chunk of real spend is missing from their report entirely.

The configuration behind it

  • No settlement rule exists on the order, or it was deleted when the order was changed, so KO88 has nothing to distribute to.
  • The settlement rule points to the wrong receiver category, or the percentage/equitable distribution across multiple rows does not sum to 100 percent, which the system rejects outright.
  • The settlement profile attached to the order type does not list cost centre as a valid receiver category, so even a correctly entered rule is rejected at save or at settlement run.
  • The cost centre is locked for actual postings, blocked entirely, or its validity period does not cover the settlement date, typically after a reorganisation or a cost centre closure that was not coordinated with open orders.
  • The CO posting period is closed for the relevant period and no back-posting period is open, so settlement is technically correct but cannot post.
  • The order status does not permit settlement, most commonly because the order was never set to technically complete and is still in released status, or a user status set by the plant blocks settlement.
  • The order has no actual costs to settle, or the balance is already zero, which is not a failure but is frequently misreported as one.
  • A secondary cost element required for settlement does not exist for the cost centre or company code, throwing an account determination error.
  • Cross-company code settlement is being attempted and the required cross-company settlement configuration for that combination is missing.

What to check

Start with the order in change mode and go to the settlement rule tab to confirm a rule exists, the receiver is a cost centre, and percentages total 100. Run the settlement transaction for that single order with the detailed log option rather than in a mass background job, because the log names the exact reason for rejection. Check the order status line for technical completion; a released order with open confirmations will often refuse settlement outright. Pull the cost centre master record and check its lock indicators and validity dates. Check whether the CO posting period for the settlement date is open. If the log references a missing cost element or account determination error, check whether the secondary cost element used for settlement exists for that controlling area. Finally check the order type's settlement profile configuration to confirm cost centre is listed as an allowed receiver.

  • Order settlement rule and status - change order transaction
  • Settlement run with detailed log - single order settlement transaction
  • Actual costs posted to the order - order cost report transaction
  • Cost centre master lock and validity - cost centre display transaction
  • CO period lock status - period control configuration
  • Settlement profile receiver categories - order type configuration

How to prove it in the data

Run the single-order settlement with the log turned on and capture the exact error text rather than describing the symptom secondhand. Pull the order's actual cost line items to show the postings exist and total a nonzero amount. Pull the cost centre's actual line items for the same period to show the amount is absent. If the rule and profile both check out, compare the order's settlement rule creation date against the cost centre's validity dates side by side; a mismatch there is the most common cause found after the obvious checks fail.

Resolution path

If the settlement rule is missing or wrong, this is a data fix on the individual order: recreate or correct the rule and rerun settlement, no transport needed. If the cost centre is locked, blocked, or outside its validity window, that is a master data correction in the cost centre record, again a data fix but one that controlling, not PM, usually has to authorise. If the CO period is closed, either open a back-posting period through the period control settings, which is a controlling operational action, or settle in the current open period, both of which are configuration-adjacent decisions rather than PM changes. If the settlement profile does not allow cost centre as a receiver category, that is a configuration change to the settlement profile itself and requires a transport through the normal change path, since it affects every order using that profile. If the order status blocks settlement, the fix is a business process step: complete outstanding confirmations and set the order to technically complete, then settle. Missing secondary cost elements require creation of the cost element, a master data action usually owned by controlling.

The fix people try first (and why it fails)

The reflex is to keep rerunning the mass settlement job hoping it clears itself, or to manually post an FI journal entry to the cost centre to make the number look right and move on. Rerunning without reading the individual log wastes cycles because the same rejection repeats every time. The manual journal entry is worse: it creates a posting on the cost centre that has no link back to the maintenance order, breaks the reconciliation between PM order costs and CO actuals, and leaves the order itself still unsettled with an open balance that resurfaces at year end.

Whose problem this is

Joint ownership between plant maintenance and controlling. PM owns the order status, confirmations, and the settlement rule itself. Controlling owns the settlement profile configuration, the cost centre master, and period locking. The handover note should carry the order number, settlement profile name, the exact settlement log error text, the receiver cost centre and its lock and validity status, and the posting period in question.

Related SAP objects

Reviewed pages this object connects to in the ERPClimb knowledge graph.

Source: ERPClimb — https://erpclimb.com/sap-functional-issues/maintenance-order-not-settling-to-the-cost-centreERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.