Skip to Content
Author's profile photo Former Member

F5557 – “Local currencies for company code && cannot be completely determined” OR FINS_ACDOC_POST002 – “Line items do not balance in Controlling area currency”

Hello all,

I want to share with you a new scenario that you could face during the SFIN migration.

You are executing SFIN Migration:



And you are receiving error message F5557 – “Local currencies for company code && cannot be completely determined


If you ignore this message you will receive message FINS_ACDOC_POST002:


The cause for this error is that the currency type of controlling area ’20’ is assigned to the company code as parallel currency in FI (Tcode OB22) and CO (TCode OKKP).

For this scenario we can have 3 resolution scenarios:

Solution 1) Use currency type 30 for the controlling area. Currency Type 30 is supported by both FI and CO, and you get integrated amounts for both application in your universal journal. (recommended setting).

Solution 2) Use another currency type  – currency type  40 – , which is supported by both applications FI and CO, if the currency key of currency type 30 does not fit to all controlling areas.

Solution 3) Use currency type 20 in the controlling area. But this is then an “CO-only” amounts in the universal journal, which we allow for compatibility reasons. This is not the recommended setting. In all line items, with G/L Accounts, which are is not a cost elements,   the amount in currency type  20 will be 0.

Solution 1) or Solution 2) is the better choice and recommended by SAP. But if you want keep with Solution 3 you should apply the corrections of note 2187380. With this note you can use currency type 20. But the amount will be filled in cost elements only.

For Solution 3 follow the steps:

1)     Apply the corrections of note 2187380.This note will avoid inconsistences in the future.

2)     Check in SE16 the of table T001A. In T001A you should not find any entry which has currency type ’20’ assigned. All values should be empty (no parallel currency used).

3)     Check it with SE16  table FINSC_LD_CMP, if the record for Ledger 0L and Company Code contains space in field CURPOSK. (Currently there is ‘2’ in this field.)

I hope this content can help you when you are planing your migration. It is important check you CO/FI customizing before the migration.

Kind Regards,


Assigned Tags

      Be the first to leave a comment
      You must be Logged on to comment or reply to a post.