Product Description zapAgent Team Werner

1. Overview

zapAgent Team Werner performs SAP data extraction, processing, attachment analysis and result generation for one-off projects and continuous monitoring scenarios.

Werner extracts SAP data, processes and prepares it within zapAnalytics, and performs analytics based on predefined indicators or ML algorithms. All data processing takes place within zapAnalytics.

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

Werner operates within the contractually agreed zapHome setup in the customer’s IT environment.

The customer acquires a license to use zapAgent Team Werner within the contractually agreed scope. The license includes only what is expressly listed under “Included in the License” in the section “License Coverage.”

The Content Bundle defines the download plan, processing plan, result plan, and features available to Werner.

The license and use of zapAgent Team Werner are subject to this Product Description, the commercial agreement, and all other applicable documents listed the section “License Conditions".

2. Content of This Product Description

This section defines which matters are governed by this Product Description and which matters are governed separately.

2.1 This Product Description defines:

the purpose and functional scope of zapAgent Team Werner;
the License Coverage of zapAgent Team Werner;
the general license conditions for using the Agent Team;
the generic zapAnalytics features used by Werner;
the Content Bundle-activated features available to the Agent Team;
detailed feature descriptions;
general cooperation obligations;
feature-specific cooperation obligations;
general prerequisites and requirements for operating the Agent Team.

2.2 This Product Description does not define such matters as:

the specific download scope, processing scope, or result scope of an individual Content Bundle;
the specific feature scope of an individual Content Bundle;
customer-specific prompts, agents, tools, MCP Servers, or workflows;
generic features or requirements of zapHome;
Customer Success services;
implementation or system integration services;
Training or Consulting services;
Custom Development services.

The specific analytical scope activated for Werner is defined in the applicable Content Bundle Description.

The matters not defined in this Product Description are governed by the applicable Product Descriptions and the commercial agreement.

3. System Context

3.1 Agent Team

zapAgent Team Werner operates within the contractually agreed zapHome setup.

The relevant product components have separate functions:

zapHome provides the technical environment for the contractually agreed Agent Team, solution and all required components.
Werner executes SAP data extraction, data processing, advanced analytics, and result generation according to the applicable solution.
- zapAnalytics provides the software environment used by Werner for SAP data extraction, data processing, and result generation.
- Content Bundles activate the download plans, processing plans, result plans, and features used by Werner.

3.2 Solution Architecture

Werner separates SAP data extraction from data processing and result generation through two technically independent layers:

Data extraction (Layer 1)
Data processing (Layer 2)

Layer 1 uses SAP RFC connectivity to extract approved SAP data and create governed data copies within the zapAnalytics database. It is defined through the download plan.

The download plan, including the data scope, is defined and approved by the customer. Werner cannot independently change the data scope or initiate additional calls. All data extractions are therefore defined, approved, and controlled by the customer.

Layer 2 operates exclusively on these extracted data copies to perform indicator-based analytics and result generation. It does not access SAP, does not use RFC, and does not process live SAP data. It is defined through the processing plan and result plan.

As a result, SAP access and data processing (including result generation) are technically separated. Processing is performed on copied data only after extraction has been completed, not on the SAP system itself.

For more information, see SAP Governance Data Extraction with zapliance.

4. License Coverage

The license coverage is determined exclusively by the section “Included in the License.” Only what is explicitly listed there is part of the license.

The section “Not Included in the License” provides common examples for additional clarification. It is not exhaustive. The absence of an item from that section does not mean that the item is included in the license.

4.1 Included in the License

The license includes:

use of zapAgent Team Werner for the contractually agreed one-off project within the agreed service period;
the generic features described in section 8;
the available solution-specific features described in section 9 if activated by the contractually agreed Content Bundle;
the agreed number of Content Bundles;
the agreed service start date, service period, and, if applicable, minimum term.

The exact scope of the included Content Bundle is defined in the applicable Content Bundle Description.

A feature marked as available in this Product Description is included only if it is activated by the applicable Content Bundle and covered by the commercial agreement.

4.2 Not Included in the License

For clarification, the license does not include in particular:

features marked as unavailable in section 9;
Custom Development services;
Customer Success services;
implementation or system integration services;
Training or Consulting services;
Power BI licenses;
interpretation or validation of analysis results by zapliance.

This list serves only as additional clarification and is not exhaustive. An item or service is not included in the license unless it is expressly listed under “Included in the License.”

Any additional item or service requires a separate contractual agreement.

5. License Conditions

The customer acquires a license for the use of zapAgent Team Werner for a One-off or Continuous project, with the following license components:

