FB02 — Change a Posted FI Document

FB02 opens a posted FI document for limited editing. The structural fact that explains almost every support ticket against this transaction: SAP hard-codes a small list of fields that remain open after posting - assignment number, text, payment terms, baseline date for payment, dunning block, payment block, house bank and a handful of others. Everything that affects the accounting impact of the document - amount, debit/credit indicator, GL account, cost center, tax code, posting date, document date - is permanently locked once the document is saved. That lock is not configurable per se; it is standard behaviour to protect audit integrity. The changeable list also shrinks further once a line item is cleared, since a cleared item exposes even fewer editable fields than an open one.

Reached for after posting when a correction is needed but the correction does not touch the accounting entry itself - fixing a typo in the line item text, adding or correcting an assignment number for reconciliation, changing a payment block or dunning block on a vendor or customer line, or shifting the baseline date for cash discount calculation. Not used when the wrong account, amount, or cost center was posted; that always goes through FB08 reversal followed by a fresh posting. Not used for parked documents either - those are edited through the park/hold change transaction (FBV0), not FB02. On Fiori-enabled systems the equivalent app performs the same restricted edit but the underlying field list is identical.

To confirm what changed and who changed it, query CDHDR filtered on object class BELEG with object value built from company code, document number and fiscal year, then join to CDPOS on the same change number to see the field, old value and new value. Cross-check the current state in BSEG for that document and line item to confirm the change actually persisted. If CDHDR shows no entry for the expected timeframe, the change either did not save or was made through a different transaction entirely.

The underlying data model moved to the universal journal on S/4HANA, with BSEG now a compatibility view over ACDOCA, but the changeable-field restriction on FB02 is unchanged from the classic behaviour. FB02 still runs on S/4HANA; a Fiori app for managing and changing journal entries provides the same functional restriction through a browser-based screen. There is no relaxation of the locked-field list on S/4HANA.

Functional FI territory - the AP, AR or GL clerk performing the correction owns this end to end. ABAP involvement is rare and limited to custom field status configuration or a user exit restricting which fields are open. A clean handover states the document number, company code, fiscal year, the field that needs to change, and the exact reason it is greyed out if the request escalates beyond the clerk's authorization.

FB08 covers the reversal path required whenever the field that needs correcting is not on the FB02 changeable list. FBV0 handles the equivalent change for parked, not yet posted, documents. FS00 explains why a given field is locked or open, since field status groups on the GL account drive part of the changeable-field logic. FBL1N and FS10N are useful afterward to confirm the change is reflected correctly in line item and account balance displays.