The more complex the SAP data flow, the less motivation there is for technical documentation. This blog article discusses the potential of technical SAP documentation, the risks of neglecting it and shows a practical approach on how to efficiently document SAP data flows across systems: With automation through SAP AddOn tools.

Complex SAP Data & Analytics Structures Complicate Documentation

SAC Stories rely on Datasphere Views, which in turn rely on Calculation Views in HANA or tables in S/4HANA, BW Queries, InfoProviders, DataSources… – modern SAP Data & Analytics architectures combine a variety of systems and technologies.

As complexity increases, the motivation and capacity to document a long and ramified data flow usually decreases – plus: New requirements take priority anyways and are simply implemented directly in the system. This practice, however, is not without risks – whether in terms of quality, compliance or development speed. And: It also wastes potential. The list of use cases in which technical SAP documentation is advantageous is long:

Advantages of Technical SAP Documentation

  • Fast knowledge transfer when new team members are onboarding or projects are handed over by external/internal staff
  • System and process analyses by mapping data origin, data transformation and data lineage
  • Accelerated search for errors in dashboards and debugging
  • Thorough change management / impact analyses
  • Audits & compliance requirements (proof of data flows, responsibilities, transformation logic, etc.)
  • Redesigns & system migrations (simplified analysis of legacy systems, optimal setup of structured target architecture, e.g. for BW on HANA → BW/4 or Datasphere migration)
  • Reusability & standardization (documented applications serve as templates for new developments)

Game Changer: Automated SAP Documentation

What many SAP developers don’t know: Thanks to automated SAP add-on tools, it has long been possible to benefit from the advantages of SAP documentation without wasting time. Integrated via function modules, Docu Performer documents entire data flows across systems at the touch of a button.

The SAP documentation tool offers the following possibilities:

  • Automated documentation of entire data flows or individual objects as well as any comments created for them
  • Export of a structured, searchable document with a directory (Word, Excel, PowerPoint, PDF or HTML) and optional upload to Confluence
  • Supported technologies for documentation: SAP BW – SAP BW/4HANA – SAP Business Objects – SAP Analytics Cloud – SAP Datasphere – SAP ECC – SAP S/4HANA

Here is an example of how to document data flow of a SAC story from a purchasing dashboard:

Document SAC Story

Object Selection and Variants:

In the settings, you can first define whether individual or all objects of the story should be documented (“Document Entire Dataflow”, available with version 24.2) and whether existing comments on the objects should also be documented. You can also specify the level of detail and the language of the documentation to suit different target groups.

Document SAP Dataflow

Export:

As export variants, you can select a desired document format (Word, Excel, PowerPoint, PDF, HTML) and specify whether the document should be uploaded centrally available to Confluence.

Document SAP Dataflow

Final Document:

The result is a detailed documentation in which all objects of the data flow are documented – searchable and clearly structured. Here you can see the information content of the SAP documentation for yourself in the exported PDF.

Automatisierte SAP Dokumentation

Schedulability:

Another exciting feature is automated updating. Documentation can be automated using scheduled jobs so that up-to-date information is available on a daily basis, for example.

Automated SAP Documentation

Conclusion: SAP Documentation Must Grow with the Complexity of the System

Manual documentation is a thing of the past – in modern SAP Data & Analytics architectures, automated documentation is not a luxury, but a decisive factor for efficiency, quality and scalability. Those who rely on smart solutions at an early stage create a resilient basis for agile further development – without having to constantly start from scratch.

You can easily try out how the automated documentation of your own data flows feels in practice: With a free trial version via our website.

Collaboration is a crucial driver of success, especially in complex domains like the Business Intelligence (BI) of a corporation. That’s because collaboration allows pooling the knowledge and skills of employees and work more efficiently together. That way, the BI team can respond to changes more quickly, act more flexibly, and ultimately positively influence their corporation’s outcome and competitiveness.

