M3CloudSlam

Trace · Value Provenance Preview

Why does this record carry this value?

Takes one specific value on one record and traces how it got there: which transaction, which setting or default, which user or job, and when.

Get preview accessAll features
Value ProvenancePreview
Order 1000234 · line 10 · unit cost12.40
  1. 3 MarchLine created by OIS100MI AddOrderLineUnit cost 12.40, copied from the item cost
  2. 18 MarchCosting run updates the item cost to 12.95This order line keeps 12.40
Answer: 12.40 was copied from the item cost when the line was created on 3 March. The later cost change does not update existing lines.

Example record and dates.

Why it matters

Today

  1. 1Compare the record with the master data by hand
  2. 2Search change logs for who changed what
  3. 3Ask finance, sales and IT for their part of the story

A long investigation for one value.

With Value Provenance

  1. 1Point at the value
  2. 2See how it was set, and what happened since
  3. 3Get the answer, with the moment it was set

Why this record carries this value, in one answer.

How it works

From one value to how it got there

  1. 1 / 4

    Point at a value

    One value on one record: here the unit cost of 12.40 on order line 10.

    Value ProvenancePreview
    Order 1000234 · line 10 · unit cost12.40

    Example record and dates.

  2. 2 / 4

    See how it was set

    Created through an API call on 3 March, with the cost copied from the item.

    Value ProvenancePreview
    Order 1000234 · line 10 · unit cost12.40
    1. 3 MarchLine created by OIS100MI AddOrderLineUnit cost 12.40, copied from the item cost

    Example record and dates.

  3. 3 / 4

    See what happened since

    The item cost changed later; this order line kept its value.

    Value ProvenancePreview
    Order 1000234 · line 10 · unit cost12.40
    1. 3 MarchLine created by OIS100MI AddOrderLineUnit cost 12.40, copied from the item cost
    2. 18 MarchCosting run updates the item cost to 12.95This order line keeps 12.40

    Example record and dates.

  4. 4 / 4

    Get the answer

    The value, its origin and the moment it was set, in plain words.

    Value ProvenancePreview
    Order 1000234 · line 10 · unit cost12.40
    1. 3 MarchLine created by OIS100MI AddOrderLineUnit cost 12.40, copied from the item cost
    2. 18 MarchCosting run updates the item cost to 12.95This order line keeps 12.40
    Answer: 12.40 was copied from the item cost when the line was created on 3 March. The later cost change does not update existing lines.

    Example record and dates.

On your own M3. Answers come from one knowledge graph of how M3 behaves, applied to your configuration and data. When something can’t be known, M3CloudSlam says so.

What it brings you

Explain any value, with evidence

  1. 1“You don’t need a consultant for that anymore”Support and finance explain a price or a cost themselves, with the evidence to show.
  2. 2Answers with proofShow the customer or the auditor exactly how a value came about.
  3. 3Rule or personSee whether a value came from a setting, a default or a manual change.
  4. 4Fix it onceKnowing the origin tells you what to change so it doesn't happen again.

Next in your journey

Field ProvenanceAvailableSee every possible origin of the field, not just this one.“Where can this value come from?” →DebuggerPreviewAsk why a record didn't go through.“Why didn't this go through?” →Data GovernanceAvailableSee who changed a master data value, and whether it was approved.“Who changed this, and was it allowed?” →

Use Value Provenance on your own M3, first

We are onboarding a small group of founding customers. You get the newest features first, a direct line to the team, and founding pricing.

Become a founding customer
  • Preview features firstPredictor, Debugger, Release Toggle Impact and Value Provenance
  • Shape the roadmapYour M3 questions decide what we build next
  • Founding pricing, locked inYour rate stays as the product grows