Skip to main content

~ Currency Types in ECC vs. S/4

Currency Types in ECC and S/4HANA FI:

ECC: There are indeed only 3 Currency Types in ECC:

  • Company Code Currency: The primary currency used for financial transactions in the company code.
  • Group Currency: The currency used for consolidation purposes at the group level.
  • Hard Currency (or Additional Currency)

S/4HANA FI: There are 10 Currency fields available in the ACDOCA:

  • Company Code Currency
  • Group Currency
  • Document Currency
  • Global Currency
  • Free-Defined Currency 1
  • .  .  .
  • Free-Defined Currency 6

Differences Between OB22 and FINSC_LEDGER:

OB22:

  • Primarily used for setting currencies at the company code level.
  • Allows you to define and manage local currencies for a specific company code.
  • The screen for "Change view additional local currencies for a company code: details" is specifically for ECC, as it only lists three local currencies.

FINSC_LEDGER:

  • A more comprehensive transaction for managing currencies and other financial ledger settings.
  • Offers a wider range of options and functionalities compared to OB22.
  • Can be used to manage currency types, exchange rates, valuation methods, and other financial ledger parameters.
  • Suitable for both ECC and S/4HANA FI environments.

Additional Considerations:

  • While OB22 is primarily focused on company code-level currency settings, FINSC_LEDGER provides a more holistic approach to currency management.
  • The choice between OB22 and FINSC_LEDGER depends on your specific requirements and the complexity of your financial processes.
  • In S/4HANA FI, FINSC_LEDGER is generally recommended for managing currencies and other financial ledger settings.

In summary, while OB22 is a useful tool for managing local currencies in ECC, FINSC_LEDGER offers a broader range of functionalities and is suitable for both ECC and S/4HANA FI environments. Understanding the differences between these transactions can help you effectively manage currency settings and financial processes in your SAP system.

Yes, you can still use OB22 to look at currency data in S/4HANA FI. Even though FINSC_LEDGER offers a more comprehensive approach, OB22 remains a valid option for viewing currency information at the company code level.

While FINSC_LEDGER provides a broader range of functionalities and is often preferred for managing currencies and other financial ledger settings, OB22 can still be a useful tool for specific tasks related to company code currencies.

Comments

Post a Comment

Popular posts from this blog

Primary & Secondary

A key aspect of how CO and FI are integrated within the SAP S/4HANA system: 1. Primary Cost Elements: • Example:  ○ FI: Salaries expense in the P&L statement. ○ CO: Salaries expense used in cost center accounting to track labor costs. 2. Secondary Cost Elements: • Example:  ○ Depreciation: While depreciation is tracked in FI, a secondary cost element might be created to allocate depreciation costs to specific cost centers or internal orders based on factors like asset usage.   In SAP S/4HANA, the distinction between cost elements and costs, whether primary or secondary, is fundamental to how Financial Accounting (FI) and Controlling (CO) interact and provide granular insights into an organization's financial performance. Here's a breakdown of the differences: 1. Primary Cost Elements What they are: Primary cost elements are essentially General Ledger (G/L) accounts from Financial Accounting (FI) that are relevant for cost accounting in Controlling (CO) ....
Post a Comment
Read more

Clients per Gem

> In SAP S/4HANA discussions, I find two discussions of client. One uses terms like dev or prod. Another uses numbers like 100. What is the difference? You're right, the term "client" in SAP S/4HANA can be confusing because it's used in two distinct contexts: 1. Logical Clients (Numbers like 100, 200, etc.): Definition: These are numerical clients within an SAP system. They represent separate, independent business entities or organizational units within the same physical SAP system.   Purpose: Data Separation: Each client has its own master data, transactional data, and customizing settings. This means data in client 100 is completely separate from data in client 200. Organizational Isolation: It allows different departments, subsidiaries, or even entirely separate companies to use the same SAP system without interfering with each other's data. Testing and Development: Clients are often used for different purposes, such as: Development (DEV): Clie...
Post a Comment
Read more