Abstract illustration on a navy background with the article title: “One owner for every field group”

Independent IFS Cloud practice · Data governance

Data domain mapping: give every IFS Cloud record and shared field one owner

Data domain mapping assigns every type of record, and every group of fields inside it, to one business domain with a named owner, and records which other domains read it. Without that map, data governance stalls: a quality problem has no addressee, a policy has no place to land, and a request for access has nobody to approve it.

The domains themselves are named earlier, in identify data domains. This article is the next level of detail: how to map IFS Cloud data to those domains field group by field group, and the mistakes that make the map fail.

Key takeaways

  • A domain map is a table, one row per record type or field group, with columns for owning domain, owner, steward, where the data is created, who reads it and which rules apply.
  • Map at field group level, not record level. A supplier in IFS Cloud holds general information, purchase defaults and invoice defaults, and those groups have different natural owners.
  • A field that appears in two groups, such as supplier payment terms in both the purchase and the invoice defaults, gets one owner and a rule for the other.
  • Map by who creates the data in the business, not by the IFS Cloud menu or the database table.
  • Map one domain completely and start governing it before mapping the remaining fields.

1.What does a data domain map contain?

A data domain map is a single table that answers, for any piece of data, who owns it, who looks after it day to day and who depends on it. I keep it to seven columns, because each one answers a question that comes up in governance meetings.

Column Question it answers
Record type and field group What exactly is being mapped, for example “supplier, invoice defaults”
Owning domain Which business domain answers for this data
Owner Which person accepts quality rules and approves access
Steward Who maintains the data and fixes errors in daily work
Created where The business step and the IFS Cloud page where the data is entered
Read by Which other domains depend on it, so changes can be announced
Rules The definitions and quality rules that apply, plus access rules, or a link to them

The “read by” column is the start of the list of data products a domain must deliver, and the “rules” column is where governance policies attach. A map without those two columns is an organisation chart.

2.Why does data governance stall without a domain map?

Data governance stalls without a domain map because every governance action needs an owner, and without a map each action starts with a discussion about who that is. Three situations show it:

  • A quality issue. A report shows suppliers with no tax code. Purchasing says tax is finance data, and finance says the supplier was created by purchasing. The issue is logged and stays open.
  • A policy. The governance committee agrees that personal data in contact records must be reviewed yearly. Nobody can say which team runs the review for which records.
  • An access request. An analyst asks for read access to customer data. IT can grant it, but nobody is entitled to approve it.

Mapping data to domains looks like drawing boxes, and that is why it is underestimated. The work is in the borders: the fields two teams both edit, and the records nobody wants. Those borders are where governance meetings lose their time when the map does not exist.

3.Why map field groups instead of whole records?

Mapping must go below the record because one IFS Cloud record often carries data that different teams create and answer for. Two examples from the IFS Cloud documentation:

  • Supplier. The general supplier information holds data such as default language and country (IFS Cloud 24R2). The general supplier purchase information holds defaults used on purchase orders, for example “a supplier statistics group, a buyer, any additions, payment terms, and currency” (IFS Cloud 24R2). The supplier invoice information holds the currency, the default payment terms, authorization and tax code (IFS Cloud 24R2).
  • Part. A part can be entered with no site and later registered as an inventory, purchase or sales part (IFS Cloud 25R1, Enter Part Data). An inventory part, by contrast, belongs to a site: the 24R2 analysis model documentation states that “each contract (site) has its own set of inventory parts” (IFS Cloud 24R2).

A map at record level would say “supplier: procurement” and stop. A map at field group level shows the real decision. The illustrative rows below are not a client record.

Record and field group Owning domain Read by Rule for the border
Supplier, general information Procurement Finance, quality Procurement creates the supplier; finance cannot create one
Supplier, purchase defaults Procurement Planning, spend analytics Buyer and statistics group maintained by purchasing
Supplier, invoice defaults Finance Procurement Tax code and authorization maintained by accounts payable
Supplier, payment terms and currency Finance Procurement One owner sets the value; the purchase default must match the invoice default, and a mismatch is a quality rule breach
Part with no site Product Inventory, purchasing, sales Part number and description are created once and not renamed per site
Inventory part at a site Inventory Planning, finance Site-level data such as planning and stock settings maintained per site under one set of definitions

The payment terms and currency row needs its own decision because these are the only fields in this map that both domains edit, in two different field groups: purchasing in the purchase defaults and accounts payable in the invoice defaults. Whichever domain gets it, the other domain needs a written agreement on what it receives, which is the subject of confirm sharing agreements.

4.How do you build the map, step by step?

