Skip to main contentSkip to footer

Governance Cadence Meaning: Definition for IFS Cloud

Governance cadence meaning: the set frequency of project reviews, from daily stand-ups to a monthly steering committee, explained for IFS Cloud projects.

TL;DR: The «Heartbeat» of ERP Success The Concept: Governance Cadence is the structured frequency of reviews that keeps IFS Cloud projects aligned with…

Read more

Enterprise Architecture for Data Governance in IFS ERP

Why neglecting the data layer in enterprise architecture is a silent risk, and how strategic data governance builds resilience and AI readiness.

TL;DR: Executive Summary The Insight: The «Data Layer» is not IT plumbing; it is the strategic asset that determines the success of M&A, AI adoption, and…

Read more

IFS Cloud Governance Cadence: SteerCo, RACI, Vendor Review

Run a governance cadence after go-live in IFS Cloud: RACI ownership, a monthly SteerCo, a change and exception register and a semi-annual vendor review.

Mastering Governance Cadence in IFS Cloud: Strategies to Hold Vendors Accountable Expert: Lead IFS ERP Architect | Domain: Data Governance & Compliance |…

Read more

Metadata Management in IFS Cloud: Data Catalog Guide

Metadata management in IFS Cloud: technical vs business metadata, IFS Data Catalog scans and glossaries, sensitivity classification and who owns it.

IFS Cloud metadata management · Independent IFS Cloud practice Metadata management in IFS Cloud: know what every field means, who owns it and how sensitive it…

Read more

ERP Data Quality in IFS Cloud: Governance, MDM, Metadata

ERP data quality in IFS Cloud rests on four disciplines: data governance, master data management, checks at entry and metadata. Where each rule belongs.

IFS Cloud data quality · Independent IFS Cloud practice ERP data quality in IFS Cloud rests on four disciplines: decision rights, one master record, checks at…

Read more

ERP Data Failures: How Data Governance Prevents Them

ERP data failures start where nobody owns the data. How federated governance, data contracts and CRIM ownership prevent them in IFS Cloud projects.

IFS Cloud data governance · Independent IFS Cloud practice ERP data failures start with data nobody owns, and governance closes that gap before go-live An ERP…

Read more

Enabling Data Mesh in IFS Cloud: Start with Master Data

Data mesh in IFS Cloud starts with master data: which supplier, customer, part and asset data to publish first, who owns it, what makes it a product.

Independent IFS Cloud practice · Data mesh and master data Enable a data mesh in IFS Cloud by publishing master data first A data mesh in IFS Cloud is easiest…

Read more

IFS Cloud Data Contracts for Master Data: What Goes In

An IFS Cloud data contract for master data: schema from the API Explorer OpenAPI spec, quality tests, permission sets, versioning rules and a checklist.

Independent IFS Cloud practice · Data contracts An IFS Cloud data contract turns a master data record into a product consumers can rely on An IFS Cloud data…

Read more

Data Domain Mapping in IFS Cloud: One Owner per Field

Data domain mapping in IFS Cloud: assign each record and field group to one owner, settle shared fields such as supplier payment terms, avoid map failures.

Independent IFS Cloud practice · Data governance Data domain mapping: give every IFS Cloud record and shared field one owner Data domain mapping assigns every…

Read more
Abstract illustration on a navy background with the article title: “Know what every field means”

IFS Cloud metadata management · Independent IFS Cloud practice

Metadata management in IFS Cloud: know what every field means, who owns it and how sensitive it is

Metadata management in IFS Cloud is the discipline of registering data assets and giving each one a description and a classification, so that a report author finds the right field without asking IT and an auditor gets a list of personal data fields without a manual search. IFS Data Catalog provides the tool, and data stewards provide the meaning.

Key takeaways

  • Technical metadata describes the structure of the database. Business metadata describes what a field means in a process and who owns it. Both are needed, and they have different owners.
  • IFS Data Catalog scans registered data sources, which must include the IFS Oracle database, and can pre-load IFS-specific metadata before users enrich the assets.
  • Classification in the catalog combines the scan with manual work: users can also apply classifications to an asset on its detail page, and a data steward checks the result.
  • Glossary terms link business vocabulary to data assets, so “project margin” means the same calculation in every report.
  • Metadata does not protect data by itself. Access is enforced by permission sets and Custom Data Access Control, and personal data is cleaned up in Personal Data Management.

1.What is the difference between technical and business metadata in IFS Cloud?

Technical metadata describes how data is stored, and business metadata describes what it means. In IFS Cloud, technical metadata covers the database structure: table and column names, data types, indexes and the relationships between tables. Administrators and developers use it to build integrations and reports.

Business metadata gives that structure a meaning in a process: which field holds the customer identifier used in order-to-cash, which definition of margin a project report uses, who owns the supplier record and how sensitive a column is. Key users and report authors depend on it, and it cannot be scanned from the database because it lives in people’s heads until someone writes it down.

Type What it records Who maintains it
Technical metadata Tables, columns, data types, indexes, relationships Collected by scanning, checked by the ERP administrator
Business metadata Meaning, owner, glossary term, business rule, sensitivity Data stewards in the business domains

2.What does IFS Data Catalog do?

IFS Data Catalog registers and scans IFS data sources, classifies the assets it finds and lets users search and edit them in IFS Cloud Web. The feature list in the documentation (IFS Data Catalog features) has these entries:

  • register and scan the IFS data sources
  • pre-load IFS-specific metadata to enhance catalog value
  • classify data assets
  • search and browse the scanned assets in IFS Cloud Web
  • edit assets
  • create, import and apply glossary terms