Project Type: The project type determines whether a project 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: The service period for the one-off project begins on the service start date and ends on the service end date or after the specified service period has expired.
Minimum Term: If a minimum term is defined in the commercial agreement, cancellation is only possible at the end of this term. The service period is effective from the service start date.
Content Bundles: Content Bundles include contractually agreed license conditions and define the download plan, processing plan, and result plan. If the customer-specific commercial agreement does not include specific plans, the details of the selected Content Bundle apply.
- Download Plan: If the commercial agreement restricts the download plan, the data scope applies to the agreed download plan, including, for example, SAP clients, company codes, fiscal years, and organizational scope.
- Processing Plan: If the commercial agreement restricts the processing plan, the processing scope applies to the agreed processing plan.
- Result Plan: If the commercial agreement restricts the result plan, the output scope applies to the agreed result plan.

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.
SAP Clients: If the commercial agreement restricts the number of SAP clients, this restriction applies to the specified clients within an SAP system.
SAP Company Codes: If the commercial agreement restricts company codes, this restriction applies to the specified company codes within an SAP client.
Fiscal Years: If the commercial agreement restricts fiscal years, this restriction applies to the specified fiscal years within an SAP client.

The use of zapAgent Team Werner is governed by the commercial agreement details, including:

the contractually agreed zapHome setup;
the selected solution;
the selected Content Bundle;
the agreed data scope (SAP clients, company codes, fiscal years);
the agreed service start date;
the agreed service period;
the agreed minimum term, if applicable.

Any restrictions regarding SAP data scope, analysis scope, output scope, or usage defined in the commercial agreement apply to zapAgent Team Werner.

In the event of any conflict between this Product Description and the commercial agreement, the commercial agreement shall prevail.

In addition to this Product Description and the commercial agreement, the following documents apply:

the applicable Content Bundle Description;
the Product Descriptions applicable to all other components included in the commercial agreement;
the General Terms and Conditions (GTC) of zapliance in their currently valid version.

6. Prerequisites and Cooperation Obligations

6.1 General Prerequisites

The following general prerequisites apply:

deployed and operational zapHome OnPrem or zapHome OnPrem AI setup;
provision of user access to Werner via a web browser;
availability and accessibility of the SAP systems required for RFC-based data extraction;
fulfillment of all prerequisites defined in the applicable Content Bundle Description.

6.2 Cooperation Obligations and Customer Responsibilities

The customer is responsible for the 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 the digital products, and the Agent Team operate or where the digital products and data are transported or transferred. The customer is guided by the measures already applied to the SAP productive system.

The customer additionally ensures 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, or 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 as required.

The customer is responsible for taking appropriate measures to prevent damage, such as virus infestation or system crashes, due to access to or software use on the customer’s systems.

The customer is responsible for complying with all applicable legal requirements, especially data protection and labor law requirements, during software use. This includes involving the data protection officer and works council where necessary.

6.3 Technical Requirements

To operate zapAgent Team Werner, the contractually agreed zapHome instance must be deployed and operational, including all required components and data workflows.

A Linux-based virtual machine 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 the Setup Guide Virtual Machine / Server.

Docker is recommended as the container management tool. For other deployment scenarios, the applicable zapHome deployment documentation applies.

7. Content Bundles

A Content Bundle defines and activates the analytical scope used by Werner in zapAnalytics.

A Content Bundle consists of:

download plans;
processing plans;
result plans;
a project template;
an organization template;
all necessary licenses;
the features activated for the applicable Agent Team and solution.

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.

The specific scope of an individual Content Bundle is defined in the applicable Content Bundle Description.

Download Plans

Download plans define the data scope to be extracted from SAP systems.
The scope definition is performed in consultation with zapliance. Download plans are created by zapliance and provided specifically for the customer in a Content Bundle.
The data scope is defined and approved by the customer. Werner cannot independently change the download plan, expand the approved data scope, or initiate additional calls.

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.
Processing operates exclusively on the extracted data copies stored in the project database. It does not access SAP, does not use RFC, and does not process live SAP data.

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 such as Microsoft SharePoint.
Result plans are created by zapliance and provided specifically for the customer in a Content Bundle.
The results generated through result plans are made available via zapAnalytics, for example through web download, database access, or an interface.

Available Content Bundles

The following Content Bundles can be processed by zapAgent Werner:

360°;
P2P (Purchase-to-Pay);
O2C (Order-to-Cash);
Finance;
DuPa (Duplicate Payment);
VAT;
DuPa Recovery;
Continuous Monitoring;
Custom Content Bundles.

