OpenText Archiving and Document Access For SAP Solutions 21.4 Release Notes

OpenText™ Archiving and Document Access for
SAP Solutions
Release Notes
21.4
Product Released: 2021-11-19
Release Notes Revised: 2022-03-31

Contents
1 Introduction .......................................................................................................................... 1
1.1 Release Notes Revision History ................................................................................................. 1
2 About OpenText™ Archiving and Document Access for SAP Solutions...................................... 2
2.1 Discontinued and Deprecated Features .................................................................................... 2
2.2 General Data Protection Regulation (GDPR) ............................................................................. 2
3 Packaging and Documentation ............................................................................................... 4
3.1 Packaging and Delivery Information ......................................................................................... 4
3.1.1 Software Components.................................................................................................. 4
3.1.2 Recommendation for OpenText™ Archiving and Document Access for SAP
Solutions 21.4 Installations................................................................................... 6
3.1.3 OpenText System Center.............................................................................................. 6
3.1.4 OpenText™ Fiori Business Object Browser for Document Access for SAP
Solutions ............................................................................................................... 7
3.2 Related Documentation ............................................................................................................ 8
3.3 Delivery...................................................................................................................................... 9
3.3.1 OpenText Customers .................................................................................................... 9
3.3.2 SAP Customers ............................................................................................................. 9
3.4 Note on the End User License Agreement ................................................................................ 9
3.4.1 Usage of DocuLink and of ArchiveLink PLUS ................................................................ 9
3.4.2 Usage of OpenText™ Fiori Business Object Browser Enabler for SAP Solutions ........ 10
3.4.3 Usage of OpenText Content Server ............................................................................ 10
3.4.4 Usage of Searchable PDF DocTool.............................................................................. 10
3.4.5 Usage of Archive Center CMIS.................................................................................... 11
3.5 Architecture Diagram .............................................................................................................. 11
4 Supported Environments and Compatibility.......................................................................... 12
4.1 Supported Systems .................................................................................................................. 12
4.1.1 Client Platform Support.............................................................................................. 12
4.1.2 Enterprise Library Discontinuation............................................................................. 13
4.1.3 Citrix Support.............................................................................................................. 14
4.1.4 Server Platform Support............................................................................................. 14
4.1.5 Content Server Syndication ........................................................................................ 15
4.1.6 SAP Server Support..................................................................................................... 15
4.1.7 Supported SAP GUIs ................................................................................................... 24
OpenText™ Archiving and Document Access for SAP Solutions 21.4 Release Notes
i
4.1.8 Supported ArchiveLink Protocols ............................................................................... 25
4.1.9 WebDAV Storage Interface for SAP NetWeaver Information Lifecycle
Management ...................................................................................................... 25
4.2 OpenText Product Compatibility ............................................................................................. 25
4.3 Language Support.................................................................................................................... 26
5 Installation and Upgrade Notes ............................................................................................ 27
5.1 Installation Notes .................................................................................................................... 27
5.1.1 Installation Requirements .......................................................................................... 27
5.1.2 BC Set Activation ........................................................................................................ 28
5.1.3 SAP Notes ................................................................................................................... 28
5.1.4 Enhancement Packages .............................................................................................. 29
5.1.5 CRM Package .............................................................................................................. 30
5.1.6 Configuring the AS ABAP for Supporting SSL ............................................................. 30
5.1.7 ArchiveLink Plus: Business Content Window ............................................................. 30
5.2 Content Server License Keys ................................................................................................... 30
5.3 Language Installation .............................................................................................................. 30
5.4 Upgrade Notes......................................................................................................................... 31
5.4.1 Upgrade Planning ....................................................................................................... 32
5.4.2 Upgrade Path.............................................................................................................. 33
5.5 OpenText Vendor Keys ............................................................................................................ 34
5.5.1 When to Use Exchange Packages ............................................................................... 34
5.5.2 When to Use Attribute Change Packages .................................................................. 34
5.5.3 When to Use Vendor Keys.......................................................................................... 34
5.5.4 OpenText™ Archiving and Document Access for SAP Solutions Vendor Keys ........... 34
5.6 Attribute Change Packages (ACPs) .......................................................................................... 34
5.6.1 Where to Obtain ACPs................................................................................................ 35
5.6.2 Version 21.4 ACP Files ................................................................................................ 35
5.7 SAP Add-on Packages Overview .............................................................................................. 36
6 Patches ................................................................................................................................ 37
6.1 Hotfixes.................................................................................................................................... 37
6.2 Updates ................................................................................................................................... 38
6.2.1 ABAP Support Package Installation ............................................................................ 38
6.2.2 Available SAP Support Packages ................................................................................ 39
6.2.3 Maintaining URL Paths to DocuLink Documentation ................................................. 39
7 Fixed Issues ......................................................................................................................... 40
ii
8 Known Issues ....................................................................................................................... 41
8.1 Accessibility ............................................................................................................................. 41
8.2 DocuLink for SAP Solutions ..................................................................................................... 41
8.2.1 DocuLink - Table and Field Restrictions...................................................................... 44
8.2.2 DocuLink - Visualization ............................................................................................. 46
8.2.3 DocuLink - SAP GUI for HTML ..................................................................................... 47
8.2.4 DocuLink - Business Application Integration (BAI) ..................................................... 47
8.2.5 DocuLink - SAP GUI for JAVA for MAC OS X ............................................................... 49
8.3 OpenText Imaging Integration ................................................................................................ 49
8.4 OpenText Imaging DesktopLink............................................................................................... 50
8.5 OpenText Imaging Clients ....................................................................................................... 50
8.6 Forms Management for ECR ................................................................................................... 50
8.7 Business Content Window ...................................................................................................... 51
8.8 S/4HANA .................................................................................................................................. 51
8.9 Other Issues ............................................................................................................................. 51
8.10 Archive Center ......................................................................................................................... 52
9 Troubleshooting .................................................................................................................. 53
10 Contact Information............................................................................................................. 54
iii
List of Tables
Table 1 - Release Notes Revision History ............................................................................................... 1
Table 2 - Detailed Component List of OpenText Archiving and Document Access for SAP Solutions ... 4
Table 3 - Add-ons of OpenText™ Fiori Business Object Browser Enabler for SAP Solutions ................. 7
Table 4 - Compatibility ADA (BOB part) versus Business Center / Vendor Invoice Management
Foundation ............................................................................................................................................. 8
Table 5 - Client Platform Support ......................................................................................................... 12
Table 6 - Supported SAP Business Suite and S/4 HANA Applications .................................................. 15
Table 7 - Required SAP Components and Support Packages ............................................................... 16
Table 8 - Required SAP Components and Support Packages for Fiori UI Support ............................... 20
Table 9 - Supported SAP GUIs .............................................................................................................. 24
Table 10 - Required Patches ................................................................................................................. 24
Table 11 - OpenText Product Compatibility ......................................................................................... 25
Table 12 - Language Support ................................................................................................................ 26
Table 13 - SAP (OSS) Notes ................................................................................................................... 28
Table 14 - SAP Add-on Packages Overview .......................................................................................... 36
Table 15 - Available Hotfixes ................................................................................................................ 37
Table 16 – Mandatory Security Hotfixes .............................................................................................. 37
Table 17 - Known Issues ....................................................................................................................... 41
Table 18 - Troubleshooting................................................................................................................... 53
iv
Table of Figures
Figure 1 - Main Components of OpenText™ Archiving and Document Access for SAP Solutions ......... 4
Figure 2 - Architecture Diagram ........................................................................................................... 11
v
1 Introduction
These release notes provide an overview of OpenText™ Archiving and Document Access for SAP
Solutions 21.4, including new features, delivery information, and supported platforms. OpenText
recommends that you read these release notes in conjunction with the documentation included
with the software package. If any conflicts exist, the release notes supersede the other
documentation.
These release notes are frequently updated. Please look for updates on a regular basis on
OpenText My Support.
We also recommend that you check OpenText My Support for any patches or documentation
updates that may have been posted after the initial release of this product.
1.1 Release Notes Revision History

Table 1 - Release Notes Revision History
Revision Date Sections Revised Description of Revisions
2021-11-19 First release
2021-11-22 4.1.6 SAP Server Support Added S/4HANA 2021 support
2021-12-02 5.1.3 SAP Notes Added SAP notes 3126094 to address

potential
SKWF_TP_NMSPC_CHECK_AFTER_IMP
issue
2021-12-06 5.1.3 SAP Notes Added SAP notes 3125721 and 3125769 to
address security issues
2021-12-09 6.1 Hotfixes Added list of mandatory security hotfixes
2022-03-31 4.1.6.3 Required SAP Added missing information that OTEXERP

Support Packages supports SAP_BASIS 750
1
2 About OpenText™ Archiving and Document Access for SAP
Solutions
This section provides an overview of OpenText™ Archiving and Document Access for SAP Solutions
21.4.
OpenText™ Archiving and Document Access for SAP Solutions 21.4 is the seamless integrated
business document solution for SAP applications providing imaging and high-volume archiving
capabilities for incoming and outgoing documents as well as desktop documents. OpenText™
Archiving and Document Access for SAP Solutions 21.4 enables you to integrate your documents into
your SAP application business processes e.g., incoming orders, outgoing correspondence, or SAP ERP
invoices.
OpenText solutions are seamlessly integrated with the SAP system: retrieval, access, and document
display all take place directly from within the SAP application. The centralized storage and
management of the documents simplifies and speeds up retrieval. Fast access to the documents
guarantees rapid processing of e.g., inquiries and complaints.
No matter where your employees are currently working, anyone with the appropriate authorization
can access the required documents at any time, worldwide.
2.1 Discontinued and Deprecated Features

