FB09 — Change Line Items
FB09 is used to change permitted fields on already-posted FI document line items without altering the accounting amount or account. It is most useful when assignment, text, payment-related or other changeable line-item attributes need correction after posting. Start with the exact organizational keys, business document and date, then reconcile the resulting SAP document or status before changing master data or configuration.
Verified practitioner reference for FB09 — Change Line Items. The page covers purpose, when to use it, practical execution, the key business data to capture, how to prove the result, S/4HANA context, common mistakes, ownership and related SAP objects.
Published 19 Sept 2026· 614 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
change permitted fields on already-posted FI document line items without altering the accounting amount or account. Treat FB09 as one step in an end-to-end process. Values shown or posted here are usually driven by master data, organization, dates and preceding documents, so an accurate diagnosis starts by preserving those inputs rather than changing the symptom screen first.
When it is used
FB09 is typically used when assignment, text, payment-related or other changeable line-item attributes need correction after posting. It is also valuable in project and regression testing because it provides a repeatable business state. In production, use the narrowest document or organizational selection that answers the question and capture the before-state before any posting, clearing or configuration change.
How to use it in practice
- Display the accounting document first and identify the exact line item.
- Confirm the target field is allowed to change after posting.
- Change only the field required by the business correction.
- Save and inspect the document/change history.
- Re-run downstream reporting or clearing selection if it depends on the changed field.
Key data objects
These are the fields and business objects that most often explain the result in FB09. Record them in support evidence so the next person can reproduce the same outcome.
- company code/document/year — verify the exact value, validity/date context and relationship to the source document.
- line item — verify the exact value, validity/date context and relationship to the source document.
- changeable field — verify the exact value, validity/date context and relationship to the source document.
- old and new value — verify the exact value, validity/date context and relationship to the source document.
- change documents — verify the exact value, validity/date context and relationship to the source document.
How to prove it in the data
Use document flow and chronology. Start from the source business event, inspect the FB09 document or master data, then follow the resulting accounting, purchasing or asset document and reconcile amount, quantity, account assignment and status. A correct proof uses the same company code or plant, business date, document keys and currency/unit context at every step.
ECC vs S/4HANA
FB09 remains a controlled line-item-change transaction in S/4HANA for fields permitted by FI configuration. Where S/4HANA offers a Fiori successor or a changed data model, the classic transaction can still be valuable for support, but the strategic process and clean-core guidance should govern new implementations.
Common pitfalls and how to diagnose them
- Expecting FB09 to change amount, account or other immutable accounting content. Reconcile the exact business document and date before applying a workaround.
- Changing assignment/text to make reconciliation appear correct without fixing the business cause. Reconcile the exact business document and date before applying a workaround.
- Editing the wrong line item in a multi-line document. Reconcile the exact business document and date before applying a workaround.
Whose problem this is
Primary ownership is the Finance/Controlling team, with adjacent teams involved when the evidence crosses into Asset Accounting, Project System, tax, Basis, Security or integration. Escalate with document numbers, organization, dates, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/fb09ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.