OpenText™ Extended ECM for SAP® Solutions

Release Notes
16.2

Product Released: 2017-03-31

Release Notes Revised: 2018-07-31

Contents
1 Introduction .......................................................................................................................... 5
1.1 Release Notes Revision History ................................................................................................. 5
2 About OpenText™ Extended ECM for SAP® Solutions ............................................................ 10
2.1 New features ........................................................................................................................... 10
2.2 General Data Protection Regulation (GDPR) ........................................................................... 11
3 Packaging and documentation.............................................................................................. 13
3.1 Packaging and delivery information ........................................................................................ 13
3.2 Related documentation ........................................................................................................... 22
3.3 Delivery.................................................................................................................................... 23
3.4 Note on the End User License Agreement .............................................................................. 23
4 Supported environments and compatibility .......................................................................... 25
4.1 Supported systems .................................................................................................................. 25
4.2 Content Server Object Types Supported in SAP UI ................................................................. 37
4.3 OpenText Product Compatibility ............................................................................................. 39
4.4 Language support .................................................................................................................... 39
4.5 Microsoft Azure Virtual Machine ............................................................................................ 40
5 Requirements for SAP Applications ...................................................................................... 41
5.1 List of Requirements................................................................................................................ 41
6 Installation and upgrade notes ............................................................................................. 43
6.1 Installation Notes .................................................................................................................... 43
6.2 Content Server 16 License Keys .............................................................................................. 46
6.3 User License Type Assignment ................................................................................................ 46
6.4 Language Installation............................................................................................................... 47
6.5 Upgrade notes ......................................................................................................................... 47
6.6 OpenText Vendor Keys ............................................................................................................ 50
6.7 Attribute Change Packages (ACPs) .......................................................................................... 51
7 Patches ................................................................................................................................ 52
7.1 Hotfixes.................................................................................................................................... 52
7.2 Updates ................................................................................................................................... 53
8 Fixed Issues ......................................................................................................................... 56
9 Known Issues ....................................................................................................................... 58

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

i
10 Troubleshooting................................................................................................................... 71
11 Contact information ............................................................................................................. 81

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

ii
List of Tables
Table 1 - Release Notes Revision History ............................................................................................... 5
Table 2 - Detailed Component List of OpenText™ Extended ECM for SAP® Solutions ......................... 14
Table 3- Compatibility Business Center Task App ID ot.approve.request02 ........................................ 18
Table 4 - Add-ons of OpenText™ Fiori Business Object Browsing Enabler for SAP Solutions 16.2 ...... 20
Table 5- Compatibility Business Center Task App ID ot.approve.request03 ........................................ 20
Table 6 - Add-ons of OpenText™ Fiori Business Object Browsing Enabler for SAP Solutions 16.3 ...... 21
Table 7 - Application Server Support .................................................................................................... 27
Table 8 - Microsoft Office Support ....................................................................................................... 28
Table 9 - Supported SAP Business Suite & S/4HANA Applications ....................................................... 28
Table 10 - Required SAP Components and Support Packages ............................................................. 29
Table 11 - Required SAP Components and Support Packages for Fiori UI Support ............................. 33
Table 12 - Supported SAP GUIs ............................................................................................................ 36
Table 13 - Required SAP Support Packages and Patches ..................................................................... 36
Table 14 - Container Content Server Object Types Supported in Workspaces .................................... 37
Table 15 - Item Content Server Object Types Supported in SAP UI ..................................................... 38
Table 16 - OpenText Product Compatibility ......................................................................................... 39
Table 17 - Language Support ................................................................................................................ 39
Table 18 - SAP (OSS) Notes ................................................................................................................... 44
Table 19 - Available Hotfixes ................................................................................................................ 52
Table 20 - Quarterly Update History .................................................................................................... 53
Table 21 - Available ABAP Support Packages ....................................................................................... 54
Table 22 - Fixed Issues .......................................................................................................................... 56
Table 23 - Known Issues ....................................................................................................................... 58
Table 24 - Troubleshooting................................................................................................................... 72

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

iii
Table of Figures
Figure 1 - Main Components of OpenText™ Extended ECM for SAP® Solutions ................................. 13

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

iv
1 Introduction
These release notes provide an overview of OpenText™ Extended ECM 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.6.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-02 6.3 User License Type Changed referenced guide for more
Assignment information about licensing to Customizing
Guide

2017-05-03 9 Known Issues Upgrading Extended ECM for SAP Solutions

10.5 SP1 to 16.2 disables all Extended ECM
themes. Added simple solution.

3.1.1 Software Added Monitoring 16.2.0

Components

2017-05-08 3.1.4 Updated Added component updates

Components

2017-05-30 4.1.2 Application Server Changed Tomcat version from 8.x to 8.5
Support

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

5
 2017-06-29 7.1.1 Available Hotfixes Released Extended ECM for SAP Solutions
16.2.1 (June 2017 Content Server module
update)

Fixed issue with smart UI localization in

Business Content Window

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

Spanish localization

2017-07-13 4.4 Language support Released Arabic, Chinese (Simplified), Dutch,

Japanese, Portuguese, Russian, and
Ukrainian localization

4.1.7 Supported SAP Added SAP GUI for Windows 7.50 support
GUIs

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

2017-08-02 4.4 Language support Released Korean localization

2017-09-18 9 Known Issues Folder Browse View embedded in Business

Content Window fails to show inline actions

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

2017-09-29 7.1.1 Available Hotfixes Released Extended ECM for SAP Solutions
16.2.2 (September 2017 Content Server
module update)
New features that Extended ECM for SAP
2.1 New features
Solutions 16.2.2 introduces
Added instructions on how to set the
8 Fixed Issues
OpenText Directory Partition field in
Extended ECM Connections
2017-10-02 4.4 Language support Released Kazakh localization
Extended ECM for SAP Solutions 16.2.2
4.1.3 Server Platform
2017-11-07 introduces support for both Windows 2016
Support Matrix
and SQL Server 2016 SP1.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

6
 4.1.6.1 Supported SAP
2017-11-09 Business Suite and Added S/4HANA On-Premise 1709 support
S/4HANA Applications

4.5 Microsoft Azure

2017-11-14 Added Microsoft Azure support
Virtual Machine
Added recommendation to upgrade to
2018-01-09 7.1.1 Available Hotfixes
Extended ECM Platform 16.2.3
7.1.2 Quarterly Update
2018-01-10 Added table of quarterly update history
History
Added warning: Enterprise Library Services
7.1.2 Quarterly Update
2018-01-22 16.2 is incompatible with Content Server
History
16.2.2
2018-01-30 4.1.6 SAP Server Support Added SAP components for S/4HANA 1709

4.1.3 Server Platform

2018-02-27 Updated server platform support matrix
Support Matrix

4.1.7 Supported SAP

2018-03-19 Added SAP NetWeaver 7.52 support
GUIs

3.1.1 Software Added OpenText My Support URL for

Components updated components
In S/4HANA, the Business Content Window
9 Known Issues does not show any notes for business
partners (BUS1006)
New features in Extended ECM for SAP
2.1 New features
2018-03-29 Solutions 16.2.4

Updated list of components for 16.2.4 (16

3.1.1 Software
EP4)
Components
Extended ECM for SAP Solutions 16.2.4 (16
6.5.2 Upgrade Path
EP4) does require that Content Server,
Archive Center, and Enterprise Library be
upgraded before SAP

Released Extended ECM for SAP Solutions

7 Patches
16.2.4 (16 EP4, March update)

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

7
 3.1.1 Software Added download URL for 16.2.4 (16 EP4)
2018-04-04
Components installation ISO images

7 Patches Added missing download URLs

Removed RTL support from the new 16.2.4
2018-04-11 2.1 New features
features
ILM not supported in Content Server 16.2.2
2018-04-19 9 Known Issues
and higher
4.1.3 Server Platform Updated server platform support
2018-04-23
Support Matrix information
After upgrading to 16.2.2 or higher, all
2018-04-27 7.1.2 Quarterly Update
business applications use the Extended ECM
History
Platform license model. Such an upgrade
requires reviewing access privileges for all
business applications.
3.1.1 Software Corrected Searchable PDF DocTool version to
2018-05-03
Components 16.2.0

2018-05-08 9 Known Issues Added S/4HANA integration restrictions

2.2 General Data

2018-05-11 Protection Regulation Added new GDPR section
(GDPR)

4.1.7 Supported SAP

2018-05-24 Added SAP GUI for HTML support restriction
GUIs
Added URL to 16.2.4 (16 EP4) localization ISO
4.4 Language support
images
4.1.1 Client Platform
2018-07-02 Updated client platform support information
Support
Released Extended ECM for SAP Solutions
7.1 Hotfixes 16.2.5 (June 2018 Content Server module
update)
2018-07-20 7.2.2 Available ABAP OTEXBAS 1620_700 SP1 requires SAP_BASIS
Support Packages 700 0018
Updated information about business object
2018-07-25 3.1.3, 3.4.1, 4.1.6, 9
browsing and SAP Server support
In Diagnostic Report, the OTDS REST test fails
2018-07-27 10 Troubleshooting
if the OTDS URL contains no port number

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

8
 Specified that known multi-assignment
2018-07-31 9 Known Issues
issues are fixed in 16.2.4 (16 EP4)

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

9
2 About OpenText™ Extended ECM for SAP® Solutions
This section provides an overview of OpenText™ Extended ECM for SAP® Solutions 16.2.

Many business processes, in both commercial and government organizations, span the worlds of
transactional data and business content. OpenText™ Extended ECM for SAP® Solutions extends the
transactional process management capabilities of SAP Business Suite with comprehensive Enterprise
Content Management (ECM) capabilities, including document management, records management,
and collaboration.

With OpenText™ Extended ECM for SAP® Solutions, you can unite the worlds of SAP Business Suite
and ECM in a single solution, reducing the risks and costs of records mismanagement, increasing
information worker productivity and enhancing your ability to comply with regulations.

OpenText™ Extended ECM for SAP® Solutions provides the powerful concepts of business
workspaces, business attachments, business relationships and business policies. These concepts are
the foundation for the tight integration of Extended ECM into SAP Business Suite.

