Skip to Content

Adding Group currency and local currency to FIBCRC001A./T


I have ICR implemented and have for 1 year plus and our users are successfully using the functionality but have received requests repeatedly to add group and local currency to the data. I can see that I can add view transaction currency in report FBIC017 and would like to see all three currencies here.

I Have read the documentation attached to the note 1164059 and also the various threads here in the SDN:




and found that i could add the HSL field to the line item table but when i do, i cannot define it as HSL because only the fields in BKPF and BSEG are available to select. So, i had dmbe2 from bseg and hwae2 from bkpf and it populates well in FBICRC001A although the amounts do not have correct signs (transaction currency is negative but group is positive) and the totals table FBICRC001T has only the two additional fields as opposed to the rolling periods normally found in these special ledges.

All of this I was able to complete by simply adding these two fields to the additional fields in reconciliation and ensuring the reference field was correctly populated (this was only possible by updating the CI includes after activation as the true reference field - BKPF-HWAE2 - is not an option to choose and no other entries are valid but those offered - FIBCRC001A- currencies.

If anyone can help with this question, would be very grateful.

How can I add HSL and KSL to the line items and HSL01 - HSL16 and HSLVT and the KSL respective fields to the total table? Perhaps there is some big piece i am missing?


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Jul 19, 2011 at 12:10 PM

    Hello Jerrie Lee,

    ICR is designed to support reconciliation in transaction currency only. With other currencies you will run into differences per definition.

    If you add other currency fields in the line item table you have to implement a BADI to make sure the sign of the amounts is correct (either set the sign according to the transaction currency value or add SHKZG as well and then handle the amount accordingly). If you add a value field you also have to add a currency field. Typically the data is extracted from other systems. Therefore there is no information available in the reconciliation system what the local or the group currency are in the sender system.

    Example: Create new field ZZLCURR as a currency field and populate it in a BADI implementation. Then you can add field HSL and refer to ZZLCURR as the currency field for this new value field.

    If you add currencies to the totals table, FBICR* will still only take fields TSL* into account. If you only want to have the additional currencies as supplementary information (e.g. reporting on ICR data) you could add the corresponding fields (e.g. HSLVT - HSL16) to the table in SE11. The automatic calculation of these fields will only work if you add the line item fields as HSL and KSL. In that case you would have to copy BSEG-DMBTR to HSL (e.g. BADI method ADD_INFORMATION_TO_DATA_RECORD in the sender system).

    What exactly is the business requirement for adding the fields? Why are the fields necessary on the totals level?

    Best regards,


    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.