OpenText Employee File Management

Installation Guide
The OpenText Employee File Management installation guide
describes the installation of the OpenText Employee File
Management 4.0 SP1 components.

EIM040001-IGD-EN-1

OpenText Employee File Management

Installation Guide
EIM040001-IGD-EN-1
Rev.: 26. Mar. 2014
This documentation has been created for software version 4.0.1.
It is also valid for subsequent software versions as long as no new document version is shipped with the product or is
published at https://knowledge.opentext.com.
Open Text SA
40 Avenue Monterey , Luxembourg, Luxembourg L-2163
Tel: 35 2 264566 1
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
Email: support@opentext.com
FTP: ftp://ftp.opentext.com
For more information, visit http://www.opentext.com

Copyright 2014 by Open Text Corporation

OpenText is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is not
exhaustive of other trademarks, registered trademarks, product names, company names, brands and service names
mentioned herein are property of Open Text SA or other respective owners.
Disclaimer
No Warranties and Limitation of Liability
Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.

Table of Contents
1

About OpenText Employee File Management ........................ 5

1.1
1.2
1.2.1

What is OpenText Employee File Management? ................................. 5

About this document .......................................................................... 5
Target audience ................................................................................ 6

Checking prerequisites ............................................................. 7

2.1
2.2
2.3

SAP prerequisites ............................................................................. 7

OpenText prerequisites ..................................................................... 8
Installation tool .................................................................................. 8

Summary of installation steps ................................................. 9

Installing ................................................................................... 11

4.1
4.2
4.3

Installing packages .......................................................................... 11

Activating BC sets ........................................................................... 13
Configuring Web Dynpro ................................................................. 16

Importing EPA archive for ESS/MSS and HR

administrator ............................................................................ 19

Installing integration for Employee Interaction Center

(EIC) .......................................................................................... 21

Upgrading ................................................................................. 23

7.1
7.2
7.3

Upgrade from EFM 3.0 or 3.5 to EFM 4.0 ......................................... 23

Delta upgrade from EIM 2.5 to EFM 3.0 ............................................ 23
Upgrading the SAP system .............................................................. 25

EIM040001-IGD-EN-1

OpenText Employee File Management

iii

Chapter 1

About OpenText Employee File Management

1.1 What is OpenText Employee File Management?
OpenText Employee File Management (EFM) provides employees in the Human
Resources (HR) department access to all HR-related documents in an electronic
personnel file. Thus, working with paper documents can be reduced to a minimum.
EFM offers data protection that guarantees only authorized employees can access
the documents. Combined with OpenText Archive and Storage Services, EFM
provides secure long-term storage.
EFM provides a clear folder structure of content such as original documents, master
data, employee-related emails and Microsoft Office documents in SAP. Double-click
on a document opens it in the appropriate viewer. The search function makes
retrieving information on employees easier.
EFM provides a direct link to the SAP ERP Human Capital Management (HCM)
objects. So, you can access the corresponding SAP transaction to view, change, or
create data records. Creation of documents is supported by integration of an upload
function in Employee-Self-Service (ESS) and Manager-Self-Service (MSS); a central
Document Inbox manages typical document workflows.
For quick and easy access to documents in a web-based environment, EFM offers the
EFM Web UI, including a feature that allows you to browse through thumbnails of
the documents. The EFM Web UI is based on the SAP Web Dynpro technology.
For mobile access to documents, EFM provides a document viewer with extensive
filtering capabilities. Currently, Android-based devices and the iPad are supported.

1.2 About this document

This guide describes the installation and upgrade process in the SAP environment
only.
For information on the other packages, see the individual installation guides. For
information on supported hardware and software platforms, check the Release
Notes in the OpenText Knowledge Center.
Important
Note that there may be a more recent version of this installation guide in the
OpenText Knowledge Center. Look there for the most up-to-date version.

EIM040001-IGD-EN-1

OpenText Employee File Management

Chapter 1 About OpenText Employee File Management

1.2.1

Target audience
The following knowledge is required from the person dealing with the installation
as described in this document:

In-depth knowledge of SAP administration tasks, in particular the SAP Add-On

Installation Tool (SAINT).

Basic knowledge of the employed operating system.

For installation of the ESS/MSS scenario, basic knowledge about administration

tasks in the SAP NetWeaver Portal environment is required.

OpenText Employee File Management

EIM040001-IGD-EN-1

Chapter 2