OpenText™ Extended ECM for SAP® Solutions also allows declaring an SAP ArchiveLink document as
a record and therefore putting such a document under control of Records Management. The
declaration can be performed automatically during document creation or interactively by an
application user. In addition, the declaration procedure can be performed in batch mode by an
administrator.

2.1 New features

OpenText™ Extended ECM for SAP® Solutions 16.2 introduces the following features:

• Business workspace integration (via smart UI) into C4C user interface
• C4C support for Opportunity, Lead, and Account/Customer business objects
• Scheduled processing support for C4C business objects
• Flexible layout for SAP Business content window
• Metadata-based template assignment
• Fiori Business Object Browsing for Extended ECM for SAP Solutions

OpenText™ Extended ECM for SAP® Solutions 16.2.2 introduces the following features:

• Ticket/Service Request business object support for C4C

• Multiple repositories support and default behavior for type creation over CMIS

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

10
OpenText™ Extended ECM for SAP® Solutions 16.2.4 introduces the following features:

• Support working with smart view perspectives in Business Content Window

• Use of integration-specific themes for folder browse widget in SAP GUI, C4C and Fiori
• Support asynchronous creation and update of business workspace in batch process
• Support declaration of multi-assigned ArchiveLink documents
• Support asynchronously declaration for ArchiveLink documents
• Improve selection of C4C business objects for scheduled processes by considering create or
change date
• Support of X.509 authentication for C4C
• Support Business Center 16.3 and its new features
• Support for uninstalling SAP add-on packages

2.2 General Data Protection Regulation (GDPR)

The General Data Protection Regulation (GDPR) is a European Union (EU) law that gives residents
greater protection and control of their personal data. It regulates the data companies inside and
outside the EU can collect, store, and transfer – as well as how they use it. All companies that
process EU resident data must comply with GDPR, starting on May 25, 2018.

OpenText™ Extended ECM for SAP® Solutions offers freely definable data containers called business
workspaces. A business workspace is a kind of folder to manage content. Content could be, for
example, Word, Excel, or PDF documents. Business workspaces are enriched with context-related
metadata and relations. You could divide metadata in two groups: (1) Attributes filled by data from
the leading business application like an SAP system and (2) attributes filled by users or workflows.

Furthermore, users in OpenText™ Extended ECM for SAP® Solutions have a user profile with
personal data like name, communication data, or personal data.

Software solutions like OpenText™ Extended ECM for SAP® Solutions can neither be considered as
GDPR-compliant nor GDPR-uncompliant. Every customer using OpenText™ Extended ECM for SAP®
Solutions is responsible for ensuring GDPR compliance in their organization.

OpenText™ Extended ECM for SAP® Solutions provides different means to help organizations be
GDPR compliant:

• Records Management to ensure a retention schedule as well as disposition at the end of

managed content lifecycle

• Audit logging to see, who accessed sensitive data

• Web Reports to do sophisticated reporting on customer or employee data used inside

OpenText™ Extended ECM for SAP® Solutions

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

11
 • Security Clearance to govern access levels for sensitive information only for defined user
groups in an organization

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

12
3 Packaging and documentation
Downloads and documentation for OpenText™ Extended ECM for SAP® Solutions are available on
OpenText My Support (https://knowledge.opentext.com/). Release notes are frequently updated.

3.1 Packaging and delivery information

The bundle OpenText™ Extended ECM for SAP® Solutions consists of many individual components.
For your convenience, this bundle is delivered in a single ISO-Image.

Figure 1 shows the main components of OpenText™ Extended ECM for SAP® Solutions.

Figure 1 - Main Components of OpenText™ Extended ECM for SAP® Solutions

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

13
 Software Components
Table 2 lists all components of OpenText™ Extended ECM for SAP® Solutions 16.2.4 (16 EP4). Most
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™ Extended ECM for SAP® Solutions
master setup.

The installation ISO images for OpenText™ Extended ECM for SAP® Solutions 16.2.4 (16 EP4) are
available at the following location in the patch area of OpenText My Support:

https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=72200371&objAction=browse
&sort=name&viewType=1
Table 2 - Detailed Component List of OpenText™ Extended ECM for SAP® Solutions
Master
Group Component Version
Setup
Activator for SAP Solutions 16.0.0 Yes
Connected Workspaces 16.2.4 Yes

Content Server
Including:
• Active View
• Attribute Extensions
• Classification Professional
• Classifications
• Content Suite Viewer
• Content Web Services
• Document Properties Synchronization
Content Server and • Enterprise Connect
16.2.4 Yes
Modules • Object Importer (full license)
• Object Importer, Records Management
Edition
• Office Editor
• Physical Object
• Perspective Manager
• Records Management
• Security Clearance
• Web Reports (full license)
• Workflow

Content Server SDK 16.2.4 No

Extended ECM for SAP Solutions 16.2.4 Yes

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

14
 Master
Group Component Version
Setup
Extended ECM Platform 16.2.4 Yes
Extensions for Enterprise Library 16.2.4 Yes
Imaging Enterprise Scan – Web Interface 16.2.1 Yes
Imaging Reviews and Notes 16.0.0 Yes
Monitoring Agent 16.2.0 No
Remote Cache (Module) 16.2.4 Yes
Template Workspaces 16.2.4 Yes
WebReports Workflow Extensions 16.2.0 Yes
Remote Cache Server 16.2.4 Yes
Content Server
Remote Cache Smart Cache Services for Primary Server 16.2.4 Yes
Smart Cache Services for Remote Server 16.2.4 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 Yes
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 Content Server 16.2.0 Yes
Document Pipeline for DocuLink 16.2.0 Yes
Document Document Pipeline for Enterprise Library 16.2.0 Yes
Pipelines
Document Pipeline for SAP Solutions 16.2.0 Yes
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 Yes
Brava! Server Components (limited usage right for
16.3.0.381 Yes
Content Suite Viewer)

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

15
 Master
Group Component Version
Setup
Brava! View for SAP Solutions 16.2.4 Yes
Content Server eLink Server 16.0.0 Yes
Directory Services (OTDS) 16.2.4 Yes
Other Servers &
Services Enterprise Library Services 16.2.0 Yes
Extended ECM CMIS 16.2.4 Yes1
Extended ECM Web Services 16.2.4 Yes
Imaging Web Viewer 16.0.0 No
Administration Client 16.2.0 Yes
Enterprise Connect Framework 16.2.4 Yes2
Imaging Enterprise Scan 16.2.0 Yes
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
Office Editor Client 16.2.4 Yes2

Extended ECM 16.2

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

1
The Windows media offers an MSI file. Linux media offers a WAR file for manual deployment.
2
The Windows media offers both a 32-bit and a 64-bit version. However, the master setup only offers
the 64-bit version.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

16
 Master
Group Component Version
Setup

Fiori Business Object Browsing Enabler for SAP

16.3 No
Solutions

SAP NetWeaver
Portal Connect 10.5.0 No
Portal

For detailed information about individual components of OpenText™ Extended ECM for SAP®
Solutions, please have a look at the respective release notes.

3.1.1.1 Tempo Box

A customer who is running the minimum of OpenText™ Extended ECM for SAP® Solutions licenses is
eligible to run Tempo Box for all employees of the company/legal entity (Limitations see below).

Employees without dedicated OpenText™ Extended ECM for SAP® Solutions, Extended ECM Platform
license, Content Suite Platform license or Tempo Box Premium license: These employees are not
allowed to access enterprise content (i.e. content managed within the Enterprise Workspace of
Content Server). Particular mention deserves that these employees are not allowed to access
business workspaces.

External users: External users of Tempo Box are offered free of charge. However, they are offered
limited functionality in the way that they can only interact with content that has been explicitly
shared with them. External users cannot share content, or add content outside of the folders that
have been shared with them.

3.1.1.2 Licensing Specialties

Following software is part of the physical delivery but not part of OpenText™ Extended ECM for
SAP® Solutions:
• Email Cloud Archiving
• Document Pipeline for File Archiving

Recommendation for OpenText™ Extended ECM for SAP® Solutions 16.2

Installations

Note

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

17
 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™ Fiori Business Object Browsing for Extended ECM for SAP Solutions
OpenText™ Fiori Business Object Browsing for Extended ECM for SAP Solutions is a collective term,
which includes the following:

• Compatible versions of
o OpenText™ Extended ECM for SAP Solutions
o OpenText™ Fiori Business Object Browsing Enabler for SAP Solutions: a collection of
compatible ABAP Add-Ons of OpenText™ Business Center for SAP Solutions. 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.

Important
Usage restrictions are detailed in chapter 3.4.1

Please check the compatibilities depending on the version of the Business

Center Fiori Task App. Make sure to have all support packages

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

Compatibility mainly depends on the version of the Business Center Fiori Task App.

3.1.3.1 Business Center Task App ID ot.approve.requests

Use ot.approve.requests02 or if possible ot.approve.requests03.

3.1.3.2 Business Center Task App ID ot.approve.requests02

Table 3- Compatibility Business Center Task App ID ot.approve.request02
Business Center Task App ID ot.approve.requests02

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

18
 Business Center Task App URL /sap/bc/ui5_ui5/otbcwui/pf07_bc_ui_02

First delivery with Business Center for SAP 16 Update 1, OTBCWUI

0740_003 SP1

Deprecated with Business Center for SAP 16.3

OTBCWUI 0740_004

Compatible custom view of Archiving Custom View

and Document Access for SAP Solutions
otx.alplus.docs4otbcwui.view.BusinessDocumentsTab
16.2
App ID

otx.alplus.docs4otbcwui

App URL

/sap/bc/ui5_ui5/otx/alf_docs4bc

ABAP Add-On

OTEXBASF 1620_700

Compatible custom view of Extended Custom View

ECM for SAP Solutions 16.2
otx.ecmlink.bws4otbcwui.view.BusinessWorkSpaceTab

App ID

otx.ecmlink.bws4otbcwui

App URL

/sap/bc/ui5_ui5/otx/rmf_bws4bc

ABAP Add-On

OTEXRLF 1620_700

Table 4 - 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 2 are
required for the framework to build custom Fiori apps:

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

19
Table 4 - 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
OTBCFND 0700_003 SP2

OTBCWSR 0740_003
OTBCWSR 0740_003 SP1

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

3.1.3.3 Business Center Task App ID ot.approve.requests03

Table 5- Compatibility Business Center Task App ID ot.approve.request03
Business Center Task App ID ot.approve.requests03

Business Center Task App URL /sap/bc/ui5_ui5/otbcwui/pf07_bc_ui_03

First delivery with Business Center for SAP 16.3,

OTBCWUI 0740_004

Compatible custom views of Custom Views

Archiving and Document Access
otx.alplus.doc4otbcwui02.view.item.BusinessDocuments,
for SAP Solutions 16.2.4
otx.alplus.doc4otbcwui02.view.item.BusinessDocumentsSplit
+
otx.alplus.doc4otbcwui02.view.item.DocumentDisplay

App ID

otx.alplus.docs4otbcwui02

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

20
 App URL

/sap/bc/ui5_ui5/otx/alf_docs4bc_02

ABAP Add-On

OTEXBASF 1620_700 SP1

Compatible custom view of Custom View

Extended ECM for SAP Solutions
otx.ecmlink.bws4otbcwui02.view.item.BusinessWorkSpace
16.2.4
App ID

otx.ecmlink.bws4otbcwui02

App URL

/sap/bc/ui5_ui5/otx/rmf_bws4bc_02

ABAP Add-On

OTEXRLF 1620_700 SP1

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

Target System ABAP Add-On

SAP Backend OTBCBAS 0700_004

OTBCBAS 0700_003 Support Package 1 (SP1)

OTBCINB 0700_004
OTBCINB 0700_004 SP1

OTBCFND 0700_004
OTBCFND 0700_004 SP1

OTBCWSR 0740_004
OTBCWSR 0740_004 SP1

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

21
 OTBCWUI 0740_004
SAP Gateway (Hub / Frontend)
OTBCWUI 0740_004 SP1

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
• 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™ Extended ECM 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/).

