<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>Martenweave Blog</title>
    <link>https://martenweave.github.io/blog/</link>
    <description>Practical notes on SAP migration, MDM, data governance, lineage, impact, and deterministic validation.</description>
    <language>en</language>
    <lastBuildDate>Wed, 15 Jul 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>SAP MDG Manages Master Data. Who Manages the Implementation Knowledge?</title>
      <link>https://martenweave.github.io/blog/sap-mdg-implementation-knowledge.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/sap-mdg-implementation-knowledge.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>SAP Master Data Governance can manage governed records, change requests, workflows, data quality rules and the operational lifecycle of master data.</description>
    </item>
    <item>
      <title>Why SAP Migration Mapping Spreadsheets Break Down</title>
      <link>https://martenweave.github.io/blog/sap-migration-mapping-spreadsheets.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/sap-migration-mapping-spreadsheets.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>Most SAP migration programmes begin with a mapping spreadsheet.</description>
    </item>
    <item>
      <title>What to Prepare Before Starting an SAP MDG Implementation</title>
      <link>https://martenweave.github.io/blog/what-to-prepare-before-starting-an-sap-mdg-implementation.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/what-to-prepare-before-starting-an-sap-mdg-implementation.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>An SAP MDG implementation often appears to begin with the platform.</description>
    </item>
    <item>
      <title>How SAP Data Migration and MDG Implementation Should Work Together</title>
      <link>https://martenweave.github.io/blog/how-sap-data-migration-and-mdg-implementation-should-work-together.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-sap-data-migration-and-mdg-implementation-should-work-together.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>SAP data migration and SAP Master Data Governance are often organised as separate workstreams.</description>
    </item>
    <item>
      <title>Why an SAP MDG Implementation Needs an Independent Model Specification</title>
      <link>https://martenweave.github.io/blog/why-an-sap-mdg-implementation-needs-an-independent-model-specification.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-an-sap-mdg-implementation-needs-an-independent-model-specification.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>An SAP MDG implementation contains several versions of the model.</description>
    </item>
    <item>
      <title>SAP Data Migration Readiness Checklist</title>
      <link>https://martenweave.github.io/blog/sap-data-migration-readiness-checklist.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/sap-data-migration-readiness-checklist.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>A migration team can complete mappings, build load files and pass several technical checks while the domain is still not ready for migration.</description>
    </item>
    <item>
      <title>Why Mapping Completion Is Not Migration Readiness</title>
      <link>https://martenweave.github.io/blog/why-mapping-completion-is-not-migration-readiness.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-mapping-completion-is-not-migration-readiness.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>A migration programme reports that 96% of mappings are complete.</description>
    </item>
    <item>
      <title>How to Build a Single Source of Truth for SAP Mappings</title>
      <link>https://martenweave.github.io/blog/how-to-build-a-single-source-of-truth-for-sap-mappings.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-build-a-single-source-of-truth-for-sap-mappings.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>Most SAP programmes claim to have a single source of truth for mappings.</description>
    </item>
    <item>
      <title>How to Detect Dataset Gaps Before SAP Migration Testing</title>
      <link>https://martenweave.github.io/blog/detect-dataset-gaps-before-sap-migration-testing.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/detect-dataset-gaps-before-sap-migration-testing.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>Many SAP migration programmes treat testing as the first serious encounter between the target model and the source data.</description>
    </item>
    <item>
      <title>How to Perform Impact Analysis for an SAP Field Change</title>
      <link>https://martenweave.github.io/blog/impact-analysis-sap-field-change.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/impact-analysis-sap-field-change.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>On Monday, a country team asks for one SAP field to become mandatory.</description>
    </item>
    <item>
      <title>How to Trace a Legacy Field to an SAP Target Field</title>
      <link>https://martenweave.github.io/blog/trace-legacy-field-to-sap-target.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/trace-legacy-field-to-sap-target.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A defect appears during the second mock load.</description>
    </item>
    <item>
      <title>How to Keep SAP MDG Design and Configuration Aligned</title>
      <link>https://martenweave.github.io/blog/how-to-keep-sap-mdg-design-and-configuration-aligned.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-keep-sap-mdg-design-and-configuration-aligned.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>The design document says the field is optional.</description>
    </item>
    <item>
      <title>How to Reduce Rework During an SAP MDG Implementation</title>
      <link>https://martenweave.github.io/blog/how-to-reduce-rework-during-an-sap-mdg-implementation.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-reduce-rework-during-an-sap-mdg-implementation.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>The programme has already approved the model.</description>
    </item>
    <item>
      <title>What an SAP MDG Handover Package Should Contain</title>
      <link>https://martenweave.github.io/blog/what-an-sap-mdg-handover-package-should-contain.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/what-an-sap-mdg-handover-package-should-contain.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>The SAP MDG programme goes live on Friday.</description>
    </item>
    <item>
      <title>Why Project Knowledge Disappears After Go-Live</title>
      <link>https://martenweave.github.io/blog/why-project-knowledge-disappears-after-go-live.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-project-knowledge-disappears-after-go-live.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>Six months after go-live, an SAP MDG validation starts rejecting supplier changes.</description>
    </item>
    <item>
      <title>How Martenweave Complements SAP MDG</title>
      <link>https://martenweave.github.io/blog/how-martenweave-complements-sap-mdg.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-martenweave-complements-sap-mdg.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>A company has already invested in SAP Master Data Governance.</description>
    </item>
    <item>
      <title>Martenweave vs Excel, Jira and Confluence</title>
      <link>https://martenweave.github.io/blog/martenweave-vs-excel-jira-and-confluence.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/martenweave-vs-excel-jira-and-confluence.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>The programme already has an approved toolset.</description>
    </item>
    <item>
      <title>Data Model Registry vs MDM Platform</title>
      <link>https://martenweave.github.io/blog/data-model-registry-vs-mdm-platform.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/data-model-registry-vs-mdm-platform.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A company has a data problem.</description>
    </item>
    <item>
      <title>Data Model Registry vs Data Catalog</title>
      <link>https://martenweave.github.io/blog/data-model-registry-vs-data-catalog.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/data-model-registry-vs-data-catalog.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A migration manager searches the enterprise data catalogue for a customer field.</description>
    </item>
    <item>
      <title>Why AI Should Propose Model Changes but Never Apply Them Directly</title>
      <link>https://martenweave.github.io/blog/why-ai-should-propose-model-changes-but-never-apply-them-directly.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-ai-should-propose-model-changes-but-never-apply-them-directly.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>AI governance</category>
      <description>An AI agent reviews a migration workbook and finds an obvious inconsistency.</description>
    </item>
    <item>
      <title>How Deterministic Validation Reduces Migration Risk</title>
      <link>https://martenweave.github.io/blog/deterministic-validation-migration-risk.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/deterministic-validation-migration-risk.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>The migration workbook looks complete.</description>
    </item>
    <item>
      <title>How to Manage Global and Local Requirements in SAP MDG</title>
      <link>https://martenweave.github.io/blog/how-to-manage-global-and-local-requirements-in-sap-mdg.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-manage-global-and-local-requirements-in-sap-mdg.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>The global template says the field is mandatory.</description>
    </item>
    <item>
      <title>How to Track SAP MDG Model Decisions</title>
      <link>https://martenweave.github.io/blog/how-to-track-sap-mdg-model-decisions.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-track-sap-mdg-model-decisions.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>During a design workshop, the programme agrees that a supplier classification should be mandatory.</description>
    </item>
    <item>
      <title>How to Validate That SAP MDG Configuration Matches the Approved Model</title>
      <link>https://martenweave.github.io/blog/how-to-validate-that-sap-mdg-configuration-matches-the-approved-model.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-validate-that-sap-mdg-configuration-matches-the-approved-model.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>The design review is complete.</description>
    </item>
    <item>
      <title>How to Build an Evidence-Based Migration Readiness Report</title>
      <link>https://martenweave.github.io/blog/evidence-based-migration-readiness-report.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/evidence-based-migration-readiness-report.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>The steering committee sees a green dashboard.</description>
    </item>
    <item>
      <title>How Better Model Traceability Reduces Rework</title>
      <link>https://martenweave.github.io/blog/how-better-model-traceability-reduces-rework.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-better-model-traceability-reduces-rework.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A migration defect appears during UAT.</description>
    </item>
    <item>
      <title>How to Reduce Key-Person Risk in SAP Programmes</title>
      <link>https://martenweave.github.io/blog/how-to-reduce-key-person-risk-in-sap-programmes.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-reduce-key-person-risk-in-sap-programmes.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>The programme has one person who knows how everything fits together.</description>
    </item>
    <item>
      <title>How Much of an MDG Programme Happens Outside the MDG Platform?</title>
      <link>https://martenweave.github.io/blog/how-much-of-an-mdg-programme-happens-outside-the-mdg-platform.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-much-of-an-mdg-programme-happens-outside-the-mdg-platform.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>The programme has selected SAP Master Data Governance.</description>
    </item>
    <item>
      <title>How a Small Martenweave Pilot Can De-Risk a Large MDG Investment</title>
      <link>https://martenweave.github.io/blog/how-a-small-martenweave-pilot-can-de-risk-a-large-mdg-investment.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-a-small-martenweave-pilot-can-de-risk-a-large-mdg-investment.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>The organisation is preparing a major SAP Master Data Governance programme.</description>
    </item>
    <item>
      <title>How Metalhatscats Helps Teams Establish Model Governance</title>
      <link>https://martenweave.github.io/blog/how-metalhatscats-helps-teams-establish-model-governance.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-metalhatscats-helps-teams-establish-model-governance.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>AMS and continuity</category>
      <description>A programme has already created most of the artefacts it needs.</description>
    </item>
    <item>
      <title>How to Turn Model Governance into an AMS Capability After Go-Live</title>
      <link>https://martenweave.github.io/blog/how-to-turn-model-governance-into-an-ams-capability-after-go-live.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-turn-model-governance-into-an-ams-capability-after-go-live.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>AMS and continuity</category>
      <description>The implementation programme has ended.</description>
    </item>
    <item>
      <title>How to Use GitHub as a Change-Control Layer for SAP Data Models</title>
      <link>https://martenweave.github.io/blog/how-to-use-github-as-a-change-control-layer-for-sap-data-models.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-use-github-as-a-change-control-layer-for-sap-data-models.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A country team changes one row in a mapping workbook.</description>
    </item>
    <item>
      <title>How to Govern Spreadsheet Changes Without Forcing Business Users into Git</title>
      <link>https://martenweave.github.io/blog/how-to-govern-spreadsheet-changes-without-forcing-business-users-into.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-govern-spreadsheet-changes-without-forcing-business-users-into.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>The business owner receives a mapping workbook.</description>
    </item>
    <item>
      <title>How to Design a Model Change Request That Business and Technical Teams Can Review Together</title>
      <link>https://martenweave.github.io/blog/how-to-design-a-model-change-request-that-business-and-technical-teams.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-design-a-model-change-request-that-business-and-technical-teams.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>AMS and continuity</category>
      <description>A business owner requests a change:</description>
    </item>
    <item>
      <title>How to Prioritise Model Changes by Business Risk Instead of Ticket Urgency</title>
      <link>https://martenweave.github.io/blog/how-to-prioritise-model-changes-by-business-risk-instead-of-ticket.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-prioritise-model-changes-by-business-risk-instead-of-ticket.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A senior stakeholder opens a ticket:</description>
    </item>
    <item>
      <title>How to Build a Model Risk Register for SAP Migration and MDG</title>
      <link>https://martenweave.github.io/blog/how-to-build-a-model-risk-register-for-sap-migration-and-mdg.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-build-a-model-risk-register-for-sap-migration-and-mdg.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>The programme risk register looks healthy.</description>
    </item>
    <item>
      <title>How to Turn Model Risks into an Actionable SAP Migration Backlog</title>
      <link>https://martenweave.github.io/blog/how-to-turn-model-risks-into-an-actionable-sap-migration-backlog.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-turn-model-risks-into-an-actionable-sap-migration-backlog.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>The migration programme has identified a serious risk:</description>
    </item>
    <item>
      <title>How to Define Exit Criteria for SAP Migration Model Risks</title>
      <link>https://martenweave.github.io/blog/how-to-define-exit-criteria-for-sap-migration-model-risks.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-define-exit-criteria-for-sap-migration-model-risks.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>The programme has completed the remediation task.</description>
    </item>
    <item>
      <title>How to Prove That an SAP Migration Risk Is Really Closed</title>
      <link>https://martenweave.github.io/blog/how-to-prove-that-an-sap-migration-risk-is-really-closed.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-prove-that-an-sap-migration-risk-is-really-closed.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>The steering committee asks whether a critical migration risk has been closed.</description>
    </item>
    <item>
      <title>How to Design a Closure Evidence Workspace for SAP Migration and MDG</title>
      <link>https://martenweave.github.io/blog/how-to-design-a-closure-evidence-workspace-for-sap-migration-and-mdg.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-design-a-closure-evidence-workspace-for-sap-migration-and-mdg.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>The programme is preparing for a risk-closure meeting.</description>
    </item>
    <item>
      <title>How to Connect Martenweave’s UI to Live Model, Dataset and Proposal Data</title>
      <link>https://martenweave.github.io/blog/how-to-connect-martenweaves-ui-to-live-model-dataset-and-proposal-data.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-connect-martenweaves-ui-to-live-model-dataset-and-proposal-data.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A migration architect opens Martenweave and searches for Customer Group .</description>
    </item>
    <item>
      <title>How to Investigate an SAP Data Model Problem Before Changing the System</title>
      <link>https://martenweave.github.io/blog/how-to-investigate-an-sap-data-model-problem-before-changing-the-system.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-investigate-an-sap-data-model-problem-before-changing-the-system.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A migration test fails because Customer Group is missing.</description>
    </item>
    <item>
      <title>How to Structure a Model Investigation Case So the Finding Can Be Reused</title>
      <link>https://martenweave.github.io/blog/how-to-structure-a-model-investigation-case-so-the-finding-can-be-reused.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-structure-a-model-investigation-case-so-the-finding-can-be-reused.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>The German migration team spends three weeks investigating why Customer Group cannot be mapped reliably.</description>
    </item>
    <item>
      <title>How to Build a Reusable Decision Library for SAP Migration and MDM</title>
      <link>https://martenweave.github.io/blog/how-to-build-a-reusable-decision-library-for-sap-migration-and-mdm.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-build-a-reusable-decision-library-for-sap-migration-and-mdm.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>A programme has an approved decision:</description>
    </item>
    <item>
      <title>How to Prevent Local SAP Decisions from Fragmenting the Global Data Model</title>
      <link>https://martenweave.github.io/blog/how-to-prevent-local-sap-decisions-from-fragmenting-the-global-data.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-prevent-local-sap-decisions-from-fragmenting-the-global-data.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A country team raises a reasonable request.</description>
    </item>
    <item>
      <title>How to Decide Whether a Local SAP Requirement Belongs in the Global Model</title>
      <link>https://martenweave.github.io/blog/how-to-decide-whether-a-local-sap-requirement-belongs-in-the-global.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-decide-whether-a-local-sap-requirement-belongs-in-the-global.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A country team requests a new field:</description>
    </item>
    <item>
      <title>How to Design Global and Local Model Inheritance Without Creating Configuration Chaos</title>
      <link>https://martenweave.github.io/blog/how-to-design-global-and-local-model-inheritance-without-creating.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-design-global-and-local-model-inheritance-without-creating.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>The global supplier model defines Supplier Risk as a mandatory final classification for active strategic suppliers.</description>
    </item>
    <item>
      <title>How to Resolve Conflicting Global and Local Rules Before They Reach SAP Configuration</title>
      <link>https://martenweave.github.io/blog/how-to-resolve-conflicting-global-and-local-rules-before-they-reach-sap.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-resolve-conflicting-global-and-local-rules-before-they-reach-sap.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>The global design states:</description>
    </item>
    <item>
      <title>How to Test Global and Local SAP Rules Against Real Migration Data</title>
      <link>https://martenweave.github.io/blog/how-to-test-global-and-local-sap-rules-against-real-migration-data.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-test-global-and-local-sap-rules-against-real-migration-data.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>The global design says that Supplier Risk is mandatory for every active strategic supplier.</description>
    </item>
    <item>
      <title>How to Turn Migration Rule Test Results into Model Decisions Instead of Defect Noise</title>
      <link>https://martenweave.github.io/blog/how-to-turn-migration-rule-test-results-into-model-decisions-instead-of.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-turn-migration-rule-test-results-into-model-decisions-instead-of.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>The first migration-rule test produces 8,420 failures.</description>
    </item>
    <item>
      <title>How to Build a Migration Finding Taxonomy That Business, Data and SAP Teams Use Consistently</title>
      <link>https://martenweave.github.io/blog/how-to-build-a-migration-finding-taxonomy-that-business-data-and-sap.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-build-a-migration-finding-taxonomy-that-business-data-and-sap.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>The migration test reports that 4,860 supplier records failed the Tax Identifier rule.</description>
    </item>
    <item>
      <title>How to Route Migration Findings to the Right Owner Without Creating Another Governance Bureaucracy</title>
      <link>https://martenweave.github.io/blog/how-to-route-migration-findings-to-the-right-owner-without-creating.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-route-migration-findings-to-the-right-owner-without-creating.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>A migration-readiness run identifies 1,284 strategic suppliers without Supplier Risk.</description>
    </item>
    <item>
      <title>How to Define Data Ownership That Still Works After the SAP Programme Ends</title>
      <link>https://martenweave.github.io/blog/how-to-define-data-ownership-that-still-works-after-the-sap-programme.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-define-data-ownership-that-still-works-after-the-sap-programme.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>Three months after go-live, an AMS analyst receives an incident.</description>
    </item>
    <item>
      <title>How to Build an AMS Model Change Process That Does Not Recreate the SAP Project</title>
      <link>https://martenweave.github.io/blog/how-to-build-an-ams-model-change-process-that-does-not-recreate-the-sap.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-build-an-ams-model-change-process-that-does-not-recreate-the-sap.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>AMS and continuity</category>
      <description>Six months after go-live, a country requests a new Supplier Classification value.</description>
    </item>
    <item>
      <title>How to Separate SAP AMS Incidents, Service Requests and Model Changes Without Losing Traceability</title>
      <link>https://martenweave.github.io/blog/how-to-separate-sap-ams-incidents-service-requests-and-model-changes.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-separate-sap-ams-incidents-service-requests-and-model-changes.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A user reports that a supplier cannot be activated in SAP.</description>
    </item>
    <item>
      <title>How to Detect When an SAP AMS Workaround Has Become an Unapproved Data Model</title>
      <link>https://martenweave.github.io/blog/how-to-detect-when-an-sap-ams-workaround-has-become-an-unapproved-data.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-detect-when-an-sap-ams-workaround-has-become-an-unapproved-data.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>AMS and continuity</category>
      <description>A supplier cannot be activated because its final risk classification is missing.</description>
    </item>
    <item>
      <title>How to Retire SAP AMS Workarounds Without Breaking the Business Process</title>
      <link>https://martenweave.github.io/blog/how-to-retire-sap-ams-workarounds-without-breaking-the-business-process.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-retire-sap-ams-workarounds-without-breaking-the-business-process.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>AMS and continuity</category>
      <description>A temporary Supplier Risk workaround has been running for nine months.</description>
    </item>
    <item>
      <title>How to Use AMS Incident Patterns to Improve the SAP Data Model Instead of Just Reducing Ticket Volume</title>
      <link>https://martenweave.github.io/blog/how-to-use-ams-incident-patterns-to-improve-the-sap-data-model-instead.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-use-ams-incident-patterns-to-improve-the-sap-data-model-instead.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>AMS and continuity</category>
      <description>The AMS dashboard shows progress.</description>
    </item>
    <item>
      <title>How Martenweave Represents a Data Model in Markdown and YAML</title>
      <link>https://martenweave.github.io/blog/how-martenweave-represents-a-data-model-in-markdown-and-yaml.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-martenweave-represents-a-data-model-in-markdown-and-yaml.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A migration team needs to confirm the meaning of Customer Group .</description>
    </item>
    <item>
      <title>Why Canonical Model Files Should Remain the Source of Truth</title>
      <link>https://martenweave.github.io/blog/why-canonical-model-files-should-remain-the-source-of-truth.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-canonical-model-files-should-remain-the-source-of-truth.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>AI governance</category>
      <description>A business owner updates Customer Group in an Excel review file.</description>
    </item>
    <item>
      <title>How Martenweave Builds a Searchable SQLite Model Index</title>
      <link>https://martenweave.github.io/blog/how-martenweave-builds-a-searchable-sqlite-model-index.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-martenweave-builds-a-searchable-sqlite-model-index.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A migration analyst searches for:</description>
    </item>
    <item>
      <title>How Deterministic Model Validation Works</title>
      <link>https://martenweave.github.io/blog/how-deterministic-model-validation-works.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-deterministic-model-validation-works.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>A migration analyst adds a new mapping:</description>
    </item>
    <item>
      <title>How Martenweave Represents Entities, Attributes, Rules and Relationships</title>
      <link>https://martenweave.github.io/blog/how-martenweave-represents-entities-attributes-rules-and-relationships.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-martenweave-represents-entities-attributes-rules-and-relationships.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A migration workbook contains one row:</description>
    </item>
    <item>
      <title>How to Version a Data Model Without Turning It into Documentation Chaos</title>
      <link>https://martenweave.github.io/blog/how-to-version-a-data-model-without-turning-it-into-documentation-chaos.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-version-a-data-model-without-turning-it-into-documentation-chaos.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A Customer Group rule changes during an SAP programme.</description>
    </item>
    <item>
      <title>How Model Diffing Should Work Across SAP Releases</title>
      <link>https://martenweave.github.io/blog/how-model-diffing-should-work-across-sap-releases.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-model-diffing-should-work-across-sap-releases.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>An SAP programme compares its Wave 2 and Wave 3 model repositories.</description>
    </item>
    <item>
      <title>How to Design Stable IDs for Enterprise Data Model Objects</title>
      <link>https://martenweave.github.io/blog/how-to-design-stable-ids-for-enterprise-data-model-objects.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-design-stable-ids-for-enterprise-data-model-objects.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A Customer Group attribute begins its life in one migration workbook.</description>
    </item>
    <item>
      <title>Why Generated Indexes Should Be Disposable</title>
      <link>https://martenweave.github.io/blog/why-generated-indexes-should-be-disposable.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-generated-indexes-should-be-disposable.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A Martenweave user opens modelops.db and corrects the name of an Attribute directly in SQLite.</description>
    </item>
    <item>
      <title>How to Package and Transfer a Martenweave Model Repository</title>
      <link>https://martenweave.github.io/blog/how-to-package-and-transfer-a-martenweave-model-repository.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-package-and-transfer-a-martenweave-model-repository.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>An SAP migration programme reaches handover.</description>
    </item>
    <item>
      <title>How to Build Field-Level Lineage for an SAP Migration</title>
      <link>https://martenweave.github.io/blog/how-to-build-field-level-lineage-for-an-sap-migration.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-build-field-level-lineage-for-an-sap-migration.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A migration programme says that it has lineage.</description>
    </item>
    <item>
      <title>Why Table-Level Lineage Is Not Enough for Master Data</title>
      <link>https://martenweave.github.io/blog/why-table-level-lineage-is-not-enough-for-master-data.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-table-level-lineage-is-not-enough-for-master-data.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A migration architect opens the lineage view and sees:</description>
    </item>
    <item>
      <title>How to Trace a Business Attribute Across Source Systems, Mappings and SAP Fields</title>
      <link>https://martenweave.github.io/blog/how-to-trace-a-business-attribute-across-source-systems-mappings-and.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-trace-a-business-attribute-across-source-systems-mappings-and.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A business owner asks:</description>
    </item>
    <item>
      <title>How to Calculate Downstream Impact Before Changing an SAP Field</title>
      <link>https://martenweave.github.io/blog/how-to-calculate-downstream-impact-before-changing-an-sap-field.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-calculate-downstream-impact-before-changing-an-sap-field.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A technical team proposes a simple change:</description>
    </item>
    <item>
      <title>How Impact Analysis Should Work for Rules, Mappings and Value Lists</title>
      <link>https://martenweave.github.io/blog/how-impact-analysis-should-work-for-rules-mappings-and-value-lists.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-impact-analysis-should-work-for-rules-mappings-and-value-lists.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A team proposes three changes:</description>
    </item>
    <item>
      <title>How to Detect Orphaned Fields, Rules and Mappings</title>
      <link>https://martenweave.github.io/blog/how-to-detect-orphaned-fields-rules-and-mappings.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-detect-orphaned-fields-rules-and-mappings.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>A repository validates successfully.</description>
    </item>
    <item>
      <title>How to Detect Broken Lineage After a Source or Target System Change</title>
      <link>https://martenweave.github.io/blog/how-to-detect-broken-lineage-after-a-source-or-target-system-change.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-detect-broken-lineage-after-a-source-or-target-system-change.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A source system is retired.</description>
    </item>
    <item>
      <title>How to Model Source Authority and Fallback Paths Without Creating Ambiguous Lineage</title>
      <link>https://martenweave.github.io/blog/how-to-model-source-authority-and-fallback-paths-without-creating.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-model-source-authority-and-fallback-paths-without-creating.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A migration team traces Customer Group upstream and finds four possible sources:</description>
    </item>
    <item>
      <title>How to Separate Design-Time Lineage from Runtime Evidence</title>
      <link>https://martenweave.github.io/blog/how-to-separate-design-time-lineage-from-runtime-evidence.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-separate-design-time-lineage-from-runtime-evidence.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A migration design states:</description>
    </item>
    <item>
      <title>How to Use Lineage Evidence During Mock Loads, Cutover and Hypercare</title>
      <link>https://martenweave.github.io/blog/how-to-use-lineage-evidence-during-mock-loads-cutover-and-hypercare.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-use-lineage-evidence-during-mock-loads-cutover-and-hypercare.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>Lineage is often treated as design documentation.</description>
    </item>
    <item>
      <title>How to Build a Lineage-Based Migration Readiness Score Without Hiding Risk</title>
      <link>https://martenweave.github.io/blog/how-to-build-a-lineage-based-migration-readiness-score-without-hiding.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-build-a-lineage-based-migration-readiness-score-without-hiding.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A migration dashboard shows:</description>
    </item>
    <item>
      <title>How to Explain Lineage and Impact to Business Owners Without Showing Them a Graph Database</title>
      <link>https://martenweave.github.io/blog/how-to-explain-lineage-and-impact-to-business-owners-without-showing.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-explain-lineage-and-impact-to-business-owners-without-showing.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A data architect opens a lineage viewer during a business review.</description>
    </item>
    <item>
      <title>How Lineage Supports AMS Root-Cause Analysis After Go-Live</title>
      <link>https://martenweave.github.io/blog/how-lineage-supports-ams-root-cause-analysis-after-go-live.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-lineage-supports-ams-root-cause-analysis-after-go-live.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A production incident arrives in the AMS queue:</description>
    </item>
    <item>
      <title>How to Connect Dataset Gaps to Lineage and Business Impact</title>
      <link>https://martenweave.github.io/blog/how-to-connect-dataset-gaps-to-lineage-and-business-impact.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-connect-dataset-gaps-to-lineage-and-business-impact.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A dataset-readiness report says:</description>
    </item>
    <item>
      <title>How to Prioritize Migration Gaps by Business Risk Instead of Field Count</title>
      <link>https://martenweave.github.io/blog/how-to-prioritize-migration-gaps-by-business-risk-instead-of-field-count.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-prioritize-migration-gaps-by-business-risk-instead-of-field-count.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>A readiness report identifies 137 data gaps.</description>
    </item>
    <item>
      <title>How to Turn Migration Gap Findings into Reviewable Patch Proposals</title>
      <link>https://martenweave.github.io/blog/how-to-turn-migration-gap-findings-into-reviewable-patch-proposals.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-to-turn-migration-gap-findings-into-reviewable-patch-proposals.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>A profiling script finds that the Product migration dataset has no Plant field.</description>
    </item>
    <item>
      <title>Why AI Should Propose Model Changes but Never Approve Them</title>
      <link>https://martenweave.github.io/blog/why-ai-should-propose-model-changes-but-never-approve-them.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-ai-should-propose-model-changes-but-never-approve-them.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>AI governance</category>
      <description>A Product migration dataset contains PLANNER GROUP , MRP TYPE and PROCUREMENT TYPE .</description>
    </item>
    <item>
      <title>Why a Data Catalogue Is Not Enough for Migration Model Governance</title>
      <link>https://martenweave.github.io/blog/why-a-data-catalogue-is-not-enough-for-migration-model-governance.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-a-data-catalogue-is-not-enough-for-migration-model-governance.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>A migration team is preparing Product data for SAP S/4HANA.</description>
    </item>
    <item>
      <title>Why SAP MDG Is Not a Replacement for a Migration Model Registry</title>
      <link>https://martenweave.github.io/blog/why-sap-mdg-is-not-a-replacement-for-a-migration-model-registry.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-sap-mdg-is-not-a-replacement-for-a-migration-model-registry.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>A programme is migrating Supplier bank data into SAP S/4HANA.</description>
    </item>
    <item>
      <title>How Martenweave Should Work Alongside SAP MDG During a Migration</title>
      <link>https://martenweave.github.io/blog/how-martenweave-should-work-alongside-sap-mdg-during-a-migration.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-martenweave-should-work-alongside-sap-mdg-during-a-migration.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>SAP MDG and MDM</category>
      <description>A programme is migrating Supplier bank data from several legacy systems into SAP S/4HANA.</description>
    </item>
    <item>
      <title>Why Migration Mapping Workbooks Become Technical Debt—and What Should Replace Them</title>
      <link>https://martenweave.github.io/blog/why-migration-mapping-workbooks-become-technical-debt-and-what-should.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-migration-mapping-workbooks-become-technical-debt-and-what-should.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>A migration programme creates a mapping workbook for Product planning data.</description>
    </item>
    <item>
      <title>How We Convert a Mapping Workbook into a Canonical Model Without Losing Business Context</title>
      <link>https://martenweave.github.io/blog/how-we-convert-a-mapping-workbook-into-a-canonical-model-without-losing.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-convert-a-mapping-workbook-into-a-canonical-model-without-losing.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>When we receive a migration mapping workbook, our first instinct should not be to convert every row into YAML.</description>
    </item>
    <item>
      <title>How We Keep Business Decisions Traceable After the Mapping Workbook Is Gone</title>
      <link>https://martenweave.github.io/blog/how-we-keep-business-decisions-traceable-after-the-mapping-workbook-is.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-keep-business-decisions-traceable-after-the-mapping-workbook-is.html</guid>
      <pubDate>Tue, 14 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>A migration team decides that MRP Controller must be derived differently for Plant PL30.</description>
    </item>
    <item>
      <title>How We Prevent Temporary Migration Exceptions from Becoming Permanent Rules</title>
      <link>https://martenweave.github.io/blog/how-we-prevent-temporary-migration-exceptions-from-becoming-permanent.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-prevent-temporary-migration-exceptions-from-becoming-permanent.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>During Mock Load 2, the Product planning migration has a coverage problem.</description>
    </item>
    <item>
      <title>How We Model Data Quality Rules Without Mixing Business Policy and Technical Validation</title>
      <link>https://martenweave.github.io/blog/how-we-model-data-quality-rules-without-mixing-business-policy-and.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-model-data-quality-rules-without-mixing-business-policy-and.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>A migration programme is preparing Supplier bank data for SAP.</description>
    </item>
    <item>
      <title>How We Turn Validation Failures into Actionable Findings Instead of Another Error Report</title>
      <link>https://martenweave.github.io/blog/how-we-turn-validation-failures-into-actionable-findings-instead-of.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-turn-validation-failures-into-actionable-findings-instead-of.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>We run a validation against a Supplier bank-data migration dataset.</description>
    </item>
    <item>
      <title>How We Decide Whether a Finding Requires Data Correction, a Mapping Change or a Model Change</title>
      <link>https://martenweave.github.io/blog/how-we-decide-whether-a-finding-requires-data-correction-a-mapping.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-decide-whether-a-finding-requires-data-correction-a-mapping.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>A Supplier bank-data validation fails for 3,400 records.</description>
    </item>
    <item>
      <title>How We Prioritize Findings by Business Impact Instead of Error Count</title>
      <link>https://martenweave.github.io/blog/how-we-prioritize-findings-by-business-impact-instead-of-error-count.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-prioritize-findings-by-business-impact-instead-of-error-count.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>We complete a Supplier bank-data validation run.</description>
    </item>
    <item>
      <title>How We Prevent Duplicate Findings Across Mock Loads and Migration Waves</title>
      <link>https://martenweave.github.io/blog/how-we-prevent-duplicate-findings-across-mock-loads-and-migration-waves.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-prevent-duplicate-findings-across-mock-loads-and-migration-waves.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>We run the Supplier bank-verification check during Mock Load 2.</description>
    </item>
    <item>
      <title>How We Connect Findings to Owners Without Building Another Workflow Engine</title>
      <link>https://martenweave.github.io/blog/how-we-connect-findings-to-owners-without-building-another-workflow.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-connect-findings-to-owners-without-building-another-workflow.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>We confirm a critical Supplier bank-data Finding.</description>
    </item>
    <item>
      <title>How We Prove That a Finding Is Actually Resolved</title>
      <link>https://martenweave.github.io/blog/how-we-prove-that-a-finding-is-actually-resolved.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-prove-that-a-finding-is-actually-resolved.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>We identify a critical Supplier bank-data Finding.</description>
    </item>
    <item>
      <title>How We Detect When Evidence Has Become Stale</title>
      <link>https://martenweave.github.io/blog/how-we-detect-when-evidence-has-become-stale.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-detect-when-evidence-has-become-stale.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>We resolve a critical Supplier bank-data Finding during Cutover Rehearsal 5.</description>
    </item>
    <item>
      <title>How We Build a Migration Readiness View That Does Not Hide Exceptions</title>
      <link>https://martenweave.github.io/blog/how-we-build-a-migration-readiness-view-that-does-not-hide-exceptions.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-build-a-migration-readiness-view-that-does-not-hide-exceptions.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>The Supplier migration dashboard shows:</description>
    </item>
    <item>
      <title>How We Separate Technical Completeness from Business Readiness</title>
      <link>https://martenweave.github.io/blog/how-we-separate-technical-completeness-from-business-readiness.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-separate-technical-completeness-from-business-readiness.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A Supplier migration load finishes successfully.</description>
    </item>
    <item>
      <title>How We Use Model Evidence During Cutover Approval</title>
      <link>https://martenweave.github.io/blog/how-we-use-model-evidence-during-cutover-approval.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-use-model-evidence-during-cutover-approval.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>The Supplier migration team completes the final rehearsal.</description>
    </item>
    <item>
      <title>Why a Successfully Loaded Material May Still Be Unusable</title>
      <link>https://martenweave.github.io/blog/why-a-successfully-loaded-material-may-still-be-unusable.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-a-successfully-loaded-material-may-still-be-unusable.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Logistics data</category>
      <description>The material migration report looks successful.</description>
    </item>
    <item>
      <title>How We Detect Missing Material Extensions Before Cutover</title>
      <link>https://martenweave.github.io/blog/how-we-detect-missing-material-extensions-before-cutover.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-detect-missing-material-extensions-before-cutover.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Logistics data</category>
      <description>The material migration team reports:</description>
    </item>
    <item>
      <title>Why Units of Measure Are One of the Most Dangerous Logistics Migration Objects</title>
      <link>https://martenweave.github.io/blog/why-units-of-measure-are-one-of-the-most-dangerous-logistics-migration.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-units-of-measure-are-one-of-the-most-dangerous-logistics-migration.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Logistics data</category>
      <description>The unit-of-measure migration report looks harmless.</description>
    </item>
    <item>
      <title>How We Model Packaging Hierarchies Without Losing Logistics Meaning</title>
      <link>https://martenweave.github.io/blog/how-we-model-packaging-hierarchies-without-losing-logistics-meaning.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-model-packaging-hierarchies-without-losing-logistics-meaning.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Logistics data</category>
      <description>The material migration team reports that packaging data is complete.</description>
    </item>
    <item>
      <title>Why S/4 Material Readiness Does Not Prove EWM Readiness</title>
      <link>https://martenweave.github.io/blog/why-s4-material-readiness-does-not-prove-ewm-readiness.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-s4-material-readiness-does-not-prove-ewm-readiness.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Logistics data</category>
      <description>The material migration dashboard is green.</description>
    </item>
    <item>
      <title>How We Create a Canonical Location Model Across ERP, EWM, TM and External Carriers</title>
      <link>https://martenweave.github.io/blog/how-we-create-a-canonical-location-model-across-erp-ewm-tm-and-external.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-create-a-canonical-location-model-across-erp-ewm-tm-and-external.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Logistics data</category>
      <description>What happens when five systems agree that a location exists—but none of them agrees on what the location actually is?</description>
    </item>
    <item>
      <title>How We Govern Lead Times Across Procurement, Production, Warehouse and Transportation</title>
      <link>https://martenweave.github.io/blog/how-we-govern-lead-times-across-procurement-production-warehouse-and.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-we-govern-lead-times-across-procurement-production-warehouse-and.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Logistics data</category>
      <description>What exactly are we promising when we say the lead time is 12 days?</description>
    </item>
    <item>
      <title>Why SAP Data Programmes Pay Consultants to Rediscover the Same Knowledge</title>
      <link>https://martenweave.github.io/blog/why-sap-data-programmes-pay-consultants-to-rediscover-the-same-knowledge.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-sap-data-programmes-pay-consultants-to-rediscover-the-same-knowledge.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>Why are we paying senior consultants to answer the same question for the fourth time?</description>
    </item>
    <item>
      <title>How a Canonical Data and Interface Registry Reduces Change-Impact Consulting Costs</title>
      <link>https://martenweave.github.io/blog/how-a-canonical-data-and-interface-registry-reduces-change-impact.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-a-canonical-data-and-interface-registry-reduces-change-impact.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>Why can changing one master-data field require six weeks of analysis?</description>
    </item>
    <item>
      <title>Why Mapping Workbooks Become a Recurring Consulting Cost</title>
      <link>https://martenweave.github.io/blog/why-mapping-workbooks-become-a-recurring-consulting-cost.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-mapping-workbooks-become-a-recurring-consulting-cost.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>How many times should a transformation programme pay to map the same 1,400 legacy codes?</description>
    </item>
    <item>
      <title>How Much Does a Green Dashboard Cost When Every Team Rebuilds the Evidence Behind It?</title>
      <link>https://martenweave.github.io/blog/how-much-does-a-green-dashboard-cost-when-every-team-rebuilds-the.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/how-much-does-a-green-dashboard-cost-when-every-team-rebuilds-the.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>How much consulting effort sits behind one green status on a steering-committee slide?</description>
    </item>
    <item>
      <title>Why Consultant Turnover Makes SAP Programmes Pay Twice for the Same Knowledge</title>
      <link>https://martenweave.github.io/blog/why-consultant-turnover-makes-sap-programmes-pay-twice-for-the-same.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-consultant-turnover-makes-sap-programmes-pay-twice-for-the-same.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>What exactly leaves the programme when an experienced consultant leaves?</description>
    </item>
    <item>
      <title>Where Martenweave Fits in Logistics: Managing the Data Behind Operations</title>
      <link>https://martenweave.github.io/blog/where-martenweave-fits-in-logistics-managing-the-data-behind-operations.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/where-martenweave-fits-in-logistics-managing-the-data-behind-operations.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Logistics data</category>
      <description>Logistics problems are often described as operational problems.</description>
    </item>
    <item>
      <title>Logistics Problems Rarely Start in Logistics</title>
      <link>https://martenweave.github.io/blog/logistics-problems-rarely-start-in-logistics.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/logistics-problems-rarely-start-in-logistics.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Logistics data</category>
      <description>When a delivery fails, people usually look at the delivery.</description>
    </item>
    <item>
      <title>SAP Logistics Data Migration Problems Usually Appear Too Late</title>
      <link>https://martenweave.github.io/blog/sap-logistics-data-migration-problems-usually-appear-too-late.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/sap-logistics-data-migration-problems-usually-appear-too-late.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Logistics data</category>
      <description>Most SAP logistics migration problems are discovered at the worst possible moment.</description>
    </item>
    <item>
      <title>What Is a Data Model Registry? A Practical Guide for Managers</title>
      <link>https://martenweave.github.io/blog/what-is-a-data-model-registry-a-practical-guide-for-managers.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/what-is-a-data-model-registry-a-practical-guide-for-managers.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>Most companies do not lack documentation.</description>
    </item>
    <item>
      <title>Why Data Migration Projects Need a Model Registry</title>
      <link>https://martenweave.github.io/blog/why-data-migration-projects-need-a-model-registry.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-data-migration-projects-need-a-model-registry.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>Most migration programmes do not fail because nobody created a mapping.</description>
    </item>
    <item>
      <title>From Mapping Spreadsheet to Governed Data Model</title>
      <link>https://martenweave.github.io/blog/from-mapping-spreadsheet-to-governed-data-model.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/from-mapping-spreadsheet-to-governed-data-model.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>Most migration programmes begin with a spreadsheet.</description>
    </item>
    <item>
      <title>Data Lineage vs Impact Analysis: Why Seeing the Flow Is Not Enough</title>
      <link>https://martenweave.github.io/blog/data-lineage-vs-impact-analysis-why-seeing-the-flow-is-not-enough.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/data-lineage-vs-impact-analysis-why-seeing-the-flow-is-not-enough.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Lineage and impact</category>
      <description>Data lineage is one of the most attractive ideas in data management.</description>
    </item>
    <item>
      <title>Data Quality Tools vs Model Validation: Clean Data Can Still Follow the Wrong Rules</title>
      <link>https://martenweave.github.io/blog/data-quality-tools-vs-model-validation-clean-data-can-still-follow-the.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/data-quality-tools-vs-model-validation-clean-data-can-still-follow-the.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Validation and readiness</category>
      <description>A data-quality report can be completely green while the migration is still wrong.</description>
    </item>
    <item>
      <title>Schema Registry vs Model Registry: Technical Compatibility Is Not Business Meaning</title>
      <link>https://martenweave.github.io/blog/schema-registry-vs-model-registry-technical-compatibility-is-not.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/schema-registry-vs-model-registry-technical-compatibility-is-not.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A message can be technically valid and still be wrong.</description>
    </item>
    <item>
      <title>Why SAP Migration Teams Still Lose Control Even with the Right Tools</title>
      <link>https://martenweave.github.io/blog/why-sap-migration-teams-still-lose-control-even-with-the-right-tools.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-sap-migration-teams-still-lose-control-even-with-the-right-tools.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>AMS and continuity</category>
      <description>An SAP migration programme may have every major tool it is supposed to have.</description>
    </item>
    <item>
      <title>Mapping Version Drift: Why SAP Migration Teams Keep Reopening the Same Decisions</title>
      <link>https://martenweave.github.io/blog/mapping-version-drift-why-sap-migration-teams-keep-reopening-the-same.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/mapping-version-drift-why-sap-migration-teams-keep-reopening-the-same.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>AMS and continuity</category>
      <description>Most migration teams believe they have a mapping problem only when a field is missing.</description>
    </item>
    <item>
      <title>SAP Migration TCO: How Model Governance Reduces Rework and Project Cost</title>
      <link>https://martenweave.github.io/blog/sap-migration-tco-how-model-governance-reduces-rework-and-project-cost.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/sap-migration-tco-how-model-governance-reduces-rework-and-project-cost.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Migration readiness</category>
      <description>The licence fee is rarely the most dangerous part of migration cost.</description>
    </item>
    <item>
      <title>Why Martenweave Creates More Value Across a Programme Than in a Single Project</title>
      <link>https://martenweave.github.io/blog/why-martenweave-creates-more-value-across-a-programme-than-in-a-single.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-martenweave-creates-more-value-across-a-programme-than-in-a-single.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>A small migration project may not need Martenweave.</description>
    </item>
    <item>
      <title>Why Data Governance Frameworks Stay on Paper During SAP Programmes</title>
      <link>https://martenweave.github.io/blog/why-data-governance-frameworks-stay-on-paper-during-sap-programmes.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-data-governance-frameworks-stay-on-paper-during-sap-programmes.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Model governance</category>
      <description>Many organisations already know what good data management should look like.</description>
    </item>
    <item>
      <title>Why DAMA-Based Data Governance Fails to Reach SAP Migration Teams</title>
      <link>https://martenweave.github.io/blog/why-dama-based-data-governance-fails-to-reach-sap-migration-teams.html</link>
      <guid isPermaLink="true">https://martenweave.github.io/blog/why-dama-based-data-governance-fails-to-reach-sap-migration-teams.html</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>AMS and continuity</category>
      <description>Many companies have a data-governance framework.</description>
    </item>
  </channel>
</rss>
