OpenText Archiving and Document Access For SAP Solutions 10.5 Release Notes

OpenText Archiving and Document
Access for SAP Solutions Release Notes

10.5.0
2018-07-11
Contents
1 Introduction .................................................................................................................................... 5
1.1 Release Notes Revision History ................................................................................................ 5
2 About OpenText Archiving and Document Access for SAP Solutions .................................... 8
2.1 What is OpenText Archiving and Document Access for SAP Solutions? .................................. 8
2.2 What's new in this release? ....................................................................................................... 8
2.3 Discontinued and Deprecated Features .................................................................................... 9
3 Packaging and Documentation .................................................................................................. 10

3.1 Packaging and Delivery Information ........................................................................................ 10
3.1.1 Software Modules in Master Setup 10.5.0 ................................................................. 10
3.1.2 Third Party Software ................................................................................................... 12
3.1.3 OpenText Customers .................................................................................................. 13
3.1.4 SAP customers ........................................................................................................... 13
3.2 Note on the End User License Agreement .............................................................................. 13
3.2.1 Usage of DocuLink and of ArchiveLink PLUS ............................................................ 13
3.2.2 Usage of OpenText Content Server ........................................................................... 14
3.2.3 Usage of Searchable PDF DocTool ............................................................................ 14
3.2.4 Usage of OpenText Portal Content Management....................................................... 14
3.2.5 Usage of ExchangeLink and NotesLink ..................................................................... 14
3.3 Related Documentation ........................................................................................................... 14
3.4 Documentation Errata .............................................................................................................. 15
3.5 Language Support ................................................................................................................... 16
4 Supported Environments and Compatibility ............................................................................. 17

4.1 Compatibility Matrix ................................................................................................................. 17
4.2 Supported Server Operating Systems, and Java Runtime Environments .............................. 17
4.2.1 Server Operating Systems ......................................................................................... 17
4.2.2 Supported Java Runtime Environments ..................................................................... 18
4.3 Supported Client Operating Systems ...................................................................................... 18
4.4 Supported SAP Systems ......................................................................................................... 18
4.4.1 Supported SAP Business Suite Applications .............................................................. 19
4.4.2 SAP HANA Support .................................................................................................... 21
4.4.3 Required SAP Support Packages and Patches ......................................................... 21
4.4.4 Supported ArchiveLink Protocols ............................................................................... 23
4.4.5 Supported SAP GUIs .................................................................................................. 23
OpenText Archiving and Document Access for SAP Solutions 10.5.0 Release Notes
2
4.4.6 Web Browsers for the OpenText Archiving and Document Access for SAP
Solutions Web User Interfaces ................................................................................... 24
4.4.7 WebDAV Storage Interface for SAP NetWeaver Information Lifecycle
Management ............................................................................................................... 24
5 Installation and Upgrade Notes .................................................................................................. 25

5.1 Installation Notes ..................................................................................................................... 25
5.1.1 Installation Requirements ........................................................................................... 25
5.1.2 BC Set Activation ........................................................................................................ 26
5.1.3 SAP Notes .................................................................................................................. 26
5.1.4 User License Type Assignment .................................................................................. 26
5.1.5 Enhancement Packages............................................................................................. 27
5.1.6 CRM Package ............................................................................................................ 27
5.1.7 ArchiveLink Plus: Full Text Search ............................................................................ 27
5.1.8 ArchiveLink Plus: Business Content Window ............................................................. 28
5.1.9 Content Server 10.5 license keys (files) ..................................................................... 28
5.2 Upgrade Notes ........................................................................................................................ 28
5.2.1 Upgrade planning ....................................................................................................... 29
5.2.2 Upgrade path .............................................................................................................. 30
5.2.3 OpenText Vendor Keys ............................................................................................... 31
5.2.4 Further Hints ............................................................................................................... 33
5.3 Patches .................................................................................................................................... 33
6 Fixed Issues .................................................................................................................................. 35
7 Known Issues ............................................................................................................................... 37

7.1 General SAP Restrictions ........................................................................................................ 37
7.2 Accessibility ............................................................................................................................. 38
7.3 DocuLink for SAP Solutions .................................................................................................... 38
7.3.1 Table and Field Restrictions ....................................................................................... 42
7.3.2 Visualization................................................................................................................ 44
7.3.3 SAP GUI for HTML ..................................................................................................... 45
7.3.4 Livelink Business Application Integration (BAI) .......................................................... 45
7.3.5 SAP GUI for JAVA for MAC OS X ............................................................................... 48
7.4 OpenText Imaging Integration ................................................................................................. 48
7.5 OpenText Imaging DesktopLink............................................................................................... 48
7.6 OpenText Imaging Clients ....................................................................................................... 49
7.7 Forms Management for ECR................................................................................................... 50
7.8 License Report ........................................................................................................................ 50
3
7.9 Business Content Window....................................................................................................... 51
7.10 Other Restrictions ....................................................................................................... 52
8 Contact Information ..................................................................................................................... 53
4
1 Introduction
These Release Notes provide an overview of OpenText Archiving and Document Access for SAP
Solutions 10.5.0, 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.
We also recommend that you check the OpenText Knowledge Center

