F.05 — Foreign Currency Valuation - Classic
F.05 is used to run classic foreign-currency valuation for open items and foreign-currency balances in ECC-style processes. It is most useful during period-end close in systems where the classic valuation program is still part of the configured accounting procedure. Start with the exact organizational keys and business date, then prove the result from SAP documents, balances or logs before changing configuration or reposting data.
This page explains F.05 — Foreign Currency Valuation - Classic — from a consultant's point of view: what it changes or displays, when it belongs in the process, which keys matter, how to prove the result, and the mistakes that create avoidable reconciliation work.
Published 19 Sept 2026· 641 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
run classic foreign-currency valuation for open items and foreign-currency balances in ECC-style processes. The transaction should be read in the context of the full accounting or logistics flow: source document, organizational assignment, posting date, configuration and resulting document all matter. A technically successful save is not enough; the output must reconcile to the intended business event.
When it is used
F.05 is typically used during period-end close in systems where the classic valuation program is still part of the configured accounting procedure. In project testing it is equally useful for proving configuration and master data with a controlled example. In production, narrow the scope first and capture the before-state so any posting, clearing, settlement or master-data change can be reconciled afterward.
How to use it in practice
- Confirm which valuation program your system and ledger design actually uses.
- Validate valuation date, method and exchange rates before execution.
- Run in test mode and review exceptions and posting proposal.
- Post only after Finance confirms the valuation scope.
- Reconcile valuation postings and planned reversals.
Key data objects
These are the fields and business objects that usually explain the result in F.05. Capture them in test evidence and incident handovers, because a mismatch in company code, plant, fiscal period, account or reference document is often more important than the screen message itself.
- valuation date — verify the exact value, validity/date context and source of derivation.
- valuation method — verify the exact value, validity/date context and source of derivation.
- exchange rate — verify the exact value, validity/date context and source of derivation.
- accounts/items selected — verify the exact value, validity/date context and source of derivation.
- valuation and reversal postings — verify the exact value, validity/date context and source of derivation.
How to prove it in the data
Prove the result end to end: identify the source document/master record, inspect the transaction's proposal or status, then open the resulting accounting or logistics document and reconcile amounts, quantities and account assignments. Use document flow, line-item displays and master-data history with the same fiscal period and organizational scope. That distinguishes a true configuration defect from a selection, timing or historical-data difference.
ECC vs S/4HANA
F.05 is primarily associated with classic valuation. S/4HANA projects often use newer foreign-currency valuation functionality, so verify the active ledger and closing design before relying on this transaction. On S/4HANA, Universal Journal, Business Partner, Material Ledger or Fiori may change the preferred analysis surface, but the business control behind the transaction still has to be understood and tested.
Common pitfalls and how to diagnose them
- Using F.05 in an S/4HANA design that has moved to newer valuation programs without understanding ledger impact. Reconcile the exact document and period before making a configuration change.
- Valuating with the wrong rate type or key date. Reconcile the exact document and period before making a configuration change.
- Posting valuation before resolving obviously incorrect open-item currency data. Reconcile the exact document and period before making a configuration change.
Whose problem this is
Primary ownership is Finance/Controlling, with Basis or ABAP involved only when runtime, authorization or custom-code evidence points there. A useful escalation includes the business document, organizational keys, posting/valuation date, expected accounting result and the exact mismatch already proven.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/f-05ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.