FBV3 — Display Parked Document
FBV3 is used to display a parked FI document without changing it. It is most useful when support, approvers or auditors need to inspect a parked document's header, line items and status before 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 FBV3 — Display 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· 601 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
display a parked FI document without changing it. Treat FBV3 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
FBV3 is typically used when support, approvers or auditors need to inspect a parked document's header, line items and status before 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
- Enter the parked document keys.
- Review header dates, currency, reference and document type.
- Inspect all line items and account assignments.
- Compare with the source document or approval request.
- Use the result to decide whether the document should be changed, posted or rejected.
Key data objects
These are the fields and business objects that most often explain the result in FBV3. 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/reference — 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.
- parking user/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 FBV3 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
SAP documents FBV3 as the display transaction for parked documents and it remains useful in 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
- Confusing a parked document with a posted accounting document. Reconcile the exact business document and date before applying a workaround.
- Checking only the header and missing line-item errors. Reconcile the exact business document and date before applying a workaround.
- Using current master data to explain values that were entered manually into the parked 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/fbv3ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.