Open to Data Analyst & SAP MDG roles · Bengaluru · on-site, hybrid or remote

Master data that breaks heals itself.

Visveswaran Lakshmanan — Data Analyst & SAP MDG Consultant12 years in SAP master data · Senior Associate at Tenthpin · Life sciences

I designed an autonomous, self-healing data-quality engine for the SAP material master. It learns its own rules from clean data, repairs what it can prove, sends the rest to a data steward, and records every change in a GxP-ready audit trail. In the working prototype it caught all 220 planted issues and cut MRP problem messages from 183 to 0.

healing engine · pass 1Rule violationMissingDuplicateHealed
Cells scanned0
Issues found0
Auto-healed0
To steward0
12 yrsSAP & master data, 5 companies
220/220planted data issues detected by my engine
183 → 0MRP problem messages after healing
9.93%forecast error (WAPE) — best of 7 models
17data projects on real public data

Featured project · Enterprise ERP data quality

Self-Healing Data Quality for the Autonomous Enterprise

My concept for an ERP that keeps its own master data clean, taken from an SAP-based design to a working web application. It uses the real SAP material-master structures — MARA, MAKT, MARC, MARM — so it shows the same approach with or without SAP, and it verifies every fix the way the business feels it: through an MRP planning run.

Scope
SAP material master
Dataset
508 materials · 4 plants
Rules
~125 (110 self-learned)
Prototype
12 working apps

The problem

Blank MRP types, 1,000× weight errors, wrong unit conversions and duplicate materials quietly break planning, purchasing and shipping. Cleaning them by hand never ends — the same mistakes come back.

My approach

Let the data teach the system. Rules are mined from the materials that are already right, every fix carries a confidence score and a written reason, and people only see what the engine cannot prove.

What I delivered

  • Web-application deck (V_4, 14 slides) mapping every SAP component to its web equivalent
  • 508-material dataset with 220 planted issues and an answer key
  • A working SAP Fiori-style prototype with 12 apps, ~125 rules and an MRP run
01 · Profile & detect

Find every defect before touching a value

Missing values, rule violations, outliers and unit errors, format problems, duplicate materials and redundant unit rows — across general, plant/MRP, unit and description data. Weight outliers use a robust z-score on a log scale per material group, so naturally wide groups raise no false alarms.

02 · Mine rules from golden records

The system writes its own rules — and says why

Rules are learned only from materials that pass every check (≈350 of 508 at the start). Support ≥ 15 and confidence ≥ 90%; rules at ≥ 95% with support ≥ 30 activate automatically, the rest wait for a Rule Owner. It even learns exceptions:

IF MTART = FERT AND WERKS ≠ 1010 THEN DISMM = M0 · 97.4%
IF MTART = FERT AND WERKS = 1010 THEN DISMM = PD · 96.3%
03 · Predict & correct

A fixed order of evidence for every gap

  1. The most specific active rule for the material's context (plant before general)
  2. The same material in another plant that follows the rule
  3. The most similar materials in the same type and group, by majority vote
  4. No reliable evidence → quarantine; a person decides. New groups with < 5 golden materials are never guessed.

Unit errors are healed by testing ÷1000, ÷100, ÷10 until the value lands in the group's normal range.

04 · Route by confidence & policy

Automation where it is safe, people where it matters

≥ 90%auto-fix, logged with reason
50–89%steward inbox, e-signature
< 50%quarantine, user provides value

Governance policies on top: an existing value is never overwritten automatically, protected fields (MATKL, MTART, MEINS) and all merges always need a steward. Steward decisions feed the next mining run.

05 · Verify & audit

Prove it with MRP, record it for GxP

A built-in SAP MD01-style MRP run with 10 problem-message types shows the business impact before and after healing. Every change, decision and rule activation goes into an append-only, SHA-256 hash-chained audit trail with electronic signatures.

Tested against an answer key the engine never sees

Planted issues by type · detected · resolved correctly

DetectedResolved correctly12 left open on purpose — rejected or held by the steward in the test

MRP run: the business result

Plant records with problem messages caused by bad master data

183before healing
(MRP-0001)
0after healing &
steward review
91 → 0uncovered requirements
1,051order proposals
130auto-fixes in run 1, all re-verified
94.8 → 97.5DQ score, first run

Built for regulated life sciences

An audit trail you can prove was not changed

  • Hash-chained, append-only log — each record holds the previous record's SHA-256 hash; "verify integrity" recomputes every link.
  • Electronic signatures with printed name, date/time and meaning, designed around 21 CFR Part 11 §11.50 / §11.200.
  • ALCOA+ by design — attributable user and role, old and new value, mandatory reason, evidence, confidence, rule and run on every change.
  • Role-based control — Data Steward, Rule Owner, DQ Admin and read-only QA Reviewer.
real SHA-256, computed in your browser

