---
title: "The Application Destination (RIKAISO_MDM_DESTINATION)"
description: "The destination used for reads and processing; its authentication type decides whose SAP user the changes run under."
source: "https://help.rikaiso.com/public-cloud/2026.2/application-destination"
edition: "public-cloud"
editionLabel: "S/4HANA Public Cloud"
version: "2026.2"
latest: true
language: "en"
section: "Information for Administrators > Completing the Destinations in SAP BTP"
updated: "2026-11-05"
---

# The Application Destination (RIKAISO_MDM_DESTINATION)

> The destination used for reads and processing; its authentication type decides whose SAP user the changes run under.

> **Draft brief for authors.** Replace with the final text; keep the task-page structure.

**Page type:** Task · **Audience:** SAP BTP administrator

**Contains**

- Properties table: Type HTTP; URL = the API host without a service path (what MDM tolerates); Proxy Type Internet (On-Premise for the Private Edition); Authentication BasicAuthentication or OAuth2ClientCredentials (integration user), OAuth2SAMLBearerAssertion (user propagation), PrincipalPropagation (on premise).
- The user-propagation procedure: OAuth 2.0 in the arrangement, trust of the subaccount's certificate in the communication system, the destination's token service settings, nameIdFormat and userIdSource, System User empty.
- Optional properties: `rikaiso.backgroundIdentity = technical-user`; `rikaiso.fiori.*` (link `fiori-links-setup`).
- MDM reads destinations from your subaccount only and never overwrites one; a deleted destination is reported as not found.

**Related information:** `technical-destination`, `identity-mode`, `checking-the-connection`.

**Source in the product repository:** customer guide §3.