SAP consultant profile

Dzmitryi Kharlanau

SAP consultant at EPAM Systems, previously at abat. I work where SAP operations, transformation, and AI readiness meet: process evidence, technical diagnosis, ownership, and delivery decisions that still make sense after handover.

Dzmitryi Kharlanau
Current context
SAP Consultant · EPAM Systems · ex‑abat
Working scope
SD, MM, O2C, P2P, MDG-related work, master data, integration troubleshooting, AMS, and ABAP-backed analysis.
Last reviewed
August 14, 2026

Operating scope

Business problems that cross SAP boundaries

Senior SAP consultant with 12+ years in SAP SD, logistics, integration, MDG-related work, and AMS-heavy delivery. Experience spans SAP S/4HANA support and enhancement work, ABAP-backed troubleshooting, SAP IS-Automotive environments, and recent public writing on integration patterns, data governance, event-driven architecture, and practical AI tooling.

My work usually sits where a business process crosses SAP configuration, master data, custom logic, interfaces, and the support model. A blocked order, failed replication, or delayed invoice is rarely a useful "single-module" problem. I start by asking which decision, dependency, or control failed, then look for the evidence that separates a local workaround from a durable fix.

This is the kind of work where I can frame the functional problem and keep the same evidence chain understandable to application, ABAP, integration, data, and operations colleagues.

Operating approach

How I approach SAP problems

1. Make the failure concreteStart with a blocked business outcome, not a technology label.
2. Trace dependenciesFollow process, master data, configuration, enhancement, and interface boundaries.
3. Separate evidence from assumptionDistinguish confirmed facts, missing evidence, and landscape-specific decisions.
4. Leave a reusable artefactTurn the result into an owner decision, runbook, backlog item, or control.

I avoid fixes that only improve the appearance of control: green SLAs while the same incidents recur, dashboards without an accountable recovery path, AI pilots without a usable knowledge layer, or clean-core work that merely moves unowned complexity elsewhere. I want the result to be a bounded change with an owner, evidence, and a recovery path.

Where experience connects

Domains that meet in real delivery work

Commercial and logistics flow

SD, O2C, delivery, billing, pricing, inventory-facing logistics, and the operational controls around them.

Procurement and data

MM, P2P touchpoints, Business Partner and MDG-related work, replication, data quality, and governance boundaries.

Integration and architecture

IDoc, RFC, web services, APIs, OData, AIF, event-driven patterns, interface ownership, and recoverability.

Operations and change

AMS-heavy delivery, incident diagnosis, ABAP-backed troubleshooting, testing, handover, operational memory, and side-by-side automation.

Industry context in the public record includes Automotive, Retail and apparel, Manufacturing, and IT services and consulting.

What a manager can expect

Useful outputs, not generic advice

Diagnostic brief

A clear statement of the business symptom, scope boundary, evidence needed, likely failure classes, and open decisions.

Decision and ownership map

A practical view of who owns the business outcome, data, integration contract, technical control, and recovery action.

Prioritised improvement backlog

Actions separated into immediate control fixes, process or data work, architecture decisions, and longer-term investment.

Reusable operational memory

Runbook, KEDB, evidence checklist, or review pattern that reduces rediscovery during future support and change work.

Career path

Roles represented in the public dataset

SAP AMS Transformation Consultant

EPAM Systems · 2025-11 to present

Current title listed in the LinkedIn export. Description points to SAP AMS transformation work with AI, RAG, knowledge engineering, clean-core thinking, and process optimization.

Senior SAP Consultant | AMS · Logistics · MDG · Integration

EPAM Systems · 2025-05 to present

Current role listed in the LinkedIn export. Description highlights logistics and data-flow stability across SD, MM, and MDG, plus ABAP and Python-based support for data checks, migration tasks, and recurring-issue prevention.

SAP migration consultant

EPAM Systems · 2026-02 to present

Additional current role title listed in the LinkedIn export without a description. Kept as-is and treated as needing clarification.

SAP SD Consultant

abat · 2019-08 to 2025-04

Designed and supported SAP SD processes in sales, delivery, and billing within S/4HANA, including rollout and logistics-related enhancements.

SAP IS Automotive consultant

abat · 2019-02 to 2025-04

Long-running automotive AMS role covering JIT processes, logistics enhancements, incident resolution, and cross-functional integrations in S/4HANA environments.

ABAP Developer

abat · 2019-02 to 2025-03

ABAP development role listed in the export. Public evidence from projects and publications supports hands-on work around debugging, integration, workflow, and SAP technical extensions.

Read the full public CV

Evidence routes

How to examine the positioning

QuestionPublic evidence
What roles and domains are on record?CV and the canonical resume dataset.
How does the diagnostic approach translate into practice?Service entry points, business scenarios, and the Knowledge Atlas.
What has been published publicly?Publications and datasets.
Which credentials are linkable?Education and credentials and the public profile audit.

Selected credentials

Publicly linkable credentials

Claude Certified Architect - Foundations

Anthropic · 2026-04

Open credential

Claude Certified Architect - Foundations Early Adopter

Anthropic · 2026-04

Open credential

Agentic AI Design Patterns for GenAI and Predictive AI

LinkedIn · 2026-03

Open credential

Build with AI: Create an Agent with GPT-OSS

LinkedIn · 2026-02

Open credential

Agentic AI: A Framework for Planning and Execution

LinkedIn · 2026-02

Open credential

Public writing

Selected published work

How to Test SAP Sales Cloud OData API with Postman

LinkedIn · July 31, 2025

Open source

Explain me Event-Driven Architecture

LinkedIn · August 1, 2025

Open source

Working with the Business Object Processing Framework (BOPF)

LinkedIn · December 24, 2024

Open source

How MRP Works in SAP: Old vs. MRP Live / Depth look / Guide

LinkedIn · December 10, 2024

Open source

How to add customer-specific fields into MB52

SAP Community · February 22, 2022

Open source

How to change Field control in ME5*N?

SAP Community · February 22, 2022

Open source

How to debug A2A inbound service call from SAP TM in SAP S4

SAP Community · February 22, 2022

Open source

Visual SAP with plantUML - Knowledge base

Hashnode · May 27, 2025

Open source

DAMA-to-SAP MDG Knowledge Map

Hashnode · May 25, 2025

Open source

SAP AMS Next Gen

SAP AI Notes · February 1, 2026

Open source

DAMA - Data Governance

DAMA short book · March 1, 2026

Open source

Verification detail

Machine-readable sources and profiles

Audit registry

Confidence levels, credential registry, publication themes, and verification issues.

Profile audit JSON

LLM access manifest

Retrieval guidance for AI systems and links to canonical public surfaces.

llms.txt

The source-of-truth audit for confidence levels and credential status is available at /ai/profile-audit.json. These files support verification; the sections above are intended for a manager assessing fit.