• OpenText™ Extended ECM for SAP® Solutions - Administration Guide (ERLK160200-00-AGD-

EN-1)
• OpenText™ Extended ECM for SAP® Solutions - Customizing Guide (ERLK160200-00-CGD-EN-
1)
• OpenText™ Extended ECM for SAP® Solutions - Installation and Upgrade Guide
(ERLK160200-00-IGD-EN-1)
• OpenText™ Extended ECM for SAP® Solutions - User Management and Access Control
Scenarios (ERLK160200-00-CUM-EN-1)
• OpenText™ Extended ECM for SAP® Solutions - Overview Guide (ERLK160200-00-GGD-EN-1)
• OpenText™ Extended ECM for SAP® Solutions - Installation Guide for Microsoft Windows
with Microsoft SQL Server (ERLK160200-00-IWS-EN-1)
• OpenText™ Extended ECM for SAP® Solutions - Installation Guide for Microsoft Windows
with Oracle (ERLK160200-00-IWO-EN-1)
As first step, we recommend to look at OpenText™ Extended ECM for SAP® Solutions - Overview
Guide (ERLK160200-00-GGD-EN-1).

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

22
3.3 Delivery
OpenText Customers
OpenText customers can download OpenText™ Extended ECM for SAP® Solutions 16.2 from the
“Download” section on OpenText My Support.

SAP Customers
SAP customers can download OpenText™ Extended ECM 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.

3.4 Note on the End User License Agreement

Usage of OpenText™ Fiori Business Browsing Enabler for SAP Solutions
OpenText™ Fiori Business Object Browsing Enabler for SAP Solutions adds the Business Center
Foundation of Business Center for SAP Solutions to implement custom SAP Fiori apps, which
integrate the SAP Fiori standard apps of OpenText™ Extended ECM for SAP® Solutions or 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
▪ 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, that need extra 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 OpenText™ Extended ECM for SAP® Solutions
o SAP Document Access by OpenText
o SAP Extended Enterprise Content Management (ECM) by OpenText

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

23
 • The integration of the Business Workspace Fiori App is restricted to the following licenses
products:
o OpenText™ Extended ECM for SAP® Solutions
o SAP Extended Enterprise Content Management (ECM) by OpenText

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.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

24
4 Supported environments and compatibility
This section provides details about supported platforms, systems, and versions.

4.1 Supported systems

Client Platform Support
OpenText™ Extended ECM for SAP® Solutions supports the same web browsers as OpenText Content
Suite Platform. For detailed information, please look at the following release notes.

OpenText Content Server 16.2 Release Notes:

https://knowledge.opentext.com/knowledge/llisapi.dll/Open/67817771

OpenText Content Suite Platform 16.4.0 Release Notes:

https://knowledge.opentext.com/knowledge/llisapi.dll/Open/72671938

4.1.1.1 Support for Fiori Web User Interface

This section lists the specific restrictions for the usage of the Fiori Web User Interface.

The list of supported client platforms depends on the SAP Front-End Server on which the Fiori Web
User Interface is hosted. See SAP’s Product Availability Matrix (PAM) at
https://support.sap.com/pam for details.
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 16 Update 1.

The Business Workspace Fiori app uses the integration widget of the Smart View of OpenText™
Content Server. Therefore, the basic restrictions of the Smart View apply. Please read the chapters
about mobile platform support and client platform support in the Release notes of OpenText™
Content Server for more details.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

25
 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 Workspace is not supported.

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

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

26
 Application Server Support
The following chart describes the application servers and Java versions that OpenText™ Extended
ECM for SAP® Solutions 16.2 supports.
Table 7 - Application Server Support
Supported Application Server Java supported on Application Server

Tomcat 8.5 Java 8.x

WebSphere 8.5 Java 8.x

Server Platform Support Matrix

Note that databases are supported on any operating system platform supported by the database
vendor. It is not required that the database be on the same platform as Content Server. Databases
which have a client component must have that client supported on an operating system platform
supported by Content Server.

Please also 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.

Some components, like OpenText Archive Center, may support more platforms than the Content
Suite Platform. For component-specific details, please refer to the respective release notes.

OpenText™ Extended ECM for SAP® Solutions supports the same server OS and server database
versions as OpenText Content Suite Platform. For detailed information, please look at the following
release notes.

OpenText Content Server 16.2 Release Notes:

https://knowledge.opentext.com/knowledge/llisapi.dll/Open/67817771

OpenText Content Suite Platform 16.4.0 Release Notes:

https://knowledge.opentext.com/knowledge/llisapi.dll/Open/72671938

Virtualization Support
OpenText Content Server is supported for use with the server operating systems listed in the
previous section. The supported server operating systems may be installed on physical or virtual
hosts. Customers that choose to use a virtual environment are encouraged to select a virtualization

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

27
platform intended for production systems and known to be fully supported by the server operating
system vendor.

Please note that Content Server is a resource-intensive application and will require at least the same
amount of resources in a virtual environment as it would in a physical environment. Therefore,
additional resource scaling may be required to maintain the same level of performance in a virtual
environment as observed in physical environment.

Microsoft Office Support

Content Server 16 supports storing, indexing, viewing, and thumbnail generation of the files
generated by the versions of Microsoft Office in the table below.
Table 8 - Microsoft Office Support
Versions Notes

Office 2010 Word, Excel, and PowerPoint 2010

Office 2013 Word, Excel, and PowerPoint 2013

Office 2016 Word, Excel, and PowerPoint 2016

SAP Server Support

4.1.6.1 Supported SAP Business Suite and S/4HANA Applications
Table 9 - Supported SAP Business Suite & S/4HANA Applications

OpenText Archiving and

SAP Platform OpenText Extended ECM
Document Access

SAP AS ABAP 7.1 Supported only for data archiving N/A

ERP 6.0, ERP 6.0,

SAP Netweaver 7.0
EhP1-3 for ERP 6.0 EhP1-3 for ERP 6.0

All SAP systems running on the All SAP systems running on the
SAP Netweaver > 7.0
required SAP_BASIS versions, for required SAP_BASIS version, for
EhP 1 - 2 for SAP NetWeaver instance: instance:
7.0
EhP 1 for SAP NetWeaver 7.3 • EhP4-8 for ERP 6.0 • EhP4-8 for ERP 6.0
SAP NetWeaver 7.40
SAP NetWeaver 7.50, 7.51, • CRM 7.0 • CRM 7.0
7.52
• EhP1-4 for CRM 7.0 • EhP1-4 for CRM 7.0

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

28
 • SRM 7.0 • SRM 7.0
• EhP1-4 for SRM 7.0 • EhP1-4 for SRM 7.0

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

For further information, please look at the release notes and guides of OpenText™ Archiving and
Document Access for SAP Solutions 16.2.
4.1.6.2 SAP HANA Support

OpenText™ Extended ECM for SAP® Solutions 16.2 supports SAP Business Suite on SAP HANA
database. OpenText™ Extended ECM for SAP® Solutions is SAP certified for SAP HANA on SAP
NetWeaver 7.40 onwards.

4.1.6.3 Required SAP Support Packages

Table 10 - Required SAP Components and Support Packages

OpenText Software Prerequisite set1 of Software Support

Release
Component OpenText Add-On Component Package Level

700, 702,
SAP_BASIS
Prerequisite set 01 SAP_BASIS 731, 740,
700: 0016
750

Archiving and Document

Access for SAP® Solutions 750, 751,
SAP_BASIS
752
OTEXBAS 1620_700
Prerequisite set 02
750, 751,
SAP_ABA 752, 75A,
75B, 75C

OTEXBAS 1620_700

700, 701,
Archiving and Document SAP_ABA 700:
702, 731,
0018,
Access for SAP® Solutions SAP_ABA 750, 751,
Prerequisite set 01 SAP_ABA 701:
OTEXBAS 1620_700: SP 1 752, 75A,
0003
75B, 75C

700, 701,
SAP_BASIS SAP_BASIS
702, 731,
700: 0018,
750, 751,

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

29
 752, 75A, SAP_BASIS
75B, 75C 701: 0003

OTEXBAS 1620_700

