Why Does the Logon Client Have a Currency Code?

  • by Kurt Goldsmith, Senior Business Consultant, Enowa Consulting
  • July 15, 2004
You will face confusing repercussions if you do not fill in the currency code field in the logon client. Using an Accounts Receivable example, the author demonstrates how to avoid this situation and explains the logic behind it.

Customization for currency exchange rates can be one of the more interesting adventures in R/3. So many different kinds of things are linked to their own USD, EUR, GBP, etc., currency code. This includes not only transaction documents such as journal entries or invoices, but also master data such as cost centers, orders, and G/L accounts. Perhaps the most surprising of all — each logon client has a place to type in a currency code. You can see this in Figure 1.


Figure 1
Each logon client has a place to type in a currency code

Now, notice in Figure 1 that for my example Client 100, I have not yet bothered to type in a currency code. I have done this on purpose to more easily answer this question — Why does the logon client have a currency?

Instead of trying to explain a lot of techno-gibberish, maybe this article will be easier to read if I just give one example within the FI/CO modules. Money is usually fun to talk about, and incoming money is nicer to imagine than outgoing money. So, let's focus on Accounts Receivable (A/R).

Kurt Goldsmith

Kurt Goldsmith is a senior business consultant for Enowa Consulting, specializing in the diagnosis and resolution of productivity-related integration issues between a company’s division of labor (end users, managers, executives) and SAP software (R/3, BW, APO, CRM). He also has a lifetime performance record of one win and two third-place finishes from five career starts as a thoroughbred racehorse trainer.

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.