Checking prerequisites
2.1 SAP prerequisites
EFM can be installed on systems with SAP ECC 6.0 or higher.
Note: Special versions are available for SAP ECC 6.0 EhP4 and EhP5; however,
all EFM versions can also be used on higher systems with higher versions.
Check the following prerequisites prior to installation:
SAP support packages
Check the latest version of the Release Notes in the OpenText Knowledge Center
for required support packages for the employed SAP system prior to
installation.
OSS notes
Check the following OSS notes to avoid known problems with the SAP Add-On
Installation Tool (SAINT):

SAP 7.00 - OSS note 822380

Installation information - OSS note 1267724

SAPCAR tool - OSS note 212876

Web Dynpro ABAP

The necessary configuration of Web Dynpro has to be provided on the server
which will provide the Web Dynpro UI application of Employee File
Management.
For more details see Configuring Web Dynpro on page 16.
SAP NetWeaver Portal 7.0 (ESS/MSS and HR administrator scenarios only)
In order to run the ESS/MSS and HR administrator scenarios in SAP NetWeaver
Portal, the SAP NetWeaver Portal 7.0 (2004s) or higher is required and the
business packages for ESS/MSS and HR administrator must be installed in the
portal.
Required minimum versions for the ESS/MSS business packages are:

Employee Self-Service 1.0 SP 14 (BP_ERP5ESS 1.0 SP14)

Manager Self-Service 1.0 SP 14 (BP_ERP5MSS 1.0 SP14)

The HR administrator scenario requires the business package HR Administrator

1.41 SP2 (BP_ERP05 HR ADMINISTRATOR 1.41 SP2)
Installation and administration of SAP NetWeaver Portal and the business
packages is described in the respective SAP documentation.

EIM040001-IGD-EN-1

OpenText Employee File Management

Chapter 2 Checking prerequisites

Note: If you plan to run the ESS/MSS and HR administrator scenarios in

the SAP NetWeaver Business Client (NWBC), you do not require an
installed SAP NetWeaver Portal; however, this solution requires SAP ECC
6.0 EhP5 as a minimum.

2.2 OpenText prerequisites

Check the following prerequisites prior to installation:

OpenText Archiving and Document Access for SAP Solutions 10.0 SP2 (software
component OTEXBAS) must be installed on the SAP system. The corresponding
software can be downloaded from the OpenText Knowledge Center.

In order to use EFM full-text search and retention management (software

component OTEXERM), OpenText Extended ECM for SAP Solutions 10.0 SP2
(software component OTEXRL) and EFM software component OTEXEIM must be
installed on the SAP system.

In order to support the thumbnail view in the DocuLink Web UI, the OpenText
Imaging Web Viewer 10.0.0 is required as a minimum. However, OpenText
strongly recommends to employ OpenText Imaging Web Viewer 10.2.0 with the
latest patch. The corresponding software can be downloaded from the OpenText
Knowledge Center.

Refer to the most recent product documentation, release notes and patches
description released in the OpenText Knowledge Center.
Note: If you upgrade from EFM 3.5 or 3.5 SP1, note that tickets created with
the ESS and MSS Upload applications cannot be processed with the new EFM
Document Inbox in EFM 4.0. Therefore it is required to process all open tickets
before an upgrade to EFM 4.0 is started. For details see also Upgrading
on page 23.

2.3 Installation tool

EFM uses the SAP Add-On Installation Tool (SAINT) for installation. SAINT uses
single PAT files (extension *.PAT) which integrate several transport files; these
collections are also called packages.
On the product CD, the single PAT files are archived in SAPCAR files (extension
*.SAR). The different SAPCAR files are located in a DATA folder below the respective
package folder named as the package and SAP release. For example the SAPCAR file
INST_ERP_600/DATA/OTEXEIM_INST_0400_600.SAR contains the archived PAT file
to install the package for EFM on SAP ECC 6.0.
Note: The handling of the installation procedure within SAINT differs
depending on the SAP system used. For more details, see the respective SAP
documentation.

OpenText Employee File Management

EIM040001-IGD-EN-1

Chapter 3

Summary of installation steps

The following overview summarizes the required installation steps and their
sequence both for the prerequisites and EFM:
1. Install OpenText Archiving and Document Access for SAP Solutions 10.0 using
SAINT transaction.
2. Install OpenText Archiving and Document Access for SAP Solutions 10.0 SP1
using SPAM transaction.
3. Install OpenText Archiving and Document Access for SAP Solutions 10.0 SP2
using SPAM transaction.
4. Install Employee File Management:

Employee File Management 4.0 Add-On using SAINT transaction.

Employee File Management 4.0 BC sets using SCPR20 transaction.

5. Install ESS/MSS and HR Administrator integration; this is optional, and is only

required for SAP portal:

Employee File Management 4.0 ESS/MSS, HR Administrator Package (EPA).

6. Install Employee Interaction Center (EIC) integration; this is optional, and is only
required for SAP CRM 7.0:

Employee File Management CRM Add-On using SAINT transaction and CRM
Add-On Manager.

Employee File Management CRM Add-On BC sets using SCPR20 transaction.

7. Install Employee File Management RM integration; this is optional, and is only

required when you want to use RM functionality or search functionality:

OpenText Extended ECM for SAP Solutions 10 Add-On using SAINT

transaction.

OpenText Extended ECM for SAP Solutions 10 Add-On SP1 using SPAM
transaction.

OpenText Extended ECM for SAP Solutions 10 Add-On SP2 using SPAM
transaction.

Employee File Management RM 4.0 Add-On using SAINT transaction.

Employee File Management RM Add-On BC sets using SCPR20 transaction.

Important
Following the order of these steps is crucial to avoid error messages during
installation.

EIM040001-IGD-EN-1

OpenText Employee File Management

Chapter 4

Installing
This chapter describes the installation of the EFM packages on an SAP application
server. For general information about installing in an SAP environment, see also
Checking prerequisites on page 7 with .
Note: During installation process, the following differing terms are used:
Component

Release

SAP
Release

OCS
Filename

OCS
Package

Password

OTEXEIM

0400_600

SAP ECC
>= 6.0

Q6B002007 SAPK-303
3437_00000 COINOTE
13.PAT
XEIM

4D779C6D53

OTEXEIM

0400_604

SAP ECC
>= 6.0 EhP4

Q6C002007 SAPK-403
3437_00000 COINOTE
01.PAT
XEIM

4A779C6D53

OTEXEIM

0400_605

SAP ECC
>= 6.0 EhP5

Q6E002007 SAPK-503
3437_00000 COINOTE
01.PAT
XEIM

4B779C6D53

OTEXERM

0400_600

SAP ECC
>= 6.0

Q6B002007 SAPK-303
3437_00000 COINOTE
16.PAT
XERM

4D77876D53

OTEXEIC

0400_700

SAP CRM
>= 7.0

Q52002011 SAPK-103
4596_00000 COINOTE
92.PAT
XEIC

4F779C6353

4.1 Installing packages

The EFM components are provided as add-on packages and can be downloaded
from the Employee File Management 4.0 download section in the OpenText
Knowledge Center.
The following packages and included EFM components are available:
Package

Source path

Component and release

OTEXEIM_INST_0400_600.SAR

INST_ERP_600\DATA\

OTEXEIM 0400_600

OTEXEIM_INST_0400_604.SAR

INST_ERP_604\DATA\

OTEXEIM 0400_604

OTEXEIM_INST_0400_605.SAR

INST_ERP_605\DATA\

OTEXEIM 0400_605

OTEXERM_INST_0400_600.SAR

INST_ERM_600\DATA\

OTEXERM 0400_600

OTEXEIC_INST_0400_700.SAR

INST_CRM_700\DATA\

OTEXEIC 0400_700

EIM040001-IGD-EN-1

OpenText Employee File Management

11

Chapter 4 Installing

The EFM components are used as follows:

OTEXEIM
Mandatory component for SAP ECC which includes the main functionality of
EFM.
Some scenarios are only supported from a certain SAP ECC enhancement
package onwards.
OTEXEIM 0400_600
Basic EFM package.
OTEXEIM 0400_604
Includes all features of OTEXEIM 0400_600; in addition, supports HCM
processes & forms and the EFM HR administrator integration for the SAP
NetWeaver Portal.
OTEXEIM 0400_605
Includes all features of OTEXEIM 0400_604, in addition, supports the SAP
NetWeaver Business Client (NWBC).
OTEXERM
Optional component for SAP ECC that only needs to be installed if EFM full-text
search and/or retention management for HR documents shall be used.
This component can only be installed if the software component OTEXRL (that is
part of OpenText Extended ECM for SAP Solutions) was previously installed.
OTEXEIC
Optional component for SAP CRM that only needs to be installed, if the CRM
Employee Interaction Center integration for EFM shall be used.