Now, what requires collaboration in a BI work context, exactly? The everyday tasks and decisions of any BI employee involve charts and reports. Most BI departments use high-end software solutions to make them accessible and offer a deeper insight. Yet, many face low use and acceptance among their teams. Collaborative BI boosts the acceptance of BI software and simultaneously changes how we handle data analysis and decision-making – by promoting teamwork and combining everyone’s knowledge. Here’s how:

 

1. Understanding Collaborative BI

In order to get a deeper understanding of Collaborative BI, let’s have a look at the ‘old’ way, before this trend: Traditional Business Intelligence follows a centralized, IT-driven model where a specialized team of analysts produces static, historical reports for decision-makers, often leading to extended turnaround times for fresh insights.

Now, on the other hand, Collaborative BI enables a wider array of users throughout the organization to interact with dynamic, real-time data using self-service tools that diminish reliance on IT. This method and its corresponding tools promote improved collaboration through functionalities such as report sharing, commenting, and annotating, while emphasizing both real-time and predictive analytics to facilitate proactive decision-making.

traditional Business Intelligence versus Collaborative Business Intelligence

Traditional BI versus Collaborative BI

 

Key Objectives of Implementing Collaborative BI

The primary aim of Collaborative BI is to enhance problem-solving and decision-making processes. The following aspects are fundamental to achieving this overarching goal:

Decentralized Analysis

By engaging and empowering a diverse range of users with various roles, backgrounds, and skill sets, organizations can tap into a multitude of perspectives and collective intelligence. This approach helps in mitigating bottlenecks that are traditionally linked to centralized teams, thereby expediting the process of problem-solving. Engaging users from diverse departments and backgrounds fosters a rich array of viewpoints and insights, ultimately resulting in more thorough and inventive solutions.

Improved Dashboard & Report Design

Users with diverse roles, backgrounds, and skill levels require customized dashboards and reports that align with their specific needs. By fostering the sharing of ideas and knowledge among these users, organizations can create tailored dashboards and reports that effectively meet the varied requirements of their audience. Moreover, real-time access to data enables users to quickly identify and address issues as they arise. Interactive dashboards and reports allow users to drill down into data, uncovering root causes and patterns more quickly than with static reports.

Collaboration Tools & Services

Collaborative BI tools provide features such as commenting, sharing, and discussion threads facilitate immediate communication and collaboration among team members, allowing for faster consensus and action. Seamless real-time data sharing across the organization ensures that all relevant stakeholders have access to the same information, fostering a unified approach to decision making. Self-service BI tools enable users to generate their own reports and queries without waiting for IT support, accelerating the decision-making process.

 

2. Challenges in Implementing Collaborative BI

The implementation of Collaborative BI presents a unique set of challenges, which can differ based on the organization’s initial position and current circumstances. Overcoming these challenges will ensure the success of your Collaborative BI implementation.

  • Tool Elasticity
  • Data Privacy, Security and Data Ownership
  • Metadata
  • Data Integration
  • Communication between Employees

shutterstock 1060077944 bluetelligence GmbH What Is Collaborative BI & How Does It Enhance The Efficiency and Acceptance of Your Business Intelligence Solutions?

 

Tool Elasticity

Tool elasticity, meaning the ability of BI tools to scale and adapt to varying user needs and workloads, poses a challenge for implementing collaborative BI as well: Ensuring scalability without performance degradation, integrating with existing systems, managing variable costs, and facilitating user adoption across all skill levels require significant effort. Additionally, data security concerns, especially with cloud-based solutions, performance optimization, maintaining consistent and reliable access, and balancing customization with stability complicate the process. These factors make it difficult for organizations to effectively implement and maintain elastic BI tools for collaborative efforts.

Data Privacy, Security & Data Ownership

Data privacy, security, and data ownership of course pose challenges when implementing collaborative BI: Handling sensitive information, managing authorized usage, ensuring compliance with regulations like GDPR and HIPAA, and managing the increased risk of data breaches is complex and critical. Additionally, implementing robust security measures and secure infrastructure require significant investment and expertise. Continuous user training and awareness programs are essential to minimize human errors that could compromise data security, further complicating the implementation of collaborative BI.

Metadata

