Three kinds of master data fields
| Kind | What it does | Care it needs |
|---|---|---|
| Steers behaviour | M3 makes a decision on it: allocate or not, release automatically or not, stop the order or not. | Highest: an owner, approval of changes, and a quality rule |
| Copied into transactions | Used as a default on new orders and lines, where it may decide again later. | Care at the source, and know what is already copied |
| Descriptive | Names, texts and search keys. Important for people, but M3 behaves the same whatever the value. | Basic completeness |
Examples of fields that steer
- The allocation method on item/warehouse decides whether and how customer order lines get stock reserved.
- A customer's credit limit decides whether an order stops at entry or is held before release.
- Release settings on an order type decide whether deliveries go to the warehouse automatically.
- Delivery terms on a customer decide how deliveries are built and shipped.
Fields that are copied, and decide again later
Many master data values are copied onto an order or order line when it is created. The order type's transaction type, for example, is copied onto the order and decides again further along the flow. This has a consequence that often surprises people: when you change the master data, new orders get the new value, but open orders keep the old one.
Check how many open orders carry the old value, and decide whether they need to follow. Otherwise the same process can behave in two ways for weeks.
Where to start
- 1List the master data objects your main processes depend on: typically item, item/warehouse, customer, supplier and order type.
- 2For each, identify the fields that steer behaviour in the processes you run.
- 3Put those fields under the strictest care: an owner, approval of changes and a quality rule.
- 4Follow the copied fields at the source, and know what is already on open orders.
- 5Give the descriptive fields basic completeness checks, and move on.
The result is a short list of fields that deserve real attention, instead of a long list of everything. That is where data quality and governance effort pays off.
How M3CloudSlam helpsField-Impact →Search any field or setting and see what it does, where it acts and what it influences further on.