M3CloudSlam

Trace · Field Provenance Available

Where can the value in this field come from?

For any field, where its values come from: typed in by a user, defaulted from master data, copied from another record, calculated, or set by the system.

Become a founding customerAll features
Field ProvenanceAvailable
EnteredDefaultedCopiedCalculatedSet by system
  1. Customer order line · unit cost
  2. comes from · copied when the line is createdItem cost in the facility
  3. which comes from · calculatedCosting run

Example field.

Why it matters

Today

  1. 1Ask around where a value comes from
  2. 2Read program documentation
  3. 3Trace it by hand through several screens

Hours of tracing, for every field.

With Field Provenance

  1. 1Pick the field
  2. 2See every way it can get its value
  3. 3Follow the chain back to the master data

The origin of any field, in one view.

How it works

From a field back to its source

  1. 1 / 3

    Pick a field

    On an order, a delivery, an item or any other record; for example the unit cost on an order line.

    Field ProvenanceAvailable
    EnteredDefaultedCopiedCalculatedSet by system
    1. Customer order line · unit cost

    Example field.

  2. 2 / 3

    See where it comes from

    Entered, defaulted, copied or calculated. Here: copied from the item cost when the line is created.

    Field ProvenanceAvailable
    EnteredDefaultedCopiedCalculatedSet by system
    1. Customer order line · unit cost
    2. comes from · copied when the line is createdItem cost in the facility

    Example field.

  3. 3 / 3

    Follow the chain to the source

    The item cost itself is calculated by the costing run: that is where to look when the value is wrong.

    Field ProvenanceAvailable
    EnteredDefaultedCopiedCalculatedSet by system
    1. Customer order line · unit cost
    2. comes from · copied when the line is createdItem cost in the facility
    3. which comes from · calculatedCosting run

    Example field.

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

Fix values at the source

  1. 1Fix the cause, not the symptomCorrect the master data a value comes from, instead of the value on one record.
  2. 2No code readingSee where a value comes from without reading programs or tables.
  3. 3Know what a change reachesSee which fields on which records a master data change will reach.
  4. 4Knowledge that staysThe origin of every field is there for the next person who asks.

Next in your journey

Value ProvenancePreviewTrace one value on one record, with its history.“Why does this line carry this price?” →Data QualityAvailableCheck the master data the field depends on.“Where is our master data wrong?” →Field-ImpactAvailableSee what the field does further on.“What does this setting actually do?” →

See Field Provenance on your own M3

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