Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Product Description zapAnalytics

Product description, license conditions and cooperation obligations

1. Introduction

zapAnalytics is a web application for analyzing SAP data, utilized by zapAgents Wolfgang, Werner and Wickie. The software runs within zapHome in the customer's own IT environment. All data remains within the customer's infrastructure at all times, ensuring full control and maximum security.

zapliance provides the business logic in form of a Content Bundle (typically .zip-file), which the customer uploads into the software (Analytics as a Service).

The core functions of zapAnalytics are:

  1. Data extraction from SAP system (“Download plan”),
  2. Data processing using predefined analyses (“Processing plan”),
  3. Preparation of results for the evaluation of the data and integration into third-party software (“Result plan”).

Both one-off analyses and recurring automated processing runs (Continuous Monitoring) can be carried out, which include data extraction, processing, result creation, and (optionally) forwarding.

2. Scope

This product description defines:

  • the purpose and functional scope of generic zapAnalytics features
  • the general license conditions for the use of zapAnalytics
  • general customer cooperation obligations
  • the features that can be activated through Content Bundles
  • detailed feature descriptions
  • feature-specific customer cooperation obligations

This product description does not define:

  • download scope, processing scope, or result scope of individual Content Bundles
  • features or requirements of zapHome
  • capabilities or requirements of zapAgents or Agent Teams
  • Customer Success services
  • Training and Consulting services
  • Custom Development services

The analytical scope activated by a specific Content Bundle is defined in the applicable Content Bundle Description.

3. License Conditions

The customer acquires a license for the creation and use of a customized One-off or Continuous project in zapAnalytics, with the following license components:

  • Project Type: The project type determines whether a project in zapAnalytics is a one-off project or a continuous service.
    • One-off projects enable the customer to extract data once, process data once, and generate a result once.
    • Continuous mode enables the customer to extract, process, and generate results multiple times.
  • Service Start Date: The service start date regulates when project processing can begin. If the offer includes a restriction on the service start date, this restriction applies to the specified period. 
    • One-off: The service period for one-off projects begins on the service start date and ends on the service end date or after the specified service period has expired.
    • Continuous: The service period for Continuous mode begins on the service start date and ends upon the effective date of termination.
  • Service Period: In Continuous mode, the service period defines the subscription and billing period during which continuous services can be processed. The service period automatically extends for another term unless terminated in writing.
  • Minimum Term: If a minimum termis defined in the offer, termination is only possible at the end of this period. The service period is effective from the service start date.
  • Content Bundles: Content Bundles include contractually agreed licensing conditions and define the download plan, processing plan, and result plan. If the customer-specific offer does not include specific plans, the details of the specified Content Bundle apply.
    • Download Plan: If the offer restricts download plans, the data scope applies to the agreed-upon download plans of our offer (e.g. company codes, fiscal years).
    • Processing Plan: If the offer restricts processing plans, the scope applies to the agreed-upon processing plans of our offer.
    • Result Plan: If the offer restricts result plans, the scope applies to the agreed-upon result plans of our offer.
  • Content Bundle Updates: The number of Content Bundle updates determines the maximum number of Content Bundles configured specifically for the customer within a service period and delivered to the customer.
  • Control Set Changes: In Continuous mode, the number of Control Set changes determines the maximum number of changes to the Control Set configured specifically for the customer within a service period and delivered to the customer as Content Bundles.
  • SAP Clients: If the offer provides a restriction on the number of SAP clients, this restriction applies to the specified clients within an SAP system.
  • SAP Company Codes: If the offer provides a restriction on company codes, this restriction applies to the specified company codes within an SAP client.
  • Fiscal Years: If the offer provides a restriction on fiscal years, this restriction applies to the specified fiscal years within an SAP client.
  • Project Frequency: In Continuous mode, the project frequency regulates the intervals at which downloads, data processing, and result generation may be automatically executed via batch run. If the offer provides a frequency restriction, the listed frequency is considered the minimum.

4. General Cooperation Obligations