Caution
Installation of the EFM records management package
OTEXERM_INST_0400_600.SAR requires further configuration steps to
make it operational. Therefore, you should install the
OTEXERM_INST_0400_600.SAR package only if you require Records
Management or Search functionality.
To install the packages:
1.

Log on with the Client 000 in English.

2.

Load the installation packages in one of the following ways:

a.

Load the packages from the application server:

i.

ii.

Copy the respective SAPCAR file (*.SAR) from the product CD to the
target SAP application server in the /usr/sap/trans folder (that is the
parent folder of the DIR_EPS_ROOT folder).
Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with
the following command:
SAPCAR xvf <name of SAPCAR file>

12

OpenText Employee File Management

EIM040001-IGD-EN-1

4.2. Activating BC sets

The resulting PAT file will be extracted to the EPS/in folder relative to
the path of the SAPCAR file.
b.

Load the packages from the front end by selecting the respective SAPCAR
file (*.SAR) from the local file system. The file will be decompressed
automatically.

3.

Carry out the import of the package as described in the SAP documentation.

4.

Load the suport packages and install them using the SPAM transaction as
described in the SAP documentation.

5.

After the import has finished, continue with the activation of the BC sets; see
Activating BC sets on page 13.

4.2 Activating BC sets

For every client, the Business Configuration Sets (BC sets) must be activated after
installation. The BC sets are activated in the specific client that contains the business
scenarios.

Caution
For clients that already have an old version of the DocuLink project $EIM
installed, the old version must be deleted first.
For all clients that already have an old version of the DocuLink project $EIM
installed, first delete the older version as described in the following; then continue
with the standard BC set activation.
To delete an older version of the DocuLink project $EIM:
1.

Execute the J6NP transaction.

2.

In the overview, delete the existing DocuLink project and its versions as
follows:
a.

Select a version and press SHIFT-F2 to make the version obsolete. Repeat
this step for every version of $EIM.

b.

Finally, select the entry of the $EIM project and press SHIFT-F2 to delete
the entire project.

c.

During the process, dialogs are displayed to use customizing transport

requests for the deletion. Create a new request for the entire deletion.
Note: After complete deletion of $EIM, do not import this customizing
request because this would overwrite the new project version
activated using BC set activation.

At this stage, all old versions of DocuLink project $EIM are deleted and do not
interfere with any subsequent BC set activation.

EIM040001-IGD-EN-1

Installation Guide

13

Chapter 4 Installing

Caution
For the following procedure, you have to log on in English in order to
avoid problems with the activation of the BC sets.
To activate BC sets:
1.

Log on in English and execute the SCPR20 transaction.

The Business Configuration Set screen appears.

2.

Activate the BC set /OTEXEIM/EFM_COMPLETE_040.

Note: To activate the complete BC set, you must select activation mode
Expert Mode in the Activation Options dialog.
The BC set /OTEXEIM/EFM_COMPLETE_040 comprises the following single BC
sets:
BC sets containing the definition of DocuLink project $EIM
/OTEXEIM/DOCULINK_PROJ_EFM_040 To activate this BC set, you must
select activation mode Expert Mode in the Activation Options dialog.
/OTEXEIM/DCLINK_PROJ_EFM_TXT_040.
BC set containing authorization profiles related to EFM-specific roles
/OTEXEIM/EFM_ROLES_040

BC set containing the default settings for the EFM Cockpit

/OTEXEIM/EFM_COCKPIT_040

BC set containing the default settings for the EFM mobile API
/OTEXEIM/EFM_MOBILE_APP_040

BC sets containing customizing of IMG activity OpenText Business Suite for

SAP Solutions > Solution Framework > Solution Extensions
/OTEXEIM/SF_CHG_DCLINK_TITL_040 (Change DocuLink titlebar)
/OTEXEIM/SF_ENABL_THUMB_VIEW_040 (Enable thumbnail for DocuLink in
SAP GUI, delivered only for SAP ERP 6.0)
/OTEXEIM/SF_CHG_DOCULINK_PIC_040 (Change DocuLink start picture)
/OTEXEIM/SF_CHG_DCLINK_VDESC_040 (Change DocuLink view
description)
/OTEXEIM/SF_ADD_FUNCT_DCTOOL_040 (Add function codes in DocuLink
toolbar)
/OTEXEIM/SF_ADD_FUN_NODETYPE_040 (Add function codes at DocuLink
nodetype)
BC sets containing customizing of IMG activity OpenText Business Suite for
SAP Solutions > Solution Framework > SAP Workflow
/OTEXEIM/SF_MNT_ACT_WF_CUST_040 (Maintain activity workflow
customizing)