Starting with version 21.2, OpenText™ Archiving and Document Access for SAP Solutions does not
support OpenText NotesLink anymore.
OpenText Imaging Java Viewer, which is not part of this bundle, is deprecated.
Starting with 21.1, both OpenText Imaging Windows Viewer and OpenText Imaging Web Viewer do
include the functionality of OpenText Imaging PDF Extensions. Therefore, OpenText™ Archiving and
Document Access for SAP Solutions does not include OpenText Imaging PDF Extensions as
standalone component anymore.
2.2 General Data Protection Regulation (GDPR)

The General Data Protection Regulation (GDPR) is a European Union (EU) law that gives residents
greater protection and control of their personal data. It regulates the data companies inside and
outside the EU can collect, store, and transfer – as well as how they use it. All companies that
process EU resident data must comply with GDPR, starting on May 25, 2018.
Software solutions like OpenText™ Archiving and Document Access for SAP Solutions can neither be
considered as GDPR-compliant nor GDPR-uncompliant. Every customer using SAP Business Suite or
SAP S/4HANA and OpenText™ Archiving and Document Access for SAP Solutions is responsible for
ensuring GDPR compliance in their organization.
2
OpenText™ Archiving and Document Access for SAP Solutions acts as a repository for documents
archived via SAP applications. Documents can be enriched with additional information called
ArchiveLink PLUS attributes. Data accessed via OpenText™ Archiving and Document Access for SAP
Solutions uses standard SAP authorization concept.
For OpenText™ Archiving and Document Access for SAP Solutions alone, retention management and
disposition at the end of ArchiveLink documents lifecycle can be achieved in combination with SAP
ILM. For OpenText™ Archiving and Document Access for SAP Solutions using OpenText Content
Server, OpenText Records Management ensures a retention schedule as well as disposition at the
end of content (attributes and documents) lifecycle.
For OpenText™ Archiving and Document Access for SAP Solutions, the change control is the standard
SAP change control. Content stored is automatically backed up, content replication can be
configured, disaster recovery is provided.
3
3 Packaging and Documentation
Downloads and documentation for OpenText™ Archiving and Document Access for SAP Solutions are
available on OpenText My Support.
3.1 Packaging and Delivery Information

OpenText™ Archiving and Document Access for SAP Solutions consists of many individual
components. The main components of OpenText™ Archiving and Document Access for SAP Solutions
are shown in Figure 1.
Figure 1 - Main Components of OpenText™ Archiving and Document Access for SAP Solutions
3.1.1 Software Components

Table 2 lists all components of OpenText™ Archiving and Document Access for SAP Solutions 21.4.
Please use OpenText System Center to download OpenText™ Archiving and Document Access for
SAP Solutions 21.4.
Table 2 - Detailed Component List of OpenText Archiving and Document Access for SAP Solutions
Group Component Version
Content Content Server

21.4
Server and (Usage limited to SAP ILM and full-text search only)
Modules Extended ECM for SAP Solutions 21.4
Please see
Section 3.4.3 Extended ECM Platform 21.4
4
Usage of
OpenText Imaging Enterprise Scan 20.4
Content Server
for usage Monitoring Agent 21.2
restrictions.
Archive Cache Server 21.2
Archive Archive Center 21.2
Center and
Components Archive Monitoring Server and Web Client 21.2
Solution Registry Agent 21.2
Document Pipeline Base 21.2
Document Pipeline for DocuLink 21.2
Document Pipeline for SAP Solutions 21.2
Document
Pipelines Document Pipeline Info 21.2
Document Pipeline Perl 21.2
Document Pipeline Remote Interface 21.2
Searchable PDF DocTool 20.4
Directory Services (OTDS) 21.3
Extended ECM Web Services 21.4
Other Servers Imaging Enterprise Scan Web Interface 20.4
& Services
Imaging Web Viewer 21.4
System Center Manager (OT Edition) 21.4
System Center Manager (SAP Edition) 21.4
Administration Client 21.2
Imaging Enterprise Scan 20.4
Clients Imaging ExchangeLink 21.4
Imaging OutlookLink 21.1
Imaging Windows Viewer and DesktopLink 21.4
5
Archiving and Document Access for SAP® Solutions

21.4
(OTEXBAS, OTEXBASB, OTEXBASF, OTEXBASO, OTEXCRM, and
OTEXERP SAP add-on packages)
Extended
ECM Enabler
for SAP® Extended ECM for SAP® Solutions
Solutions 21.4
(OTEXRL SAP add-on package)
(SAP® Add-on
packages)
Vendor Invoice Management Foundation

20.4 SP2
(OTBCBAS and OTBCWUI SAP add-on packages)
For detailed information about individual components of OpenText™ Archiving and Document
Access for SAP Solutions, please have a look at the respective release notes.
3.1.2 Recommendation for OpenText™ Archiving and Document Access for SAP
Solutions 21.4 Installations
Note
We strongly recommend using OpenText System Center to keep your Content
Server 21.4 (or higher) up to date with the latest patches for Content Server and
modules.
3.1.3 OpenText System Center

OpenText System Center is the next generation solution for Content Server patching and updates.
Some of the featured capabilities are:
• Management of multiple environments

• Better online/offline support
• Proper proxy support
• Enhanced user experience
• Self-updating
6
• Not reliant on browser to remain running when executing tasks
• Content Server no longer needs internet access to download patches
For more information about System Center, please access the product page on OpenText My
Support.
3.1.4 OpenText™ Fiori Business Object Browser for Document Access for SAP Solutions
OpenText™ Fiori Business Object Browser for Document Access for SAP Solutions is a collective term,
which includes the following:
• Compatible versions of
o OpenText™ Archiving and Document Access for SAP Solutions
o OpenText™ Fiori Business Object Browser Enabler for SAP Solutions:
2 ABAP add-Ons of OpenText™ Vendor Invoice Management for SAP® Solutions.
These are required to build custom Fiori apps to browse for business objects.
Important
Usage restrictions are detailed in chapter 3.4.2
Please check the compatibilities depending on the version of the Process

Base Fiori Task App.
Please read the Release Notes and guides of OpenText™ Vendor Invoice
Management for SAP® Solutions to learn about the details of installation
and configuration and regarding mandatory actions after upgrading from
older versions. You find them here at the OpenText™ Knowledge Center.
Table 3 lists the ABAP add-ons of Vendor Invoice Management required for a business object
browser scenario (see also OpenText Archiving and Document Access for SAP Solutions: Scenario
Guide - Packages for business browser) as of version 21.4.
Table 3 - Add-ons of OpenText™ Fiori Business Object Browser Enabler for SAP Solutions
Target System ABAP Add-on
SAP Backend OTBCBAS
SAP Gateway (Hub / Frontend) OTBCWUI
Optional: OTBCBAS
7
Table 4 lists the compatibility between ADA and Vendor Invoice Management Foundation versions.
Table 4 - Compatibility ADA (BOB part) versus Business Center / Vendor Invoice Management Foundation
Archiving and Business Center for SAP Solutions VIM2
Document
Access for SAP 16 20.4
Solutions 16.3 16.3.1 16.3.2 16.3.3 16.3.4 16.3.5 20.4 21.4
UPD 2 SP1
Version1
16.2.0 (16 EP2) Yes - - - - - - - - -
16.2.4 (16 EP4) - Yes Yes Yes - - - - - -
16.2.8 (16 EP6) - - - Yes Yes - - - - -
16.2.10 (16 EP7) - - - Yes Yes Yes Yes - - -
20.2 - - - Yes Yes Yes Yes - - -
20.3 - - - Yes Yes Yes Yes - - -
20.4 - - - - - - - Yes Yes Yes
21.2 - - - - - - - Yes Yes Yes
21.4 - - - - - - - Yes Yes Yes
3.2 Related Documentation

For additional information about OpenText™ Archiving and Document Access for SAP Solutions, or
for supplemental information about related products, refer to the following documents, which are
available on OpenText My Support.
List of recommended documentation:
• OpenText™ Archiving and Document Access for SAP Solutions - Scenario Guide
• OpenText™ Archiving and Document Access for SAP Solutions - Installation and Upgrade
Guide
• OpenText™ DocuLink for SAP Solutions - User Guide
1
Compatibility references to Business Object Browser
2
Foundation Component of Vendor Invoice Management for SAP Solutions
8
If you want to use of capabilities of OpenText™ Extended ECM for SAP Solutions in the context of
ArchiveLink PLUS or ILM (Information Lifecycle Management), then the release notes of OpenText™
Extended ECM for SAP Solutions 21.4 are a good starting point. They contain a list of recommended
documentation, as well.
3.3 Delivery
3.3.1 OpenText Customers
OpenText customers can download OpenText™ Archiving and Document Access for SAP Solutions
21.4 from the “Download” section of OpenText My Support.
3.3.2 SAP Customers

SAP customers can download OpenText™ Archiving and Document Access for SAP Solutions 21.4
from the SAP Support Portal, SAP Software Download Center. At the SAP Software Download Center,
the software is listed under SAP ARCHIVING AND DOCUMENT ACCESS BY OPENTEXT 21.4.
3.4 Note on the End User License Agreement

OpenText™ Archiving and Document Access for SAP Solutions is shipped with the following
OpenText™ products:
• OpenText™ Data Archiving for SAP Solutions

• OpenText™ Archiving for SAP Solutions
• OpenText™ Archiving and Document Access for SAP Solutions
• OpenText™ Extended ECM for SAP Solutions
Respectively with the SAP Solution Extensions:
• SAP Archiving by OpenText

• SAP Archiving and Document Access by OpenText
• SAP Extended Enterprise Content Management (ECM) by OpenText
3.4.1 Usage of DocuLink and of ArchiveLink PLUS

The use of the functionality “DocuLink” (transaction J6NY) as provided by the module OpenText™
DocuLink for SAP Solutions and the usage of ArchiveLink PLUS is restricted to the following licensed
products
• OpenText™ Archiving and Document Access for SAP Solutions