The applicable Content Bundle Description defines the included download plan, processing plan, result plan, project scope, activated features, prerequisites, and license conditions.

8. Generic zapAnalytics Features Used by Werner

The following generic zapAnalytics features can be used without uploading a Content Bundle.

Web Application

central installation hosted within the customer’s IT environment;
deployment as a Docker container or through Kubernetes;
user access via a web browser;
German and English language support.

Security

integrated role and permissions concept;
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 Multi-Factor Authentication

Authentication through login credentials with optional Multi-Factor Authentication.

Password Reset on Login Screen

Password reset directly from the login screen.

Change of Login Credentials

Modification of the email address and password used for authentication.

Email Notifications for Project Status

Automatic email notifications regarding:

project status changes;
completed activities;
processing errors.

Application Log Download

Download of application log files for troubleshooting, support, and audit purposes.

Content Bundle Upload

Upload of a Content Bundle provided by zapliance, typically as a .zip file. Uploading a Content Bundle activates the included project configuration, workspace, licenses, and features.

9. Features Available to zapAgent Team Werner

9.1 Feature Overview

The features activated in a specific setup depend on the selected Content Bundle. The applicable Content Bundle Description defines the detailed feature scope.

Feature	Available
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)³³	❌

9.2 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).

SAP connections are created, edited, and deleted exclusively by authorized users through the zapAnalytics user interface. zapAgents do not have access to SAP connection management and cannot create, modify, or delete SAP connections. 

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 specified in the respective Content Bundle Description.

All data extractions and their scope are approved and controlled by the customer. zapAgents cannot independently change the data scope or initiate extractions.

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. 

All data extractions and their scope are approved and controlled by the customer. zapAgents cannot independently change the data scope or initiate extractions.

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.

All data extractions and their scope are approved and controlled by the customer. zapAgents cannot independently change the data scope or initiate extractions.

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.

All downloads and their scope are approved and controlled by the customer. zapAgents cannot independently change the data scope or initiate downloads.

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. The ML algorithm operates exclusively on the already extracted data copies stored in the project database. It does not access SAP, does not use RFC, and does not process live SAP data. It cannot change the data scope or initiate data extractions.

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 (through Azure OpenAI). The LLM operates exclusively on the already extracted copies. It does not access SAP, does not use RFC, and does not process live SAP data. It cannot change the data scope, initiate data extractions or attachment downloads.

Cooperation Obligations

create and deploy required Azure OpenAI Services resources (Large Language Model)
provide required endpoints and API keys for integration
See details in Setup Guide Azure OpenAI Setup and Setup Guide Document Intelligence

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.

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.

22. Custom Outputs (Custom Result Plan)

Provides customer-specific output structures and result formats.

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.

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 all analytical results. Result files (e.g., parquet files), databases used by MCP servers, and all derived visualizations and interfaces, including Power BI dashboards and Wilma, contain only pseudonymized data. Since zapliance has no technical or organizational means to reverse pseudonymization, pseudonymized customer data cannot be linked to natural persons by zapliance and is therefore considered anonymous for all processing activities performed by zapliance. 

Important: If the customer displays data during meetings involving zapliance, the customer must ensure that only pseudonymized data is shown. The customer remains solely responsible for preventing the disclosure of non-pseudonymized data during such sessions (e.g. screen-sharing a live SAP system containing actual transactions or accounting documents).

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.

SAP Web GUI and FIORI are only used to access individual SAP documents from the results dashboards after data extraction and processing have been completed. Their use is technically separate from RFC-based data extraction and cannot influence its scope or execution.

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.

This feature is not available for zapAgent Team Werner.

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.

Azure OpenAI is technically separate from the data extraction layer. It does not access SAP, does not use RFC, and does not process live SAP data. It cannot change the data scope or initiate data extractions.

This feature is not available for zapAgent Team Werner.

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.

This feature is not available for zapAgent Team Werner.

Product Description zapAgent Team Werner

License Coverage, License Conditions and Functionality of the zapAgent Team

1. Overview

2. Content of This Product Description

2.1 This Product Description defines:

2.2 This Product Description does not define such matters as:

3. System Context

3.1 Agent Team

3.2 Solution Architecture

4. License Coverage

4.1 Included in the License

4.2 Not Included in the License

5. License Conditions

6. Prerequisites and Cooperation Obligations

6.1 General Prerequisites

6.2 Cooperation Obligations and Customer Responsibilities

6.3 Technical Requirements

7. Content Bundles

8. Generic zapAnalytics Features Used by Werner

9. Features Available to zapAgent Team Werner

9.1 Feature Overview

9.2 Feature Descriptions and Cooperation Obligations