(https://knowledge.opentext.com/) for any patches or documentation updates that may have been
posted after the initial release of OpenText Archiving and Document Access for SAP Solutions 10.5.0.
1.1 Release Notes Revision History
Release Notes Modification Section Modified Modifications

Revision Date
Number
1.0 2013-11-21 All Initial draft
1.01 2014-04-16 2, All Wording in About and What's new;

harmonized design of tables
1.02 2014-06-02 3, 4: 3.5, 4.2, 4.3 12 language installation media;

Solaris 10 support
released; chapters 3 and 4 restructured
1.03 2014-06-12 7.8 Known issue with PDF output of

OpenText license report with languages
Chinese, Japanese and Polish.
1.04 2014-06-17 5.3 Added warning concerning Microsoft

redistribution files for Imaging
Enterprise Scan
Added customer advisory regarding
pat105000014
1.05 2014-06-30 5.3 Added cumulative patches for ECMLink

10.0.4 and 10.5.0 modules.
5
1.06 2014-08-01 5.3 Added new patch requirements:
• Update 2014.1 for Archive Server
10.5
• Update 2014.06 and pat105000160
for Content Server 10.5
• Service Pack 2 Update 2014.06
and pat100001621 for Content
Server 10.0.
1.07 2014-08-04 5.3 Added pat105000129 for Template

Workspaces 10.5.
1.08 2014-08-08 5.3 Updated cumulative patches for

ECMLink 10.0.4 and 10.5.0 modules.
1.09 2014-09-09 7.4 Hint about Web Viewer and

URIEncoding="UTF-8"
1.10 2014-10-09 4.4.5 Added SAP GUI for Windows 7.40

support.
1.11 2014-10-16 4.4.5 Added NWBC for Desktop 5.0 support;

updated NWBC info in general
1.12 2014-11-20 5.3 Update cumulative patches for

ECMLink 10.0.4 and 10.5.0 modules.
7.9 Added known issue with entry

configuration in SGOSATTR SAP table.
1.13 2014-12-04 3.4 Added details about OTEXBAS,

OTEXERP and OTEXCRM packages
1.14 2015-01-22 3.1.1 Corrected RCS version to 10.2.1
1.15 2016-03-21 3.4 Forms Management for TCP Context

Server: added location where to find
sap_OverlayForm.ixbxml
6
1.16 2016-11-21 4.4.1 Supported Added SAP NetWeaver 7.5 / EhP 8 for
SAP Business
ERP 6.0 support
Suite Applications
4.4.3 Required Added EhP 4 for CRM 7.0 support

SAP Support
Packages and Added EhP 4 for SRM 7.0 support
Patches
Added SAP GUI for Windows 7.40
4.4.5 Supported support
SAP
GUIsSupported
SAP GUIs
5.1.6 CRM
Package
1.17 2017-11-21 4.4.3 Required Added SAP GUI for Windows 7.50
SAP Support
support
Packages and
Patches
4.4.5 Supported
SAP GUIs
1.18 2017-11-22 4.4.3 Required Added support information for SAP GUI
SAP Support
for Windows
Packages and
Patches
1.19 2018-07-11 5.1.3 SAP Notes SAP Note 1833702
7
2 About OpenText Archiving and Document Access for
SAP Solutions
This section provides an overview of OpenText Archiving and Document Access for SAP Solutions
10.5.0.
2.1 What is OpenText Archiving and Document Access for SAP

Solutions?
OpenText Archiving and Document Access for SAP Solutions 10.5.0 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 10.5.0 enables you to integrate your documents into your
SAP application business processes e.g. incoming orders, outgoing correspondence or SAP ERP
invoices.
The OpenText solution is 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.2 What's new in this release?

OpenText Archiving and Document Access for SAP Solutions 10.5.0 includes the following new
features.
Important
Please pay attention to the licensing restrictions outlined in chapter 3.2
Note on the End User License Agreement.
Archive Server
Simplified deployment, Improved Single File Backup, Configuration of Storage Systems, Updated
Archive Monitoring Web Client.
Document Pipelines
Simplified installation.
Enterprise Scan
Improved usability, Full support for PDF Import; Improved support for Citrix and Terminal Server;
8
Improved documentation and capabilities for scripting; Side-by-side viewing for easier document
compare.
DocuLink
Thumbnail view supports rendering of MS office documents (in combination with Web Viewer).
DesktopLink
DesktopLink supports ArchiveLink enhancement with table TOAAT as described in SAP OSS Note
1451769.
OpenText Rendition Management

Multiple file download improved, Convenience Mode of Rendition Server is supported, Stream API
enhanced
OpenText License Measurement

The OpenText License Measurement was significantly changed. Please see the OpenText Archiving
and Document Access for SAP Solutions 10.5.0 Scenario Guide for more details.
For further new features please look at the respective release notes.
2.3 Discontinued and Deprecated Features

The following features have been discontinued in this release:
• There are no ABAP Add-Ons of OpenText Archiving and Document Access for SAP Solutions
10.5.0 OTEXBAS and OTEXERP anymore for the following SAP ERP Releases:
• SAP R/3 4.7 (SAP Basis 620)
• SAP ECC 5.0 ( SAP NetWeaver 2004/SAP Basis 640)
Please refer to the Installation and Upgrade Guide of of OpenText Archiving and Document
Access for SAP Solutions 10.5.0 and to the sections of these release notes about upgrade for
more details.
• There is no ABAP Add-On OTEXCRM anymore for the following SAP CRM Releases:
• SAP CRM 5.0
• SAP CRM 2007
Please refer to the Installation and Upgrade Guide of of OpenText Archiving and Document
Access for SAP Solutions 10.5.0 and to the sections of these release notes about upgrade for
more details.
• There are no ABAP Add-Ons of OpenText Extended ECM for SAP Solutions 10.5.0 OTEXRL
anymore for the following SAP ERP Releases:
• SAP R/3 4.7 (SAP Basis 620)
• SAP ECC 5.0 ( SAP NetWeaver 2004/SAP Basis 640)
Please refer to the Installation and Upgrade Guide of of OpenText Extended ECM for SAP
Solutions 10.5.0 and to the sections of the related release notes about upgrade for more
details.
9
3 Packaging and Documentation
Downloads and documentation for OpenText Archiving and Document Access for SAP Solutions are
available in the OpenText Knowledge Center (https://knowledge.opentext.com/).
3.1 Packaging and Delivery Information

The software for OpenText Archiving and Document Access for SAP Solutions is delivered in an
operating system dependent ISO-Image.
3.1.1 Software Modules in Master Setup 10.5.0

The following table lists all components of OpenText Archiving and Document Access for SAP
Solutions 10.5.0 (please pay attention to the licensing restrictions in chapter 3.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 the OpenText Archiving and Document Access for
SAP Solutions Master Setup.
Group Component Version Master

Setup
Archive Server Archive Monitoring Server and Web Client 10.5.0 Yes
Archive Server 10.5.0 Yes
Client Software Administration Client 10.5.0 Yes
Imaging Enterprise Scan 10.5.0 Yes
Imaging ExchangeLink 10.5.0 Yes
Imaging NotesLink 10.5.0 Yes
Imaging PDF Extensions 10.5.0 Yes
Imaging Windows Viewer and DesktopLink 10.5.0 Yes
Imaging Java Viewer 10.5.0 Yes
Document Document Pipeline Base 10.5.0 Yes

Pipelines
Document Pipeline for DocuLink 10.5.0 Yes
Document Pipeline for Enterprise Library 10.5.0 Yes
Document Pipeline for SAP Solutions 10.5.0 Yes
Document Pipeline Info 10.5.0 Yes
10
Document Pipeline Perl 10.5.0 Yes
Document Pipeline Remote Interface 10.5.0 Yes
Searchable PDF DocTool 11.0.0 No
Services Directory Services 10.5.0 + Patch Yes

(regarding 2
licensing see Yes
ECMLink Web Services 10.5.0
chapters 3.2.1 and
3.2.2; regarding
known issues ECMLink Web Services (Needed for 10.0.4 No
please read deployment on RCS 10.2.1 only)
section 7.10) No
Imaging Web Viewer Service 10.5.0
Enterprise Library Services 10.5.0 Yes
Content Server Activator for SAP Solutions 10.0.2 Yes

and Modules Yes
Archiving for Content Server 10.5.0
(regarding
licensing see Attribute Extensions 10.5.0 Yes
chapters 3.2.1 and Yes
Classifications 10.5.0
3.2.2)
Content Server 10.5.0 + Yes
2014.031
Document Properties Synchronization 10.5.0 Yes
ECMLink 10.5.0 Yes
ECMLink (Needed for deployment on Content 10.0.4 No

Server 10.0 only)
Extensions for Enterprise Library 10.5.0 Yes
Forms 10.5.0 Yes
Imaging Enterprise Scan 10.5.0 Yes
1Please read the Content Server licensing 10.5 FAQ in the OpenText Knowledge Center to learn
about Content Server 10.5 license key/file.
11
Imaging Reviews and Notes 10.5.0 Yes
Physical Objects 10.5.0 Yes
Pulse 10.5.0 Yes
Records Management 10.5.0 Yes
Recycle Bin 10.5.0 Yes
Renditions 10.5.0 Yes
SAP Base 10.2.0 Yes
Security Clearance 10.5.0 Yes
Template Workspaces (Case Management) 10.5.0 Yes
Web Forms 10.5.0 Yes
SAP Business Archiving and Document Access for SAP 10.5.0 No

Suite Software Solutions
(ABAP Add-on No
ECMLink for SAP Solutions (see also 10.5.0
packages)
chapters 3.2.1 and 3.2.2)
For detailed information about the packaging and delivery of individual components of OpenText
Archiving and Document Access for SAP Solutions please have a look at the individual release notes.
For information and restrictions concerning the OpenText Enterprise Library Services and the
OpenText Imaging Clients, see the OpenText Enterprise Library Services and OpenText Imaging
Release Notes. These Release Notes come with the installation package or you can find them in the
OpenText Knowledge Center (https://knowledge.opentext.com/).
3.1.2 Third Party Software

The following table lists all third party software that is on the ISO-Image, but not part of the product
OpenText Archiving and Document Access for SAP Solutions.
Group Component Version
Application Server Apache Tomcat 7.0.50
Java Java Runtime Environment 1.7
Note
These third party components are not covered by OpenText software
12
maintenance. These components are provided for installation convenience. Should
you need support for these components, please contact their respective software
manufacturer.
3.1.3 OpenText Customers

OpenText Archiving and Document Access for SAP Solutions 10.5.0 can be downloaded from
OpenText Knowledge Center in the Download area
(https://knowledge.opentext.com/knowledge/cs.dll?func=ll&objId=14162727&objAction=browse&sort=
name).
3.1.4 SAP customers

SAP Archiving and Document Access by OpenText software components can be downloaded from
the SAP Support Portal -> SAP Software Download Center. At the SAP Software Download Center
the software is listed under SAP ARC&DOC ACCESS BY OPEN TEXT -> SAP ARC&DOC ACCESS
10.5 BY OT.
Note: SAP Archiving and Document Access by OpenText 10.5 will be available for SAP
customers after having done the Premium Qualification certification. Planned release date is
end of June 2014.
3.2 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
3.2.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 Document Access for SAP Solutions
13
• SAP Extended Enterprise Content Management (ECM) by OpenText
3.2.2 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 is 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.2.3 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.
3.2.4 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.
3.2.5 Usage of ExchangeLink and NotesLink

The use of OpenText ExchangeLink and OpenText NotesLink is restricted to the following licensed
products:

• SAP Archiving by OpenText
• SAP Extended Enterprise Content Management (ECM) by OpenText.
3.3 Related Documentation

For additional information on OpenText Archiving and Document Access for SAP Solutions, or for
supplemental information on related products, refer to the following documents, which are available in
the OpenText Knowledge Center (https://knowledge.opentext.com/knowledge/llisapi.dll/open/docs).
OpenText Archiving and Document Access:

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=15050695&objAction=browse&vie
wType=1
14
3.4 Documentation Errata
Installation and Upgrade Guide: OpenText Archiving and Document Access for SAP Solutions
(ER10005-IGD)
In chapter 1 - What is OpenText Archiving and Document Access for SAP Solutions?
an additional section is needed that lists more details about the content of the SAP (ABAP) packages:
Archiving and Document Access for SAP Solutions software packages
Archiving and Document Access for SAP Solutions consists of the following SAP packages:
• SAP basis package OTEXBAS
Provides all base applications: DocuLink, DesktopLink, Forms Management, Imaging

Integration, ArchiveLink attributes, License Measurement
• SAP ERP package OTEXERP (optional)
Optional package with ERP specific functionality
o Allows use of DVS/PLM nodetypes in DocuLink
o Transaction /ixos/plm to have an uploader transaction for DVS/PLM documents
o Client independent objects and code for sample DocuLink projects, which are not
only SAP ERP specific but can also be used for base examples
• SAP CRM package OTEXCRM (optional)
Optional package with CRM specific functionality.
o Allows use of SAP CRM link range in Content Management node type in DocuLink
o Client independent objects and code for a sample DocuLink project in SAP CRM
In chapter 3.4.2 - Installing Forms Management

the text of the numbered item 3e needs to be changed to:
Enter the path and file name of the mapping configuration file sap_OverlayForm.ixbxml.
This file is contained in a ZIP archive file located in the patches area of OpenText Knowledge Center:
Forms Management (All Versions) - mapping configuration file sap_OverlayForm.ixbxml
Note that though located in a folder for ADA version 10.5.1, the file is valid for all versions.
15
3.5 Language Support
OpenText Archiving and Document Access for SAP Solutions is currently localized in the following
languages. Future releases may add additional languages.
Languages
EN DA DE ES FR IT JA NL NO PL PT(BR) RU ZH
B UI UI UI UI UI UI UI UI UI UI UI UI
UI = user interface only

B = both user interface and online help
Note
The most recent language packages and setups related to
OpenText Archiving and Document Access for SAP Solutions
10.5 will be made available in the Open Text Knowledge Center
soon.
16
4 Supported Environments and Compatibility
This section provides details on supported platforms and version information.
The Release Notes for OpenText Archiving and Document Access for SAP Solutions 10.5.0 are
updated continually. The latest version and further technical information are available in the OpenText
Knowledge Center (https://knowledge.opentext.com/).
OpenText Archiving and Document Access for SAP Solutions 10.5.0 is the successor of OpenText
Archiving and Document Access for SAP Solutions 10.0.0.
Caution
Only the products and versions specified in the Release Notes are
supported. Other versions have not been tested and are therefore not
officially supported for this version. The Release Notes contain the
definitive list of supported versions. Any other versions mentioned in the
product documentation are superseded by the versions specified in the
Release Notes.
4.1 Compatibility Matrix

For details on compatibility between OpenText products, refer to the Compatibility Matrix
(https://knowledge.opentext.com/knowledge/llisapi.dll/open/15507401) in the OpenText Knowledge
Center.
You may find the specific compatibility matrix for ECM Suite for SAP® here.
For information and restrictions concerning other OpenText products, see the corresponding Release
Notes in the OpenText Knowledge Center.
4.2 Supported Server Operating Systems, and Java Runtime

Environments
4.2.1 Server Operating Systems
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 10.5.0.
17
Components such as OpenText Archive Server may support more platforms than the Content Suite
Platform as a whole.
The ISO image for OpenText Archiving and Document Access for SAP Solutions 10.5.0 is available
for Windows 2012, Windows 2008R2, Red Hat Linux 6, and Solaris 10.
Exception: The “Document Properties Synchronization Module” is only available for a Windows
Platform.
4.2.2 Supported Java Runtime Environments

Application Servers: Apache Tomcat 7 (64 Bit)
Java Environment: Java 7 (JRE or JDK) (64 Bit)
4.3 Supported Client Operating Systems

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
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.
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.4 Supported SAP Systems
Note
• OpenText Archiving and Document Access for SAP Solutions 10.5.0 only supports
version 6.0 of SAP ERP (ECC).
version 7.0 of SAP CRM.
version 7.0 of SAP SRM.
18
4.4.1 Supported SAP Business Suite Applications
The following table shows the SAP application versions and by which OpenText software components
they are supported.
19
OpenText Software SAP AS SAP NetWeaver EhP 1 – 2 for SAP NetWeaver 7.0
Component ABAP 7.1 7.0 EhP 1 for SAP NetWeaver 7.3
SAP NetWeaver 7.40
SAP NetWeaver 7.50
OpenText Archive Supported Full Support Full Support

only for Data
Archiving,
Document
Archiving,
and Display
OpenText Basis - ERP 6.0, All SAP systems running on these

(OTEXBAS) EhP1-3 for ERP SAP_BASIS versions, e.g. EhP4-8
6.0 for ERP 6.0,
(support for CRM CRM 7.0,
5.0 and CRM EhP1-4 for CRM 7.0,
2007 is EhP1-4 for SRM 7.0
discontinued)
OpenText ERP Package - ERP 6.0, EhP4-8 for ERP 6.0
(includes SAP PLM EhP1-3 for ERP
features) (OTEXERP) 6.0
OpenText CRM - (support for CRM CRM 7.0,

Package (includes CRM 5.0 and CRM EhP1-4 for CRM 7.0
CM link range features) 2007 is
(OTEXCRM) discontinued)
OpenText DocuLink - Supported Supported

Web User Interface
(included in OTEXBAS)
OpenText ECMLink - ERP 6.0, All SAP systems running on this

EhP1-3 for ERP SAP_BASIS version, e.g.
6.0
EhP4-8 for ERP 6.0,
CRM 7.0,
EhP1-4 for CRM 7.0,
SRM 7.0,
EhP1-4 for SRM 7.0
20
OpenText Archiving and Document Access for SAP Solutions 10.5.0 supports the KPro (Knowledge
Provider) infrastructure. The underlying OpenText Archiving and Storage Service respectively
OpenText Archive can be used to store KPro / SAP DMS documents and/or can be used as a content
cache server.
Note
In the case of pure data and document archiving Open Text
Archiving for SAP Solutions respectively SAP Archiving by
OpenText supports the SAP NetWeaver releases 7.0 to 7.4
inclusive. This applies to all SAP solutions running that version of
SAP NetWeaver e.g. Banking Services and other IS solutions.
4.4.2 SAP HANA Support

OpenText Archiving and Document Access for SAP Solutions 10.5.0 supports SAP Business Suite on
SAP HANA. SAP HANA support has been certified by SAP on SAP NetWeaver 7.40.
4.4.3 Required SAP Support Packages and Patches
SAP Software Version SPAM Minimum Support Package Comments

Component level Stack
SAP Basis / 7.0 45 16 SAPKB70016

NetWeaver
(SAP_BASIS,
SAP_ABA)
EHP 1- 2 for 45 Any
SAP NW
7.0, EHP1
for SAP NW
7.3, 7.4, 7.5
SAP ERP ERP 6.0, 45 Any depends on requirements

EhP1-8 for for SAP Basis 7.0
ERP 6.0
SAP CRM CRM 7.0, 45 Any depends on requirements

(Archiving and EhP1-4 for for SAP Basis 7.0
Document CRM 7.0
Access)
21
SAP CRM CRM 7.0 39 CRM 7.0 SP Stack 02 SAPKA70103
(ECMLink) (SAP_BASIS 701 03 SAPKB70103
SAP_ABA 701 03 SAPKU70002
BBPCRM 700 02 SAPK-70002INWEBCUIF
WEBCUIF 700 02)
EhP1-4 for 39 Any See SAP OSS Notes:

CRM 7.0 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
SAP SRM SRM 7.0 42 SRM 7.0 SP Stack 08 SAPKA70107

(ECMLink) (SAP_BASIS 701 07 SAPKB70107
SAP_ABA 701 07 SAPKIBKV08
SRM_SERVER 700 08)
EhP1 for 42 EhP1 for SRM 7.0 SP Stack 03 See SAP OSS Note
SRM 7.0 1494683 - SAP SRM 7.0
Enh.Pk.1 SP Stacks -
Release & Information
Note
EhP2-4 for 42 Any See SAP OSS Note

SRM 7.0 1582094 - EHP2 for SAP
SRM 7.0 SP stacks -
Release & Information
Note
22
SAP Software Component Version Recommended Minimum Patch Level
7.30 6
7.40 3
SAP GUI for Windows
7.50 2 - See SAP note 1258724 for additional

requirements.
4.4.4 Supported ArchiveLink Protocols

The ArchiveLink protocols 4.5 and 4.6 are supported. OpenText provides for ArchiveLink following
communication protocols: IX_OLEU1, IX_OLEU2, IX_HTTP2, IX_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, the OpenText Archive Cache Server and the SAP Content Server
Cache are supported.
4.4.5 Supported SAP GUIs

The supported SAP GUIs depend only on the SAP Basis/NetWeaver version.
SAP Software Version SAP GUI SAP GUI SAP NetWeaver SAP GUI for
Component for for HTML Business Client JAVA
Windows (NWBC)
SAP 7.0 7.30, 7.40, Integrated 3.02, 3.5, 4.0 7.20 for
Basis/NetWeaver 7.50 Stand-Alone, 5.0 MAC OS X
Stand-Alone v10.5.7 and
newer1
EhP1-2 for 7.30, 7.40, Integrated 3.02, 3.5, 4.0, 5.0

NW 7.0, 7.50
EhP1 for NW
7.3
7.4 7.30, 7.40, Integrated 4.0, 5.0

7.50
7.5 7.40, 7.50 Integrated 4.0, 5.0
23
1 SAP support for SAP GUI for JAVA 7.20 ended 31.01.2013. Regarding the common requirements of
SAP GUI for Java 7.20 please refer to the related SAP documentation. Regarding known
restrictions/behaviour related to OpenText Archiving and Document Access for SAP Solutions please
have a look at chapter 7.3.5 of these release notes.
2 maintenance came to an end on January 1, 2014. See SAP OSS Note 1029940
Regarding the use of SAP NetWeaver Business Client (NWBC) please read the following and related
notes:
• SAP Library: NWBC Versions

• SAP OSS Note 1029940 – SAP NWBC 3.0 prerequisites and restrictions
• SAP OSS Note 1620514 – NWBC 3.5 for Desktop: Prerequisites and restrictions
• SAP OSS Note 1754946 – NWBC for Desktop 4.0: Prerequisites and restrictions
• SAP OSS Note 2066345 – NWBC for Desktop 5.0: Prerequisites and restrictions
Depending on the specific scenario how SAP NWBC is used (SAP GUI or SAP GUI for HTML) please
also note the requirements or restrictions of OpenText Archiving and Document Access for SAP
Solutions 10.5.0 as mentioned in its documentation or in these release notes.
4.4.6 Web Browsers for the OpenText Archiving and Document Access for
SAP Solutions Web User Interfaces
The OpenText DocuLink for SAP Solutions Web User Interface and the OpenText ArchiveLink PLUS -
Search Web User Interface are based on Web Dynpro ABAP. Therefore the same limitations are valid
as for Web Dynpro ABAP. As a minimum Microsoft Internet Explorer 7.0 is supported. Please see
SAP/OSS note 1098009 for more details, especially regarding the usage of MS IE 8.0 or Firefox 3.x.
Use of MS IE 9.0 or newer is also supported. Please have a look at the Product Availability Matrix
(PAM)2 for SAP NetWeaver 7.0, SAP EhP1 for SAP NetWeaver 7.0, SAP EhP2 for SAP NetWeaver
7.0, SAP EHP1 for SAP NetWeaver 7.3 or SAP NetWeaver 7.4 to find out which Web browser
version is supported and which patch levels are required.
4.4.7 WebDAV Storage Interface for SAP NetWeaver Information Lifecycle

Management
The WebDAV Storage Interface for SAP NetWeaver Information Lifecycle Management is supported.
2The most recent version of SAP NetWeaver 7.0 Product Availability Matrix (PAM) can be
downloaded from the SAP Service Marketplace (SMP).
24
SAP Integration scenarios BC-ILM 2.0 and BC-ILM 3.0 operate with WebDAV Storage Interface for
SAP NetWeaver Information Lifecycle Management.
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.
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.
5.1.1 Installation Requirements

The SAP-specific installation of OpenText Archiving and Document Access for SAP Solutions 10.5.0
components is described in details in the OpenText Archiving and Document Access for SAP
Solutions – Installation and Upgrade guide (ER-IGD), which can be found in the OpenText Knowledge
Center. Furthermore, the client installation from the OpenText Imaging CD 3 is necessary for the
additional clients.
Also consider the software requirements mentioned in SUPPORTED SAP Systems on page 18.
Caution
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
3 May be an ISO-Image or ZIP-Package as well.
25
5.1.2 BC Set Activation
The OpenText Archiving and Document Access for SAP Solutions - Installation and Upgrade guide
(ER-IGD) Version 10.5.0 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 OpenText Knowledge Center
(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 KNOWN ISSUES on page 37 for SAP notes required for special
scenarios.
OSS Required for

Note
884077 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 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.
1128338 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 behaviour 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 behaviour,
whether a new window is opened.
1713851 This note prevents a dump screen when one tries to open a document, gets a SAP
Security dialog, and presses the “Deny” button.
1833702 Check this note, if errors occur when calculating Archive URL’s. The note fixes issues of
function SCMS_LOCATION_GET, which is used in function SCMS_URL_GENERATE.
5.1.4 User License Type Assignment

With OpenText Archiving and Document Access for SAP Solutions 10.5 a new license report is
implemented. Users are counted in types related to the product that is used and depending on the
26
degree of usage. A user type, for example full, professional, or occasional, has to be assigned to
every user. You create roles using authorization object J_6NLC_TYP to assign the license type to
users. The complete list of license types is available in the F4 help of field /OTX/CLTYP of
authorization object J_6NLC_TYP.
E.g. OpenText Document Access - Occasional User (ID = ODOCF) is the type to indicate, that
Document Access is used occasionally (i.e. one day per week or less).
Please read the OpenText Archiving and Document Access for SAP Solutions - Scenario guide
(ER100500-CCS) for detailed information about the OpenText License Report.
5.1.5 Enhancement Packages

The Add-On packages for software component OTEXBAS are installable on SAP systems with
enhancement packages for SAP NetWeaver 7.0. No additional ACP package is needed.
Furthermore the Add-On packages for software component OTEXBAS are installable on SAP
Systems with enhancement package 1 for SAP NetWeaver 7.30 or on SAP Systems with SAP
NetWeaver 7.4. No additional ACP package is needed.
In this context please also read SAP Note: 1615808 The NW Release 7.3 EHP1 uses the same ABAP
stack 7.31 as NW Release 7.0 EHP3; its name is AS ABAP 7.31 (=SAP_BASIS 7.31).
The (optional) Add-On package for software component OTEXERP is installable on SAP systems with
enhancement packages for SAP ERP 6.0. No additional ACP package is needed.
5.1.6 CRM Package

One (optional) OTEXCRM Add-On package is delivered which may be installed on SAP CRM 7.0 and
SAP EhP1 – 4 for SAP CRM 7.0. Please refer to the details given in the OpenText Archiving and
Document Access for SAP Solutions - Installation and Upgrade guide (ER-IGD).
5.1.7 ArchiveLink Plus: Full Text Search

The ABAP functionality is included in the Add-On OTEXRL of OpenText Extended ECM for SAP
Solutions 10.5.0 and also requires other components of OpenText Extended ECM for SAP Solutions
10.5.0.
Therefore the same version and compatibility restrictions apply as for OpenText Extended ECM for
SAP Solutions 10.5.0.
Please refer to the chapter about ARCHIVELINK FULL TEXT SEARCH in the OPENTEXT ARCHIVING AND
DOCUMENT ACCESS FOR SAP SOLUTIONS - SCENARIO GUIDE (ER-CCS) and the related documentation
of OpenText Extended ECM for SAP Solutions 10.5.0.
27
5.1.8 ArchiveLink Plus: Business Content Window
The ABAP functionality is included in the Add-On OTEXRL of OpenText Extended ECM for SAP
Solutions 10.5.0 and also requires other components of OpenText Extended ECM for SAP Solutions
10.5.0.
Therefore the same version and compatibility restrictions apply as for OpenText Extended ECM for
SAP Solutions 10.5.0.
Please refer to the chapter about OPENTEXT BUSINESS CONTENT W INDOW in the OPENTEXT ARCHIVING
AND DOCUMENT ACCESS FOR SAP SOLUTIONS - SCENARIO GUIDE (ER-CCS) and the related
documentation of OpenText Extended ECM for SAP Solutions 10.5.0.
5.1.9 Content Server 10.5 license keys (files)

Please read the Content Server licensing 10.5 FAQ in the OpenText Knowledge Center to learn about
Content Server 10.5 license key/file.
5.2 Upgrade Notes

In addition to the description given in the OPENTEXT ARCHIVING AND DOCUMENT ACCESS FOR SAP
SOLUTIONS - INSTALLATION AND UPGRADE GUIDE (ER-IGD) please read these information regarding
Upgrades.
Warning
If you import an upgrade into an SAP system with OpenText Archiving
and Document Access for SAP Solutions 10.5.0 and the data of the
respective upgrade packages is not read (upgrade phase IS_SELECT),
the OpenText Archiving and Document Access for SAP Solutions 10.5.0
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 7-2 of the OPENTEXT ARCHIVING AND DOCUMENT
ACCESS FOR SAP SOLUTIONS - INSTALLATION AND UPGRADE GUIDE (ER-
IGD) VERSION 10.5.0, the existing Add-ons are kept ("KEEP" in upgrade
phase IS_SELECT).
28
Caution
• User exits
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 the

OpenText Knowledge Center entry on user exits in DocuLink
9.6.0 (https://knowledge.opentext.com).
• Patch dependencies when upgrading
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.
• Table entries in SGOSATTR
Version 9.8.0 and 10.0 of the 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.2.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.
29
• 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.
• 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 10.5.0 does not provide any
exchange upgrade packages. I.e. 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 10.5.0 on the target release.
Please check in the OpenText Archiving and Document Access for SAP Solutions -
Installation and Upgrade guide (ER-IGD) Version 10.5.0 when a so called "KEEP" with vendor
keys has to be done to preserve the functionality.
5.2.2 Upgrade path

Customers using 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 the OpenText Knowledge Center. The next step is
then the upgrade to the 9.6.1 version and then to OpenText Archiving and Document Access for
SAP® Solutions 9.6.2 and then to Version 9.8.0 with upgrade packages. Version 10.0 was the first
version without (delta) upgrade packages. Instead the installation packages are installed on top of the
previous version. The same is true for version 10.5.0. Install the installation package of version 10.5.0
on top of version 10.0.0. Please also be aware, that older transports may be interpreted as
modifications and then its important to keep an eye on the modification browser (transactions SPDD
and SPAU).
Note
If you follow an upgrade via several versions of OTEXBAS,
OTEXERP or OTEXCRM, that no support packages or hot fix
transports need to be applied until the final target version is
reached. The add-on OTEXBAS 10.5.0 contains the bug fixes
contained in OTEXBAS 10.0 SP1, and SP2.
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.
30
5.2.3 OpenText Vendor Keys
When to use exchange packages?
As SAP Basis 620 and 640 are discontinued in version 10.5.0 there are no exchange upgrade
packages. Therefore 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 10.5.0 on the
target release.
When to use vendor keys?
You already have installed Add-On packages OTEXBAS, OTEXERP or OTEXCRM of version 10.5.0
on an SAP System with SAP NetWeaver 7.0, EhP1 or EhP2 for SAP NetWeaver or EhP 1 for SAP
Netweaver 7.3. I.e. OTEXBAS 1050_700, OTEXERP 1050_600 or OTEXCRM 1050_700 are already
installed. Furthermore you have to upgrade to a new SAP Release which still is based on SAP NW
7.0, EhP1 for NW 7.0, EhP2 for NW 7.0, EhP1 for NW 7.3 or NW 7.40. Then the Add-on exchange
package cannot be used. Instead in the upgrade phase IS_SELECT please choose a "KEEP"
upgrade. In this case the upgrade tool asks you for a vendor key.
Please have a look in the OpenText Archiving and Document Access for SAP Solutions - Installation
and Upgrade guide (ER-IGD) Version 10.5.0 for more details about the different installation and
upgrade packages.
Vendor key list
Regarding the vendor keys SAP indicates that installations and upgrades are done with different
tools, therefore different keys are required. The list below contains the possible keys for every target
release, depending on upgrade or EhP installation process. For 701 there are 2 possible keys
depending on the source release. SAP recommends to simply try both of them. Furthermore SAP
recommends using the latest versions of SAPUP or SAPehpi , which can be downloaded from the
SAP Service Marketplace.
SW Component Action NW target Key Number
OTEXBAS Upgrade 701 1905323
OTEXBAS EHP install 701 2121071
701 1848589
31
OTEXBAS EHP Install 740 1280876
OTEXERP Upgrade 701 3692324
OTEXERP EHP install 701 1583814
701 1101221
OTEXCRM Upgrade 701 2988495
OTEXCRM EHP install 701 1699730
701 807655
32
5.2.4 Further Hints

"Deleted Records" table
When upgrading from DocuLink version <= 6.0 or when upgrading from non-unicode to unicode
releases:
Consider recovering and/or erase deleted records table entries before upgrading from non-unicode to
unicode. (See "Maintenance of deleted records" in transaction J6NA table /IXOS/DC_TBRB) This may
only be interesting, if customers like to keep this "recycle bin" data.
5.3 Patches
The following patches must be applied to OpenText Archiving and Document Access for SAP
Solutions 10.5.0 (and/or OpenText Extended ECM for SAP Solutions 10.5.0, respectively). OpenText
also recommends that you check the OpenText Knowledge Center (https://knowledge.opentext.com/)
for any patches or documentation updates that may have been posted after this release.
• ECMLink 10.5
• Hotfix 1 for SAP
• D6VK901039 (workbench transport)
• Q6VK900063 (customizing transport – apply on each SAP client)
• ECMLink 10.5.0 (Content Server 10.5 module)
• pat105000237(4) (cumulative patch)
• ECMLink 10.0.4 (Content Server 10.0 module)
• pat100001734(4) (cumulative patch)
• Archive Server 10.5
• Update 2014.1(4)
• Content Server 10.5
• Update 2014.06(4)
• pat105000160(4)
4This patch, or patch bundle, is not on the OpenText Archiving and Document Access for SAP
Solutions media but is available on OpenText Knowledge Center.
33
• Content Server 10.0
• Service Pack 2 Update 2014.06(4)
• pat100001621(4)
• Directory Services 10.5
• Patch 2
• Hotfix 1-3 for Patch 2
• Document Pipeline 10.5 (Windows only)
• DPC-1050-001
• Imaging Enterprise Scan 10.5 (Windows only)
• ESC-1050-001
• Template Workspaces 10.5
pat105000129(4)
Note
Archive Server 10.5.0 Patch Collection 2014_01 is mandatory.
Warning
The Archiving and Document Access ISO image provides Microsoft redistribution
files for Imaging Enterprise Scan (location: //Clients/Enterprise Scan/redist).
Unfortunately, these files are not up to date. Instead, one should take the Microsoft
redistribution files provided for Imaging Windows Viewer and DesktopLink (location:
//Clients/Windows Viewer and DesktopLink/redist).
Customer Advisory
OpenText™ official patch pat105000014 that you downloaded from the
Knowledge Center or took from the Archiving and Document Access or
Extended ECM 10.5 media has been repackaged.
OpenText official patch pat105000014 fixes several issues in the Office Editor 10.5
module.
The patch that you downloaded or took from the Archiving and Document Access or
Extended ECM 10.5 media was malformed and may fail to deploy.
The patch has been repackaged to resolve this issue. The fixes included in the
patch have not changed.
The original patch pat105000014 file has been removed from our Web site and is no
longer available. The repackaged patch file is now available and can be downloaded
from our Web site at the link below:
34
https://knowledge.opentext.com/knowledge/llisapi.dll/open/44504051
If you have not applied the original patch pat105000014 file, do not apply it. If you
have applied it, download the repackaged patch file and reapply it.
6 Fixed Issues
This section provides information about past issues that have been fixed in this release.
Version 10.5.0 includes all fixes of support packages 1 and 2 of previous version 10.0.0.
Check this list for further fixes:
Issue Description
LLSAPS-3271 Security fix LLSAPS-3271; prevent abusive calls of RFC

function/IXOS/DC_H_REPORT_TAB_ENTRIES from outside of DocuLink
SAPRM-4742, Rendition Management Hotfix 2013_02: New function module in Rendition Server
SAPRM-4744, Connector, index table for document download, fixes regarding GUID in streaming
LLSAPS-3339 function, revision of DocuLink projects RSUMONITOR and RS_TRFC_ST
LLSAPS-3321 Implement protection of function module /IXOS/DC_K_GET_VALUETAB_SELECT
LLSAPS-3348 Fixes for Fulltext Search Web UI
LLSAPS-3322 Business Content WindoW – Barcode Entry dumps in transaction BP
LLSAPS-3316, WebDynpro hitlist: Dump, if table field of the attribute object contains char "/"
LLSAPS-3337,
LLSAPS-3338
LLSAPS-3372 AL PLUS: ArchiveLink attributes for file properties are not prefilled for all documents
LLSAPS-3349 Workflows: Authorization checks are not correctly executed for workflow profiles
which have names with more then 12 characters
LLSAPS-3325, Function module /IXOS/DCCRM_EXA_READ dumps due to type mismatch when

LLSAPS-3324 calling CRM_DOC_FLOW_READ_OB
35
LLSAPS-3279, Webdynpro selects data wrong, uses wrong( to many) selection fields in
LLSAPS-2376 /IXOS/DC_Z_READ
LLSAPS-3368 Inconsistent workflow possible because of missing authorizations
LLSAPS-3370 Unable to execute the customization in SPRO "Maintain deletion workflow options"
LLSAPS-3356 Icon "Document Processing" allows access to excluded RS Task Profiles
LLSAPS-3382, Problem with the INPLACE display of documents in DocuLink in SAP WebGUI
LLSAPS-3383
LLSAPS-3380 Short-Dump when exceeding the maximum number of sessions in a project
LLSAPS-3376 WF: standard check for records fails, if technical user does not have authorization
for AL authorization object S_WFAR_OBJ
LLSAPS-3369 Multiple workflows - inconsistent fields displayed in SAP GUI vs. Web UI
LLSAPS-3329 When moving a document a new storage date is set
LLSAPS-3343 Erroneous error handling of delete workflow when Archive server is not available
LLSAPS-3332 ArchiveLink Attributes file upload - does not recognize generic document class
LLSAPS-3358 Workflows: Improve error handling at automatic recipient determination
LLSAPS-3378 Improve message text in Copy operation (Web UI)
LLSAPS-3379 Workflows: Displaying Doculink tree from workflows (button 'Personnel file') started
in older project versions might cause shortdumps
LLSAPS-3381 Workflow WebUI: Text 'Automatic processor determination' is hard coded in

program and needs to be changed to text element
36
7 Known Issues
Caution
• Restrictions on behalf of non-OpenText products are not listed
here. See the respective Release Notes of those products for
further information.
• Some entries have an internal reference number (Reference
139941, for example). 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.
The following known issues exist in this release.
7.1 General SAP Restrictions
Issue Description
SAP It is recommended to use SAP GUI for Windows 7.30 patch level 6 or higher. This
Note 1774514, solves known issues with drag-and-drop.
SAP Note
1832794 SAP standard transaction OAWD or the SAP GOS toolbar function “Store business
document” use a text-edit-control to create a field into which documents can be
dropped which have been dragged from the Windows file explorer. With SAP GUI
for Windows 7.30 patch level 2 and less this feature is not working due to some
unreadable text added to the retrieved file names: see also SAP Note 1774514.
With SAP GUI for Windows 7.30 patch level 3 this issue is fixed at least if only one
file is dragged and dropped at a time. The action still may fail, if more than one file
was selected. The issue is addressed in SAP Note 1832794.
The drag-and-drop fields in the ArchiveLink file upload as used in EFM or in

“Business Content Window – Business documents” are affected in the same way,
because they were implemented with the same text-edit-control functionality as the
SAP standard features.
37
7.2 Accessibility
Issue Description
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.
7.3 DocuLink for SAP Solutions
Warning
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.
Issue Description
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.
38
Transporting projects of version 10.0.0 and 10.5.0
If it occurs that a DocuLink project based on version 10.0.0 or 10.5.0 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.
39
DocuLink Web User Interface
The DocuLink Web User Interface is implemented based on the ABAP Web Dynpro
Framework. Not all features of DocuLink are supported in this visualization. For an
overview of supported functionality in the projects themselves, see the OpenText
DocuLink for SAP Solutions – Customizing and Administration Guide. The following
features are not supported for DocuLink projects that are accessed using the DocuLink
Web User Interface:
• RFC communication to the archive
• Scanning via front-end and file upload via DesktopLink
• Assigning files via barcode
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.
Error dump in DocuLink Web User Interface

SAP Note
1669913 In case of runtime errors in CL_WDR_VALUE_HELP_HANDLER when starting projects
in the DocuLink Web UI check also, if SAP note 1669913 needs to be installed on the
SAP system.
142195 Output masks for dynamic nodes
If the values for a field are restricted by input in a selection screen, the restriction 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.
204528 Logging for CM documents in hit lists
When you perform actions on CM documents that are displayed in a hit list, no logging
information is stored for these actions.
40
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.
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.
Notes:
1
$EX_FI an optional example DocuLink project which may be downloaded from the KC
(https://knowledge.opentext.com).
41
7.3.1 Table and Field Restrictions
Issue Description
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.
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.
42
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.
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.
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.
43
7.3.2 Visualization
Issue Description
SA Problems when displaying archived documents with Web Viewer

P note
1128338, SAP The maintenance table /IXOS/OA_CUST_A (viewer customizing) offers a flag
note 1061637 called Open in curr. Window. The program code of this feature uses the SAP
function module CALL_BROWSER. In case of problems when displaying archived
documents with the Web Viewer check the following SAP notes:
• 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.
SA Unnecessary scrollbars in pop ups

P
note 592607 Sometimes scrollbars are displayed even in small pop ups where they are not
necessary. To avoid this behaviour, implement SAP note 592607.
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 8.0 or
MS IE 9.0.
44
7.3.3 SAP GUI for HTML
Description
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 the OpenText Imaging: Windows Viewer.
Archiving documents via front-end
Archiving scenarios do not work with SAP GUI for HTML.
7.3.4 Livelink Business Application Integration (BAI)
Description
45
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 Livelink ECM
– PDMS Context Server.
IXOS Records with time stamps
Timestamps in IXOS Records cannot be used in queries to retrieve data from a Livelink ECM – PDMS
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 PDMS
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 a Livelink ECM – PDMS Context Server, you cannot use ECR
relations. Use the required IXOS Record type directly.
46
Special characters in Administration for ECR Context Server
In the Administration for ECR 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
If the Livelink ECM – PDMS Context Server = 6.0D is used, characters supported by ISO-8859-1 are
also supported for these parameters.
New standard data model in the Livelink ECM – PDMS Context Server 6.0E for the Livelink BAI
scenario
During data export from an SAP system to a PDMS Context Server using the Livelink 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.
Support of a two layer data model in Livelink ECM – PDMS Context Server 6.0E
The standard data model for PDMS Context Server 6.0E has been changed to a two layer model. For
the BAI service, you must apply patch CR60-052 to the PDMS Context Server, and patch PD095-013
to the Livelink ECM – PDMS Document Modeler.
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 PDMS
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 PDMS 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
the Livelink ECM – PDMS Document Modeler - Customization Guide (CC-CGD).
47
7.3.5 SAP GUI for JAVA for MAC OS X
Description
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.
7.4 OpenText Imaging Integration
Issue Description
Behavior of Imaging Integration 10.0.0 with /IXOS/OA_DOCTYPE
Starting with version 10.0.0 the standard behavior of the 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.
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 the OpenText Imaging Web Viewer Installation
and Configuration Guide at the chapter "Requirements" how to set the URIEncoding="UTF-
8".
7.5 OpenText Imaging DesktopLink
Description
48
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
There are known issues with SAP GUI 7.20 on SAP NetWeaver 7.4 systems. Please upgrade to SAP
GUI 7.30.
7.6 OpenText Imaging Clients
Issue Description
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 the OpenText Knowledge Center:
https://knowledge.opentext.com.
Java Viewer inplace in DocuLink view
If a Java Viewer = 6.0 is displayed inplace in OpenText DocuLink for SAP Solutions view,
the context menu is not displayed correctly. Thus it is not possible to select a context menu
option (e.g. to create Notes).Using Java Viewer 9.5 inplace, display is not possible at all.
Please use a newer version of Java Viewer (e.g. 10.0) instead 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).
49
203652 Web Viewer (< 9.6.0) inplace in DocuLink view
When the Web Viewer (< 9.6.0) is displayed inplace in a OpenText DocuLink for SAP
Solutions view, notes to the document cannot be displayed or added, as the necessary
protocol is not supported by SAP.
It is recommended to use a newer version of Web Viewer. Or, if possible, use the old SAP
GUI visual design (option in the SAP Configuration settings) or disable the inplace view for
OpenText DocuLink for SAP Solutions (setting in view header data).
Inplace viewing of TIF documents using the 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 the
OpenText Imaging: Windows Viewer.
7.7 Forms Management for ECR
Description
Forms Management for Livelink ECM – PDMS Context Server 6.0C
Migrating forms maintained in SAP to a Livelink ECM – PDMS Context Server is not supported.
7.8 License Report
Issue Description
50
LLSAPS- License Report PDF Output issue with certain languages (Chinese, Japanese,
3425 Polish)
In transaction /otx/license the PDF output of the license report is started with "Display
Latest License Report (F7)". This output is created using the output device with short
name LOCL which can be created and maintained in transaction SPAD (see SAP online
documentation, e.g. here). Usually the device type SWIN is sufficient. However, in the
case of languages (simplified) Chinese, Japanese or Polish, the PDF output may contain
scrambled characters. In this case the PDF output of the license report will look ok, if the
device type of output device LOCL is changed to a value according to the following table:
Valid device type values of output

Logon language in SAP
device LOCL
Simplified Chinese (ZH) CNPDF, CNSAPWIN or PDFUC
Japanese JPPDF, JPSAPWIN or PDFUC
Polish I2PDF, I2SWIN or PDFUC
Please note, that device type PDFUC is implemented with SAP OSS Note 999712.
Furthermore it is possible, that other device types will also lead to readable results.
As an alternative please also consider to log on in English and then to create the PDF
output.
In future versions/patch levels the PDF output of the OpenText license report will make
use of device type PDFUC whenever available and will fall back to other device types
like e.g. SWIN.
7.9 Business Content Window
Issue Description
SAPRM- Business Content Window

6570
In SGOSATTR database table, the “Commit Required” field of the OTX_ATTACH service
(Class for Generic Service = /OTX/RM_GOS_SRV_ATTACH_LIST) must be unset,
otherwise the Business Content Window might not open.
51
7.10 Other Restrictions
Issue Description
144870 Migration report
The migration report /IXOS/RT_AL_SCENARIO only moves the main component, not
additional components such as notes, annotations, page index or attributes.
LLSAPS- Migration report

2570
The migration program /IXOS/RT_KPRO_SCENARIO (FUNCTION
/IXOS/RT_KPRO_BASIS) uses the same base functions as program RSIRPIRL.
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.
52
8 Contact Information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1
Email: support@opentext.com
Knowledge Center: https://knowledge.opentext.com
For more information, visit www.opentext.com
Copyright ©2013 Open Text Corporation. Visit online.opentext.com. OpenText is a trademark or registered trademark of Open Text SA and/or Open Text ULC. 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 SA or other respective owners.
53

OpenText Archiving and Document Access For SAP Solutions 10.5 Release Notes

Uploaded by

OpenText Archiving and Document Access For SAP Solutions 10.5 Release Notes

Uploaded by

OpenText Archiving and Document

Access for SAP Solutions Release Notes

3 Packaging and Documentation .................................................................................................. 10

4 Supported Environments and Compatibility ............................................................................. 17

5 Installation and Upgrade Notes .................................................................................................. 25

6 Fixed Issues .................................................................................................................................. 35

7 Known Issues ............................................................................................................................... 37

8 Contact Information ..................................................................................................................... 53

We also recommend that you check the OpenText Knowledge Center

1.1 Release Notes Revision History

Release Notes Modification Section Modified Modifications

1.0 2013-11-21 All Initial draft

1.01 2014-04-16 2, All Wording in About and What's new;

1.02 2014-06-02 3, 4: 3.5, 4.2, 4.3 12 language installation media;

1.03 2014-06-12 7.8 Known issue with PDF output of

1.04 2014-06-17 5.3 Added warning concerning Microsoft

1.05 2014-06-30 5.3 Added cumulative patches for ECMLink

1.07 2014-08-04 5.3 Added pat105000129 for Template

1.08 2014-08-08 5.3 Updated cumulative patches for

1.09 2014-09-09 7.4 Hint about Web Viewer and

1.10 2014-10-09 4.4.5 Added SAP GUI for Windows 7.40

1.11 2014-10-16 4.4.5 Added NWBC for Desktop 5.0 support;

1.12 2014-11-20 5.3 Update cumulative patches for

7.9 Added known issue with entry

1.13 2014-12-04 3.4 Added details about OTEXBAS,

1.14 2015-01-22 3.1.1 Corrected RCS version to 10.2.1

1.15 2016-03-21 3.4 Forms Management for TCP Context

4.4.3 Required Added EhP 4 for CRM 7.0 support

1.19 2018-07-11 5.1.3 SAP Notes SAP Note 1833702

2.1 What is OpenText Archiving and Document Access for SAP

2.2 What's new in this release?

OpenText Rendition Management

OpenText License Measurement

2.3 Discontinued and Deprecated Features

3.1 Packaging and Delivery Information

3.1.1 Software Modules in Master Setup 10.5.0

Group Component Version Master

Archive Server 10.5.0 Yes

Client Software Administration Client 10.5.0 Yes

Imaging Enterprise Scan 10.5.0 Yes

Imaging ExchangeLink 10.5.0 Yes

Imaging NotesLink 10.5.0 Yes

Imaging PDF Extensions 10.5.0 Yes

Imaging Windows Viewer and DesktopLink 10.5.0 Yes

Imaging Java Viewer 10.5.0 Yes

Document Document Pipeline Base 10.5.0 Yes

Document Pipeline for DocuLink 10.5.0 Yes

Document Pipeline for Enterprise Library 10.5.0 Yes

Document Pipeline for SAP Solutions 10.5.0 Yes

Document Pipeline Info 10.5.0 Yes

Document Pipeline Remote Interface 10.5.0 Yes

Searchable PDF DocTool 11.0.0 No

Services Directory Services 10.5.0 + Patch Yes

Enterprise Library Services 10.5.0 Yes

Content Server Activator for SAP Solutions 10.0.2 Yes

Document Properties Synchronization 10.5.0 Yes

ECMLink 10.5.0 Yes

ECMLink (Needed for deployment on Content 10.0.4 No

Extensions for Enterprise Library 10.5.0 Yes

Forms 10.5.0 Yes

Imaging Enterprise Scan 10.5.0 Yes

Physical Objects 10.5.0 Yes

Pulse 10.5.0 Yes

Records Management 10.5.0 Yes

Recycle Bin 10.5.0 Yes

Renditions 10.5.0 Yes

SAP Base 10.2.0 Yes

Security Clearance 10.5.0 Yes

Template Workspaces (Case Management) 10.5.0 Yes

Web Forms 10.5.0 Yes

SAP Business Archiving and Document Access for SAP 10.5.0 No

3.1.2 Third Party Software

Group Component Version

Application Server Apache Tomcat 7.0.50

Java Java Runtime Environment 1.7

3.1.3 OpenText Customers