Metadata is extremely helpful in the context of collaborative BI because it answers the questions of data origin, usage. In traditional BI, these questions are asked by business departments and answered by IT. In collaborative BI, business users find answers themselves. This, however, presents the challenge of ensuring data is correctly understood by less tech-savvy users and utilized across the organization – e.g. by comprehensive training. Additionally, metadata is only of use for correct analyses when it is maintained up-to-date – this involves a significant effort and constant documentation of data sources, definitions, structures, and usage. Discrepancies in metadata can lead to misinterpretations and inconsistencies, complicating data sharing and collaboration.

Data Integration

Data integration is particularly challenging and crucial for Collaborative BI: It involves consolidating different data sources with varying formats, structures, and quality levels into a unified system that all users can access and analyze. It is essential for enabling real-time, collaborative decision-making, but it requires sophisticated tools and processes for data extraction, transformation, and loading (ETL). Effective data integration also necessitates collaboration between IT and business units to align on data definitions and standards, a challenging but essential task to ensure that all users are working with the same accurate and consistent data.

Communication between Employees

Communication between employees is the heart of the whole matter of Collaborative BI – and it is a challenge itself: Due to the varying levels of (technical and business) expertise and understanding of data, differences in language, priorities, and perspectives, misunderstandings are bound to occur. They can lead to incorrect data interpretations, flawed analyses, and poor decision-making. Additionally, coordinating across departments and ensuring that everyone is aligned on BI objectives, processes, and tools necessitates continuous effort. Implementing these channels and fostering a culture of open communication requires ongoing commitment from leadership to break down silos and encourage active participation from all employees.

 

3. Recommendations for Improving Collaboration in Your Existing BI Landscape

Collaborative BI may pose its challenges, but with the following recommendations, you will eventually overcome and even outweigh them with its striking benefits:

  • Self-Service & Data Visualization
  • Data Quality & Data Governance
  • Metadata Management & Data Cataloging
  • Culture & Communication

for improving collaboration in your existing BI landscape

Self-Service & Data Visualization

Self-service and data visualization are key when it comes to Collaborative BI – both aspects take the weight of the IT departments’ shoulders and make data accessible and understandable to all departments. They materialize in the form of

  • intuitive, user-friendly tools that empower employees of all skill levels…
  • …to access, analyze, and visualize data independently, fostering a data-driven culture across the organization
  • comprehensive training to ensure the usage and efficiency of these tools
  • Enhancing data visualization with customizability allows users to tailor dashboards to their specific needs and easily share findings with colleagues
  • Ensuring robust data governance and real-time data access will further enhance the reliability and relevance of the insights generated.

Encouraging feedback and continuous improvement of these tools based on user experience helps to keep them aligned with the evolving needs of the organization.

Data Quality & Data Governance

A second big necessity in the process of introducing Collaborative BI is improving data quality. It can be achieved by implementing strong data governance practices:

Establishing

  • standardized data entry protocols,
  • regular data cleaning
  • validation processes
  • and clear data ownership that ensures accountability among all stakeholders

is essential to maintain high-quality data.

Advanced data management tools even automate error detection and correction and can significantly reduce inconsistencies. Ultimately, the culture of transparency with Collaborative BI fosters an open communication about data issues and collective efforts to resolve them, even if done manually.

Metadata Management & Data Cataloging

Finally, metadata management and data cataloging are an essential aspect to facilitate Collaborative BI. Ideally, you can even combine the two of them: Via APIs or dedicated metadata repositories, it is possible to include SAP or Power BI metadata into or next to your Data Catalog.

When implementing a data catalog, make sure that it

  • serves as a centralized access to every BI employee (single point of truth)
  • provides an intuitive interface and displays data in straight-forward way, so that users with varying backgrounds are able to comprehend the information
  • includes metadata like the usage, source and lineage of data in order to efficiently answer questions that arise in the context of reporting
  • displays up-to-date metadata in order to make the single point of truth really true – and thus, boost the usage of the Data Catalog

