Why the PO account assignment category cannot be changed
The account assignment category field on a PO item is locked once the item has follow-on activity: a goods receipt, an invoice, a down payment, or an earmarked funds commitment already exist against that account assignment. The system protects the value flow already posted to FI/CO/FM. The category is also locked when field selection ties it to release status, or when the line is linked to a sales order.
Covers why buyers get a change-not-permitted error or a greyed-out field when trying to switch a purchase order line between cost centre, order, WBS or unassigned account assignment. Walks through the check sequence on PO history, funds commitment and field selection, and separates the data-level fixes (reverse and re-post) from the genuine configuration cases.
Published 16 Sept 2026· 1,131 words
The business symptom
A buyer or requisitioner tries to change the account assignment on a PO line, either the category itself (K to F, or U to K) or just the cost object underneath it, and gets an error such as the field being display-only in change mode, or a message stating the item cannot be changed because of existing follow-on documents. The complaint usually comes in as 'I need to move this PO to a different cost centre / WBS element and the system will not let me' or 'the account assignment tab is greyed out even though the PO is still open'. It is frequently reported alongside a goods receipt or invoice that was already posted, but the requester rarely connects the two events themselves.
The configuration behind it
- PO history already exists for the item: a goods receipt, service entry acceptance, or invoice has posted against the current account assignment. Changing the account assignment after value has flowed to FI/CO would orphan or misstate the posted document, so the field locks.
- A down payment has been made and cleared against the item's account assignment. Same protection logic as above, just triggered by FI-AP rather than MM.
- An earmarked funds commitment or budget reservation in Funds Management is tied to the specific account assignment. FM will not let the account object move underneath an active commitment without that commitment being reduced or reversed first.
- Field selection configuration ties the account assignment category to the item's release/approval status. Once the PO item has passed a release step, the category and account object become display-only by design, independent of whether a receipt exists yet.
- The item category and account assignment category combination is checked in customizing; the target category the user wants is not permitted for the current item category (standard, subcontracting, third-party), so the change is rejected as an invalid combination, not a locked field.
- The item is linked to a sales order, typically third-party or individual purchase order processing. The account assignment is derived from and tied to the SD document; it cannot be edited independently once that link exists.
- Multiple account assignment with distribution already used: several account objects share the value, and one or more distribution lines already carry posted quantity or value, blocking a category-level change on the whole item.
What to check
- ME23N: open the item, check the 'Purchase order history' tab for goods receipt, service entry, invoice or down payment lines against this item.
- ME22N: attempt the change and capture the exact message text and message number; it distinguishes a hard lock from an invalid combination.
- MIGO / MIR4: if history exists, identify the specific material or invoice document that needs reversal before the field will unlock.
- Account assignment tab (EKKN segment) on the item: check for more than one distribution line and whether any of them already carries posted value.
- Funds Management: check whether an earmarked funds document or active commitment line is attached to the PO item's account assignment.
- Release strategy tab: check if the item has already passed a release step; field selection may tie the account assignment lock to release status rather than to history.
- SPRO, account assignment category configuration (transaction OME9) and the item category / account assignment category combination table: confirm whether the target category is even permitted for this item category.
How to prove it in the data
Pull the PO history (EKBE) for the item and show non-zero quantity or value on movement type 101 or invoice category lines; that quantity is the reason the category is locked. Cross-check the account assignment segment (EKKN) for multiple distribution lines and flag which ones already carry posted value. If Funds Management is in scope, pull the commitment line tied to the PO item and show it is still open. Attach the exact error message number from the change attempt as corroboration.
Resolution path
If PO history is the cause, this is a data fix, not configuration: reverse the goods receipt (MIGO, movement reversal) or cancel the invoice (MR8M) first, change the account assignment, then re-post. This has real accounting consequences and should go through the same approval as any GR/invoice reversal. If an earmarked funds document or commitment is the cause, reduce or close that funds document in FM before the account assignment field unlocks; also a data-level action. If the lock comes from field selection tied to release status, and the business genuinely needs the category editable at that status, that is a configuration change to the field selection key or release strategy setup and requires a transport plus testing of the release workflow; it should not be applied as a one-off unlock. If the rejection is an invalid item category / account assignment category combination, the combination is disallowed by design; the correct action is to cancel and recreate the line with the right item category, not to force the combination through configuration. If the item is linked to a sales order, the account assignment cannot be changed at all on that PO line; the sales order or the PO line itself has to be cancelled and rebuilt.
The fix people try first (and why it fails)
The common reflex is to edit the account assignment segment directly through a table editor, or to force the field open with a screen variant, treating the lock as a UI nuisance. This bypasses the very check that protects the posted GR/IR and CO postings, and leaves the PO's value string, the material document, and the cost object out of sync with each other. A second reflex is deleting and re-adding the same line to sidestep the lock, which breaks the PO history link to any receipt or invoice already posted against the old line number and complicates GR/IR clearing at period end.
Whose problem this is
Purchasing raises the ticket but the diagnosis sits with MM functional support, pulling in FI-CO or FM ownership whenever a commitment or posted value is the blocker. The handover note should carry the PO number and item, the account assignment change requested, the PO history status, the exact error message, and whether a funds commitment or invoice is attached, so the receiving team does not have to re-run the same checks.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-functional-issues/account-assignment-category-change-rejected-on-the-purchase-orderERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.