Symptom
- Error message SG 105: "Enter rate & / & rate type & for & in the system settings" (Message Class: SG, Message Number: 105) appears when uploading AR/AP open items using the Migration Cockpit.
- The error occurs despite maintaining amounts in both Transaction Currency and Company Code Currency along with respective currencies in the template.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Open the "Migrate Your Data" app in SAP S/4HANA Cloud Public Edition.
- Upload AR/AP open items
- Attempt to simulate or execute the migration.
- Observe the error message: "Enter rate & / & rate type & for & in the system settings"
Cause
Two approaches for currency and amount:
- Provide all relevant currencies and related amounts via the template. The amounts you provide will be adopted as-is and will not be recalculated. However, the system still performs an exchange rate master data validation as a pre-check before processing the uploaded amounts. If no exchange rate is maintained for the currency pair, rate type, and posting date, the system raises error SG 105 — even if the amounts are already provided in the file. Once the rate exists and validation passes, the uploaded amounts take priority over any system-calculated values.
- Leave the second local/group currency amount fields empty. The system will calculate the amounts automatically using the exchange rate maintained in the "Currency Exchange Rates" app for the posting date.
Important: The system does not derive or reverse-calculate a missing exchange rate from the amounts provided in the template. The rate master data must exist independently for the validation to pass.
The posting date used for rate determination is typically the migration key date, which is configured in the "Define Settings for Legacy Data Transfer" app.
Resolution
Option A — Use the migration key date as posting date (recommended for initial loads):
Instead of keeping the original historical posting dates, use the migration key date (configured in "Define Settings for Legacy Data Transfer") as the posting date for migrated open items. This means you only need to maintain exchange rates for that single date per currency pair and rate type M. Original business dates (document date, baseline date, etc.) can still be provided in their respective template fields.
Option B — Keep original posting dates and maintain historical rates:
If business requirements demand the original posting dates, maintain the required exchange rates in the "Currency Exchange Rates" app for each unique combination of currency pair, rate type M, and posting date in your migration file. Rates can be mass-uploaded via CSV import. To minimize effort:
- Extract the unique (currency pair + posting date) combinations from your migration template.
- Prepare a rate upload file covering only those combinations.
- Upload the rates, then re-run the migration simulation.
See KBA 3571602 for step-by-step guidance on maintaining rates for message SG 105.
Note: Message SG 105 is a standard system error in SAP S/4HANA Cloud Public Edition. Its severity cannot be changed to a warning via customer configuration. Message control mechanisms available in on-premise environments are not applicable in Public Cloud.
See Also
- KBA 3663625 — Error message SG105 during AR/AP open items migration
- KBA 3571602 - Simulate error: Enter rate Curr1/Curr2 and rate type M for DD/MM/YYYY in the system settings (Message no. SG 105).
- KBA 3735206 - Error message SG105: "Enter rate Curr1/Curr2 and rate type M for DD/MM/YYYY in system settings"
- Fiori App "Currency Exchange Rates" (F3616)
- Fiori App "Define Settings for Legacy Data Transfer" (FINS_MIG_CTRL_1)
- Fiori App "Migrate Your Data - Migration Cockpit" (DMC_WDA)
Keywords
SG105 error, AR/AP balances upload, migration cockpit, exchange rates, LTMC template, SAP S/4HANA Cloud Public Edition, currency exchange rates, finance initial upload, error message, data migration. , KBA , CA-GTF-MIG , SAP S/4HANA Data Migration Cockpit Content , FI-FIO-GL-CA-2CL , Cross Application Configuration in General Ledger (Publ Cld) , Problem
SAP Knowledge Base Article - Public