Prerequisite set 01 700 - 702,

SAP_BASIS
SAP_BASIS 731, 740,
700: 0016
750
Extended ECM for SAP®
OTEXBAS 1620_700
Solutions
OTEXRL 1620_700
750, 751,
SAP_ABA 752, 75A,
Prerequisite set 02
75B, 75C

750, 751,
SAP_BASIS
752

OTEXBS
Extended ECM for SAP® OTEXBAS 1620_700 1620_700:
Solutions Prerequisite set 01 0001
OTEXRL 1620_700: SP 1
OTEXRL 1620_700

OTEXBAS 1620_700

600 – 606,
SAP_APPL
616 - 618
Prerequisite set 01
Archiving and Document
Access for SAP® Solutions 700 - 702,
SAP_BASIS
for ERP SAP_BASIS 731, 740,
700: 0016
750
OTEXERP 1620_600

OTEXBAS 1620_700

Prerequisite set 02 700 - 702,

SAP_BASIS
SAP_BASIS 731, 740,
700: 0016
750

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

30
 617, 618,
SAP_FIN 700, 720,
730

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 special
BBPCRM 700 - 704
note

OTEXRL 1620_700
Prerequisite set 01 (OTEXBAS) (1620_700)

701, 702,
SAP_BASIS 732, 740,
Extended ECM for SAP® 750
Solutions for CRM
OTEXRLC 1620_700 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,
Special
SAP_ABA 701 0003, BBPCRM 700 02,
requirements
WEBCUIF 700 0002)
See SAP OSS Notes:
1625333 - SP Equivalence for update/upgrade
to EHP 1 for SAP CRM 7.0

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

31
 1625284 - SP Equivalence for update/upgrade
to EHP 2 for SAP CRM 7.0

OTEXRL
Extended ECM for SAP® OTEXRL 1620_700 1620_700:
Solutions for CRM Prerequisite set 01 0001
OTEXRLC 1620_700: SP 1
OTEXRLC 1620_700

OTEXRL 1620_700
(OTEXBAS) (1620_700)

Prerequisite set 01 701, 702,

SAP_BASIS 731, 740,
750

SRM_SERVER 700 - 704

Extended ECM for SAP®
Although not explicitly added as an import
Solutions for SRM
condition of OTEXRLS, the following
OTEXRLS 1620_700 requirements must be met:
SRM 7.0 SP Stack 08 (SAP_BASIS 701 0007,
Special SAP_ABA 701 0007, SRM_SERVER 700 0008)
requirements
See SAP OSS Notes:
1494683 - SAP SRM 7.0 Enh.Pk.1 SP Stacks -
Release & Information Note
1582094 - EHP2 for SAP SRM 7.0 SP stacks -
Release & Information Note

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

1
Prerequisite set: In transaction SAINT, see menu Goto > Installation and Support Pack.
Directory. In the list of packages a set of import condition is named prerequisite sets.
SPAM/SAINT Version: The most recent Attribute Change Packages (ACP) require 0066.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

32
4.1.6.4 Fiori UI Support

SAP Fiori apps of OpenText™ Extended ECM 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.

They also require the SAP Fiori Apps of OpenText™ Archiving and Document Access for SAP Solutions
16.2 (Add-On OTEXBASF 1620_700).
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 11 for detailed requirements.
Table 11 - Required SAP Components and Support Packages for Fiori UI Support

OpenText Software Prerequisite set1 of Software Support

Release
Component OpenText Add-On Component Package Level

IW_BEP 200 0010

Prerequisite set 01
700 – 02, SAP_BASIS 700:
SAP_BASIS
731 0018

SAP_BASIS 740
Prerequisite set 02
SAP_GWFND
Archiving and Document SAP_GWFND 740, 750
740: 0009
Access for SAP® Solutions
OTEXBASO 1620_700 750, 751,
SAP_ABA 752, 75A,
75B, 75C

Prerequisite set 03 750, 751,

SAP_BASIS
752

750, 751,
SAP_GWFND
752

Archiving and Document

Prerequisite set 01 OTEXBASO 1620_700
Access for SAP® Solutions

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

33
 OTEXBASO 1620_700: SP
1

IW_BEP 200 0010

Prerequisite set 01
700-702, SAP_BASIS 700:
SAP_BASIS
731 0018

SAP_BASIS 740
Prerequisite set 02
SAP_GWFND
Extended ECM for SAP® SAP_GWFND 740, 750
740: 0009
Solutions OData Services
OTEXRLO 1620_700 750, 751,
SAP_ABA 752, 75A,
75B, 75C

Prerequisite set 03 750, 751,

SAP_BASIS
752

750, 751,
SAP_GWFND
752

SAP_BASIS 740, 750

Prerequisite set 01
SAP_UI 740:
SAP_UI 740, 750
0013

OpenText™ Archiving and 750, 751,

Document Access for SAP SAP_ABA 752, 75A,
Solutions Fiori Apps 75B, 75C
OTEXBASF 1620_740
Prerequisite set 02 750, 751,
SAP_BASIS
752

750, 751,
SAP_UI
752

OpenText™ Archiving and

Document Access for SAP Prerequisite set 01 OTEXBASF 1620_740
Solutions Fiori Apps

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

34
 OTEXBASF 1620_740:
SP 1

OTEXBASF 1620_740

SAP_BASIS 740, 750

Prerequisite set 01
SAP_UI 740, 750 SAP_UI 740:
0013

Extended ECM for SAP®

Solutions Fiori Apps OTEXBASF 1620_740
OTEXRLF 1620_740
750, 751,
SAP_ABA 752, 75A,
75B, 75C
Prerequisite set 02
750, 751,
SAP_BASIS
752

750, 751,
SAP_UI
752

Extended ECM for SAP®

Solutions Fiori Apps Prerequisite set 01 OTEXRLF 1620_740
OTEXRLF 1620_740: SP 1

Information is based on most recent Attribute Change Packages (ACP) from patches area.
1
Prerequisite set: In transaction SAINT, see menu Goto > Installation and Support Pack.
Directory. In the list of packages a set of import condition is named prerequisite sets.
SPAM/SAINT Version: The most recent Attribute Change Packages (ACP) require 0066.

4.1.6.5 Fiori Business Object Browsing Enabler Support

The Add-ons of Fiori Business Object Browsing Enabler are the same of the respective version of
OpenText™ Business Center for SAP Solutions. Please have a look at the specific system
requirements in the release notes and documentation in OpenText™ My Support in area Business
Center for SAP Solutions.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

35
 Supported SAP GUIs
The supported SAP GUIs depend only on the SAP Basis/NetWeaver version.
Table 12 - Supported SAP GUIs
SAP
NetWeaver
SAP Software SAP GUI for SAP GUI for SAP GUI for
Version Business
Component Windows HTML Java
Client
(NWBC)

SAP Basis / 5.0 Stand- -

7.0 7.40, 7.50 Integrated
NetWeaver alone

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

7.4 7.40, 7.50 Integrated 5.0 -

7.5, 7.51,
7.40, 7.50 Integrated 5.0 -
7.52

Table 13 - Required SAP Support Packages and 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

Note: SAP GUI for HTML Support Restriction

SAP GUI for HTML is a limited SAP GUI for Windows emulator. OpenText™
Extended ECM for SAP® Solutions fully supports SAP GUI for Windows integration.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

36
 However, OpenText™ Extended ECM for SAP® Solutions can only restrict the SAP
GUI for HTML support to issues also reproducible in SAP GUI for Windows.

4.2 Content Server Object Types Supported in SAP UI

Table 14 lists the Content Server object types that are supported inside business workspaces. Other
Content Server object types are not currently supported.

Table 14 - Container Content Server Object Types Supported in Workspaces

Shown as Create Content

Content Server Object Supported in
Folder Command Server Smart
Type SAP UI3
in SAP UI in SAP UI UI

Folder Yes Yes Yes Yes

Business Workspace Yes Yes Yes Yes

Yes but Yes but Yes but

Binder No
deprecated deprecated deprecated

Yes but Yes but Yes but

Cases No
deprecated deprecated deprecated

Related Business
Yes Yes No Yes
Workspaces

No (shown Yes
Collection Yes No
separately) Browse only

Yes
No (shown
Task List Yes No Classic UI
separately)
Browse only

No (shown Yes
Task Group Yes No
separately) Classic UI

3
“SAP UI” applies here to both the new OpenText Business Content and the classic business workspace
browser

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

37
 Browse only

No (shown
Discussion Yes No No
separately)

Yes
Compound Document Yes Yes No
Browse only

Table 15 - Item Content Server Object Types Supported in SAP UI

Shown as Create Content

Content Server Object Supported
Folder Command Server Smart
Type in SAP UI
in SAP UI in SAP UI UI

Document Yes N/A Yes Yes

Yes
Text Document Yes N/A No
Read only

Yes
Opens
E-Mail Yes N/A No Outlook or
download
dialog

URL Yes N/A No Yes

Yes (for
Shortcut N/A No Yes
documents)

Poll Yes N/A No No

Yes
yes (in right
Task N/A No Classic UI
panel)
Read only

yes (in right No (shown

Milestone No No
panel) separately)

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

38
 No (shown
Search Query Yes No Yes
separately)

No (shown
Live Report Yes No No
separately)

Physical Item Yes N/A No No

4.3 OpenText Product Compatibility

The section provides details about which versions of other OpenText products are compatible with
this release of OpenText™ Extended ECM 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.

Table 16 - 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

Connected Workspaces 16.2

4.4 Language support

OpenText™ Extended ECM for SAP® Solutions 16.2 is currently available in the following languages.
Table 17 - Language Support

Components

AR DE EN ES FR IT JA KK KO NL PT RU UK ZF ZH

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

39
 End-user
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

The default UI language for the components is English; other languages are available as language
packs or language module versions on OpenText My Support (Open Text customers) and on the SAP
Support Portal (SAP customers). Starting with version 16.2, the localization of the Fiori apps is also
available in (ABAP) language packs.

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

The OpenText™ Extended ECM for SAP® Solutions 16.2.4 (16 EP4) localization ISO images are
available on OpenText My Support at the following location:
https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=74336342