• OpenText™ Extended ECM for SAP Solutions
• SAP Archiving and Document Access by OpenText
• SAP Extended Enterprise Content Management (ECM) by OpenText
9
3.4.2 Usage of OpenText™ Fiori Business Object Browser Enabler for SAP Solutions
OpenText™ Fiori Business Object Browser Enabler for SAP Solutions includes 2 add-ons of
OpenText™ Vendor Invoice Management for SAP® Solutions to implement custom SAP Fiori apps,
which integrate the SAP Fiori standard apps of OpenText™ Archiving and Document Access for SAP
Solutions. The usage is restricted in the following ways:
• Usage allowed without extra licenses:

o Browse business objects in the Fiori Web UI of workplace
o The supported customizing options and enhancements are described in OpenText™
Vendor Invoice Management for SAP® Solutions Customizing Guide for Foundation
• The following usages need extra licenses for OpenText™ Vendor Invoice Management for
SAP® Solutions:
o Solutions specifically designed for preconfigured processes, like incoming sales
orders, purchase order/purchase requisition dashboard, incoming delivery notes or
incoming HT documents
o OpenText™ Vendor Invoice Management for SAP® Solutions for
▪ Import
▪ Capture
▪ Dispatch
▪ Process
o In the case of doubts, the license audit report of Vendor Invoice Management can
be executed to find out, if the framework is used in a way, that need extra licenses
for OpenText™ Vendor Invoice Management for SAP® Solutions.
• The integration of the Business Documents Fiori App is restricted to the following licensed
products:
o OpenText™ Archiving and Document Access for SAP Solutions
o SAP Archiving and Document Access by OpenText
3.4.3 Usage of OpenText Content Server

The use of OpenText™ Content Server is restricted to the scenarios ILM (Information Lifecycle
Management) and ArchiveLink PLUS. Content Server Document Management and Content Server
Records Management are expressively not considered a legitimate use of the software. (In the same
sense, the use of the “Business Workspace” and of the “Business Attachments” functionality
integrated in “Business Content Window” [formerly known as “Attachment List PLUS”] and
integrated in DocuLink is not considered a legitimate use of the software)
3.4.4 Usage of Searchable PDF DocTool

The Searchable PDF DocTool allows rendering scanned documents to searchable PDF/A. This
DocTool must only be used in scan pipelines together with Enterprise Scan, means it is intended only
10
for documents manually scanned in with Enterprise Scan. Batch conversion of imported images is
expressively not considered a legitimate use of the software.
3.4.5 Usage of Archive Center CMIS

Archive Center CMIS is not part of OpenText™ Archiving and Document Access for SAP Solutions
licenses. Using Archive Center CMIS requires additional licenses.
3.5 Architecture Diagram

Figure 2 shows the architecture of OpenText™ Archiving and Document Access for SAP Solutions
21.4.
Figure 2 - Architecture Diagram
11
4 Supported Environments and Compatibility
This section provides details about supported platforms, systems, and versions.
4.1 Supported Systems

4.1.1 Client Platform Support
For information and restrictions concerning operating systems please have a look at the release
notes of:
• OpenText™ Imaging ExchangeLink

• OpenText™ Imaging OutlookLink
• OpenText™ Imaging Viewers and DesktopLink
• OpenText™ Imaging Enterprise Scan
Please take into consideration your intended deployment scenario. Often not all components are
installed on the same machine and thus different client operating systems might be used for the
installation of the complete solution.
Table 5 - Client Platform Support
Client OS Client Browser Support Notes
Windows IE 11 • OpenText DocuLink for SAP Solutions Web User

IE 11 Enterprise Mode Interface and OpenText ArchiveLink PLUS - Search
Edge Web User Interface are based on Web Dynpro ABAP.
Therefore, the same limitations are valid as for Web
Dynpro ABAP. See SAP/OSS note 1098009 for more
details.
Windows Firefox ESR • Regarding Web Dynpro ABAP based applications, see
Firefox SAP/OSS note 1098009 for more details.
Chrome
Non-Windows Firefox • Regarding Web Dynpro ABAP based applications, see

Safari SAP/OSS note 1098009 for more details.
Chrome • Regarding Fiori UI support, see chapter 4.1.1.1 below.
Firefox
4.1.1.1 Support for Fiori Web User Interface
This chapter lists the specific restrictions for the usage of the Fiori Web User Interface.
The list of supported client platforms depends on the SAP Front-End Server on which the Fiori Web
User Interface is hosted. See SAP’s Product Availability Matrix (PAM) at
https://support.sap.com/pam for details.
12
There is also a browser and platform overview for SAPUI5 by SAP located here.
Further general information by SAP is given at SAP Note 1716423.
If integrated into the Process Base Fiori Web User Interface for Business Object Browser, then please
also read the related chapter in the Release Notes of OpenText™ Vendor Invoice Management for
SAP® Solutions.
SAP Fiori Web User Interface restrictions

Safari Home-Screen bookmark
This mode is not supported.
Android devices:
It will work as stated by SAP in their product availability matrix with Android 4.4
browser or Chrome for Android browser. Due to the variety of hardware specific
implementations of the Android OS it is not supported in general.
MOB SAP Fiori Client:
The usage of the Business Documents is supported. But document display normally
opens a new browser tab. In the case of the mobile SAP Fiori Client, the display
switches to the document and after closing the document the display returns to the
original Fiori app and refreshes it.
4.1.2 Enterprise Library Discontinuation

Starting with OpenText™ Archiving and Document Access for SAP Solutions 20.2, Enterprise
Library is discontinued. This announcement includes the following Enterprise Library
components:
• Extensions for Enterprise Library

• Enterprise Library Services
• Document Pipeline for Enterprise Library
OpenText™ Archiving and Document Access for SAP Solutions 16.2.10 ceased to use Enterprise
Library for declaring documents to Content Server. Customers who declared documents
with an earlier version should use 20.2 to migrate Enterprise Library documents to Extended
ECM documents. After a successful migration, one should uninstall both Extensions for
Enterprise Library and Enterprise Library Services.
Customers using Enterprise Library ILM must keep Enterprise Library until Archive Center
offers an ILM migration mechanism in a future release.
13
4.1.3 Citrix Support
To find out which OpenText™ Archiving and Document Access for SAP Solutions components
support Citrix, please refer to their respective release notes.
4.1.4 Server Platform Support

Please take into consideration your intended deployment scenario. Often, not all components are
installed on the same machine and, thus, different server operating systems and database systems
might be used for the installation of the complete solution.
For further information regarding operating systems and database servers, please read the release
notes for OpenText Archive Center 21.2 and OpenText Content Server 21.4. Notice that Content
Server is only relevant here for ILM and full-text search.
14
4.1.5 Content Server Syndication
OpenText™ Archiving and Document Access for SAP Solutions does not support Content Server
Syndication.
4.1.6 SAP Server Support

4.1.6.1 Supported SAP Business Suite and S/4HANA Applications
Supported S/4HANA applications include the following:
- S/4HANA on premise
- S/4HANA Cloud single tenant
o S/4HANA Private Cloud Edition (PCE)
o S/4HANA Extended Edition (EX)
Table 6 - Supported SAP Business Suite and S/4 HANA Applications
SAP Platform OpenText Archiving and Document Access
SAP AS ABAP 7.1 Supported only for data archiving, document archiving, and display
ERP 6.0,
SAP NetWeaver 7.0
EhP1-3 for ERP 6.0
All SAP systems running on the required SAP_BASIS versions, for

instance:
• EhP4-8 for ERP 6.0
SAP NetWeaver > 7.0
• CRM 7.0
EhP 1 - 2 for SAP NetWeaver
7.0 • EhP1-4 for CRM 7.0
EhP 1 for SAP NetWeaver 7.3
SAP NetWeaver 7.40 • SRM 7.0
SAP NetWeaver 7.50, 7.51,
7.52 • EhP1-4 for SRM 7.0
• SFINANCIALS 1.0, 1503 (SAP_FIN 700 or 720), or SAP S/4HANA
FINANCE 1605 (SAP_FIN 730) with most recent ACP (see Section
5.6 for more details)
S/4HANA Applications 1610, 1709, 1809, 1909, 2020, 2021

on premise and single
tenant All FPS are supported.
15
4.1.6.2 SAP HANA Support
OpenText™ Archiving and Document Access for SAP Solutions 21.4 supports SAP Business Suite on
SAP HANA database. OpenText™ Archiving and Document Access for SAP Solutions is SAP certified
for SAP HANA on SAP NetWeaver 7.40 onwards.
4.1.6.3 Required SAP Support Packages

Table 7 - Required SAP Components and Support Packages
OpenText Software Prerequisite set1 of Software Support

Release
Component OpenText Add-on Component Package Level
ABAPFND optional
DW4CORE optional
S4FND optional
700 0018
701 0003
702
Archiving and Document 731
Prerequisite set 01
Access for SAP® Solutions 740
750
OTEXBAS 2140_700
751
SAP_ABA 752
75A
75B
75C
75D
75E
75F
75G
16
700 0018
701 0003
702
731
740
750
SAP_BASIS 751
752
753
754
755
756
OTEXBAS 2140_700
ABAPFND optional
DW4CORE optional
S4FND optional
700 0018
701 0003
702
731
Extended ECM for SAP® Prerequisite set 01 740
Solutions
750
OTEXRL 2140_700
751
SAP_ABA 752
75A
75B
75C
75D
75E
75F
75G
SAP_BASIS 700 0018

701 0003
17
702
731
740
750
751
752
753
754
755
756
OTEXBAS 2140_700
Any version,
SAP_APPL not optional
(*)
700
Prerequisite set 01
701
702
SAP_BASIS
731
740
750
Archiving and Document
Access for SAP® Solutions SAP_FIN optional
for ERP
OTEXBAS 2140_700
OTEXERP 2140_700
Any version,
SAP_BASIS
S4CORE not optional
700: 0016
(*)
Any version,
Prerequisite set 02 SAP_ABA not optional
(*)
750
751
SAP_BASIS 752
753
754
18
755
756
700
701
702
BBPCRM
712
713
Access for SAP® Solutions
for CRM Prerequisite set 01
OTEXBAS 2140_700
OTEXCRM 2140_700
701
702
SAP_BASIS 731
740
750
Information is based on most recent packages or Attribute Change Packages (ACP).

