SAP Knowledge Base Article - Public

3839082 - Transaction currency from migration template is not retained in migrated Business Solution Order (SAP S/4HANA Cloud Public Edition)

Symptom

When a Business Solution Order is created using the migration object, the transaction currency entered in the migration template is not retained. The generated Solution Order instead uses the currency maintained in the Sold-to party’s sales-area data.

For example:

  • Transaction currency entered in the migration template: (Currency A)

  • Currency configured for the Sold-to party’s sales area: (Currency B)

  • Currency in the generated Solution Order: (Currency B)

The currency provided in the migration template may still be displayed correctly in the staging record, and the simulation and migration may complete successfully. This behaviour does not occur when the Solution Order is created manually and a different transaction currency is entered explicitly.

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

  1. Prepare a Business Solution Order migration where the Sold-to party’s sales-area currency (for example, currency A) differs from the header TransactionCurrency supplied in the migration load (for example, currency B).
  2. Transfer the data to the staging tables and verify that the staged header TransactionCurrency is currency B.
  3. Complete value mapping, simulate successfully, and run the migration to create the Solution Order.
  4. Open the created Solution Order and check the header currency.
  5. Observe that the saved document shows currency A (from the Sold-to sales area) instead of currency B from the migration load.

Cause

This behaviour is caused by a defect in the Business Solution Order Migration API. During creation of the Solution Order, the transaction currency supplied through the migration template is ignored or overwritten. The system instead derives the transaction currency from the Sold-to party’s sales-area data.

Resolution

A permanent correction has been implemented by SAP Development and is planned for delivery through the applicable Hotfix Collection 2608.4 (12/12/2026). 

Until the correction is available in the customer system, use one of the following workarounds.

Workaround 1

Maintain the required currency in the Sold-to party’s applicable sales-area data before migrating the Solution Order. Assess the effect of this master-data change on other business processes before applying it.

Workaround 2

  1. Leave the transaction currency field empty when migrating the Solution Order.

  2. Complete the migration using the currency derived from the Sold-to party.

  3. After the Solution Order has been created, update its TransactionCurrency field by using a batch request with the V4 Solution Order API.

Use the SAP-provided batch payload example and ensure the API user has the required authorizations.

See Also

Keywords

Business Solution Order, Solution Order migration, migration object, Migration Cockpit, Migration API, transaction currency, TransactionCurrency, currency overwritten, currency ignored, Sold-to party, Sold-to customer, sales area currency, default currency, staging tables, V4 API, batch request, API workaround, S/4HANA Cloud, Public Edition , KBA , CRM-S4-SOL-SLO , S4CRM: Solution Order , Problem

Product

SAP S/4HANA Cloud Public Edition 2508