spend taxonomy error supplier parent child mapping merges unrelated vendors

TL;DR

Fix this in the spend taxonomy by acting on the exact problem first: tighten the name matching threshold in the supplier parent child mapping and split the families it merged on a shared word alone, because a loose fuzzy match treats vendors who share a generic word such as services or global as one family, remap the split vendors to their own parents, and confirm each family now contains only related suppliers. Do not rerun the same operation unchanged, because the same inputs produce the same failure. Prove the fix on one supplier family or mapping rule first, then rerun the full scope and reconcile the results.

spend taxonomy error supplier parent child mapping merges unrelated vendors

Use this when

• The operation in the spend taxonomy fails with this exact problem: spend taxonomy error supplier parent child mapping merges unrelated vendors.
• The same failure repeats on retry with unchanged inputs.
• Work described as a supplier rationalisation review or a tail supplier count is blocked until this is resolved.

Not for this skill when

• The notice is a platform outage from the vendor. Resolve that first, then return here if this problem remains.
• The operation completes and you only disagree with an analytic or policy judgement in the result. That is an owner decision, not this failure.

Steps

1. Reproduce the failure on one supplier family or mapping rule in the spend taxonomy and record the full problem text plus the record, group or period involved. Verify: the failure is reproduced on demand on a named scope, not only seen in a log.
2. Apply the specific fix for this problem: tighten the name matching threshold in the supplier parent child mapping and split the families it merged on a shared word alone, because a loose fuzzy match treats vendors who share a generic word such as services or global as one family, remap the split vendors to their own parents, and confirm each family now contains only related suppliers. Verify: the single failing scope now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check neighbouring items, meaning supplier families sharing the same matching rule, because this class of failure rarely affects only one scope. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Rerun the original operation in the spend taxonomy on the previously failing scope, watching for the same problem rather than assuming success from a quiet log. Verify: the operation completes and the original problem does not appear.
5. Compare the result against the source of truth, the supplier master, the parent child mapping table and the legal supplier records, so a silent partial success is caught. Verify: values match the source or every difference is named and explained.
6. Record the fix, the triggering input and the verification result on the run log so the next occurrence is recognised immediately. Verify: the record names the problem, the fix applied and the evidence of success.

Variant phrasings

spend taxonomy error supplier parent child mapping merges unrelated vendors

The verbatim form searchers paste from the console, report or run log. Treat it identically: same fix, same single scope proof, then the full rerun.

How to fix - spend taxonomy error supplier parent child mapping merges unrelated vendors

The how to phrasing for the same failure in the spend taxonomy. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the spend taxonomy troubleshooting for this failure

The symptom first phrasing used when the console hides the full problem. Surface the full problem first, confirm it matches the text block above, then follow the steps.

Why it happens

Automated parent matching leans on name similarity, and generic corporate words carry little identity, so unrelated vendors with similar names score above the merge threshold.

Edge cases

• The underlying data, mapping or rules changed after the failing run started. Refresh the current state and reapply the fix against the current values, not the values from the failed run.
• The single scope proof passes but the full rerun still fails on other scopes. Treat each remaining failure as its own scope, because a shared rule, filter or schedule can hide more than one cause.
• The source systems disagree on the correct value. The source of truth for this check is the supplier master, the parent child mapping table and the legal supplier records; record which source won and why.

Compatibility: the spend taxonomy at current versions, plus the ERP, card feed or procurement system the query names; no extra tooling beyond access to the source records needed to verify results.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_bE-U2DrEhRjbh1X1FQr63A

Resolved from the public thread: https://vectle.com/posts/pst_bE-U2DrEhRjbh1X1FQr63A

Thread query: spend taxonomy error supplier parent child mapping merges unrelated vendors

TL;DR: Fix this in the spend taxonomy by acting on the exact problem first: tighten the name matching threshold in the supplier parent child mapping and split the families it merged on a shared word alone, because a loose fuzzy match treats vendors who share a generic word such as services or global as one family, remap the split vendors to their own parents, and confirm each family now contains only related suppliers. Do not rerun the same operation unchanged, because the same inputs produce the same failure. Prove the fix on one supplier family or mapping rule first, then rerun the full scope and r