F-02 — General Posting
F-02 is used to post a general Financial Accounting document using posting keys and account types. It is most useful when accountants or consultants need a classic FI posting that is not tied to a specialized vendor, customer or G/L entry screen. 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 F-02 — General Posting. 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· 634 words
Esta página aún no está disponible en español.
Purpose
post a general Financial Accounting document using posting keys and account types. Treat F-02 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
F-02 is typically used when accountants or consultants need a classic FI posting that is not tied to a specialized vendor, customer or G/L entry screen. 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
- Confirm the posting belongs in FI and that a more specific business transaction is not required.
- Enter document header dates, company code, currency and reference.
- Enter debit and credit line items with the correct posting keys and accounts.
- Simulate to verify balance, tax and account assignments.
- Post and review the accounting document in FB03.
Key data objects
These are the fields and business objects that most often explain the result in F-02. Record them in support evidence so the next person can reproduce the same outcome.
- company code — verify the exact value, validity/date context and relationship to the source document.
- document and posting date — verify the exact value, validity/date context and relationship to the source document.
- document type/currency — verify the exact value, validity/date context and relationship to the source document.
- posting key/account — verify the exact value, validity/date context and relationship to the source document.
- amount and account assignment — 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 F-02 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
F-02 remains available in S/4HANA, while role-based Fiori journal-entry apps are often the preferred day-to-day surface. 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
- Using F-02 to bypass a business process such as MM invoice verification. Reconcile the exact business document and date before applying a workaround.
- Entering posting keys by memory without checking account type and debit/credit direction. Reconcile the exact business document and date before applying a workaround.
- Posting directly to reconciliation accounts where subledger posting is required. 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/f-02ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.