1
Prerequisite set: In transaction SAINT, see menu Goto > Installation and Support Pack.
Directory. In the list of packages, a set of import condition is named prerequisite sets.
All prerequisite sets of an Add-On presented here are alternatives to each other.
“Minimum of 700” means release 700 or higher.
“optional” means that the Add-On can be installed or not.
“any version, not optional” means that the Add-On is required, but the version is not defined
distinctively. In this case other conditions already defined sufficient restrictions.
SPAM/SAINT Version: A minimum of 0071 is required.
4.1.6.4 Fiori UI Support
The SAP Fiori apps of OpenText™ Archiving and Document Access for SAP Solutions 21.4 require a
minimum SAPUI5 runtime version 1.60 (a minimum of 1.71 is recommended). Though, this is not
enforced by import conditions. For optimal behavior regarding accessibility please go for the highest
SAPUI5 version with long-term maintenance.
For details about SAPUI5 versions on different SAP Releases read

SAP Note 2217489 Maintenance and Update Strategy for SAP Fiori Front-End Server
The OData services need either the enablement component IW_BEP 200 or the gateway foundation
component SAP_GWFND 740 on the SAP Back-End server.
Please note, that the optional package OpenText™ Solution Framework for Business Object Browser
(OTEXBASB) also requires packages from OpenText™ Vendor Invoice Management for SAP®
19
Solutions.
See Table 8 for detailed requirements.
Table 8 - Required SAP Components and Support Packages for Fiori UI Support
OpenText Software Prerequisite set1 of Software Support

Release
Component OpenText add-on Component Package Level
IW_BEP 200 0010
700 0018
Prerequisite set 01
701 0003
SAP_BASIS
702
731
ABAPFND optional
DW4CORE optional
S4FND optional
740
750
Access for SAP® Solutions 752
75A
OTEXBASO 2140_700
SAP_ABA 75B
75C
Prerequisite set 02 75D
75E
75F
75G
740
750
751
752
SAP_BASIS
753
754
755
756
20
740 0009
750
751
752
SAP_GWFND
753
754
755
756
ABAPFND optional
DW4CORE optional
S4FND optional
740
750
751
752
75A
SAP_ABA 75B
75C
Archiving and Document 75D
Access for SAP® Solutions 75E
Fiori Apps Prerequisite set 01 75F
75G
OTEXBASF 2140_740
740
750
751
752
SAP_BASIS
753
754
755
756
752
SAP_UI 753
754
21
755
756
ABAPFND optional
DW4CORE optional
Minimum
OTBCBAS of
0700_006
OTEXBAS 2140_700
S4FND optional
700
701
702
731
740
Solution Framework for 750
Business Object Browser 751
Prerequisite set 01
SAP_ABA 752
OTEXBASB 2140_700 75A
75B
75C
75D
75E
75F
75G
700
701
702
731
SAP_BASIS 740
750
751
752
753
754
22
755
756
Information is based on most recent packages or Attribute Change Packages (ACP) from
patches area.
1
Prerequisite set: In transaction SAINT, see menu Goto > Installation and Support Pack.
Directory. In the list of packages, a set of import condition is named prerequisite sets. All
prerequisite sets of an Add-On presented here are alternatives to each other.
“Minimum of 700” means release 700 or higher.
“optional” means that the Add-On can be installed or not.
“any version, not optional” means that the Add-On is required, but the version is not defined
distinctively. In this case other conditions already defined sufficient restrictions.
SPAM/SAINT Version: A minimum of 0071 is required.
4.1.6.5 Fiori Business Object Browser Enabler Support
The add-ons of Fiori Business Object Browser Enabler are the same of the respective version of
component Foundation of OpenText™ Vendor Invoice Management for SAP® Solutions. Please have
a look at the specific system requirements in the release notes and documentation in OpenText™
My Support in area Vendor Invoice Management.
23
4.1.7 Supported SAP GUIs
The supported SAP GUIs depend only on the SAP Basis/NetWeaver version.
Table 9 - Supported SAP GUIs
SAP
NetWeaver
SAP Software SAP GUI for SAP GUI for SAP GUI for
Version Business
Component Windows HTML Java
Client
(NWBC)
7.0 and
1
7.0 7.60, 7.70 Integrated higher -
Standalone
EhP1-2 for
7.0 and
NW 7.0, EhP1 7.60, 7.701 Integrated -
higher
for NW 7.3
SAP Basis / 7.0 and

7.4 7.60, 7.701 Integrated -
NetWeaver higher
7.5, 7.51,
7.52 7.0 and
7.60, 7.701 Integrated -
(Business higher
Suites)
S/4HANA 7.0 and

7.60, 7.701 Integrated
(7.5 – 7.56) higher
1) OpenText™ recommends using OpenText™ Archiving and Document Access for SAP
Solutions with SAP GUI for Windows 7.70 combined with Microsoft Edge.
Table 10 - Required Patches
Software Component Minimum Version Minimum Patch Level
7.60
SAP GUI for Windows
7.701 3.1
1) OpenText™ recommends using OpenText™ Archiving and Document Access for SAP
Solutions with SAP GUI for Windows 7.70 combined with Microsoft Edge.
24
SAP GUI for Windows and NWBC versions, for which SAP support ended, are not listed here
anymore. See also SAP Notes 147519 Maintenance strategy / deadlines for SAP GUI for Windows /
SAP GUI for Java and 2302074 - Maintenance strategy and deadlines for SAP Business Client / NWBC
Note: SAP GUI for HTML Support Restriction

SAP GUI for HTML is a limited SAP GUI for Windows emulator. OpenText™
Archiving and Document Access for SAP Solutions fully supports SAP GUI for
Windows integration. However, OpenText™ Archiving and Document Access for
SAP Solutions can only restrict the SAP GUI for HTML support to issues also
reproducible in SAP GUI for Windows.
4.1.8 Supported ArchiveLink Protocols

The ArchiveLink protocols 4.5, 4.6, and 4.7 are supported. OpenText provides for ArchiveLink
following communication protocols: OT_OLEU1, OT_OLEU2, OT_HTTP2, OT_HTTP3 . For usage of
ArchiveLink protocol 4.6 (Cache Server Extension), copy one of the provided communication
protocols and set the version to 0046 in SAP. Therefore, OpenText Archive Cache Server and SAP
Content Server Cache are supported.
4.1.9 WebDAV Storage Interface for SAP NetWeaver Information Lifecycle Management
The WebDAV Storage Interface for SAP NetWeaver Information Lifecycle Management is supported.
SAP Integration scenarios BC-ILM 2.0, BC-ILM 3.0, and BC-ILM 3.1 operate with WebDAV Storage
Interface for SAP NetWeaver Information Lifecycle Management.
4.2 OpenText Product Compatibility