14

OpenText Employee File Management

EIM040001-IGD-EN-1

4.2. Activating BC sets

BC sets containing customizing of IMG activity OpenText Business Suite for

SAP Solutions > Employee File Management (EFM) > Basic settings
/OTEXEIM/EFM_BS_ASSIGN_VALUE_040 (Assign values for basic settings)
/OTEXEIM/EFM_BS_CONF_ACT_LOG_040 (Configure activity logging)
BC sets containing customizing of IMG activity OpenText Business Suite for
SAP Solutions > Employee File Management (EFM) > Guest User
/OTEXEIM/EFM_GU_ASSIGN_VALUE_040 (Assign values for basic settings)
/OTEXEIM/EFM_GU_DEFINE_SCEN_040 (Define scenario)
/OTEXEIM/EFM_GU_ACCESS_TYPE_040 (Maintain access type specific setting)
BC set containing ESS/MSS customizing of IMG hierarchy
/OTEXEIM/EFM_ESS_MSS_040 (Customizing for ESS/MSS)
BC set containing HR customizing of IMG hierarchy (only for ERP 6.0 EhP4
and higher)
/OTEXEIM/EFM_HRADMIN_040 (Customizing for HR Administrator)
BC set containing roles for Netweaver Business Client integration (only for
ERP 6.0 EhP5 and higher)
/OTEXEIM/EFM_NWBC_ROLES_040

BC set containing customizing of IMG activity OpenText Business Suite for

SAP Solutions > Employee File Management (EFM) > Reporting
/OTEXEIM/EFM_REPORTING_040

BC set containing customizing of IMG activity OpenText Business Suite for

SAP Solutions > Employee File Management (EFM) > Document Upload and
Inbox Application
/OTEXEIM/EFM_UPLOAD_INBOX_040 (Self-Service Document Upload and
Inbox configuration)
/OTEXEIM/EFM_UPLOAD_INBOX_HL_040 (Hyperlink customizing for EFM
Web UI Inbox)
After activation, this BC set must be customized manually. For details see
OpenText Employee File Management - Administration Guide (EIM-AGD).
Note: For more details, see the respective SAP documentation.
3.

The /OTEXEIM/EFM_ROLES_040 BC set activated with the /

OTEXEIM/EFM_COMPLETE_040 requires the following steps to ensure proper
profile generation:
a.

Execute the PFCG transaction.

b.

Select the Utilities > Mass generation command from the menu.

c.

