5/18/2021 by Malay  Upadhyay Posted in SAP

man workingIn my last AI blog, 7 Tips To Make Your SAP Data Ready For AI, I discussed how you can become data ready to leverage AI solutions. The TUSCANE (Timely, Usable, Structured, Complete, Accurate, Neutral, Enough) model was designed to ensure that an AI tool or model in use has the right data available on SAP for accurate insights.

In this blog, we will take a step back to understand how you can ensure your data meets each of the conditions laid out in the TUSCANE model. In simpler words, we talk about the importance of a Data Dictionary.


Unleashing SAP's Power

A robust data dictionary is the secret sauce to unleashing SAP’s power because it ensures a firm grasp of organizational data to leverage not only advanced AI insights but even the most pedestrian day-to-day insights that inform the managerial strategy and its execution.

Let’s say you decide to write a book because you have a great story in mind. This story and other information supporting it are your data. However, only jotting them down on paper doesn’t create a book; that would be akin to simply taking notes.

That is the SAP equivalent of simply adding information to fields. A good book also needs you to plan the chapters, understand the link between different points of information, be clear on the core objective or message of your story, validate and verify the accuracy and availability of information, use the right sources for accurate information, plan the flow of the story in a way that would hook your target readers best, design a proper cover and get the right people to review it.

A data dictionary brings all this information and puts it in your control. Without it, you may successfully add your story to the pages but you won’t really unleash its true potential.


Coming Back to The TUSCANE Model of Data Readiness

To move beyond the book analogy, organizational data needs a dictionary also because of the dynamic nature of data flow, with new data coming in, old ones becoming redundant at times, and the very purpose or method of analysis of data evolving with time.

Now, the TUSCANE model of data readiness aims to ensure that the data available to an AI model is timely, usable, structured, complete, accurate, not biased, and enough. A quick note on the “structure” requirement: While advanced models can also work with unstructured data, it does not imply that we can feed the model garbage in the guise of an excel file or database, with incorrect information in incorrect fields or spread across multiple fields without a logical structure to it.

Coming back, while TUSCANE explains the state of data that a model should be able to feed on, how do we get our data on SAP to meet these conditions? This is where a data dictionary can help. So, what does it look like?


6 Steps to Create a Data Dictionary in Excel

A data dictionary contains your metadata. SAP is a good host for your database but can become severely complex with all information we add to it unless we find a way to track and manage all that information on SAP.

A data dictionary can be created on a simple Excel file for starters. It showcases the overall purpose of collecting data, the KPI’s that are central to the business and for which data is being collected, the lower level metrics down to individual pieces of data feeding them, the sources of that data, the gaps therein, the relationship between the data points, and the stakeholders responsible.

In doing so, it reveals points of risk as well as rewards that have not yet been leveraged. Let’s look at how to construct it on a simple Excel file to inform your SAP instance.


  1. The Overview: This sheet notes the business strategy, the business model, the customers, the industries served, the competitors, and the products in separate columns. The purpose of this sheet is to ensure your team has a good understanding of the business and its objectives.
  2. The Dictionary: The business objective directly informs what needs to be tracked and measured. The core dictionary sheet constitutes three layers of data: Process, KPI & Data.
  3. Process layer: Process refers to the business components that process the core KPIs, strategize, and execute accordingly to achieve business objectives. In this segment, the columns would depict the process name (Eg: operations, revenue management, cost management, etc), description, primary executive stakeholder, other stakeholders, process dependencies (Eg: operations may be dependent on contracts negotiated by revenue/sales management teams), and process data owners (Eg: the one who generates reports on a particular process performance).
  4. KPI layer: This is where we track the core and secondary measures for each process area, down to individual variables/fields of data. The columns would depict the KPI category, description, KPI, formula, inputs needed, input definitions, and KPI stakeholders. Each KPI can have corresponding information for its dependent secondary KPI’s, with each line item in separate rows.
  5. Data layer: This is where we boil things down to individual data fields that SAP holds or is supposed to hold. We track the data class, description, data source, the data source owner, frequency of data collection, any delays in data arrival/addition, data file type, file size, data accuracy level, & security level.
  6. The Stakeholders: At the end of the day, all points of information are being entered by individuals. SAP admins are responsible for identifying gaps and maintaining the database, but not necessarily sourcing data. The stakeholders needed to be tracked for each process, KPI and data follow a RACI framework, which lists for any line item:
    1. The person Responsible for ensuring accurate & updated information
    2. The person Accountable for it
    3. The person to be Consulted to ensure it
    4. The person to be kept Informed on it


A data dictionary can help SAP admins ensure that the individuals in RACI framework understand their roles in having the data on SAP adhere to the TUSCANE criteria. That not only makes the life of SAP admins easier but also ensures that organizations walk the talk en route to data, and by extension AI, readiness. 

Author Photo

Malay Upadhyay is the Chief Customer Experience Officer at SalesChoice, a North American AI firm, having trained 150+ executives on AI adoption & management and held executive sessions for CEOs and CHROs on AI strategy. He also drives the subject of AI Management as an Online Instructor, Board Advisor at the AI Directory, member of the European AI Alliance & Author of books on AI Management. You can reach him at linkedin.com/in/malayaupadhyay. If you would like to become an expert in leveraging AI solutions successfully on SAP for your organization, you can take his crash course on Artificial Intelligence Management on Michael Management.
More Blogs by Malay  Upadhyay:
person working on computer
7 Tips to Make Your SAP Data Ready for AI

A crucial factor behind AI functioning well is Data. A 2019 report mentioned that 96% of organizations ran into problems with AI and machine learning projects, primarily owing to data. In fact, a few ...