2022-01-04 2898534

2898534 - Credit exposure after S/4HANA migration is

not matching ECC exposure when involving currency
conversion
Version 1 Type SAP Knowledge Base Article
Language English Master Language English
Release Status Released to Customer Category Problem
Component SD-BF-CM (Credit Management) Released On 02.03.2020

Please find the original document at https://launchpad.support.sap.com/#/notes/2898534

Symptom

You are migrating credit exposure from ECC to S/4HANA.

Credit values of open orders, deliveries and invoices are moved from the S066 and S067 infostructures to the
respective credit exposure liability category.
You compare the SD credit values in ECC (e.g. trx FD33 -> Extras -> Sales Value) and the liability categories
(100, 400, 500) in transaction UKM_COMMITMENTS (or trx UKM_BP credit segment details).
There is a difference in the values, which can be the result of currency translation between the sales
documents' currency and the credit control area/credit segment currency.

Environment

• Sales And Distribution (SD)

• Logistics Execution (LE)
• SAP S/4HANA

Reproducing the Issue

On an ECC system you created a sales order on 01.01.2019 with document currency EUR. The order value
was updated to the S066 infostructure with the credit control area currency USD. Exchange rate from EUR to
USD on this day was 1.1516. The sales order with a value of 1000 EUR got updated to S066-OEIKW as
1151.6 USD.

You have migrated your system to S/4HANA and the credit values were updated to the UKM_ITEM table in
the relevant liability category on 01.01.2020. You display the sales order value in the credit segment currency
and it is 1121.2 USD. The average currency conversion rate from EUR to USD on this day is 1.1212. The
credit value of the order is correct considering the current exchange rate.

Cause

The FSCM Credit Management was designed to be run 'disconnected' from the SD or FI system(s), meaning
you could connect one or more SD or FI system to a single FSCM system. In order to have efficient
communication the interfaces to the FSCM are 'restricted', where as the data passed is as small as possible.

Therefore the FSCM does only store the document currency (in the above example the EUR values) in it's
respective credit exposure table UKM_ITEM.

When your Credit Segment currency is then different, the UKM_BP or commitment display function will take

© 2022 SAP SE or an SAP affiliate company. All rights reserved 1 of 2

2022-01-04 2898534

the documents in different 'document' currencies and calculate this value into the Credit Segment currency.
This also means that the conversion is not relying on one particular date, but it is done according to the
current system date.

Resolution

This is the correct system behaviour in case the document currency is not matching the credit segment
currency.

You need to check the up-to-date exchange rates to verify the consistency of the credit exposure values pre-
and post-migration.

Keywords

credit exposure, migration, liability, commitment, exchange rate, obligo, Währungsschlüssel,

Währungsumrechnungskurse

Products

SAP S/4HANA all versions

Other Components

Component Description

FIN-FSCM-CR Credit Management

BC-SRV-BSF-CUR Currency translation / Expiring currencies

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2022 SAP SE or an SAP affiliate company. All rights reserved 2 of 2