4.1 General prerequisites for using zapAnalytics

  • Provision of a server or virtual machine (VM) to serve as the host environment for the contractually agreed zapHome variant.
  • Deployed and operational zapHome setup.
  • Administrator rights for installing zapAnalytics on a virtual machine or server.
  • The customer is responsible for security requirements and measures for operating the system. Security requirements for the server and system environment should meet the SAP data security standard.
  • The customer ensures the logical and physical security of the IT infrastructure on which the digital products, the data generated by digital products, and/or zapAnalytics operate or where the digital products and data are transported or transferred. The customer is guided by their already applied measures concerning the SAP productive system.
  • Additionally, the customer ensures the interface security between the SAP systems, zapAnalytics, and the web browser used for access. zapliance GmbH is not liable, subject to the provisions in section VII of the General Terms and Conditions, for damages due to lack of access protection, lack of security measures, insufficient archiving, and lack of encryption of the customer’s data.
  • The customer ensures that (network) access to the customer’s SAP systems – or direct use of zapAnalytics on the customer’s systems – and possibly on an SAP test system (with up-to-date original data) is enabled for zapAnalytics. The customer is responsible for taking appropriate measures to prevent damage (e.g., virus infestation, system crash) due to access or software use on the customer’s systems.
  • The customer is responsible for complying with all legal (especially data protection and labor law) regulations during software use, including the data protection officer and works council if necessary.

4.2 Technical requirements

To operate zapAnalytics, the contractually agreed zapHome instance must be deployed and operational.

A Linux-based virtual machine (VM) or server that meets the specified requirements must be prepared as the host environment for Docker.

The requirements, including recommended hardware and software configurations, are specified in this article: Setup Guide Virtual Machine / Server

We recommend Docker as the container management tool. For other deployment scenarios, please refer to this article.

5. Generic zapAnalytics Features

This is a list of all generic zapAnalytics features that can be used without uploading a Content Bundle.

  • Web Application
    • A central installation that is hosted on-premises within the customer's IT environment
    • Deployment as a Docker container or via Kubernetes is possible
    • User access via web browser
    • Multilingual support: German and English
  • Security
    • A role/permissions concept is integrated into the application, allowing for controlled access.
    • Password-protected installation
    • Encrypted system database
    • Project database with password encryption
  • User Creation
    • Creation and management of user accounts for accessing zapAnalytics.
  • User Login (with optional MFA)
    • Authentication of users via login credentials. Optional Multi-Factor Authentication (MFA) can be activated for additional security.
  • Password Reset on Login Screen
    • Password reset directly from the login screen in case of forgotten credentials.
  • Change of Login Credentials (E-Mail & Password)
    • Change of the e-mail address and password used for user authentication.
  • E-Mail Notifications for Project Status
    • Automatic e-mail notifications regarding project status changes, completed activities, and processing errors.
  • Application Log Download
    • Download of application log files for troubleshooting, support, and audit purposes.
  • Content Bundle Upload
    • Upload of Content Bundles (typically .zip file) provided by zapliance. Uploading a Content Bundle activates the included project configuration, workspace, licenses, and features.

6. zapAnalytics Features Activated by Content Bundles

6.1 Content Bundles

A Content Bundle consists of a set of download, processing, and result plans, as well as a project template, an organization template, and all necessary licenses.

A Content Bundle is provided by zapliance (typically as a .zip file) and can be uploaded by the customer into zapAnalytics. The project features become available to the customer, once the project is activated.

  • Download plans
    • Download plans define the data scope to be extracted from SAP systems.
    • The scope definition is done in consultation with zapliance. Download plans are created by zapliance and provided specifically for the customer in a Content Bundle.
  • Processing plans
    • Processing plans determine the automated processing of extracted data in zapAnalytics according to the agreed product.
    • Processing plans are created by zapliance and provided specifically for the customer in a Content Bundle.
  • Result plans
    • Result plans define the output format of the project results.
    • Typical output formats include CSV, Excel, database files, REST API, Parquet, pbix, pbit, or interfaces to external tools like Microsoft SharePoint.
    • Result plans are created by zapliance and provided specifically for the customer in a Content Bundle.
    • The results of result plans are made available via zapAnalytics, for example, through web download, database access, or interface.

6.2 Available Features by Agent Team

This is a list of all zapAnalytics features activated by Content Bundles and their availability per Agent Team.

The features activated in a specific setup depend on the selected Content Bundle. See the applicaple Content Bundle Description for detailed information on the features activated by each Content Bundle.

Feature

Wolfgang

Werner

Wolfgang + Wilma

Werner + Wilma

Wickie + Wilma

Management

 

 

 

 

 

Workspace Management¹

✅

✅

✅

✅

✅

Workspace API Management²

✅

✅

✅

✅

✅

Workspace User Management³

✅

✅

✅

✅

✅

Project Creation⁴

✅

✅

✅

✅

✅

Project Management⁵

✅

✅

✅

✅

✅

Project Scheduler⁶

❌

✅

❌

✅

✅

Database Management⁷

✅

✅

✅

✅

✅

SAP Connection Management⁸

✅

✅

✅

✅

✅

Data Extraction

 

 

 

 

 

One-off Standard SAP Data Extraction (Standard Download Plan)⁹

✅

✅

✅

✅

✅

Continuous Standard SAP Data Extraction (Standard Download Plan)¹⁰

❌

✅

❌

✅

✅

Custom SAP Data Extraction (Custom Download Plan)¹¹

❌

✅*

❌

✅*

✅*

Batched SAP Attachment Download¹²

❌

✅

❌

✅

✅

Data Processing

 

 

 

 

 

Process Labeling¹³

✅

✅

✅

✅

✅

One-off Standard Indicator Processing (Standard Processing Plan)¹⁴

✅

✅

✅

✅

✅

Continuous Standard Indicator Processing (Standard Processing Plan)¹⁵

❌

✅

❌

✅

✅

Custom Indicator Processing (Custom Processing Plan)¹⁶

❌

✅*

❌

✅*

✅*

ML Algorithm-based Processing¹⁷

❌

✅

❌

✅

✅

Batched SAP Data Processing¹⁸

✅

✅

✅

✅

✅

Batched LLM Attachment Analysis¹⁹

❌

✅

❌

✅

✅

Output

 

 

 

 

 

One-off Standard Outputs (Standard Result Plan)²⁰

✅

✅

✅

✅

✅

Continuous Standard Outputs (Standard Result Plan)²¹

❌

✅

❌

✅

✅

Custom Outputs (Custom Result Plan)²²

❌

✅*

❌

✅*

✅*

Power BI Templates (.pbit)²³

✅

✅

✅

✅

✅

Source Files for Power BI Dashboards (.parquet)²⁴

✅

✅

✅

✅

✅

Excel File per Indicator with Marked SAP Documents²⁵

✅

✅

✅

✅

✅

Pseudonymization of Results²⁶

✅

✅

✅

✅

✅

Interfaces

 

 

 

 

 

Link to SAP Documents (Web GUI/Fiori) in Power BI Dashboards²⁷

✅

✅

✅

✅

✅

Wilma Link in Power BI Dashboards²⁸

❌

❌

✅

✅

✅

REST API Access²⁹

❌

✅*

❌

✅*

✅*

MCP Server Creation & Management³⁰

❌

❌

✅

✅

✅

Result Transfer to MCP Server³¹

❌

❌

✅

✅

✅

Web Search (via Azure OpenAI)³²

❌

❌

❌

❌

✅

VAT ID Validation via Endpoint Connection (BZSt & VIESS)³³

❌

❌

❌

❌

✅

Legend:

✅ = Feature available for this Agent Team

❌ = Feature not available for this Agent Team

✅* = Custom feature available for this Agent Team as part of a Custom Content Bundle. Only activated if explicitly included in the commercial agreement. May require a custom development project that is charged separately.

Note: In case of Custom Content Bundles, the RFC authorizations, SAP tables and indicators detailed below do not necessarily apply. The applicable scope will be agreed separately as part of the Custom Content Bundle development.

6.3 Feature Descriptions and Cooperation Obligations

 

1. Workspace Management

Enables creation and deletion of project workspaces within zapAnalytics. Uploading the Content Bundle (.zip file) automatically creates a workspace containing the project.

 

2. Workspace API Management

Enables management of workspace-specific integration settings, including the zapliance API key, Azure Document Intelligence endpoint and Azure Document Intelligence API key.

 

3. Workspace User Management

Enables the assignment and removal of existing users within a workspace to control access to the project and its results.

 

4. Project Creation

Enables creation of a project by uploading the Content Bundle (.zip file) into zapAnalytics. Projects organize and control data extraction, processing, and preparation.

Cooperation Obligations
  • end user needs access to Content Bundle (.zip file)
  • end user needs access to zapAnalytics application (via web browser)


5. Project Management

Enables management of project-specific settings, including the project name, result language and project lifecycle. Projects can be deleted from the user interface while retaining or deleting the associated project database. The projects and results are separated at least by SAP client.

 

6. Project Scheduler

Enables scheduled execution of project activities, including data extraction, data processing and result creation according to a predefined schedule. The projects and results are separated at least by SAP client.

 

7. Database Management

The zapAnalytics PostgreSQL database stores data on data extraction, processing, and forwarding. For the creation of a project, existing zapAnalytics databases or a new database can be selected.

Users can store the connection data for this database in zapAnalytics. Databases and database connections can be password-protected.

Cooperation Obligations
  • ensure ability to use a PostgreSQL database

 

8. SAP Connection Management

For data extraction, saved connection data can be selected, or new connection data can be entered to create a new SAP connection. An SAP data extraction occurs either via the SAP message server or application server using read-only RFC (Remote Function Call).

Cooperation Obligations
  • provide connection data to relevat SAP system (message server or application server)

 

9. One-off Standard SAP Data Extraction (Standard Download Plan)

Enables one-off extraction of SAP for a specific project within the data scope defined in the download plan activated by the selected Content Bundle.

The data scope of each Content Bundle is specific in the respective Content Bundle Description.

Important: The recommended maximum project size is 100 million BSEG rows. Larger datasets may lead to Power BI performance and memory limitations, affecting dashboard usability and responsiveness. Reliable operation above this threshold cannot be guaranteed. 

Cooperation Obligations
  • ensure availability and accessibility of the following SAP function modules:
    • BBP_RFC_READ_TABLE
    • RFC_READ_TABLE
  • set up SAP user with RFC access rights to the function modules and SAP tables listed in this article: Setup Guide SAP
  • provide end user with RFC user credentials to set up SAP connection within zapAnalytics
  • provide the SAP clients, company codes, fiscal years, and organizational scope to be analyzed
  • ensure the availability and accessibility of the required SAP tables throughout project execution
  • ensure stable network connection to the SAP system for the duration of data and document extraction
  • communicate any SAP-side changes that may affect extraction activities


10. Continuous Standard SAP Data Extraction (Standard Download Plan)

Enables continuous extraction of SAP data within the data scope defined in the Download Plan activated by the Content Bundle. The cooperation obligations (especially the necessary RFC access rights) 

Important: The recommended maximum project size is 100 million BSEG rows. Larger datasets may lead to Power BI performance and memory limitations, affecting dashboard usability and responsiveness. Reliable operation above this threshold cannot be guaranteed. 

Cooperation Obligations
  • ensure availability and accessibility of the necessary SAP function modules discussed individually with zapliance depending on the selected data scope
  • set up SAP user with RFC access rights to the function modules and SAP tables discussed individually with zapliance depending on the selected data scope
  • provide end user with RFC user credentials to set up SAP connection within zapAnalytics
  • provide the SAP clients, company codes, fiscal years, and organizational scope to be analyzed
  • ensure the availability and accessibility of the required SAP tables throughout project execution
  • ensure stable network connection to the SAP system for the duration of data and document extraction
  • communicate any SAP-side changes that may affect extraction activities


11. Custom SAP Data Extraction (Custom Download Plan)

Enables extraction of customer-specific SAP data beyond the standard Download Plan activated by the Content Bundle.

Important: The recommended maximum project size is 100 million BSEG rows. Larger datasets may lead to Power BI performance and memory limitations, affecting dashboard usability and responsiveness. Reliable operation above this threshold cannot be guaranteed. 

Cooperation Obligations
  • define the additional data requirements
  • identify the required SAP objects, tables, and fields
  • validate the requested scope before implementation
  • ensure availability and accessibility of the necessary SAP function modules discussed individually with zapliance depending on the selected data scope
  • set up SAP user with RFC access rights to the function modules and SAP tables discussed individually with zapliance depending on the selected data scope
  • provide end user with RFC user credentials to set up SAP connection within zapAnalytics
  • provide the SAP clients, company codes, fiscal years, and organizational scope to be analyzed
  • ensure the availability and accessibility of the required SAP tables throughout project execution
  • ensure stable network connection to the SAP system for the duration of data and document extraction
  • communicate any SAP-side changes that may affect extraction activities

 

12. Batched SAP Attachment Download

Enables batch download of SAP attachments and makes the downloaded files available for subsequent processing and analysis.

Cooperation Obligations
  • ensure availability of extracted attachments
  • configure RFC user with additional access rights (GOS: SO_DOCUMENT_READ_API1, ArchiveLink: ALINK_RFC_TABLE_GET)
  • check all required RFC user access rights and SAP connection requirements defined in the SAP setup documentation


13. Process Labeling

Enables classification and assignment of extracted SAP documents and transactions to business processes.

 

14. One-off Standard Indicator Processing (Standard Processing Plan)

Executes data processing with the standard indicator scope defined in the processing plan activated by the Content Bundle.

The indicator scope of each Content Bundle is specific in the respective Content Bundle Description.

 

15. Continuous Standard Indicator Processing (Standard Processing Plan)

Executes continuous data processing using the standard indicator scope defined in the Processing Plan activated by the Content Bundle.

 

16. Custom Indicator Processing (Custom Processing Plan)

Executes data processing using customer-specific indicators and processing logic.

Cooperation Obligations
  • provide business requirements for custom indicators
  • validate indicator specifications
  • validate the resulting analytical outputs


17. ML Algorithm-based Processing

Executes zapliance proprietary machine-learning algorithms to identify predefined analytical patterns within the processed data.

 

18. Batched SAP Data Processing

Enables automated processing of all extracted SAP data according to the Processing Plan activated by the Content Bundle.

Cooperation Obligations
  • ensure availability of extracted source data
  • ensure sufficient system resources for processing
  • communicate known data-quality issues affecting processing results


19. Batched LLM Attachment Analysis

Enables automated analysis of downloaded SAP attachments using a customer-provided Large Language Model (Azure OpenAI).

Cooperation Obligations
20. One-off Standard Outputs (Standard Result Plan)

Provides the standard outputs defined in the Result Plan activated by the Content Bundle.

The output scope of each Content Bundle is specific in the respective Content Bundle Description.

Important: The recommended maximum project size is 100 million BSEG rows. Larger datasets may lead to Power BI performance and memory limitations, affecting dashboard usability and responsiveness. Reliable operation above this threshold cannot be guaranteed. 

Cooperation Obligations
  • validate the relevance of analytical findings
  • review and interpret generated results
  • validate that outputs meet the intended project objectives

The result files are separated at least by SAP client. 

 

21. Continuous Standard Outputs (Standard Result Plan)

Enables continuous creation of standard outputs defined in the Result Plan activated by the Content Bundle.

Important: The recommended maximum project size is 100 million BSEG rows. Larger datasets may lead to Power BI performance and memory limitations, affecting dashboard usability and responsiveness. Reliable operation above this threshold cannot be guaranteed. 

 

22. Custom Outputs (Custom Result Plan)

Provides customer-specific output structures and result formats.

Important: The recommended maximum project size is 100 million BSEG rows. Larger datasets may lead to Power BI performance and memory limitations, affecting dashboard usability and responsiveness. Reliable operation above this threshold cannot be guaranteed. 

Cooperation Obligations
  • define required output formats
  • validate output specifications
  • review output acceptance criteria


23. Power BI Templates (.pbit)

Provides predefined Power BI templates for the creation and customization of analytical dashboards based on the generated result data.

Cooperation Obligations
  • provide Power BI Desktop on end users’ devices
  • provide required Microsoft licenses


24. Source Files for Power BI Dashboards (.parquet)

Provides processed result files in .parquet format that serve as the data source for Power BI dashboards.

Important: The recommended maximum project size is 100 million BSEG rows. Larger datasets may lead to Power BI performance and memory limitations, affecting dashboard usability and responsiveness. Reliable operation above this threshold cannot be guaranteed. 

Cooperation Obligations
  • manage distribution and storage of result files

 

25. Excel File per Indicator with Marked SAP Documents

Provides a Microsoft Excel file for each indicator containing all SAP documents identified by the respective indicator.

Cooperation Obligations
  • provide software (e.g. Microsoft Excel) capable of opening .xlsx files
  • manage distribution and storage of result files


26. Pseudonymization of Results

Applies zapliance pseudonymization logic to analytical results in accordance with the activated Content Bundle configuration.

 

27. Link to SAP Documents (Web GUI/Fiori) in Power BI Dashboards

Allows users to access individual SAP documents directly from the Power BI dashboards without additional effort of searching for the specific item in SAP. The feature utilizes SAP Web GUI or SAP Fiori.

Cooperation Obligations

Conduct all necessary preparations listed in the article Setting Up SAP Web GUI, including:

  • provide users with required SAP user access to view documents
  • provide users with access rights to required transaction codes:
    • FB03: Display accounting documents
    • ME53: Display purchase requisitions
    • ME23: Display purchase orders
    • VL03: Display deliveries
    • VA03: Display sales orders
    • VF03: Display billing documents
  • provide Web GUI or Fiori URL
  • ensure that users' devices have access to the provided Web GUI or Fiori URL


    28. Wilma Link in Power BI Dashboards

    Allows users to access zapAgent Wilma via link directly from the Power BI dashboards for an explanation of the selected data set, for example an explanation of a specific DuPa Recovery candidate pair. The link automatically activates a predefined prompt, meaning that Wilma starts the analysis and responds without the need to enter a prompt manually.

    Cooperation Obligations
    • deployment of zapAgent Wilma including customer-provided LLM integration (Azure OpenAI Services)
    • provide users with access to Wilma via browser


    29. REST API Access

    Enables the ability to call external tools and systems via their REST APIs, for example to push results.

     

    30. MCP Server Creation & Management

    Enables creation and management of one MCP Server per project within zapAnalytics, operated as Docker containers.

    Cooperation Obligations
    • provide the required technical environment for operating the MCP Server
    • ensure network connectivity between zapAnalytics and MCP consumers
    • manage access permissions for MCP users and systems
    • maintain the systems consuming MCP services


    31. Result Transfer to MCP Server

    Enables publication of data processing results to the MCP Server(s) created and managed within zapAnalytics for further consumption by connected systems and services.

    Cooperation Obligations
    • ensure MCP consumers are configured correctly
    • define which users and systems may consume MCP results
    • manage access governance for published result datasets


    32. Web Search (via Azure OpenAI)

    Utilizes the customer's Azure OpenAI Web Search tool to conduct targeted web search, for example for VAT ID validation and company detail research.

    Cooperation Obligations
    • set up Azure OpenAI Services
    • activate the web_search tool in the Responses API
    • see details in Setup Guide Azure OpenAI


    33. VAT ID Validation via Endpoint Connection (BZSt & VIESS)

    Utilizes the customer's Azure OpenAI Services for data validation via targeted endpoint connections, for example for VAT ID verification.

    Cooperation Obligations


    In addition to this Product Description, the Product Descriptions of all components included in the offer, contractual or commercial agreement apply.

    The General Terms and Conditions (GTC) of zapliance in their currently valid version apply.