Sievo supplier error duplicate supplier masters inflate tail supplier count

Not specified by the original author.

TL;DR

Fix this in Sievo by acting on the exact problem first: in Sievo, run supplier normalisation over the duplicate masters and merge the name variants of the same supplier into one master record, because the ERP and the card feed spell the same supplier differently and each spelling became its own master, then confirm the tail supplier count drops by the merged duplicates. Do not rerun the same operation unchanged, because the same inputs produce the same failure. Prove the fix on one supplier group or data load first, then rerun the full scope and reconcile the results.

Sievo supplier error duplicate supplier masters inflate tail supplier count

Use this when

• The operation in Sievo fails with this exact problem: Sievo supplier error duplicate supplier masters inflate tail supplier count.
• The same failure repeats on retry with unchanged inputs.
• Work described as a tail supplier count or a supplier rationalisation plan 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 group or data load in Sievo 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: in Sievo, run supplier normalisation over the duplicate masters and merge the name variants of the same supplier into one master record, because the ERP and the card feed spell the same supplier differently and each spelling became its own master, then confirm the tail supplier count drops by the merged duplicates. 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 groups loaded from the same sources, 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 Sievo 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 ERP supplier master, the card feed supplier list and the Sievo supplier table, 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

Sievo supplier error duplicate supplier masters inflate tail supplier count

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 - Sievo supplier error duplicate supplier masters inflate tail supplier count

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

Sievo 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

Supplier masters arrive from several systems with no shared identifier, and name based creation treats each spelling variant as a new supplier.

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 ERP supplier master, the card feed supplier list and the Sievo supplier table; record which source won and why.

Compatibility: Sievo 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/pst5SQSLv7LcOQwKDRBdmAsw

Resolved from the public thread: https://vectle.com/posts/pst5SQSLv7LcOQwKDRBdmAsw

Thread query: Sievo supplier error duplicate supplier masters inflate tail supplier count

TL;DR: Fix this in Sievo by acting on the exact problem first: in Sievo, run supplier normalisation over the duplicate masters and merge the name variants of the same supplier into one master record, because the ERP and the card feed spell the same supplier differently and each spelling became its own master, then confirm the tail supplier count drops by the merged duplicates. Do not rerun the same operation unchanged, because the same inputs produce the same failure. Prove the fix on one supplier group or data load first, then rerun the full scope and reconcile the results.