In a project, the catalog is set up in four steps.

  1. Register the data sources. Registered sources must include the IFS Oracle database. Other sources, such as cloud storage or data lakes, can be added to the same catalog.
  2. Prepare the scan. Scan jobs run as background jobs under the service user IFSDCAT. If classifications exist in Purview, they have to be synchronised to IFS Data Catalog before the scan (Data Catalog prerequisites).
  3. Grant access. Two default permission sets cover the roles: FND_DCAT_ADMIN for catalog administrators and FND_DCAT_USER for catalog users.
  4. Enrich. After the scan, users refine the assets: they edit names and descriptions and add classifications and glossary terms.

The scan delivers technical metadata. The enrichment step is where business metadata enters the catalog, and it only happens if someone is assigned to do it.

3.How should IFS Cloud data be classified by sensitivity?

Classification marks data assets by type so that sensitive and personal data can be found. The catalog scan identifies and classifies data, and users can apply further classifications to an asset on its detail page. A classification has to be synchronised with Purview before it can be used: the documentation states that “Any classification must be in Synced status in order to be applied to an asset” (Data Catalog classifications).

The levels below are the scheme I use as a starting point. They are a proposal to adapt to your own data protection policy, not an IFS standard.

Sensitivity level Example IFS Cloud data Metadata action
Public Product catalogue, office addresses Tag as open data
Internal Internal operating procedures Assign a process owner
Confidential Trade margins, supplier contracts Restrictive tag and an access rule
Personal data Employee IDs, payroll data Personal data tag and a link to the processing purpose

A tag records sensitivity, and enforcement happens elsewhere. Which records a user can read through the APIs is decided by Custom Data Access Control, which configures access control lists based on the attributes of a projection entity. Which projections a user can reach at all is decided by permission sets, covered in IFS Cloud permission sets and segregation of duties. Clean-up and anonymisation of personal data are handled in the Personal Data Management page, where Customize Anonymization sets how a specific data type is anonymised (Customize Anonymization).

4.What does metadata change in daily work?

Metadata shortens the path from a question to the right data, and the two situations below are where the difference shows first. Both are illustrations, not client records.

  • A new report: a BI analyst needs a project profitability report. With a glossary term “project margin” linked to its source assets and its definition, the analyst searches the catalog and finds the tables and the calculation, instead of asking IT which columns to use.
  • An audit question: an auditor asks where personal data is stored. With personal data classifications maintained, the answer is a search for the classification in the catalog, not a hunt through screens and exports.

The general case for findable data is made in data discoverability: make data easy to find and trust.

5.Who should own metadata in an IFS Cloud company?

Metadata ownership is split: ERP administrators own the technical metadata and the scans, and data stewards in the business domains (finance, logistics, HR) own the business definitions and the accuracy of classifications in their areas.

The steward role fits the data mesh model, where the domain that creates the data owns it. Ownership and the controls that prevent data failures are described in ERP data failures and governance, and metadata as one of four data disciplines in ERP data quality in IFS Cloud. The people side, moving users from passive consumers to stewards, is the subject of building skills and mindsets for data mesh.

Setting up the catalog, the classification scheme and the steward roles for an IFS Cloud company is part of my services for IFS Cloud.

6.Frequently asked questions

What is the difference between a data catalog and metadata management?

A data catalog, such as IFS Data Catalog in IFS Cloud, is the tool where users search and browse data assets. Metadata management is the discipline around it: scanning sources, enriching assets with meaning, classifying them and assigning data stewards who keep the definitions correct.

Does IFS Cloud automatically classify data for GDPR?

IFS Data Catalog classifies data during a scan, and users can apply further classifications to assets manually, so GDPR classification in IFS Cloud should not be treated as fully automatic. A data steward should check and complete the personal data classifications. Clean-up and anonymisation of personal data are handled separately in Personal Data Management.

Who should be responsible for metadata management in an IFS Cloud company?

Responsibility for metadata in an IFS Cloud company is shared: ERP administrators manage technical metadata and the catalog scans, while data stewards from the business domains, such as finance or logistics, manage business definitions and the accuracy of classifications in their areas.

Which permission sets does IFS Data Catalog use?

IFS Data Catalog comes with two default permission sets: FND_DCAT_ADMIN for catalog administrators and FND_DCAT_USER for catalog users. Catalog scans run as background jobs under the service user IFSDCAT.

Does tagging a field as sensitive restrict access to it in IFS Cloud?

A sensitivity tag in IFS Data Catalog records what the data is, but it does not restrict access by itself. Access in IFS Cloud is enforced by permission sets, which grant access to projections, and by Custom Data Access Control, which applies access control lists to the records an API returns.

7.About the author

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

Selected clients from my IFS work: 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.

Test your metadata with one question

Ask a report author where the margin figure in last month’s management report comes from and who owns its definition. If the answer takes more than one search, the metadata is not written down yet.

Book a call about metadata in your IFS Cloud See services for IFS Cloud

×
Need Expert Guidance?
We've helped hundreds of businesses succeed. Get a free consultation to discuss your project requirements.
Get Free Consultation
17Years Experience
50Implementations
PRINCE2Certified
100%Success Rate

ROI Calculator

Calculate your return on investment

Input Values

€
€
€

Results

Annual Savings
€ 0
Payback Period
0 months
ROI
0%
Monthly Savings
€ 0

Get Detailed Report

Enter your details to receive a detailed ROI report.