SAP Knowledge Base Article - Public

3803493 - Sales Order Message Remains "In Process" Due to "Error while determ. loc. crcy: exchange rate type M" – SAP S/4HANA Cloud Public Edition

Symptom

When creating a sales order through the inbound SalesOrderBulkRequest_In service in SAP S/4HANA Cloud Public Edition, the message remains in "In Process" status in the Message Monitoring app.

The sales order is not created successfully.

When the corresponding message is checked in SRT_MONI, it has a processing status such as System_Error / Execution_Error and displays an error similar to:

Error while determ. loc. crcy: exchange rate type M date XX/XX/XXXX from XXX to XXX

For example:

Error while determ. loc. crcy: exchange rate type M date 07/16/2026 from PHP to SGD

Subsequent messages belonging to the same processing sequence may remain in Wait_for_Scheduler stat

Environment

SAP S/4HANA Cloud Public Edition

Reproducing the Issue

  1. Create a sales order in an external source system and send it to SAP S/4HANA Cloud.
  2. Open Message Monitoring and select interface /SDSLS – SO_BULK_I.
  3. Filter by status “In Process” and locate the affected inbound message.
  4. Observe that the message remains in “In Process” and no sales order is created.

Cause

A required currency exchange rate cannot be determined for the date used during sales order processing.

The required currency pair and exchange rate type M is either:

  • Not maintained.
  • Not valid for the required date.
  • Missing the necessary currency conversion/translation configuration.

As a result, processing of SalesOrderBulkRequest_In terminates with a currency determination error.

Because the SOAP message is processed sequentially, subsequent messages in the same sequence can remain waiting until the failed message is successfully processed.

Resolution

  1. In Message Monitoring, identify the affected /SDSLS - SO_BULK_I message and note the Message ID and processing timestamp.
  2. Locate the corresponding SalesOrderBulkRequest_In message in message monitoring and review Error Information.
  3. Identify the exchange-rate type, currency pair, and date reported in the error. For example:
    • Exchange Rate Type: M
    • From Currency: PHP
    • To Currency: SGD
    • Required Date: 16.07.2026
  4. In the Currency Exchange Rates app, verify that the required exchange rate is maintained and valid for the date specified in the error.
  5. If the required rate/configuration is missing, have the responsible Finance/Configuration user maintain the appropriate exchange rate.
  6. Once the exchange rate has been corrected, restart/reprocess the failed message.
  7. Verify that the sales order is created successfully and that any subsequent messages previously in Wait_for_Scheduler are processed.

See Also

Keywords

SalesOrderBulkRequest_In, /SDSLS, SO_BULK_I, In Process, Message Monitoring, System_Error, Execution_Error, Wait_for_Scheduler, exchange rate type M, Error while determ. loc. crcy, local currency, currency conversion, missing exchange rate, Currency Exchange Rates, PHP, SGD, SOAP, bgRFC, Sales Order, Public Cloud, SAP S/4HANA Cloud Public Edition , KBA , SD-SLS-SO-2CL , Sales Orders (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions