Product Description zapAgent Wolfgang

Wolfgang extracts SAP data via RFC, prepares it in a structured format, and performs indicator-based analyses. These analyses can be executed as project-based one-off runs. All data processing takes place within zapAnalytics.

Results are delivered in Power BI and various export formats, and can be further processed in combination with other zapliance agents.

Description zapAnalytics

General Description

Wolfgang operates within zapAnalytics, zapliance's on-premises software for SAP data extraction and processing. It is operated entirely within the customer's locally installed zapHome instance, ensuring that data remains at the site where the software is running. 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:

Data extraction from ERP systems (“Download Plan”),
Data processing using predefined analyses (“Processing Plan”),
Preparation of results for the evaluation of the data and integration into third-party software (“Result Plan”).

With Wolfgang, one-off analyses can be carried out, which include data extraction, processing, and forwarding.

zapAnalytics Features

Web application
- A central installation that is hosted on-premises
- Deployment as a Docker container
- Multilingual support: German and English
Management of:
- Projects:
  - Projects organize and control data extraction, processing, and preparation.
  - Projects are managed within an organization and provided through a “Content Bundle”.
- Databases:
  - The zapAnalytics 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 can be password-protected.
  - Database connections can be encrypted.
  - Supported databases: PostgreSQL
- Connection data to ERP systems:
  - For data extraction, saved connection data can be selected, or new connection data can be created.
  - An SAP data extraction occurs either via the SAP message server or application server using RFC (Remote Function Call).
- Download Plans:
  - Download plans define the data scope to be extracted from ERP 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, 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.
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 and can be uploaded by the customer into zapAnalytics. The project features become available to the customer, once the project is activated.
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

Wolfgang's Capabilities

This section provides an overview of Wolfgang's key characteristics and a detailed breakdown of all features he offers.

Wolfgang's key capabilities at a glance:

SAP Access: Read-only RFC
Artificial Intelligence: No
Internet Connection: No

The following table provides a detailed breakdown of all features. Every Wolfgang deployment utilizes the full set of features listed below:

Category	Feature	Available
SAP Data Extraction	RFC-Based Data Extraction Only the data required for the defined analysis scope is extracted from SAP via RFC (read-only access) and stored as a copy in a locally secured database.	✅
	Standard Download Plan Wolfgang allows the use of standard Content Bundles with a predefined download scope.	✅
	Shortest Frequency	Project-based
Data Processing	Process Labeling Wolfgang classifies SAP documents into business processes based on their characteristics, independently of existing SAP labels.	✅
	Off-the-Shelf Analytics Wolfgang allows the use of standard Content Bundles with a predefined set of indicators.	✅
	Batched SAP Data Processing Wolfgang analyzes all extracted SAP data in one processing session.	✅
Output Format	Standard Output Plan Wolfgang allows the use of standard Content Bundles with a predefined set of outputs.	✅
	Power BI Dashboards The dashboards are created using template files (.pbit) and source files (.parquet) provided by Wolfgang.	✅
	Link to SAP Document The Power BI dashboards include direct links to access SAP documents via Fiori or the Web GUI.	✅
	Excel Various details can be exported as Excel files for further use.	✅
	Pseudonymization of Output Data	✅
Interfaces	MCP Integration Wolfgang can connect his project results to other zapliance agents (e.g. Wilma) via MCP for further processing.	✅

The specific analytical objective of a deployment - for example, whether Wolfgang performs a 360° digital audit preparation or an Order-to-Cash analysis - is defined by the selected Content Bundle. It determines which SAP data is extracted, which processing steps are applied, and which outputs are generated.

For information on Content Bundles, please refer to this overview and then select the respective bundle for details.

License Conditions

The following section outlines the licence conditions governing the use of zapAgent Wolfgang.

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 Services enable the customer to extract, process, and generate results multiple times.
Service Start or Service-Date: The service period regulates when projects can be processed. If the offer includes a restriction on the service date, this restriction applies to the specified period.
- One-Off projects: The service period for one-off projects begins on the service start date and ends on the service end date.
- Continuous Services: The service period for Continuous Services begins on the service start date and ends upon the effective date of termination.
Service Period: In Continuous Service 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 Duration: If a minimum duration is 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 Update: 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.
SAP Clients: If the offer provides a restriction on clients, this restriction applies to the specified clients within an SAP system. The content bundle can either:
- contain no restrictions for an SAP client.
- contain a predefined response key for a customer-specified SAP client. Changing the SAP client within the project is not possible.
- include a Response Key voucher. By specifying the SAP client in the zapAnalytics project, an activation-required Challenge Key is generated.
SAP Company Codes: If the offer provides a restriction on company codes, this restriction applies to the specified company codes within an SAP client. The content bundle can either:
- contain no restrictions for SAP company codes.
- contain a predefined response key for customer-specific SAP company codes. Changing SAP company codes within the project is not possible.
- include a Response Key voucher. By specifying SAP company codes in the zapAnalytics project, an activation-required Challenge Key is generated.
Fiscal Years: If the offer provides a restriction on fiscal years, this restriction applies to the specified fiscal years within an SAP client. The content bundle can either:
- contain no restrictions for SAP fiscal years.
- contain a predefined response key for customer-specific SAP fiscal years. Changing SAP fiscal years within the project is not possible.
- include a Response Key voucher. By specifying SAP fiscal years in the zapAnalytics project, an activation-required Challenge Key is generated.
Frequency: In Continuous Service mode, the 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.
Continuous Services: If the offer includes a restriction on continuous services, a control subscription may be used for a maximum of the specified number of Continuous Services.

Cooperation Obligations

General prerequisites for using zapAnalytics:

Provision of a server or virtual machine (VM) with the specified hardware requirements.
Administrator rights for installing zapAnalytics on a virtual machine or server.
Installation, licensing, and granting user access to the necessary Microsoft Services to utilize the zapliance outputs.
Use of a PostgreSQL database.
The hardware used requires a network connection to the ERP system for the duration of data and document extraction.
For licensing download plans, the following information must be made available to zapliance before data download: SAP client, SAP company codes, and fiscal years to be analyzed.
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.

Hardware Requirements for Using zapAnalytics

To efficiently operate zapAnalytics, a powerful and properly configured virtual machine (VM) or server is required:

Modern Linux distribution (alternative deployment methods must be discussed with zapliance)
Modern multi-core processor (at least 8 cores)
Scalable RAM with 64GB or more
Scalable hard drive capacity from 1 TB with a read/write speed of at least 100 MB/s
Uninterrupted availability during the processing of projects, including data , processing, and preparation
Administrator access to the VM/server is required

For details, see Setup Guide Virtual Machine / Server

Required Open Ports

zapAnalytics: 9007 (HTTPS)
SAP RFC: 3300, 3600, 3299 (default application and message server port)
(optional) Judgements Info Server: 59008