a. FAGL_FC_VALUATION
b. SAPF100
c. FAGL_VALUATION
d. SAPF130K
Which is the correct answer?
---
2) Every currency used in SAP S/4HANA must have a
a. Exchange rate type
b. Currency key assigned
Which is the correct answer?
---
Answers:
1) a
Explanation:
If you're navigating the world of SAP S/4HANA, here's something you should know: the program FAGL_FC_VALUATION, which was a familiar face in SAP ECC for handling foreign currency valuation, is now replaced by the more advanced FAGL_FCV.
Let’s unpack that a bit.
In ECC systems that used the New General Ledger, FAGL_FC_VALUATION did the job of revaluing open items and balances in foreign currencies. But with SAP S/4HANA streamlining architecture and performance, that old tool got a significant upgrade. Enter FAGL_FCV - built with modern requirements in mind.
Here’s what’s better about FAGL_FCV:
- It supports simulation ledgers, giving you more flexibility.
- It integrates with Error Correction and Suspense Accounting (ECS) - a huge win if you’ve ever battled with batch input session errors.
- It’s more aligned with the real-time processing nature of S/4HANA.
- SAPF100: Yep, this one was used in Classic GL for currency valuation in older SAP R/3 systems - but it’s not relevant in the S/4HANA world.
- FAGL_VALUATION: Doesn’t exist. It’s often confused with the real program FAGL_FC_VALUATION, but it’s not a valid T-code or report.
- SAPF130K: That’s a totally different ballgame — used for customer balance confirmations, not currency valuation.
2) b
Explanation:
Here’s the thing, when you’re dealing with financial systems like SAP S/4HANA, precision is everything. Every currency you work with, whether it’s US Dollars, Euros, or Japanese Yen, must have a currency key assigned. This isn’t just SAP being picky; it’s fundamental to how the system identifies and handles currencies across transactions, reporting, and valuations.Think of the currency key as the official "ID card" for any currency in SAP. Without it, the system simply won’t know what you’re referencing. The key is typically a 3-letter code like USD, EUR, or JPY, and it’s stored in SAP’s TCURC table (which is essentially the master list of currency codes).
Now, you might be wondering, “What about exchange rate
types?”
Good question!
While exchange rate types (like M for average rate, B for bank buying rate) are important for certain processes - like converting one currency to another or handling foreign currency valuation, they aren’t mandatory for every currency you define in the system. They come into play when you need to calculate conversion rates, but not simply to define the currency.
So to sum it up:
✅ Currency key = always required
❌ Exchange rate type = only needed for specific scenarios
