---
title: "The Technical Destination (RIKAISO_MDM_TECH_DESTINATION)"
description: "The destination for work without a signed-in user: the custom-field synchronization and background runs of integration-user tables; it must be technical and name the same SAP system."
source: "https://help.rikaiso.com/public-cloud/2026.2/technical-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 Technical Destination (RIKAISO_MDM_TECH_DESTINATION)

> The destination for work without a signed-in user: the custom-field synchronization and background runs of integration-user tables; it must be technical and name the same SAP system.

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

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

**Contains**

- What it is used for; it must use a technical authentication type (a user-dependent type is refused before a run instead of failing halfway).
- Both destinations must point to the same SAP system; MDM compares them at every app start and before every background run; a mismatch warns in the apps and refuses background runs; switch both together when moving to another system.
- The communication user needs the arrangement of every object family you process; MDM checks it with the first call a background run would make.

**Related information:** `application-destination`, `checking-the-connection`, `messages-connection`.

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