Continuous training and support for employees on the importance and use of metadata further enhance their ability to contribute to and benefit from the collaborative BI efforts, ultimately leading to more informed and effective decision-making.

Culture & Communication

Last, but not least, people make a company. In order to foster the new collaborative culture, management should:

  • prioritize transparency and actively encourage the sharing of information and insights across all levels of the organization.
  • Implement regular training sessions and workshops to enhance data literacy, ensuring all employees feel confident in their ability to contribute to BI initiatives
  • Recognize and reward teamwork and collective problem-solving
  • additionally, the physical aspect of creating dedicated collaboration spaces will streamline communication and data sharing, making it easier for teams to work together effectively
 

4. Collaborative BI Tools: Data Catalog meets Metadata Repository

As described above, user-friendly Data Catalogs and Metadata Repositories are two crucial tools to enhance Collaborative BI in your company. As a BI software development company of 16 years, bluetelligence has developed a combination of both: Our Data Catalog “Enterprise Glossary” includes business information as well as automatically synchronized metadata of all connected SAP and Power BI systems. It checks all the boxes of driving Collaborative BI by

  • providing a central access to all key figures and reports in the company
  • including information for all knowledge levels: business definitions as well as technical metadata (data source, data lineage, related key figures, etc) in an understandable way
  • offering a user-friendly search and intuitive interface
  • automatically syncing all connected SAP & Power BI systems for up-to-date information
  • providing communication features for remarks and discussions
  • being able to use standard templates or customize it to your needs entirely
 
 
Glossary Entry Data Catalog

Glossary Entry Data Catalog

image 1 bluetelligence GmbH What Is Collaborative BI & How Does It Enhance The Efficiency and Acceptance of Your Business Intelligence Solutions?

Data Lineage in the Data Catalog


 

Overall, bluetelligence empowers your company to leverage metadata more effectively, driving innovation and improving business outcomes through enhanced collaboration. Read more about our data catalog, the Enterprise Glossary, on www.enterprise-glossary.de/en.

Should you already utilize a Data Catalog but are looking to include SAP or Power BI metadata, our API serves this purpose exactly. In this case, head to www.bluetelligence.de/en/metadata-api.

Abstract — As software developers in the area of SAP Business & Analytics, we repeatedly encounter “time wasters”, i.e. everyday Business Intelligence processes that could be approached much more effiecient. This article deals with the dependency between business departments that work with dashboards and reports and IT, which in turn processes tickets when errors occur. As a solution, it discusses the BI Self Service concept, which can help to speed up these processes and thus save costs, time and nerves. Specifically, it involves utilizing data cataloging to provide business departments with insights into the metadata of their key figures and reports – thus relieving the burden on IT and making business processes more efficient.

The Use Case: Usually an Error in a Dashboard

We all know how it goes: Business dashboards are supposed to provide clarity – but if they don’t display the correct values or show error messages, the opposite is of course the case. This is particularly bad if the department notices the error shortly before a meeting in which the dashboard is needed.

The error often stems from one of the key figures used in the SAP system – especially if the key figure is made up of several other key figures in the system. We call this a ‘nested key figure’. Another term that is often used is the ‘calculated key figure’.

BI Self-Service bei SAP-Dashboards

Calculated Key Figures Have Their Pitfalls

The key figure ‘Expected Incoming Orders’ in a sales dashboard can, for example, be made up of four to six other, equally nested key figures – for example, the sales probability, the open offers, and so on.

Finding out whether there is an error in one of the many key figures in the SAP system takes a hell of a lot of time.

What exactly is taking so long? As long as the department can only detect the error in the dashboard, but cannot see which other underlying key figures the incorrectly displayed key figure contains, it can only submit an unspecific support ticket to IT. The IT then have to search for errors and investigate the entire background of the key figure in the SAP system. And since IT is known to be swamped with tickets, the problem will not be solved in time before the meeting (or the next one).

As promised, this article is not only about problems, but also about solutions – and the solution in this case is BI Self-Service – more precisely, a Data Catalog. And a driver tree. Let us explain, why.

