---
title: "How RIKAISO MDM Works"
description: "From SAP records to a template, an upload, a Task of staged records, checks and corrections, processing and the result in SAP, with the history alongside."
source: "https://help.rikaiso.com/public-cloud/2026.2/how-mdm-works"
edition: "public-cloud"
editionLabel: "S/4HANA Public Cloud"
version: "2026.2"
latest: true
language: "en"
section: "Get Started"
updated: "2026-11-05"
---

# How RIKAISO MDM Works

> From SAP records to a template, an upload, a Task of staged records, checks and corrections, processing and the result in SAP, with the history alongside.

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

**Page type:** Concept · **Audience:** Everyone

**Contains**

- Diagram: SAP records → template → upload → **Task** (staged records) → check and correct → process → SAP; Application Logs alongside.
- One paragraph each: the Task as the unit of work; staged records are copies and SAP changes only when you process; what processing sends per row action; results per record.
- Who acts in SAP: your own user or an integration user (link `concept-identity`).
- Where data lives: staged rows in your tenant, master data stays in SAP, retention (link `data-retention`).

**Related information:** `task-lifecycle`, `concept-tasks-and-staging`, `concept-identity`.

**Source in the product repository:** `CLAUDE.md`, `docs/mass-processing-architecture.md` (diagram source).