Navy abstract cover with the eyebrow “IFS Cloud | Data governance” and the headline “Data governance inside the IFS Cloud project”

Independent IFS Cloud practice · Data governance

Implementing data governance in an IFS Cloud project: what to decide, what to configure, and in which order

Data governance in an IFS Cloud project is implemented in the same order as the project itself: owners and rules are decided before design, standard controls are configured during build, the rules are first enforced at data migration, and the measures start at go-live. A project that leaves governance until after go-live loads unowned, duplicated data into a new system and then pays for cleaning it twice.

Key takeaways

  • Name a data owner for every master data domain before the first design workshop, because workshops produce data rules and somebody has to accept them.
  • Write each rule as one testable sentence with a measure, and keep it in a decision log, not in workshop slides.
  • Permission sets, duplicate check actions, history logging and anonymization settings are standard IFS Cloud configuration, so the common rules need no custom objects.
  • Data migration is the first real enforcement: a legacy record that breaks a rule is fixed or rejected before load, not after.
  • After go-live, each rule keeps its measure and its owner, reviewed at a fixed meeting rhythm.

1.Why implement data governance inside the IFS Cloud project, not after it?

An IFS Cloud implementation already forces the decisions that governance is made of: which parts, customers and suppliers move to the new system, which fields are filled, who may create a supplier and who approves it. If nobody owns those decisions, the consultant or the migration team takes them by default, and the business discovers them at UAT. The definition of the discipline, and how it differs from data management, is in the definition of data governance.

Governance also has a cost that grows with time. A duplicate supplier found in a migration file is one deleted row. Found after go-live, the same duplicate already carries purchase orders and postings that cannot simply be deleted, so it has to be blocked for new use and its open items settled before it can be retired.

2.What has to be decided before the design workshops?

Before design starts, the project needs a list of data domains and a named owner for each. A domain is a group of records with one accountable person: part master data, customers, suppliers, the chart of accounts, prices.

Decision Who takes it Why before design
List of data domains Project manager with the process owners Every workshop produces rules for one or more domains
Data owner per domain Steering committee Rules need someone with authority to accept them
Data steward per domain Data owner Somebody maintains the records and the measures day to day
Where rules are recorded Project manager A rule only in slides is lost by UAT

Rules accepted in workshops go into a decision log, each with its owner and the reason behind it, as described in the IFS Cloud decision register. Rules that will apply permanently, after the project closes, are later promoted to the enterprise book of rules.

3.How do you write a data rule that can be enforced?

An enforceable data rule names the record, the condition, the moment it must hold and the measure that shows it holds. “Supplier data must be high quality” cannot be tested. “A supplier is created only by the master data team, after a supplier request, and the count of open duplicate warnings on supplier requests is reviewed monthly” can be tested and configured.

Each rule then gets one of three answers: a standard IFS Cloud function enforces it, a procedure enforces it (a person checks), or it is dropped because nobody will check it. The third answer is legitimate: a rule without a measure controls nothing.

4.Which IFS Cloud functions do you configure during build?

Four standard IFS Cloud functions enforce the common governance rules, and each needs a decision from the data owner before configuration.

  • Permission sets. Access rules become permission sets created in Solution Manager > Access Control > Permission Sets. New sets get the delivery type Custom. Design them from the ownership decisions, for example separate sets for creating suppliers and for raising supplier requests, so that the rule “buyers request, the master data team creates” holds in the system. Segregation of duties for SOX-relevant processes is designed at the same time.
  • Duplicate check. For leads, accounts and supplier requests, the duplicate check compares a new record with existing ones using configured rules. On Duplicate Check Action Setup the owner chooses the action: prevent the save, warn with a list of possible duplicates, notify, or do nothing.
  • History logging. Changes to critical fields are traced through History Log Configuration in Solution Manager / Monitoring / History, with Log Insert, Log Update and Log Delete per table or column. Saving the configuration generates database triggers, and an automatic cleanup removes entries older than a set number of days, so the owner chooses the fields and the retention.
  • Personal data cleanup. For GDPR, decide which personal data is deleted when its purpose ends and which is anonymized. Where IFS Cloud cannot delete personal data, anonymization is enabled for it instead, and the anonymization settings per data type include Skip Anonymization and a Fixed Anonymization Value.