4.5 Microsoft Azure Virtual Machine

Microsoft Azure Virtual Machine Services offer an Infrastructure as a Service (IaaS) platform.
OpenText™ Extended ECM for SAP® Solutions 16.2 supports Azure Virtual Machines (IaaS).

The IaaS platform allows deploying various scenarios, including hybrid deployments with
connections to the on-premise customer network.

For questions about installation, sizing, storage, backup, monitoring, integration into on the premise
network, contact OpenText Professional Services.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

40
5 Requirements for SAP Applications
OpenText™ Extended ECM for SAP® Solutions is built on SAP standard technologies that are used in
most of the SAP applications. This chapter lists the required SAP standard technologies. This list is
useful for all who want to check whether an SAP application or a specific SAP transaction can be used
in combination with OpenText™ Extended ECM for SAP® Solutions.

5.1 List of Requirements

WSP = Relevant in the context of the business workspace concept
REF = Relevant in the context of the business reference concept
RM = Relevant in the context of the records management concept

• SAP Business Objects [WSP, REF, RM]: OpenText™ Extended ECM for SAP® Solutions relies strongly
on the concept of SAP business objects. For each entity, e.g. a material, a business object type
maintained in the SAP business object repository is required (transaction SWO1).
o Requirements for the business object type:
▪ Application runs on ABAP stack
▪ IFSAP interface implemented
▪ IFARCH21 interface implemented [RM only]
▪ Triggers SAP business events for creation and change
• The events need to be called after commit call
• Alternative: usage of change document (see transaction SCDO or table
TCDOBT)
▪ Reasonable key definition of the business object [WSP, REF]
• Data Access [WSP, REF, RM]: Document property providers and/or workspace property providers
have to be written for each business object type/document type as part of OpenText™ Extended
ECM for SAP® Solutions implementation. Document property providers and workspace property
providers need access to the data and the relationships of a business object. BAPIs for this data
access with good performance make the implementation easier.
o Alternative: Usage of ABAP SQL for access to the data
• User Interface Integration [WSP, REF]: The general way of UI integration into SAP transactions is
based on the GOS (Generic Object Services). Therefore, the GOS needs to be available in the UI of
the transaction and the business object needs to be published to the GOS.
o Exception: OpenText™ Extended ECM for SAP® Solutions 10.0 SP1 (and higher) provides
for CRM 7 an UI integration via CRM assignment blocks and a tab integration into the CRM
interaction center
o Exception: OpenText™ Extended ECM for SAP® Solutions 10.0.0 SP1 (and higher) provides
for SRM 7 an UI integration via WebDynPro components
o Alternative 1: OpenText™ Extended ECM for SAP® Solutions provides a Web UI and an
ABAP Web Dynpro control for a business workspace and even an ABAP API. Therefore,
specific UI integrations can be programmatically achieved in case the SAP transaction

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

41
 provides suitable enhancement capabilities or is a custom transaction that can be
modified.
o Alternative 2: OpenText™ Extended ECM for SAP® Solutions 16.2 provides a SAP Fiori app
for business workspaces. OpenText™ Archiving and Document Access for SAP® Solutions
16.2 provides a SAP Fiori app for business documents. Both apps can be programmatically
integrated into other SAP Fiori apps.
• Business Policies [WSP]: Business policies rely on SAP roles and SAP authorization objects.
Therefore, in order to use the business policy concept the SAP application has to use authorization
objects and the customer has to maintain SAP roles
• Search Help [WSP, REF]: Manual selection of business objects relies on SAP search helps. For these
scenarios it is necessary to define SAP search helps.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

42
6 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.

6.1 Installation Notes

Before installing, 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.

Installation Requirements

OpenText™ Extended ECM for SAP® Solutions - Installation and Upgrade Guide (ERLK160200-00-IGD-
EN-1) describes all installation steps.

Important
The Extended ECM Web Services ensure communication between SAP Server
and OpenText Content Server. Extended ECM Web Services support Tomcat
8.5 only.

BC Set Activation