The section provides details about which versions of other OpenText products are compatible with
this release of OpenText™ Archiving and Document Access for SAP Solutions 21.4.
Note: For additional compatibility information for OpenText products, refer to the
Compatibility Matrix (https://knowledge.opentext.com/go/matrix) on OpenText My
Support. Notice that the release notes supersede the Compatibility Matrix.
Table 11 - OpenText Product Compatibility
Product Name Version Notes

OpenText™ Extended ECM for SAP Solutions 21.4
OpenText Extended ECM Platform 21.4
Content Suite Platform 21.4
25
4.3 Language Support
OpenText™ Archiving and Document Access for SAP Solutions is currently available in the following
languages.
Table 12 - Language Support
Language SAP Code End-user Interface User Guide
Arabic AR X
Chinese (Simplified) ZH X X
Chinese (Traditional) ZF X
Danish DA X
Dutch NL X
English EN X X
French FR X X
German DE X X
Italian IT X X
Japanese JA X X
Kazakh KK X
Korean KO X
Norwegian NO X
Polish PO X
Portuguese PT X X
Russian RU X X
Spanish ES X X
Turkish TR X
Ukrainian UK X
The default UI language for the components is English; other languages are available as language
packs or language module versions on OpenText My Support (Open Text customers) and on the SAP
Support Portal (SAP customers). Starting with version 16.2, the localization of the Fiori apps is also
available in (ABAP) language packs.
In many cases, administrative user interfaces are only available in English.
26
5 Installation and Upgrade Notes
This section provides additional installation and upgrade information, including related or third-
party product information and any required critical patches.
Note
Should you need several servers of the same kind (e.g., Content Server,
Archive Server), please never attempt to duplicate a virtual image
installation. This approach is not supported and could lead to severe
issues. Always install additional servers from scratch.
5.1 Installation Notes

Before you install OpenText™ Archiving and Document Access for SAP Solutions, review these
additional installation notes and verify related product or third-party product requirements.
Warning
Installing Content Server modules on Linux may require manually granting
more permission of the module files in the Content Server staging directory
before proceeding further.
5.1.1 Installation Requirements
All installation steps are described in OpenText™ Archiving and Document Access for SAP Solutions -
Installation and Upgrade Guide.
Also consider the software requirements mentioned in 4.1.6 SAP Server Support.
Important
Please make sure BEFORE installation that in table TAORA and IAORA are
entries maintained for TABART ‘USER’ and ‘USER1’ which link to a valid
TABSPACE.
Table TAORA
TABART USER / USER1
Table IAORA
TABART USER / USER1.
27
5.1.2 BC Set Activation
OpenText™ Archiving and Document Access for SAP Solutions - Installation and Upgrade Guide lists
SAP notes which must be applied to avoid issues with the activation of Business Configuration (BC)
sets. If you still experience errors when activating BC sets, customizing transports are available in the
KC (https://knowledge.opentext.com) which correlate to the settings activated with the BC sets.
5.1.3 SAP Notes
Some SAP (OSS) notes are required to avoid known problems with the SAP system. In
addition to those notes listed below, also refer to the Known Issues section on page 41 for SAP notes
required for special scenarios.
Table 13 - SAP (OSS) Notes
SAP (OSS) Note Required for
Language-dependent texts in the GUI

110910 Some language-dependent texts may not be displayed correctly
in the GUI. Reference 144437
Logon error from external systems to WAS 7.00 systems

The external candidate's password contains at least one lower
case letter. In accordance with the rules, which were valid up to
and including WAS 6.40, the registration application changes the
884077 passwords to capital letters. However, as of WAS 7.00 (see OSS
note 862989), the system can be set in a way that it
distinguishes between upper case and lower-case letters in a
password. In this case, the log-on fails if the original password
contains at least one lower case letter.
CALL_BROWSER does not launch a new window to open the URL,

even when the NEW_WINDOW parameter is passed to the
function module. Instead, an existing window is made use to
open the URL. However, as of OSS Note 1177636, the behavior
1128338
of CALL_BROWSER is changed to also allow opening URLs on
other platforms than Windows. And then the settings of the MS
Internet Explorer govern the behavior, whether a new window is
opened.
28
SAP (OSS) Note Required for
This note prevents a dump screen in the Business Content

1713851 Window when one tries to open a record, gets an SAP Security
dialog, and presses the “Deny” button.
Starting with version 16.2 Archiving and Document Access for

SAP Solutions and Extended ECM for SAP Solutions use a new
URL escaping, which is based on SAP’s escape_xss_url as
implemented in SAP note 1582870.
For SAP BASIS 731 and higher method

1582867 cl_abap_dyn_prf=>escape_xss_url is directly called.
For older releases a Kernel function is used, if a SAP Kernel as of

note 1582867 is at place, or a fallback code is used as derived
from SAP’s original implementation of SAP note 1582870.
In the case of non-Unicode systems, the related notes
referenced in SAP Note 1582867 should be applied.
This note describes the solution if the upgrade or the

installation stops
3126094
at the SKWF_TP_NMSPC_CHECK_AFTER_IMP post-import
method.
Security Issue
3125721 Manual instruction for SLIN_SEC obsolete URL escape method
used
Security Issue
3125769 Manual instruction for SLIN_SEC potential cross-site scripting in
/OTX/RM_CSUI_BASE_REDIRECT_SRV
5.1.4 Enhancement Packages
The add-on packages for software component OTEXBAS are installable on SAP systems with
enhancement packages for SAP NetWeaver 7.0, on EhP1 for SAP NetWeaver 7.3 (=SAP_BASIS 731), on
SAP NetWeaver 7.4 and SAP NetWeaver 7.5. No additional ACP package is needed.
29
The (optional) add-on package for software component OTEXERP is installable on SAP systems with
enhancement packages 1 - 8 for ERP 6.0. It is also installable on S/4 HANA on-premise 1610, 1709,
1809, 1909, 2020, 2021.
5.1.5 CRM Package

One (optional) OTEXCRM add-on package is delivered, which may be installed on SAP CRM 7.0 and
EhP1 – 4 for SAP CRM 7.0. Please refer to the details given in OpenText™ Archiving and Document
Access for SAP Solutions - Installation and Upgrade Guide.
5.1.6 Configuring the AS ABAP for Supporting SSL
To configure the AS ABAP to support SSL, please follow the following procedure:
http://help.sap.com/saphelp_nw70ehp2/helpdata/en/49/23501ebf5a1902e10000000a42189c/fram
eset.htm
5.1.7 ArchiveLink Plus: Business Content Window

The ABAP functionality is included in the add-on OTEXRL of OpenText™ Extended ECM for SAP
Solutions 21.4 and also requires other components of OpenText™ Extended ECM for SAP Solutions
21.4.
Therefore, the same version and compatibility restrictions apply as for OpenText™ Extended ECM for
SAP Solutions 21.4.
Please refer to the chapter about OPENTEXT BUSINESS CONTENT WINDOW in OpenText™ Archiving
and Document Access for SAP Solutions - Scenario Guide and the related documentation of for
OpenText™ Extended ECM for SAP Solutions 21.4.
5.2 Content Server License Keys

Please read Content Server licensing FAQ on OpenText My Support to learn about Content Server
license keys.
For customers of SAP Extended ECM by OpenText, a temporary license key is provided on the SAP
Services Marketplace under the name “Content Server License Key”.
5.3 Language Installation

The master setup installs the English version of the software components that are part of
OpenText™ Archiving and Document Access for SAP Solutions 21.4. Other languages are available as
language packs or language module versions on OpenText My Support.
30
Notice: For all components, installing the English version is a pre-requisite to installing a localized
version.
5.4 Upgrade Notes

In addition to the description given in OpenText™ Archiving and Document Access for SAP Solutions
- Installation and Upgrade Guide read these information regarding upgrades.
Furthermore, if you use parts of OpenText™ Extended ECM for SAP Solutions and the Content
Server, please review the instructions in the release notes and installation guides of OpenText™
Extended ECM for SAP Solutions 21.4
Warning
If you import an upgrade into an SAP system with OpenText™ Archiving and
Document Access for SAP Solutions 21.4 and the data of the respective upgrade
packages is not read (upgrade phase IS_SELECT), OpenText™ Archiving and
Document Access for SAP Solutions 21.4 add-on (i.e., OTEXBAS, OTEXERP,
OTEXCRM) will no longer work after the upgrade procedure. Since the status of the
system is then inconsistent, OpenText can no longer accept any liability. Please
note, that as listed in table 9-3 of OpenText™ Archiving and Document Access
for SAP Solutions - Installation and Upgrade Guide, the existing add-ons are kept
("KEEP" in upgrade phase IS_SELECT).
31
Caution
• User exits (legacy versions)
Due to the support of Unicode systems, DocuLink was modified
significantly in earlier versions. Therefore, user exits from DocuLink
versions = 2.6 are no longer supported. Projects using such user exits must
be revised. Furthermore, user exits from DocuLink versions > 2.6 may
have been modified; projects using such user exits must be adapted to the
new interfaces. Be aware that, as a rule, user exits are generally not
released for implementation in projects created by customers or partners!
Note for OpenText consultants implementing projects: See OpenText My
Support entry on user exits in DocuLink 9.6.0.
• Patch dependencies when upgrading (prior to 9.6.0)
When upgrading from versions lower than Livelink® ECM Suite for SAP®
Solutions 9.6.0 please avoid installing patch SS096-001.
Or when upgrading from versions lower than Livelink® ECM -Suite for
SAP® Solutions 9.6.0 and if patch SS096-001 was also installed on an
SAP Basis Release 6.40 or 7.00, then patch SS096-008 must also be
applied before upgrading to version 9.6.1 or higher. Otherwise, the add-on
installation tool SAINT will not carry out the installation due to problems
with the version numbers of the OTEXBAS/OTEXERP component.
Caution
Table entries in SGOSATTR
add-ons OTEXBAS and OTEXERP are not containing any table entries of
SGOSATTR anymore. But, if you are doing an upgrade step-by-step from an older
version, please note, that OTEXBAS and OTEXERP of versions 9.6.1 and 9.6.2
contain some DocuLink or DesktopLink entries in SGOSATTR by mistake.
Therefore, please take care to replace those erroneous entries again after upgrade.
(See also "Known issues" in the release notes of those older versions).
5.4.1 Upgrade Planning

OpenText highly recommends that customers thoroughly plan each upgrade on their SAP systems:
• Please get in contact with an OpenText consultant or with SAP/OpenText Support when
considering upgrading.
• Before executing an upgrade on a productive system, please consider doing the same
upgrade on a dedicated test and/or quality assurance system. It is also highly recommended
to do a database backup before the upgrade.
• If an SAP release upgrade or an update with enhancement packages is planned and if
OpenText add-on packages are already installed on the source release, please note, that
32
OpenText™ Archiving and Document Access for SAP Solutions 21.4 does not provide any
exchange upgrade packages. That means, when upgrading from SAP Releases R/3 4.7 or ECC
5.0 to ERP 6.0 or higher please consider doing the exchange upgrade with older OpenText
versions (like 9.8 or 10.0) and then to do a plain installation of version 21.4 on the target
release. Please check on OpenText™ Archiving and Document Access for SAP Solutions -
Installation and Upgrade Guide.
5.4.2 Upgrade Path

5.4.2.1 Gradual upgrade vs. installing most recent version
OpenText and SAP are not able to test and validate all upgrades from each version, which already
existed to the most recent version.
Only upgrades from the previous version of the most recent version are tested and checked.
Therefore the gradual upgrade from one version to its successor version is still the recommended
upgrade path to follow.
In the case you prefer to install the most recent add-ons right on top of an older version, then please
make sure, to check this on a test instance first on which you may also roll back, because OpenText
and SAP cannot guarantee, that an untested path works, even if it is expected to work.
Please also be aware, that older transports may be interpreted as modifications and then it is
important to keep an eye on the modification browser (transactions SPDD and SPAU).
Tip: If you follow an upgrade via several versions of OTEXBAS, OTEXERP or OTEXCRM,
skip support packages and hot fix transports, which are overwritten by follow-up versions, that
still follow in the path.
Note the cases described in the next sections, which need special care.
5.4.2.2 From transport-based versions prior to 9.6.0
Customers using transport-based versions prior to 9.6.0 must first upgrade to Livelink® ECM – Suite
for SAP® Solutions 9.6.0 using a product CD or patches from OpenText My Support.
Older descriptions required to install all older add-on versions step-by-step to the most recent
version. If you are already on a newer SAP release, it may be, that some older add-ons cannot be
imported. If a version is in sustaining maintenance it also may be, that no Attribute Change Package
can be made available. In those cases, it is ok to skip the add-on packages of older versions.
5.4.2.3 EFM 2.5
If OpenText Employee File Management 2.5 is installed on the SAP system and you plan to do an
upgrade of the OTEXBAS add-on, this can only be accomplished by installing the upgrade add-on
OTEXEIM 3.0 (EFM 3.0) together with add-on OTEXBAS 9.8 in transaction SAINT. The upgrade add-on
of EFM 3.0 already contains the requirement to be installed combined with the upgrade add-on of
33
OTEXBAS 9.8 in its package parameters.
After that, you can continue installing the newer add-ons on the path.
5.5 OpenText Vendor Keys

5.5.1 When to Use Exchange Packages
SAP Basis 620 and 640 were discontinued in version 10.5.0. Therefore, from version 10.5.0 no
exchange upgrade packages are delivered. And when upgrading from those releases, please consider
doing an upgrade to ERP 6.0 or higher with the exchange packages of version 10.0 and then to do an
update to 16 on the target release.
5.5.2 When to Use Attribute Change Packages

You need to install add-on packages on a release, which is expected to be supported, but the import
conditions do not match. Then please check, if Attribute Change Packages (ACP's) are available.
Also, following the recommendations of SAP (as in SAP Note 1324996) SAP Release updates or EHP
updates shall rather be supported by ACP's than by vendor keys. Starting with target SAP NetWeaver
release 702, this is supported by SAP.
Furthermore, in the case of Support Stack updates on newer SAP Releases, the Maintenance
Optimizer (MOPZ) is used to install new support package stacks. During this process MOPZ checks
the import conditions of already installed add-ons. Certain conditions, like dependencies to the
NetWeaver Release are implicitly checked for downwards compatibility. Other import conditions
must match exactly. Furthermore, the tool does not offer a phase to choose a "KEEP" followed by
entering the vendor key.
But MOPZ considers the Attribute Change Package (ACP) during the maintenance process. In the
case you are no SAP reselling customer, you may not be allowed to download the ACP using the SAP
Download Manager.
In this case, please refer to the chapter Attribute Change Packages (ACPs).
5.5.3 When to Use Vendor Keys

You already have installed add-on packages of version 21.4 on an SAP System with SAP NetWeaver
7.0 to SAP NetWeaver 7.5. You must upgrade to a new SAP Release which still is based on SAP NW
7.xx. Then the add-on exchange package cannot be used. And you didn't get an ACP to match the
import conditions. In the upgrade phase IS_SELECT please choose a "KEEP" upgrade. In this case the
upgrade tool asks you for a vendor key.
5.5.4 OpenText™ Archiving and Document Access for SAP Solutions Vendor Keys
The vendor keys are listed in a cross-version document located here on OpenText My Support.
5.6 Attribute Change Packages (ACPs)

Read SAP Note 1119856 for description, tips, and tricks for Attribute Change Packages
34
5.6.1 Where to Obtain ACPs
According to SAP Note 1119856 ACP's are usually delivered in an integrated manner or you can
download ACP's from the SAP Service Marketplace.
In the case of OpenText add-on (OCS) packages, OpenText is entitled to create ACP’s on their own.
Therefore, it can be that SAP will not make ACP’s available to SAP reselling customers.
Therefore, ACPs of OpenText™ Archiving and Document Access for SAP Solutions will be made
available to all customers in the patches area of OpenText My Support.
In the case you would expect an import condition in an ACP, which is missing, please get in contact
with OpenText Customer Support. In the case, the missing import condition is a valid request, then
OpenText development can add this.
For SAP reselling customers it is important to note, that OpenText may allow their direct selling
customers to install on systems, for which there is no SAP validation.
5.6.2 Version 21.4 ACP Files

You will find the most recent ACP files related to version 21.4 of OpenText™ Archiving and
Document Access for SAP Solutions in the patches area of OpenText™ Archiving and Document
Access for SAP Solutions on OpenText My Support.
35
5.7 SAP Add-on Packages Overview
Table 14 gives an overview of SAP add-on packages release per enhancement pack. Notice that add-
on packages 16.2.4 (16 EP4) or higher require Content Server 16.2.4 or higher.
Table 14 - SAP Add-on Packages Overview
Product Add-On Name Version
21.4
November 2021
Archiving and OTEXBAS 21.4

Document Access OTEXBAS 2140_700
OTEXBASB 21.4
OTEXBASB 2140_700
OTEXBASF 21.4
OTEXBASF 2140_740
OTEXBASO 21.4
OTEXBASO 2140_700
OTEXCRM 21.4
OTEXCRM 2140_700
OTEXERP 21.4
OTEXERP 2140_700
Extended ECM for OTEXRL 21.4

SAP Solutions OTEXRL 2140_700
36
6 Patches
A patch is a piece of software that is designed to fix or improve a computer program or its
supporting data. These may include repairs to security vulnerabilities or resolution of bugs and may
also improve usability or performance. On OpenText My Support you will find two general types of
patches. Hotfixes are also known as quick-fixes or bug fixes. Updates are also known as service packs
or service releases.
The following patches must be applied to OpenText™ Archiving and Document Access for SAP
Solutions 21.4. OpenText recommends that you check OpenText My Support for any patches or
documentation updates that may have been posted after this release.
6.1 Hotfixes
Hotfixes are small patches that address software issues. Typically, there is no new functionality in a
hotfix. Hotfixes can be cumulative.
The following table lists and describes the hotfixes available for this release.
Table 15 - Available Hotfixes
Hotfix Name Additional Info Downloads

Extended ECM for SAP Solutions
21.4 module:
Extended ECM for SAP Solutions 21.4 https://knowledge.opentext.com/

knowledge/llisapi.dll/open/85215
Requires the following: 52
pat162003839
• Content Server 21.4 Extended ECM for SAP Solutions
• Extended ECM Platform 21.4 21.4 module localization update.
Extended ECM Platform 21.4

module localization update.
The following table lists all mandatory security hotfixes for OpenText™ Archiving and Document
Access for SAP Solutions 21.4.
Table 16 – Mandatory Security Hotfixes
Component Description Severity Hotfix
curl - BDSA-2021-2140 (+4) High Hotfix-20210917-AS-20755.zip
37
Upgrade of libcurl to latest version
7.79.0
curl - BDSA-2021-2778
Hotfix Archive Center 21.2 - CVE-

2021-3450 and CVE-2021-3449 High Hotfix-20210913-AS-20714.zip
vulnerability in OpenSSL
Upgrade of libxml2 to latest version

OpenText™ High Hotfix-20210917-AS-20757.zip
2.9.12
Archive
Center 21.2 Upgrade of Apache CXF to latest
High Hotfix-20210914-AS-20758.zip
version 3.4.4
Upgrade of Jackson library to latest

version 2.12.5
Upgrade of Hazelcast to latest

version 3.12.9
Upgrade of Google Auth Library to

V1.2.1
BlackDuck: Apache Xerces-C 3.0.0 to

Medium
3.2.3 XML parser - Shared
OpenText™ ESC-2040-003.msp
Imaging BlackDuck: Apache Log4Net CVE-
Medium
Enterprise 2018-1285 (BDSA-2020-1058) - Scan
Scan 20.4 pat162003546_CS64_WIN.zip
BlackDuck : Underscore.js 1.10.2 -
Medium
Scan.Web pat162003546_CS64_LNX.tar.gz
6.2 Updates
Updates consist of many fixes combined into a single patch. Typically, the minor version number of
the product will increase, for example from 2.0 to 2.1. An update may also include new features
proactively introduced into the product. In most cases, updates are cumulative.
6.2.1 ABAP Support Package Installation

On client 000 of the target SAP system use transaction SPAM to install the ABAP support packages.
38
6.2.2 Available SAP Support Packages
There are currently no SAP support packages for OpenText™ Archiving and Document Access for SAP
Solutions 21.4.
Caution
OTEXBAS 2140 require SAP_BASIS 700 0018.
6.2.3 Maintaining URL Paths to DocuLink Documentation

URL paths to DocuLink documentation must now end with /$LANG$/. At runtime, $LANG$ is
substituted with the login uppercase 2-character ISO language code.
39
7 Fixed Issues
This section provides information about past issues that have been fixed in this release.
40
8 Known Issues
The following known issues exist in this release.
Caution
Restrictions on behalf of non-Open Text products are not listed here. See the
respective release notes for those products for further information.
Some entries have an internal reference number (pattern: reference- 139941). This
number refers to an internal information system and allows OpenText to
provide you with even faster high-quality support.
Entries with an icon refer to an SAP (OSS) note.
Table 17 - Known Issues
Issue
Issue Description
Number
8.1 Accessibility
Displaying a Print list from the Archive System
When a user needs full accessible mode within a print lists, OpenText
recommends using document display within the SAP GUI using the SAP Document
Viewer.
8.2 DocuLink for SAP Solutions

Caution
User exits
As a rule, user exits are generally not released for implementation in

projects created by customers or partners. Ask your OpenText
consultant for more information.
Transporting projects
When you transport DocuLink projects into an SAP system, where DocuLink is
already installed, an internal error may occur when executing a DocuLink
transaction, due to caching problems. In this case, try exiting and restarting the
transaction. If it fails again, execute /$sync.
41
Transporting projects of version 10.0, 10.5.0, 16.0
If it occurs that a DocuLink project based on version 10.0.0 to 16 needs to be

transported to a target system with an older DocuLink version, than it is
recommended to exclude "Settings for Generic Object Services" in the Advanced
Options during export in transaction J6NP. The reason is a change of fields in table
/IXOS/DC46_TBGOS.
Deleting SAP print lists
It is not possible to delete SAP print lists in DocuLink, as DocuLink does not allow
SAP tables to be edited (in this case, TOADL).
Unexpected result when hit list flag is applied to the root node
There is an unexpected behavior when a hit list is invoked from a first-level node
under the root node; this only happens when the hit list flag is applied to the root
node. After entering an invalid selection, the resulting hit list is empty (standard
behavior). If, however, you now go back and enter a valid selection, the resulting
hit list is still empty. You must click (Refresh) to get the correct results.
Permanent workaround:
1. Assign the required selection fields to the root node.
2. Create an additional static node under the root node and select under
Selection type option 2 or 3.
3. Remove the hit list flag from the root node and apply it to the new static
node.
4. Apply the option Open nodes automatically to the new static node.
5. Move the respective first-level node from the root node one level below
under the new static node.
Wrong focus in tree view DocuLink Web User Interface
With SAP EhP1 for SAP Basis 7.0 (NW 7.0 EhP1) SAP offers a Web Dynpro
rendering called Light Speed. A known issue is that in DocuLink Web UI with tree
view the root node is focused instead of the expanded tree node. The only known
measure so far to resolve this issue is to add an empty URL parameter sap-wd-
lightspeed (i.e., add &sap-wd-lightspeed= to the URL) to switch off Lightspeed
rendering.
42
Hit lists in DocuLink Web User Interface
Starting with 10.5 SP1 DocuLink hit list customizing of horizontal alignment is also
having affect in the Web UI with the following restrictions:
SAPRM-5871 • personalization done in the Web UI via administration mode overrides the
customizing
• if no alignment is defined, the alignment is 00 (=auto mode)
• The first column is not aligned by this customizing.
Error dump in DocuLink Web User Interface
In case of runtime errors in CL_WDR_VALUE_HELP_HANDLER when starting

SAP Note
projects in the DocuLink Web UI check also if SAP note 1669913 needs to be
1669913
installed on the SAP system.
Output masks for dynamic nodes
If the values for a field are restricted by input in a selection screen, the restriction
142195 may be ignored by a dynamic node, where an output mask is defined. In this case,
the restriction defined by the output mask overrules the one in the selection
screen.
Logging for CM documents in hit lists

204528 When you perform actions on CM documents that are displayed in a hit list, no
logging information is stored for these actions.
Displaying documents from a logical system
The user that is used to access the logical system must be of the user type Dialog.
Users of type Communication cannot display documents and input screens,
although they have permission to retrieve data.
43
Table maintenance for DocuLink sample project $EX_FI3
The maintenance data of the /IXOS/DC_EX_GJAH table is not populated

automatically. Therefore, this table must be maintained manually with year
numbers in field GJAHR and the client number in field MANDT. The maintenance is
required to make the DocuLink sample project $EX_FI or its copies work properly.
Otherwise, the view 001 of the sample project does not show any BKPF data
because of the value restriction GJAHR at node C_GJAHR, which in turn depends
on the data specified in the /IXOS/DC_EX_GJAH.
8.2.1 DocuLink - Table and Field Restrictions

Storing documents
Documents should be stored using ArchiveLink link tables (TOA0x). It is not

recommended to use the same table for archive ID, document ID and attributes.
Automatic filling of fields and tables containing archive ID and document ID
Tables containing archive ID and document ID must not have a key field filled
automatically (for example by means of a number range) if they are used for
manual archiving (not applicable to COLD).
Automatic filling of fields and DocTool R3Insert
If automatic filling of fields via DocTool R3Insert is used, an RFC destination <SY-
HOST>_<SY-MANDT> is created with user SAPCPIC and password ADMIN.
The customer can create this RFC destination. The user can be edited.
Table size
Only tables with a maximum width of 4,160 bytes are supported for hit lists.
Maximum width of fields in the database
If you create or change records in the database, the maximum width of fields in
the view is 132 characters.
3
$EX_FI an optional example DocuLink project which may be downloaded
from the KC (https://knowledge.opentext.com).
44
Maximum length of node type texts
Only node type texts with a maximum length of 500 characters can be displayed
correctly.
Check tables
A maximum of 4 fields may be linked via check tables to execute a foreign key
check against these check tables.
Check tables for COLD records
When inserting COLD records, possibly available check tables are ignored. This
includes the client specified when importing data, which means that it is not
checked whether the client exists. If not, the import will fail without an error
message and the entries are written into the table with a non-existing client.
Table names for COLD
Insertion of COLD records will succeed only for tables with names <= 25
characters.
Inserts into table TOAAT with COLD
Inserts into new ArchiveLink attribute table TOAAT are allowed without enabling
its name by a user exit. As no further integration of TOAAT was implemented,
fields like creation time and user will not be filled automatically without further
customizing. If wanted, you can use a DocuLink project to customize automatic
filling of these fields.
Dynamic nodes and cluster tables
Dynamic nodes will not work with cluster tables like BSEG. SAP does not support
the SELECT DISTINCT statement correctly. Duplicates are not eliminated.
Therefore, the performance will be poor. Enter an attribute object in the field
Value restriction at the dynamic node type.
String, Sstring or Rawstring data types in tables
String, Sstring or Rawstring data types are not supported in tables used by
DocuLink views.
Packed and float format at dynamic node types
Dynamic node types do not support selection fields with the data type packed (P)
or float (F) as COLLECT (non-info) fields.
45
Customizing output masks at dynamic node types
When an output mask is defined for the COLLECT field of a dynamic node type,
only selection fields with the data types CHAR and DATE are supported.
Using F4 help for authorization fields
When using the F4 help to enter authorization fields for authorization checks at
the attribute object, wildcards may be ignored. Restrict the amount of hits within
the search help screen instead.
8.2.2 DocuLink - Visualization

Problems when displaying archived documents with Web Viewer
The maintenance table /IXOS/OA_CUST_A (viewer customizing) offers a flag called

SAP note Open in curr. Window. The program code of this feature uses the SAP function
1128338, SAP module CALL_BROWSER. In case of problems when displaying archived documents
note with the Web Viewer check the following SAP notes:
1061637 • SAP note 1128338 - CALL_BROWSER does not open URL in new window
• SAP note 1061637 - Problems with the CALL_BROWSER function module
Displaying several documents at the same time
When several documents are selected, and you click on Display, not all selected
documents may be displayed. This is due to a synchronization problem between
the SAP GUI and the applications opened to display the documents. We
recommend displaying documents one at a time.
“Screens as popups” option
When displaying screens as pop ups, the pop ups may not be displayed correctly
after scrolling down in one of them. If a seemingly empty popup appears, try
scrolling upwards to display the “missing” fields. This is an SAP problem and
depends on the patch level of the SAP system and on the used SAP GUI.
No support of embedded MS Office documents in thumbnails view with Internet

Explorer 64-bit
The DocuLink thumbnail view uses Microsoft's ActiveX controls for the embedded
display of MS Office documents. They are not available as a 64-bit version.
Therefore, they are not supported when using the 64-bit versions of MS IE.
46
8.2.3 DocuLink - SAP GUI for HTML
Customizing (J6NP transaction)
Customizing via the J6NP transaction is not supported in the SAP GUI for HTML.
Common SAP GUI features
Not all common SAP GUI features like integration of desktop programs or certain
controls are supported: e.g., DesktopLink, Enterprise Scan.
ITS and selection screens
When using ITS, if the Screen as Popup option is activated in the header of a view
you must use the Refresh function to get the selection screen when you open a
node that has been assigned for such use. To avoid this effect and get the
selection screen directly, do not use the Screen as Popup option.
Displaying columns in a hit list
To display columns in a hit list correctly, a fixed font must be set in the
corresponding ITS CSS file columntreedhtml.css.
Checkbox alignment
Checkboxes are automatically aligned to the left in the SAP GUI for HTML.
Displaying FAX documents in-place
FAX documents can only be displayed in-place using OpenText Imaging: Windows
Viewer.
Archiving documents via front-end
Archiving scenarios do not work with SAP GUI for HTML.
8.2.4 DocuLink - Business Application Integration (BAI)

Displaying multi-value properties in IXOS Records
IXOS Records with multi-value properties cannot be displayed correctly in

OpenText DocuLink for SAP Solutions. Only one value of the property is displayed.
Exporting float values
SAP records with float values are not exported, as no data type for such values
exists in OpenText TCP Context Server.
47
IXOS Records with time stamps
Timestamps in IXOS Records cannot be used in queries to retrieve data from a

OpenText TCP Context Server, as no unique data type exists for timestamps in SAP
systems. The only exception is the creation date for IXOS records.
When exporting SAP records with timestamps, the SAP timestamps cannot be
mapped to the TCP Context Server data type DATETIME. Instead, use a string or
decimal type that corresponds to the SAP data dictionary type used for the
timestamp. (However, time zone conversion and date/time formatting are not
available for these types.)
Initial values in IXOS Records
Properties in IXOS Records for which no values have been set yet are displayed
with initial values in the SAP system. You cannot specify queries in SAP to select all
records where properties are unset.
Relations in Queries
In queries to retrieve data from OpenText TCP Context Server, you cannot use ECR
relations. Use the required IXOS Record type directly.
Special characters in Administration for TCP Context Server
In the Administration for TCP Context Server settings in DocuLink, special

characters are not supported for the following parameters:
• Organization for logon in ECR
• Domain for logon in ECR
• User for logon in ECR
Standard data model in OpenText TCP Context Server for the Livelink BAI
scenario
During data export from an SAP system to a TCP Context Server using the BAI
functionality, exported ArchiveLink documents are reclassified (specialized) from
the general ixos.dms:Entity type to the special ixos.bai:Document type.
Therefore, some prerequisites must be fulfilled.
48
Special permissions for the transfer user (BAI user)
The BAI user requires the write properties and ACL write permissions for
ArchiveLink documents archived to the ixos.dms:Entity. An ACL mapping
configuration must be specified on the TCP Context Server (e.g., for the
DMSALDefaultUser user for ArchiveLink documents without SecKeys).
If documents are archived using ODMA and DesktopLink, the BAI user requires Full
Access permission to the ixos.dms:Entity data record type on the TCP Context
Server, in addition to the specified ACL mapping configuration. Add the BAI user to
the EntityFullAccess group in OpenText User Management.
For details on ACL mapping configuration, see the “Permissions and ArchiveLink
interface” section in OpenText Transactional Content Processing: Customization
Guide (TCP-CGD).
8.2.5 DocuLink - SAP GUI for JAVA for MAC OS X

Problems with rendering
It is recommended to use the most recent patch level of SAP GUI for JAVA 7.20 on
MAC OS X to avoid unwanted issues with wrong UI rendering (e.g., wrong
rendering of background colors in list views)
Thumbnail view is not supported
The thumbnail view function is not supported with SAP GUI for JAVA on MAC OS X.
8.3 OpenText Imaging Integration

Behavior of Imaging Integration with /IXOS/OA_DOCTYPE
Starting with version 10.0.0 the standard behavior of OpenText imaging

integration was changed in the following way: if a document class is not
maintained in table /ixos/oa_doctype and if there is no special maintenance in
/ixos/oa_cust3, then the imaging integration exits to fall back to the setting of the
SAP communication protocols (as maintained in transactions in oaa3, oag1, etc.)
instead of doing a call browser with the standard ArchiveLink URL. In the case of
the DocuLink Web UI the fallback is to call the standard ArchiveLink URL.
49
Display of umlauts and other special characters in title of Web Viewer
The imaging integration transfers document type related descriptions to the Web
Viewer. To support special characters like umlauts (e.g., ä, ö, ü) the Web Viewer
must be set to support UTF-8 URI encoding. Please have a look at OpenText
Imaging Web Viewer Installation and Configuration Guide at the chapter
"Requirements" how to set the URIEncoding="UTF-8".
8.4 OpenText Imaging DesktopLink

Archiving via OpenText Imaging: DesktopLink
Sometimes the SAP logon window is opened behind all other windows. In this
case, use Alt-Tab to move the SAP logon window to the front.
Assigning multiple documents via OpenText Imaging: DesktopLink
The number of files that can be assigned with a single command via OpenText
Imaging: DesktopLink is limited, due to the technical restriction that command line
parameters may only contain up to 256 characters. Thus, the precise restriction
depends on the length of the file and path names of the documents to be
assigned.
SAP GUI Support
To avoid issues with older versions, please upgrade to SAP GUI 7.40 or higher.
8.5 OpenText Imaging Clients

Annotations on SAP print lists
The annotations functionality for SAP print lists is disabled for print lists displayed
without a page index. For further restrictions see OpenText My Support.
In-place viewing of TIF documents using OpenText Imaging: Windows Viewer
TIF documents stored within the SAP Content Management document model
cannot be displayed in-place in the HTML control of OpenText DocuLink for SAP
Solutions using OpenText Imaging: Windows Viewer.
8.6 Forms Management for ECR

Forms Management for Livelink ECM – PDMS Context Server 6.0C
Migrating forms maintained in SAP to a TCP Context Server is not supported
50
8.7 Business Content Window
Business Content Window
In SGOSATTR database table, the “Commit Required” field of the OTX_ATTACH

SAPRM-6570
service (Class for Generic Service = /OTX/RM_GOS_SRV_ATTACH_LIST) must be
unset, otherwise the Business Content Window might not open.
8.8 S/4HANA
Amount Field Length Extension (AFLE)
In S/4HANA 1809, currency amount fields between 9 and 22 digits, including 2

decimals, have been extended to 23 digits, including 2 decimals. Furthermore,
selected data elements of DDIC type DEC, CHAR, and NUMC that may hold
currency amounts have been extended as well.
Consequently, Content Server category attributes mapped to currency amount

properties might need to be enlarged.
8.9 Other Issues

Migration report
144870 The migration report /IXOS/RT_AL_SCENARIO only moves the main component,
not additional components such as notes, annotations, page index or attributes.
Migration report
The migration program /IXOS/RT_KPRO_SCENARIO (FUNCTION

/IXOS/RT_KPRO_BASIS) uses the same base functions as program RSIRPIRL.
LLSAPS-2570
Currently documents cannot be migrated with these programs if the logical
archive of the source and the logical archive of the target are located on the same
OpenText Archive Server.
ArchiveLink OLE Calls (Enterprise Scan) going wrong
Calls of applications like OpenText Enterprise Scan from SAP GUI transactions like
OAWD may go wrong or have issues, because of a wrong order of commands in
SAP Note
the customizing in transaction OAA4. This may be caused by an SAP bug, see SAP
2613144
Note 2613144. Please check whether the order of commands in transaction OOA4
is as suggested in the OpenText Archiving and Document Access for SAP Solutions
installation and scenario guides.
51
Cannot see any Layout _OTEB_BC_TEMPLATE_01 in Maintain Perspective tile
LLSAPS-3943
Apply the hot fix from the patches area.
8.10 Archive Center

A Content Server with Enterprise Library replacement (16.2.10 or higher) cannot
AS-18439 share an Archive Center with another Content Server still using Enterprise Library.
52
9 Troubleshooting
Troubleshooting describes some commonly encountered problems, with solutions or tips on how to
avoid them.
Table 18 - Troubleshooting
Problem Cause Solution
The formatting in the custom

columns of the document list is
as follows:
Dates and time are formatted
as defined in the user
maintenance (transaction
ArchiveLink PLUS Fiori app to SU01). The decimal numbers On the SAP frontend server
show business documents: The are formatted simply by using maintain the user defaults in
language setting does not have a dot (.) as the decimal transaction SU01 to match the
impact on formatting of date, delimiter. settings expected by the user.
time, and decimal point The formatting in the Edit
dialog is as follows:
Dates, time and decimal
numbers are formatted as
defined in the user
maintenance (transaction
SU01).
53
10 Contact Information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1
OpenText My Support: https://support.opentext.com
For more information, visit www.opentext.com
Copyright © 2021 Open Text. All Rights Reserved.

Trademarks owned by Open Text. One or more patents may cover this product. For more information, please visit https://www.opentext.com/patents.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However, Open Text Corporation and its affiliates accept no
responsibility and offer no warranty whether expressed or implied, for the accuracy of this publication.
54

OpenText Archiving and Document Access For SAP Solutions 21.4 Release Notes

Uploaded by

OpenText Archiving and Document Access For SAP Solutions 21.4 Release Notes

Uploaded by

OpenText™ Archiving and Document Access for

Product Released: 2021-11-19

Release Notes Revised: 2022-03-31

1.1 Release Notes Revision History

Revision Date Sections Revised Description of Revisions

2021-11-19 First release

2021-11-22 4.1.6 SAP Server Support Added S/4HANA 2021 support

2021-12-02 5.1.3 SAP Notes Added SAP notes 3126094 to address

2021-12-09 6.1 Hotfixes Added list of mandatory security hotfixes

2022-03-31 4.1.6.3 Required SAP Added missing information that OTEXERP

2.1 Discontinued and Deprecated Features

2.2 General Data Protection Regulation (GDPR)

3.1 Packaging and Delivery Information

3.1.1 Software Components

Group Component Version

Content Content Server

Archiving and Document Access for SAP® Solutions

Vendor Invoice Management Foundation

3.1.3 OpenText System Center

• Management of multiple environments

Please check the compatibilities depending on the version of the Process

SAP Backend OTBCBAS

SAP Gateway (Hub / Frontend) OTBCWUI

16.2.0 (16 EP2) Yes - - - - - - - - -

16.2.4 (16 EP4) - Yes Yes Yes - - - - - -

16.2.8 (16 EP6) - - - Yes Yes - - - - -

16.2.10 (16 EP7) - - - Yes Yes Yes Yes - - -

20.2 - - - Yes Yes Yes Yes - - -

20.3 - - - Yes Yes Yes Yes - - -

20.4 - - - - - - - Yes Yes Yes

21.2 - - - - - - - Yes Yes Yes

21.4 - - - - - - - Yes Yes Yes

3.2 Related Documentation

List of recommended documentation:

3.3.2 SAP Customers

3.4 Note on the End User License Agreement

• OpenText™ Data Archiving for SAP Solutions

Respectively with the SAP Solution Extensions:

• SAP Archiving by OpenText

3.4.1 Usage of DocuLink and of ArchiveLink PLUS

• OpenText™ Archiving and Document Access for SAP Solutions

• Usage allowed without extra licenses:

3.4.3 Usage of OpenText Content Server

3.4.4 Usage of Searchable PDF DocTool

3.4.5 Usage of Archive Center CMIS

3.5 Architecture Diagram

Figure 2 - Architecture Diagram

4.1 Supported Systems

• OpenText™ Imaging ExchangeLink

Windows IE 11 • OpenText DocuLink for SAP Solutions Web User

Non-Windows Firefox • Regarding Web Dynpro ABAP based applications, see

4.1.1.1 Support for Fiori Web User Interface

SAP Fiori Web User Interface restrictions

This mode is not supported.

MOB SAP Fiori Client:

4.1.2 Enterprise Library Discontinuation

• Extensions for Enterprise Library

4.1.4 Server Platform Support

4.1.6 SAP Server Support

Supported S/4HANA applications include the following:

SAP Platform OpenText Archiving and Document Access

All SAP systems running on the required SAP_BASIS versions, for

S/4HANA Applications 1610, 1709, 1809, 1909, 2020, 2021

4.1.6.3 Required SAP Support Packages

OpenText Software Prerequisite set1 of Software Support

SAP_BASIS 700 0018

Information is based on most recent packages or Attribute Change Packages (ACP).

For details about SAPUI5 versions on different SAP Releases read

OpenText Software Prerequisite set1 of Software Support

IW_BEP 200 0010

4.1.6.5 Fiori Business Object Browser Enabler Support

SAP Basis / 7.0 and

S/4HANA 7.0 and

Table 10 - Required Patches

Software Component Minimum Version Minimum Patch Level

Note: SAP GUI for HTML Support Restriction