OpenText™ Archiving and Document Access for

SAP Solutions
Release Notes
16.2

Product Released: 2017-03-31

Release Notes Revised: 2018-02-12

Contents
1 Introduction .......................................................................................................................... 1
1.1 Release Notes Revision History ................................................................................................. 1
2 About OpenText™ Archiving and Document Access for SAP Solutions...................................... 3
2.1 New features ............................................................................................................................. 3
2.2 Discontinued and deprecated features ..................................................................................... 3
3 Packaging and documentation ............................................................................................... 4
3.1 Packaging and delivery information .......................................................................................... 4
Software Components.................................................................................................. 5
Recommendation for OpenText™ Extended ECM for SAP Solutions 16.2
Installations .......................................................................................................... 6
OpenText™ Fiori Business Object Browsing for Document Access for SAP
Solutions 16.2 ....................................................................................................... 7
Updated Components .................................................................................................. 8
3.2 Related documentation............................................................................................................. 9
3.3 Delivery...................................................................................................................................... 9
OpenText Customers .................................................................................................... 9
SAP Customers ............................................................................................................. 9
3.4 Note on the End User License Agreement .............................................................................. 10
Usage of DocuLink and of ArchiveLink PLUS .............................................................. 10
Usage of OpenText™ Fiori Business Object Browsing Enabler for SAP
Solutions ............................................................................................................. 10
Usage of OpenText Content Server ............................................................................ 11
Usage of Searchable PDF DocTool.............................................................................. 11
Usage of OpenText Portal Content Management ...................................................... 11
4 Supported environments and compatibility .......................................................................... 12
4.1 Supported systems .................................................................................................................. 12
Client Platform Support.............................................................................................. 12
Citrix Support.............................................................................................................. 13
Server Platform Support............................................................................................. 13
SAP Server Support..................................................................................................... 14

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
i
 Supported SAP GUIs ................................................................................................... 21
Supported ArchiveLink Protocols ............................................................................... 22
WebDAV Storage Interface for SAP NetWeaver Information Lifecycle
Management ...................................................................................................... 22
4.2 OpenText Product Compatibility ............................................................................................. 22
4.3 Language support .................................................................................................................... 23
5 Installation and upgrade notes ............................................................................................. 25
5.1 Installation Notes .................................................................................................................... 25
Installation Requirements .......................................................................................... 25
BC Set Activation ........................................................................................................ 26
SAP Notes ................................................................................................................... 26
Enhancement Packages .............................................................................................. 27
CRM Package .............................................................................................................. 28
Configuring the AS ABAP for Supporting SSL ............................................................. 28
ArchiveLink Plus: Business Content Window ............................................................. 28
5.2 Content Server 16 License Keys .............................................................................................. 28
5.3 User License Type Assignment ................................................................................................ 28
5.4 Language Installation .............................................................................................................. 29
5.5 Upgrade notes ......................................................................................................................... 29
Upgrade planning ....................................................................................................... 30
Upgrade path.............................................................................................................. 31
5.6 OpenText Vendor Keys ............................................................................................................ 32
When to use exchange packages? ............................................................................. 32
When to use Attribute Change Packages? ................................................................. 32
When to use vendor keys? ......................................................................................... 32
OpenText™ Archiving and Document Access for SAP Solutions Vendor Keys ........... 33
5.7 Attribute Change Packages (ACPs) .......................................................................................... 33
What are Attribute Change Packages?....................................................................... 33
Where to obtain ACPs? .............................................................................................. 33
Version 16.2 ACP files................................................................................................. 33
6 Patches ................................................................................................................................ 34
6.1 Hotfixes.................................................................................................................................... 34

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
ii
 Hotfix installation ....................................................................................................... 34
