FB03 — Display Accounting Document
FB03 displays a posted Financial Accounting document with its header, line items, account assignments, clearing information, and navigation to related source documents. Use it to prove what SAP actually posted and to reconcile logistics or subledger activity to FI. In S/4HANA, distinguish the operational document view from Universal Journal reporting.
This practitioner page covers FB03, Display Accounting Document. It explains the transaction's operational purpose, the evidence to capture, the data or configuration objects that matter, and the failure patterns that commonly mislead SAP support teams.
Published 20 Sept 2026· 700 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
display posted FI documents with header, line items, account assignments and links to clearing or source documents. The useful way to think about FB03 is as part of an end-to-end business or technical flow, not as an isolated screen. Capture the exact organizational context, business object, user and timestamp before drawing conclusions, because those values determine which data and configuration the transaction reads.
When it is used
FB03 is typically used when validating what was actually posted, tracing an accounting error, or reconciling a logistics document to FI. It is also valuable during test cycles because it provides a repeatable way to prove what SAP processed, selected or rejected. In production, narrow the selection to the affected population first and separate diagnostic/display actions from functions that can post, retry, clear or change system state.
How to use it in practice
- Enter company code, document number and fiscal year from the source document or report.
- Review header dates, document type, reference and posting user.
- Inspect every line item, not just the line that appears wrong.
- Use environment/document relationships to navigate to clearing or originating logistics documents.
- Compare entry view and general-ledger view when document splitting or ledger detail matters.
Key data objects
These are the strongest anchors for a FB03 investigation. Record the values in the incident or test evidence so another consultant can reproduce the same conclusion and distinguish master data, configuration, authorization and transaction-state problems.
- company code — verify the exact value, organizational context and relationship to the affected document or interface.
- document number — verify the exact value, organizational context and relationship to the affected document or interface.
- fiscal year — verify the exact value, organizational context and relationship to the affected document or interface.
- posting/document date — verify the exact value, organizational context and relationship to the affected document or interface.
- line-item accounts and clearing references — verify the exact value, organizational context and relationship to the affected document or interface.
How to prove it in the data
Use a three-part proof: first establish the source document or request and its exact keys; second show the status, accounting/interface record or runtime evidence produced by SAP; third show the corrected result using the same selection. Cross-check neighboring transactions and logs rather than relying on a single screen message. This prevents a successful retry, changed selection or unrelated master-data edit from being mistaken for the real fix.
ECC vs S/4HANA
FB03 remains a core accounting diagnostic in S/4HANA. Universal Journal changes the storage model, but accountants and consultants still use document display to validate the posted business event. Availability does not automatically mean it is the preferred design for new work. On S/4HANA, pair familiar SAP GUI diagnostics with Fiori apps, Universal Journal, ODP, RAP/CDS or released APIs where those are the strategic surface for the process.
Common pitfalls and how to diagnose them
- Opening the right document number in the wrong company code or fiscal year. Recheck the exact keys and chronology before changing configuration or reposting data.
- Assuming the displayed entry view contains every ledger-specific detail. Recheck the exact keys and chronology before changing configuration or reposting data.
- Changing master data after posting and expecting the historical document to change. Recheck the exact keys and chronology before changing configuration or reposting data.
Whose problem this is
Primary ownership normally sits with the FI FICO team. Bring in Basis for infrastructure/runtime issues, Security for authorization evidence, and ABAP or integration developers only when the transaction evidence points to custom logic or mapping. A useful escalation includes exact keys, timestamp, 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/fb03ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.