OpenText™ Extended ECM for SAP® Solutions - Installation and Upgrade Guide (ERLK160200-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.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

43
 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 58 for SAP notes required
for special scenarios.

Table 18 - 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 passwords to
884077
capital letters. However, as of WAS 7.00 (see OSS
note 862989), the system can be set in a way that
it distinguishes between upper case and lower case
letters in a password. In this case, the log-on fails if
the original password contains at least one lower
case letter.

CALL_BROWSER does not launch a new window to

open the URL, even when the NEW_WINDOW
parameter is passed to the function module. Instead
an existing window is made use to open the URL.
1128338 However, as of OSS Note 1177636, the behavior
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 is required for the declare functionality of

1255948
the print lists.

This note is required to avoid known problems with

1122938
the web services.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

44
 SAP (OSS) Note Required for
1227752

This note enables the transmission of SOAP error

1424747
codes to identify problems.

Unexpected error message “No vendor specified”

1267258
when logon language is English.

1437593 The caught exception cx_ai_system_fault contains

only string SOAPCodeFaultError:1 and no other
(for SAP_BASIS 701 only) error text.

1713851 This note prevents a dump screen in the Business

Content Window when one tries to open a record,
(for SAP_BASIS 700 and gets a SAP Security dialog, and presses the “Deny”
higher) button.

SAP 7.00 - OSS note

822380.
The OSS notes have to be applied to avoid known
Installation information -
problems with the SAP Add-On Installation Tool
OSS note 1040369.
(SAINT)
SAPCAR tool
OSS note 212876

1382711
Required if using CRM Investigative Case
1379958
Management.
1613012

Several outbound web service proxies should be

2238264 triggered. In that process a program termination of
type STYLESHEET_GENERATION_FAILURE is raised.

Starting with version 16.2 Archiving and Document

Access for SAP Solutions and Extended ECM for SAP
1582867 Solutions use a new URL escaping, which is based on
SAP’s escape_xss_url as implemented in SAP note
1582870.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

45
 SAP (OSS) Note Required for

For SAP BASIS 731 and higher method

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 OTEXRL are installable on SAP systems with
enhancement packages for SAP NetWeaver 7.0. No additional ACP package is needed.

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

6.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”.

6.3 User License Type Assignment

OpenText™ Extended ECM for SAP® Solutions 16.2 has functionality to gather specific licensed user
data, like product-related license types and usage statistics, from both Content Server and SAP
server. On the SAP server, a license report consolidates this information.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

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

On Content Server, one uses the administration of users and groups to assign license types out of
the Extended ECM license list. Every licensed user must get a license type, either directly or by
belonging to a group that has a license type.

An example of type is “OpenText Extended ECM - Named User (ID = OXECMF)”. This type indicates
usage of OpenText Extended ECM.

Please read OpenText™ Extended ECM for SAP® Solutions - Customizing Guide (ERLK160200-00-
CGD-EN-1) for detailed information about OpenText License Report.

6.4 Language Installation

The master setup installs the English version of the software components that are part of
OpenText™ Extended ECM for SAP® Solutions 16.2. Other languages are available as language packs
or language module versions on OpenText My Support.

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

6.5 Upgrade notes

Before upgrading, please review these instructions.

Upgrade Planning
Open Text highly recommends that customers thoroughly plan each upgrade. Please get in contact
with an Open Text Professional Services or with SAP / Open Text 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.

Upgrade Path
Upgrading to OpenText™ Extended ECM for SAP® Solutions 16.2 implies upgrading the Content
Server to version 16.2, the ECMLink module to Connected Workspace 16.2, and OpenText™
Extended ECM for SAP® Solutions add-on packages to version 16.2.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

47
 Note
Upgrading to OpenText™ Extended ECM for SAP® Solutions 16.2 requires one of
the following start points:

• OpenText™ Extended ECM for SAP® Solutions 10.5 SP1 and Content
Server 10.5 SP1:

o Content Server 10.5 with ECMLink 10.5.1

o SAP server with ECMLink 10.5.1

• OpenText™ Extended ECM for SAP® Solutions 16 and Content Server

16:

o Content Server 16 with Connected Workspaces 16

o SAP server with OpenText™ Extended ECM for SAP® Solutions

16

Upgrading server components from OpenText™ Extended ECM for SAP® Solutions 10.5 SP1 or 16 to
OpenText™ Extended ECM for SAP® Solutions 16.2 requires the following steps:

• Content Server
1. Upgrade Directory Services to 16.2
2. Upgrade Archive Center to 16.2
3. Upgrade Content Server to 16,2, including Connected Workspaces 16.2 (new name
for ECMLink module) and all other modules, together with Enterprise Library Services
16.2 and Extended ECM Web Services 16.2 (both services require Tomcat 8.5 and Java
8)
• SAP server
1. Upgrade Extended ECM for SAP Solutions to add-on package 16.2

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

48
One may update either the Content Server or the SAP server first, and the other one in a second
maintenance window.

CAUTION
Extended ECM for SAP Solutions 16.2.4 (16 EP4) does require that Content Server,
Archive Center, and Enterprise Library be upgraded before SAP. See Section 7 for
details.

Note
When upgrading the Extended ECM for SAP Solutions SAP component from 10.5
SP1 to 16.2, one must recreate the SOA Manager entry for the Extended ECM SPI.
For more details, see OpenText™ Extended ECM for SAP® Solutions - Installation
and Upgrade Guide (ERLK160200-00-IGD-EN-1).

Note
To properly upgrade Enterprise Library Services from 10.2.2 to a higher version, you
need a tool that exports all existing document IDs from Content Server into two text
files. You also need a second tool to import these IDs on the Archive Server. For
more details, see OpenText™ Extended ECM for SAP® Solutions - Installation and
Upgrade Guide (ERLK160200-00-IGD-EN-1).

Please read OpenText™ Extended ECM for SAP® Solutions - Installation and Upgrade Guide
(ERLK160200-00-IGD-EN-1) for detailed information about the update procedure.

New SAP Authorization Objects

OTX/RM_USER is the standard role for Extended ECM users. As alternative to using the
/OTX/RM_USER role, SAP administrators can also grant authorizations as follows:

• In authorization object J_6NRL_WSC, set field /OTX/RMWAC to “00” for granting access to
business-workspace-related functionality.
• In authorization object J_6NRL_DOL, set field /OTX/RMDAC to “00” for granting access to
business-attachments-related functionality.
• In authorization object /OTX/RM, set field /OTX/RMACT to “00” for granting access to record-
management-related functionality.
• In authorization object S_GUI, set field ACTVT to “60” for granting access to drag-and-drop
functionality in Business Content Window.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

49
 • In authorization object J_6NRL_LFS, set field /OTX/RMLAC to “00” for granting access to the
Local File section in Business Content Window.

6.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™ Extended ECM for SAP® Solutions Vendor Keys

Please have a look in OpenText™ Extended ECM for SAP® Solutions - Installation and Upgrade Guide
(ERLK160200-00-IGD-EN-1) for more details about the different installation and upgrade packages.

The vendor keys are listed in a cross-version document located here on OpenText My Support.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

50
6.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™ Extended ECM 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.

Version 16.2 ACP files

You will find the most recent ACP files related to version 16.2 of OpenText™ Extended ECM for SAP®
Solutions from the patches area of OpenText™ Extended ECM for SAP® Solutions on OpenText My
Support (https://knowledge.opentext.com).

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

51
7 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™ Extended ECM 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.

7.1 Hotfixes
Hotfixes are small patches that address software issues. Typically, there is no new functionality in a
hotfix. Hotfixes can be cumulative.

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

Hotfix Name Additional Info Downloads

Extended ECM for SAP Solutions 16.2.5
(June 2018 Content Server module update)
https://knowledge.opentext.com/
Requires the following:
pat162000555 knowledge/llisapi.dll?func=ll&objI
• Content Server 16.2.5 d=74941024&objAction=browse
• Connected Workspaces 16.2.5
• Extended ECM Platform 16.2.5

AS 16.2.1 Update 16.2.1 for Archive Center 16.2 https://knowledge.opentext.com/

knowledge/llisapi.dll?func=ll&objI
d=69766394&objAction=browse

ELS-1620-002 Update 16.2.2 for Enterprise Library https://knowledge.opentext.com/

knowledge/llisapi.dll?func=ll&objI
d=72985382&objAction=browse

Quarterly Update History

The following table gives an overview of the quarterly update history.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

52
Table 20 - Quarterly Update History
Template Connected Extended ECM Extended ECM
Workspaces Workspaces Platform for SAP Solutions

Latest update to 16.2

16.2.5 2018-06 pat162000506 pat162000511 pat162000542 pat162000555

History

16.2.4 2018-03 pat162000341 pat162000334 pat162000367 pat162000363

16.2.3 2017-12 pat162000238 pat162000234 pat162000271 --

16.2.2 2017-09 pat162000150 pat162000149 pat162000213 pat162000155

pat162000119
16.2.1 2017-06 -- (superseded pat162000080 pat162000083
pat162000073)

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

Caution
OpenText™ Extended ECM for SAP® Solutions 16.2.2 introduces the
Extended ECM Platform license model. After upgrading to 16.2.2 or
higher, all business applications use the Extended ECM Platform
license model. Such an upgrade requires reviewing access privileges for
all business applications.

7.2 Updates
Updates consist of many fixes combined into a single patch. Typically, the minor version number of
the product will increase, for example from 2.0 to 2.1. An update may also include new features
proactively introduced into the product. In most cases, updates are cumulative.

ABAP Support Package installation

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

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

53
 Available ABAP Support Packages
The following table lists and describes the SAP (ABAP) support packages available for this release.
Table 21 - Available ABAP Support Packages
Support Package
Additional Info Downloads
Name

OTEXBAS_SP_162 Archiving and Document Access for SAP https://knowledge.opentext.c

0_700_01.SAR Solutions 16.2 SP1 (SP SAP add-on package om/knowledge/llisapi.dll?fun
for OTEXBAS) c=ll&objid=72201689&objacti
on=location
Requires the following:

• Extended ECM for SAP Solutions 16.2.4

• Update 16.2.1 for Archive Center 16.2
• Update 16.2.2 for Enterprise Library

OTEXRL_SP_1620 Extended ECM for SAP Solutions 16.2 SP1 (SP https://knowledge.opentext.c
_700_01.SAR SAP add-on package for OTEXRL) om/knowledge/llisapi.dll?fun
c=ll&objid=72193321&objacti
Requires the following:
on=location
• Extended ECM for SAP Solutions 16.2.4
• Update 16.2.1 for Archive Center 16.2
• Update 16.2.2 for Enterprise Library
• OTEXBAS_SP_1620_700_01.SAR

OTEXRLC_SP_162 Extended ECM for SAP Solutions 16.2 SP1 (SP https://knowledge.opentext.c
0_700_01.SAR SAP add-on package for SAP CRM) om/knowledge/llisapi.dll?fun
c=ll&objid=72193321&objacti
Requires the following:
on=location
• Extended ECM for SAP Solutions 16.2.4
• Update 16.2.1 for Archive Center 16.2
• Update 16.2.2 for Enterprise Library
• OTEXBAS_SP_1620_700_01.SAR
• OTEXRL_SP_1620_700_01.SAR

OTEXRLF_SP_162 Extended ECM for SAP Solutions 16.2 SP1 (SP https://knowledge.opentext.c
0_740_01.SAR SAP add-on package for SAP Fiori frontend) om/knowledge/llisapi.dll?fun
c=ll&objid=72193321&objacti
Requires the following:
on=location
• Extended ECM for SAP Solutions 16.2.4
• Update 16.2.1 for Archive Center 16.2

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

54
 • Update 16.2.2 for Enterprise Library
• OTEXBAS_SP_1620_700_01.SAR
• OTEXRL_SP_1620_700_01.SAR

Caution
OTEXBAS 1620_700 SP1 (Archiving and Document Access for SAP Solutions
16.2 SP1) requires SAP_BASIS 700 0018.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

55
8 Fixed Issues

This section provides information about further past issues that have been fixed in this release.
Table 22 - Fixed Issues

Issue Number Issue Description

Content Server smart UI is incompatible with CRM

SAP CRM fails to display any Content Server smart UI. The business workspace
integration can therefore only occur via classic UI.
Resolved! Content Server 16.2 enables integrating smart UI in CRM.

Content Server smart UI is incompatible with SAP portals, including SAP SRM
Portal

SAP portals, including SAP SRM Portal, fail to display any Content Server smart
UI. Content Server smart UI requires Internet Explorer (IE) 11 or higher.
However, SAP portals force IE to simulate older versions.

The business workspace integration in SAP portals can therefore only occur via
classic UI, unless SAP portals manage to operate IE in version 11 or higher.

Resolved! Content Server 16.2 enables integrating smart UI in SAP portals,

including SAP SRM Portal.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

56
 Extended ECM Connections – OpenText Directory Partition Field

For using synchronizing SAP roles to OTDS groups, enter the domain name in
the partition field.

For using synchronizing SAP roles to Content Server groups or business

policies, do as follows.

a) In case of a non-synchronized partition, enter the partition name in the

partition field.
b) In case of a synchronized partition, fill the partition field as follows:

“__NAME__” Resource Mapping* Partition field

SAPRM-10179
oTExternalID1 Leave empty

oTExternalID2 Domain name

oTExternalID3 Partition name

oTExternalID4 NetBIOS domain name

(*) Directory Services Integration Administration -> Configure Directory Services -> Resources ->
Properties (for Content Server) -> User Attributes Mappings -> OTDS attribute value for the
“__NAME__” resource attribute

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

57
9 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 23 - Known Issues

Issue
Issue Description
Number

Common Issues

Document Properties Synchronization (DPS)

DPS-558
DPS does not work properly with the Template Workspaces module. DPS fails to
work properly for documents created with the document template wizard.
Extended ECM Administration in SAP

Mixing of cryptic text elements in languages other than English

The Extended ECM administration pages in SAP (SPRO) may have empty or cryptic
text elements when the log-on language is not English. These pages have not
been localized. Unfortunately, even the original English text elements are
sometimes missing when the log-on language is not English. To avoid this
problem, SAP administrators should log on in English.

Content server domain not compatible with Extended ECM

Content Server 10.0.0 update 6 reintroduces Content Server domains. Such

domains are not compatible with OTDS and therefore not compatible with
Extended ECM.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

58
 Records Management for ArchiveLink Documents and Print Lists

Type restriction during re-assignment of ArchiveLink documents

An ArchiveLink document can be re-assigned to a different business object. This

can be necessary if a document e.g. an invoice is linked to a wrong finance
document. During a reassignment of a record to a different business object, the
metadata and the record management settings are recalculated and updated. All
the metadata and records management settings from the first business object are
lost.

Fixed in 16.2.4 (16 EP4)!

Type restriction and update behavior during multi-assignment of ArchiveLink

documents

An ArchiveLink document can be assigned to many business objects. During an

additional assignment of a document to another business object, the metadata
and the record management settings are recalculated and updated for the new
assignment. All the other metadata and records management settings from the
other business objects are lost.

Fixed in 16.2.4 (16 EP4)!

Update of Document category attributes on non-unique document name

configuration
SAPRM-687
If the document name within a document declaration is not configured to be
unique, the category attributes are only updated on the last declared document.

Declare Records into Workspace does not work if Workspace is a Case or a Sub-
SAPRM-1394 binder

SAPRM-1411 For Cases and Sub-Binders (Binders located under Binders) the Root folder option
“Workspace” cannot be used within the Enterprise Library Document Declaration
ELIB-7603
configuration.

SAPRM-2178 Record Name Uniqueness Issue

ELIB-8733 Upon document name collision, record declaration fails.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

59
 Document declaration raises an exception when the display name is provided in
an unknown or inactive Content Server language
SAPRM-4254
To declare documents, the SAP server can provide display names in several
ELIB-9689 languages. However, the Content Server raises an exception if a given language is
unknown or inactive.

RM Classification not supported on business workspace templates

Definition of RM classification and security clearance settings is not supported in

business workspace templates.

It is best practice to define RM classification and security clearance on the target

location with inheritance enabled.

Business Workspaces

