Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
cancel
Showing results for 
Search instead for 
Did you mean: 
Ajeet
Employee
Employee
Dear Colleagues

This is in continuation of my previous currency blog SAP S/4HANA Currency Setup

Many time we get question that what should be our controlling area currency 10/ 20 or 30, in cases where Cross-company-code cost accounting is active.



Let us understand different options & their implications for this CO Area currency setting  .

Case 1: The currency type of the controlling area (e.g. 30 = Group Currency) is also configured as parallel currency in FI (table T001A / tx OB22)

  • Then KSL filled in all line items in all ledgers. The field is used as a common currency for FI and CO. It is called "Global currency for FI and CO"

  • This is the recommended setting for all new installations.


 

Case 2: The currency type of the controlling area ( e.g. 20/30) is not configured as parallel currency in FI (table T001A / tx OB22)

  • Then KSL is filled only in the leading ledger for CO relevant line items, i.e. line item assigned to a CO Object and a cost element.

  • KSL is empty for all line items without CO relevance, i.e. balance sheet accounts or nonoperating expense or income.

  • KSL is empty for non-leading ledgers. 


Note :These above mentioned limitations of KSL update for CT 20 has been removed as of SAP S/4HANA 2020 for many of the scenarios. Would try to share the details about this as soon as I get some further insight.

Case 3: The currency type of the controlling is the local currency (currency type 10)

  • KSL is filled with the same rules as in case 2.

  • This means for CO relevant items KSL contains the same amount like HSL, and for non CO relevant line items KSL is empty.


 In case 2 and 3 we say KSL is "used by CO only". This settings are not recommended for new installations, but it is supported in order to be compatible with all existing currency configration of installed systems. Unfortunately it is not possible to automatically introduce a new currency in FI during the migration to SFIN or S/4H.

Reference SAP note 2231255

Universal journal (ACDOCA) integrates posting of Financial Accounting and Controlling.


The universal journal integrates postings of Financial Accounting (FI) and Controlling (CO). To be more specific, it unifies the general Ledger view of FI with CO. As a consequence, each journal entry contains the currency type of the controlling area, regardless of whether this currency type is defined as second or third local currency in FI. Each journal entry always contains the postings from CO.

If the currency type of the controlling area is defined as second or third local currency in FI, this currency type is filled not only in the general ledger view of the FI postings (table ACDOCA, field KSL) but also in the entry view (table BSEG, fields DMBE2 etc.). The controlling area currency is thus integrated with FI.

Having the currency type of the controlling area as second or third local currency in FI is the recommended setting , however if you have currency type 20 the same can not be assigned as FI currency for BSEG.

I hope this would help and comment in case need any further clarification.

Linkedin
4 Comments
panditnm
Discoverer
Hi Ajeet

 

Thanks for this informative blog. Can we change the controlling area currency from 20 to 40 (hard currency) if both are USD by making changes to FINSC_LEDGER in a productive environment? We have material ledger active for some of the plants. However, it has been configured to have currency types 10 & 40. Will the system allow to change the controlling area currency in such case? Will it cause any inconsistency?

 

Regards

Neha
0 Kudos
Hi Neha, did you find any answer? I got same requirement
panditnm
Discoverer
0 Kudos
Hi Cristian

No, we did not get any answer to manage this set up. We have identified a custom solution to fix our issue. Generally SAP SLO team is to be involved in this situation. They can confirm on the possibility, impacts, timeline to make any changes etc.

 

Regards

Neha

 
howard111
Newcomer
0 Kudos
Hi Ajeet,

have you found any new information about your note in case 2?

 

Note :These above mentioned limitations of KSL update for CT 20 has been removed as of SAP S/4HANA 2020 for many of the scenarios. Would try to share the details about this as soon as I get some further insight.

 

Thank you very much in advance.

 

Kind regards Michael