Select the Roles with Non-Current Profiles option; in the Role field enter
the pattern /OTEI/*. Click the

button.

The profiles are displayed as a list; the non-generated profiles feature a

icon.

EIM040001-IGD-EN-1

Installation Guide

15

Chapter 4 Installing

d.
4.

Select the required non-generated profiles and click the

generate the profiles.

button to

The /OTEXEIM/EFM_ESS_MSS_040 BC set activated with the /

OTEXEIM/EFM_COMPLETE_040 requires an additional report to deliver

information of service URLs and sets service descriptions which cannot be

delivered via BC sets (STRING and XSTRING values are not supported by BC
sets).

5.

6.

a.

Execute the SE38 transaction.

b.

Execute the /OTEI/XSS_SET_CUSTOMIZING report.

Only for ERP 6.0 EhP4 and higher: The /OTEXEIM/EFM_HRADMIN_040 BC set
activated with the /OTEXEIM/EFM_COMPLETE_040 requires an additional report
which sets customizings that cannot be delivered via BC sets.
a.

Execute the SE38 transaction.

b.

Execute the /OTEI/HRADMIN_SET_CUSTOMIZING report.

Activate the BC set /OTEI/RM_SEARCH_CONFIG_035 which customizes the

search template configuration in the IMG activity OpenText Business Suite for
SAP Solutions > Employee File Management (EFM) > Employee File
Management Full Text Search Configuration.
For the activation of this BC set you have to select activation mode Expert Mode
in the Activation Options dialog.
Note: When you activate the BC set, an Enterprise Library ID has to be set.
The Enterprise Library ID can be set with the IMG activity OpenText
ECMLink for SAP Solutions > Maintain Enterprise Library Server
Settings.

4.3 Configuring Web Dynpro

To configure Web Dynpro:
1.

Perform general Web Dynpro configuration of the web application server(s)

which provide the Web Dynpro UI; for example configuration of the ICM and
activating services.
For details see the respective SAP documentation.

2.

Check the activation of the following services by executing the SICF transaction:
<Path of Web Dynpro services>
/ixos/dc
/ixos/dcview
/ixos/dcview_xss
/oteb/swf_wd_comp_main
/oteb/swf_wd_agent_hlp
/otei/du_wd_inbox
/otei/du_wd_upload_ess

16

OpenText Employee File Management

EIM040001-IGD-EN-1

4.3. Configuring Web Dynpro

/otei/du_wd_upload_mss
/otei/fu_wd_multi_fileupload
/otei/rp_wd_reporting
<Path of SAP namespace>
/bc/otei_fileupload
/bc/otei_inboxupld
/bc/otei_api
/bc/otei_api_auth
/bc/otei_api_meta
/bc/bsp/otei/fu_wd_bsp_start
/bc/bsp/otei/moa_ui_app
/bc/bsp/otei/rp_wd_bp_hdr

3.

For SAP ECC 6.0 EhP4 and higher, check the activation of the following
services:
<Path of Web Dynpro services>/otei/hradmin_dc_int
<Path of Web Dynpro services>/otei/hradmin_profs_show

4.

For SAP ECC 6.0 EhP5, check the activation of the following services:
<Path of Web Dynpro services>/otei/ess_dc_int

EIM040001-IGD-EN-1

Installation Guide

17

Chapter 5

Importing EPA archive for ESS/MSS and HR

administrator
EFM integrates its functionality also in the SAP HR portal applications EmployeeSelf-Service (ESS) and Manager-Self-Service (MSS) as well as the SAP HR
Administrator (HRA) portal component. If your system employs a business package
using Web Dynpro Java (WDJ) configured by the SAP Homepage Framework, you
have to import the respective EPA archive file into the SAP NetWeaver Portal 7.0
system. You can find the EPA archive file
com.opentext.efm_4_0_xss_hradmin.epa on the product CD.
To import the EPA archive:
1.

Start the Package Import Editor in the SAP NetWeaver Portal.

2.

Choose if you want to import from the client or the server:

a.

b.

If you import from the server, browse to the directory containing

com.opentext.efm_4_0_xss_hradmin.epa and select the file to be
imported.
If you import from the client, select the
com.opentext.efm_4_0_xss_hradmin.epa file on the client and upload it
to the server. The objects of the EPA archive are listed in the object preview.
Select the file to be imported.

3.

Specify that existing portal content shall be overwritten by the import.

4.

Start the import.

A new screen shows the import status; you can check if the objects are imported
correctly.

With the import of the EPA archive, OpenText portal directories are created. These
are subdirectories of the portal directories Content for Line Managers, Content for
Specialists and End User Content respectively.

EIM040001-IGD-EN-1

OpenText Employee File Management

19

Chapter 5 Importing EPA archive for ESS/MSS and HR administrator

Caution
For using the ESS/MSS integration, it is essential that the OpenText portal
directories and their sub-components are either assigned directly to an
individual user, or collectively to user groups and roles. The created access
control lists (ACLs) should at least consider the administrator read
permission and the end user permission level.

20

OpenText Employee File Management

EIM040001-IGD-EN-1

Chapter 6

Installing integration for Employee Interaction

Center (EIC)
EFM offers an integration between an Employee Interaction Center (EIC) and EFM
in an ERP system.
Note: If you have already installed the integration for EIC with EFM 3.0 (with
SP2), you dont have to perform an update.
To install the integration in the CRM system:
1.

Install the SAPCAR file OTEXEIC_INST_0400_700.SAR in the CRM system using

the SAINT transaction and the CRM Add-On Manager. For details, see
Installing on page 11.

2.

Activate the BC sets delivered in the installation package.

To activate BC sets:
1.

Execute the SCPR20 transaction.

The Business Configuration Set screen appears.

2.

Activate the following BC sets:

BC set containing customizing of IMG activity Customer Relationship
Management > Interaction Center WebClient > Basic Functions > Define
Navigation Bar Profile
/OTEXEIC/EFM_NAV_BAR_040 (Adds EFM-specific navigation bar buttons)
BC set containing EFM-specific roles
/OTEXEIC/EFM_ROLES_040 (Example role for the EFM integration)
BC set containing customizing of IMG activity Customer Relationship
Management > Interaction Center WebClient > Basic Functions > Transaction
Launcher > Define URLs and Parameters & Copy/Delete Launch Transactions
/OTEXEIC/EFM_TA_LAUNCH_040 (Creates EFM-related transaction launch ID
and URL)
Note: When using SAP CRM 7.01 and higher versions, you have to
select activation mode Expert Mode in the Activation Options dialog.
BC set containing customizing of IMG activity Customer Relationship
Management > OpenText Employee File Management Integration >
Webdynpro themes
/OTEXEIC/EFM_THEMES_040 (Default settings for Web Dynpro themes)

EIM040001-IGD-EN-1

OpenText Employee File Management

21

Chapter 6 Installing integration for Employee Interaction Center (EIC)

BC sets containing customizing of IMG activity Customer Relationship

Management > OpenText Employee File Management Integration > URL
Parameters
/OTEXEIC/EFM_URL_PARAMETER_040 (Default URL parameter customizing)

22

OpenText Employee File Management

EIM040001-IGD-EN-1

Chapter 7

Upgrading
7.1 Upgrade from EFM 3.0 or 3.5 to EFM 4.0
No specific upgrade packages are delivered for EFM 4.0.
For an upgrade from EFM 3.0 or 3.5 to EFM 4.0, install the standard EFM 4.0
installation packages in your system and execute the installation tasks as described.
Note: If you upgrade from EFM 3.0, you should disable the service <Path of
Web Dynpro services>/otei/swf_wd_comp_main using the SICF transaction.
If you upgrade from EFM 3.5 or 3.5 SP1, note that tickets created with the ESS
and MSS Upload applications cannot be processed with the new EFM
Document Inbox in EFM 4.0. Therefore it is required to process all open tickets
before an upgrade to EFM 4.0 is started.

7.2 Delta upgrade from EIM 2.5 to EFM 3.0

The upgrade from EIM 2.5 to EFM 3.0 is called a delta upgrade, because the version
of OpenTexts Add-On package changes, while the SAP release remains unchanged.
There are specific EFM delta upgrade packages.
The following delta upgrades are supported:
Table 7-1: Delta upgrades
Previous add-on release

Upgrade package required

OTEXEIM 0250_470

OTEXEIM_DELT_0300_470.SAR

OTEXEIM 0250_500

OTEXEIM_DELT_0300_500.SAR

OTEXEIM 0250_600

OTEXEIM_DELT_0300_600.SAR

OTEXEIM 0300_600

OTEXEIM_DELT_0300_604.SAR

Tip: Use the SAINT transaction to get an overview of the add-ons installed on
your SAP system.
Customers that upgrade to EFM 3.0 have to consider the following:

Due to dependencies between OpenText Archiving and Document Access for

SAP Solutions 9.8 (ADA) and EFM 3.0, an upgrade from EIM 2.5 to EFM 3.0 also
requires an update of ADA 9.6.2 to ADA 9.8. The ADA upgrade is automatically
requested during the update of EIM 2.5 to EFM 3.0.

EFM 3.0 is based on the version 3 of the DocuLink project $EIM, while EIM 2.5 is
based on version 2 of the project. To ensure that activation of the BC set

EIM040001-IGD-EN-1

OpenText Employee File Management

23

Chapter 7 Upgrading

containing this new project version does not cause problems, you must delete the
old project version as described in To delete an older version of the DocuLink
project $EIM: on page 13.

Some EFM customizing entries refer to the DocuLink project version. The EFMspecific BC sets that activate the EFM default customizing entries already
consider the new project version. However, if you have changed the EIM default
customizing in EIM 2.5, you have to make the same changes on the new EFM 3.0
specific customizing entries. The following customizing is affected:

Assign values for basic settings

Configure activity logging

Change DocuLink titlebar

Change DocuLink start picture

Change DocuLink view description

Add function codes in DocuLink toolbar

Add function codes at DocuLink nodetype

Assign EFM view to EFM DesktopLink scenario (maintenance view /

OTEI/T_DLV)

Solution Extension User-Exits

To perform a delta upgrade procedure:

1.

Select the appropriate upgrade package from the table Delta upgrades
on page 23.

2.

Copy the required SAPCAR files (*.SAR) from the product CD to the target SAP
application server in the /usr/sap/trans folder (that is the parent folder of the
DIR_EPS_ROOT folder).
File

Source path

OTEXEIM_DELT_0300_*.S DELT_*_<Release>\DATA\
AR

3.

Target path
/usr/sap/trans

Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with the

following command:

SAPCAR xvf <name of SAPCAR file>

The resulting PAT file will be extracted to the EPS/in folder relative to the path
of the SAPCAR file.
4.

Carry out import of package as described in the respective SAP documentation.

After the upgrade, most of the customizing and configuration will not change.

24

OpenText Employee File Management

EIM040001-IGD-EN-1

7.3. Upgrading the SAP system

7.3 Upgrading the SAP system

Depending on your current system configuration, you may perform an upgrade of
your SAP system from SAP R/3 Enterprise 4.70 or from SAP ECC 5.0 to SAP ECC
6.0. Note that EFM 3.5 requires SAP ECC 6.0 as a minimum. For a detailed list of the
supported combinations, refer to the Release Notes in the OpenText Knowledge
Center.
When you have to upgrade your SAP system where EFM 3.0 is already installed,
you must use the specific EFM exchange upgrade package during the upgrade of the
SAP system. If you use EFM 3.5 or 4.0, no specific package is required.
Because of the dependency on OpenText Archiving and Document Access for SAP
Solutions (ADA), the corresponding exchange upgrade package for ADA must also
be specified during the upgrade of the SAP system.
Details for this upgrade can be found in OpenText Archiving and Document Access for
SAP Solutions - Installation and Upgrade Guide (ER-IGD).
Note: Contact your OpenText consultant to plan your individual upgrade
strategy.

Caution
If you import an upgrade into an SAP system with EFM and the data of the
respective upgrade packages is not read (upgrade phase IS_SELECT), the
EFM add-on (that is OTEXEIM) will no longer work after the upgrade
procedure. Since the status of the system is then inconsistent, OpenText can
no longer accept any liability.
Upgrade
packages

The following exchange upgrades are supported:

Table 7-2: Exchange upgrades for SAP system
Upgrade from EFM on

Upgrade to

Upgrade package required

SAP R/3 Enterprise 4.7

SAP ECC 6.0

OTEXEIM_UPGR_0300_600.SAR

SAP ECC 5.0

SAP ECC 6.0

OTEXEIM_UPGR_0300_600.SAR

SAP ECC 6.0 or SAP

ECC 6.0 EhPx

SAP ECC 6.0 EhPy

No package; instead choose KEEP in

the upgrade phase IS_SELECT.
Vendor keys are required.

After an upgrade to SAP ECC 6.0 EhP4 or EhP5, you can install special packages

OTEXEIM 0400_604 or OTEXEIM 0400_605 with additional functions. For details, see

Installing packages on page 11.

Note: Make sure to re-install the respective support packages after the upgrade
procedure.

EIM040001-IGD-EN-1

Installation Guide

25

Chapter 7 Upgrading

Customizing

Any EFM-specific customizing will not be changed by an exchange upgrade, but the
versions for SAP ECC 6.0 and SAP ECC 6.0 EhP4 include the following additional
customizing activities and BC sets:
Additional BC sets for SAP ECC 6.0

/OTEXEIM/SF_ENABL_THUMB_VIEW_030 (Enable thumbnail for DocuLink in SAP

GUI)

/OTEXEIM/EFM_ESS_MSS_030 (Customizing for ESS/MSS)

Additional BC sets for SAP ECC 6.0 EhP4

/OTEXEIM/EFM_HRADMIN_030 EFM (Customizing for HR Administrator)
Additional IMG activities for SAP ECC 6.0 EhP4
HCM Processes & Forms Integration:

Connection between HR documents and Processes & Forms documents

User-Exits

To perform an upgrade procedure from SAP R/3 Enterprise 4.70 or SAP ECC
5.0 to SAP ECC 6.0 with efm30:
1.

Copy the required SAPCAR files (*.SAR) from the product CD to the target SAP
application server in the /usr/sap/trans folder (that is the parent folder of the
DIR_EPS_ROOT folder).
File

Source path

OTEXEIM_UPGR_0300_60 UPGR_ERP_600\DATA\
0.SAR

2.

Target path
/usr/sap/trans

Extract the SAPCAR file to the /usr/sap/trans/EPS/in folder with the

following command:

SAPCAR xvf <name of SAPCAR file>

The resulting PAT file will be extracted to the EPS/in folder relative to the path
of the SAPCAR file.
3.

Follow the standard SAP system upgrade instructions. During the upgrade
phase IS_SELECT, select the upgrade type for the installed add-ons Upgrade
with SAINT Package.
Note: No passwords are required for the upgrade packages.

4.

26

After the upgrade, no activation of BC sets is necessary.

OpenText Employee File Management

EIM040001-IGD-EN-1