Tooltip for business workspace icon is not the reference type

SAPRM-1102 In the list view, the tool tip for the business workspace icon is not the reference
type. In the widgets and the path trail the reference type is given.

Metadata synchronization does a category upgrade

SAPRM-1161 If the category within Enterprise Server is updated the metadata synchronization
does an automatic upgrade of the category.

Maintain Business Object Declaration (SPRO)

The value verification for Business Object Declaration is erroneous when one
SAPRM-1615
attempts to change several related fields at once. The workaround is to save after
changing each field.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

60
 Caching and re-using results of filtering

The results of filtering by policies are cached; the default time frame for reusing
the filter results is 100 seconds.
The following setting can be added to opentext.ini to change/deactivate the
caching:
[OTSAPXECM]
FilterNodesCallbackCache=10000

The digit specifies the time frame in milliseconds; the above example would set
the cache re-use time frame to 10 seconds. If you want to deactivate the cache,
set the value to 0.

Virtual folder incompatibility

SAPRM-3093 Neither OpenText Business Content nor the classic business workspace browser
can open virtual folders.

Workspace sidebar does not display Document Workflows initiated within bub
binders or sub cases

Any Document Workflow that was initiated from within a Sub Binder or Sub Case
SAPRM-3356
will appear in the Extended ECM Sidebar on the Sub Binder or Sub Case, if
configured to display, but it will not appear at any higher level Extended ECM
Sidebar for parent [Sub] Binders or [Sub] Cases.

Sub path for workspace target root location has limitations

ECMLink 10.0.2 introduces the possibility of adding a sub path to the target root
location for creating workspaces. However, cases and binders do not take this sub
SAPRM-3287 path into consideration.

Furthermore, it is always possible that a sub path element, specified as a

property, evaluates to an empty string at runtime. In such a case, the sub path is
contracted by omitting the empty sub path element.

Updating attributes with the Object Importer fails to update the Workspace
group mapping

When using the Object Importer to update attribute values that are used for the
Workspace group mapping, the permissions are not updated.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

61
 Composite business workspaces only support task lists (BUS1019) and
maintenance orders (BUS2007)

Composite business workspaces: Business workspaces may reside in other

business workspaces to reflect the corresponding SAP business object hierarchy.
This functionality is currently restricted to task lists (BUS1019) and maintenance
orders (BUS2007).

In Content Server, the manual creation of a composite business workspace

omits to create any child composite business workspaces

In Content Server, the manual creation of composite business workspace omits

any composite structure information. Only composite business workspaces
created from the SAP side can have a hierarchy of sub composite business
workspaces.

Business Content Window shows related business workspaces in its document

SAPRM-4357 pane

ELIB-9719 The Business Content Window shows related business workspaces in both its
container and document panes.

Business Content Window

SAPRM-6570 In SGOSATTR database table, the “Commit Required” field of the OTX_ATTACH
service must be unset, otherwise the Business Content Window might not open.

Content Server Smart UI does not support cases and binders

Content Server 16 does only support cases and binders in its Classic UI.

Shortcuts to a folder in Business Content Window

SAPRM-6498,
With 10.5 SP1 the browse action was disabled. Therefore, for a shortcut to a folder
SAPRM-8213
the double-click action was also disabled.

Folder Browse View embedded in Business Content Window fails to show inline
actions

When Business Content Window is set to use smart UI, the Folder Browse View
SAPRM-9744
takes charge of displaying business workspaces. However, due to an Internet
Explorer limitation, the Folder Browse View embedded in Business Content
Window fails to show inline actions.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

62
 Business References

Content Server workflow item attachment do not support business references

SAPRM-2274 Business references are not showing for workflow attachment in the initiated
workflow instance.

Business references associated with the template get lost when creating the
business workspace
SAPRM-2318
If a template has business references, any workspace created from this template
does not get these business references.

Business references Content Server link to display SAP business object

In Content Server, the business references property tab of a given document lists
all business objects that the document refers to. For each business object, there is
a display link to show the corresponding SAP display transaction. Such links do not
work properly for SRM Shopping Carts and SRM Business Partners.

Callback interface before adding and removing business objects

In Content Server, upon adding or removing business objects, optional execution

of additional Business Add-Ins (BAdIs) is not possible. A future release will address
this issue.

Policies

Role assignment overwrites existing policies which are added manually to user

Role assignment overwrites existing policies which are added manually to user.
SAPRM-1138
For any given user, SAP policy synchronization (via report or event) deletes all
prior policy assignment in Content Server.

Policy name is not updated if profile changes in SAP

SAPRM-969 If the name of a role/profile is changed in SAP the name of the policy is not
updated within the Enterprise Server. Authorization changes are updated.

Policies do not apply to the content of compound documents in Workspaces

A compound document is a special Content Server container that can hold several
sub documents. Policies cannot restrict the access to such sub documents.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

63
 Viewers

Imaging Viewers
Enhanced functionality of Imaging Viewers (Windows Viewer, Java Viewer, Web
Viewer) like notes and annotations are supported only in scenarios that call
directly the viewers, e.g. inside SAP UI Generic Object Services or Content Server
viewer integration. If the viewers are called indirectly via MIME type then the
enhanced functionality is not available.

FAX documents created through Content Server may not display correctly in the
External Viewers

SAPRM-2161 This is a limitation of how Content Server determines the MIME type of uploaded
content. Possible solution is to add the 'fax' extension as an alternative to the
'image/tiff' entry in the Content Server's config\mime.types

Brava Viewer document compare and merge functionality not available in

Business Content Window

The Business Content Window offers the option to view documents with the
Brava Viewer. However, comparing and merging document is not possible.

SCS-739 Brava Viewer does not support Remote Cache server.

Enterprise Connect

Displaying related workspace contents in Enterprise Connect will not respect

pagination

NGD-6471 This is a limitation of the Enterprise Connect module. Even if pagination is enabled
in Content Server, EC displays related child business workspaces in a non-
paginated single list.

SAP Configuration

Ping button in SOA Manager fails on SAP Release 702

SAPRM-3419 When using the SOA Manager transaction on SAP Release 702, the ping button to
test logical ports always reports connection failures.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

64
 On SAP Release 702, “Activate Business Function” has new confusing column

On SAP Release 702, the ECMLink SPRO activity “Activate Business Function”
(SFW5 transaction) has a new "Additional Prerequisite" column. Despite this new
information, the ECMLink switches do not have any dependencies.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

65
 Single Sign-on

Single Sign-on Issue with Content Server Popup Dialogs

Some Content Server pages offer buttons or links that trigger the popping up of a
Content Server dialog (e.g. a category selection dialog). In such cases, the SAPGUI
fails to transmit the Content Server authentication cookie (LLCookie) from the
caller page to the popup. As a result, the popup may display a logon dialog upon
the first call.

Content Server Search

Adding shortcuts using search is not available for case workspaces

SAPRM-5077 ECMLink 10.0.3 introduces the possibility to use search for adding shortcuts in
business workspaces. However, this feature is not available for case workspaces.

SAP CRM

CRM Lean Orders

SAPRM-6486
ECMLink does not support CRM Lean Orders (LORD) (ERP_H component).

SAP SRM

SAP SRM with SAP NetWeaver Business Client (NWBC) – Portal-independent

navigation frame

NWBC must be displayed in HTML standards mode. See SAP Note 1753544 for
more details.

Connected Workspace Transport for Content Server

Group IDs
SAPRM-6453
When importing workspace templates, group IDs are not adapted

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

66
 Related Workspaces Folder templates
SAPRM-6469
After importing related workspaces folder templates, users cannot edit references
whose workspace types are unknown.

Group replacement
SAPRM-6670
The Connected Workspaces transport mechanism does not take group
replacement configuration into consideration.

SAP Fiori

Fiori does not support drag & drop in Internet Explorer

For business documents, in Fiori, drag and drop does not work in Internet
Explorer, because Fiori Upload Control does not support it. If you use a different
browser instead, upload works.

Time-selection pop up fails to close after pressing browser back button

SAPRM-7475
In the document upload dialog, any active time-selection pop up fails to close
after pressing the browser back button.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

67
 Business Workspace integration in Business Center Fiori app (or in custom
Business Object Browsing Fiori app)

By default the Fiori Task App has a strict error handling (see Fiori Task App:
detailed error messages ) which may end up in an unrecoverable error.
In the case of the business workspace integration this is replaced by a relaxed
handling. This has the following effects:

• Advantage:
o Minor glitches in OpenText Content Server integration widget do
not lead to unrecoverable error messages in the leading Fiori app.
Instead the errors are written to the browser console.
Users can continue to use the integration.
SAPRM-8551
• Disadvantage:
o In the case of more major issues in OpenText Content Server
integration widget, uncaught errors may also have negative
effects on the leading application. In the long term the errors
which cause uncaught exceptions must be fixed.
• Other Side Effect:
o In the case a user switches fast between two instances of the Fiori
Task App / custom Fiori browsing app, which both integrate the
business workspace widget, it may happen, that the strict error
handling is still switched on and uncaught exceptions are raised.
In such cases the user can continue to work after a browser
refresh. In the long term any errors which cause uncaught
exceptions must be fixed.

Pipelines

AS-15476
Scan pipeline does not support barcode scenarios
SCAN-3283

SAP C4C

SAPRM-9315 Calling the C4C adapter within Content Server Process Scheduling results in
incorrect paging.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

68
 Themes/Appearances

Upgrading Extended ECM for SAP Solutions 10.5 SP1 to 16.2 disables all
Extended ECM themes.
SAPRM-9372
Calling the following URL fixes this issue:

<Content Server>?func=otsapxecm.Configure&module=otsapxecm

Fiori Business Object Browser

Compatibility with S/4HANA 1709

ABAP Add-Ons of Business Center / Fiori Business Object Browsing Enabler for
SAP Solutions 16.3 or higher can be installed on S/4HANA 1709.

S/4HANA

SAPRM- In S/4HANA, the Business Content Window does not show any notes for
11407 business partners (BUS1006)

S/4HANA integration restrictions

