open text archiving and document access for sap solutions...
TRANSCRIPT
Open Text Archiving and Document Access for SAP Solutions 9.8.0
SAP 9.8.0 Extension for SAP Archiving and Document Access 9.6.2 by Open Text
Release Notes 7/20/2011
2 | Open Text Archiv ing and Document Access for SAP Solut ions 9.8.0
Contents
Open Text Archiving and Document Access for SAP Solutions 9.8.0 .................... i
SAP 9.8.0 Extension for SAP Archiving and Document Access 9.6.2
by Open Text ................................................................................................................. i
Release Notes 7/06/2011 .............................................................................................. i
Contents ....................................................................................................................... 2
1 Introduction .................................................................................................... 4 1.1 Release Notes Revision History ...................................................................... 4
2 About Open Text Archiving and Document Access for SAP
Solutions 9.8.0 ............................................................................................................. 5 2.1 What is Open Text Archiving and Document Access for SAP
Solutions? ........................................................................................................ 5 2.2 New Features ................................................................................................... 5
2.2.1 Integration of Open Text ECMLink for SAP Solutions in
DocuLink .................................................................................................... 5 2.2.2 New DocuLink Web UI for SAP NetWeaver 7.0 systems ................... 6 2.2.3 Other new features ............................................................................. 6
2.3 Deprecated Features ....................................................................................... 6 2.3.1 Deprecated Features in Version 9.8.0 ................................................ 6
3 Packaging and Documentation .................................................................... 7 3.1 Packaging and Delivery Information ................................................................ 7
3.1.1 Open Text Archiving and Document Access for SAP
Solutions .................................................................................................... 7 3.1.2 SAP 9.8.0 Extension for SAP Archiving and Document
Access by Open Text ................................................................................. 8 3.2 Note on the End User License Agreement ...................................................... 9
3.2.1 Usage of DocuLink .............................................................................. 9 3.2.2 Usage of Searchable PDF DocTool .................................................... 9
3.3 Documentation overview ................................................................................ 10 3.4 Documentation Errata .................................................................................... 11
4 Supported Environments and Compatibility ............................................. 13 4.1 Supported SAP Software ............................................................................... 13
4.1.1 Supported SAP Business Suite Applications .................................... 14 4.1.2 Required SAP Support Packages and Patches ................................ 15 4.1.3 Supported ArchiveLink Protocols ...................................................... 16 4.1.4 Supported SAP GUIs ........................................................................ 16 4.1.5 Web Browsers for the Open Text DocuLink for SAP
Solutions Web User Interface .................................................................. 17 4.2 Compatibility Matrix ........................................................................................ 17 4.3 Language Support ......................................................................................... 17
3 | Open Text Archiv ing and Document Access for SAP Solut ions 9.8.0
5 Installation and Upgrade Notes .................................................................. 19 5.1 Installation Notes ........................................................................................... 19
5.1.1 Installation Requirements ................................................................. 19 5.1.2 BC Set Activation .............................................................................. 20 5.1.3 SAP Notes ......................................................................................... 20 5.1.4 Enhancement Packages ................................................................... 21 5.1.5 CRM Package ................................................................................... 21
5.2 Critical Hot Fixes or Support Packages ......................................................... 22 5.2.1 Support Package 1 ........................................................................... 22
5.3 Upgrade Notes ............................................................................................... 22 5.3.1 Upgrade planning .............................................................................. 23 5.3.2 Upgrade path .................................................................................... 23 5.3.3 Open Text vendor keys ..................................................................... 24 5.3.4 Further hints ...................................................................................... 25 5.3.5 Known issue with upgrade of OTEXERP and DocuLink
for LES 9.7.3 ............................................................................................ 25
6 Fixed Issues.................................................................................................. 27 6.1 Issues fixed with version 9.8.0 ....................................................................... 27 6.2 Issues fixed with Support Package 1 ............................................................. 27
7 Known Issues ............................................................................................... 29 7.1 General SAP restrictions ................................................................................ 29 7.2 Accessibility.................................................................................................... 30 7.3 DocuLink for SAP Solutions ........................................................................... 30
7.3.1 Table and Field Restrictions .............................................................. 32 7.3.2 Visualization ...................................................................................... 34 7.3.3 SAP GUI for HTML ........................................................................... 34 7.3.4 Livelink Business Application Integration (BAI) ............................... 35 7.3.5 Open Text Imaging: DesktopLink ...................................................... 37 7.3.6 Open Text Imaging Clients ................................................................ 37 7.3.7 Forms Management for ECR ............................................................ 38 7.3.8 Other Restrictions ............................................................................. 38
8 Contact Information ..................................................................................... 39
4 | Open Text Archiv ing and Document Access for SAP Solut ions 9.8.0
1 Introduction
These Release Notes describe updates and last minute changes in Open Text
Archiving and Document Access for SAP Solutions 9.8.0 respectively SAP 9.8.0
Extension for SAP Archiving and Document Access 9.6.2 by Open Text.
If you receive your software via SAP Marketplace then you need to download
SAP Archiving and Document Access by Open Text 9.6.2 and SAP 9.8.0
Extension for SAP Archiving and Document Access 9.6.2 by Open Text. (Please
see chapter 3 Packaging and Documentation for delivery details.)
Open Text recommends that you read these Release Notes in conjunction with
the documentation included with the software package. If any conflicts exist, the
Release Notes supersede the other documentation.
We also recommend that you check the Open Text Knowledge Center
(https://knowledge.opentext.com/) for any patches or documentation updates that
may have been posted after the initial release of Open Text Archiving and
Document Access for SAP Solutions 9.8.0.
1.1 Release Notes Revision History
If the release notes document is modified and republished, update the revision
history to indicate what changed from the previous version.
Topic Modifications Revision Number
All topics Initial Draft of RN ADA 9.8 RN-ADA0980-1
Updates Smaller updates RN-ADA0980-2
Updates SAP 9.8.0 Extension RN-ADA0980-3
5 | Open Text Archiv ing and Document Access for SAP Solut ions 9.8.0
2 About Open Text Archiving and Document Access for SAP Solutions 9.8.0
2.1 What is Open Text Archiving and Document Access for SAP Solutions?
Open Text Archiving and Document Access for SAP Solutions 9.8.0 is the
seamless integrated business document solution for SAP applications providing
imaging and high volume archiving capabilities for both incoming and outgoing
documents.
Open Text Archiving and Document Access for SAP Solutions 9.8.0 enables you
to integrate your documents into your SAP application business processes e.g.
incoming contracts, outgoing correspondence or SAP R/3 invoices. The Open
Text solution is seamlessly integrated with the SAP system: retrieval, access, and
document display all take place directly from within the SAP application. The
centralized storage and management of the documents simplifies and speeds up
retrieval. Fast access to the documents guarantees rapid processing of e.g.
inquiries and complaints.
No matter where your employees are currently working: anyone with the
appropriate authorization can access the required documents at any time,
worldwide.
2.2 New Features
The following new features were added in this release
2.2.1 Integration of Open Text ECMLink for SAP Solutions in
DocuLink
New type of workspace node in DocuLink to display Open Text Content
Server workspaces.
ArchiveLink document nodes in DocuLink may use Open Text Records
Management.
Note
This functionality requires licenses for Extended ECM for SAP Solutions.
6 | Open Text Archiv ing and Document Access for SAP Solut ions 9.8.0
2.2.2 New DocuLink Web UI for SAP NetWeaver 7.0 systems
New state of the art Web UI based on SAP‟s modern WebDynpro
technology.
2.2.3 Other new features
Additional application logging (SLG1) in DesktopLink
Support of Open Text Imaging Web Viewer and Java Viewer in SAPGUI
for HTML environments.
The Open Text license report was enhanced.
In DocuLink views the copy, move and delete behavior for ArchiveLink
Documents can be adjusted.
2.3 Deprecated Features
Include a list of features that were deprecated in this release and features that
are planned for deprecation in future release.
2.3.1 Deprecated Features in Version 9.8.0
The old Web UI based on BSP technology is deprecated in this release.
On SAP systems using NetWeaver 7.0 or above the usage of the new
Web UI based on the Web Dynpro framework is highly recommended.
On lower SAP releases the old Web UI functionality is expected to still
work, but maintenance of the old Web UI won't be continued for Version
9.8.0 .
Application logging (SLG1) won't be continued for the DocuLink User
Audit Trail. The DocuLink User Audit logging will still be available, though.
7 | Open Text Archiv ing and Document Access for SAP Solut ions 9.8.0
3 Packaging and Documentation
3.1 Packaging and Delivery Information
3.1.1 Open Text Archiving and Document Access for SAP
Solutions
This product is delivered via downloadable files:
Open Text Archiving and Document Access for SAP Solutions 9.8.0
Open Text Enterprise Library Services 10.1.0 (for the required
platform)optionally, if requested: database CD for the required platform
Open Text Imaging Enterprise Scan 9.7.1
Open Text Imaging Viewers and DesktopLink 9.7.0
Open Text Imaging Web Viewer 9.7.5
Open Text Imaging PDF Extensions 9.7.0
Open Text Searchable PDF Doctool 10.0.0
This product is delivered with the following Release Notes:
Open Text Archiving and Document Access for SAP Solutions 9.8.0
Open Text Enterprise Library Services 10.1.0
Open Text Imaging Enterprise Scan 9.7.1
Open Text Imaging Viewers and DesktopLink 9.7.0
Open Text Imaging Web Viewer 9.7.5
Open Text Imaging PDF Extensions 9.7.0
Open Text Searchable PDF Doctool 10.0.0
An ISO-Image-File (ot ada for sap 9.8.0.iso) can be downloaded from
https://knowledge.opentext.com/knowledge/llisapi.dll/properties/14162727
It contains Open Text Archiving and Document Access for SAP Solutions 9.8.0
with the following software components:
OTEXBAS : Open Text Archiving and Document Access for SAP Basis
(delivered in Add-On packages 0980_620, 0980_640, 0980_700 for the
SAP Basis releases 620, 640 and 700)
OTEXERP : Open Text Archiving and Document Access for SAP ERP
(delivered in Add-On packages 0980_470, 0980_500, 0980_600 for the
SAP ERP releases 4.7, 5.0 and 6.0)
OTEXCRM : Open Text Archiving and Document Access for SAP CRM
(delivered in Add-On package 0980_500 for the SAP CRM releases 5.0,
2007 (=6.0) and 7.0)
The ISO-Image (CD-ROM) contains also the documentation for Open Text
Archiving and Document Access for SAP Solutions 9.8.0.
8 | Open Text Archiv ing and Document Access for SAP Solut ions 9.8.0
For information and restrictions concerning the Open Text Enterprise Library
Services and the Open Text Imaging Clients, see the Open Text Enterprise
Library Services and Open Text Imaging Release Notes. These Release Notes
come with the installation package or you can find them in the KC
(https://knowledge.opentext.com).
3.1.2 SAP 9.8.0 Extension for SAP Archiving and Document
Access by Open Text
Note
This is just an extension to SAP Archiving and Document Access by Open Text 9.6.2. Therefore, you first need to install SAP Archiving and Document Access by Open Text 9.6.2.
This extension is delivered via downloadable files:
Open Text Archiving and Document Access for SAP Solutions 9.8.0
This extension is delivered with the following Release Notes:
Open Text Archiving and Document Access for SAP Solutions 9.8.0
This software can be downloaded from SAP Marketplace
SAP Extension for Archiving and Document Access by Open Text software
components can be downloaded from the SAP Marketplace. At the SAP
Marketplace the software is listed under SAP ARC&DOC ACCESS BY OPEN
TXT. You will find there:
SAP 9.8 ARC&DC ACC BY OT 9.6.2
It contains Open Text Archiving and Document Access for SAP Solutions 9.8.0
with the following software components:
OTEXBAS : Open Text Archiving and Document Access for SAP Basis
(delivered in Add-On packages 0980_620, 0980_640, 0980_700 for the
SAP Basis releases 620, 640 and 700)
OTEXERP : Open Text Archiving and Document Access for SAP ERP
(delivered in Add-On packages 0980_470, 0980_500, 0980_600 for the
SAP ERP releases 4.7, 5.0 and 6.0)
OTEXCRM : Open Text Archiving and Document Access for SAP CRM
(delivered in Add-On package 0980_500 for the SAP CRM releases 5.0,
2007 (=6.0) and 7.0)
The ISO-Image (CD-ROM) contains also the documentation for Open Text
Archiving and Document Access for SAP Solutions 9.8.0.
9 | Open Text Archiv ing and Document Access for SAP Solut ions 9.8.0
For information and restrictions concerning the Open Text Enterprise Library
Services and the Open Text Imaging Clients, see the Open Text Enterprise
Library Services and Open Text Imaging Release Notes. These Release Notes
come with the installation package or you can find them in the KC
(https://knowledge.opentext.com).
3.2 Note on the End User License Agreement
Open Text Archiving and Document Access for SAP Solutions is shipped with the
following licensed Open Text products
- Open Text Archiving for SAP Solutions
- Open Text Document Access for SAP Solutions
- Open Text Extended ECM for SAP Solutions
Respectively with the SAP Solution Extensions
- SAP Archiving by Open Text
- SAP Document Access by Open Text
3.2.1 Usage of DocuLink
Please note that the use of the functionality “DocuLink” (transaction J6NY) as
provided by the module Open Text DocuLink for SAP Solutions is restricted to
the following licensed products
- Open Text Document Access for SAP Solutions
- SAP Document Access by Open Text
- Open Text Extended ECM for SAP Solutions
- SAP Employee File Management by Open Text
- Open Text Employee Information Management
3.2.2 Usage of Searchable PDF DocTool
3.2.2.1 Open Text Archiving and Document Access for SAP Solutions
The Searchable PDF DocTool allows rendering scanned documents to
searchable PDF/A. This DocTool must only be used in scan pipelines together
with Enterprise Scan, means it is intended only for documents manually scanned
in with Enterprise Scan. Batch conversion of imported images is expressively not
considered a legitimate use of the software.
3.2.2.2 SAP 9.8.0 Extension for SAP Archiving and Document Access by Open
Text
The Searchable PDF DocTool is not included in this SAP 9.8.0 Extension.
10 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
3.3 Documentation overview
The following section gives you an overview of manuals that are available in the
respective languages.
The most recent documentation is available from the Open Text Knowledge
Center under:
https://knowledge.opentext.com/knowledge/llisapi.dll?func=ll&objId=15050695&o
bjAction=browse&viewType=1
Note
Please also check this location for the most recent language versions of the documentation.
Moreover, this section tells you where to find what manuals on the product CD-
ISO image:
The easiest way to find the required manual is to open the index.htm file in the
root (documentation) directory. Alternatively, you can look for the individual
manuals in the subdirectory\manual\<language>\<manual folder name>.
The following table describes which manuals of the SAP-related Open Text
Archiving and Document Access for SAP Solutions components are located on
the Open Text Archiving and Document Access for SAP Solutions 9.8.0 CD (in
the Documentation directory):
Open Text Archiving and Document Access for SAP Solutions
Document title <manual>
folder name
Available
languages
en
Open Text Archiving and Document Access for
SAP® Solutions - Installation and Upgrade
guide (ER-IGD)
ER-IGD-EN
er-igd x
Open Text Archiving and Document Access
SAP® Solutions - Scenario Guide (ER-CCS)
ER-CCS-EN
Not on CD, please
download from
Open Text
Knowledge Center
x
Open Text DocuLink for SAP Solutions
11 | Open Text Archiv ing and Document Access for SAP Solut ions 9.8.0
Document title <manual>
folder name
Available
languages
en
Open Text DocuLink for SAP® Solutions -
Customizing and Administration Guide (DC-
CGD)
DC-CGD-EN
dc-cgd x
Open Text DocuLink for SAP® Solutions -
User Guide (DC-UGD)
DC-UGD-EN
dc-ugd x
3.4 Documentation Errata
The following information in the Open Text Archiving and Document Access
SAP® Solutions - Scenario Guide (ER090800-CCS-EN) has to be changed:
Chapter 10.3 “Authorizations in SAP applications”. An additional
chapter 10.3.5 "Minimum Authorizations of DesktopLink RFC users" is
required:
If a user saves a document via DesktopLink client (Drag&Drop, or "Save to Livelink
DesktopLink"), the client program will open an RFC connection to the SAP system.
Minimum RFC related authorizations are required for the user login which is used for
the RFC connection (i.e. the user you are logging on with from the client)
Apart from the authorizations required to archive documents in SAP or to open and
see data in e.g. Open Text DocuLink the following minimum permissions are needed
regarding RFC connections:
Authorization object S_RFC ("Authorization Check for RFC Access")
"Activity" (ACTVT) : 16
"Name of RFC to be protected" (RFC_NAME) : J8A3, RFC1, RFCH, SYST
"Type of RFC object to be protected" (RFC_TYPE) : FUGR
The values above were sufficient for minimum access to DesktopLink functionality.
Please also refer to the description in
SAP OSS Note 460089 - Minimum authorization profile for external RFC programs
In addition to the values which are also recommended in the SAP note, the values
J8A3 and RFCH were necessary to make the DesktopLink solution work.
Chapter 16.1.2.2 "Creating multi-document types"
After the lines: ...
Doc.class
MULTI
...
12 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
the following information is required:
Depending on the SAP release it may be necessary to define the document class
MULTI in transaction oad2 despite warnings, that you should not define objects in the
SAP namespace.
13 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
4 Supported Environments and Compatibility
The Release Notes for Open Text Archiving and Document Access for SAP
Solutions 9.8.0 are updated continually. The latest version and further technical
information are available in the KC at https://knowledge.opentext.com.
Open Text Archiving and Document Access for SAP Solutions 9.8.0 is the
successor of Open Text Archiving and Document Access for SAP Solutions 9.6.2.
Note
Only the products and versions specified in the Release Notes are supported. Other versions have not been tested and are therefore not officially supported for this version. The Release Notes contain the definitive list of supported versions. Any other versions mentioned in the product documentation are superseded by the versions specified in the Release Notes.
4.1 Supported SAP Software
14 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
4.1.1 Supported SAP Business Suite Applications
The following table shows the SAP application versions and by which Open Text
software components they are supported.
Open Text
Software
Component
SAP Basis
6.20
SAP Basis
6.40
SAP AS
ABAP
7.1
SAP NetWeaver
7.0,
NetWeaver 7.0
EHP 1 - 2
Open Text
Archive
Full Support Full Support Supported
only for
data
archiving
Full Support
Open Text Basis
(OTEXBAS)
All SAP
systems
running on this
Basis version,
e.g. R/3
Enterprise 4.7
All SAP
systems
running on
this Basis
version, e.g.
ECC 5.0
- All SAP systems
running on this
Basis version, e.g.
ERP 6.0,
PLM 7.0,
CRM 5.0, 6.0, 7.0
SCM 5.0, 2007, 7.0
SRM 5.0, 6.0, 7.0
Open Text ERP
Package
(includes SAP
PLM features)
(OTEXERP)
Enterprise (4.7) ECC 5.0,
ERP 2004
- ECC 6.0,
ERP 6.0,
ERP 6.0 EHP 1 - 5
Open Text CRM
Package
(OTEXCRM)
- - - CRM 5.0,
CRM 6.0 (2007),
CRM 7.0
Open Text
DocuLink Web
User Interface
(included in
OTEXBAS)
- - - Supported
Open Text Archiving and Document Access for SAP Solutions 9.8.0 supports the
KPro (Knowledge Provider) infrastructure. The underlying Open Text Archiving
and Storage Service respectively Open Text Archive can be used to store KPro /
SAP DMS documents and/or can be used as a content cache server.
15 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
4.1.2 Required SAP Support Packages and Patches
SAP
Software
Component
Version SPAM
Level
Minimum
Support
Package
Stack
Comments
SAP Basis /
NetWeaver
6.20
(= R/3 4.7x110)
35 (63) Patch SAPKB62063
6.40
(= NetWeaver 04)
35 19 SAPKB64019
7.0 36 16 SAPKB70016
7.0 EHP 1 - 2 36 Any
SAP ERP Enterprise 4.7 Any Any depends on
requirements for SAP
Basis 6.20
ERP Central
Component (ECC)
5.0
Any Any depends on
requirements for SAP
Basis 6.40
ERP 6.0 Any Any depends on
requirements for SAP
Basis 7.0
ERP 6.0 EHP 1 – 5 Any Any depends on
requirements for SAP
Basis 7.0
SAP CRM CRM 5.0 31 Any depends on
requirements for SAP
Basis 7.0
CRM 6.0 31 Any depends on
requirements for SAP
Basis 7.0
CRM 7.0 31 Any depends on
requirements for SAP
Basis 7.0
Software
Component
Version Minimum Patch Level
SAP GUI for 6.20 45
16 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
Windows 7.10 14
7.20 Any
Tp, R3trans 6.40 145
Unicode-compatible
4.1.3 Supported ArchiveLink Protocols
The ArchiveLink protocols 4.5 and 4.6 are supported. Open Text provides for
ArchiveLink following communication protocols: IX_OLEU1, IX_OLEU2,
IX_HTTP2, IX_HTTP3. For usage of ArchiveLink protocol 4.6 (Cache Server
Extension), copy one of the provided communication protocols and set the
version to 0046 in SAP.
4.1.4 Supported SAP GUIs
The supported SAP GUIs depend only on the SAP Basis/NetWeaver version.
SAP
Software
Component
Version SAP GUI
for
Windows
SAP
GUI for
HTML
SAP
NetWeaver
Business
Client
SAP GUI
for Java
SAP Basis/
NetWeaver
6.20
(= R/3 4.7x110)
6.20, 7.10,
7.20
6.20,
6.40
- -
6.40
(= NetWeaver 04)
7.10, 7.20 6.40 - 6.40 for
MAC OS X
v10.4
7.0 7.10, 7.20 7.00 NWBC v3.0
Stand-Alone
6.40 for
MAC OS X
v10.4
7.0 EHP1 - 2 7.10, 7.20 7.00 NWBC v3.0 6.40 for
MAC OS X
v10.4
17 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
Regarding the use of SAP NetWeaver Business Client (NWBC) please read SAP
OSS Note 1029940 – NetWeaver Business Client requirements and
restrictions and related notes. Depending on the specific scenario how SAP
NWBC is used (SAP GUI or SAP GUI for HTML) please also note the
requirements or restrictions of OpenText Archiving and Document Access for
SAP Solutions 9.8.0 as mentioned in its documentation or in these release
notes.
4.1.5 Web Browsers for the Open Text DocuLink for SAP Solutions
Web User Interface
The new Open Text DocuLink for SAP Solutions Web User Interface as delivered
with this Version 9.8.0 is based on Web Dynpro ABAP. Therefore the same
limitations are valid as for Web Dynpro ABAP. As a minimum Microsoft Internet
Explorer 7.0 is supported. Please see SAP/OSS note 1098009 for more details,
especially regarding the usage of MS IE 8.0 or Firefox 3.0.
4.2 Compatibility Matrix
For information on supported Open Text product versions , see the Open Text
Compatibility Matrix in the KC.
You may find the compatibility matrix for ECM Suite for SAP® here .
If this link is not working please go to the Product Compatibility Matrix overview
page and navigate to ECM Suite for SAP®.
For information and restrictions concerning other Open Text products, see the
corresponding Release Notes in the KC.
4.3 Language Support
The following section gives you an overview of the GUIs and manuals available
for Open Text Archiving and Document Access for SAP Solutions 9.8.0 in the
respective languages.
Component Name Available Languages1 Installation
EN DE FR ES JA PT RU Type
Open Text Archiving and
Document Access for SAP
Solutions 9.8.0
x x x x x x x Language
Pack1
ECMLink for SAP Solution –
Administration, Customizing
and Batch declaration
x x x x x x Language
Pack1
18 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
Component Name Available Languages1 Installation
EN DE FR ES JA PT RU Type
Notes:
1Default UI language for the components is English; translations to other languages will be
available as language packs or language module versions on the Open Text Knowledge
Center and via SAP market place.
19 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
5 Installation and Upgrade Notes
5.1 Installation Notes
5.1.1 Installation Requirements
The SAP-specific installation of the Open Text Archiving and Document Access
for SAP Solutions 9.8.0 components is described in detail in the Open Text
Archiving and Document Access for SAP® Solutions - Installation and Upgrade
guide (ER-IGD), which can be found in the KC. Furthermore, the client installation
from the Open Text Imaging CD1 is necessary for the additional clients.
Also consider the software requirements mentioned in "
1 May be an ISO-Image or ZIP-Package instead as well.
20 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
Supported SAP " on page 14.
Caution
Please make sure BEFORE installation that in table TAORA and IAORA are entries maintained for TABART „USER‟ and „USER1‟ which link to a valid TABSPACE.
Table TAORA
TABART USER / USER1
Table IAORA
TABART USER / USER1
5.1.2 BC Set Activation
The Open Text Archiving and Document Access for SAP® Solutions - Installation
and Upgrade guide (ER-IGD) Version 9.8.0 lists SAP notes which have to be
applied to avoid issues with the activation of Business Configuration (BC) sets. If
you still experience errors when activating BC sets, even if you did as described,
customizing transports are available in the KC (https://knowledge.opentext.com)
which correlate to the settings activated with the BC sets.
5.1.3 SAP Notes
Some SAP (OSS) notes are required to avoid known problems with the SAP
system. In addition to those notes listed below, also refer to “Known Issues” on
page 29 for SAP notes required for special scenarios.
OSS Note Required for
110910 Language-dependent texts in the GUI
Some language-dependent texts may not be displayed
correctly in the GUI. Reference 144437
21 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
OSS Note Required for
207196 Missing sample project data
Despite a correct transport of the sample data and correct
authorizations, some sample project data may not be
displayed.
884077 Logon error from external systems to WAS 7.00 systems
The external candidate's password contains at least one
lower case letter. In accordance with the rules, which were
valid up to and including WAS 6.40, the registration
application changes the passwords to capital letters.
However, as of WAS 7.00 (see OSS note 862989), the
system can be set in a way that it distinguishes between
upper case and lower case letters in a password. In this
case, the log-on fails if the original password contains at
least one lower case letter.
1128338 CALL_BROWSER does not launch a new window to open
the URL, even when the NEW_WINDOW parameter is
passed to the function module. Instead an existing window
is made use to open the URL. However, as of OSS Note
1177636, the behaviour of CALL_BROWSER is changed
to also allow opeining 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.
5.1.4 Enhancement Packages
The Add-On packages for software component OTEXBAS are installable on SAP
systems with enhancement packages for SAP Netweaver 7.0. No additional ACP
package is needed.
The Add-On packages for software component OTEXERP are installable on SAP
systems with enhancement packages for SAP ERP 6.0. No additional ACP
package is needed.
5.1.5 CRM Package
Starting with release 9.8.0 only one (optional) OTEXCRM Add-On package is
delivered which may be installed on SAP CRM 5.0, SAP CRM 2007 or SAP CRM
7.0. special care has to be taken during a system upgrade. Please refer to the
details given in the Open Text Archiving and Document Access for SAP®
Solutions - Installation and Upgrade guide (ER-IGD).
22 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
5.2 Critical Hot Fixes or Support Packages
5.2.1 Support Package 1
This package can be downloaded from the Open Text Knowledge Center. The
package consist of the Support Package 1 of Add-On OTEXBAS.
System Requirements
The respective OTEXBAS Add-On of version 9.8.0 was installed.
SP1 for Basis Release 6.20: the same support packages are required as for
installation Add-On
SP1 for Basis Release 6.40: the same support packages are required as for
installation Add-On
SP1 for Basis Release 7.00: the same support packages are required as for
installation Add-On
Please read the text file delivered together with the support package files for
more details. Furthermore chapter "6.2 Issues fixed with Support Package 1"
shows an overview of fixed issues.
5.3 Upgrade Notes
In addition to the description given in the Open Text Archiving and Document
Access for SAP® Solutions - Installation and Upgrade guide (ER-IGD) please
read these information regarding Upgrades.
Warning
If you import an upgrade into an SAP system with Open Text Archiving and Document Access for SAP Solutions 9.8.0 and the data of the respective upgrade packages is not read (upgrade phase IS_SELECT), the Open Text Archiving and Document Access for SAP Solutions 9.8.0 add-on (i.e. OTEXBAS, OTEXERP, OTEXCRM) will no longer work after the upgrade procedure. Since the status of the system is then inconsistent, Open Text can no longer accept any liability. Please note, that only in cases as listed in Table 7-3 of the Open Text Archiving and Document Access for SAP® Solutions - Installation and Upgrade guide (ER-IGD) Version 9.8.0, the existing Add-Ons may be kept ("KEEP" in upgrade phase IS_SELECT).
Caution
User exits Due to the support of Unicode systems, DocuLink was modified significantly. Therefore, user exits from DocuLink versions = 2.6 are no longer supported. Projects using such user exits must be revised.
23 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
Furthermore user exits from DocuLink versions > 2.6 may have been modified; projects using such user exits must be adapted to the new interfaces. Be aware that, as a rule, user exits are generally not released for implementation in projects created by customers or partners! Note for Open Text consultants implementing projects: See the KC entry on user exits in DocuLink 9.6.0 (https://knowledge.opentext.com).
Patch dependencies when upgrading When upgrading from versions lower than Livelink® ECM Suite for SAP® Solutions 9.6.0 please avoid to install patch SS096-001. Or when upgrading from versions lower than Livelink® ECM Suite for SAP® Solutions 9.6.0 and if patch SS096-001 was also installed on an SAP Basis Release 6.40 or 7.00, then patch SS096-008 must also be applied before upgrading to version 9.6.1 or higher. Otherwise the add-on installation tool SAINT will not carry out the installation due to problems with the version numbers of the OTEXBAS/OTEXERP component.
5.3.1 Upgrade planning
Open Text highly recommends that customers thoroughly plan each upgrade on
their SAP systems:
Please get in contact with an Open Text consultant or with SAP/Open
Text Support when considering to upgrade.
Before executing an upgrade on a productive system please consider to
do the same upgrade on a dedicated test and/or quality assurance
system. It is also highly recommended to do a database backup before
the upgrade.
If an SAP release upgrade or an update with enhancement packages is
planned and if Open Text Add-on packages are already installed on the
source release, please check in the Open Text Archiving and Document
Access for SAP® Solutions - Installation and Upgrade guide (ER-IGD)
Version 9.8.0 whether dedicated exchange upgrade packages exist, or if
a so called "KEEP" with vendor keys has to be done to preserve the
functionality.
5.3.2 Upgrade path
Customers using versions prior to 9.6.0 must first upgrade to Livelink® ECM –
Suite for SAP® Solutions 9.6.0 using a product CD or patches from the KC. The
next step is then the upgrade to the 9.6.1 version and then to Open Text
Archiving and Document Access for SAP® Solutions 9.6.2 and then to Version
9.8.0 with upgrade packages. When upgrading Open Text Add-Ons from 9.6.1 to
24 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
9.6.2 and then to 9.8.0 the support packages and hot fixes of 9.6.1 and 9.6.2
don't need to be applied. Version 9.8.0 includes all bug fixes of support package
2 of version 9.6.2.
5.3.3 Open Text vendor keys
When to use exchange packages ?
You already have installed Add-On packages OTEXBAS, OTEXERP or
OTEXCRM of version 9.8.0 on an SAP System with SAP Basis 620 or 640.
And you have to do a switch upgrade to an SAP System with NW 7.0 or NW 7.0
EhPx (e.g. Upgrade to ECC 6.0 or to ECC 6.0 EhP 4, etc.). Then in the upgrade
phase IS_SELECT please choose the Add-On exchange packages.
When to use vendor keys ?
You already have installed Add-On packages OTEXBAS, OTEXERP or
OTEXCRM of version 9.8.0 on an SAP System with SAP Netweaver 7.0 or SAP
Netweaver 7.0 EhPx. I.e. OTEXBAS 0980_700, OTEXERP 0980_600 or
OTEXCRM 0980_500 are already installed. Furthermore you have to upgrade to
a new SAP Release which still is based on SAP NW 7.0 or NW 7.0 EhPx (e.g.
NW 7.0 EhP 1). Then the Add-on exchange package cannot be used. Instead in
the upgrade phase IS_SELECT please choose a "KEEP" upgrade. In this case
the upgrade tool asks you for a vendor key.
Please have a look in the Open Text Archiving and Document Access for SAP®
Solutions - Installation and Upgrade guide (ER-IGD) Version 9.8.0 for more
details about the different installation and upgrade packages.
Vendor key list
Regarding the vendor keys SAP indicates that installations and upgrades are
done with different tools, therefore different keys are required. The list below
contains the possible keys for every target release, depdending on upgrade or
EhP installation process. For 701 there are 2 possible keys depending on the
source release. SAP recommends to simply try both of them. Furthermore SAP
recommends to use the latest versions of SAPUP or SAPehpi , which can be
downloaded from the SAP Service Marketplace.
Open Text Vendor Keys
SW Component Action NW Target Key Number
OTEXBAS Upgrade 701 1905323
OTEXBAS EHP install 701 2121071
701 1848589
OTEXBAS Upgrade 702 2412412
25 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
SW Component Action NW Target Key Number
OTEXBAS EHP install 702 1445805
OTEXERP Upgrade 701 3692324
OTEXERP EHP install 701
701
1583814
1101221
OTEXERP Upgrade 702 2851239
OTEXERP EHP install 702 1273721
OTEXCRM Upgrade 700 1934125
OTEXCRM Upgrade 701 2988495
OTEXCRM EHP install 701
701
1699730
807655
OTEXCRM Upgrade 702 2862981
OTEXCRM EHP install 702 1411921
Please get in contact with Open Text support if a vendor key is not working or
missing.
5.3.4 Further hints
"Deleted Records" table
When upgrading from DocuLink version <= 6.0 or when upgrading from non-
unicode to unicode releases:
Consider to recover and/or erase deleted records table entries before upgrading
from non-unicode to unicode. (See "Maintenance of deleted records" in
transaction J6NA table /IXOS/DC_TBRB) This may only be interesting, if
customers like to keep this "recycle bin" data.
5.3.5 Known issue with upgrade of OTEXERP and DocuLink for
LES 9.7.3
Symptom: You are not able to upgrade software component OTEXERP to
version 9.8.0 with the help of the Delta Upgrade package because of an
unresolved conflict with DocuLink for LES 9.7.3 package OTEXDESE.
Prerequisite: On your SAP System you already had installed packages
OTEXBAS and OTEXERP of version 9.6.2. You also had installed packages
26 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
OTEXDESB and OTEXDESE of DocuLink for LES 9.7.3. Now you want to
upgrade your packages OTEXBAS and OTEXERP to 9.8.0.
Reason: The upgrade package (AOU) of OTEXERP 9.8.0 doesn't replace the
full piecelist of OTEXERP 9.6.2. Therefore a conflict between OTEXERP 9.8.0
and OTEXDESE 9.7.3 is evaluated by the system during the evaluation which
actually is not existing anymore.
Solution: Cleanly roll back this attempt within transaction SAINT. Leave this
transaction. Instead start the transaction SAINT again but now use the installation
package for software component OTEXERP 9.8.0 instead, i.e. SAPK-
103COINOTEXERP, SAPK-203COINOTEXERP or SAPK-303COINOTEXERP
depending on your SAP ERP target release.
27 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
6 Fixed Issues
6.1 Issues fixed with version 9.8.0
Open Text Archiving and Document Access for SAP Solutions 9.8.0 includes all
bug fixes of support packages 1 and 2 of previous version 9.6.2.
In addition to that the following issues have been solved as well.
Umlaute im Titel des Web Viewers sind falsch
Reference LLSAPS-2047 Umlauts in the title of the Web viewer were not displayed
correctly
/IXOS/DC_A_PROTOCOL_ENTRIES doesn´t work for entry "A" Archive
Documents (Scan)
Reference LLSAPS-2255 The user audit trail for entry type "A" , i.e. archiving
documents via scan generates an entry, but no record details were generated.
Content of table /IXOS/DC_TAECR is not transportable, due to table
settings
Reference LLSAPS-1784 Due to wrong table settings the customizing ifor the ECR
mapping for DocuLink could not be exported via transports.
AUTH_CHECK UserExit wird für offline-Daten (Datenarchivierung) nicht
aufgerufen
Reference LLSAPS-2057 Due to this issue consultants could not do implementations
in customer specific DocuLink projects with User-Exit AUTH_CHECK in the case
of displaying "offline" records, i.e. records archived with data archiving.
6.2 Issues fixed with Support Package 1
The support package 1 (SP1) of Add-On OTEXBAS 9.8 contains several bug
fixes. This chapter shows an overview of some of those topics.
Solution Framework
This support package contains several bug fixes within the solution framwork
which are required by OpenText Employee File Management (EFM).
DocuLink
Several issues were fixed, especially the following
28 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
Reference LLSAPS-2308 DocuLink called by GOS forward error message instead of
output of RFC dump
Reference LLSAPS-2346 DocuLink J6NA: Delete generated reports more robust
Reference LLSAPS-2309 When physical delete is set for tree, then ArchiveLink
documents are now deleted, if they are records and if records management
allows to do so.
Reference LLSAPS-2373, Reference LLSAPS-2374 File upload to ArchiveLink documents
in SAP GUI : document types related to generic document class '*' are offered by
default. The stored document class in ArchiveLink is then derived from the file
extension.
Reference LLSAPS-2387 DocuLink Workspace: Remove @W_LENGTH from list of
available internal selection fields of "W" nodes due to change in ECMLink API (as
delivered in support package 1 of Extended ECM Add-On OTEXRL 9.8)
DocuLink Web
Some minor bug fixes were done. Especially topics related to OpenText
Employee File Management (EFM):
Reference LLSAPS-2340, Reference LLSAPS-2341 Fixes of issues related to thumbnail
view in SAP GUI (e.g. display of documents of document class 'PDF_SCAN')
Rendition Management
Reference LLSAPS-2327 Enable SSL/HTTPS communication between SAP and OT
rendition server
DesktopLink
A few minor bug fixes were done.
Forms Management
Some bug fixes, particularly:
Reference LLSAPS-2326 Fix RFC dump issue with print in ERP 6.0
29 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
7 Known Issues
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 (Reference
139941, for example). This number refers to an internal information system and allows Open Text to provide you with even faster high quality support.
Entries with an icon refer to an SAP (OSS) note.
7.1 General SAP restrictions
Importing archive info structures from SAP R/3 4.6 to version 4.7
Due to an SAP transport system error, the table contents of archive info
structures are not imported correctly. Applying the SAP note 584452 will solve
this problem.
Displaying Content Management documents in preview mode
Some documents cannot be displayed in preview mode. This is due to the fact
that SAP defines the EAIWEB.WEBVIEWER2D as the default viewer for some
document classes, however, this viewer is not installed during a pure SAP GUI
installation.
You can solve this problem either by performing the complete GUI installation on
the front-end computer, or by specifying another, existing viewer application on
the front-end computer to be used for these document classes. The assignment
of applications to document classes can be defined using the OAM1 transaction.
See the SAP note 646328 for more details.
Login problems with Java Connector (JCo) version 2.1.5 on SAP ERP
When using the Java Connector (JCo) version 2.1.5 on SAP ERP, login problems
may occur. In this case, enter the password for the user connecting to the SAP
system in capital letters.
See the SAP note 792850 for more details.
30 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
7.2 Accessibility
Displaying a Printlist from the Archive System
When a user needs full accessible mode within a printlists, Open Text
recommends to use document display within the SAP GUI using the SAP
Document Viewer.
7.3 DocuLink for SAP Solutions
Warning
User exits
As a rule, user exits are generally not released for implementation in projects created by customers or partners. Ask your Open Text consultant for more information.
Transporting projects
When you transport DocuLink projects into an SAP system where DocuLink is
already installed, an internal error may occur when executing a DocuLink
transaction, due to caching problems. In this case, try exiting and restarting the
transaction. If it fails again, execute /$sync.
Deleting SAP print lists
It is not possible to delete SAP print lists in DocuLink, as DocuLink does not allow
SAP tables to be edited (in this case, TOADL).
Unexpected result when hitlist flag is applied to the root node
There is an unexpected behavior when a hitlist is invoked from a first-level node
under the root node; this only happens when the hitlist flag is applied to the root
node. After entering an invalid selection, the resulting hitlist is empty (standard
behavior). If, however, you now go back and enter a valid selection, the resulting
hitlist is still empty. You have to click (Refresh) to get the correct results.
Permanent workaround:
1. Assign the required selection fields to the root node.
2. Create an additional static node under the root node and select under
Selection type option 2 or 3.
3. Remove the hitlist flag from the root node and apply it to the new static
node.
31 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
4. Apply the option Open nodes automatically to the new static node.
5. Move the respective first-level node from the root node one level below
under the new static node.
Default archiving scenario in the Create screen
When you create a new record with a document at a node where several
document nodes are assigned, the default archiving scenario defined for the
corresponding attribute object is ignored in the Create screen. Therefore, the
popup asking you which archiving scenario to use always appears.
DocuLink Web User Interface
Please note, that starting with Version 9.8.0 the DocuLink Web User Interface is
implemented based on the ABAP Web Dynpro Framework. Therefore many
restrictions of the former BSP based Web UI don't apply. But still not all features
of DocuLink are supported in this visualization. For an overview of supported
functionality in the projects themselves, see the Open Text DocuLink for SAP®
Solutions - User Guide (DC-UGD). The following features are not supported for
DocuLink projects that are accessed using the DocuLink Web User Interface:
• RFC communication to the archive
• Scanning via front-end and file upload via DesktopLink
• Assigning files via barcode
Output masks for dynamic nodes
If the values for a field are restricted by input in a selection screen, the restriction
may be ignored by a dynamic node where an output mask is defined. In this
case, the restriction defined by the output mask overrules the one in the selection
screen.
Reference 142195
Simultaneous access to CM document properties
When two or more users access the CM document properties dialog for the same
document at the same time, only the first user can switch to edit mode. When
another user tries to switch to edit mode for the dialog as well, an error occurs
and an empty popup titled “List of unprocessed documents” is displayed. To avoid
this, implement SAP note 761469.
Reference 144866
32 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
Logging for CM documents in hitlists
When you perform actions on CM documents that are displayed in a hitlist, no
logging information is stored for these actions.
Reference 204528
Displaying documents from a logical system
The user that is used to access the logical system must be of the user type
Dialog. Users of type Communication cannot display documents and input
screens, although they have permission to retrieve data.
Table maintenance for DocuLink sample project $EX_FI2
The maintenance data of the /IXOS/DC_EX_GJAH table is not populated
automatically. Therefore this table has to be maintained manually with year
numbers in field GJAHR and the client number in field MANDT. The maintenance
is required to make the DocuLink sample project $EX_FI or its copies work
properly. Otherwise the view 001 of the sample project does not show any BKPF
data because of the value restriction GJAHR at node C_GJAHR, which in turn
depends on the data specified in the /IXOS/DC_EX_GJAH.
7.3.1 Table and Field Restrictions
Storing documents
Documents should be stored using ArchiveLink link tables (TOA0x). It is not
recommended to use the same table for archive ID, document ID and attributes.
Automatic filling of fields and tables containing archive ID and document ID
Tables containing archive ID and document ID must not have a key field filled
automatically (for example by means of a number range) if they are used for
manual archiving (not applicable to COLD).
Automatic filling of fields and Doctool R3Insert
If automatic filling of fields via doctool R3Insert is used, an RFC destination <SY-
HOST>_<SY-MANDT> is created with user SAPCPIC and password ADMIN. The
customer can create this RFC destination. The user can be edited.
Table size
Only tables with a maximum width of 4,160 bytes are supported for hitlists.
2 This an optional example DocuLink project which may be downloaded from the
KC (https://knowledge.opentext.com).
33 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
Maximum width of fields in the database
If you create or change records in the database, the maximum width of fields in
the view is 132 characters.
Maximum length of node type texts
Only node type texts with a maximum length of 500 characters can be displayed
correctly.
Check tables
A maximum of 4 fields may be linked via check tables to execute a foreign key
check against these check tables.
Check tables for COLD records
When inserting COLD records, possibly available check tables are ignored. This
includes the client specified when importing data, which means that it is not
checked whether the client exists. If not, the import will fail without an error
message and the entries are written into the table with a non existing client.
Table names for COLD
Insertion of COLD records will succeed only for tables with names <= 25
characters.
Dynamic nodes and cluster tables
Dynamic nodes will not work with cluster tables like BSEG. SAP does not support
the SELECT DISTINCT statement correctly. Duplicates are not eliminated.
Therefore the performance will be poor. Enter an attribute object in the field Value
restriction at the dynamic node type.
String, Sstring or Rawstring data types in tables
String, Sstring or Rawstring data types are not supported in tables used by
DocuLink views.
Packed and float format at dynamic node types
Dynamic node types do not support selection fields with the data type packed (P)
or float (F) as COLLECT (non-info) fields.
Customizing output masks at dynamic node types
When an output mask is defined for the COLLECT field of a dynamic node type,
only selection fields with the data types CHAR and DATE are supported.
Using F4 help for authorization fields
34 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
When using the F4 help to enter authorization fields for authorization checks at
the attribute object, wildcards may be ignored. Restrict the amount of hits within
the search help screen instead.
7.3.2 Visualization
Problems when displaying archived documents with Web Viewer
The maintenance table /IXOS/OA_CUST_A (viewer customizing) offers a flag
called Open in curr. Window. The program code of this feature uses the SAP
function module CALL_BROWSER. In case of problems when displaying
archived documents with the WebViewer check the following SAP notes:
• SAP note 1128338 - CALL_BROWSER does not open URL in new window
• SAP note 1061637 - Problems with the CALL_BROWSER function module
Displaying several documents at the same time
When several documents are selected and you click on Display, not all selected
documents may be displayed. This is due to a synchronization problem between
the SAP GUI and the applications opened to display the documents. We
recommend displaying documents one at a time.
“Screens as popups” option
When displaying screens as pop ups, the pop ups may not be displayed correctly
after scrolling down in one of them. If a seemingly empty popup appears, try
scrolling upwards to display the “missing” fields. This is an SAP problem and
depends on the patch level of the SAP system and on the used SAP GUI.
Unnecessary scrollbars in pop ups
Sometimes scrollbars are displayed even in small pop ups where they are not
necessary. To avoid this behavior, implement SAP note 592607.
7.3.3 SAP GUI for HTML
Customizing (J6NP transaction)
Customizing via the J6NP transaction is not supported in the SAP GUI for HTML.
Common SAP GUI features
Not all common SAP GUI features like integration of desktop programs or certain
controls are supported.
35 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
ITS and selection screens
When using ITS, if the Screen as Popup option is activated in the header of a
view you must use the Refresh function to get the selection screen when you
open a node that has been assigned for such use. To avoid this effect and get the
selection screen directly, do not use the Screen as Popup option.
Displaying columns in a hitlist
In order to display columns in a hitlist correctly, a fixed font has to be set in the
corresponding ITS CSS file columntreedhtml.css.
Checkbox alignment
Checkboxes are automatically aligned to the left in the SAP GUI for HTML.
Displaying FAX documents inplace
FAX documents can only be displayed inplace using the Open Text Imaging:
Windows Viewer.
Archiving documents via front-end
Archiving scenarios do not work with SAP GUI for HTML.
7.3.4 Livelink Business Application Integration (BAI)
Displaying multi-value properties in IXOS Records
IXOS Records with multi-value properties cannot be displayed correctly in Open
Text DocuLink for SAP Solutions. Only one value of the property is displayed.
Exporting float values
SAP records with float values are not exported, as no data type for such values
exists in Livelink ECM – PDMS Context Server.
IXOS Records with time stamps
Timestamps in IXOS Records cannot be used in queries to retrieve data from a
Livelink ECM – PDMS Context Server, as no unique data type exists for
timestamps in SAP systems. The only exception is the creation date for IXOS
records.
When exporting SAP records with timestamps, the SAP timestamps cannot be
mapped to the PDMS Context Server data type DATETIME. Instead, use a string
or decimal type that corresponds to the SAP data dictionary type used for the
timestamp. (However, timezone conversion and date/time formatting is not
available for these types.)
36 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
Initial values in IXOS Records
Properties in IXOS Records for which no values have been set yet are displayed
with initial values in the SAP system. You cannot specify queries in SAP to select
all records where properties are unset.
Relations in Queries
In queries to retrieve data from a Livelink ECM – PDMS Context Server, you
cannot use ECR relations. Use the required IXOS Record type directly.
Special characters in Administration for ECR Context Server
In the Administration for ECR Context Server settings in DocuLink, special
characters are not supported for the following parameters:
• Organization for logon in ECR
• Domain for logon in ECR
• User for logon in ECR
If the Livelink ECM – PDMS Context Server server = 6.0D is used, characters
supported by ISO-8859-1 are also supported for these parameters.
New standard data model in the Livelink ECM – PDMS Context Server 6.0E
for the Livelink BAI scenario
During data export from an SAP system to a PDMS Context Server server using
the Livelink BAI functionality, exported ArchiveLink documents are reclassified
(specialized) from the general ixos.dms:Entity type to the special
ixos.bai:Document type. Therefore, some prerequisites must be fulfilled.
Support of a two layer data model in Livelink ECM – PDMS Context Server
6.0E
The standard data model for PDMS Context Server 6.0E has been changed to a
two layer model. For the BAI service, you must apply patch CR60-052 to the
PDMS Context Server server, and patch PD095-013 to the Livelink ECM – PDMS
Document Modeler.
Special permissions for the transfer user (BAI user)
The BAI user requires the write properties and ACL write permissions for
ArchiveLink documents archived to the ixos.dms:Entity. An ACL mapping
configuration must be specified on the PDMS Context Server (e.g. for the
DMSALDefaultUser user for ArchiveLink documents without SecKeys).
If documents are archived using ODMA and DesktopLink, the BAI user requires
Full Access permission to the ixos.dms:Entity data record type on the PDMS
37 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
Context Server, in addition to the specified ACL mapping configuration. Add the
BAI user to the EntityFullAccess group in Open Text User Management.
For details on ACL mapping configuration, see the “Permissions and ArchiveLink
interface” section in the Livelink ECM – PDMS Document Modeler -
Customization Guide (CC-CGD).
7.3.5 Open Text Imaging: DesktopLink
Archiving via Open Text Imaging: DesktopLink
Sometimes the SAP logon window is opened behind all other windows. In this
case, use Alt-Tab to move the SAP logon window to the front.
Assigning multiple documents via Open Text Imaging: DesktopLink
The number of files that can be assigned with a single command via Open Text
Imaging: DesktopLink is limited, due to the technical restriction that command line
parameters may only contain up to 256 characters. Thus, the precise restriction
depends on the length of the file and path names of the documents to be
assigned.
SAP GUI Support
Logon with DesktopLink scenario may fail with SAP GUI 6.20 when SAP system
distinguishes between upper and lower case password; in this case upgrade to
SAP GUI 7.10 or higher.
7.3.6 Open Text Imaging Clients
Annotations on SAP print lists
The annotations functionality for SAP print lists is disabled for print lists displayed
without a page index. For further restrictions see the KC:
https://knowledge.opentext.com.
Java Viewer inplace in DocuLink view
If a Java Viewer = 6.0 is displayed inplace in Open Text DocuLink for SAP
Solutions view, the context menu is not displayed correctly. Thus it is not possible
to select a context menu option (e.g. to create Notes).Using Java Viewer 9.5
inplace, display is not possible at all.
In both cases, use the old SAP GUI visual design (option in the SAP
Configuration settings), or disable the inplace view for DocuLink (setting in view
header data).
Web Viewer (< 9.6.0) inplace in DocuLink view
38 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
When the Web Viewer (< 9.6.0) is displayed inplace in a Open Text DocuLink for
SAP Solutions view, notes to the document cannot be displayed or added, as the
necessary protocol is not supported by SAP. If possible, use the old SAP GUI
visual design (option in the SAP Configuration settings) or disable the inplace
view for Open Text DocuLink for SAP Solutions (setting in view header data).
Reference 203652
Inplace viewing of TIF documents using the Open Text Imaging: Windows
Viewer
TIF documents stored within the SAP Content Management document model
cannot be displayed inplace in the HTML control using the Open Text Imaging:
Windows Viewer.
Java Viewer and SSL support
HTTPS is not available for the Java Viewer.
7.3.7 Forms Management for ECR
Forms Management for Livelink ECM – PDMS Context Server 6.0C
Migrating forms maintained in SAP to a Livelink ECM – PDMS Context Server is
not supported.
7.3.8 Other Restrictions
Migration report
The migration report /IXOS/RT_AL_SCENARIO only moves the main component,
not additional components such as notes, annotations, page index or attributes.
Reference 144870
39 | Open Text Archiving and Document Access for SAP Solut ions 9.8.0
www.opentex t . com
For more information about Open Text products and services, visit www.opentext.com. Open Text is a publicly traded company on both NASDAQ (OTEX) and the TSX (OTC).
Copyright © 2010 by Open Text Corporation. Open Text and The Content Experts are trademarks or registered trademarks of Open Text Corporation. This list is not exhaustive. All other trademarks or registered trademarks are the property of their respective owners. All rights reserved.
8 Contact Information
Open Text Corporation
275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1
Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544
International: +800-4996-5440
Fax: +1-519-888-0677
E-mail: mailto:[email protected]
FTP: ftp://ftp.opentext.com
Knowledge Center: https://knowledge.opentext.com/
For more information, visit http://www.opentext.com