One build error to avoid is switching on history logging for whole tables “to be safe”. Every logged insert and update writes a history row, so the history table grows fast and nobody reads it. Logging a short list of fields that the owner actually reviews gives a usable audit trail.

5.How does data migration enforce the rules for the first time?

Data migration is the point where every written rule meets real legacy data, so it is the first enforcement of governance. In the IFS Data Migration Manager, a migration project defines the scope, legacy source data is imported and mapped to target tables, and migration jobs are scheduled. Between import and load the team checks legacy records against the rules and sends failures back to the data owner.

  1. Scope. The data owner decides which records move, for example only suppliers with activity in a defined period.
  2. Check. Staged legacy records are tested against each rule: mandatory business fields, duplicates, valid codes.
  3. Decide. Failures go to the steward as a list. Each is fixed in the source, fixed in staging with a logged reason, or excluded.
  4. Load and reconcile. Counts and key values are compared between source and IFS Cloud, and the owner signs the result.

The planning side of this work is in the IFS Cloud data migration plan, and the reasons to treat migration as a clean break are in data migration as a business reset. If you want these checks run on your migration by the consultant who does the work, see professional data migration services: profiling and scope with the process owners, cleansing decisions taken by the business, mock loads, and count and value reconciliation with sign-off.

6.What keeps governance working after go-live?

After go-live, governance survives only if each rule keeps its owner and its measure and somebody looks at the measures on a fixed date. The steering committee hands data rules to a standing data governance meeting, the rhythm of which is described in IFS Cloud governance cadence. A four-phase view of the same programme (assessment, design, implementation, continuous improvement) is in four phases of implementing data governance in IFS Cloud.

The objection users raise is the extra step: a buyer who used to create a supplier in two minutes now raises a request and waits. The answer that works is showing the cost on the other side, such as the duplicate supplier that received a payment twice or the part created with the wrong unit of measure, and keeping the request turnaround short enough that nobody looks for a way around it.

7.Frequently asked questions

When should data governance start in an IFS Cloud implementation?

Data governance in an IFS Cloud implementation should start before the first design workshop, with a list of data domains and a named data owner for each. Design workshops produce data rules, build configures the IFS Cloud controls that enforce them, and data migration applies the rules to legacy data for the first time.

Is data governance only for large enterprises?

Data governance is not only for large enterprises. A smaller IFS Cloud customer needs fewer roles and fewer rules, but one wrong inventory cost or duplicate supplier has a proportionally larger effect on a smaller business. A short list of owners with one measured rule per domain is enough to start.

How does IFS Cloud support GDPR compliance for personal data?

IFS Cloud supports GDPR through personal data cleanup: personal data is deleted when there is no longer a reason to keep it, and where IFS Cloud cannot delete data, anonymization is enabled for it instead. Anonymization settings are configured per data type, with options to skip anonymization or replace the value with a fixed one. The company still decides retention periods and which data is covered.

Can we govern data across several IFS Cloud sites?

Data governance across several IFS Cloud sites works best with central rules for shared master data, such as part numbering and supplier creation, and local responsibility for site transactions. Each shared domain keeps one data owner for the whole company, while site stewards maintain local records within the central rules.

Which IFS Cloud functions help enforce data governance rules?

Four standard IFS Cloud functions enforce common data governance rules: permission sets for who may create or change records, the duplicate check for leads, accounts and supplier requests, History Log Configuration for tracing changes to selected fields, and anonymization settings for personal data cleanup. Each function needs a decision from the data owner before it is configured.

8.About the author

Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5–10 and IFS Cloud), IFS Certified Associate Consultant, PRINCE2® 7. Based in Kraków, delivering remotely across Europe and globally through an independent practice. You talk to the consultant who does the work, not a sales layer.

Selected clients: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.

IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.

Put data owners and rules into your IFS Cloud plan

Send me your project plan and the list of master data domains. On a call we mark where each owner decision belongs and which control enforces each rule, before the design workshops fix them by default.

Book a call about data governance in your project Read the definition of data governance