For the integration with S/4HANA, the following restrictions apply:
1. Business workspace creation > Search form to find a business object
• When searching for a business object, the input given for non-string fields
must complete. Partial input or wildcards do not yield a result.
• You must not use attributes with the same label in the search form, with
which you search business objects while creating a business workspace.
The Displayed Attributes list must not contain the same name twice. If
you cannot rename the label, you must remove the attribute.
2. S/4HANA adapter
The S/4HANA adapter supports those business objects, which have key fields
of type String.
3. Scheduled Processing
A Scheduled Processing job created for “Listen to S/4HANA Events” does not
consider the input given for the Business Object Type field. The job processes all
business objects found in the event queue and which are registered.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

69
 ILM

ELIB-10542 Disabled recycle bin doesn't purge all deleted documents

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

70
10 Troubleshooting
Troubleshooting describes some commonly encountered problems, with solutions or tips on how to
avoid them.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

71
Table 24 - Troubleshooting

Problem Cause Solution

Verify your Extended ECM

connection:
Is the Content Server
running?
Is the Content Server protocol
correct?
Is the Content Server
hostname correct?
Is the Content Server port
correct?
Is the Content Server path
correct?
Content Server HTML dialogs
do not display (for example, Is the Content Server
when pressing F4 to select a The single sign-on process hostname provided in a fully
Content Server system fails. qualified format?
category of a Content Server Verify your SAP HTTP server
folder). settings:
Has the HTTP server service
(/sap/public/myssocn
tl) been activated? (See
"Activate HTTP Service" IMG
task)
Have the SAP HTTP server
and the Content Server the
same second-level and top-
level domain name?
Verify that your Internet
Explorer settings allow
cookies.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

72
 Problem Cause Solution

Verify the SAP user has the

/OTX/RM_USER role.
Either the SAP user or the
A user cannot declare records corresponding Content Server Verify that the Content Server
or view record details. user does not have sufficient user has sufficient
permissions. permissions in the target
folder for the desired activity
(creating or viewing).

If SAP_BASIS is greater than

700, then:
1. Go to the
SOAMANAGER
transaction
2. For both ELIB and
ECMLink, increase
the value of the
A batch record or business "Maximum Wait for
workspace declaration ends WS Consumer" field
up with the following error of the "Transport
Settings" tab.
message: HTTP connection time-out
setting is insufficient Otherwise:
ICF Error when
receiving the 1. Go to the SM59
response: transaction
ICM_HTTP_TIMEOUT
2. For both the ELIB
and the ECMLink
HTTP connections, set
a timeout of 120000
(CAUTION: Timeouts
are always in
milliseconds even if
the GUI says they are
in seconds).

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

73
 Problem Cause Solution

A user cannot declare records

or view record details or
maintain Enterprise Library Verify that time settings of
document declarations. SAP server and Content
Content Server HTML dialogs Server are identical.
Time of SAP server and
do not display (for example, It is recommended to use a
Content Server different.
when pressing F4 to select a time server to keep time
Content Server system settings of SAP and Content
category of a Content Server Server identical.
folder).

Search the SAP logs for an

Enterprise Library error
message.
Verify that the given
document type has been
associated to a declaration
and this association has been
marked as automatic (IMG
Enterprise Library error, or activity Assignment of
When storing a business
configuration problem, or declaration ID to object type
document in a given SAP
missing workflow entry, or and doc. Type).
business object, a record is
SAP Workflow System not
not automatically declared. Verify that a workflow entry
running correctly.
has been configured (IMG
activities Maintain/Activate
Receiver Module Events).
Verify that the SAP Workflow
System is set up and running
correctly (SWU3 transaction).
See SAP documentation for
details.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

74
 Problem Cause Solution

- Your SAP user also exists in

Content Server
- Your SAPGUI is running on a
PC located in a domain whose
last 2 elements are identical
to the those of the Content
Server domain
- You are not using another
instance of IE logged in the
Content Server with another
user
- If your Content Server is
In SAP, you are performing an configured to work with
action that pops up a Content Windows authentication, SSO
Server pop-up dialog. SSO SSO mechanism fails is off in your Enterprise
fails and you see a Content Library Server Settings (see
Server logon dialog. SPRO)
- Your Content Server security
settings are not too strict
Give the following a try:
1. Close all IE instances
2. Close all SAPGUIs
3. Kill any remaining SAPGUI
processes
4. Open IE and delete all
cookies
5. Try again

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

75
 Problem Cause Solution

Wrong error message “No

vendor specified” shows up in
SAP GUI in various error
Make sure SAP Note 1267258
situations when logon SAP translation error
is applied.
language is English. The right
error message is found in SAP
log SLG1.

These pages haven’t been

The Extended ECM
localized. Unfortunately, even
administration pages in SAP
the original English text SAP administrators should log
(SPRO) have empty or cryptic
elements are sometimes on in English.
text elements when the log-
missing when the log-on
on language isn’t English.
language isn’t English.

On the development and test

servers:
In the SE03 transaction,
under “Set System Change
Transaction Option”, set both the
/OTX/RM_WSC_GEN fails to “OTEXRL” software
The /OTX/ namespace is not component and the “/OTX/”
create reports in the /OTX/
modifiable. namespace to “Modifiable”
namespace because the SAP
server doesn’t allow it. On the production servers:
Transport all reports
generated on the test server
by the /OTX/RM_WSC_GEN
transaction

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

76
 Problem Cause Solution

The following parameters

must be present in
opentext.ini:
[WebDAVExtraTypes]
848=202
Problems with WebDAV Configuration settings 854=0
[pstage]
AdditionalSupportedC
ontainers={848}
AdditionalSupportedV
olumes={849}

Import directory has over

Fails to install language pack. Read SAP Note 1416497
1000 documents.

Use the OTDS SAPSSOEXT

Authentication Handler
The OTDS SAP Authentication instead (configured with a
com.sap.security.api.ticket.Tic Handler isn’t compatible with PSE file – see OpenText™
ketException: Unsupported some codepages coming from Extended ECM for SAP®
codepage 4102 in ticket. SAP servers running on UNIX Solutions - Installation and
platforms. Upgrade Guide (ERLK160200-
00-IGD-EN-1) for more
details).

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

77
 Problem Cause Solution

While creating a Logical Port

the following error message is
displayed:
Error: HTTP: Error
Set the SSO profile
in interface for
management of HTTP parameters to the
destinations; Delete corresponding values (see
the flag for the OpenText™ Extended ECM for
"Send SAP Logon The SAP SSO profile SAP® Solutions - Installation
Ticket" checkbox parameters are not set as and Upgrade Guide
specified. (ERLK160200-00-IGD-EN-1)
or
for more details):
SRT Framework
login/accept_sso2_ticket
exception: HTTP: = 1
Error in interface login/create_sso2_ticket
for management of = 2
HTTP destinations;
Delete the flag for
the "Send SAP Logon
Ticket" checkbox

The context menu of both In the Content Server

documents and folders, in the Administration, under Server
classic business workspace Configuration, Configure
SAP GUI as well as in the new Content Server 10.0 update 6 Security Parameters, there is
OpenText Business Content, disables the document now a new Document
has no open command. opening function. Functions section with an
Furthermore, double clicking Open sub-section. The default
on a document or folder does value is Disabled. Set it to
not open it. Enabled.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

78
 Problem Cause Solution

The systems with kernel 740

and higher dont need
(lib)sapsecu.(dll|so) library,
but use always the
(lib)sapcrypto.(dll|so) library,
which is part of the kernel. It
fully replaces the SSF library
(lib)sapsecu.(dll|so), see note
1848999.
In case of standalone licence
check there was one issue
there the license check still
requires to load sapsecu
Problem: instead of sapcrypto. This is
During usage of saplikey or fixed with this note.
other command line tools The hardcoded default to
load the library for license The kernel patch will be
which maintain the SAP
check is set to available with patch level
license (e.g. BR*Tools for
mentioned in tab. "SP Patch
Oracle) you receive the error: (lib)sapsecu.(dll|so), but in Level.
Could not load SSF library 740 there is only a
(lib)sapcrypto.(dll|so) However if you get this error
libsapsecu.so.
available. in upgrade scenario, e.g. in
brbrackup, then you need an
update of the BR*Tools.
Workaround:
If you face this problem but
you are not able to download
the mentioned kernel- and
br- patches, you can simply
copy the
(lib)sapcrypto.(dll|so) to
(lib)sapsecu.(dll|so), because
both libraries have the same
licence check functions
inside.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

79
 Problem Cause Solution

After a Web Service upgrade,

execution of bulk document Some SAP versions seem to Recreate the corresponding
declaration (/OTX/RMMIG have issues with Web Service logical port.
transaction) ends up with a upgrades.
screen dump.

The assertion ticket cannot

be created if the SID and
client are not maintained in
Web services authentication RFC destinations of type H/G. Provide both SID and client in
fails with SAP_BASIS 701 on This results in logon errors. RFC destinations of type H/G
SP15. This issue occurs only in (ref.: SAP Note 1998001).
SAP_BASIS 701 on SP15.
Other releases and other SPs
are not affected.

In the Content Server

In CRM, SRM, and other Web
Administration, under Server
Dynpro integration, the
Configuration, click on
embedded Content Server
Configure Security
view fails to display a Content Server prevents
Parameters. Under Frame
business workspace. Instead, request handlers from being
Embedding, make sure that
the view shows an error embedded in external frames.
“Prevent request handlers
message stating that the
from being embedded in
content cannot be displayed
external frames” is
in a frame.
unchecked.

In Diagnostic Report, the In Content Server

OTDS REST test fails if the Administration, add the port
OTDS URL contains no port number (typically 80 or 443)
number. to the OTDS URL.

OpenText™ Extended ECM for SAP® Solutions 16.2 Release Notes

80
11 Contact information
OpenText Corporation
275 Frank Tompa Drive
Waterloo, Ontario
Canada, N2L 0A1

Support: https://support.opentext.com

OpenText My Support: https://knowledge.opentext.com

For more information, visit www.opentext.com

Copyright © 2017 Open Text SA and/or Open Text ULC. All Rights Reserved.
Open Text 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 and/or Open Text ULC or other respective owners.

81