Available Hotfixes ....................................................................................................... 34
6.2 Updates ................................................................................................................................... 34
ABAP Support Package installation ............................................................................ 34
Available ABAP Support Packages .............................................................................. 34
7 Fixed Issues ......................................................................................................................... 36
8 Known Issues ....................................................................................................................... 37
8.1 Accessibility ............................................................................................................................. 37
8.2 DocuLink for SAP Solutions ..................................................................................................... 37
DocuLink - Table and Field Restrictions...................................................................... 40
Doculink - Visualization .............................................................................................. 42
DocuLink - SAP GUI for HTML ..................................................................................... 43
DocuLink - Business Application Integration (BAI) ..................................................... 43
DocuLink - SAP GUI for JAVA for MAC OS X ............................................................... 45
8.3 OpenText Imaging Integration ................................................................................................ 45
8.4 OpenText Imaging DesktopLink............................................................................................... 46
8.5 OpenText Brava! View for SAP Solutions ................................................................................ 46
8.6 OpenText Imaging Clients ....................................................................................................... 47
8.7 Forms Management for ECR ................................................................................................... 47
8.8 Business Content Window ...................................................................................................... 47
8.9 Fiori Business Object Browser ................................................................................................. 47
8.10 Other Restrictions ................................................................................................................... 48
9 Troubleshooting .................................................................................................................. 49
10 Contact information ............................................................................................................. 50

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
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 ... 5
Table 3 - Add-ons of OpenText™ Fiori Business Object Browsing Enabler for SAP Solutions 16.2 ........ 8
Table 4 - Client Platform Support ......................................................................................................... 12
Table 5 - Supported SAP Business Suite and S/4 HANA Applications .................................................. 14
Table 6 - Required SAP Components and Patches ............................................................................... 15
Table 7 - Required SAP Components and Support Packages for Fiori UI Support ............................... 18
Table 8 - Required SAP Components and Support Packages for Business Object Browsing Enabler .. 20
Table 9 - Supported SAP GUIs .............................................................................................................. 21
Table 10 - Required Patches ................................................................................................................. 22
Table 11 - OpenText Product Compatibility ......................................................................................... 23
Table 12 - Language Support (1/2) ....................................................................................................... 23
Table 13 - SAP (OSS) Notes ................................................................................................................... 26
Table 14 - Available Hotfixes ................................................................................................................ 34
Table 15 - Available ABAP Support Packages ....................................................................................... 35
Table 16 - Fixed Issues .......................................................................................................................... 36
Table 17 - Known Issues ....................................................................................................................... 37
Table 18 - Troubleshooting................................................................................................................... 49

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
iv
Table of Figures
Figure 1- Main Components of OpenText™ Archiving and Document Access for SAP Solutions .......... 4

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
v
1 Introduction
These release notes provide an overview of OpenText™ Archiving and Document Access for SAP
Solutions 16.2, 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 (https://knowledge.opentext.com/).

We also recommend that you check OpenText My Support (https://knowledge.opentext.com/) 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

2017-03-31 First release

2017-04-10 4.1.4.4 Fiori UI Support Added new Attribute Change Packages (ACP)
to support SAP Frontend Server with
NetWeaver 7.51

2017-04-20 3.1 Packaging and Updated component diagram

delivery information

2017-05-03 3.1.1 Software Added Monitoring Agent 16.2.0

Components

2017-05-08 3.1.4 Updated Added component updates

Components

2017-05-24 3.1.1 Software Removed foot note; added SAP Add-On

Components packages

2017-06-30 4.3 Language support Released German, French, Italian, and

Spanish localization

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
1
 2017-07-13 4.3 Language support Released Arabic, Chinese (Simplified),
Danish, Dutch, Japanese, Norwegian, Polish,
Portuguese, Russian, Turkish and Ukrainian
localization

4.1.5 Supported SAP Added SAP GUI for Windows 7.50 support
GUIs

2017-07-31 4.3 Language support Released Traditional Chinese localization

2017-08-02 4.3 Language support Released Korean localization

2017-09-26 4.1.4 SAP Server Support Added requirements for SAP GUI for
Windows 7.50 support

2017-09-29 2.1 New features Improved list of new features

2017-10-02 4.3 Language support Released Kazakh localization

2017-11-09 4.1.4 SAP Server Support Added S/4HANA On-Premise 1709 support

2018-01-22 5.1 Installation Notes Added warning: Enterprise Library Services

16.2 is incompatible with Content Server
16.2.2

2018-01-30 4.1.4 SAP Server Support Added SAP components for S/4HANA 1709

2018-02-12 3.1.1 Software Reduce list of software components to

Components reflect license perspective

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
2
2 About OpenText™ Archiving and Document Access for SAP
Solutions
This section provides an overview of OpenText™ Archiving and Document Access for SAP Solutions
16.2.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 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 16.2 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 New features

OpenText™ Archiving and Document Access for SAP Solutions 16.2 includes the following new
features.

• ArchiveLink PLUS – new properties can be mapped to ArchiveLink attributes during file upload
• Current local date and time of SAP logon user
• ID of SAP logon user
• Fiori Business Object Browsing for OpenText Document Access for SAP Solutions.
• Fiori Business Documents enter bar code; bar code recognition, if run on mobile device with the
SAP MOB Fiori client.
• License Report: New license types for SAP Reselling Document Access and Archiving; set
“occasional” limit to 52 days per year.
• Asynchronous migration report

2.2 Discontinued and deprecated features

No features have been discontinued or deprecated in this release.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
3
3 Packaging and documentation
Downloads and documentation for OpenText™ Archiving and Document Access for SAP Solutions are
available on OpenText My Support (https://knowledge.opentext.com/).

3.1 Packaging and delivery information

The bundle OpenText™ Archiving and Document Access for SAP Solutions consists of many individual
components. For your convenience, this bundle is delivered in a single ISO-Image.

• 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

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
4
 Software Components
The following table lists all components of OpenText™ Archiving and Document Access for SAP
Solutions 16.2. The majority of software components can be installed via the master setup. The last
column in the table indicates whether a component can be installed by using OpenText™ Archiving
and Document Access for SAP Solutions master setup.
Table 2 - Detailed Component List of OpenText Archiving and Document Access for SAP Solutions
Master
Group Component Version
Setup
Content Server
Use of Content Server is restricted to the scenarios
ILM (Information Lifecycle Management) and
ArchiveLink PLUS, i.e fulltext search. Content Server 16.2 Yes
Document Management and Content Server Records
Content Server and Management are expressively not considered a
Modules legitimate use of the software.
Extensions for Enterprise Library 16.2.0 Yes
Monitoring Agent 16.2.0 No
Records Management 16.2.0 Yes
Archive Cache Server 16.2.0 Yes
Archive Center 16.2.0 Yes
Archive Center and
Archive Monitoring Server and Web Client 16.2.0 Yes
Components
Archive Spawner 16.2.0 No
Solution Registry Agent 16.2.0 Yes
Document Pipeline Base 16.2.0 Yes
Document Pipeline for Archive Center 16.2.0 Yes
Document Pipeline for DocuLink 16.2.0 Yes
Document Pipeline for SAP Solutions 16.2.0 Yes
Document Pipelines
Document Pipeline Info 16.2.0 Yes
Document Pipeline Perl 16.2.0 Yes
Document Pipeline Remote Interface 16.2.0 Yes
Searchable PDF DocTool 16.2.0 No
Brava! View for SAP Solutions 16.2.0 No

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
5
 Master
Group Component Version
Setup
Directory Services (OTDS) 16.2.0 Yes
Other Servers & Enterprise Library Services 16.2.0 Yes
Services
Extended ECM Web Services 16.2.0 Yes
Imaging Web Viewer 16.0.0 No
Administration Client 16.2.0 Yes
Imaging Enterprise Scan 16.2.0 No
Imaging ExchangeLink 16.0.0 Yes
Clients
Imaging NotesLink 16.0.0 Yes
Imaging PDF Extensions 16.0.0 Yes
Imaging Windows Viewer and DesktopLink 16.0.0 Yes

Extended ECM
Enabler for SAP® Archiving and Document Access for SAP® Solutions 16.2 No
Solutions
(SAP® Add-on Extended ECM for SAP® Solutions 16.2 No
packages)

The ISO image may contain more components than listed in this table. For detailed information
about individual components of OpenText™ Archiving and Document Access for SAP Solutions,
please have a look at the respective release notes.

Recommendation for OpenText™ Extended ECM for SAP Solutions 16.2

Installations

Note
We strongly recommend using OpenText Cluster Management Patch
Deployment System to keep your Content Server 16.2 (or higher) up-to-
date with the latest patches for Content Server and modules.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
6
 OpenText™ Fiori Business Object Browsing for Document Access for SAP
Solutions 16.2
OpenText™ Fiori Business Object Browsing for Document Access for SAP Solutions 16.2 is a collective
term, which includes the following:

• OpenText™ Archiving and Document Access for SAP Solutions 16.2

• OpenText™ Fiori Business Object Browsing Enabler for SAP Solutions 16.2: a collection of
ABAP Add-Ons of OpenText™ Business Center for SAP Solutions 16 Update 1. These are
required to build custom Fiori apps to browse for business objects. The required Add-Ons
are available in the patches area of OpenText My Support.
• Solution Accelerator Fiori Business Object Browsing for Document Access and Extended ECM
for SAP Solutions: it is released in OpenText Developers Network (OTDN) and in OpenText
My Support, which provides you with example configurations and implementations which
run against an SAP ERP 6.0 system as a minimum SAP Backend.

Please note, that the scenarios of OpenText™ Fiori Business Object Browsing for Document Access
for SAP Solutions can also be used against all SAP back ends matching the criteria of chapter 4.1.4.5
Fiori Business Object Browsing Enabler Support.

Table 3 - Add-ons of OpenText™ Fiori Business Object Browsing Enabler for SAP Solutions 16.2 lists,
which ABAP Add-on packages of OpenText™ Business Center for SAP Solutions 16 Update 1 are
required for the framework to build custom Fiori apps:

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
7
Table 3 - Add-ons of OpenText™ Fiori Business Object Browsing Enabler for SAP Solutions 16.2

Target System ABAP Add-On

SAP Backend OTBCBAS 0700_003

OTBCBAS 0700_003 Support Package 1 (SP1)

OTBCINB 0700_003
OTBCINB 0700_003 SP1

OTBCFND 0700_003
OTBCFND 0700_003 SP1

OTBCWSR 0740_003
OTBCWSR 0740_003 SP1

OTBCWUI 0740_003
SAP Gateway (Hub / Frontend) OTBCWUI 0740_003 SP1
OTBCWUI 0740_003 SP2

Important
Usage restrictions are detailed in chapter 3.4.2

Usage of Supported SAP platforms and requirements are detailed in chapter

4.1.4.5 Fiori Business Object Browsing Enabler Support.

Please read the Release Notes, installation guide and configuration guide of
OpenText™ Business Center for SAP Solutions 16 Update 1 to learn about
the details of installation and configuration and regarding mandatory actions
after upgrading from OpenText™ Business Center for SAP Solutions 16.
You can find them here at the OpenText™ Knowledge Center.

Updated Components
On OpenText My Support, the product-specific patch area offers an Updated Components folder
that contains the following updates:

• Document Pipeline for Content Server 16.2.0

• Imaging Enterprise Scan 16.2.0

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
8
 • Imaging Enterprise Scan Web Interface 16.2.0
• Monitoring Agent 16.2.0
• Searchable PDF DocTool 16.2.0

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 (https://knowledge.opentext.com/).

List of recommended documentation:

• OpenText™ Archiving and Document Access for SAP Solutions - Scenario Guide (ER160200-
00-CCS-EN-1)
• OpenText™ Archiving and Document Access for SAP Solutions - Installation Guide
(ER160200-00-IGD-EN-1)
• OpenText™ DocuLink for SAP Solutions - Customizing and Administration Guide (DC160200-
00-CGD-EN-1)
• OpenText™ DocuLink for SAP Solutions - User Guide (DC160200-00-UGD-EN-1)

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 16.2are a good starting point. They contain a list of recommended
documentation, as well.

3.3 Delivery
OpenText Customers
OpenText customers can download OpenText™ Archiving and Document Access for SAP Solutions
16.2 from the “Download” section of OpenText My Support.

SAP Customers
SAP customers can download OpenText™ Archiving and Document Access for SAP Solutions 16.2
from the SAP Support Portal, SAP Software Download Center. At the SAP Software Download Center,
the software is listed under SAP EXTENDED ECM BY OPEN TEXT, SAP EXTENDED ECM BY OT 16.2.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
9
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™ Document Access for SAP Solutions
• OpenText™ Extended ECM for SAP Solutions

Respectively with the SAP Solution Extensions:

• SAP Archiving by OpenText

• SAP Document Access by OpenText
• SAP Extended Enterprise Content Management (ECM) by OpenText

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™ Document Access for SAP Solutions

• OpenText™ Extended ECM for SAP Solutions
• SAP Document Access by OpenText
• SAP Extended Enterprise Content Management (ECM) by OpenText

Usage of OpenText™ Fiori Business Object Browsing Enabler for SAP Solutions
OpenText™ Fiori Business Object Browsing Enabler for SAP Solutions adds the Business Center
Foundation of OpenText™ Business Center for SAP Solutions 16 Update 1 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:

• Business Center Foundation

o Browse business objects in the Fiori Web UI of Business Center Workplace
o The supported customizing options and enhancements are described in OpenText™
Business Center for SAP Solutions Configuration Guide
• The following usages need extra licenses for OpenText™ Business Center for SAP Solutions:
o Solution accelerators specifically designed for preconfigured processes of Business
Center, like incoming sales orders, purchase order/ purchase requisition dashboard,
incoming delivery notes or incoming HT documents

o Business Center Foundation for

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
10
 ▪ Import
▪ Capture (OpenText Business Center Capture for SAP Solutions)
▪ Dispatch
▪ Process
o In the case of doubts, the license report of OpenText Business Center can be
executed to find out, if the framework is used in a way, which needs additional
licenses for OpenText™ Business Center for SAP Solutions
• The integration of the Business Documents Fiori App is restricted to the following licensed
products:
o OpenText™ Document Access for SAP Solutions
o SAP Document Access by OpenText

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)

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
for documents manually scanned in with Enterprise Scan. Batch conversion of imported images is
expressively not considered a legitimate use of the software.

Usage of OpenText Portal Content Management

Usage of OpenText™ Portal Content Management is not allowed at all. Portal Content Management
is expressively not considered a legitimate use of the software.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
11
4 Supported environments and compatibility
This section provides details about supported platforms, systems, and versions.

4.1 Supported systems

Client Platform Support
For information and restrictions concerning operating systems please have a look at the release
notes of:

• OpenText™ Imaging NotesLink

• OpenText™ Imaging ExchangeLink
• OpenText™ Imaging Viewers and DesktopLink
• OpenText™ Imaging Enterprise Scan
• Brava! View for SAP Solutions

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 4 - 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
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

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
12
https://support.sap.com/pam for details.
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 Business Center Fiori Web User Interface for business object browsing, then
please also read the related chapter in the Release Notes of OpenText™ Business Center 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 also refreshes it.

Citrix Support
To find out which OpenText™ Archiving and Document Access for SAP Solutions components
support Citrix, please refer to their respective release notes.

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 information and restrictions concerning operating systems and database systems please have a
look at the release notes of OpenText Content Suite Platform 16.2.

Components such as OpenText Archive Center may support more platforms than the Content Suite
Platform as a whole (see below).

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
13
The ISO image for OpenText™ Archiving and Document Access for SAP Solutions 16.2 is available for
Windows and Linux.

In the download area of OpenText My Support, these images are:

• Archiving and Document Access for SAP Solutions 16.2 Windows (ISO image file)
[file name ada_16.2.0_win64.iso]
• Archiving and Document Access for SAP Solutions 16.2 Linux (ISO image file)
[file name: ada_16.2.0_rhel6.iso]

SAP Server Support

4.1.4.1 Supported SAP Business Suite and S/4HANA Applications
Table 5 - 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:
SAP Netweaver > 7.0 • EhP4-8 for ERP 6.0
EhP 1 - 2 for SAP NetWeaver
• CRM 7.0
7.0
EhP 1 for SAP NetWeaver 7.3 • EhP1-4 for CRM 7.0
SAP NetWeaver 7.40
SAP NetWeaver 7.50, 7.51, • SRM 7.0
7.52
• EhP1-4 for SRM 7.0
• SFINANCIALS 1.0 or 1503 (SAP_FIN 700 or 720)

S/4HANA On-Premise 1511, 1610, 1709

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
14
4.1.4.2 SAP HANA Support

OpenText™ Archiving and Document Access for SAP Solutions 16.2 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.4.3 Required SAP Support Packages

Table 6 - Required SAP Components and Patches

Support
OpenText Software Prerequisite set1 of
Software Component Release Package
Component OpenText Add-On
Level

700, 702, SAP_BA

Prerequisite set 01 SAP_BASIS 731, 740, SIS 700:
750 0016
Archiving and Document
Access for SAP® Solutions 750, 751,
SAP_BASIS
OTEXBAS 1620_700 752
Prerequisite set 02
75A, 75B,
SAP_ABA
75C

OTEXBAS 1620

Prerequisite set 01 700 - 702, SAP_BA

SAP_BASIS 731, 740, SIS 700:
Extended ECM for SAP® 750 0016
Solutions (used for
Business Content OTEXBAS 1620_700
Window, Fulltext Search)
OTEXRL 1620_700 75A, 75B,
SAP_ABA
Prerequisite set 02 75C

750, 751,
SAP_BASIS
752

Prerequisite set 01 OTEXBAS 1620_700

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
15
 600 –
SAP_APPL 606, 616 -
618

700 - 702, SAP_BA

SAP_BASIS 731, 740, SIS 700:
750 0016

OTEXBAS 1620_700
Archiving and Document
700 - 702, SAP_BA
Access for SAP® Solutions SAP_BASIS 731, 740, SIS 700:
for ERP Prerequisite set 02
750 0016
OTEXERP 1620_600
617, 618,
SAP_FIN
700, 720

OTEXBAS 1620_700

S4CORE 100 - 102

Prerequisite set 03 75A, 75B,

SAP_ABA
75C

750, 751,
SAP_BASIS
752

BBPCRM 700 - 704

Archiving and Document
Access for SAP® Solutions OTEXBAS 1620_700
for CRM Prerequisite set 01
701, 702,
OTEXCRM 1620_700 SAP_BASIS 731, 740,
750

See
Extended ECM for SAP® BBPCRM 700 - 704 special
Solutions for CRM Prerequisite set 01 note
OTEXRLC 1620_700
OTEXRL 1620_700

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
16
 (OTEXBAS) (1620_70
0)

701, 702,
SAP_BASIS 732, 740,
750

Although not explicitly added as an import

condition of OTEXRLC, the following
requirements must be met:
CRM 7.0 SP Stack 02 (SAP_BASIS 701 0003,
SAP_ABA 701 0003, BBPCRM 700 02,
Special WEBCUIF 700 0002)
requirements
See SAP OSS Notes:
1625333 - SP Equivalence for update/upgrade
to EHP 1 for SAP CRM 7.0
1625284 - SP Equivalence for update/upgrade
to EHP 2 for SAP CRM 7.0

1620_700
OTEXRL
(1620_70
(OTEXBAS)
0)

Prerequisite set 01 701, 702,

SAP_BASIS 731, 740,
750
Extended ECM for SAP® SRM_SERVER 700 - 704
Solutions for SRM
OTEXRLS 1620_700 Although not explicitly added as an import
condition of OTEXRLS, the following
requirements must be met:
Special SRM 7.0 SP Stack 08 (SAP_BASIS 701 0007,
requirements SAP_ABA 701 0007, SRM_SERVER 700 0008)

See SAP OSS Notes:

1494683 - SAP SRM 7.0 Enh.Pk.1 SP Stacks -
Release & Information Note

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
17
 1582094 - EHP2 for SAP SRM 7.0 SP stacks -
Release & Information Note

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.
SPAM/SAINT Version: Although the extended requirements of some of the ABAP Add-Ons above
may require lower version values, a minimum version of 0059 is recommended. This may also
change with the delivery of future Attribute Change Packages (ACP).

4.1.4.4 Fiori UI Support

The SAP Fiori apps of OpenText™ Archiving and Document Access for SAP Solutions 16.2 require a
minimum SAPUI5 runtime version 1.38.9.
Though, this is not enforced by import conditions. SAPUI5 1.3.8.9 is based on SAP_UI 750.

• Read SAP Note 2227501 about the minimal installation requirements for SAP_UI 7.50
• Read SAP Note 2361404 regarding SAPUI5 upgrade to version 1.38.9.

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. See Table 7 for detailed requirements.
Table 7 - Required SAP Components and Support Packages for Fiori UI Support

Support
OpenText Software Prerequisite set1 of
Software Component Release Package
Component OpenText Add-On
Level

IW_BEP 200 0010

Prerequisite set 01 SAP_BA

700 – 02,
SAP_BASIS SIS 700:
731
0018

Archiving and Document SAP_BASIS 740

Access for SAP® Solutions
OTEXBASO 1620_700 SAP_G
Prerequisite set 02²
WFND
SAP_GWFND 740, 750
740:
0009

75A, 75B,
Prerequisite set 03 SAP_ABA
75C

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
18
 750, 751,
SAP_BASIS
752

750, 751,
SAP_GWFND
752

SAP_BASIS 740, 750

Prerequisite set 01² SAP_UI

SAP_UI 740, 750 740:
0013
Error! Unknown
document property 75A, 75B,
name. Fiori Apps SAP_ABA
75C
OTEXBASF 1620_740
750, 751,
Prerequisite set 02² SAP_BASIS
752

750, 751,
SAP_UI
752

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.
²Attribute Change Package (ACP): The most recent (ACP) from the patches area is required for
SAP Frontend Server with NetWeaver 751.
SPAM/SAINT Version: Although the extended requirements of some of the ABAP Add-Ons above
may require lower version values, a minimum version of 0059 is highly recommended. This may
also change with the delivery of future Attribute Change Packages (ACP).

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
19
4.1.4.5 Fiori Business Object Browsing Enabler Support

SAP Fiori apps build with OpenText™ Business Center for SAP Solutions 16 Update 1 require a
minimum SAPUI5 runtime version 1.38.9.

Therefore the SAPUI5 Runtime 1.38.9 must be installed based on SAP_UI 750.

The OData services of Business Center and Document Access need either the enablement
component IW_BEP 200 or the gateway foundation component SAP_GWFND 740 on the SAP Back-
End server. See Table 8 for detailed requirements.

Table 8 - Required SAP Components and Support Packages for Business Object Browsing Enabler

Support
OpenText Software Prerequisite set1 of
Software Component Release Package
Component OpenText Add-On
Level

700,
SAP_BASIS 701,
702,
Prerequisite set 01
Business Object Browsing 731
Enabler - SAP Backend
IW_BEP 200 0010
OTBCBAS 0700_003
OTBCBAS 0700_003 SP1 SAP_BASIS
740
OTBCINB 0700_003
OTBCINB 0700_003 SP1 Prerequisite set 02
SAP_GWFND
OTBCFND 0700_003 740 0010
OTBCFND 0700_003 SP1
OTBCWSR 0740_003 SAP_BASIS
OTBCWSR 0740_003 SP1 750
Prerequisite set 03
SAP_GWFND
750

SAP_BASIS 740 0008

Business Object Browsing
Enabler - SAP Gateway Prerequisite set 01 SAP_GWFND 740 0010
(Hub / Frontend)
SAP_UI 750

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
20
 OTBCWUI 0740_003 (update to minimum
OTBCWUI 0740_003 SP1 SAPUI5 1.38.9
OTBCWUI 0740_003 SP2 required)

Requires SAP Notes: 2361404, 2227501

SAP_BASIS 750
SAP_UI
(update to minimum
SAPUI5 1.38.9
Prerequisite set 02 750
required)

Requires SAP Notes: 2361404, 2227501

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.
SPAM/SAINT Version: Although the extended requirements of some of the ABAP Add-Ons above
may require lower version values, a minimum version of 0059 is highly recommended. This may
also change with the delivery of future Attribute Change Packages (ACP).

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)

5.0 Stand-
7.0 7.40, 7.50 Integrated -
alone

SAP Basis / EhP1-2 for

NetWeaver NW 7.0, EhP1 7.40, 7.50 Integrated 5.0 -
for NW 7.3

7.4 7.40, 7.50 Integrated 5.0 -

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
21
 7.5, 7.51 7.40, 7.50 Integrated 5.0 -

Table 10 - Required Patches

Software Component Minimum Version Minimum Patch Level

7.40 3
SAP GUI for Windows
2 - See SAP note 1258724 for additional
7.50
requirements
SAP GUI for Windows and NWBC versions for which SAP support ended are not listed here anymore.
The following documentation provides additional NWBC usage information:

• SAP Library: NWBC Versions

• SAP OSS Note 2066345 – NWBC for Desktop 5.0: Prerequisites and restrictions

Supported ArchiveLink Protocols

The ArchiveLink protocols 4.5 and 4.6 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.

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 and BC-ILM 3.0 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 16.2.

Note: For the latest compatibility information for OpenText products, refer to the Compatibility
Matrix (https://knowledge.opentext.com/go/matrix) on OpenText My Support.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
22
Table 11 - OpenText Product Compatibility

Product Name Version Notes

OpenText™ Extended ECM for SAP Solutions 16.2

OpenText Extended ECM Platform 16.2

Content Suite Platform 16.2

4.3 Language support

OpenText™ Archiving and Document Access for SAP Solutions is currently available in the following
languages. Additional language support should be available in July 2017.
Table 12 - Language Support (1/2)

Components

AR DA DE EN ES FR IT JA KK KO NL NO PO PT RU TR UK ZF ZH

End-user
X X X X X X X X X X X X X X X X X X X
Interface

User Guide X X X X X X X X X

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
23
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 be available in (ABAP) language packs.

In many cases, administrative user interfaces are only available in English.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
24
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.

Caution
Enterprise Library Services 16.2 is incompatible with Content
Server 16.2.2. Should you currently use this combination, please
upgrade Content Server and modules to a newer version.

Installation Requirements

All installation steps are described in OpenText™ Archiving and Document Access for SAP Solutions -
Installation Guide (ER160200-00-IGD-EN-1).

Also consider the software requirements mentioned in 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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
25
 Table TAORA
TABART USER / USER1
Table IAORA
TABART USER / USER1.

BC Set Activation

OpenText™ Archiving and Document Access for SAP Solutions - Installation Guide (ER160200-00-IGD-
EN-1) lists SAP notes which have to be applied to avoid issues with the activation of Business
Configuration (BC) sets. If you still experience errors when activating BC sets, even if you did as
described, customizing transports are available in the KC (https://knowledge.opentext.com) which
correlate to the settings activated with the BC sets.

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 37 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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
26
 SAP (OSS) Note Required for

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 URL's on
other platforms than Windows. And then the settings of the MS
Internet Explorer govern the behavior, whether a new window is
opened.

This note prevents a dump screen in the Business Content

1713851 Window when one tries to open a record, gets a 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 trhe case of non-unicode systems, the related notes
referenced in SAP Note 1582867 should be applied.

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.

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 1511, 1610,
and 1709.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
27
 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 Guide (ER160200-00-IGD-EN-1).

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

ArchiveLink Plus: Business Content Window

The ABAP functionality is included in the Add-On OTEXRL of OpenText™ Extended ECM for SAP
Solutions 16.2 and also requires other components of OpenText™ Extended ECM for SAP Solutions
16.2.

Therefore the same version and compatibility restrictions apply as for OpenText™ Extended ECM for
SAP Solutions 16.2.

Please refer to the chapter about OPENTEXT BUSINESS CONTENT WINDOW in OpenText™ Archiving
and Document Access for SAP Solutions - Scenario Guide (ER160200-00-CCS-EN-1) and the related
documentation of for OpenText™ Extended ECM for SAP Solutions 16.2.

5.2 Content Server 16 License Keys

Please read Content Server licensing 16 FAQ on OpenText My Support to learn about Content
Server 16 license keys/files.

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 User License Type Assignment

OpenText™ Archiving and Document Access for SAP Solutions 16.2 has functionality to gather
specific licensed user data, like product-related license types and usage statistics, from one or more
SAP servers. A license report consolidates this information.

On the SAP server, one creates roles using the J_6NLC_TYP authorization object to assign license
types to users. Every licensed user must get a license type (e.g. full, professional, occasional). The F4
help of the /OTX/CLTYP field of authorization object J_6NLC_TYP provides the complete list of
available license types.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
28
An example of type is “OpenText Document Access - Named User (ID = ODOCF)”. This type indicates
usage of OpenText Document Access.

Please read OpenText™ Archiving and Document Access for SAP Solutions - Scenario Guide
(ER160200-00-CCS-EN-1) for detailed information about OpenText License Report.

5.4 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 16.2. Other languages are available as
language packs or language module versions on OpenText My Support.

Notice: For all components, installing the English version is a pre-requisite to installing a localized
version.

5.5 Upgrade notes

In addition to the description given in OpenText™ Archiving and Document Access for SAP Solutions -
Installation Guide (ER160200-00-IGD-EN-1) 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 16.2

Warning
If you import an upgrade into an SAP system with OpenText™ Archiving and
Document Access for SAP Solutions 16.2 and the data of the respective upgrade
packages is not read (upgrade phase IS_SELECT), OpenText™ Archiving and
Document Access for SAP Solutions 16.2 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 Guide (ER160200-00-IGD-EN-1), the existing Add-ons
are kept ("KEEP" in upgrade phase IS_SELECT).

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
29
 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
(https://knowledge.opentext.com).
• Patch dependencies when upgrading (pre 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).

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 to do 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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
30
 • 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
OpenText™ Archiving and Document Access for SAP Solutions 16.2 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 to do the exchange upgrade with older OpenText
versions (like 9.8 or 10.0) and then to do a plain installation of version 16.2 on the target
release. Please check on OpenText™ Archiving and Document Access for SAP Solutions -
Installation Guide (ER160200-00-IGD-EN-1).

Upgrade path
5.5.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 actually 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.5.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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
31
5.5.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
OTEXBAS 9.8 in its package parameters.
After that, you can continue installing the newer Add-Ons on the path.

5.6 OpenText Vendor Keys

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
to do 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.

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

When to use vendor keys?

You already have installed Add-On packages of version 16.2 on an SAP System with SAP NetWeaver
7.0 to SAP NetWeaver 7.5. You have to 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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
32
 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.7 Attribute Change Packages (ACPs)

What are Attribute Change Packages?
Read SAP Note 1119856 for description, tips and tricks for Attribute Change Packages

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
(https://knowledge.opentext.com)

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.

Version 16.2 ACP files

You will find the most recent ACP files related to version 16.2 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 (https://knowledge.opentext.com):

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
33
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 16.2. OpenText recommends that you check OpenText My Support
(https://knowledge.opentext.com/) 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.

Hotfix installation
No hotfixes are available at the moment.

Available Hotfixes
The following table lists and describes the hotfixes available for this release.
Table 14 - Available Hotfixes

Hotfix Name Additional Info Downloads

6.2 Updates
Updates consist of a number of 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.

ABAP Support Package installation

On client 000 of the target SAP system use transaction SPAM to install the ABAP support packages.

Available ABAP Support Packages

The following table lists and describes the SAP (ABAP) support packages available for this release.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
34
Table 15 - Available ABAP Support Packages
Support Package Name Additional Info Downloads

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
35
7 Fixed Issues
This section provides information about past issues that have been fixed in this release.
Table 16 - Fixed Issues

Issue Number Issue Description

Display problems using embedded view of Web Viewer 10.x or higher and
LLSAPS-3539
Internet Explorer 11 in DocuLink

LLSAPS-3547 Delete generated reports in J6NA does not work when saving variants

LLSAPS-3563 Insert of additional table entries not working cross client

LLSAPS-3572 Call of Java Viewer causes Error Dump

Use of “open nodes automatically” in copies of the Employee File Management

LLSAPS-3574
project may cause dump in function AC_SYSTEM_FLUSH

License Report: correct reseller count in PDF output in sections of single CS and
SAPRM-8773
SAP instances

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
36
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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
37
 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 behaviour 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
behaviour). If, however, you now go back and enter a valid selection, the resulting
hit list is still empty. You have to 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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
38
 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:
LLSAPS-5871
• personalisation 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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
39
 Table maintenance for DocuLink sample project $EX_FI1

The maintenance data of the /IXOS/DC_EX_GJAH table is not populated

automatically. Therefore this table has to 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.

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.

1
$EX_FI an optional example DocuLink project which may be downloaded
from the KC (https://knowledge.opentext.com).

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
40
 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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
41
 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.

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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
42
 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, EnterpriseScan.

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

In order to display columns in a hit list correctly, a fixed font has to 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 inplace

FAX documents can only be displayed inplace using OpenText Imaging: Windows
Viewer.

Archiving documents via front-end

Archiving scenarios do not work with SAP GUI for HTML.

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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
43
 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 is 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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
44
 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).

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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
45
 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.

8.5 OpenText Brava! View for SAP Solutions

Brava! View for SAP Solutions restrictions

The following functions are currently not supported by

Brava! View for SAP Solutions:

• Display of ALF (print list) or OTF documents

• Display of Form Overlays
• Thumbnail view in DocuLink
• Thumbnail view in Business Content Window - Business Documents (that
is the ArchiveLink attachment list)
• document compare and merge is not possible

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
46
 8.6 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:
https://knowledge.opentext.com.

Java Viewer inplace in DocuLink view

Please use a version of Java Viewer of at least 10.0 to avoid issues or use the old
SAP GUI visual design (option in the SAP Configuration settings), or disable the
inplace view for DocuLink (setting in view header data).

Inplace viewing of TIF documents using OpenText Imaging: Windows Viewer

TIF documents stored within the SAP Content Management document model
cannot be displayed inplace in the HTML control of OpenText DocuLink for SAP
Solutions using OpenText Imaging: Windows Viewer.

8.7 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

8.8 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.9 Fiori Business Object Browser

Compatibility with S/4HANA 1709

The current included version of Fiori Business Object Browser is not compatible
with S/4HANA 1709.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
47
 8.10 Other Restrictions
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.

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
48
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).

OpenText™ Archiving and Document Access for SAP Solutions 16.2 Release Notes
49
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 © 2017 Open Text. All Rights Reserved.

Trademarks owned by Open Text. The list of trademarks is not exhaustive of other trademarks, registered trademarks, product names, company names, brands and service names
mentioned herein are property of Open Text or other respective owners.

50