FBV2 — Change Parked Document
FBV2 is used to change header or line-item data on a parked FI document before it is finally posted. It is most useful when reviewers or processors need to correct incomplete or inaccurate parked accounting data. 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 FBV2 — Change Parked Document. 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· 602 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
change header or line-item data on a parked FI document before it is finally posted. Treat FBV2 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
FBV2 is typically used when reviewers or processors need to correct incomplete or inaccurate parked accounting data. 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
- Open the exact parked document.
- Compare the proposed posting with source evidence.
- Correct only fields that are wrong or incomplete.
- Save and re-run any required review or approval.
- Use FBV3 or the workflow to confirm the final parked state.
Key data objects
These are the fields and business objects that most often explain the result in FBV2. Record them in support evidence so the next person can reproduce the same outcome.
- parked document — verify the exact value, validity/date context and relationship to the source document.
- company code/fiscal year — verify the exact value, validity/date context and relationship to the source document.
- header fields — verify the exact value, validity/date context and relationship to the source document.
- line items — verify the exact value, validity/date context and relationship to the source document.
- workflow/review status — 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 FBV2 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
FBV2 remains the standard parked-document change transaction in classic FI workflows on S/4HANA. 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
- Changing a parked document after approval without revalidating authorization/workflow requirements. Reconcile the exact business document and date before applying a workaround.
- Treating parked data as if it already affected the ledger. Reconcile the exact business document and date before applying a workaround.
- Correcting the parked document when the source invoice or business request itself is wrong. 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/fbv2ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.