The Solution: SAP Metadata in Any Business Department's Data Catalog

In order to provide business departments with more empowerment with their dashboards and relieve IT of work in equal measure, it is advisable to use a data catalog that also provides an overview of SAP – the prerequisite, however, is that the information displayed is prepared in a way that is understandable for business departments.

Our Data Catalog, the Enterprise Glossary creates glossary entries for each key figure of synchronized SAP systems, in which both the technical definition and its calculation with all involved key figures are mapped. With the latest Enterprise Glossary function, the “driver tree”, the formula is even displayed graphically in a network graphic, providing an easy-to-understand overview of all levels of the nested key figure (see GIF).

This means that specialist departments without access to SAP backend can immediately see which key figures are involved in the dashboard. Since they can comprehend the mathematical calculation of the key figure, they will most likely already be able to tell IT the specific key figure that is displayed incorrectly in SAP. IT then will be able to rectify the problem in the backend in a much more targeted manner – and much more quickly. The Data Catalog thus acts as a link between business departments and IT – and makes life a little easier for everyone. Of course, the function is also useful in everyday life to understand how certain values in dashboards come about in the first place.

Conclusion: The use of a data catalog with a real-time connection to the SAP systems creates a self-service point that enables more efficient collaboration between specialist departments and IT – be it when searching for errors in dashboards, defining key figures or answering questions about existing reports.

Plastic waste in the world’s oceans is a huge problem. With his Ocean Cleanup Project, the young Dutchman Boyan Slat has set himself the task of actively tackling this problem. We are impressed by his determination and innovative strength and have been supporting the project since last year. So it’s high time we told you about it.

Five trillion pieces of plastic are currently floating in the ocean. However this figure can be quantified, it sounds frightening. In the long term, the pieces of plastic break down into microplastics and cause fatal damage to our ecosystem. In addition to marine life, humans are also affected along the food chain.

Boyan Slat Ocean Cleanup Project

The question remains as to what to do about it. Collecting and transporting each piece individually would be neither affordable nor time-consuming. For many, however, simply giving up on the oceans is – fortunately – not an option.

Dutchman Boyan Slat has decided not to give in helplessly and take action instead. He made this decision at the age of just 17. Two years later, in 2013, he founded the Ocean Cleanup Project. With a team of up to 100 researchers and engineers, he has continued to tinker and develop an ingenious system.

The targeted technology is essentially based on plastic tubes arranged in a U-shape. Held to the seabed by weights, these tubes float on the sea surface and bundle the waste in the middle with the help of natural ocean currents, where it can be skimmed off after a while. The sea collects its own waste, so to speak.

You are currently viewing a placeholder content from YouTube. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.

More Information

After the first prototype was successfully deployed, the first major marine clean-up mission with “System 001” – affectionately known as “Wilson” – was launched in 2018. It began with the Great Pacific Garbage Patch between Hawaii and California, the largest of the five large plastic waste fields. It is estimated to be 1.6 million square kilometers in size. The goal: to eliminate 50 percent of the Great Pacific Garbage Patch in just five years. To this end, continuous improvements have been made to the system since the start of the mission in order to make it more effective.

When we at bluetelligence first heard about the Ocean Cleanup Project, we were impressed by Boyan Slat’s tenacity, his passion and not least his visionary solution. It was therefore an easy decision to donate €5,000 to the Ocean Cleanup Project in spring 2018. Since then, we have also continued to support the project with €10 per employee per month.

Boyan Slat acts sustainably and wants to leave the world better than he found it. We at bluetelligence can identify with this. Long-term, resource-saving solutions and persistence in implementing visions are also important to us in product development. In addition, just like the well-known African proverb, we believe that many small people in many small places doing many small things can change the face of the world. This starts, for example, with the switch to glass bottles in the office kitchen and continues with electric company cars and donations to great projects like this one. Of course, we continue to be inspired in this respect and hope to inspire others to contribute to the preservation of our environment.

If you would also like to donate, you can do so directly on the Ocean Cleanup Project website. Please contact us if you have any questions.