Chain intact · 5 of 5 records verified

From SAP landscape to a web application

CapabilitySAP (concept deck)My web application
Validation rulesMDG DQM, BRFplusRule engine: configured + mined
Rule generationMDG Rule MiningAssociation-rule mining on golden records
Predict missingSAP-RPT-1.5, Gen AI HubRule → other plant → similar materials
AnomaliesSAP AI CoreRobust z-score (log scale) per group
DuplicatesMDG ConsolidationFuzzy match + attribute checks
ApprovalBuild Process AutomationSteward inbox with e-signature
AuditSAP Audit LogHash-chained audit trail
VerificationNightly MRP runBuilt-in MRP run, 10 messages

Why no LLM in the healing loop

Learning that a finished good uses MRP type M0 is counting. Filling a blank from peers is lookup and voting. Unit errors and duplicates are statistics and fuzzy matching. Keeping it deterministic makes every decision explainable, auditable, repeatable, free to run and offline — what a validated GxP system needs. An LLM stays an optional add-on to explain corrections in plain language.

Production plan: React (Fiori-style) · Python FastAPI · PostgreSQL · pandas · scikit-learn · mlxtend · RapidFuzz; SAP connection via OData/RFC.

SAP MM / MDGRule miningFuzzy matchingMRPGxP21 CFR Part 11JavaScriptSheetJS

Run the prototype yourself — no install, no SAP

Load the uncleaned data, run MRP, mine rules, run self-healing, approve suggestions with an e-signature, merge duplicates, run MRP again — and break the audit trail on purpose to watch it get caught. The Home screen walks you through 9 steps (≈ 20 min).

Demo signature password: demo · synthetic dataset of 508 materials · everything runs in your browser

Open the live prototype ↗

Featured project · Machine learning

Retail demand forecasting that beats every benchmark

Empty shelves and wasted stock both start with a bad forecast. On real Walmart sales (the M5 competition data) I forecast daily sales 28 days ahead for 70 store-department series, combining two very different models — LightGBM and a Temporal Fusion Transformer — in a fixed 50/50 hybrid.

How it works

  • Data: 10 stores in CA, TX and WI · 3,049 products · 1,913 days (2011–2016), aggregated to 70 store × department series
  • LightGBM: 29 features — calendar, events, SNAP days, price index, lags 28–364 days, rolling means (no data leakage: lags start at the horizon)
  • Temporal Fusion Transformer: attention-based deep learning with quantile forecasts (10/50/90%), 3 seeds averaged · Darts on PyTorch
  • Testing: 3 rolling 28-day origins, 5,880 forecasts per model, Diebold–Mariano significance tests
PythonLightGBMTFTPyTorch / DartsTime seriesEnsembles

Forecast error by model · WAPE (lower is better)

−30.5%RMSE vs Holt-Winters
−0.9%bias (errors cancel out)
p = 0.017vs LightGBM alone

Visveswaran Data Lab

17 more projects on real public data

Life-sciences studies, data cleansing and de-duplication, business decisions and visual analytics. Every project ships with an interactive study, a written project document, a data sheet and the raw data — most with Python source code.

Experience

12 years of SAP master data

From SAP consultant in manufacturing and retail, to master data governance in a regulated pharmaceutical company, to data analysis and SAP master data for life-science clients.

Skills

What I bring to a data team

SAP master data & MDG

SAP MDGMaterial master (MARA · MARC · MARM · MAKT)Data governanceGolden recordMRPS/4HANA migration

Data quality engineering

Self-healing DQRule miningAnomaly detectionFuzzy matching & de-duplicationRecord linkageDQ scorecards

Analytics & machine learning

PythonSQLpandas · scikit-learnLightGBM · TFTSurvival analysisA/B testingForecasting

Visualisation & apps

DashboardsD3.jsthree.jsJavaScriptWeb prototypes

Regulated data

GxPALCOA+21 CFR Part 11Audit trailsClinical & trial data

SAP data platform & delivery

SAP DatasphereSAP Business Data CloudScrum (CSM)Remote global teams

Licenses & certifications

2010 — 2014

B.Tech, Information Technology

Pandian Saraswathi Yadav Engineering College · Grade 7.8

Languages

Tamil · English · Malayalam

Native · full professional · limited working

Let's talk

Need master data that stays clean?

I'm open to Data Analyst, SAP MDG and data-quality roles — in Bengaluru, hybrid or fully remote. LinkedIn is the fastest way to reach me.

Message me on LinkedIn
Name
Visveswaran Lakshmanan
Role
Data Analyst · SAP MDG Consultant
Based in
Bengaluru, Karnataka, India
LinkedIn
linkedin.com/in/visveswaranlakshmanan
Live demo
visveswaran.in/new5/self-healing-dq
Data Lab
visveswaran.in/data