A domain map is built in workshops with the people who create the data, one domain at a time, in six steps.

  1. List the record types of the domain. Start with master data: suppliers, customers, parts, assets. Add transactional records once the master data is mapped.
  2. Split each record into field groups. Use the tabs and sections users already work with in IFS Cloud Web as a first cut, then merge or split by who maintains the fields.
  3. Ask who creates each group. The team that enters the data in its daily work is the natural owner. A team that only reads the data is a consumer.
  4. Mark the borders. Every field that two teams edit, and every group nobody claims, goes on a separate list for the owners to decide together.
  5. Name owner and steward. The owner is a manager who can accept rules; the steward is the person who fixes errors. The sponsor confirms the owners.
  6. Attach the rules. For each group, link the definitions and quality rules that apply, plus the access rules. Access in IFS Cloud is granted through permission sets, which the 25R1 documentation says can grant permissions to “Projections, Lobby Pages, Workflows, Database Tasks and Database Task Chains and System Privileges”, so the owner should be able to name the permission set that implements each access rule.

The map lives outside IFS Cloud, in a shared document with change history. It feeds two things inside the system: permission sets, and the descriptions in whatever catalog the company uses. IFS Cloud has its own IFS Data Catalog, which is meant “to enable users to quickly find data assets within their IFS data sources”. The domain map supplies what a scan cannot: the owner and the business meaning.

5.Should you map every domain before governance starts?

Governance should start as soon as one domain is mapped completely, not after the whole company is. A complete map of the supplier domain lets the owner set quality rules and approve access, and settle the payment terms question while the other domains are still in workshops.

The first domain also produces the template: the column set, the workshop agenda and the list of border questions. The second domain reuses them, and the time goes into its own borders instead of into the format. A domain with a willing owner and a consumer waiting for its data is the right first choice, which is why enabling data mesh in IFS Cloud argues for starting with master data.

6.What makes a data domain map fail?

A data domain map fails in five recognisable ways.

  • Mapped by menu. Each IFS Cloud functional area becomes a domain. The map then mirrors the software, and teams that work across several areas end up with no domain of their own. A comparison of modules and business domains is in mapping IFS functional modules to business domains.
  • Mapped by table. The map is built from the database model by IT. It is precise and nobody in the business recognises it.
  • Too fine. Every field gets its own row. The map becomes unreadable, and field groups are enough for every decision except the borders.
  • Borders left open. Shared fields are marked “joint ownership”. Joint ownership means both teams edit and neither answers, which is the problem the map was meant to solve.
  • Never updated. The organisation changes, a site is added or a team is merged, and the map stays as it was. Review it when the organisation changes and at least when governance roles change hands.

Once the map holds, each domain team works autonomously within its own data, while company-wide rules for privacy and security still apply to all of them, as do the common quality rules. That balance is the federated model described in apply federated computational governance.

7.Frequently asked questions

What is data domain mapping in IFS Cloud?

Data domain mapping in IFS Cloud is the assignment of each record type and field group, such as supplier invoice defaults or inventory parts at a site, to one business domain with a named owner and steward, together with the list of domains that read the data and the rules that apply to it. It is the basis for data governance and for data products.

How is data domain mapping different from identifying data domains?

Identifying data domains decides which business areas exist and who leads each one, for example procurement or finance. Data domain mapping comes next and assigns the actual data to those domains at field group level, including the shared fields that two domains both edit, such as payment terms on an IFS Cloud supplier.

Who should own supplier payment terms in IFS Cloud: purchasing or finance?

Supplier payment terms in IFS Cloud appear both in the purchase defaults and in the invoice defaults, so one domain must own the value and the other must follow it. Either choice works if it is written in the data domain map, with a quality rule that the purchase and invoice defaults match. Leaving both teams to edit the value is the choice that fails.

Should the data domain map follow IFS Cloud modules?

A data domain map should follow the teams that create the data, not the IFS Cloud modules. Modules are a useful cross-check, but one team can work in several functional areas and one functional area can serve more than one team. A map built from the menu mirrors the software and leaves business teams without clear ownership.

Where should the data domain map be kept?

The data domain map should be kept outside IFS Cloud, in a shared document with change history that owners and the governance committee can open. Its content is then implemented inside IFS Cloud through permission sets for access, and reflected in the descriptions of the data catalog the company uses, such as the IFS Data Catalog.

8.About the author

Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5–10 and IFS Cloud). 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.

A migration to IFS Cloud is a natural moment to build the domain map, because every record is reviewed and someone has to approve each cleansing decision. If that is where you are, see my professional data migration services.

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

Map one domain before the next governance meeting

Pick the supplier domain, list its field groups and write down who creates each one. If two names appear next to payment terms, you have found the first decision for your governance committee.

Book a call about your data domain map Next step: master data as data contracts