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.
Open to Data Analyst & SAP MDG roles · Bengaluru · on-site, hybrid or remote
Visveswaran Lakshmanan — Data Analyst & SAP MDG Consultant12 years in SAP master data · Senior Associate at Tenthpin · Life sciences
Bengaluru, India · linkedin.com/in/visveswaranlakshmanan · visveswaran.in/new5 · Live prototype: visveswaran.in/new5/self-healing-dq · Data Lab: visveswaran.in/data
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.
Featured project · Enterprise ERP data quality
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.
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.
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.
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.
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:
Unit errors are healed by testing ÷1000, ÷100, ÷10 until the value lands in the group's normal range.
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.
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.
Planted issues by type · detected · resolved correctly
Plant records with problem messages caused by bad master data
Built for regulated life sciences
Chain intact · 5 of 5 records verified
| Capability | SAP (concept deck) | My web application |
|---|---|---|
| Validation rules | MDG DQM, BRFplus | Rule engine: configured + mined |
| Rule generation | MDG Rule Mining | Association-rule mining on golden records |
| Predict missing | SAP-RPT-1.5, Gen AI Hub | Rule → other plant → similar materials |
| Anomalies | SAP AI Core | Robust z-score (log scale) per group |
| Duplicates | MDG Consolidation | Fuzzy match + attribute checks |
| Approval | Build Process Automation | Steward inbox with e-signature |
| Audit | SAP Audit Log | Hash-chained audit trail |
| Verification | Nightly MRP run | Built-in MRP run, 10 messages |
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.
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
Featured project · Machine learning
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.
Visveswaran Data Lab
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
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
Licenses & certifications
2010 — 2014
Pandian Saraswathi Yadav Engineering College · Grade 7.8
Languages
Native · full professional · limited working
Let's talk
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.